Table of contents
- How does Sitelint Platform work?
- 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?
- I’ve created an API token. Can I use that on multiple sites?
- How scores are calculated
- Why element can’t be located on the page?
- Have a more questions?
How does Sitelint Platform work?
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 analyse 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 Devices/OS/Browser.
Does running SiteLint Audits impacts the site performance?
SiteLint Audits Platform has no impact on the site performance. When we think about the 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
freetime, 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 the care of screen reader users. Contact us if you find any issues or want to give us feedback.
I’ve created an API token. Can I use that on multiple sites?
Yes. Once the API token is created you can reuse it on any site. What’s important here is parameter Unique URLs and Sessions.
The total amount of reports can’t exceed limits defined for Unique URLs and Sessions. A session is a single report sent from the client. However, the reports are sent only when there are changes on the page. If the page doesn’t change then the report is not being sent. The sessions counter is connected to the Workspace so you can have any amount of sites, but total sessions are limited by your subscription plan.
How scores are calculated
The metrics scores and the performance score are defined according to these ranges:
- 0 to 49 – poor, marked with the red color.
- 50 to 89 – needs Improvement, marked with the orange color.
- 90 to 100 – good, marked with the green color.
The scoring algorithm is based on the following calculation:
Errors = issues error counter + (issues warning counter / 10); Total = issues passed counter + Errors; Error Ratio = Errors / Total;
Why element can’t be located on the page?
The element may not be located on the live page due to the following potential issues:
- The element doesn’t exist anymore.
- The element is on the page that comes from redirection and URL parameters was not preserved. In other words, URL
example.com/pageA?sitelint=paramswere redirected to page
sitelint=paramsURL query param.
Have a more questions?
Contact us to get more details.