07aLighthouse (mobile)
A real mobile Lighthouse run on the homepage. Three of the four headline scores are strong. The one to watch is speed, where a classic WordPress front-end is carrying more weight than it needs to.
Performance · decent, but held back by load speed below
SEO · a perfect on-page SEO score, nothing to fix here
Accessibility · strong, a small polish away from full marks
Best Practices · solid, room to tidy a few front-end items
Core Web Vitals (the page-speed signals Google and AI both read)
| Metric | Value | Read |
|---|---|---|
| LCP (Largest Contentful Paint) | 3.9s | Slow target is under 2.5s. The main content takes too long to appear on mobile. |
| Speed Index | 5.9s | Poor the page feels slow to fill in visually on a phone. |
| FCP (First Contentful Paint) | 2.4s | Borderline first pixels are a touch late, tied to the same weight problem. |
| TBT (Total Blocking Time) | 10ms | Good the page stays responsive, the main thread is not jammed. |
| CLS (Cumulative Layout Shift) | 0.055 | Good the layout is stable, nothing jumps around as it loads. |
The pattern is clear and common: this is classic WordPress weight. TBT and CLS are healthy, which means the problem is not your code logic or your layout. It is the sheer amount of front-end the page ships before it can paint. The slow LCP and Speed Index are exactly what cost a site mobile rankings and conversions, because a visitor on a phone waits, and Google notices the wait.
07bThe stack
A full Wappalyzer detection of what powers the site. This is a well-built, modern WordPress setup. Nothing here is wrong. It is simply a profile that a static rebuild transforms cleanly.
| Layer | Detected |
|---|---|
| CMS + language | WordPress PHP MySQL |
| Server | LiteSpeed a fast server, doing its job well |
| CDN + protocol | Cloudflare CDN HTTP/3 modern delivery, good calls |
| JavaScript | jQuery 3.7.1 jQuery Migrate 3.4.1 the heritage front-end layer most WordPress themes still ship |
| UI libraries | Splide Masonry sliders and grid layout helpers |
| Analytics | Google Tag Manager Google Analytics tracking is in place, good |
| Social + sharing | Open Graph link previews are set up correctly |
A jQuery plus WordPress plus LiteSpeed stack is exactly the profile a static Astro rebuild transforms. The same content, rebuilt as static pages, drops to a sub-1-second LCP, ships with no jQuery weight at all, and gets its schema baked in site-wide. The site looks identical to a visitor. It just loads instantly and reads cleanly to both Google and the AI engines.
07cWhat is broken or thin
A short, specific list. None of these are big rebuilds. Each is a known fix with a known result, ordered by what moves the needle most.
| Item | Status | What it means |
|---|---|---|
| sitemap.xml | Broken | Returns an HTTP 500 error. This is the top fix. A working sitemap is how Google and the AI engines find and trust every page. Right now that map is returning a server error, which quietly hampers crawl and AI discovery across the whole site. |
| Homepage schema | Missing | Zero schema on the homepage, no Person or Organization markup. You clearly know how to do schema well, the Person schema on /about is correct. It just is not applied site-wide, and the homepage is the page that matters most. |
| Consulting + coaching schema | Missing | The consulting and coaching pages, your money pages, carry no schema either. These are exactly the pages where structured data helps an AI understand what you sell. |
| Coaching page depth | Thin | Roughly 147 words. For a flagship offer page, that is too thin for Google or an AI to fully understand and recommend. The substance exists in your head and your podcast, it just is not on the page yet. |
The encouraging read here: every one of these is additive, not corrective. Nothing has to be torn out. The schema you already write well simply needs to spread to the rest of the site, and the sitemap needs to return a 200 instead of a 500.
07dSEO surface
Pulled live from DataForSEO Labs. The keyword footprint is genuinely large. The catch is in where all that ranking lands.
US ranking keywords
UK ranking keywords
Zero of the top 200 keywords point to a commercial page. Every single one of the strongest rankings is informational, all the theory content under /management/* (motivation theories, leadership styles, decision-making models). The site ranks for theory, not for buyers.
This is the most strategically important line in the whole audit. The site pulls strong traffic for people researching management concepts, students and the curious, but almost none of that ranking touches a page where someone hires a coach. The traffic is real. It is just pointed at the wrong rooms. That is a content-architecture fix, not a "you need more authority" problem, and it pairs directly with the AI surfacing gap from the AI Visibility page.
07eThe Astro case
A static Astro rebuild is the move that collapses most of this page into a single fix. In one rebuild it:
- Crushes the slow LCP and Speed Index by shipping static pages with no jQuery and no WordPress front-end weight, sub-1-second loads on mobile.
- Bakes schema in site-wide, so the homepage, consulting, and coaching pages all carry the structured data the AI engines read, automatically, on every page.
- Kills the sitemap 500 by generating a clean, always-valid sitemap as part of the build.
- Removes the jQuery and Migrate weight entirely, lighter, faster, and easier to keep secure.
The same content, the same look, but instant and clean to both Google and the AI engines. The phased version of this lives on the 90-Day Map, costed and sequenced so nothing breaks during the move.
A small note, no pressure attached: every fix on this page is something we do as routine. If any of it is useful to hand to whoever maintains the site, the list above is yours to take. That is the whole point of this showcase.