Writing
Blog
Notes on performance scores, what Lighthouse actually measures, and building PafCore in the open. Newest first.
-
Why a website feels slow on a phone
Fine on your computer. Late on a phone. Here is why that happens, and how a free report names the file.
-
A fast homepage can still hide a slow site
A homepage score is one URL. Checkout and product pages can still wait. Check the pages people actually use.
-
What usually slows a WordPress site
What people feel, what a tip list misses, and how a free PafCore report names the slow file when it can.
-
I asked an AI to guess three speed scores. Then I measured them.
A blind test on gov.uk, BBC News and Smashing Magazine. The guesses sounded right. One was 28 points away.
-
When PageSpeed Insights is enough (and when it is not)
A free snapshot of one URL is often right. When tab hell starts, add schedules. Keep three quiet runs so proof stays honest.
-
Why getting faster barely moves your Lighthouse score
A real wait can drop while PageSpeed and the Lighthouse grade stay flat. The curve, tip lists, and what to track instead.
-
Why your Lighthouse score changes when you did nothing
Three quiet runs. Learn the gap. Stop celebrating a lucky Lighthouse screenshot as proof the fix worked.
-
Why I am building PafCore
People pay for speed work. They still guess if it worked. The gap I am closing with a free report that names the slow file.
-
Why a performance score is not enough
A number out of 100 can tell you the page is slow without telling you what to change, or whether the change you made actually helped.
-
How the Lighthouse score is actually calculated
Which five things carry marks, how a timing becomes points, and why fixing a slow page often wins you nothing.