Website speed and enquiries: what Core Web Vitals mean for a local business
Core Web Vitals are Google's three measures of how a page feels to a real visitor: how fast the main content appears, how quickly it responds to a tap, and whether it jumps around. Aim for the main content in under 2.5 seconds on a phone; pages under two seconds convert 57% better than pages taking three to four.
Written by the nextwebsite.co team, and last checked on November 7, 2026.
The three Core Web Vitals
Google measures how a page feels to real visitors with three numbers, and calls them Core Web Vitals1:
- Largest Contentful Paint (LCP): how long the main content, usually the headline or hero image, takes to appear. Good is 2.5 seconds or less.
- Interaction to Next Paint (INP): how quickly the page responds when someone taps or clicks. Good is 200 milliseconds or less. It replaced the older First Input Delay measure on 12 March 20242.
- Cumulative Layout Shift (CLS): how much the page jumps around while it loads. Good is 0.1 or less.
A page passes when at least 75% of real visits meet all three, measured separately on phones and desktops1.
Why phones are the test that matters
Your customers search on their phones, often on a mobile connection, and phones are slower than the computer you use at work. A site that feels fine at the office can take five seconds on a phone. Only 38.4% of WordPress sites pass Core Web Vitals on mobile, and almost all of the gap is loading time3.
Speed and enquiries
Speed shows up in the number of calls and bookings you get. In one 2026 study, pages that loaded in under two seconds converted at 3.05%, against 1.94% for pages taking three to four seconds: 57% more conversions from the same visitors4.
What usually makes a local business site slow
- A heavy hero. A full-width slider or autoplay video at the top, loaded before anything else.
- Third-party scripts. Chat widgets, old trackers, review badges and font services, each one a separate download.
- Page builders. Code for every feature the builder offers, on every page, whether you use the feature or not.
- A distant server. Pages built on request, on one server, for visitors who may be far away.
How to fix it
Measure on a phone profile first. Then make the main content load first, compress and resize images, remove what's above the fold that doesn't earn its place, and cut scripts you don't need. Reserve space for images so the page doesn't jump. For the biggest gain, serve pages built in advance from a network close to your visitors, so nothing is computed when someone arrives.
Checklist
- Measure the page on a phone profile, not on your office desktop.
- Find the largest element on screen at load, usually a hero image or headline, and make it load first.
- Compress and resize images, and remove sliders and autoplay video above the fold.
- Cut third-party scripts you don't need: chat widgets, old trackers, unused fonts.
- Reserve space for images and embeds so nothing jumps.
- Serve the site from a content delivery network close to your visitors.
Check your own site
The free scan loads your homepage on a simulated phone and reports when the main content appears. It takes under a minute.
Or run just this check: the website speed test.
Read next
- Is your WordPress site a security risk? Plugins, PHP and what to check
Over half of WordPress sites run a plugin with a known vulnerability. The five things to check on yours, and what to do about each.
- Joomla, Wix and Squarespace: when to move, and what it costs
Joomla 3 and 4 are past end of life, and site builders trade ownership for convenience. How to tell when it's time to move, and what a move costs.
More on security and speed, and what we build for home services and boutique hotels.