Website Speed and Core Web Vitals: What Actually Matters
A site is slow when it fails Google's Core Web Vitals on mobile: largest contentful paint over 2.5 seconds, interaction to next paint over 200 milliseconds, or layout shift over 0.1. Test it in PageSpeed Insights, fix the images first, and rebuild when patching stops working. Built fast from day one: websites and landing pages.
About 880 people a month search "website speed optimization" and another 70 search "core web vitals optimization" (our September 2026 keyword pull). Most are owners who were told their site is slow by a customer, a competitor's salesperson, or a free audit tool that emailed them a red score. Here is what slow means in numbers, how to check it yourself, what causes it, and when a rebuild beats patching.
What are Core Web Vitals?
Core Web Vitals are the three measurements Google publishes thresholds for: largest contentful paint (LCP), interaction to next paint (INP) and cumulative layout shift (CLS). A page is rated good when LCP is 2.5 seconds or less, INP is 200 milliseconds or less and CLS is 0.1 or less, measured at the 75th percentile of real visits (Google's web.dev Core Web Vitals documentation, checked September 2026).
In plain language they answer three questions: how long until the page looks loaded, how fast it reacts when someone taps, and how much it jumps while loading. If you are holding an older audit, note that INP replaced first input delay in March 2024 (web.dev, checked September 2026).
| Metric | Google's good threshold | What it measures | Most common cause on a small business site |
|---|---|---|---|
| LCP (largest contentful paint) | 2.5 seconds or less | How long until the biggest thing on screen is painted, usually the hero image or headline | A hero image or background video uploaded at full desktop size and sent to a phone unchanged |
| INP (interaction to next paint) | 200 milliseconds or less | How fast the page responds when someone taps a menu, a form field or a call button | Too much JavaScript at once: page builder scripts, a chat widget, tracking tags, a pop-up tool |
| CLS (cumulative layout shift) | 0.1 or less | How much the page moves under the reader's thumb while it loads | Images and embeds with no reserved space, plus a web font that swaps in late and pushes text down |
The 75th percentile part is what people skip. Passing means three out of four real visits hit the target on real phones, so loading your homepage once on office wifi and deciding it feels fine proves nothing.
How do you test your website speed?
Run the page through PageSpeed Insights at pagespeed.web.dev, which is free and made by Google, then read the three metrics instead of the score out of 100. It reports two things: field data from real Chrome visits over the previous 28 days, and lab data from a simulated phone on a throttled connection.
- 01
Test the pages that earn money. Speed is measured per page, so your homepage can pass while the service page your ads point at fails.
- 02
Read the mobile tab. Desktop almost always looks better, and it is not the version Google judges you on.
- 03
Watch LCP, INP and CLS, not the score. The composite score moves between runs because it depends on the machine running the test.
- 04
Check Google Search Console. Its Core Web Vitals report sorts your URLs into good, needs improvement and poor, so you see how much of the site is affected.
Why is the mobile score the one that matters?
Because Google crawls, indexes and ranks the mobile version of your site, and because most local service searches happen on a phone. Google completed the move to mobile-first indexing on July 5, 2024, and now uses its smartphone crawler for all sites (Google Search Central, checked September 2026).
The gap is bigger than owners expect. A hero image that appears instantly on office fiber is a multi second wait on a phone with two bars in a driveway, and a tap that feels immediate with a mouse feels sticky under a thumb while a chat widget is still starting up.
Green on desktop and red on mobile means you have a slow website.
Why is my small business website slow?
Almost always page weight and a busy server, not a hidden coding fault. Six causes explain most slow small business sites, and the first two account for most of the seconds.
- Oversized images. A photo straight off a phone can be several megabytes. Shown at 600 pixels wide, the visitor still downloads the full file.
- A hero video. Autoplay background video is the heaviest thing most small sites ship, and it loads before anything is readable.
- Page builder bloat. Drag and drop builders output deeply nested layouts and load their own CSS and JavaScript on every page, used or not.
- Plugin pile-up. A site with 25 plugins loads files from 25 vendors, several of them doing a job the theme could do alone.
- Cheap shared hosting. On a crowded plan the server is slow to send the first byte, and every on-page fix sits on top of that delay.
- Third party scripts. Chat bubbles, review sliders, booking embeds, heat maps and tag managers each load code from someone else's server, and you inherit their speed.
Want a site that is fast before it launches?
Ziwi builds on WordPress, checks every page on mobile before it goes live, and hosts it for $99 a month. Published prices, month to month, and you own the site.
Which speed fixes pay off first?
Images first, then video, then scripts, then hosting, then the builder. The order is deliberate: the first three are usually most of the page weight and cost nothing but an afternoon, while the last two cost money.
- 01
Resize and compress every image. Export at the size it is actually displayed, save as WebP, and lazy load anything below the fold. Biggest single win on most sites.
- 02
Remove the autoplay hero video. Use a still frame, or load the video only when someone taps play.
- 03
Cut third party scripts you are not using. Old pixels, an abandoned chat tool, two analytics tags doing the same job.
- 04
Reserve space for images and embeds. Width and height set so the browser can hold the space is what stops the jumping, which is all of CLS.
- 05
Audit the plugins. Deactivate the unused, replace anything loading a whole library for one small feature, and stop running two plugins that overlap.
- 06
Move to managed WordPress hosting. A faster server improves every page at once. Ziwi hosting is $99 a month, as of September 2026, with updates and backups included.
- 07
Add caching and a CDN last. Caching makes a heavy page arrive sooner. It does not make it lighter, and the problem returns the next time you edit the page.
Does website speed affect Google rankings?
Yes, but less than most free audit emails imply.
Google says its core ranking systems aim to reward content with a good page experience, which includes Core Web Vitals, while also stating there is no single page experience signal and that helpful content still wins (Google Search Central page experience documentation, checked September 2026).
The cost you feel is usually not ranking anyway. It is the visitor who leaves before the page paints, and you paid for that click if it came from ads. Google Ads grades landing page experience as part of Quality Score, so a slow page can raise what you pay per click (Google Ads Help, checked September 2026).
When is a rebuild cheaper than patching?
When the slowness is built into the theme, the page builder or the plugin stack, which is common on sites older than about five years. At Ziwi a rebuild starts at $1,000 for a designed template and $2,500 for a custom design, or $0 with an ongoing plan kept for 12 months, live in 3 days from kickoff (published pricing, September 2026).
- The theme is abandoned. No developer updates means no fixes coming, and eventually a security problem sitting on top of a speed problem.
- The plugins are doing the theme's job. Sliders, layout add-ons and shortcode kits stacked on each other are weight you cannot remove without breaking pages.
- The fix list is longer than the build. Twenty items across every template means paying to renovate a structure that was never fast.
Every Ziwi build goes through a speed gate before launch: pages are checked on mobile in PageSpeed Insights against Google's published thresholds, and anything that misses is fixed before the site goes live rather than after a client complains. Hosting is $99 a month. Ziwi Care is $299 a month per location, adding a new post every week and unlimited small edits, with the first month free.
A fast site drifts slow again the week someone uploads a four megabyte photo of the new truck, so speed checks belong in an ongoing plan rather than a one time audit. The task list that keeps a WordPress site quick sits on our WordPress maintenance plans page, and the plan comparison is in what website maintenance includes. If the site itself is the problem, look at the website redesign service, or start with the build options and prices on websites and landing pages.