A boutique owner in Santa Fe checks her analytics on a Monday morning. The holiday promotion drove 4,000 visitors over the weekend and netted 60 sales. The shop down the street ran a similar campaign and converted twice as many. The offers were nearly identical. The difference, as it often is, was about three seconds of page load time.
Page speed is the slowest-burning problem in web design — invisible until you measure it, then impossible to unsee. For most small businesses, a slow site is not an annoyance. It is a quiet revenue leak that gets worse every time another plugin is installed or another oversized photo is uploaded.
What “slow” actually means in 2026
For years, page speed meant a single stopwatch number: total load time. Google now uses three more specific signals — the Core Web Vitals — to judge whether a page feels fast to a real human on a real device.
- Largest Contentful Paint (LCP): how quickly the biggest visible element renders. Good: 2.5 seconds or less.
- Interaction to Next Paint (INP): how quickly the page responds when someone taps, clicks, or types. Good: 200 milliseconds or less.
- Cumulative Layout Shift (CLS): how much the page jumps around as it loads. Good: under 0.1.
Google evaluates these at the 75th percentile of real user visits over the previous 28 days. That means 75 percent of your visitors need to hit those thresholds for the page to be considered good. A site that feels fast on your own home Wi-Fi can still be failing for the customer loading it on a phone in a parking lot off Cerrillos Road.
The conversion math
Page speed is a confirmed Google ranking factor, but the bigger story is what it does to revenue before search ever enters the picture. The widely cited industry figure: every 100 milliseconds of additional load time costs approximately one percent in conversions.
Specific case data backs this up. A Google and Deloitte study found a 10.1 percent increase in conversions for every 0.1-second improvement on travel sites. Retail sites in the same study saw 8.4 percent per 0.1 seconds. E-commerce sites loading in under two seconds convert at roughly 3.05 percent on average; sites loading between three and four seconds convert at 1.94 percent — a 57 percent gap from one second of difference.
On mobile, the cliff is steeper. A one-second delay can drop mobile conversions by up to 20 percent, and roughly 53 percent of mobile users abandon a site that takes longer than three seconds to load. For a small business doing $300,000 a year online, the gap between a two-second site and a four-second site is not a tuning detail. It is the difference between buying a new piece of equipment this year and not.
How much does a one-second delay actually cost a small business?
A one-second delay in page load time produces roughly a 7 percent reduction in conversions, averaged across e-commerce, B2B, and lead-generation sites. On mobile, the effect can be two to three times larger. For a site doing $200,000 in annual online revenue, a one-second delay translates to about $14,000 in lost sales — with no drop in traffic, no change in ad spend, and no decline in product quality. The traffic is showing up. It just leaves before it buys.
Where the speed leaks come from on WordPress sites
Almost every slow WordPress site I have audited in Albuquerque, Santa Fe, and Rio Rancho has the same five culprits in some combination:
- Uncompressed images. Hero photos at 4,000 pixels wide, weighing two megabytes each, served the same on every device.
- Bloated themes. Multipurpose themes that load every page-builder library and font file on every page, whether the page uses them or not.
- Plugin pile-up. A site with 35 active plugins, half of them loading scripts on the homepage where they are not needed.
- No caching layer. Every request building the page from scratch in PHP rather than serving a pre-built HTML version.
- Cheap shared hosting. A server doing its best to keep 200 sites running on the same physical machine — your speed limited by the other 199.
None of these are sophisticated problems. They are accumulation problems. Every plugin install, every uploaded photo, every theme update without cleanup adds a little weight. The site that used to feel fine slowly stops feeling fine, and nobody notices the exact week it crossed the line.
How to measure your own site
Three tools cover most of what a small business needs to know.
- PageSpeed Insights (pagespeed.web.dev). Google’s free tool. Run your homepage and your two or three highest-traffic pages. Look at the Field Data section, which shows real user measurements over the last 28 days — that is what Google ranks you on. The Lab Data section is useful for diagnosing but not for evaluating.
- Chrome User Experience Report (CrUX). The underlying dataset PageSpeed Insights draws from. If your site is too low-traffic to appear in CrUX, you will need to lean on lab data and synthetic monitoring tools instead.
- GTmetrix or DebugBear for a deeper waterfall view. These show every file the page requests, in order, so you can see exactly which scripts and images are causing the waits.
Run all three on a Monday and a Saturday. Run them with a mobile device profile on a simulated 4G connection, not your office desktop. The story those reports tell is usually unflattering and usually fixable.
What’s worth fixing first
In practice, the highest-leverage interventions for an under-performing site are predictable:
- Compress and resize images. A single afternoon of work on a 200-photo site can drop total page weight by 60 to 70 percent.
- Audit and remove unused plugins. If you cannot remember what a plugin does, deactivate it for a week and see if anyone notices.
- Add a caching layer. Most quality hosts include server-side caching by default, and most quality WordPress sites add a second layer through a plugin or a content delivery network.
- Move off the cheapest shared hosting. The price difference between $5-a-month and $30-a-month hosting is usually visible in the LCP numbers within a week.
Those four steps, done well, will get most under-performing small-business sites into the Good Core Web Vitals range. Anything past that — code splitting, critical CSS, server-side rendering decisions — is specialist work and rarely the right first move.
Patrick Iverson builds custom WordPress websites for small and mid-sized businesses across New Mexico, with performance tuning baked into the process — including the server-side performance work and heavily customized WooCommerce build for W Department, a Santa Fe boutique with a deep product catalog. If your site feels slow and you are not sure where to start, the right move is to measure first, then decide whether the fix is an afternoon, a weekend, or a rebuild.