WordPress performance wizard

Start with the page URL

Ready

Analyze a WordPress page

Scan the page, review the detected tech stack, then fix only the main image speed problem (LCP) first.

Backend status is being checked...

Main image speed scan (LCP)

WordPress stack detection can work without a key. PageSpeed scores and main image speed evidence (LCP audit evidence) require a PageSpeed API key when the public quota is exhausted.

Open PageSpeed Insights

Scan Summary

Mobile -
Desktop -
Main image speed (LCP) - The biggest image or hero area customers see first.
Page movement (CLS) - How much the page jumps while loading.
JavaScript delay (TBT) - How long scripts block taps and clicks.
No scan run yet.

Main Image Speed Findings (LCP)

PageSpeed-matched main image speed findings (LCP) will appear here after a full scan.

  • Run a scan or use the manual main image speed picker (LCP) in step 3.

Tech Stack Verdict

Run a scan to detect the cache plugin, host, theme, builder, image optimizer, and CDN.

No stack scanned yet

The tool will rate the detected combination after the scan finishes.

Confirm the WordPress setup

The same PageSpeed warning needs different steps depending on plugins, builder, hosting, and CDN. The Stack Advisor below shows host/plugin recommendations live.

Safety access

Stack Advisor

Recommendations update from your selected host, cache plugin, builder, CDN, and image optimizer.

Pick the main image speed issue to fix (LCP)

Start with one main image speed fix, test it, then loop through the next adjustment only if needed.

Run PageSpeed Insights, open the mobile report, copy one warning, and paste it here.

Issue-specific questions

Answer these so the fix plan can avoid generic advice.

Fix plan

Follow the steps in order and run the QA checks before changing another setting.

Customer copy

Generate the fix plan first.