A fast website feels like good manners

What a slow website costs the visitor

A visitor does not experience a performance score. They experience a delay before the main answer appears, a button that ignores the first tap or a page that moves just as they try to use it. On a mobile connection, those small failures can be enough to send an otherwise interested customer back to the results.

Speed also changes how every other quality is perceived. Clear writing feels less clear when it arrives late. A polished design feels less trustworthy when it jumps around. Performance is therefore part of the service experience, not a separate technical exercise.

Use the three Core Web Vitals as symptoms

Largest Contentful Paint measures how quickly the main visible content appears. Interaction to Next Paint measures how promptly the page responds after someone interacts. Cumulative Layout Shift measures unexpected movement. Google’s good-experience thresholds are an LCP within 2.5 seconds, INP below 200 milliseconds and CLS below 0.1.

Treat those figures as diagnostic boundaries rather than a marketing badge. Field data in Search Console matters because it reflects real visits across ordinary devices and connections. A laboratory test is useful for finding causes, but a perfect test run does not prove that every visitor receives the same experience.

Check the expensive parts first

Large hero images, externally loaded fonts, third-party scripts and oversized page builders are common starting points. An image should be delivered close to the dimensions and format actually needed. Fonts should be limited to useful weights. Marketing scripts should justify the delay and privacy cost they introduce.

The server matters too, but replacing hosting is not always the first answer. If the initial response is already quick, the delay may be happening in the browser while it downloads, parses and lays out the page. Measure before moving infrastructure.

• Run PageSpeed Insights for the homepage and the most important service page.
• Check Search Console’s Core Web Vitals report for real-user patterns.
• Compress and correctly size the largest above-the-fold image.
• Remove scripts and widgets that do not support a valuable user task.
• Reserve image and embed dimensions so the layout stays still.
• Test on a real mid-range phone, not only a fast desktop connection.

Fix the journey, then watch real users

Prioritise the pages and actions that create business value. A small improvement to the contact journey may matter more than a larger score change on a rarely visited policy page. Record the starting metrics, make one understandable group of changes and compare the same pages afterwards.

Good performance work leaves less for the visitor to notice. The main content arrives, controls respond and the page stays where it was placed. That calmness is the outcome; the score is evidence that helps you reach it.