Writing

Case study

protectorguardrail.com: a Lighthouse 12 performance case study

A multilingual industrial-products site I built and tuned end to end, measured with Lighthouse 12 on the mobile preset: 1.7 s LCP, 0.052 CLS, 0 ms TBT.

This article is currently available in English only.

Updated 14 September 2026

protectorguardrail.com is a multilingual industrial-products site. I built and tuned it end to end, including the markup, styling and delivery.

What the numbers are

Measured with Lighthouse 12 on the mobile preset, with moto-g-class throttling, on 5 August 2026:

  • Performance 99
  • Accessibility 100
  • Best practices 100
  • SEO 100

The headline lab metrics from the same run: LCP 1.7 s, CLS 0.052, TBT 0 ms.

The 100 scores for accessibility, best practices and SEO came from the same mobile-throttled run. The 0 ms total blocking time means Lighthouse recorded no load-time tasks above its blocking threshold in that run. It does not predict the interaction experience of every real visitor.

How it was measured

Lighthouse 12, mobile preset, on 5 August 2026. That is a lab run: a simulated mid-range Android on a throttled connection, not a summary of what every real visitor experienced. Lab numbers are reproducible, which is exactly what makes them useful as a claim — you can re-run them.

The PageSpeed Insights report can be run again here:

PageSpeed Insights run for protectorguardrail.com

Scores move as browsers, Lighthouse versions and the site itself change, so a run you do today may not match the figures above to the decimal. This report is a new measurement rather than a permanent copy of the run dated above. The figures above are a Lighthouse audit result; they do not promise search rankings, accessibility conformance in every context, or the experience of every visitor. For what Lighthouse measures, see Google’s Lighthouse performance documentation.

Alfred Westerveld