WordPress Performance: Hitting 99 PageSpeed Without Cutting Corners

How to hit 99 PageSpeed on WordPress in 2026 — without breaking design, without sacrificing plugins, and without the snake oil.

The honest baseline

A modern WordPress site, properly built, hits 95+ on mobile PageSpeed in 2026. If yours scores 40, the problem is almost never WordPress — it is page builders shipping 600KB of JavaScript per page, eight competing caching plugins, and a theme that loads jQuery in 2026.

Hosting is the first lever

Managed hosting on PHP 8.3+ with OPcache, HTTP/3, and a CDN included. Kinsta, WP Engine, Cloudways, Pressable — pick one and stop fighting with shared hosting. The hosting upgrade alone moves PageSpeed by 15–25 points on most audits I run.

Caching done correctly

Server-level page cache (LiteSpeed, NGINX FastCGI, or the host's built-in). One — and only one — caching plugin if the host does not include it. Object cache (Redis) for query-heavy sites. Browser cache headers set correctly for static assets. That is the entire caching stack.

Asset optimisation

Convert all raster images to AVIF or WebP. Specify width and height on every img. Lazy-load below-the-fold images natively (loading='lazy'). Defer non-critical JavaScript. Inline critical CSS, async-load the rest. Audit fonts — most sites load four weights they never use.

The plugin audit

Quarterly: list every active plugin, score it on value vs performance cost, remove anything that no longer earns its place. Most WordPress sites I audit carry 6–10 plugins they could delete tomorrow with zero functional loss.