// about

PageSpeed scores
shouldn't be confusing

// the problem

What you get today

A score and a wall of jargon

Google PageSpeed Insights gives you metrics like LCP, FID, and CLS. Unless you live and breathe web performance, this means nothing.

No clear priorities

Most developers don't know which issues actually matter. Is that render-blocking CSS worse than that unoptimized image?

Generic advice

"Serve images in next-gen formats" is great, but how do you do that in Next.js vs WordPress vs plain HTML?

// who writes this stuff

Meet Declan

D

I'm Declan, a software engineer based in Melbourne. I build web performance tools and Australian cost-of-living calculators. PageSpeedFix is one of them.

These guides come out of real production work — when I hit a problem worth documenting, I write it up here so the next person Googling it finds the actual fix instead of generic advice.

No filler, no "it depends" without a follow-up answer. If you want to see other things I'm working on, head to dekk.dev.

22guides written
3Core Web Vitals obsessed over
0slow pages tolerated
// editorial method

How guides are written

Started from a real performance problem

Articles are based on issues seen while building, auditing, or debugging production web apps. When a guide uses a synthetic example, it is there to isolate the fix, not to replace the real workflow.

Checked against current platform behavior

Framework-specific posts are reviewed against the relevant docs, build output, browser DevTools, or Lighthouse behavior before publication. Advice that changes between versions is called out in the article.

Updated when the fix changes

Older guides are revised when frameworks, browser metrics, or deployment platforms make the original recommendation incomplete. Contact corrections go through the same review before they are published.

Want to learn more?

Explore our in-depth guides on web performance and Core Web Vitals.

Read our guides