There is a version of your website that loads in 8 seconds. It exists. Visitors find it, start to wait, and leave. You never know they were there. No analytics event fires for the revenue that never happened. This is what website speed costs businesses — not a technical metric, but real customers lost before they read your first headline.

Google has made website performance measurable, named it Core Web Vitals, and made it a ranking factor. But the business case for speed precedes any algorithm update. Research published by Google and confirmed by independent data from Cloudflare, Akamai, and Deloitte shows consistent patterns: every additional second of load time reduces conversion rates by a measurable percentage, and the impact compounds as speed degrades further. This is not a technical issue to be delegated to a developer. It is a revenue issue that belongs in every marketing strategy conversation.

What the data actually shows

The following findings come from published research and case studies across industries. A 1-second delay in page response can result in a 7% reduction in conversions, according to Aberdeen Group research. Pages that load in under 1 second convert at 3x the rate of pages that take 5 seconds, per Portent's conversion research. Google and SOASTA research found that 53% of mobile users abandon a site that takes more than 3 seconds to load. Walmart found that every 1-second improvement in page load time resulted in a 2% increase in conversions. The BBC found they lost an additional 10% of users for every additional second their site took to load.

These are not edge cases. They are the norm across commerce, services, and B2B. If your website takes more than 3 seconds to load on mobile, you are losing the majority of visitors before they see your value proposition. And since most digital marketing channels — SEO, paid ads, social media — are driving mobile traffic predominantly, a slow mobile experience undermines every acquisition investment you make.

What are Core Web Vitals?

Core Web Vitals are Google's set of performance metrics that measure real user experience as it happens in browsers, not in laboratory conditions. There are three primary metrics, each measuring a distinct aspect of perceived performance.

Largest Contentful Paint (LCP) measures how quickly the largest visible element on the page loads. This is typically the hero image or main heading. Good LCP is under 2.5 seconds. Needs improvement is 2.5 to 4 seconds. Poor is over 4 seconds. LCP directly correlates with perceived load speed — it is the point at which a user feels the page has "arrived."

Interaction to Next Paint (INP) replaced Cumulative Layout Shift in 2024 and measures how quickly the page responds to user interaction. When a user clicks a button or taps a link, INP measures the delay before the browser renders a visual response. Good INP is under 200 milliseconds. Needs improvement is 200 to 500ms. Poor is over 500ms. Poor INP makes a site feel sluggish and unresponsive even if the initial load seems fast.

Cumulative Layout Shift (CLS) measures how much the page layout shifts unexpectedly during load. When elements appear, resize, or move after initial render, they cause layout shifts that make users mis-tap links or lose their reading position. Good CLS is under 0.1. Needs improvement is 0.1 to 0.25. Poor is over 0.25. Late-loading images, ads that inject themselves into the layout, and fonts that cause text reflow are common CLS culprits.

Google uses Core Web Vitals as a ranking signal through the Page Experience algorithm. Sites with poor scores are ranked lower than comparable sites with good scores, all else being equal. For competitive keywords where quality content is similar across multiple competing sites, Core Web Vitals can be the tiebreaker that determines page one versus page two visibility.

The most common speed killers

In our experience auditing client websites across industries, the same issues appear with high frequency. Understanding them helps you diagnose your own site before running a formal audit.

Unoptimised images. This is the single most common cause of slow load times across websites we audit. Large, uncompressed images that should be 80KB are often 800KB or more. The solution is threefold: compress images during export, serve in modern formats (WebP instead of JPEG, AVIF for supported browsers), and serve appropriately sized images at different viewport widths using responsive images. WebP conversion alone typically cuts image weight by 30-50% with no perceptible quality difference.

Render-blocking scripts. JavaScript that loads synchronously in the document head blocks the browser from rendering any page content until the script has fully downloaded, parsed, and executed. Third-party scripts are the most common offender: analytics pixels, chat widgets, marketing automation tags, and social media embeds. Each one that loads synchronously in the head adds its loading time to the user's wait before they see anything. Deferring scripts and loading them asynchronously can dramatically improve LCP.

No caching strategy. Without browser caching and a CDN (Content Delivery Network), every page load requests every asset from the origin server. For users physically distant from the server, latency compounds significantly. A user in Lagos loading a site hosted in London adds round-trip latency to every resource request. A CDN stores cached copies of static assets close to users globally, eliminating this latency for returning visitors and reducing origin server load.

Plugin bloat on WordPress. WordPress sites commonly run 20-40 active plugins. Each plugin can add HTTP requests, database queries, and additional CSS and JavaScript files. Many plugins load their assets on every page regardless of whether that page actually uses the plugin's functionality. A contact form plugin that loads its CSS and JS on every blog post page is adding weight to every page that does not contain a form. Plugin audits and conditional loading can dramatically reduce the asset burden on WordPress sites.

Cheap or shared hosting. Server response time, measured as TTFB (Time to First Byte), is the starting gun for all subsequent load activity. Before the browser can render a single pixel, it must receive the first byte of the HTML document from the server. Shared hosting with high resource contention produces slow TTFB, sometimes exceeding 1 second, which delays everything downstream. Moving to managed WordPress hosting (Kinsta, WP Engine, Flywheel) or a VPS with adequate resources often produces the single largest performance improvement available to underperforming sites.

No lazy loading. Loading all images on page load, including those below the fold that the user may never scroll to, wastes bandwidth and delays the loading of content that is actually visible. Modern browsers support native lazy loading via the loading="lazy" attribute, which defers off-screen images until the user scrolls toward them. This should be standard on all image-heavy pages.

How to measure your current performance

Three free tools give you reliable, actionable performance data. Google PageSpeed Insights (pagespeed.web.dev) analyses both lab data and field data collected from real Chrome users, gives a score out of 100, and lists specific issues with fix recommendations. It is the starting point for any performance audit. Google Search Console, under Core Web Vitals, shows your site's real-world performance across all pages as experienced by actual visitors, segmented by mobile and desktop. Issues are categorised as Poor, Needs Improvement, or Good. WebPageTest (webpagetest.org) is more advanced, allowing testing from specific global locations on specific connection speeds, and showing waterfall charts that make asset loading bottlenecks visually clear.

Run a PageSpeed Insights test on your homepage and your top landing page. If either scores below 70 on mobile, you have a problem worth fixing immediately. If either scores below 50, you have an urgent problem that is actively costing you customers and rankings.

The ROI of a performance optimisation project

Performance improvements compound across every channel. Better Core Web Vitals improve SEO rankings, which increases organic traffic. Faster load times increase conversion rates, which increases revenue from existing traffic. More efficient pages reduce bounce rates, which sends better engagement signals to Google and reinforces ranking positions. The investment in a performance optimisation project typically produces the highest marketing ROI of any technical investment a business can make, because it improves every metric simultaneously rather than improving just one channel.

Most sites we audit can achieve 90+ Lighthouse scores after a focused optimisation project. The timeline is typically 4-6 weeks for a thorough optimisation engagement covering image compression, script management, caching, CDN setup, and hosting review. The conversion rate improvements that follow are often visible within the first month post-optimisation.

If you want a free performance audit of your website, get in touch. We will run a full Core Web Vitals analysis and tell you exactly what is slowing you down, what it is costing you in rankings and conversions, and what the prioritised fix list looks like.

The relationship between speed and SEO rankings

Website speed affects conversion rates directly, but it also affects them indirectly through its impact on search rankings. Google's Core Web Vitals became an official ranking signal in 2021 and have been weighted progressively more heavily since. The practical implication is that a slow website gets fewer visitors from organic search, and then converts a smaller percentage of the visitors it does get. Both effects compound: a site with poor Core Web Vitals suffers both reduced visibility and reduced conversion efficiency simultaneously.

For competitive keywords, the difference between a site with excellent Core Web Vitals (90+ Lighthouse score on mobile) and one with poor metrics (sub-50) can be several positions in search rankings. A drop from position 3 to position 7 on a competitive keyword can represent a 50-70% reduction in organic clicks. When the reduced-click-volume audience then encounters a slow-loading page, the compounding effect on total conversions is severe.

Performance optimisation therefore produces a double return: higher traffic from improved rankings, and higher conversion rate from improved user experience. This makes it one of the few marketing investments that simultaneously improves the numerator (conversions) and the denominator (traffic needed per conversion) in the revenue equation.

Prioritising speed improvements: where to start

With many possible performance improvements available, prioritisation matters. Not every fix has equal impact, and some are significantly more complex and expensive to implement than others. The highest-impact, most accessible improvements for most websites follow a clear priority order. Start with image optimisation: audit all images across your five highest-traffic pages, compress using a tool like Squoosh or ImageOptim, convert to WebP format, and implement responsive srcset attributes. This single intervention typically produces the largest Largest Contentful Paint improvement available.

Next, audit and defer third-party scripts. Use the Network tab in Chrome DevTools or the WebPageTest waterfall view to identify all third-party scripts loading on your pages. For each one, evaluate whether it is currently providing measurable business value. Scripts from abandoned chat tools, outdated A/B testing platforms, and redundant tracking pixels accumulate over time on many websites. Removing or deferring them can shave seconds from load time with zero cost and zero development complexity.

Implement a CDN if you are not already using one. For sites hosted on standard web hosting without a CDN, enabling a service like Cloudflare's free tier can reduce TTFB for geographically distributed audiences and reduce origin server load significantly. This improvement requires minimal technical implementation and produces measurable benefits for any site with a geographically diverse audience.

Frequently asked questions about website speed

What is a good Lighthouse score? A score of 90 or above is considered Good. 50-89 is Needs Improvement. Below 50 is Poor. Aim for 90+ on both mobile and desktop as a baseline. Mobile scores typically run 15-25 points lower than desktop for the same page due to simulated mobile network and CPU constraints in the test.

Should I prioritise mobile or desktop performance? Mobile. Google uses mobile-first indexing, meaning it evaluates your site's mobile performance for ranking purposes. And since the majority of web traffic is mobile, mobile performance has a larger impact on conversion rates. Improve mobile first; desktop improvements often follow from the same changes.

How often should I audit website performance? Run a full PageSpeed Insights audit on your key pages quarterly, and whenever you make significant changes to your site. New plugins, new tracking scripts, and new design elements can all affect performance. Treat performance as an ongoing maintenance item, not a one-time project.