Speed & SEO
The 3-second rule
Google's own research has said it for years: as page load time goes from one to three seconds on mobile, the probability of a visitor bouncing jumps dramatically — and over three seconds, more than half of mobile visitors leave. Every technology choice in web design is downstream of that one statistic, and most sites still lose the bet.
Speed isn't a technical vanity metric. It's the tax you pay (or don't) on every marketing dollar — the Facebook ad, the flyer QR code, the friend's recommendation all end at the same loading spinner.
What actually makes sites slow
In audits, the culprits are almost always the same four, in this order:
- Uncompressed images. A phone photo dropped straight from the camera is 4–8 MB. Multiply by a gallery and the site is carrying tens of megabytes for pixels nobody can see on a 6-inch screen.
- Script sprawl. Forty third-party scripts — chats, pixels, analytics, fonts, widgets — each adding round trips and render blocking. Most sites use a fraction of what they load.
- Heavy page builders. Visual drag-and-drop convenience ships as hundreds of KB of CSS and JS before your content appears.
- Cheap shared hosting far from your visitors. The server itself adds whole seconds before the first byte arrives.
The fixes, in order of payoff
1. Resize and compress every image. Serve images at the size they're displayed, in WebP, and lazy-load everything below the fold. This single change routinely halves a small business site's weight. It's boring and it wins.
2. Go static where you can. A site that doesn't strictly need a database or per-request rendering shouldn't pay for one. Static HTML behind a cache or a CDN is served from disk and from edge nodes close to the visitor — this very blog is a static site hosted free on Cloudflare Pages, and it's faster than sites that cost monthly fees to run.
3. Audit third-party scripts quarterly. Every pixel and widget should justify its milliseconds. Load what you need after the page is interactive.
4. Measure what visitors measure. Run your site through PageSpeed Insights on mobile, not desktop — mobile scores are the honest ones. Watch "Largest Contentful Paint"; under about 2.5 seconds is where you want to live.
The uncomfortable truth for buyers
Speed is decided at build time, not tune-up time. A site architected around a heavyweight builder with 40 plugins can be nudged 20% faster; it can't be made instant. When I build through Nexa Dev Studio, static-first and tuned for Google from day one is the default, because retro-fitting speed is like retro-fitting a foundation. Ask any prospective builder for a live site they made and test it on your phone, on mobile data, before you sign anything.
Speed is decided at build time. You can't decorate your way out of an architecture problem.
Free speed worth taking
Two zero-cost moves almost any site can benefit from: put a free CDN in front of your origin (Cloudflare's free tier is fine), and cache aggressively everything that doesn't change per-visitor. Together they shave round trips off every page view, wherever your visitors are.