Core Web Vitals for Contractors: Measure Performance and Fix the Causes
A contractor website should load useful content promptly, respond when customers interact, and keep controls from moving unexpectedly. Core Web Vitals help measure those experiences. They do not tell you how many rankings, leads, or booked jobs a particular fix will produce.
Know what each metric measures
Google's Web Vitals guidance defines three Core Web Vitals. Good performance is assessed at the 75th percentile, with mobile and desktop considered separately.
Scroll horizontally to view all columns.
| Metric | Experience measured | Good | Needs improvement | Poor |
|---|---|---|---|---|
| LCP | Loading of the largest eligible visible image or text block | 2.5 seconds or less | Over 2.5 through 4 seconds | Over 4 seconds |
| INP | Responsiveness to interactions | 200 milliseconds or less | Over 200 through 500 milliseconds | Over 500 milliseconds |
| CLS | Unexpected visual layout movement | 0.1 or less | Over 0.1 through 0.25 | Over 0.25 |
Separate real-user evidence from a lab test
PageSpeed Insights provides field data from the Chrome User Experience Report when enough data is available, alongside a Lighthouse lab analysis. The field section reflects a rolling 28-day period. Check whether it describes the particular URL or the broader origin.
A Lighthouse score is a diagnostic result under test conditions. It does not establish that real visitors pass every Core Web Vital. Missing field data means there is insufficient reportable evidence, not that the page failed. Record the date, device, URL or origin scope, and data source when comparing results.
Investigate the loading bottleneck
For LCP, identify the actual element in the performance trace. It may be a hero image or a text block. Google's LCP optimization guide separates server response, resource discovery, transfer time, and rendering delay so you can address the part that is slow.
Use appropriately sized images and test suitable compression and formats. Avoid lazy-loading an image that is needed immediately for LCP. A priority hint can help the browser schedule an important resource, but it does not guarantee a fixed improvement. If rendering is waiting on other work, a smaller image may not resolve the delay.
Test real interactions
Try the navigation, contact form, booking controls, and other important actions on representative devices. INP diagnosis considers input delay, event-processing time, and the delay before the next visual update.
Investigate long tasks, expensive handlers, and rendering work. Remove unnecessary scripts only after checking their purpose. Re-test consent, attribution, accessibility, and lead capture after changing script loading. A faster synthetic result is not a successful fix if customers can no longer complete an inquiry.
Keep the layout stable
Reserve space for images, embeds, and content that appears later. Check shifts during interaction as well as initial loading. Font swapping may change text dimensions; font-display:swap and preloading alone do not guarantee stability.
Check the menu, consent controls, and form at several viewport sizes. Preserve usable controls and required information while correcting the measured source of movement.
Measure improvement without promising rankings
Google says Core Web Vitals are used by its ranking systems, but good scores do not guarantee top placement. Useful, relevant content and the broader experience still matter.
Start with important customer journeys and observed problems. Record the baseline, make a targeted change, verify functionality, and compare equivalent measurements afterward. Track inquiries and qualified leads separately. Do not convert a faster score into a revenue claim without actual business evidence.