Make Your Site Faster

Quick wins for immediate speed gains.

Your site is slow. Let’s fix it.

Here’s the brutal truth: users decide whether to stay or leave in the first 2-3 seconds. If your site loads like it’s 2005, they’re gone before your hero image finishes rendering.

Google cares about this too. Page speed is a ranking factor. Not the only one, but a real one. The sites that load fast get a small but measurable edge in search results.

But forget Google for a second. Think about what it feels like to wait for a slow site. You start questioning the business. Is this company legit? Can they even keep a website running? That judgment happens instantly, and it’s usually permanent.

What “Fast” Actually Means

Google defines fast with three specific metrics called Core Web Vitals. These aren’t arbitrary—they measure what users actually experience.

LCP is usually your hero image or main headline. If that takes 4+ seconds to show up, you’ve already lost visitors.

INP (which replaced FID in March 2024) measures whether clicking things actually works. Ever tap a button and nothing happens for a second? That’s bad INP.

CLS is when you go to click something and it moves because an ad loaded above it. Infuriating. Google agrees.

The 80/20 of Page Speed

You don’t need to become a performance engineer. Most slow sites have the same few problems:

1. Images Are Too Big

This is the #1 issue on most sites. That 4MB PNG your designer uploaded? It needs to be a 200KB WebP.

What to do:

• Use WebP or AVIF formats (smaller files, same quality)
• Resize images to the actual display size (don’t serve 4000px images for 800px spaces)
• Lazy load images below the fold
• Always specify width and height attributes (prevents layout shift)

2. Too Much JavaScript Running at Once

JavaScript blocks rendering. Every tracking script, chat widget, and analytics tool fights for the same resources.

What to do:

• Defer scripts that aren’t critical: <script defer src="script.js"></script>
• Load analytics after the page is interactive, not during initial render
• Audit your third-party scripts—you will have 5 that do the same thing

document.addEventListener('DOMContentLoaded', () => {
  setTimeout(() => {
    const script = document.createElement('script');
    script.src = 'analytics.js';
    document.head.appendChild(script);
  }, 2000);
});

3. No Caching

If returning visitors download your entire site every time, you’re wasting their bandwidth and your server resources.

What to do:

• Set cache headers so browsers remember your files
• Use a CDN (Cloudflare’s free tier is genuinely good)
• Cache static assets for a year, HTML for an hour

4. Server Is Slow (TTFB)

Time to First Byte measures how long before your server starts sending data. If this is over 600ms, no amount of image improvement will save you.

What to do:

• If you’re on cheap shared hosting, upgrade
• Enable server-side caching
• Consider managed WordPress hosting (WP Engine, Kinsta) if you’re on WordPress

Platform-Specific Quick Wins

WordPress

Most WordPress speed problems come from plugins. Every plugin adds JavaScript, CSS, and database queries.

Quick fixes:

• Install a caching plugin: LiteSpeed Cache (free) or WP Rocket (paid, but worth it)
• Use ShortPixel to auto-compress uploads
• Delete plugins you’re not using—yes, even the deactivated ones
• Switch to a faster theme if yours is bloated

Shopify

Shopify handles a lot of improvement automatically, but themes matter.

Quick fixes:

• Use a lightweight theme (Dawn is fast by default)
• Compress product images before uploading
• Minimize apps—each one adds JavaScript
• Remove unused sections from pages

Squarespace

Limited improvement options, but still:

Quick fixes:

• Compress images before uploading
• Use fewer sections per page
• Avoid autoplay video
• Pick a simpler template

Custom Sites

Full control means full responsibility.

Quick fixes:

• Enable GZIP compression on your server
• Implement browser caching
• Use a build tool to minify CSS/JS
• Set up a CDN

How to Test Your Speed

Don’t guess. Test.

Google PageSpeed Insights

pagespeed.web.dev
The official tool. Shows both lab data (simulated tests) and field data (real user experiences). Fix what it tells you to fix.

WebPageTest

webpagetest.org
More detailed than PageSpeed Insights. The waterfall chart shows exactly what’s loading and when. Great for debugging specific issues.

GTmetrix

gtmetrix.com
Good for historical tracking. Create an account and monitor your pages over time.

Chrome DevTools

Press F12 → Network tab → reload the page. You’ll see every file loading. Sort by size to find the biggest offenders.

The Technical Stuff (If You’re Into That)

Critical CSS

The CSS needed to render above-the-fold content should be inline in your HTML. Everything else can load later.

body { margin: 0; font-family: system-ui, sans-serif; }
.header { height: 60px; background: #fff; }
.hero { height: 100vh; display: flex; align-items: center; }

Resource Hints

Tell browsers what to fetch early:

Server Configuration (Apache)

# .htaccess
<IfModule mod_deflate.c>
AddOutputFilterByType DEFLATE text/html text/css text/javascript application/javascript
</IfModule>

<IfModule mod_expires.c>
ExpiresActive On
ExpiresByType image/webp "access plus 1 year"
ExpiresByType text/css "access plus 1 month"
ExpiresByType application/javascript "access plus 1 month"
</IfModule>

Server Configuration (Nginx)

# Enable GZIP
gzip on;
gzip_types text/plain text/css application/javascript application/json image/svg+xml;

location ~* \.(jpg|jpeg|png|webp|css|js)$ {
  expires 1y;
  add_header Cache-Control "public, immutable";
}

Common Speed Optimization Mistakes

Avoid these—they cause most of the problems.

• Improving only the homepage. Your product pages and blog posts need love too. Test the pages that actually get traffic.
• Adding more tools to fix slow tools. If your analytics setup is slow, adding a speed monitoring tool doesn’t help. Remove things before adding things.
• Ignoring mobile. Mobile users are on worse connections with slower processors. Always test mobile performance, not just desktop.
• Chasing perfect scores. A PageSpeed score of 90 vs 100 doesn’t matter to users. Focus on real experience improvements, not vanity metrics.
• Improving everything at once. Change one thing, test, repeat. Otherwise you won’t know what worked.

What to Do Right Now

• Run PageSpeed Insights on your homepage and top 3 pages
• Fix the biggest image (there’s always one)
• Add loading="lazy" to images below the fold
• Defer non-critical scripts with the defer attribute
• Test again and see your score improve

That’s it. You don’t need to understand every improvement technique. Fix the obvious problems first, and you’ll be faster than 80% of your competitors.

Keep It Fast

Speed isn’t a one-time project. Every new feature, image, and tracking script can slow you down again.

Monthly habit: Run PageSpeed Insights on your key pages. If scores drop, find out why.

Before launching changes: Test performance impact. That new chat widget will cost you 0.5 seconds of load time.

Set budgets: Decide that your homepage will never exceed 1.5MB total size. Enforce it.

Sources

• Google Core Web Vitals Documentation – Official thresholds and measurement guidance
• Google PageSpeed Insights – How scoring works
• HTTP Archive Web Almanac – Annual state of web performance data

The Speed Verification Checklist

• PageSpeed Insights mobile score is 70+ (higher is better but diminishing returns past 85)
• Core Web Vitals (LCP, INP, CLS) all show green/good
• Pages load visibly within 3 seconds on a mobile connection
• Search Console shows no Core Web Vitals issues

Maintenance: Speed degrades over time as you add features and content. Run PageSpeed Insights quarterly to catch regressions before they hurt rankings.