Speed audit
Fetch your busiest pages and see exactly which files are slowing them down — named files, real sizes, and which plugin shipped them.
Speed audit
Visibility Flux → AI Visibility → Speed fetches your pages and reports what is actually slowing them, by name.
Most speed tools hand you a score and a list of abstractions. A score does not tell you which plugin to deactivate. This audit names the file, its size, where it came from, and what to do about it.
No API key. No third-party service. Visibility Flux requests your own pages the way a visitor does and reads what comes back.
Choosing what to analyse
Pick how many pages to check — 5, 10, 20, 50 or 100 — from the selector above the button. The default is 20.
Visibility Flux analyses your busiest pages first, taken from your Search Console import, so the audit covers the pages where speed actually costs you traffic. Without an import it falls back to your most recent content.
Each page is a real HTTP request, so more pages take longer. Twenty is a good balance; raise it when you want coverage rather than a spot check.
What it finds
Server response time
How long your server took before it returned anything. Everything else waits on this, so a slow figure here caps every other improvement. Usually hosting, a heavy plugin, or a missing page cache.
The main image
The largest image on screen is almost always what the reader is waiting for, and it is the most commonly misconfigured thing on a WordPress page:
- Set to load lazily — the single most damaging speed mistake on WordPress. Lazy loading is right for images below the fold and wrong for the one at the top: it tells the browser to delay the exact thing being measured
- No priority hint — the browser has not been told this image matters most
- Heavy — oversized for the space it occupies
- Not WebP or AVIF — still JPEG or PNG, typically two to three times larger than needed
Images with no width and height
An image without dimensions makes the page jump as it loads, which is a poor experience and a direct ranking signal. Visibility Flux counts them and names the pages.
Render-blocking files in the head
CSS and JavaScript in the <head> that the browser must download and process before it
can paint anything. Visibility Flux lists each file, its size, and — the useful part — which
plugin, theme or third party shipped it, so you know whose setting to change or what to
deactivate.
JavaScript weight
Total JavaScript the page carries, and how many separate outside domains it comes from. Scripts from many domains mean many DNS lookups and connections before anything runs.
Webfonts that hide text
Fonts loaded so that text stays invisible while they download. Readers see blank space where
your words should be. A one-line font-display change fixes it.
Reading the results
Pages are listed worst first, with build time and JavaScript weight summarised per row, and the specific findings underneath. Results paginate five pages at a time, because each row carries a lot of detail.
Everything is deterministic: run it twice on an unchanged site and you get the same answer.
What this is not
This is a diagnostic of your own markup and assets, not a lab measurement. It does not report Core Web Vitals scores from Google's field data, and it does not simulate a particular device or connection.
What it does instead is tell you which file to change. A score tells you that you have a problem; this tells you which one.