On speeding up a website, I was early on misled by the “you need money to be fast” line — thinking that without a paid CDN there was no optimization to do. Later I found that for most sites, about 70% of speed problems are solvable with free methods. Money isn’t the prerequisite; method is. The mindset needs to flip first.
No budget still has no-budget playbooks: compression, caching, slimming, merging — all zero cost. For exact sequencing, cross-reference the speed chapter in the technical SEO handbook, working by ROI from high to low. You speed up without spending a cent; the order just needs to be right.
Measure first, then move
Don’t guess when speeding up. First use PageSpeed and GSC Core Web Vitals to see which page is slowest and where it’s slow — big images, too many scripts, or a slow server. Locate it clearly, then act; spend effort on the sharp end. Blind optimization tends to spin in place; quantifying is step one, so you don’t waste effort. Direction needs to be right.
Focus on LCP and TTFB: the former usually bottlenecks on big images and resources, the latter on origin response. Single out the reddest pages and rescue them first. This thinking matches crawl budget optimization — find where resources are most needed rather than spreading evenly, for the highest return without waste.
Don’t be fooled by the total score; look per page: if one type of page is especially slow, rescue that type first, more effective than spreading evenly. Metric tools can drill into templates, locating far more precisely than eyeballing the site, saving guessing and keeping effort on the sharp end.
Compress images and code
Images are often the number-one killer: switch to WebP/AVIF, output at display size, lazy-load off-screen images, and volume can be cut by more than half. On the code side, enable Gzip/Brotli, remove unused CSS/JS, merge small files — transfer size drops and first paint naturally speeds up. All zero cost, immediate results.
Many people waste money on a CDN without doing these two free things, getting limited effect. Compress images and code to a reasonable level first; then talk about the rest. The technical SEO handbook has step-by-step operations for this part; follow it once and most sites land in the green zone without spending a cent — eat this first.
Use caching instead of origin hits
You can cache without a CDN: enable browser caching (Cache-Control) and server-level caching (like page cache, object cache) at the origin so repeated requests don’t hit the origin. Short caching for HTML, long caching for static assets, paired with versioned filenames, gets both speed and freshness. Pure configuration, zero cost, fast results.
Caching turns “compute every time” into “compute once, fetch many times,” slashing origin pressure and dropping TTFB. The technical SEO handbook’s caching section has a checklist for this layer: purge on publish, long caches don’t bleed into each other. Follow it; no paid service required, free can be stable too. Recommended to do first.
Slim down third-party scripts
Analytics, ads, chat, share buttons — each is a weight dragging you down, and most aren’t essential. Evaluate one by one: delete what you can, delay-load or async the rest, and don’t let them grab first-paint resources. One fewer script lightens first paint by a notch; this is the cheapest speedup, available instantly.
Especially on mobile, third-party is often the culprit for lag. Use DevTools to see each script’s main-thread usage and push non-critical ones back. This governance shares the same source as the handbook’s “resource priority”: keep core, defer secondary, improving both experience and speed without wasting money.
Server and database
If the origin itself is slow, no amount of front-end optimization saves it. Check slow database queries, turn off redundant background tasks, use persistent connections — even low-end machines can get fast. Much “slowness” is badly written code and queries, not a bad machine; tuning is far cheaper than replacing hardware. Diagnose before prescribing; don’t rush to spend.
Only at a real bottleneck do you consider upgrading specs or moving to a closer datacenter; that’s when spending pays. Don’t throw money at every slowdown; squeeze out the free potential first. Combined with the handbook’s thinking: eight in ten speed problems are about “how you use it,” not “what you use.” Get the method right and you save real money — invest rationally.
Coordinate with the technical handbook
Write the free speedup list into the front-end spec: image formats, compression, caching, script evaluation each defined, reviewed before new pages launch. Standards make speedup repeatable — not dependent on one person knowing the ropes. Team growth doesn’t slow the site down; speed becomes a habit, not a project. Long-term benefit, not one-off.
The overall speed strategy can fold into the technical SEO handbook, read alongside caching, rendering, and Core Web Vitals. “No money for a CDN” is no excuse at all; get the free measures right and most sites’ speed is enough. Money is an accelerator, not an entrance ticket. Don’t be misled; do the things at hand thoroughly first.
Images are the biggest lever
With no budget, compressing images is the highest-ROI move: one unoptimized image can be hundreds of KB, and switching to WebP often cuts 70%. When the first-screen hero lightens, LCP improves immediately. This step costs nothing yet often beats a CDN in effect — do it first, the return is real, don’t ignore it.
Pair it with lazy loading so off-screen images don’t fight for first-paint bandwidth and users see main content faster. Image governance is a free “accelerator” that most sites keep ignoring. Work through the handbook’s checklist item by item; first-paint weight drops and speed shows immediately, with zero dependence on paid tools.
Test mobile-first
Speed results should be judged on real mobile networks; desktop fast doesn’t mean phone fast. Test with real devices or throttling; third-party scripts and images are deadliest on weak networks. Make mobile the primary standard, and optimization aims at the majority of visitors. Don’t be fooled by desktop appearances; direction matters.
When mobile is good, desktop naturally follows. Make the Core Web Vitals mobile report the main dashboard and watch trends weekly. This view matches crawl budget optimization: watch the most constrained end, invest resources where the bottleneck is, and the whole stays balanced — no weak subjects, steady.
One table for the free actions
Figure: Free Speedup — Key Points (compiled by YunyingGO)
| Action | Cost | Gain |
|---|---|---|
| Compress images/code | 0 | Cut most of the volume |
| Enable caching | 0 | Lower origin TTFB |
| Cut third-party | 0 | Lighten first paint |
| Fix slow queries | 0 | Faster origin |
When you act, follow these steps: first use metric tools to locate the slowest pages and why they’re slow; convert images to WebP, enable compression, add lazy loading; enable browser and page caching at the origin; finally evaluate and slim third-party scripts. All four are free, and after one pass most sites’ first-paint speed improves by a clear notch.
