Why Is This Page Slow — WordPress & Elementor diagnosis
Unknown author · Developer Tools
Media
3 items
Description
Reloads the page, measures it from navigation, and names the actual cause of the delay. No score. Built for WordPress and Elementor. Stop guessing why your WordPress page is slow. Find the actual bottleneck. Most performance tools hand you a score and a list of file names. A score tells you that something is wrong. It doesn't tell you which widget put a 84 KB stylesheet in front of your hero image. This extension does one thing: it reloads the page, measures the load from the moment navigation starts, and tells you where the time actually went — in the language of the page builder you're using. WHAT YOU GET Every finding is built the same way: Evidence — what was measured, with file names and sizes Mechanism — why that costs time, in one sentence Saving — how much it is worth on this page, derived from the measurement rather than a rule of thumb Fix — the setting or the markup change that removes it WHAT IT LOOKS AT • LCP, split into server response, resource discovery, download and render, so you can see which phase the time died in • Render-blocking CSS and JavaScript, grouped by the plugin or theme that queued it • Images served far larger than they are displayed • Third-party scripts holding the main thread, with per-script attribution • Layout shifts, including telling font swap apart from late-rendering content — the two need opposite fixes • Elementor asset loading and which widget types the page actually uses MEASUREMENT YOU CAN DEFEND • It reloads the page, because real performance starts at navigation. A tool that measures after load is describing the page you already have, not the one your visitor waits for. • It measures a first visit by default, ignoring the cache. Switch it off to see what a returning visitor gets. • It runs three loads and reports the median, with the range shown. One load is a sample, not a fact. • No score. Findings are ranked by what they cost on this page. If nothing costs measurable time, it says so instead of inventing a problem. PRIVACY • No account, no server, no analytics. • Nothing leaves your browser. Measurements are stored locally and cleared when the tab closes. • Site access is asked for one domain at a time, only when you press Diagnose. Built for WordPress and Elementor sites. It works on any page, but the attribution layer — naming the plugin, theme or widget behind a finding — is where the value is, and that is WordPress-specific today.