Look at more than loading time
A page can display its heading quickly but freeze when someone opens the menu. Another may react well but shift its enquiry button just as a visitor tries to tap it. These are different performance problems.
Google’s Core Web Vitals guidance describes LCP for loading, INP for responsiveness and CLS for visual stability. Good scores support a better experience; they do not guarantee top rankings.
Describe the problem before running a report
Imagine a restaurant menu page in Johor Bahru. The owner says it feels slow. A useful observation would be more specific: the menu photograph takes several seconds to appear, or the booking button moves when a banner loads.
Record the exact page, device and action. Test the public page rather than an editor preview. Where possible, ask someone unfamiliar with the site to try the task so you notice problems you have learned to work around.
Use reports as evidence to investigate
A controlled test models a particular visit. Field data, when available, reflects measurements from real users. The two can differ because devices, connections, page states and measurement periods differ.
Use PageSpeed Insights to inspect a page, then discuss the findings with your developer. Ask which recommendation relates to the behaviour you observed and what trade-off a change would introduce.
Run comparisons under similar conditions. One better score from one run is weak evidence of a lasting improvement.
Check common sources of unnecessary work
- Large images exported far beyond their display size.
- Scripts or widgets that no longer serve a business purpose.
- Images and embeds without reserved layout space.
- Content that is delayed until several other resources finish.
- Heavy interactions that make controls respond slowly.
These are investigation points, not a diagnosis of every website. Removing a booking widget may improve a score while breaking the customer journey. Understand what each component does before changing it.
Verify the improvement where it matters
After a fix, repeat the original task. Check that images remain clear, forms work and the page still explains the offer. Record the change and compare measurements without treating a single number as the whole outcome.
For a small business, fixing a slow or shifting enquiry flow may deserve attention before polishing a rarely visited decorative page. Use the SEO priorities guide to choose a manageable task.
For smaller image files, see image compression and ALT text.