Controlled WordPress Core Web Vitals lab: slow and fixed builds

Inspect the fixed implementation, not a screenshot claim

The clean WordPress implementation, dummy content, custom theme, setup script, and safe lab notes are public. The deliberately overloaded source remains private because it contains fault-injection code; the observable slow routes remain available for comparison.

What stayed the same

• the same dummy business and core route structure;
• the same page purpose, section order, and content pattern;
• the same hero source subject, reviews, gallery, FAQ, testimonials, and post-grid pattern;
• no client data, contact form, payment flow, or visitor tracking.

What the fixed build changes

• removes artificial origin delay and the no-store fault injector;
• removes parser-blocking JavaScript and deliberate long main-thread tasks;
• serves responsive WebP derivatives from the same hero source;
• restores image dimensions and below-fold lazy loading;
• replaces an automatically loaded chat widget with a click-opened static stub;
• removes late layout-shift injections and unnecessary global DOM/widget bloat;
• uses stable file-based asset versions and a system font stack.

Compare like with like

• test the matching slow and fixed route in the same tool, browser mode, region, and time window;
• record cache state and repeat both cold and warm requests where server response is relevant;
• save raw Lighthouse or PageSpeed JSON before quoting a number;
• compare the LCP element, request priority, main-thread work, layout shifts, transfer path, and cache response—not only an aggregate score;
• treat the 28-day field dataset as separate evidence from a current lab trace.

What this controlled lab does not prove

Hosting, network, browser, cache, and dependency state can change a live demo. The lab does not prove a historical score, a field Core Web Vitals pass, a ranking or traffic change, a client outcome, or the result another production site will achieve. Production WordPress sites also carry consent tools, analytics, ads, ecommerce behavior, third-party widgets, editorial constraints, and rollback requirements that this dummy lab does not reproduce.

Inventory the assets loaded by selected WordPress pages

IndexLane Core Web Vitals Asset Snapshot lists scripts, styles, WordPress plugin/theme asset paths, and third-party domains found in selected same-site HTML. It exports evidence; it does not run Lighthouse, calculate Core Web Vitals, or change the site.