Why Is My Website Slow, and Does It Actually Matter?

Here is the trap almost everyone falls into.

You open your website. It appears instantly. It has always appeared instantly. You conclude the site is fast, and you’re wrong, because you are the single least representative visitor it has.

You’re on the office wifi. You’re probably on a desktop. Your browser has your site cached from the last forty times you looked at it. You know exactly where everything is, so you don’t experience the two seconds where nothing is on screen yet.

A first-time visitor tapping your Google listing from a phone in a parking lot with two bars of signal is having a different experience entirely. That’s the one being measured.

The three numbers Google actually uses

Google publishes these openly as Core Web Vitals on its web.dev documentation site, and they’re worth knowing in plain terms because the names are terrible.

Largest Contentful Paint (LCP) — how long until the biggest thing on screen actually appears. Usually your header image or headline. Google considers under 2.5 seconds good, 2.5 to 4 seconds needs improvement, and past 4 seconds poor.

Interaction to Next Paint (INP) — when someone taps a menu, how long before something visibly happens. Good is 200 milliseconds or less. This is the one behind the universal experience of tapping a button twice because nothing seemed to happen.

Cumulative Layout Shift (CLS) — how much the page jumps around while it loads. Good is 0.1 or less. This is the ad or image that loads late, shoves everything down, and makes you tap the wrong thing.

Two details in Google’s documentation matter more than the numbers themselves.

First, it grades at the 75th percentile of real page loads, separated for mobile and desktop. Three out of four visits need to clear the bar. Your fast visits don’t cancel out your slow ones.

Second, this is field data — measurements from real people on real devices — not a lab test run on a fast connection. Which is exactly why your own impression of your site is not evidence.

Does it change your ranking?

Somewhat, and less than speed-optimization vendors suggest.

Google Search Central documents Core Web Vitals as part of how Google assesses page experience, and page experience is one signal among many. A fast page about the wrong thing still loses to a slow page that answers the question.

The stronger argument has nothing to do with ranking. A visitor who taps through from Maps looking for your service times and sees a blank screen for four seconds may simply leave. They don’t file a complaint. You never learn it happened. That’s the actual cost, and it doesn’t show up in any report.

What’s actually making it slow

In small-business and church sites, it’s nearly always some combination of five things.

1. Images nobody resized. The most common cause by a wide margin. Someone uploads a 4,000-pixel photo from a phone into a slot that displays it at 800 pixels. Every visitor downloads the whole file. A single unoptimized hero photo can be larger than an entire well-built page.

2. Plugin sprawl. Every plugin can add its own scripts and stylesheets to every page, including pages where it does nothing. A site running twenty-five plugins is loading a lot of code to render a contact form. This overlaps with the security problem: the same sprawl that slows a site down is the thing that gets it compromised.

3. Third-party scripts. Analytics, chat widgets, social feeds, embedded maps, tracking pixels. Each is a request to someone else’s server, and your page waits on their speed. An embedded social feed is frequently the slowest thing on a small-business homepage.

4. Cheap shared hosting. Your site sits on a server with hundreds of others. When one of them gets busy, yours slows down, and you have no control over it or visibility into it. This is where the difference between four dollars a month and thirty actually shows up.

5. Fonts and layout loading in the wrong order. Custom fonts that block text from appearing, images without dimensions declared so the page reflows when they arrive. These are the usual causes of a bad layout-shift score.

What to do, in order

1. Measure it properly. Run your site through Google’s PageSpeed Insights and read the field data section, which reflects real visitors, rather than the lab score. Test the pages people actually land on, not just your homepage.
2. Fix the images. Resize to the dimensions you actually display, save in a modern format, and check the biggest offenders first. Often this alone moves you from poor to good.
3. Audit your plugins. Remove anything you don’t use. Deactivated isn’t removed.
4. Cut third-party scripts you can live without. Ask what each one earns you. The chat widget nobody has answered in eight months is costing you every visitor.
5. Reconsider hosting if the first four don’t get you there. This is the expensive step, so do it last.

The honest summary

Speed matters, and it matters most for the visitor who found you on a phone and hasn’t decided about you yet. It is not the most important thing about your website, and anyone selling you a rebuild purely on a speed score is overselling.

Most slow sites are slow because of what’s been piled onto them over the years, not how they were built. That’s good news: it means the fix is usually an afternoon of cleanup rather than a project.

Start with the images. It’s almost always the images.