Table of contents
- How does your Platform works?
- What is the difference between SiteLint Platform and other solutions?
- Does running SiteLint Audits impacts the site performance?
- Can screen reader users use SiteLint Platform?
- Have a more questions?
How does your Platform works?
What is the difference between SiteLint Platform and other solutions?
The common model today’s day is to run the crawler on the server-side, crawl the site and then analyze the content. SiteLint Audits works in a next-generation model – all audits are running on your site when visitors arrive on your site. This gives more precise results because audits are running on the user environment. What’s working on one configuration of Device/OS/Browser doesn’t have to work on the other configuration. Hence running audits on the client-side brings better results of testing across all combinations of Device/OS/Browser.
Does running SiteLint Audits impacts the site performance?
SiteLint Audits Platform have no impact on the site performance. When we think about performance it relates to loading and running.
By default, Audits is loading with 3.5 seconds delay so that it gives an opportunity to first load your content in high priority.
All audits are running during a browser’s idle periods (
requestIdleCallback), either at the end of a frame or when the user is inactive. Because the audits are performed in the browser’s “free” time, the performance of the site is not impacted. Also, audits aren’t running every time the user lands on your site. It runs only when the content changes.
Can screen reader users use SiteLint Platform?
Yes. SiteLint Audits Platform itself is being made with care of screen reader users. Contact us if you find any issues or want to give us feedback.
Have a more questions?
Contact us to get more details.