"The website feels slow" is the most common complaint with the least useful wording. Visitors don't see your server or your code — they see a white screen that lasts a beat too long, a button that scoots away just as they tap it, a page that won't respond mid-scroll. Each of those is a distinct, measurable problem with a known fix.

This post maps the feelings to their causes, gives you the four fixes that actually move the needle, and — just as important — the list of things you have permission to ignore. Speed work has brutal diminishing returns; the trick is spending your effort where perception lives.

Three feelings, three measurements

The industry measures "slow" with Core Web Vitals — and the vitals are just your visitors' feelings with numbers attached:

Fix 1: The first image is the whole ballgame

The single most common cause of a slow-feeling small-business site is a 4MB phone photo doing the job of a 150KB web image. The camera's original is magnificent and irrelevant — the browser downloads all of it before your visitor sees anything that matters.

• Export for web before it enters the media library — sized for its actual display, in a modern format. This one habit beats every other optimization on this page combined.
• The first image loads first; everything below the fold waits. The hero earns priority; gallery photos load as the visitor scrolls to them. (Pages built in your workspace get this pattern by default — it matters most for images added by hand.)
• Videos don't autoplay their full weight up top. A poster image with a tap-to-play beats a hero video on every connection your customers actually use.

Fix 2: Stop blocking the first paint

Browsers paint nothing until the critical styling and fonts arrive — so everything that loads before first paint is a toll on every visitor. Faster's themes handle the defaults (critical styles first, scripts deferred, fonts that show fallback text instead of invisible text), which means the danger isn't your theme — it's what gets added afterward: the booking widget pasted from a third party, the three tracking pixels, the social feed embed, each one inserting itself into the toll booth.

The discipline is additive hygiene: when something new goes on the page, ask whether it needs to load before the visitor sees content (almost nothing does). And keep one font family with a couple of weights — every extra typeface is another thing the headline waits for.

Fix 3: Reserve space for everything that arrives late

Layout jump has one root cause: the page didn't save a seat for something, so its arrival shoves everything else. The fixes are mechanical:

• Images declare their size so the browser reserves the box before the pixels arrive — placed-from-library images carry this; hand-pasted ones often don't.
• Banners and notices get a reserved slot or appear as overlays — a cookie notice that pushes the whole page down is a self-inflicted layout shift on literally every visit.
• Embeds get a fixed-size container — the map, the reviews widget, the video all load into a box that was always there.

The third-party tax audit

Every widget is someone else's code running on your page at your visitors' expense — the chat bubble, the heatmap tool you stopped checking in March, the spinning badge. Individually defensible; together, they're usually the answer to "why does my site ignore taps."

Quarterly, list every third-party thing on the site and ask two questions: did we act on its data this quarter? and would we add it again today? Whatever fails both gets removed. The fastest performance work you'll ever do is deletion — and since most tracking needs are covered by your connected analytics, many widgets are paying rent for a job that's already done.

Measure like a visitor, fix like a mechanic

Don't guess — audit. Ask for a deep page-speed audit on your most important page (it's part of the same page insight tooling as your SEO checks) and you get the vitals with a ranked list of opportunities: which image, which script, how much each would save. The working loop:

1. Audit the page that earns the money — home, services, booking.
2. Fix the top opportunity only — it's usually the hero image or one heavyweight third-party script.
3. Re-run, confirm the number moved, and stop when the page feels fast on a phone over mobile data — your own thumb is the final reviewer, the same way it is in the publish review.

Speed is also compounding marketing: faster pages rank better, convert better, and bounce less — which you'll see show up in the weekly numbers within a month of fixing the big two.

What you have permission to ignore

• The perfect 100 score. The difference between 88 and 100 is invisible to humans and expensive to chase. Scores are a flashlight, not a grade.
• Server and hosting obsession. For sites on a managed platform, the server is the fast part; the slow part is almost always what the page asks the browser to do.
• Micro-optimizations — minifying an extra 3KB, shaving one request — while a 2MB hero image sits at the top of the page. Order of magnitude first, always.
• One bad number on a tool, once. Like every metric, judge the trend and the feel, not a single synthetic run on a Tuesday.

Frequently asked questions

Run the deep audit on your homepage this week, fix the one image it points at, and delete the widget you stopped checking in March. That's most of "website performance" for a small business — twenty minutes, and your visitors feel it on every visit after.