Google has updated Lighthouse, the testing engine used in PageSpeed Insights, changing how page loads are simulated in lab performance tests. As a result, some websites may see different PageSpeed Insights scores even if no changes were made to the site itself.
For European businesses, this matters because PageSpeed Insights is widely used by internal teams, agencies and developers to assess website performance, support SEO work and prioritise technical improvements. A score change caused by the testing model is not the same as a real-world improvement in user experience.
What happened
According to the report, the Lighthouse update changes how PageSpeed Insights simulates page loading during lab testing. This can increase or otherwise alter reported performance scores on pages that have not been updated.
PageSpeed Insights combines different types of data. Lab data is based on a controlled simulation, while field data reflects real user experience data where available. The reported change concerns the lab-testing side of the tool.
This means before-and-after comparisons may no longer be directly comparable if one test used the previous Lighthouse version and a later test used the updated one.
Why it matters for European businesses
Many SMEs, e-commerce teams and marketing departments use PageSpeed Insights as a simple benchmark for site quality, SEO readiness and conversion optimisation. If scores change because the test methodology changed, businesses could misread the cause of the result.
That has several practical implications:
- SEO reporting may need context. Agencies and in-house teams may need to explain that a score increase does not automatically mean a technical fix delivered the improvement.
- Website KPIs may appear to improve suddenly. Performance dashboards or monthly reports may show a jump that reflects the tool update rather than a website release.
- Development priorities could be affected. Teams that rely heavily on lab scores may need to re-check whether optimisation work is still justified based on user impact, not only on a synthetic score.
- Client communication becomes more important. Businesses working with external SEO or development partners should ensure score changes are interpreted correctly.
For companies operating across multiple markets, especially those with lead-generation or e-commerce websites, performance metrics influence decisions around SEO, landing page design and mobile usability. Misunderstanding the source of score changes can lead to poor prioritisation.
Who may be affected
- SMEs using PageSpeed Insights as a simple website health check
- E-commerce businesses monitoring speed as part of conversion and search performance efforts
- Marketing teams reporting on SEO and website performance to management
- Developers and IT teams using Lighthouse outputs to prioritise optimisation work
- Digital agencies managing performance reporting for clients
What companies should consider
- Review how performance is measured. Separate tool-driven lab scores from real-world indicators such as field data, conversion rates and user engagement.
- Add context to reporting. If PageSpeed Insights scores changed recently, note that a Lighthouse update may be part of the explanation.
- Avoid overreacting to a single score change. Reassess trends across multiple tests and metrics before changing roadmap priorities.
- Focus on business outcomes. Use performance testing to support user experience, search visibility and conversion goals rather than treating the headline score as the only KPI.
- Coordinate across teams. Marketing, SEO and development teams should align on which performance measures are used for decision-making and client reporting.
The update does not necessarily indicate that websites have become faster for real users. Instead, it changes how one of the most widely used testing tools evaluates loading behaviour in a simulated environment. For businesses, the key takeaway is to interpret new scores carefully and compare them with broader website performance evidence.