How to guarantee a PageSpeed score of 90+ for your clients The complete technical guide

A PageSpeed score of 45 on mobile. That is the reality for the majority of WordPress sites delivered by agencies that do not make development their core business. For a client whose traffic is 60% from Google, that number represents lost revenue every single day.

Guaranteeing a PageSpeed 90+ score for your clients is not a technical luxury. It is a baseline condition for SEO and conversion rates to work. This guide explains how to achieve it systematically, regardless of the stack.

Why PageSpeed is non-negotiable in 2026

Google integrated Core Web Vitals into its ranking algorithm in May 2021. Five years later, the impact has amplified with each update. In 2026, field data shows a direct correlation between load speed and positioning on competitive queries.

The numbers speak for themselves:

• A 1-second increase in load time reduces conversions by 7% (Google/Deloitte, 2023)
• 53% of mobile visitors abandon a site that takes more than 3 seconds to load (Google)
• Sites with "Good" ratings on all Core Web Vitals have a 24% higher chance of not recording an abandonment (Google Search Console, aggregated data)

For clients in Belgium, Switzerland, and Luxembourg, mobile connections remain the dominant channel for local queries. A poor mobile score means a poor score overall.

Understanding PageSpeed scores and Core Web Vitals

Before optimizing, you need to understand what you are measuring. PageSpeed Insights combines two very different data sources.

The Lighthouse score (lab data)

This is the 0-to-100 score you see on PageSpeed Insights. It is calculated by Lighthouse under simulated conditions: throttled 4G connection, slowed CPU. It is useful for diagnosis, but it is not what Google uses for ranking.

Core Web Vitals (field data)

These are the metrics Google actually collects via Chrome. Three main indicators:

LCP is the metric with the biggest SEO impact. If your largest visible element (hero image, H1 title, text block) takes more than 2.5 seconds to appear, you are in the red zone.

The main causes of poor scores

The majority of performance problems come from five sources. Identifying them quickly allows you to prioritize optimizations.

1. Unoptimized images

This is the number one cause of poor LCP scores. A hero image in PNG format at 2MB without compression, without WebP format, and without lazy loading can alone drop a site from 90 to 50.

Classic mistakes:

• Images uploaded directly from a camera without resizing
• PNG or JPEG formats when WebP or AVIF would be 40 to 60% lighter
• Missing loading="lazy" attribute on images below the fold
• Missing explicit width and height attributes, which causes CLS

2. Render-blocking JavaScript

Every external script loaded synchronously in the <head> blocks page rendering until it is downloaded and executed. Usual suspects: poorly configured Google Tag Manager, marketing scripts loaded too early, outdated jQuery.

3. Non-critical CSS loaded all at once

A 500KB CSS file loaded in full blocks rendering even if most of the CSS covers off-screen components. The Critical CSS inline technique (Above the Fold CSS) solves this problem.

4. Slow hosting

TTFB (Time to First Byte) measures server response time. Above 800ms, it is impossible to achieve a good LCP. Cheap shared hosting, an unindexed database, or the absence of server-side caching alone can produce TTFBs of 2 to 4 seconds.

5. Unoptimized web fonts

Loading 4 or 5 Google Fonts variants blocks text rendering. The CSS property font-display: swap and local font hosting reduce the impact by 60 to 80%.

Le problème

A standard WordPress site delivered with a premium theme, a page builder (Elementor or Divi), and 15 plugins typically scores between 30 and 55 on mobile. The page builder scripts alone often represent 1 to 2MB of JavaScript.

Le coût réel

La solution

Replacing the page builder with custom development or a lightweight theme like GeneratePress reduces JS by 70 to 90%. Combined with quality hosting and a CDN, the score climbs back to 85-92 without further intervention.

Signal d'alerte :

The tech stack that guarantees 90+

Choosing the right stack from the start is the most cost-effective performance decision. Here are the proven combinations in descending order of performance.

Stack 1: Next.js static export (recommended)

This is the approach we use at Kayden Digital. Next.js with output: 'export' generates static HTML files served from a CDN. Typical results: 95-100 on desktop, 88-96 on mobile.

Technical advantages:

• Server-side rendering (SSG): zero server computation time at request
• Image Optimization with next/image: automatic conversion to WebP/AVIF, native lazy loading, and explicit dimensions
• Automatic code splitting: each page only loads the JavaScript it needs
• Font Optimization with next/font: locally hosted fonts, automatic font-display: swap

Stack 2: Astro

Astro is designed for content-heavy static or semi-dynamic sites. Its "zero JavaScript by default" architecture makes it an excellent choice for brochure sites. Scores of 98-100 are common with Astro.

Stack 3: WordPress with optimizations

For clients who require WordPress, here is the minimum configuration to achieve 85-92:

• Managed hosting: Kinsta, WP Engine, or Cloudways (minimum 10-15€/month)
• Lightweight theme: GeneratePress, Blocksy, or custom development (no page builder)
• CDN: Cloudflare free tier or Bunny.net
• Performance plugin: WP Rocket (59€/year) or Perfmatters
• Image optimization: Imagify or ShortPixel
• Server-side caching enabled at the hosting level

Step-by-step optimization checklist

This checklist covers optimizations in decreasing order of impact. Start at the top.

What this means for your clients

A PageSpeed 90+ score is not just a technical figure to include in your commercial proposal. It has concrete, measurable effects on the metrics that matter to your clients.

SEO impact

Google has used Core Web Vitals as a ranking factor since 2021. Concretely, a site that moves from "Poor" to "Good" on its Core Web Vitals gets a positive signal in the algorithm. On local queries in French-speaking Belgium or Switzerland, where technical competition is often low, this advantage can represent several ranking positions.

A good score also facilitates crawling by Google's bots: pages load faster for Googlebot, which improves crawl budget on large sites.

Conversion impact

The data is clear. For an e-commerce site, every second saved in load time represents on average 2 to 3% additional conversions. For a brochure site or landing page, the correlation is similar: a load time under 2 seconds reduces bounce rate by 35% compared to a 5-second load.

For clients investing in Google Ads or Meta campaigns, a fast landing page directly improves Quality Score and reduces cost per click.

Client retention and agency reputation

Delivering a high-performance site creates a lasting competitive advantage for your agency. When your client has their site audited by an SEO consultant 6 months after delivery, and the PageSpeed score is still at 92, you benefit from that. It is a differentiating criterion that few marketing or communication agencies can put forward.

Case study: from 45 to 94 in three weeks

Here is the concrete case of a Kayden Digital client, an SEO agency based in the Walloon region that entrusted us with the technical redesign of a client site.

The context

The agency's client is an accounting firm with a 5-year-old WordPress site. Initial PageSpeed score: 45 on mobile, 62 on desktop. Organic traffic had been stagnant for 18 months despite a regular content strategy.

The initial diagnosis with WebPageTest and PageSpeed Insights revealed:

• TTFB of 1.8 seconds (basic OVH shared hosting)
• LCP of 6.2 seconds (1.4MB PNG hero image)
• CLS of 0.28 (cookie banner appearing without reserved space)
• 14 render-blocking JavaScript requests
• Google Fonts loaded from Google's CDN

The interventions

Week 1: infrastructure and images

• Migration to Kinsta hosting (server cache, PHP 8.2, integrated CDN). TTFB reduced to 180ms.
• Replaced Avada theme with GeneratePress. CSS weight reduced from 850KB to 45KB.
• Image optimization with ShortPixel: WebP conversion, lossless compression. Total homepage weight reduced from 3.2MB to 640KB.
• CLS fix: fixed-size reserved space for the cookie banner.

Week 2: JavaScript and fonts

• Replaced Avada shortcodes with native HTML/CSS. 11 scripts removed.
• GTM loaded after 3 seconds of inactivity.
• Fonts hosted locally with font-display: swap.
• Hero image preloaded with <link rel="preload">.

Week 3: critical CSS and testing

• Above the Fold critical CSS extracted and inlined in the <head>.
• Tests on 5 real devices (iPhone SE, mid-range Android, tablet).
• Final adjustments on lazy loading and loading priorities.

The results

After three weeks of intervention:

Six weeks after going live, the site's organic traffic had increased by 31% on target local queries. The bounce rate had dropped from 68% to 44%.

Frequently asked questions

Is PageSpeed really a Google ranking factor?

What is the difference between PageSpeed Insights and Lighthouse?

Is a perfect score of 100 necessary?

Do animations and videos always hurt scores?

My client wants WordPress. Can we still hit 90+?

How do you maintain a good score over time?

Conclusion

Guaranteeing a PageSpeed 90+ score is not an option reserved for large, high-budget projects. It is a discipline that applies to every project, with the right stack choices and a systematic checklist.

For SEO and marketing agencies, it is also a powerful commercial argument: delivering measurable performance differentiates your offer and strengthens client trust over time. If you are looking for a development partner that builds these performance requirements in from day one, learn about how our white-label service works or read our checklist of 15 criteria for choosing a development partner.

To go further on the technical foundations of SEO, read our complete article on the technical SEO foundations you are neglecting and our technical SEO checklist for developers.