Web app accessibility, performance, security, SEO, and quality can generally be measured in one of two ways:
- Server-side: on a consistent, controlled environment.
- Client-side: on real users actually loading and interacting with the page.
Client-side and server-side web audits are two different approaches to evaluating a website’s accessibility, performance, usability, security, and SEO. The main difference between them is the location where the audit is performed.
Client-side web audit is done on the user’s device. Server-side web audit, on the other hand, is done on the web server by loading your page and run audits.
However, performing audits on the server-side isn’t necessarily reflective of how all users experience your site in reality. The condition of a site can vary dramatically based on a user’s device capabilities and network conditions, or people may be experiencing varying degrees of auditory, cognitive, physical, speech, and visual disabilities. It can also vary based on whether or not a user is interacting with the site.
This approach means that we aren’t crawling your website, but all audits are being performed directly on your site. Read more about Active Scanning Mode.
Let’s visualize first how SiteLint works
Now let’s see how to set up and start using SiteLint
Sign Up. An initial API token will be created for you.Step 1 –
Create an account on our Platform.
Put the code snippet on your siteStep 2 –
After signing up, you’ll land on Welcome Page with the initially created API token. Copy the code snippet and put it on your site.
Get results and analyse themStep 3 –
To verify that SiteLint Audits works just go to any page where the code was injected and go to the SiteLint Platform to analyze the results.
Platform Frequently Asked Questions
You may want to read our Platform Frequently Asked Questions.
SiteLint vs Lighthouse
You may want to read about SiteLint vs Lighthouse comparison.