WordPress PageSpeed: 54 to 100 in 7 Days

Client pings me at 2 a.m., screenshot attached: WordPress PageSpeed Insights mobile score frozen at 54. Eight-second loads on a simulated 4G connection—Core Web Vitals all red.

Seven days. Boom. 100/100 on Performance, Accessibility, Best Practices, SEO. Under two seconds to load. No black magic, no $10k agency bill—just elbow grease and a refusal to buy the plugin hype.

I’ve chased these scores for two decades now, back when dial-up was king and everyone pretended Flash was the future. WordPress PageSpeed optimization? It’s not rocket science. It’s housekeeping agencies charge five figures for.

Why Bother Chasing PageSpeed 100?

Look, Google’s PageSpeed Insights isn’t some holy grail. But it correlates with bounce rates—users bolt after three seconds, max. This site? Service business in Ottawa, PeakSpire’s playground. They knew rankings were tanking; mobile traffic meant nothing if it choked on fonts and scripts.

Before: LCP at 6.2s, TBT 1,800ms, CLS 0.32. Load time: 8+ seconds. Standard Elementor mess—12 plugins, unoptimized images, render-blocking everything.

I cracked the Lighthouse docs first. Weights matter:

TBT alone is 30% of the score. That told me where to focus first.

Smart. TBT: 30%, LCP 25%, CLS 25%, FCP 10%, Speed Index 10%. Scripts hogging the main thread? Kill ‘em.

Biggest win, hands down. Audited every enqueued script. Jquery-migrate? Useless relic. Elementor-waypoints, elementor-frontend? Dequeue on pages that don’t need ‘em.

Here’s the code that nuked TBT from 1,800ms to zero:

function peakspire_dequeue_scripts() {
    wp_deregister_script('jquery-migrate');
    wp_dequeue_script('elementor-waypoints');
    wp_dequeue_script('elementor-frontend');
    remove_action('wp_head', 'print_emoji_detection_script', 7);
}
add_action('wp_enqueue_scripts', 'peakspire_dequeue_scripts', 100);

Score jumps to 75 overnight. That’s 30% of your grade, gone. And no, your site won’t break—test it.

But scripts were just the appetizer.

Is Loading Fonts Only on Desktop Cheating?

Three Google Font families, six weights: 75KB bloat. On mobile 4G? That’s competing with your hero image for precious bytes.

Fix: Conditional load.

@media (min-width: 769px) {
    @font-face {
        font-family: 'Inter';
        src: url('/fonts/inter-v12-latin-regular.woff2') format('woff2');
        font-display: swap;
    }
}
body { font-family: 'Inter', -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, sans-serif; }

Mobile? System fonts. Zero downloads. LCP plummets. This stuck the score at 97—then punched it to 100. Fonts, man. The silent killer everyone ignores.

Here’s my unique take, absent from the original: This mirrors the Netscape wars of ‘95. Back then, we debated image formats while ignoring font bloat. History repeats—Google Fonts are today’s GIFs. Prediction? In two years, Core Web Vitals weights shift; font efficiency becomes 40%. Agencies spinning ‘custom audits’ will pivot to ‘font-first strategies’ at premium prices.

Images next. WebP conversion: 60-70% smaller. Lazy load below-fold. Explicit width/height on every —CLS vanishes. Preload hero:

<link rel="preload" as="image" href="/hero.webp" fetchpriority="high" type="image/webp">

Critical CSS inlined—roots vars for colors, hero flexbox basics. Async the rest:

<link rel="preload" href="/style.css" as="style" onload="this.onload=null;this.rel='stylesheet'">

FCP: 3.1s to 0.8s. No-brainer.

Results table tells the tale:

Cynical eye: Who’s profiting? Plugin devs pushing ‘speed boosters’ that do half this for $99/year. Elementor? Great builder, crap out-of-box perf. WordPress core’s emoji script? Relic from 2015.

This isn’t hype—it’s discipline. Agencies like PeakSpire (full disclosure: not mine, but hats off) offer audits. Free ones in comments, even. Skeptical me says: Do it yourself first. Tools are free.

But wait—stuck at 95? Fonts were the breakthrough. Mobile savings: 75KB on slow links. That’s real-world impact, not lab scores.

Why Does WordPress PageSpeed Still Trip Up Pros?

Twenty years in, and devs still enqueue everything. Buzzword fatigue—‘headless CMS’ promises, yet 40% of web is WordPress, choking on basics.

My critique: PR spin calls this ‘optimization.’ Nah. It’s cleanup. Who makes money? The $5k ‘experts’ skipping dequeue scripts. Bold call: If Google mandated TBT audits pre-launch, half the plugins die.

Devs, replicate this. Start with scripts. Fonts conditional. Images WebP. Test mobile-first.

And that client? Traffic up 20% already. No coincidence.

🧬 Related Insights

• Read more: AI Coding Assistant Snaps: ‘Use Tables for That Div, It’s 1999’
• Read more: StudioMeyer CRM: The Chat-Only Killer of Bloated Contact Trackers

Frequently Asked Questions

How do I improve WordPress PageSpeed from 54 to 100?

Dequeue bloat scripts first (TBT 30%), conditional fonts for mobile, WebP images with lazy/preload. Seven days max.

What’s the biggest WordPress PageSpeed killer?

Render-blocking JS/CSS, especially Elementor cruft and Google Fonts on mobile—nuke ‘em smartly.

Does perfect PageSpeed guarantee more traffic?

No, but it halves bounce rates. Real test: mobile users stick around.