Website performance

Test and improve your website’s loading speed

Measure the same page more than once, on mobile and desktop, then fix the slowest part first. A single score is useful evidence, but it is not the whole visitor experience.

Test both devicesMobile and desktop results can expose different bottlenecks.

Repeat the testRun it several times and compare the median, not one unusually fast or slow result.

Fix the largest delayStart with server response, oversized media or blocking code rather than chasing every warning.

Quick test

Start with the exact page your visitors use

1

Open PageSpeed InsightsEnter the full public URL, including https:// and the page path.

2

Review mobile and desktopA page can perform well on a fast desktop connection but poorly on a mobile device.

3

Run two or three more testsHosting caches, third-party services and network conditions can vary between runs.

4

Record the URL, time and resultThis makes later comparisons meaningful after you change the site.

Open Google PageSpeed Insights. For a detailed loading timeline, you can also use WebPageTest.

Reading the result

Understand the measurements that matter

Largest Contentful Paint (LCP)How quickly the main visible content appears.

Interaction to Next Paint (INP)How responsive the page feels when a visitor interacts with it.

Cumulative Layout Shift (CLS)Whether content moves unexpectedly while the page loads.

Time to First Byte (TTFB)How long the browser waits before the first response arrives from the server.

Field data and lab data answer different questions.

Field data reflects eligible real Chrome visits over time. Lab data is a controlled diagnostic run. A new or low-traffic site may not have enough field data yet.

Find the bottleneck

Separate hosting delay from page weight

Slow first responseInvestigate PHP work, database queries, uncached pages, external API calls and server resources.

Large transfer sizeResize and compress images, use modern formats, and avoid loading video before it is needed.

Long main-thread workReduce heavy JavaScript, duplicate plugins and third-party widgets.

Render-blocking resourcesLoad critical styles efficiently and defer non-essential code where safe.

WordPress

Make one controlled change at a time

Back up the site first. Update WordPress, the theme and plugins, remove software you no longer use, optimise original images and test page caching. Re-run the same URL after each material change so you know what helped.

A caching or optimisation plugin can break a site when configured aggressively.

Check menus, forms, checkout, login and mobile layouts after combining or delaying scripts. Clear both the application cache and browser cache before comparing.

Fair comparison

Avoid misleading tests

  • Test the final HTTPS URL and note any redirect chain.
  • Compare equivalent pages, not a simple home page with a complex shop or portal.
  • Test while logged out unless the slow experience affects signed-in users.
  • Try a private browser window to separate extensions and old browser data.
  • Check from more than one network if only one person reports the issue.

Need help?

Give support a reproducible example

Send the exact slow URL, the date and time of a recent test, mobile or desktop, your PageSpeed or WebPageTest result, whether the delay occurs before content appears or after interaction, and any recent plugin or site change.

UKC-hosted website still slow?Open a ticket with that evidence and the affected hosting service. Do not send your password.

Open a support ticket

Was this answer helpful?

« Back