Slow website: measure speed and choose what to fix

A slow website can make it harder to view services, send an enquiry or complete a purchase. But a performance score alone cannot calculate lost customers. Measure important pages and connect problems to the actual experience.

Lab tests and real visitors are different

PageSpeed Insights may show real-user data and a laboratory test. Field data aggregates observed experiences over a period; the lab test simulates a visit under controlled conditions. Smaller sites may lack sufficient field data. Its absence does not establish that the site is fast or slow.

Compare similar measurement conditions. Mobile and desktop tests are not equivalent. Repeat when appropriate and record address, date and context rather than selecting only the best result.

What to observe

Core Web Vitals cover main-content loading, interaction response and visual stability. They help investigate experience but do not promise a Google ranking.

Signal	Practical question
Main content appears late	Is the hero image large? Is server response slow?
Buttons seem unresponsive	Are scripts occupying the browser or requests taking time?
Elements jump during loading	Is space reserved for images and dynamic content?

Choose important pages and actions

Test the entry page, a service or product page and the path to contact or purchase. On a phone, open the menu and complete the form. A fast homepage does not compensate for a slow or broken checkout.

Illustrative example: the report identifies a 4 MB image displayed in a small area. Serving appropriate dimensions is a concrete improvement hypothesis. Measure the result afterwards rather than promising a percentage beforehand.

Investigate before replacing the site

Images, third-party scripts, plugins, caching and hosting response are possible investigation areas. Understand a component’s purpose before removing it. Disabling a payment plugin to raise a score would lose functionality rather than improve the experience.

Ask for a plan describing the change, risk, checks and before/after comparison. With WordPress, prepare a recoverable copy before altering configuration or components. See missing images when the issue is presentation rather than speed.

Evaluate the result

Compare the same addresses and conditions, perform the customer’s task and monitor real data when available. Technical improvements may be measurable quickly; enquiry volume also depends on traffic, content and offer. We do not treat a score above 90 as a sales guarantee or a reason to rebuild every website.

Request an assessment of your case

Our support starts from €10 per hour of work. Suggest your hours, choose “I cannot estimate” or propose what you can spend. The request does not commission work or confirm a quote: we agree scope and price first. Request support or explore website maintenance.