Why fast loading matters
Fast loading matters because most people searching for a local business are on a phone, often in a hurry, and a slow page gives them a reason to hit the back button and call someone else.
Google's own research backs this up. In a Think with Google study, Google found that as page load time goes from one second to 10 seconds, the probability of a mobile visitor bouncing (leaving without doing anything) increases 123%.
Speed also shows up in sales. Google's web.dev team collects case studies on this, including one where Vodafone saw 8% more sales after improving how fast its main content appeared by 31% (web.dev). Your business isn't Vodafone, but the pattern is the same: people stay with pages that respond quickly.
Core Web Vitals, in plain English
Core Web Vitals are three measurements Google uses to describe how a page feels to real visitors. Google's web.dev guide to Web Vitals sets the "good" thresholds:
| Metric | What it measures | Good |
|---|---|---|
| Largest Contentful Paint (LCP) | How long until the biggest thing on screen, usually a photo or headline, appears | 2.5 seconds or less |
| Interaction to Next Paint (INP) | How quickly the page reacts when someone taps or clicks | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | How much the page jumps around while it loads | 0.1 or less |
To pass, a page needs to hit these numbers for at least 75% of visits (the 75th percentile), measured on real phones and computers, not just in a lab test. INP is the newest of the three. It replaced First Input Delay in March 2024 because it measures responsiveness across the whole visit, not just the first tap.
How Google actually uses page experience
I want to be straight about this, because speed often gets oversold. Google's page experience documentation says there is no single page experience signal. Core Web Vitals are used by its ranking systems, but Google is clear that it always tries to show the most relevant content, even if the page experience is poor.
Where speed helps is when there are lots of helpful pages competing for the same search. Google says a great page experience can contribute to success in those cases. So a fast site won't push a thin page past a genuinely better one, but it can be the edge between two similar local businesses.
That's why I treat speed as part of a bigger picture with good content, structured data and local signals. My SEO and AEO page covers the rest.
How themes and plugins slow sites down
Themes and plugins aren't bad on purpose. They're built to work for thousands of different businesses, so they carry code for features most sites never use. Here's where the weight comes from:
- Extra CSS and JavaScript. A theme may load styles for sliders, shop pages and layouts you'll never use, and each plugin often adds its own files on every page.
- Render-blocking files. Some of those files have to download before the browser can show anything at all, so visitors stare at a blank or half-built screen.
- Database queries. On platforms like WordPress, a page is often assembled from a database each time someone visits, and every plugin can add more lookups before the page is sent.
- Page-builder markup. Drag-and-drop builders tend to wrap content in many layers of extra code, which makes pages larger and slower to draw.
- Third-party add-ons. Chat widgets, pop-ups and tracking scripts each add requests to other servers.
Caching and optimization plugins can help, but they're often a fix layered on top of a heavy page. I compare the approaches in more detail on custom code vs. website builders.
How custom code stays fast
Custom code stays fast mostly by leaving things out. When I write a site by hand, each page loads only the code it uses. A few specific habits make a difference:
- Pages built ahead of time. Most pages are generated once and served as ready-made files, so there's no database lookup when someone visits.
- A global edge network. Your site is copied to servers around the world, so it's delivered from a location close to each visitor.
- Properly sized images. Photos are compressed, served in modern formats and sized for the screen they're shown on.
- Reserved space. Images and sections have set dimensions, so the page doesn't jump while loading, which keeps CLS low.
- Minimal JavaScript. Interactive features are added only where they're needed, which helps INP.
Speed is something I check after launch too, as part of website care and hosting.
How to test your own site with PageSpeed Insights
You can test any website yourself in about a minute with Google's free PageSpeed Insights tool.
- Go to PageSpeed Insights and paste in your home page address.
- Click Analyze and wait for the report. Check the Mobile tab first, since that's how most local customers find you.
- Look at the top section first. If your site gets enough traffic, it shows real-visitor data from the Chrome User Experience Report over the previous 28 days, plus a pass or fail for the Core Web Vitals assessment.
- Scroll down to the lab test, which is run by a tool called Lighthouse in a simulated environment. Its score is useful for spotting problems, but it can change from one run to the next.
- Read the suggestions under Diagnostics. Items like "reduce unused JavaScript" or "eliminate render-blocking resources" point straight at theme and plugin weight.
Google's PageSpeed Insights documentation explains the difference between the real-visitor data and the lab data. Try a few inner pages too, not just the home page. If you'd like a second opinion on what your report means, call or text me at 480-550-2871.
Frequently asked questions
What is a good page load speed?
A good target is for your main content to appear within 2.5 seconds, which is Google's "good" threshold for Largest Contentful Paint. The page should also react to taps within 200 milliseconds and shouldn't shift around while loading. Google measures these at the 75th percentile, so most of your visitors need to get that experience, not just the lucky ones.
Does website speed affect Google rankings?
Yes, but less than many people claim. Google says Core Web Vitals are used by its ranking systems, but relevance comes first, and Google will still show the most relevant page even if its experience is poor. Speed matters most when several helpful pages compete for the same search, and it always matters to the people visiting.
Why is my PageSpeed Insights score different every time?
The lab score changes because each test is a fresh simulated load, and small differences in network and server timing add up. The real-visitor data at the top of the report is more stable because it covers the previous 28 days of actual visits. If your site doesn't get enough traffic, that section may not appear.
Can a speed plugin fix a slow WordPress site?
A caching or optimization plugin can help, sometimes a lot, but it works around the weight instead of removing it. If a theme and a dozen plugins are loading code on every page, the plugin is compressing and rearranging that code rather than eliminating it. A lean build avoids most of the problem from the start.
What is INP?
INP stands for Interaction to Next Paint, and it measures how quickly a page visibly responds when someone taps, clicks or types. A good score is 200 milliseconds or less. It became a Core Web Vital in March 2024, replacing First Input Delay, because it looks at responsiveness throughout the visit rather than just the first interaction.