When we show a Lighthouse report to a Geneva-based business owner for the first time, the reaction is usually the same: "What does 42 mean?" The short answer: it means your site is losing Google rankings, visitors and customers, every single day.
Lighthouse is Google's official audit tool. A score of 95 or more on Performance is not an honorary badge reserved for geeks; it is the threshold at which a website stops actively undermining its own visibility.
This article explains what Lighthouse is, how to read its score, why 95+ is the minimum standard for a professional website in 2025, and, in concrete terms, what drags scores down (WordPress, plugins, images, unnecessary JavaScript) versus what pushes them up (custom-built code, clean architecture).
What Lighthouse is, and why Google created it
The universal audit tool of the modern web
Lighthouse is an open-source tool developed by Google and built directly into Chrome DevTools since 2017. It analyses any public URL across five areas:
Each area is scored from 0 to 100. The Performance score is the one that directly affects your Google rankings, and it is the one this article is about.
How Lighthouse calculates its score
The Lighthouse Performance score is a weighted combination of six metrics:
The weighting changed in 2024 to give more weight to INP (which replaced FID). A site that excelled in 2022 may have seen its score drop by 15 to 25 points if it has not been updated since.
Lighthouse vs field data (CrUX)
A crucial and often misunderstood point: Lighthouse measures simulated conditions (slow 4G throttling, 4× CPU slowdown). That is not what your real users experience.
Field data (the Chrome User Experience Report, CrUX) measures real Chrome users. Google Search Console displays it in the "Core Web Vitals" section. A site can score 88 on Lighthouse and still be rated "Good" by field data, or the other way round.
The practical rule: a Lighthouse score of 95+ guarantees that your field data will also sit in the "Good" zone. Below that, things get blurry: some users get a decent experience, others less so, and Google takes that into account.
Why 95+ is the minimum premium standard in 2025
Changing expectations, and a changing algorithm
In 2018, a score of 70 was respectable. In 2021, 80 was the usual target. In 2025, 95+ has become the credibility threshold for any professional website. Here is why:
Google Page Experience: since its full rollout in 2022, page experience has been a confirmed ranking factor. Sites that do not reach the "Good" thresholds on Core Web Vitals are mechanically disadvantaged, regardless of the quality of their content.
The cumulative effect: Google does not apply a one-off penalty. It continuously favours fast sites. Over 12 months, a site scoring 95+ builds a considerable lead over a site scoring 60 in terms of impressions, clicks and domain authority.
User expectations have shifted: according to Google (2023 data), 53% of mobile users leave a site that takes more than 3 seconds to load. In 2025, that threshold is moving towards 2 seconds. Swiss users, accustomed to fast connections, are particularly intolerant of slow sites.
What studies say about business impact
Portent (2023): sites with a Lighthouse Performance score above 90 have an average conversion rate 2.4× higher than sites below 50.
Ahrefs (2024): pages ranking in positions 1 to 3 on Google have a median Lighthouse score of 91, compared with 64 for pages in positions 8 to 10.
WebFX (2024): a 10-point improvement in Lighthouse Performance is correlated with an 8 to 12% increase in organic traffic over a 6-month period.
Kinsta (2024): sites hosted with active optimisation (caching, CDN, modern server) score an average of 88 on Lighthouse Performance. Sites without optimisation: 51. Hosting alone accounts for 20 to 30 points.
Why the threshold is 95 (not 100)
A score of 100 is possible but rare in real-world production (with analytics scripts, third-party fonts and chat widgets). It is achieved on ultra-minimal static pages or under perfect lab conditions.
The 95+ threshold is realistic, sustainable and sufficient to secure every documented SEO benefit. Below 90, you lose guarantees. Between 90 and 94, you are in the uncertainty zone. At 95+, you are in the zone of excellence.
What drags scores down: the usual culprits
The WordPress + plugins problem: structural technical debt
WordPress powers 43% of the world's websites (W3Techs, January 2025). That is a real strength for making website creation accessible, and a structural handicap for performance.
The problem with premium themes: Divi, Elementor, Avada, WPBakery. These page builders load between 800 KB and 3 MB of CSS and JavaScript, only a tiny fraction of which is used on any given page. The browser has to parse, compile and evaluate all of that code before it can display anything.
Here is what a typical Lighthouse audit reveals on a WordPress site built with Elementor:
Resulting score: 35 to 55/100. Not because WordPress is fundamentally broken, but because the stacking of layers (theme + page builder + plugins) creates a weight that nothing can genuinely lighten without rewriting the site.
Security, SEO and analytics plugins: the silent overload
Every WordPress plugin adds code. Not just server-side PHP, but often client-side JavaScript and CSS that runs in every visitor's browser.
A "standard" WordPress site for a Geneva-based SME has an average of 18 active plugins (source: audits carried out by INFUSE). Among them:
- 1 SEO plugin (Yoast, Rank Math): adds JS for real-time validation
- 1 security plugin (Wordfence): adds client-side detection JS
- 1 analytics plugin (MonsterInsights): loads a Google Analytics script plus a wrapper
- 1 caching plugin (WP Rocket, W3 Total Cache): helps, but does not offset the others
- 1 form plugin (Contact Form 7, Gravity Forms): loads its JS on every page
- 1 GDPR/cookie plugin: heavy JavaScript overlay, often render-blocking
None of these scripts is "bad" on its own. Together, they generate an initial load that can exceed 4 MB of resources and 80 HTTP requests. No caching plugin solves this problem; at best it mitigates it marginally.
Unoptimised images: the number one LCP culprit
According to the HTTP Archive report (2024), images account on average for 51% of a web page's total weight. On WordPress sites, this figure often rises to 65-70% because:
- Images are uploaded as full-resolution JPEG or PNG files (3 to 8 MB)
- They are served without appropriate resizing (a phone receives the same image as a 4K screen)
- They are not converted to WebP or AVIF (20 to 50% lighter than JPEG)
- Lazy loading is not always configured correctly
- The hero image (the one that determines LCP) is not preloaded
A single change (switching the hero image from a 2 MB JPEG to a 300 KB AVIF) can gain 15 to 20 points on LCP and 8 to 12 points on the Lighthouse score.
Third-party JavaScript: slow poisoning
Third-party scripts are the scourge of performance in 2025. A chat widget, a Facebook pixel, an A/B testing script, a Google Maps embed in an iframe: each one adds extra requests to external servers whose response times are entirely outside your control.
According to Calibre (2024), third-party scripts are responsible on average for 57% of Long Tasks on the browser's main thread. These are the tasks that degrade INP.
What pushes scores up: clean architecture
Next.js 16: a platform built for performance
Next.js is not a magic bullet. But its default architecture structurally solves the problems that cause Lighthouse scores to plummet:
Smart hybrid rendering: pages can be rendered entirely as static HTML (SSG), on the server for each request (SSR), or as a combination of both. In every case, the browser receives HTML that is ready to display, not an empty document waiting for JavaScript to run.
Server Components (React 19): purely presentational components (text blocks, static images, navigation) generate no client-side JavaScript at all. This drastically reduces bundle weight and eliminates the hydration tasks that affect INP.
Turbopack: the native bundler in Next.js 16 produces optimised bundles with automatic code splitting, so each page loads only the JavaScript it needs.
next/font: Google Fonts are downloaded at build time and hosted on your own domain. Zero third-party requests on load, zero font-related CLS, zero additional network delay.
Tailwind v4: only the CSS you actually use
Tailwind CSS v4 generates a CSS file containing only the classes present in the source code. On a typical INFUSE project, production CSS weighs between 8 and 25 KB (gzipped), compared with 200 KB to 1.5 MB for a Bootstrap theme or a WordPress theme.
This is far from trivial: a lighter CSS file means less parsing time, fewer reflows and a faster FCP. Combined with @layer to prioritise critical styles, Tailwind v4 completely eliminates the "Reduce unused CSS" audit category in Lighthouse.
GSAP: animations with no performance cost
GSAP (GreenSock Animation Platform) is the standard animation library on INFUSE projects. Its reputation for being lightweight and fast is well deserved:
- GSAP uses
requestAnimationFrameto synchronise animations with the browser's rendering cycle: zero layout thrashing. - GSAP animations target
transformandopacityfirst, GPU-accelerated properties that do not trigger reflow and do not affect CLS. - GSAP is imported with tree-shaking: only the modules in use (ScrollTrigger, SplitText, etc.) are included in the bundle.
The result: smooth 60 fps animations with no impact on LCP, INP or CLS.
Hosting and infrastructure: the often overlooked factor
The best code served by a slow host is still slow. A TTFB (Time to First Byte) above 600 ms already eats up 25% of the LCP budget before the browser has displayed a single pixel.
INFUSE projects are deployed on Vercel (global Edge Network, CDN with 30+ PoPs including one in Zurich), guaranteeing a TTFB below 150 ms from Switzerland. Static assets are served from the nearest node: images, fonts and CSS files arrive in under 100 ms.
Practical audit: how to read your Lighthouse score today
In 5 minutes, with nothing to install
- Open Chrome > F12 (or Cmd+Option+I on Mac) > "Lighthouse" tab
- Tick "Performance", "SEO", "Best practices"
- Select "Mobile" (mobile is Google's reference environment)
- Click "Analyse page load"
Or go straight to pagespeed.web.dev: enter your URL and get results in 30 seconds.
How to interpret the results
The most revealing diagnostics
Lighthouse does not just give you a score, it gives you an action plan. The three most impactful diagnostics to look for:
"Eliminate render-blocking resources": scripts and CSS loaded in blocking mode before the page renders. This signals a poor loading order, often costing 15 to 25 points.
"Reduce unused JavaScript": the ratio of JS loaded versus JS executed. Beyond 30% unused, something is wrong with the architecture. On WordPress themes, this ratio often exceeds 70%.
"Serve images in next-gen formats": if your images are JPEG or PNG, switching to WebP or AVIF cuts 20 to 50% of their weight at no cost. Next.js does this automatically.
Lighthouse score and SEO: the documented direct link
Official confirmation from Google
Google announced in 2021 (and confirmed in 2023-2024) that page experience (including the Core Web Vitals measured by Lighthouse) is a ranking factor. Unlike other signals, its weight is transparent: Google states clearly that pages offering a good experience are more likely to rank well.
What is less documented but observed empirically: the effect compounds over time. A site that maintains excellent metrics over 12 months sees its domain authority grow faster, which amplifies the impact of every new piece of content it publishes.
The effect on Google Ads Quality Score
If you advertise on Google, the Quality Score of your landing pages is directly influenced by page experience. A Lighthouse Performance score above 90 mechanically improves your Quality Score, and lowers your cost per click.
WordStream documented (2024) that a 1-point improvement in Quality Score reduces CPC by 16%. On a monthly advertising budget of CHF 2,000, moving from a Quality Score of 5 to 7 can save CHF 600/month. Over 12 months, a custom-built site partly pays for itself through the reduction in advertising costs alone.
The effect on crawl budget
Google's bots visit your site constantly to index your new pages. A slow site consumes more server resources on every crawler visit, which reduces the number of pages indexed per session.
A high Lighthouse score correlates with a low TTFB and lightweight pages. Fast sites are crawled more efficiently, which speeds up the indexing of new content. For sites with more than 50 pages, this is a genuine differentiator.
Keeping a 95+ score over time: best practices
Continuous monitoring
A Lighthouse score is not permanent. Add a new script, a third-party widget or an oversized image, and the metrics drop.
Good habits:
- Audit on every deployment: integrate Lighthouse into your CI/CD pipeline with Lighthouse CI (open source). An alert fires automatically if a metric drops.
- Monitor third-party scripts: every new script added (analytics, chat, A/B testing) must be assessed for its impact. Systematic lazy loading, deferred loading after the first render.
- Audit images on upload: set an internal rule: no image above 200 KB before optimisation, WebP or AVIF format only.
Additions that cost nothing
Some practices improve the experience without affecting the metrics:
- Preconnect to critical third-party domains (fonts, analytics) via
<link rel="preconnect"> - Prefetch pages that are likely to be visited next (Next.js does this automatically via
<Link>) - Service Worker to cache resources between sessions (can be configured with Next.js in PWA mode)
Conclusion: the Lighthouse score as a quality standard
A Lighthouse score of 95+ is not a technical obsession. It is the numerical expression of a business reality: your site is fast, stable and responsive. Google knows it, your users feel it, and conversion figures confirm it.
The difference between a site scoring 45 and one scoring 95 is the difference between a site that survives and a site that performs. In Geneva and across French-speaking Switzerland, where companies are only beginning to grasp what is at stake with organic search, this gap is a concrete opportunity to get ahead of competitors who have not yet made the move.
At INFUSE, a Lighthouse score of 95+ is not a target, it is the baseline. Every site we deliver passes the audit before going live. If it does not reach 95+, it does not ship.
Want to see where your site stands? Request a free audit. Within 48 hours, you receive a full report with your current metrics, the issues identified and a costed action plan.