How We Achieved Near-Perfect Google PageSpeed Insights Scores – And Why It Matters for Every Website We Build

Website performance has become a core part of how users experience the web. Fast websites feel smoother, load instantly on mobile, and keep people engaged for longer. Slow websites frustrate visitors and increase the chance they leave before taking action.

Over the past few months, we committed to improving the performance of our own website. The aim was simple: achieve near-perfect PageSpeed Insights scores on both mobile and desktop, not for the numbers themselves, but for the real benefits that come with a faster, more efficient site.

This article shares the steps we took, why we made certain technical choices, and how the improvements now support a better experience for everyone who visits our site.

Mobile & Desktop Results

Why PageSpeed Insights Still Matters

PageSpeed Insights is not just a test. It is one of the easiest ways to understand how a site performs in the real world. The data it provides helps identify:

• slow loading scripts
• layout shift issues
• oversized assets
• inefficient caching
• bottlenecks on mobile devices

A high score is not the goal in itself, but a reflection of a strong user experience. Faster websites convert better, support SEO more effectively, and feel more reliable on every device.

Our aim was to bring our site up to the same standard we deliver for clients. If we expect high performance from the websites we build, our own platform must meet the same standard.

What We Discovered During Our Audit

Even though the site was already modern and well-built, the audit highlighted a few opportunities for improvement:

• legacy images that were larger than necessary
• CSS that could be optimised and served more efficiently
• some unused scripts that were once needed but no longer in use
• room to improve caching and server-side delivery
• network delivery that could be enhanced through a CDN

None of these issues were severe, but small refinements often add up to major improvements in real-world performance.

Why We Chose LiteSpeed as the Foundation

Our server environment already performed well, but LiteSpeed offered a far more efficient way to handle caching, compression, and optimisation.

LiteSpeed Cache gives us:

• automatic image optimisation
• critical CSS generation
• efficient delivery of JS and CSS
• improved caching rules for both logged-in and logged-out users
• advanced HTTP/3 support
• low-resource overhead, even under load

Most importantly, LiteSpeed integrates seamlessly with QUIC.cloud CDN, which became a major factor in our optimisation strategy.

Integrating the QUIC.cloud CDN

Choosing a CDN plays a critical role in how quickly a website loads across the UK and internationally. After testing several options, including Cloudflare, we chose QUIC.cloud for three main reasons:

1. Deep, native integration with LiteSpeed

LiteSpeed and QUIC.cloud are built to work together. Features like:

• full page caching,
• dynamic cache purging,
• image optimisation, and
• server-level HTTP/3 tuning

all function more effectively when used as a pair.

This removes the need for complicated workarounds or plugin conflicts.

2. True, full HTML caching for WordPress

Cloudflare offers HTML caching, but typically only with more advanced configurations or paid add-ons. QUIC.cloud provides full-page HTML caching designed specifically for WordPress/LiteSpeed setups, which makes performance both predictable and consistent.

3. Better control over optimisation workflows

QUIC.cloud gives us an integrated dashboard to manage:

• image compression
• WebP conversion
• critical CSS
• page optimisations
• content delivery adjustments

The result is a single ecosystem where everything works together, rather than a collection of third-party tools.

What We Changed and Improved

Once the optimisation plan was agreed, we began tackling the site step by step. The improvements included:

1. Full caching configuration

LiteSpeed Cache was configured to ensure:

• efficient page caching
• correct handling of dynamic content
• optimal rules for mobile and desktop users

2. Global CDN activation

QUIC.cloud was activated and configured for full-page caching. DNS records were updated to ensure the CDN handled as much of the delivery pipeline as possible.

3. Image optimisation

Legacy images were optimised, converted to WebP where appropriate, and resized to match their on-page use.

4. Removal of unused scripts and CSS

Older assets no longer needed were removed or replaced with streamlined versions.

5. Critical CSS and asynchronous loading

Critical CSS was generated per URL, and less important CSS was deferred. This massively improved first contentful paint and layout stability.

6. Font loading improvements

Fonts were optimised to prevent layout shift and reduce initial load times.

7. Fine-tuning server settings

LiteSpeed’s server-level compression, Brotli, and HTTP/3 settings were activated for maximum efficiency.

The Final Results

Once the optimisation phase was complete, the site was tested again on both desktop and mobile. The results were extremely positive, with near-perfect scores across the board.

You can add your screenshots to this section once ready.

Why These Improvements Matter for Our Clients

Improving our own site was not just a technical exercise. It reinforced the principles we apply to every client project:

• optimised websites convert more effectively
• fast sites rank more reliably over time
• better performance reduces server costs
• mobile users receive the experience they expect
• a well-tuned site is easier to maintain and scale
• Core Web Vitals are far easier to pass when foundations are strong

By applying the same process to our clients’ websites, we ensure their platforms remain competitive and future-proof.

Final Thoughts

Achieving excellent PageSpeed Insights scores is not about chasing numbers. It is about building websites that feel fast, reliable, and effortless to use.

Optimising our own site has helped us refine our process even further, proving that performance is not a one-time job — it is an ongoing part of running a modern website.

If you’re planning a redesign, considering performance improvements, or simply unsure how your website measures up, taking the time to review your PageSpeed Insights results is one of the simplest and most impactful steps you can take.