How to Make Your Website Faster: 9 Quick Wins That Actually Move Metrics
Site speed is one of the few optimizations that users, Google and your hosting bill all agree on. Google's Core Web Vitals — largest paint, interaction latency, layout shift — are ranking signals, and every one of them traces back to a small set of causes. This is the checklist, ordered by how much each fix usually buys you.
Step 0: measure before touching anything
Run PageSpeed Insights (pagespeed.web.dev) on your live URL — it gives both lab and field data. Note your scores, change one thing, re-measure. Without this loop you are guessing. (Google's "good" thresholds: LCP under 2.5 s, INP under 200 ms, CLS under 0.1.)
The wins, biggest first
1. Fix your images
Usually 40-70% of a page's weight. Serve WebP or AVIF, size files to their display dimensions, and lazy-load everything below the fold: <img loading="lazy" width="1200" height="630">. Preload only the image you need on first paint.
2. Cut third-party scripts
Tag managers, chat widgets and ad scripts block rendering longer than their size suggests. Every script you add later should load with async or defer — and ask whether it earns its place.
3. Ship fewer bytes of CSS and JavaScript
Delete unused rules (most sites ship more CSS than they render), minify in production, and defer non-critical JS. One stylesheet in the head beats three fighting for it.
4. Fonts
Self-host, subset to the characters you use, and always set font-display: swap so text appears instantly while the webfont loads. Limit yourself to two or three weights.
5. Caching
Static assets: Cache-Control: public, max-age=31536000, immutable for fingerprinted files; short or revalidating caches for HTML. On Cloudflare Pages this is configured with a small _headers file.
6. Use the CDN you already have
Cloudflare, Vercel and Netlify all serve from edge locations — make sure you are on one before buying anything.
7. Preconnect and preload hints
<link rel="preconnect"> to origins you depend on removes a DNS+TLS handshake from the critical path.
8. Reduce layout shift
Reserve space for ads, images and embeds (width/height attributes, fixed ad-slot heights) so nothing jumps as it loads.
9. Kill render-blocking redirects
Every redirect hop adds a round trip. Serve canonical URLs directly — the clean-URL behaviour of hosts like Cloudflare Pages already handles this server-side.
What "fast enough" looks like
For a content site: text on first paint, no layout jumps, images arriving progressively, nothing waiting on a script. Most static sites that follow this list land in the "good" range on PageSpeed without touching a server — speed is mostly discipline, not infrastructure.
Want the full checklist applied to your site? Start with PageSpeed Insights, fix images first, then work down the list — and compare hosting behavior in Netlify vs Vercel vs Cloudflare Pages.
Need something like this built? I take freelance projects in streaming, web apps and automation. Get in touch.