My Own Site – 100 on Google PageSpeed

This is my own portfolio site, rebuilt as a custom WordPress theme and tuned until Google PageSpeed Insights showed 100 for Performance, Accessibility, Best Practices and SEO, on mobile and on desktop. It is the standard I tune client sites towards, and a record of how I got there.

The result

On 24 October 2026 the home page was tested on Google PageSpeed Insights, on mobile (a simulated phone on slow 4G) and on desktop.

• Performance, Accessibility, Best Practices and SEO: 100 / 100 / 100 / 100, on both mobile and desktop.
• Mobile: largest content in 1.1 s, blocking time 0 ms, layout shift 0.001.
• Home page mobile score: 89 → 100 in one day. The Projects, About and Boat tours pages score 98 on mobile.

What these numbers do not say: this is a lab test, and lab scores move by a point or two between runs (on the same code I saw 98 once and 100 on the other runs). Google’s real-user data for the site says “No Data” for now, because the site has not had enough visitors yet, so I do not claim more than the lab shows.

Where it started

The same morning the mobile score of the home page was 89, and the Projects and About pages were at 88. To find out what was costing the points, I tested the main changes on copies of the page before keeping them on the live site.

What was slowing it down

• The Google Analytics tag, about 156 KB of script, started in the middle of the first paint and kept a phone’s processor busy for a quarter of a second.
• A code-copy plugin pulled jQuery into every page, and a form plugin loaded five files on pages that have no form.
• The home page waited for three stylesheets before it could paint anything.

What I changed

• The analytics tag now loads on the first tap, click, key press or wheel turn, or 10 seconds after the page has loaded. A visit shorter than that with no interaction is not counted, which is the one trade-off.
• Plugin files load only on the pages that use them. Blog posts keep everything.
• The home page CSS is inlined, so nothing blocks the first paint, and two small script and animation costs were fixed.

What this means for your site

Your site is not mine. A store with many plugins needs different fixes, and I never promise a score. The method is the same: measure, find what blocks the first paint, fix the biggest cost first, then measure again. A six-language tourism site I optimized went from 57 to 90 on mobile.

Get a free site audit ↗