GOMAX ULTIMATE 5.42.0 adds a built-in Core Web Vitals auditor that reads your own rendered pages and your server environment, then returns a 0-100 performance score with each issue mapped to a specific vital and a concrete fix — without calling Google PageSpeed, Lighthouse, or any external service. It catches the front-end and server problems that actually move LCP, CLS and INP, and it does it entirely on your own site.
Most "speed test" tools send your URL to a cloud service, run one lab test, and hand you a number. That's useful occasionally, but it means your pages leave your server and you can't audit staging or members-only pages. GOMAX takes a different route: it analyses the same HTML a browser receives, plus your WordPress environment, locally.
Key takeaways
- Score pages and the site. Audit a single URL, post or path, or sample your key pages for an overall score and the issues that recur across the theme.
- Mapped to the vitals. Every finding is tied to LCP, CLS, INP or TTFB, so you know which metric you're improving.
- Front-end and server together. It checks markup (image dimensions, render-blocking assets, lazy loading, DOM size, fonts) and environment (page cache, object cache, PHP version, compression, autoloaded options).
- Concrete fixes. Each issue includes a plain fix — add width/height, defer head scripts, enable a page cache, upgrade PHP.
- No cloud, no hammering. No external PageSpeed/Lighthouse call and no third-party assets are fetched. Nothing leaves your server.
What it checks
On the front end, parsed straight from the rendered HTML:
-
Layout shift (CLS): images and iframes missing width/height (or an aspect-ratio), and web fonts loaded without
display=swap. -
Largest paint (LCP): render-blocking scripts in the `
withoutdefer/async, too many blocking stylesheets, below-the-fold images that aren't lazy-loaded, missingpreconnect` for third-party origins, and legacy JPG/PNG images that could be WebP/AVIF. - Interactivity (INP): an excessively large DOM and heavy inline CSS/JS.
On the server, read from your WordPress environment:
- Whether a page cache is active (it detects common caching plugins and cache drop-ins).
- Whether a persistent object cache (Redis/Memcached) is in use.
- Your PHP version, whether responses are gzip/brotli compressed, and how big your autoloaded options are (a common hidden cause of slow TTFB).
Why local and first-party is the right call
A single external lab score is easy to game and easy to misread. What reliably predicts good Core Web Vitals in the field is following the well-known best practices — reserving space for media, not blocking the first paint, caching, and a modern PHP. GOMAX audits exactly those signals from your own markup and environment, so you get an actionable checklist rather than one opaque number, and you can run it on any page including ones you'd never expose to a public tester. It fits a pay-once, privacy-first product: no per-scan metering, no data leaving the site.
From score to fixes
Because each issue names the vital it affects and the fix, the workflow is simple: run scan_site, look at the top recurring issues (they're usually theme- or plugin-level and fixing one helps every page), apply the fixes, and re-scan to confirm the score moved. Pair it with the built-in accessibility auditor and SEO tools and you're covering the three things search engines and users care about most — speed, accessibility and findability — from one plugin.
Frequently asked questions
Is this the same as a Google PageSpeed or Lighthouse score?
No. Those run a lab test in a headless browser and measure timings. This auditor checks the best-practice signals that predict Core Web Vitals from your HTML and server, without calling any external service. It's an actionable hygiene score, not a lab measurement — use both if you like.
Does scanning send my pages to a third party?
No. It fetches and analyses your own pages on your own server and reads your WordPress environment locally. No external performance API is used and no third-party assets are downloaded.
Which issues should I fix first?
Start with the "serious" ones — render-blocking head scripts, missing image dimensions, and no page cache — and with any issue that appears on many pages in a site scan, since those are usually theme- or plugin-level and fixing them helps everywhere.
Will it tell me if my caching or PHP is the problem?
Yes. retrieve_server_health (and every page scan) reports whether a page cache and object cache are active, your PHP version, whether compression is on, and how large your autoloaded options are — common server-side causes of slow response times.
Can I track improvements over time?
Yes. Every scan is scored and stored, so list_scan_history shows the trend as you apply fixes.
