Skip to content
ROI Synth

How to improve website speed: a practical order of work

By ROI SynthPublished 7 min read

To improve website speed, measure first with real-user data (PageSpeed Insights and the Core Web Vitals report in Search Console), then fix causes in order: slow server response, a heavy or late-loading main image, render-blocking CSS and JavaScript, long JavaScript tasks that delay interactions, web fonts, and layout shifts. Aim for the targets Google's documentation gives for a good user experience: Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint below 200 milliseconds and Cumulative Layout Shift below 0.1.

On this page
  1. Measure what real visitors experience
  2. Fix slow server response first
  3. Make the main content load early
  4. Remove render-blocking CSS and JavaScript
  5. Reduce JavaScript work to improve responsiveness
  6. Handle web fonts and layout shifts
  7. Keep it fast after the fix
  8. Questions
  9. Sources

Speed work goes wrong in a predictable way: someone runs a lab test, sees a low score, and applies whatever fixes a plugin or checklist suggests. Some help, some do nothing, and some make things worse, such as lazy-loading the one image that most needs to load first.

The order below starts with measurement and works from the server towards the browser, because a fix early in that chain often makes later problems smaller.

Measure what real visitors experience

There are two kinds of speed data. Lab data comes from a test run in a controlled environment, such as Lighthouse; it is repeatable and good for diagnosing. Field data comes from real visits; it is what your visitors actually experience and what Google's Core Web Vitals assessment is based on.

Google's Chrome UX Report (CrUX) collects field data from real Chrome users. PageSpeed Insights shows both: field data at the top when there is enough traffic, and a Lighthouse lab test below. Search Console's Core Web Vitals report groups similar URLs and shows which groups pass. Smaller sites often have no field data, in which case lab tests on a mobile profile are the best available guide.

Core Web Vitals and Google's targets for a good user experience
MetricWhat it measuresTarget
Largest Contentful Paint (LCP)Loading: when the main content, usually the largest image or text block, has renderedWithin 2.5 seconds
Interaction to Next Paint (INP)Responsiveness: how quickly the page responds visually to clicks, taps and key pressesBelow 200 milliseconds
Cumulative Layout Shift (CLS)Visual stability: how much visible content moves unexpectedlyBelow 0.1

INP replaced First Input Delay as a Core Web Vital in 2024, so older guides that focus on FID are out of date. Our free SEO audit runs PageSpeed Insights and reads the Chrome UX Report for a page, which is a quick way to get both kinds of data in one place.

Fix slow server response first

Every other metric waits for the first byte of the HTML. Time to First Byte (TTFB) is not a Core Web Vital, but a slow start pushes LCP late no matter how well the rest of the page is built.

  • Serve pages from a cache or as pre-rendered static HTML where the content allows it, instead of building every page on every request.
  • Use a content delivery network (CDN) so pages and assets are served from a location near the visitor.
  • Remove redirect chains, especially on the first request (for example http to https to www to the final URL).
  • Find slow database queries and third-party calls made while the server builds the page.

Make the main content load early

On most pages the LCP element is a hero image or a large heading. Find it first: PageSpeed Insights names it in the diagnostics. Then make sure the browser discovers it early and can download it quickly.

  • Don't lazy-load the hero image

    Lazy loading suits images below the fold. Applied to the LCP image, it delays the most important download on the page.

  • Prioritise it

    Reference the image directly in the HTML rather than through JavaScript or CSS backgrounds, and consider fetchpriority="high" on the LCP image.

  • Right-size and compress

    Serve images at the size they are displayed, with responsive srcset sizes, in a modern format such as WebP or AVIF where supported.

  • Keep text visible

    If the LCP element is text, make sure web fonts do not hide it while they load (see step 6).

Remove render-blocking CSS and JavaScript

Stylesheets and synchronous scripts in the document head stop the browser rendering until they have downloaded and run. Keep the CSS needed for the first screen small, load the rest without blocking, and add defer or async to scripts that do not need to run before the page appears.

Third-party tags are a frequent cause: chat widgets, tag managers, A/B testing scripts and embedded media. Each one should earn its place. Removing a tag nobody uses is often the single biggest improvement available.

Reduce JavaScript work to improve responsiveness

INP suffers when the browser's main thread is busy with long tasks (JavaScript that runs without pausing) at the moment a visitor interacts. The page looks ready but does not respond.

  • Ship less JavaScript: remove unused libraries and code, and avoid loading features on pages that do not use them.
  • Break long tasks into smaller pieces so the browser can respond to input in between.
  • Do the minimum work in event handlers before the next paint, and defer non-urgent work.
  • Render content on the server where possible, so the browser does not have to build the page from JavaScript before anyone can use it.

Frameworks that render HTML on the server or at build time, such as Next.js, make this easier because content arrives ready to display. It is one reason our Next.js development services build sites that way; it does not make a site fast by itself, but it removes a common source of slow interactions.

Handle web fonts and layout shifts

Web fonts can hide text while they load or swap it in late, moving everything around it. Use font-display: swap or optional, preload only the font files needed for the first screen, and subset fonts to the characters you use.

Layout shifts happen when something appears without space reserved for it. Give images and videos width and height attributes, reserve space for embeds and banners, and avoid inserting content above what the visitor is already reading.

Keep it fast after the fix

Speed regresses quietly: a new tracking tag, an unoptimised banner image, a heavier component. Check the Core Web Vitals report monthly, test key templates before releases, and agree a size budget for images and scripts on the pages that matter most.

Google's page experience documentation says Search always seeks to show the most relevant content, even if the page experience is sub-par, and that a great page experience can contribute to success where many pages are equally helpful. The stronger reason to improve speed is commercial: visitors who wait leave. Our website speed optimization work starts from field data and fixes causes in the templates, so improvements apply to every page built from them.

Questions people also ask

What is a good page load time?

Google's Core Web Vitals give the most useful targets: Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint below 200 milliseconds and Cumulative Layout Shift below 0.1.

Why is my PageSpeed Insights score different every time?

The score comes from a lab test, which varies with network conditions and server load at the moment of testing. Field data from the Chrome UX Report is more stable because it summarises a period of real visits.

Does website speed affect SEO?

Page experience can contribute to success in Google Search, but Google says it always seeks to show the most relevant content first. Speed matters most for visitors: slow pages lose them before they read anything.

Will a speed plugin fix my website?

Plugins can help with caching, image compression and script loading, but they cannot fix slow hosting, heavy themes or too many third-party scripts. Measure before and after to see whether a change helped.

How do I improve mobile website speed?

Test with a mobile profile, then apply the same order of work: server response, the main image, render-blocking code, JavaScript and layout shifts. Mobile devices feel heavy JavaScript most, so reducing scripts often helps most.

Where ROI Synth can help

Sources

Search engines change their documentation and features. Facts were checked against these sources on 14 November 2026.

Talk to ROI Synth about your website

Share where your site stands and what you want more of. We will tell you plainly which work is worth doing first, and what it would cost.