The Ultimate Guide

How to Speed Up Your WordPress Website

A comprehensive, battle-tested guide covering TTFB optimization, image compression, caching strategies, JavaScript delay techniques, font optimization, and 200+ free tools and plugins to achieve 90+ mobile PageSpeed scores.

2026 Edition · 200+ Free Tools · Step-by-Step Optimization

Table of Contents

Why Page Speed Matters

Speed Testing Fundamentals

Understanding TTFB

Waterfall Chart Analysis & Inferences

Common Misconceptions

Security Without Sacrificing Speed

Image Optimization

JavaScript & CSS Optimization

Font Optimization

Caching Strategy

Theme & Page Builder Selection

Database Optimization

Third-Party Files & Local Hosting

Server & Network Optimization

Video & Media Optimization

The Complete Optimization Toolkit

Chapter 01

Why Page Speed Matters

Page speed directly influences conversions, bounce rate, time on page, Google search engine rankings, user experience, and revenue. For e-commerce sites, improving page speed increases sales, reduces the number of abandoned carts, and increases the percentage of users who complete the checkout process. Performance optimization is one of the most important things you can do to improve a website.

The Business Case for Speed

Multiple authoritative studies have confirmed the direct link between page speed and business metrics:

Google's Core Web Vitals study documented the direct business impact of page speed improvements across hundreds of sites.

Deloitte's "Milliseconds Make Millions" report provides a thorough analysis of how page speed improvements impact business revenue, showing that even 100ms improvements translate to measurable gains.

Conductor's research compiled case studies demonstrating improvements in conversion rates, bounce rates, and engagement metrics after speed optimizations.

Google Ranks by Mobile Speed Only

Whether the majority of your site's traffic is desktop or mobile is irrelevant to how Google ranks your webpage. Google does not care about desktop performance when they rank a website. Over 80% of traffic on the internet comes from mobile devices, and Google calculates their rankings accordingly. Even if your website's users browse primarily from desktop devices, your mobile score is the only one that will be considered as a ranking factor.

Beyond SEO: Customer Retention

While the primary motivation for improving page speed is often better SEO rankings, an often overlooked factor is customer retention. Reducing your bounce rate from 60% to 30% can result in significantly higher revenue and conversions, more sales, and improvements in actions like contact form fill-outs. The benefits of enhanced visitor engagement extend far beyond just attracting more visitors.

Key Takeaway

Page speed affects everything: SEO rankings, conversions, bounce rate, user experience, and revenue. Mobile performance is the only metric Google uses for ranking.

Chapter 02

Speed Testing Fundamentals

Mobile Scores Are the Only Scores That Matter

Desktop scores have almost zero diagnostic value. In fact, their only value is as a reverse metric: poor desktop scores indicate a massive amount of performance issues. Good desktop scores indicate nothing about how well a website is optimized.

The reasons mobile scores are all that matters:

Improving mobile inherently improves desktop — the sources of pagespeed issues (CSS, JS, unoptimized images) are universal across devices.

Performance issues hit harder on mobile — a sub-1-second desktop load can be 2-6 seconds on mobile.

Mobile tests simulate worst-case conditions — using a simulated Moto G Power on a throttled connection.

Google ranks by mobile speed exclusively — regardless of your traffic split.

Warning

The vast majority of sites screenshotting high scores in the 90s are displaying desktop performance scores. Anyone displaying desktop scores is being deceptive. Always verify mobile scores.

Which Speed Tests to Use

Google PageSpeed Insights (Free)

https://pagespeed.web.dev/

The end-all-be-all for mobile tests. You need to satisfy Google's speed tests for SEO. Other sites may offer mobile tests, but the only company you need to satisfy is Google.

Debug Bear (Free)

https://www.debugbear.com/test/website-speed

Use Debug Bear to diagnose issues, but PageSpeed Insights to gauge how much farther you need to go. Debug Bear is superior for mobile diagnosis because it provides waterfall charts showing load times for specific files, plus a list of all CSS and JS files loading on the page.

ByteCheck (Free)

https://www.bytecheck.com/

The best tool for TTFB analysis. Breaks TTFB into its 6 constituent components: DNS, Connect, SSL, Send, Wait, Receive.

GTMetrix (Free)

Useful for desktop waterfall chart analysis. Shows page weight and number of requests at the bottom of the waterfall.

Testing Best Practices

Average 3 tests — your true scores are best measured as an average of multiple tests.

Optimize for lab data — lab data (synthetic tests) are the only scores you can actually optimize for. Field data is collected over 30 days and has no diagnostic utility.

You do not need paid speed testing plans — everything needed to optimize a site can be gleaned from free speed tests.

Target

Any site you optimize should ideally have a mobile score of 90+ on PageSpeed Insights. For the vast majority of sites, this is easily achievable once you implement the steps in this guide.

Chapter 03

Understanding TTFB

Time to First Byte (TTFB) has 6 components, each of which can be individually optimized:

1. DNS

The time taken to query and receive a response from a DNS server with the IP address of the domain. If the DNS response is not cached locally, this adds significant time to TTFB.

Optimization: Use a fast DNS provider with DNS caching such as Cloudflare. Even if you don't use them as a CDN, Cloudflare is an excellent DNS provider.

2. Connect

The time to perform the TCP handshake — SYN and ACK packets between client and server.

Optimization: Optimize TCP settings including the initial congestion window, keep-alive settings, and client request handling.

3. SSL

The SSL/TLS handshake time for authentication and encryption negotiation.

Optimization: Use TLS 1.3 (newest and most performant). Implement faster cipher suites, TLS False Start, and Session Resumption.

4. Sending

The time to send the first byte of the response from server to client after processing.

Optimization: Enable Brotli or GZIP compression. Optimize server configuration (NGINX/LiteSpeed worker processes, keep-alive). Use HTTP/2 or HTTP/3 for multiplexing.

5. Waiting (Server Processing)

The time for the server to process the request — running scripts, querying databases, generating the response.

Optimization: Optimize WordPress at the application level. Reduce inline JavaScript, HTML weight, CSS. Optimize your DOM size and database queries.

6. Receiving

The time for the client to receive the first byte of data.

Optimization: Reduce server response size. Deliver only essential resources for initial render. Use HTTP/2 or HTTP/3. Deploy a CDN to reduce physical distance.

TTFB Targets

Desktop: Under 300ms. Mobile: Under 500ms. If your desktop TTFB exceeds 300ms or mobile exceeds 500ms, you likely have unimplemented optimization opportunities remaining.

Chapter 04

Waterfall Chart Analysis & Inferences

Performance optimization requires inferences. No external tool will identify all issues — you must make conclusions through interpretation of the waterfall chart.

Key Metrics to Analyze

Page weight — visible at the bottom of GTMetrix waterfall charts. Ideal target: under 500 KB. Top-performing sites achieve 150-200 KB.

Number of requests — every additional request adds latency, even tiny ones. Under 40 requests is the sweet spot.

JavaScript files — the prime targets for optimization. Each JS file is parser-blocking and adds blocking time.

Image files — check if lazy loaded, check file sizes, check formats (WebP/AVIF vs PNG/JPG).

Third-party requests — any files not served from your domain introduce additional latency.

What to Look For

Font Awesome libraries — often load 77+ KB of icon fonts when you may only use a few icons. Replace with individual SVGs.

Images not lazy loaded — images below the fold loading in the initial request wastes page weight.

Bloated HTML document — anything over 50 KB should be considered large. Check for excessive inlined CSS, JavaScript, and SVGs.

Cache plugin identification — look for references like "nowprocket" (WP Rocket) in the HTML body.

CDN and compression — verify Brotli/GZIP is active and files are served from cache.

HTTP protocol — check if resources are served over HTTP/2 or HTTP/3.

Redirect chains — ensure there's no intermediary HTTP > HTTPS > HTTPS://WWW redirect.

Preloaded resources — verify the LCP image is preloaded. Avoid preloading too many resources.

Pro Tip

Use BuiltWith to identify plugins and services that can't be detected from the waterfall chart alone, such as analytics tools and specific WordPress plugins.

Chapter 05

Common Misconceptions

"PageSpeed Lab Scores Don't Matter"

They absolutely do. Lab scores are the metrics you optimize for because speed tests can only measure synthetic data under controlled conditions. Improvements in lab scores directly translate to real-world performance improvements.

"Page Builders Can't Be Fast"

A half truth. Any page builder will be slow without optimization, including "lightweight" ones like Bricks and Oxygen. Once optimized, even Elementor can easily achieve scores over 90 on mobile PageSpeed Insights.

"Server Caching Replaces WordPress Caching Plugins"

Incorrect. They are complementary layers. WordPress-level caching provides optimized HTML generation, granular control, reduced backend load, improved TTFB, and cache warming — benefits that server-level caching alone cannot provide.

"A Bloated DOM Kills Performance"

Another half truth. A bloated DOM combined with a large HTML document weight will hurt performance. But your DOM can be large if your document weight is low. A page with 1500 or even 2000 DOM elements can render quickly if the HTML document weight stays low.

"Too Many Plugins Slow You Down"

There is no such thing as "too many" plugins. A plugin is simply bundled code. What matters is the quality and weight of each plugin. A properly optimized site can run 90 plugins simultaneously without performance issues. Only debug and analysis plugins should be deactivated when not needed.

"Security Plugins Are Required on Live Sites"

Wordfence can drop your mobile score by 10-15 points. Use it only on staging for malware scanning. On live sites, use lightweight firewalls at multiple layers instead.

"PageSpeed Only Affects SEO"

While SEO is the primary motivation, customer retention is equally important. Reducing bounce rate from 60% to 30% through speed improvements can result in significantly higher revenue.

Chapter 06

Security Without Sacrificing Speed

Security and performance are a trade-off that must be carefully evaluated. The key is implementing security at the right layers with lightweight tools.

Three-Layer Firewall Approach

WAF Level (Network) — Cloudflare WAF, BunkerWeb (free, self-hosted), or NGINX App Protect WAF. Blocks malicious traffic before it reaches your server.

Server Level — 7G Firewall for NGINX or 8G Firewall for Apache by Jeff Starr. Performant rule-based firewalls.

Application Level (WordPress) — BBQ Firewall or Ninja Firewall. Lightweight last line of defense.

Essential Security Measures

Disable XML-RPC — prevents DDoS amplification and brute force attacks. Use Asset Cleanup or the Simple Disable XML-RPC plugin.

Limit login attempts — Limit Login Attempts Reloaded restricts login attempts across standard login, XMLRPC, WooCommerce, and custom login pages.

Virtual patching — Patchstack applies virtual patches to vulnerable plugins before developers release updates.

Security headers — target an A grade on securityheaders.com. Use the Headers Security Advanced & HSTS WP plugin.

Two-factor authentication — Two Factor (official WP core team plugin) or Fluent Auth. Both lightweight.

Audit logging — CoreActivity Log (most comprehensive) or Stream (entirely free).

Avoid on Live Sites

Do not use Wordfence on your live site. It's extremely bulky and detrimental to performance. Use it only on staging for malware scanning.

Chapter 07

Image Optimization

Images are typically the largest files on any page and represent the biggest optimization opportunity. A 300-400 KB weight difference can mean the difference between a score in the low 80s vs the high 90s.

Manual Compression Strategy

Always compress images through multiple passes until quality degrades beyond acceptable levels. Bounce images between services:

Example workflow: TinyPNG > TinyPNG > TinyPNG > TinyJPG > TinyJPG > 11zon > TinyPNG > 11zon > TinyJPG

Even once a service exhausts its ability to compress further, switching to another service often allows further compression. Converting between formats also unlocks additional compression.

Free Compression Services

TinyPNG (tinypng.com) — unique multi-pass capability. Always do 3+ passes.

TinyJPG (tinyjpg.com) — slightly different algorithm from TinyPNG.

11zon (imagecompressor.11zon.com) — complements TinyPNG/TinyJPG.

Compress-or-Die (compress-or-die.com) — advanced compression options.

Batch Compress (batchcompress.com) — converts PNG to JPG (loses transparency).

WordPress Image Plugins

ShortPixel (Freemium) — best overall image optimizer per ThemeIsle's comparison tests.

Smush (Free/Premium) — generous free tier with unlimited images under 5 MB.

Flying Images (Free) — compression, WebP, lazyload, and free image CDN.

Converter for Media (Free) — auto-converts images to WebP, fully local.

CompressX (Free) — WebP and AVIF conversion, done locally.

Lazy Loading

Lazy loading prevents images below the fold from loading until they enter the viewport, dramatically reducing initial page weight.

Exclude above-the-fold images from lazy loading — this is critical.

Use Perfmatters, Flying Images, or a3 Lazy Load.

Auto-sizes plugin implements sizes="auto" for lazy-loaded images.

Fix CLS Issues

Add missing width and height attributes to all images. Use Perfmatters, FlyingPress, or the free Specify Missing Image Dimensions plugin.

SVG Icon Optimization

Replace Font Awesome libraries with individual SVG files. Font Awesome loads thousands of icons (77+ KB) when you may only need a handful. Compress SVGs with Vecta.io + SVGOMG together.

Target

Compressed images should ideally be under 100 KB each. Start with high-quality originals and compress through multiple passes across multiple services.

Chapter 08

JavaScript & CSS Optimization

JavaScript Strategy

JavaScript files are parser-blocking and add to the Blocking Time metric. Every additional request, even tiny ones, adds latency.

Delay All Non-Critical JavaScript

Delaying JavaScript completely negates its pagespeed impact. Delayed files don't download until user interaction. The page loads instantaneously, and the user experiences no visible delay when delayed JavaScript finally loads.

WP Core Files That Can Be Delayed or Removed

wp-polyfill.min.js — fallback for old browsers (Internet Explorer). Safe to delay/remove.

regenerator-runtime.min.js — unneeded in most cases.

i18n.min.js — translation functionality. Safe to delay if not multilingual. Console errors are ignorable.

hooks.min.js — many plugins depend on it but don't need it immediately. Delay, don't remove.

imagesloaded.min.js — usually safe to delay. Test with sliders.

Selectively Disable Plugins Per Page

Use Asset Cleanup Pro or Freesoul Deactivate Plugins (free) to prevent plugins from loading on pages where they aren't needed.

CSS Strategy

Remove Unused CSS

Use Debloat (free), FlyingPress (paid), or Perfmatters (paid) to strip CSS not used on each page. You'll need to add exclusions for CSS that's dynamically needed.

Inline Critical CSS

Embed only essential CSS in the HTML document. For Elementor, enable the Internal Embedding CSS Print Method to inline post-xxxx.css files.

Target

HTML document weight should be under 50 KB. Anything larger has a noticeable detrimental effect on performance. Zero JavaScript requests in the initial waterfall is the ideal state.

Chapter 09

Font Optimization

Fonts are heavy files, and loading them from Google's CDN introduces additional latency from external HTTP requests. Every single external call adds lag.

Best Practices

Use WOFF2 format — best compression and broadest browser support.

Host fonts locally — eliminates external calls to fonts.gstatic.com.

Subset your fonts — strip unused characters. Can reduce font size by 80-90%.

Replace icon font libraries with individual SVGs — Font Awesome loads the entire icon set for a few icons.

Preload critical fonts — fonts used above the fold should be preloaded.

Consolidate font families and weights — minimize the number of font files.

Local Font Hosting Plugins

Yabe Webfont (Free) — best plugin for locally hosting Google Fonts. Supports variable fonts, Adobe Fonts, and custom fonts.

OMGF (Free) — auto-hosts Google Fonts locally.

FlyingPress (Paid) — can locally host Google Fonts but can't serve manually uploaded fonts.

Font Subsetting Tools

Font Squirrel (fontsquirrel.com) — granular web font generator. Can significantly reduce font file sizes.

Everything Fonts Subsetter (everythingfonts.com/subsetter)

Glyphhanger — CLI tool for subsetting and optimizing fonts.

FontForge (Free) — remove unnecessary glyphs to reduce font sizes by 80-90%.

Pro Tip

Download Google Fonts locally using Google Fonts Web Helper (gwfh.mranftl.com/fonts), then run them through Font Squirrel's web font generator for maximum compression.

Chapter 10

Caching Strategy

A common misconception is that server-level caching replaces WordPress caching plugins. In reality, they create a powerful multi-tiered system when used together.

How the Layers Interact

First Request

User request → Web server (cache miss) → WordPress (cache miss) → WordPress dynamically generates page → WP caching plugin saves static HTML → Server receives and caches static HTML.

Subsequent Requests

User request → Web server (cache hit) → Static HTML served from server cache.

If Server Cache Misses

User request → Web server (cache miss) → WordPress (cache hit) → WordPress serves cached HTML → Server caches it.

WordPress Caching Plugins

FlyingPress (Paid) — best overall results. Recently added local hosting of third-party CSS/JS.

Speed Booster Pack (Free) — great free alternative.

WP Rocket (Paid) — solid despite its flaws. One of the most performant caching plugins.

Object Caching

Docket Cache (Free) — WordPress-level object cache. Often outperforms Redis. Works on shared hosting.

Redis (Free) — server-level object cache. Requires VPS/hosting provider support. Use Redis Object Cache plugin as connector.

Why WordPress Caching Plugins Are Necessary

Optimized HTML generation — removes unnecessary characters, comments, whitespace.

Granular control — specific rules for logged-in users, e-commerce pages, dynamic content.

Reduced backend load — fewer database queries and PHP executions.

Improved TTFB — serves static HTML directly from the WordPress layer.

Cache warming — pre-caches pages for the fastest possible response.

Chapter 11

Theme & Page Builder Selection

Your Theme Is Slowing You Down

If you use a page builder, themes are dead weight. They add nothing to the design since all CSS and JS is generated by the builder. Astra, for example, inserts hundreds of KB of unnecessary code that intermixes with your builder's CSS, creating dependency chains that prevent removal without breaking the site.

Recommended Themes

Hello Elementor (Free) — ultra-lightweight barebones theme. The entire plugin zip is 3x smaller than alternatives.

Picostrap (Free) — very lightweight. Pairs perfectly with LiveCanvas.

Page Builders Ranked

Oxygen Builder (Paid) — clean, optimized code. Minimal unnecessary div tags, reducing DOM bloat.

Bricks Builder (Paid) — well-optimized, outputs clean code.

LiveCanvas (Paid) — outputs clean Bootstrap 5 HTML5 with a built-in live code editor. Extremely lightweight.

Elementor (Freemium) — bloated pre-optimization but becomes one of the lightest builders post-optimization. Can easily achieve 90+ mobile scores in 20 minutes.

Builders to Avoid

WPBakery — extremely problematic. Just don't.

Beaver Builder — poorly optimized. Native shape dividers bloat HTML by 135+ KB per section. Cannot be removed with Remove Unused CSS.

Divi — extremely bloated with unremovable cruft.

Elementor Optimization Tips

Enable all Performance Experiments in Settings > Features.

Use Internal Embedding CSS Print Method to inline post CSS files.

Limit use of containers, sections, and columns — each adds DOM elements.

Don't set background images on unconventional elements (spacers, etc.).

Use Pro Elements (free, proelements.org) for all Elementor Pro features.

Theme Warning

Avoid Astra for new builds. It adds over 300 KB of JS/CSS, and delaying its JS breaks headers and menus due to dependency chains.

Chapter 12

Database Optimization

A poorly optimized database causes high CPU load, excessive RAM pressure, and slow TTFB. Low TTFB is a strong indicator of a well-optimized database.

Reduce Autoloaded Options

Many plugins set options to autoload even when unnecessary. This slows every page load.

Sweeppress (Free) — modify or delete autoload options.

AAA Option Optimizer (Free) — another autoload optimization plugin.

Caution

Disabling the wrong autoload option can lock you out of the backend. Always test on staging first and have backups ready.

Object Caching

Docket Cache (Free) — WordPress-level object cache. Can outperform Redis in many cases. Works when you can't install Redis.

Redis (Free) — server-level object cache. Use with Redis Object Cache plugin.

MySQL Tuning

MySQLTuner (Free) — Perl script that reviews your MySQL installation and suggests adjustments. Supports ~300 indicators.

Releem (Paid) — auto-tunes MySQL configuration based on current and average load.

Index WP MySQL For Speed (Free) — adds proper indexes to WordPress database tables.

Query Analysis

Query Monitor (Free) — debug database queries, PHP errors, hooks, enqueued scripts. Shows query time per caller and identifies duplicate queries. Total query time should be under 0.04 seconds.

Fluent Query Logger (Free) — selective query logging.

Database Cleanup

Advanced Database Cleaner (Free/Pro) — clean orphaned tables, options, and entries left by deleted plugins.

Enable Database Tools (Free) — enables InnoDB and MyISAM table optimization using WordPress built-in tools.

Chapter 13

Third-Party Files & Local Hosting

You should always host every file you possibly can on your server locally. Third-party files (anything not served from your domain) always load slower due to additional DNS lookups and connection overhead.

Host Everything Locally

Google Analytics — use CAOS (Complete Analytics Optimization Suite) to download and serve analytics files locally.

Google Fonts — use Yabe Webfont or OMGF to self-host.

Third-party CSS/JS — use GDPR Cache Scripts and Styles plugin or FlyingPress to locally cache external files.

Images from external domains — download and host locally.

Resource Hints

When you absolutely cannot host files locally, use resource hints to improve connection speed:

Pre-Party (Free) — adds DNS prefetch, prerender, preconnect, prefetch, and preload hints.

HTTP/2 Server Push — more powerful than resource hints because the server pushes resources before the browser requests them.

YouTube Optimization

Normal YouTube implementations severely impact site speed. Use lightweight YouTube players with placeholder images that prevent the video from downloading until the user clicks play. Delay the player's JS file for videos below the fold.

Pro Tip

Check your GTMetrix waterfall for any domain that isn't yours. Every third-party call introduces latency. Eliminate as many as possible.

Chapter 14

Server & Network Optimization

Fix Redirect Chains

Your site should have a single redirect: http://domain.com → https://domain.com (or https://www.domain.com). Never have intermediary redirects like http → https → https://www. Implement via server config or CDN (Cloudflare redirect rules) for lowest latency.

Disable WP-Cron, Use Server Cron

WP-Cron fires on every page load, adding overhead. Replace it with a proper server-side cron job. Use free generators: Cronhub (crontab.cronhub.io), Crontab Guru (crontab.guru), or Crontab Generator (crontab-generator.org).

Control the Heartbeat API

Too many WP-Admin tabs open simultaneously can cause excessive CPU and RAM usage. Use Dynamic Frontend Heartbeat Control (free) to automatically optimize heartbeat intervals.

Performance Monitoring

New Relic (Free open-source projects) — invaluable for observability into performance issues. Monitors all aspects of your web stack. Only activate when diagnosing issues to avoid performance overhead.

SigNoz (Free self-hosted) — good alternative to New Relic. Self-hostable open source community version.

WP-Config Settings

Set the memory limit in wp-config.php:

define( 'WP_MEMORY_LIMIT', '256M' );

Do not exceed 512M. If a plugin needs more, switch plugins.

Cloud Autoscaling

For high-traffic sites, cloud VPS providers offer auto-scaling that automatically upgrades and downgrades server resources based on load. This is a necessity for high-traffic sites.

Chapter 15

Video & Media Optimization

Video Compression

Handbrake (Free) — open source installable program for video compression.

Convert to WebM — WebM files are ~30% smaller than MP4. Handbrake supports WebM conversion.

Free Convert Video Compressor (freeconvert.com/video-compressor) — online video compression.

Lazy Load Video Iframes

Lazy Embed (Free) — defers loading of video resources until the video is requested. Shows a placeholder with srcdoc attribute.

Perfmatters, FlyingPress, and many other plugins can also lazy load video iframes.

Lightweight Video Players

Presto Player (Free) — lightweight. HTML5, YouTube, and Vimeo support.

Video Pack (Free) — lightweight, local hosting.

HTML5 Video Player (Free) — another lightweight option.

Lottie Animation Optimization

AM Lottie Player (Free) — lightweight Lottie player plugin.

Lottiemizer (Free) — compresses Lottie animations.

dotLottie (dotlottie.io) — aggregates Lottie files into compressed .lottie format.

GIF Compression

Use multiple services for maximum compression: Ezgif, Gifcompressor, Free Convert, Xconvert, ILoveIMG, Veed.io, and Animately.

Embed Optimization

Embed Optimizer (Free) — lazy-loads embeds (YouTube, TikTok, etc.) so they don't compete with resources during page load.

Chapter 16

The Complete Optimization Toolkit

Here is the proven plugin stack to achieve 90+ mobile PageSpeed scores on an Elementor site. This was demonstrated on a site running Elementor + WooCommerce with a page weight of just 168 KB.

The Paid Stack (12 plugins)

Advanced Database Cleaner Pro

Index WP MySQL For Speed (free)

Asset Cleanup Pro

Perfmatters (paid)

Disable Gutenberg (free)

Docket Cache (free)

Pre-Party (free)

FlyingPress (paid)

Flying Pages (free) — preloads inner pages HTML

Inspect HTTP Requests (free)

Disable WordPress and WooCommerce Bloat (free)

Theme: Hello Elementor (free)

The Free Alternative Stack (16 plugins)

Because it takes 16 free plugins to replicate Perfmatters functionality, the paid stack is recommended if budget allows. But the free stack works just as well:

Asset Cleanup (free version)

Debloat (free)

Pre-Party (free)

Remove Global Styles (free)

Disable WordPress and WooCommerce Bloat (free)

CAOS for Local Analytics (free)

Freesoul Plugin Deactivator (free)

Fluent Snippets (free)

A3 Lazy Load or any lazyload plugin (free)

Dynamic Heartbeat Control (free)

CDN Enabler (free)

Yabe Webfont (free)

Disable Google Fonts (free)

WPS Hide Login (free)

Lazy Load Anything (free)

Speed Booster Pack (free)

By Category: Essential Plugins

Caching

FlyingPress (paid) or Speed Booster Pack (free)

Docket Cache (free object cache) or Redis

JavaScript & CSS Optimization

Perfmatters (paid) or Debloat + Asset Cleanup (free)

Disable Gutenberg (free) if not using block editor

Disable WP & WooCommerce Bloat (free)

Image Optimization

ShortPixel (freemium) or Smush (free) or Flying Images (free)

Converter for Media (free WebP conversion)

Auto-sizes for Lazy-loaded Images (free)

Font Optimization

Yabe Webfont (free) for local hosting

Pre-Party (free) for resource hints

Database

Advanced Database Cleaner (free/pro)

Index WP MySQL For Speed (free)

Sweeppress or AAA Option Optimizer (free)

Diagnosis & Analysis

Query Monitor (free)

Code Profiler (free/pro)

F12 Profiler (free)

Debug Log Manager (free)

Security (Lightweight)

BBQ Firewall (free)

Limit Login Attempts Reloaded (free)

Two Factor (free)

Patchstack (freemium)

Headers Security Advanced & HSTS WP (free)

Final Note

An Elementor site can be optimized to 90+ mobile scores in 20 minutes once you have your configuration down. Export your settings and import them on any Elementor site. This is easily replicable, site after site.

Quick Reference: Key Targets

Metric | Target
Mobile PageSpeed Score | 90+
Desktop TTFB | < 300ms
Mobile TTFB | < 500ms
Page Weight | < 500 KB (ideal < 200 KB)
HTML Document Weight | < 50 KB
Image File Weight | < 100 KB each
Number of Requests | < 40
DOM Size | < 1000 elements (up to 2000 acceptable)
Database Query Time | < 0.04 seconds

The Ultimate WordPress Guide to Speed Up Your Website · 2026 Edition

All tools and plugins mentioned are either free or have free tiers unless otherwise noted.