The fix I made to my own site, with the full numbers
My own website
A performance check (PageSpeed Insights, mobile) on peterwallconsulting.com showed a Performance score of just 67. The main content element (LCP) took 7.0 seconds to load, first content (FCP) took 3.0 seconds, and the overall Speed Index sat at 4.8. The causes: oversized hero images sent at the same size to every screen, including mobile, and Google Fonts blocking the page’s initial render.
I fixed both problems for real, not just in theory. I added mobile-sized responsive hero images (srcSet/sizes), so mobile gets a much smaller file than desktop. I changed how Google Fonts load so text shows immediately in a fallback font (font-display: swap) and the brand font swaps in when ready, instead of blocking the page’s initial render. And I shrank an oversized image asset that had no reason to be that large.
Re-measured after deployment: the performance score went from 67 to 92. Main content load time (LCP) dropped from 7.0 to 3.1 seconds, first content (FCP) from 3.0 to 1.7 seconds, Speed Index from 4.8 to 2.0, and total blocking time (TBT) from 140 to 120 milliseconds. Visual stability (CLS) stayed perfect both before and after. These aren’t synthetic numbers, this is a real before-and-after check, on my own site. Later I put the site behind Cloudflare’s protection, and the score settled around 82: a deliberate trade of a few speed points for protection against attacks. Another round of fixes in September 2026 brought it to 88, with the protection still in place.
Say hello
Start with a short business efficiency diagnostic, or reach out directly to discuss your information systems, pipelines, or operational bottlenecks.