All fix guides

Page speed (A-psi)

PageSpeed performance (mobile)

What this check means

This guide helps you act on one scan finding. It is not legal advice or a compliance verdict.

What to fix

Raise the mobile PageSpeed lab score by cutting render-blocking theme/plugin CSS and JavaScript on the scanned URL.

Step-by-step fix

  1. In WordPress admin, open the scanned page template (theme customizer, Elementor/builder, or page editor) and note above-the-fold media plus plugins that inject CSS/JS on every view.
  2. Defer or remove non-critical scripts: tag managers that are not needed on this URL, chat widgets, and unused page-builder widgets. Prefer one optimization plugin path (for example WP Rocket or LiteSpeed) — do not stack two full optimizers.
  3. Compress and size the hero image for mobile (WebP/AVIF when the host supports it) and set explicit width/height so the lab run is not blocked on a giant asset.
  4. Purge page cache / CDN cache for the URL, then wait for the edge to settle before the next scan.

Choose the path for your setup

  • WP Rocket / LiteSpeed / similar

    Enable Delay JS / defer CSS only for this template after a staging check. Exclude critical checkout or form scripts from delay.

  • Elementor / page builder

    Replace background videos and large carousels on the mobile template; load secondary sections on interaction when the builder supports it.

Confirm it is fixed

Run a free leak scan on the same URL and compare the mobile PageSpeed check (A-psi) to the prior report. The lab score should move in the direction you expect under the same bot conditions.

Rescan this check on your site

Scan the same URL again, then compare this check with your previous report.

Run a free leak scan