Platform

Table of contents

1. How does Sitelint Platform work?
2. How does SiteLint Platform’s client-side auditing technology differ from traditional server-side crawling methods?
3. How does SiteLint Platform’s client-side auditing technology precisely analyze website content without slowing down page loading times?
4. How long does it take for SiteLint to run its code snippet on a website?
5. Can I schedule regular audits with SiteLint or do they only occur when a user visits the website?
6. How often do SiteLint’s audits typically occur during real-time visits?
7. Can screen reader users use SiteLint Platform?
8. I’ve created an API token. Can I use that on multiple sites?
9. How scores are calculated
10. Why may an element not be located on the live page, and how can I resolve this issue?
11. Have a more questions?

• #How does Sitelint Platform work?

  SiteLint Audits Platform works by relying on a small bit of JavaScript code that is placed on your website. This code is activated when visitors arrive on your site. It allows running all audits on your site directly on the client side.

• #How does SiteLint Platform’s client-side auditing technology differ from traditional server-side crawling methods?

  SiteLint Platform’s client-side auditing technology differs from traditional server-side crawling methods in that it runs audits directly on the client side, providing more precise results as it analyzes the content in the user’s environment. This approach allows for testing across all combinations of devices, OS, and browsers, whereas server-side crawling methods may not be able to replicate the same user experience. Additionally, SiteLint Audits has no impact on site performance as it runs during browser idle periods and only when content changes.

• #How does SiteLint Platform’s client-side auditing technology precisely analyze website content without slowing down page loading times?

  SiteLint Platform’s client-side auditing technology precisely analyzes website content without slowing down page loading times by running audits directly on the client side during browser idle periods, such as 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 should not impacted. Also, audits aren’t running every time the user lands on your site. It runs only when the content changes.

  By default, Audits are loading with 3.5 seconds delay so that it gives an opportunity to first load your content in high priority.

• #How long does it take for SiteLint to run its code snippet on a website?

  SiteLint runs its code snippet on a website whenever a user lands on the page. This means the audit process is triggered in real-time, as soon as a user visits the site. The duration of the audit depends on the complexity of the webpage and the user’s network speed. It is usually few hundred milliseconds.

• #Can I schedule regular audits with SiteLint or do they only occur when a user visits the website?

  SiteLint audits are performed whenever a user lands on the page. The term scheduling occurs when the audit is performed by crawling. SiteLint does not use crawling and therefore there is no need to schedule scans. All audits are run on the client side and only when a user visits your website.

• #How often do SiteLint’s audits typically occur during real-time visits?

  SiteLint monitors and audits websites in real-time, without specifying any particular interval between audits. SiteLint operates 24 hours a day, 7 days a week, 365 days a year. This means that an audit can occur at any time a user visits the website.

  However, the exact frequency of audits can vary based on the number of users visiting the site and the specific circumstances of each visit. For example, if a single user visits multiple pages on a website, SiteLint will run its audit after each page load. It is worth mentioning that if the same user visits the web page again and the web page has not changed since the previous visit, the audit is not performed.

• #Can screen reader users use SiteLint Platform?

  Yes, SiteLint Audits Platform is designed to be accessible to screen reader users. We strive to ensure that our technology is inclusive and can be used by everyone, regardless of their abilities or assistive technologies. If you encounter any issues or have feedback, please contact us.

• #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 may an element not be located on the live page, and how can I resolve this issue?

  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=params were redirected to page example.com/pageB without sitelint=params URL query param.

  If the issue persists, you can contact us for further assistance.