Scoring Rules

Lighthouse Performance Score

Runs a google lighthouse test on the site. The resulting score of the category Performance is also used as your commerce-score for this test. (learn more)

First Contentful Paint

FCP measures how long it takes the browser to render the first piece of DOM content after a user navigates to your page. (learn more)

up to 1.5s: +50above 4s: -25

Number of Requests

Measures the number of requests the browser has to make to finish rendering the page. (learn more)

up to 150: +25above 250: -25

Number of Javascripts

Measures the number of Javascript files loaded on the page. (learn more)

up to 10: +50above 40: -25

Total Blocking Time

TBT Measures the total amount of time that a page is blocked from responding to user input. (learn more)

up to 0.07: +50above 0.2: -25

Third Party Transfer Size

Measures the transfer size of resources loaded from 3rd party domains. (learn more)

up to 400KB: +50above 1500: -25

Lighthouse Best Practice Score

Runs a google lighthouse test on the site. The resulting score of the category Best Practices is also used as your commerce-score for this test. (learn more)

Lazy Load Images

Checks if offscreen images are beeing deferred via lazy loading. (learn more)

if Yes: +25

Uses HTTP/2?

Checks if the site is using the HTTP/2 protocol. (learn more)

if Yes: +25

Redirects HTTP to HTTPS?

Tests if the page does a redirect from HTTP to HTTPS. (learn more)

if No: -25

Uses unsupported PHP Version?

Checks if the site is exposing the used PHP version and also if this version is still supported and gets security updates. Currently PHP versions older than 7.2 match as unsupported. (learn more)

if Yes: -25

Lighthouse Accessibility Score

Runs a google lighthouse test on the site. The resulting score of the category Accessibility is also used as your commerce-score for this test.(learn more)

First Input Delay

Measures interactivity. To provide a good user experience, pages should have a FID of less than 100 milliseconds. (learn more)

Largest Contentful Paint

Measures loading performance. To provide a good user experience, LCP should occur within 2.5 seconds of when the page first starts loading. (learn more)

Time To First Byte

TTFB Measures the repsonse time of the server until the browser receives the HTML. (learn more)

up to 0.5s: +100up to 0.75s: +50above 1s: -50above 1.25: -100

Total Byte Weight

Measures the total transfer size of all elements on the page. (learn more)

up to 1800KB: +50above 4000KB: -25

Number of Fonts

Measures the number of Fonts loaded on the page. (learn more)

up to 3: +50above 6: -25

Number of Stylesheets

Measures the number of CSS files loaded on the page. (learn more)

up to 3: +50above 10: -25

Third Party Time

TPT Measures the runtime of javascript and rendering of resources loaded from 3rd party domains. (learn more)

up to 0.2s: +50above 0.5s: -25

Vulnerable Javascript Libraries

Checks if the site is using Javascirpt Libraries with known security vulnerabilities. (learn more)

if Yes: -50

Uses CDN?

Checks if the site is using a CDN for product images. (learn more)

if Yes: +50

Protect Admin URL?

Tests if commonly known Admin- or Backoffice-URLS can be accessed without protection.

if No: -25

Is on HTTPS?

Tests if all elements on the page are loaded via SSL encryption. (learn more)

if No: -25

Exposes Server Software Version?

Checks if version numbers of used server software are exposed for example via "Server:", "Varnish:" or "X-POWERED-BY" Headers. This could help an attacker target vulnerabilities of specific versions. (learn more)

if Yes: -25

Lighthouse SEO Score

Runs a google lighthouse test on the site. The resulting score of the category SEO is also used as your commerce-score for this test. (learn more)

First Contentful Paint

FCP measures how long it takes the browser to render the first piece of DOM content after a user navigates to your page, pages should have a FCP of less than 2 seconds. (learn more)

Interaction to Next Paint

Measures interactivity. To provide a good user experience, pages should have a INP of less than 200 milliseconds. (learn more)

Cumulative Layout Shift

Measures visual stability. To provide a good user experience, pages should maintain a CLS of less than 0.1. (learn more)