Table of contents
- Why site audits?
- Automated Testing through SiteLint Audits Platform(AI Powered, real-time)
- Manual and User Testing
- UX / UI Support
- Remediation Support
- Active scanning mode
- Active Mode vs Passive Mode
- Want to know more?
Why site audits?
A site audit helps to identify a wide range of issues. It determines whether your site is accessible, optimized for search engine traffic, has any broken files or links, loads quickly, has security or privacy issues. A complete and detailed real-time site audit will give you a deeper understanding of how your content is operable by your users. Having all audits in one place helps to better understand the business impact.
SiteLint Audits are an all-in-one examination and analysis of your site to uncover issues that can impact Accessibility, Quality, Performance, Privacy, Security, and SEO. It also helps to gather runtime issues through Error and Console Tracking audit.
- Accessibility – we help to identify accessibility issues and provide recommendations needed to fix and improve your product and services as well as to meet Web Content Accessibility Guidelines (WCAG) standard (2.0 and above). If your organization requires Section 508 conformance, you need a Voluntary Product Accessibility Template (VPAT).
- Quality – identify dynamic URLs, determine page title, headings, meta content length, large images, and many more. Validate HTML and CSS as well as check for cross-browser compatibilities.
- Performance – find out why your site is loading slow.
- Privacy – determine whether best practices in security and privacy protection techniques are implemented.
- Security – test if the website has any obvious security flaws.
- Search Engine Optimization (SEO) – identify issues and get tips on optimising your site to get better ranking.
- Error and Console Tracking – catch console message and runtime issues to get better quality and stability.
Automated Testing through SiteLint Audits Platform
(AI Powered, real-time)
One Platform to work with Accessibility, Error and Console Tracking, Quality, Performance, Privacy, Security and SEO. Since all of these areas overlap with each other than having one place to manage them gives a wider perspective. It saves time as you have all reports in one place.
- Our automated scanning tool SiteLint Audits Platform helps you scan and monitor in real-time because it works on the client-side.
- One page – one report. When you change anything on the page the SiteLint Change Detection will be done automatically and results will be updated on the fly.
- Effectively Prioritization Bug Fixes. Knowing where the issues appear and how often the page has been visited leads to better prioritization of bug fixes.
- Better results and more automated testing. The Platform does not focus on project management as it cost overhead, communication overhead, and time overhead.
- Easy to track the remediation process. Once the issue has been fixed it will be gone automatically from the report.
- No need to schedule any monitoring or authentication flow because all SiteLint Audits are being executed on the client-side.
- We do not store sensitive data so it is safe to scan content with sensitive data.
- Managing false positives can be done directly in the code so you can instruct SiteLint Audits Platform about false positives.
- Running on a real user environment – our audits aren’t limited to a single environment. They are working on the client-side when visitors arrive on your site. That gives more precise results like what type of browser, operating system, device type, and more.
- All audits are SiteLint only. We are not using 3rd party tools.
Manual and User Testing
Finding the issues using the automated SiteLint Platform is the first step. However, a further step is to perform also manual testing. Some cases do require manual testing due to technical limitations. For example, accessibility checking for color contrast issues can’t be determined with 100% certainty and manual testing is the next step.
UX / UI Support
Checking UX / UI on the design level before it goes to the software development saves not only time but also makes the product and services more robust and accessible.
Our UX / UI Checklist will guide you to get better results. We can also help by doing UX / UI reviews and providing tips and tricks improvements.
Not sure how to fix the issues? We can help here. Our technical team can support you throughout the software development cycle:
Active scanning mode
SiteLint Audits works in an active way, unlike the classic passive way. The active way means that audits are being executed when users visit your site. Passive way means that your site is being scanned by the application located on the server-side.
Active Mode vs Passive Mode
|Feature||Active (SiteLint)||Passive (classic)|
|Environment||Always reflects real user environment.||Hermetic, mostly as a one-type of the environment with predefined settings and browser.|
|Scanning behind authentication||Does not require any settings.||It requires complex solutions to handle different authentication flows.|
|Fixes verification||Once the issues are fixed you only need to go to your fixed page, reload and then verify status directly in our SiteLint Audits Analytics.||Once the issues are fixed you need to crawl the page to see the results.|
|User specific settings||Not needed as SiteLint Audits are running on a real user environment.||Mostly running with default settings with a given few options like viewport size.|
|Fixes prioritisation||Always start from Critical Types of issues, but Active scanning helps you also to understand mostly visited pages so you can start fixing issues on those pages first.||Once the scan is performed using the passive scanning approach you need to walk through all issues, but without knowing which pages are most visited.|
|Monitoring||No need to set up anything as SiteLint Audits are always executed whenever your users visit your site.||Requires a set of various options like scheduling cadence, frequency, limit pages, scan level depth.|
|Production, Stage, Development other environments.||You only need to create a token with any additional identifier, e.g.
||Depending on the solution, the most common approach requires one of the following actions: set up a new project, define URL, configure scanning.|
|Performance||Since audits are running on the client-side it doesn’t engage server infrastructure for scanning.||Every scan requires a browser instance and performing a scan on the server-side.|