How to Measure Your Website's Performance

Your website is often the first interaction a potential customer has with your business. In the UK, where consumers are increasingly comfortable researching, comparing, and purchasing online, website performance is not just a technical concern — it is a business-critical factor that directly affects your revenue, your search engine rankings, and your brand perception.

A slow website costs you money. Research consistently shows that every additional second of load time increases bounce rates, reduces conversions, and pushes potential customers towards your competitors. Google has made page speed a ranking factor for both desktop and mobile search, meaning that poor performance also affects your visibility in search results.

But measuring website performance goes far beyond simply timing how long your homepage takes to load. Modern performance measurement encompasses a range of metrics that capture different aspects of the user experience — from the initial visual response to full interactivity, and from perceived speed to actual technical efficiency.

Core Web Vitals: The Metrics That Matter Most

Google's Core Web Vitals are the most important performance metrics for any UK business with an online presence. These three metrics — Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS) — are used by Google as ranking signals and provide a standardised way to measure the user experience.

Largest Contentful Paint (LCP)

LCP measures how long it takes for the largest content element visible in the viewport to render. This is typically the main image, a video thumbnail, or a large block of text. LCP captures the user's perception of when the page has "loaded" — even if background resources are still being fetched. Google considers an LCP of 2.5 seconds or less to be "good", between 2.5 and 4 seconds to "need improvement", and over 4 seconds to be "poor".

Interaction to Next Paint (INP)

INP replaced First Input Delay (FID) as a Core Web Vital in March 2024. It measures the responsiveness of a page to user interactions — clicks, taps, and keyboard inputs — throughout the entire page lifecycle, not just the first interaction. A good INP is 200 milliseconds or less. If your website takes noticeably long to respond when users click buttons, fill in forms, or navigate menus, you likely have an INP problem.

Cumulative Layout Shift (CLS)

CLS measures visual stability — how much the page layout shifts unexpectedly as it loads. If you have ever tried to click a link or button on a website and had the target move just as you clicked because an image loaded above it or an advert appeared, you have experienced poor CLS. A good CLS score is 0.1 or less. Common causes of high CLS include images without defined dimensions, dynamically injected content, and web fonts that cause text to reflow as they load.

Tools for Measuring Website Performance

There is no shortage of tools available for measuring website performance. The challenge is knowing which ones to use and how to interpret their results. Here are the most valuable tools for UK businesses.

Google PageSpeed Insights

PageSpeed Insights is the most accessible starting point. Enter any URL and it provides both lab data (from a simulated test) and field data (from real users via the Chrome User Experience Report). It scores your page out of 100 and provides specific, actionable recommendations for improvement. The field data is particularly valuable because it reflects the actual experience of real users visiting your site — not just a laboratory simulation.

Google Lighthouse

Lighthouse is an open-source tool built into Chrome DevTools that audits your site across five categories: Performance, Accessibility, Best Practices, SEO, and Progressive Web App. It runs a comprehensive series of tests and provides detailed recommendations. You can run Lighthouse directly in Chrome by opening DevTools (F12), navigating to the Lighthouse tab, and clicking "Generate report".

WebPageTest

WebPageTest is a more advanced tool that provides extremely detailed performance data, including waterfall charts showing exactly when each resource loads, filmstrip views of the rendering process, and the ability to test from multiple geographic locations and device types. For UK businesses, testing from a UK-based server location gives the most relevant results for your local audience.

Tool	Type	Cost	Best For	Difficulty
Google PageSpeed Insights	Lab + Field	Free	Quick overview and Core Web Vitals	Easy
Google Lighthouse	Lab	Free	Detailed audits across five categories	Easy–Medium
WebPageTest	Lab	Free	Deep waterfall analysis and comparison	Medium
Google Search Console	Field	Free	Core Web Vitals across your entire site	Easy
GTmetrix	Lab	Free/Paid	Visual performance monitoring	Easy
Chrome DevTools	Lab	Free	Real-time debugging and profiling	Advanced
New Relic / Datadog	Real User Monitoring	Paid	Continuous production monitoring	Advanced

Understanding Your Performance Report

When you run a performance test, you will receive a wealth of data. Knowing what to focus on — and what can safely be deprioritised — is essential for making efficient use of your time and budget.

The Performance Score

Google Lighthouse provides a performance score out of 100. A score of 90 or above is considered "good", 50 to 89 "needs improvement", and below 50 "poor". However, the score itself is less important than the individual metrics that compose it. A site can have a decent overall score but still have one critical metric — like LCP or CLS — that is causing a poor user experience.

Waterfall Charts

A waterfall chart shows every resource that your page loads — HTML, CSS, JavaScript, images, fonts, third-party scripts — in the order they are requested, along with the time each takes to download. This is invaluable for identifying bottlenecks. Look for resources that block rendering (render-blocking CSS and JavaScript), large resources that take a long time to download, resources loaded from slow third-party servers, and unnecessary resources that could be removed or deferred.

Common Performance Issues and How to Fix Them

Unoptimised Images

Images are typically the largest resources on a web page and the most common cause of slow loading times. Ensure all images are served in modern formats (WebP or AVIF), appropriately sized for the display dimensions (do not serve a 4000-pixel image in a 400-pixel container), compressed to reduce file size without visible quality loss, and lazy-loaded where they are below the fold (not visible on initial page load). For UK businesses using WordPress, plugins such as Smush or ShortPixel can automate image optimisation.

Render-Blocking Resources

CSS and JavaScript files that are loaded in the <head> of your HTML can block the browser from rendering any content until they have been downloaded and parsed. Minimise render-blocking resources by inlining critical CSS (the CSS needed for above-the-fold content), deferring non-critical CSS, and adding the async or defer attribute to JavaScript files that are not needed for initial rendering.

Third-Party Scripts

Analytics tools, marketing pixels, live chat widgets, social media embeds, and advertising scripts can dramatically slow down your website. Each third-party script adds DNS lookups, connection time, and download time. Audit your third-party scripts regularly and remove any that are no longer delivering value. For essential scripts, load them asynchronously and consider using a tag manager to control when they load.

Server Response Time

The Time to First Byte (TTFB) measures how long it takes for the server to respond to the browser's initial request. A slow TTFB (over 600 milliseconds) indicates server-side performance issues — perhaps a slow database query, an overloaded server, or a hosting provider with inadequate infrastructure. If your TTFB is consistently high, consider upgrading your hosting, implementing server-side caching, using a Content Delivery Network (CDN), or optimising your backend code and database queries.

Setting Up Continuous Performance Monitoring

Measuring performance once is useful. Monitoring it continuously is essential. Performance can degrade gradually as content is added, plugins are updated, and third-party scripts change. Without ongoing monitoring, you may not notice until your search rankings drop or your conversion rate declines.

Google Search Console provides free, ongoing monitoring of your Core Web Vitals across your entire site, broken down by mobile and desktop. Set up alerts in Search Console so that you are notified if any pages fall below the "good" threshold. For more detailed monitoring, tools like New Relic, Datadog, or SpeedCurve provide real-user monitoring (RUM) that tracks performance for every visitor to your site, giving you percentile-based data that reveals the experience of your slowest users — not just the average.

We recommend checking your Core Web Vitals monthly and conducting a full performance audit quarterly. If you make significant changes to your website — a redesign, a platform migration, or the addition of new features — run a performance test before and after to measure the impact.