A website can display its opening page quickly but respond slowly when you open the menu or submit a form. Another may feel slow only on a phone during a first visit. Before buying an optimisation extension or more expensive hosting, describe the situation: the page address, device, connection and action that takes too long. These details help identify a useful intervention.
Start with mobile and the pages that matter
Check the homepage, a service page and the route to an enquiry or order. Open them without relying on a previous visit's cache as well. A powerful computer on a wired connection can conceal a problem that a customer encounters on an ordinary phone. Note whether the delay occurs before content appears, after it appears or when pressing a control.
PageSpeed Insights separates its laboratory test from real user experiences aggregated over the previous 28 days. Check whether the real data covers the page or the whole origin. Missing data does not establish that a page is fast or slow: there may simply be too few measurements.
What do the metrics tell you beyond the score?
An overall score provides a starting point but cannot identify the cause on its own. Core Web Vitals cover different experiences:
- LCP: when the main element of the page becomes visible.
- INP: how quickly the page responds to interactions.
- CLS: how much elements move while the page is displayed.
A large image can delay the main content, a busy script can block interactions, and an image without reserved space can shift a button. Laboratory testing helps with diagnosis but does not replace evidence from actual visitors. Ask for an explanation of the observed problem, rather than just a screenshot with a green circle.
Images, scripts or the server: where is the bottleneck?
Images should be checked against their displayed size, format and loading order. A banner photograph need not be delivered as the original camera file. However, postponing the main image until after other resources may delay the opening screen itself. Optimisation should retain clarity and check the appearance on mobile.
Scripts for chat, analytics, advertising, maps or extensions can add requests and work in the browser. Review what each page needs and when it should run. Removing form code at random to improve a score is not a useful fix: functionality and existing consent choices must be preserved.
The server and caching matter if the initial response is slow or the same page is regenerated unnecessarily. Check the platform, hosting and external resources before recommending a migration. A larger hosting package does not automatically fix oversized images or code that blocks interactions.
How do you compare before and after fairly?
Keep the original reports with the exact address, date, tool version and mobile or desktop mode. Repeat measurements under similar conditions and compare several runs. One score difference may reflect the network or the test machine's workload without demonstrating the effect of a change.
After the work, check the same pages and actions: navigation, forms and checkout, where present. Ask for the changes made, comparable measurements and unresolved issues. Aggregated real user data does not refresh immediately after publication. The result should also explain constraints imposed by the platform or external services.
What impact should you look for, and what does it cost?
The practical aim is to let visitors read the offer and complete their task without unnecessary delays. A technical improvement does not automatically establish an increase in sales, which also depend on the offer, traffic and content. Google explains that good measurement results do not guarantee top rankings. Promising a score of 100 regardless of the website is not a useful commitment.
Website speed optimisation starts from 499 lei per project, covering one website and the interventions agreed after an audit. Scope and checks are defined in the quote; the starting price does not automatically cover any redesign. Website maintenance has a separate responsibility. See Pricing and use Contact to send the page addresses and specific situations that feel slow.