A slow page can make a useful website harder to use. But a performance score cannot tell you how much revenue a change will create. Start with the experience, identify the delay, then measure what happens after the fix.
For a service business, that means looking at both page behavior and the route to an inquiry. A fast page still needs a clear offer and an obvious next step.
Measure three parts of the experience
Google's Core Web Vitals cover loading, responsiveness and visual stability. The current good-experience thresholds are measured at the 75th percentile of visits:
| Measure | What it describes | Good threshold |
|---|---|---|
| Largest Contentful Paint (LCP) | When the main visible content appears | 2.5 seconds or less |
| Interaction to Next Paint (INP) | How quickly the page responds visually to interactions | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | Unexpected movement of visible content | 0.1 or less |
See the Web Vitals reference for definitions and measurement guidance. A low score tells you where to investigate, not which specific business outcome will follow.
Separate a lab test from real visits
Lighthouse runs a controlled test under configured conditions. It helps compare a page before and after a change and identify likely bottlenecks. Real-user data includes the devices, connections and interactions your actual visitors have.
Record the tool, date, page and test settings with a result. Compare equivalent runs. Do not label a local test as evidence of what every customer experiences, and do not treat the Lighthouse SEO checklist as proof of search rankings.
Fix the largest visible image first
The first screen often contains a large photograph or illustration. Send an image sized for the layout and device, give it dimensions so space is reserved, and avoid delaying the main image behind lazy loading.
Images lower on the page can load later. On Westcode, portfolio photographs and the footer photograph are deferred so the opening experience has less competing work. The image still has a stable place in the layout before its bytes arrive.
Load expensive features when they are useful
The British Columbia guide starts with an SVG landscape and a readable place list. Its interactive map loads near the map section. A visitor reading the introduction does not need the mapping engine immediately.
Booking embeds have a similar tradeoff. Westcode loads the calendar after someone chooses to book, while keeping a direct link available if the embed fails. The useful question is: does this feature need to compete with the first screen?
Keep motion responsive
A decorative effect should stop when it is off-screen or the page is hidden. Avoid repeatedly measuring and changing page layout during scrolling. Respect reduced-motion preferences and check touch devices separately from pointer interactions.
Test the menu, disclosures, search and inquiry flow as well as the hero. An attractive animation does not compensate for a delayed response to a tap.
Check whether the change helped the business
Record page visits, relevant service or project views, inquiry starts and confirmed outcomes. A booking click and a completed booking are different events. Compare a meaningful period and account for changes in traffic sources, offers and campaigns.
Google uses page-experience signals alongside other considerations; strong scores do not guarantee top rankings. Its page-experience guidance explains that distinction.
A useful first pass
Choose a high-traffic page and a complete customer journey. Capture a baseline, identify the biggest delay, make one focused improvement and repeat the same checks. Keep the result only if the user experience improves without breaking the content or interactions.
