In the Toprova score, 20 % comes from automated measurements, and speed makes up a third of that. Toprova runs Lighthouse with the desktop profile, three times, and keeps the median. So it is worth knowing what the tool looks at, and where the easy points are.

Five metrics, five weights

In Lighthouse 12, the performance score out of 100 combines five weighted metrics:

  • First Contentful Paint (FCP), 10 %: the moment the first text or image appears.
  • Speed Index, 10 %: how quickly the page visibly fills in while it loads.
  • Largest Contentful Paint (LCP), 25 %: the moment the largest visible element is displayed, often an image or a large heading.
  • Total Blocking Time (TBT), 30 %: the total time the main thread is blocked between FCP and the moment the page becomes interactive. For every task longer than 50 ms, anything beyond 50 ms is counted.
  • Cumulative Layout Shift (CLS), 25 %: how much the layout moves around unexpectedly.

Each metric is converted into a score along a curve, then weighted. From 90 upwards the score is green, from 50 to 89 orange, below that red. TBT and LCP together account for more than half: that is where you gain the most.

Images: the right format, the right size

  • Serve images as AVIF or WebP, with a JPEG fallback if needed.
  • Use srcset and sizes so the browser loads the right size, not a 4000-pixel photo for a 600-pixel block.
  • Give every image a width and a height, or an aspect-ratio in CSS. The browser reserves the space and CLS stays low.
  • Put loading="lazy" on images further down the page, never on the main image.
  • For the image that is your LCP, add fetchpriority="high" or a preload.

Fonts: fewer, and sooner

  • Use the WOFF2 format and limit the number of weights and styles.
  • Cut the files down to the characters you actually need (subsetting).
  • Preload the body text font and use font-display: swap so text appears straight away.
  • Tune the fallback font with size-adjust so the font swap does not shift the page.

JavaScript: take the load off the main thread

TBT almost always comes from JavaScript. While a long task is running, the page does not respond.

  • Remove unused code and split your bundle by page.
  • Load non-essential scripts with defer, or only after an interaction.
  • Trim third-party scripts: widgets, trackers, chat windows. Each one has a cost.
  • Break long tasks into shorter chunks so the browser gets control back in between.

Server and caching

  • Turn on Brotli or gzip compression for HTML, CSS and JavaScript.
  • Give versioned files a long Cache-Control with immutable, and serve them from a CDN.
  • Keep an eye on server response time: a slow first byte delays every other metric.
  • Reserve space for elements injected later, such as banners or embeds, to avoid layout shifts.
Before you submit your site, run Lighthouse yourself in desktop mode, several times. You will see roughly what Toprova will see.