Full-page caching is disabled and OPcache is not enabled, creating the primary bottleneck that compounds database autoloading and backend plugin overhead to severely elevate time to first byte. Enable full-page caching first. Full view →
Activate server-side full-page caching to cache entire HTML responses and eliminate redundant processing on every request. This is the single highest-impact fix: it reduces TTFB by removing per-request database and plugin overhead entirely for cached pages.
6 fixes, ranked by impact. Each is independently reversible.
Activate server-side full-page caching to cache entire HTML responses and eliminate redundant processing on every request. This is the single highest-impact fix: it reduces TTFB by removing per-request database and plugin overhead entirely for cached pages.
Enable OPcache to cache compiled PHP bytecode in memory, eliminating the need to recompile PHP files on every request. This reduces CPU load and latency for all PHP execution.
Activate gzip or brotli compression on the web server to compress HTTP responses, reducing payload size by 60–80% for text assets (HTML, CSS, JS, JSON).
Clean up and optimize WordPress options to reduce in-memory overhead from 1 MB to under 900 KB. Autoloaded options are queried on every page request regardless of whether they are used, so reducing this directly decreases TTFB.
Reduce the 53 active plugins to fewer than 30 by auditing each one for necessity and performance impact. Each plugin adds PHP execution time, database queries, and memory usage. Fewer plugins directly reduce TTFB and improve stability.
Reduce the 49 loaded JavaScript files and convert 5 render-blocking scripts in <head> to async/defer attributes. This allows the page to paint sooner and reduces Largest Contentful Paint (LCP) and First Input Delay (FID).
Click any row to expand evidence, fix steps, and references.
Full-page caching is disabled, forcing the server to execute PHP, load plugins, and query the database on every single request. This is the primary root cause of elevated time to first byte and prevents any downstream performance optimization from being effective. Every request incurs the full cost of WordPress initialization and theme rendering.
PHP OPcache (opcode cache) is not active, forcing the PHP interpreter to recompile every PHP file on every request. With 53 active plugins and complex WordPress core, this results in significant CPU overhead and latency. OPcache caches the compiled bytecode in memory, eliminating recompilation.
Only 21% of images on the site use modern, efficient formats (WebP or AVIF). The majority of images are likely in JPEG or PNG format, which are significantly larger than modern equivalents. This increases payload size and page load time, especially on mobile networks.
HTTP response compression (gzip/brotli) is not enabled on the web server, forcing clients to download uncompressed HTML, CSS, JavaScript, and JSON payloads. Text assets typically compress 60–80%, so disabling compression significantly increases bandwidth and perceived latency.
The site has 53 active plugins, each of which adds PHP execution time, database queries, and memory overhead on every request. This is above the commonly recommended threshold of < 30 plugins and creates a compounding performance penalty. Plugin overhead is especially problematic before caching is enabled, as each plugin code is executed fresh on every uncached request.
Two ways to keep moving the score up
7 audits · since Apr 2026
Our WordPress performance team can apply every fix in this report, run a deeper hands-on audit, and verify Core Web Vitals afterwards — no plugins or guesswork on your end.
Replies within 1 business day · No commitment