Alejandro Rioja.
SEO

How To Speed Up WordPress Site? Effective Tips & Tricks

Alejandro Rioja
Alejandro Rioja
10 min read
TL;DR

Speed up your WordPress site in 2026 by targeting Core Web Vitals (LCP, INP, CLS), pairing a caching plugin with good hosting, serving WebP/AVIF images, and routing static assets through a CDN.

Free newsletter

Every Wednesday. 28,400+ operators. Zero fluff.

Table of contents

Open Table of contents

Why site speed matters more than ever in 2026

A slow site costs you on multiple fronts:

  1. First impression — visitors decide within milliseconds whether to stay or bounce. A page that drags signals low quality before they’ve read a word.
  2. Core Web Vitals in search — Google measures Largest Contentful Paint (LCP), Interaction to Next Paint (INP, which replaced FID in 2024), and Cumulative Layout Shift (CLS). Poor scores hurt rankings.
  3. Mobile reality — the majority of web traffic is mobile. Smaller CPUs and variable connectivity mean every unoptimized kilobyte costs more on a phone than on a desktop.
  4. Conversion impact — a well-known industry pattern: page load time correlates directly with bounce rate. The longer your page takes to load, the more potential customers leave before they convert.
  5. AI search referrals — if your content gets cited by an AI Overview or a Perplexity answer, that traffic arrives cold and high-intent. A slow load kills the conversion before it starts.

Read: How To Optimize Your Website Speed

Understanding Core Web Vitals in 2026

Google’s Core Web Vitals are the three metrics that matter most for search ranking:

These aren’t abstract — they show up in Google Search Console under Core Web Vitals. Check your field data there before touching anything else.

Testing site speed

Before optimizing, get a baseline. Use these tools:

  1. Google PageSpeed Insights — shows both lab and field (real-user) data; directly reflects what Google sees.
  2. GTmetrix — detailed waterfall charts; useful for finding what’s blocking render.
  3. Pingdom — straightforward load-time reporting from multiple regions.

Run each test from a location close to your actual audience. Numbers vary between tools — that’s normal. What you want is a consistent baseline to measure improvement against.

Things that influence WordPress speed

Three layers control how fast your site actually loads:

  1. Hosting infrastructure — the server’s hardware, the PHP version it runs, its geographic proximity to your visitors, and whether it uses SSD storage. This is the foundation everything else sits on.
  2. WordPress itself — the theme, plugins, and database all add weight. A bloated theme or a plugin that runs 40 database queries on every page load will undermine every other optimization.
  3. End-user devices and connections — you can’t control these, but you can serve your content in formats that are forgiving of slower hardware and connections (more on that under images and CDN).

How to speed up your WordPress site

1. Start with good hosting

Shared hosting pools server resources across many sites. When a neighbor spikes traffic, your site slows down — there’s no way around this. Managed WordPress hosting (Kinsta, WP Engine, Pressable, and similar providers) gives you dedicated resources, server-level caching, and PHP configured specifically for WordPress. Verify current pricing and features directly with each provider, as plans change frequently.

If you’re on shared hosting and hitting performance ceilings, the hosting upgrade will have more impact than any plugin tweak.

Also confirm your host is running PHP 8.2 or newer (verify current recommended version). PHP 8.x delivers meaningful performance gains over the 7.x branch, and older PHP versions are also security risks. Most managed hosts let you switch PHP version from the control panel.

2. Use a caching plugin — and pick the right one

Caching stores a pre-built version of each page so WordPress doesn’t rebuild it from scratch for every visitor. In 2026, the leading options are:

A word of warning: don’t use a caching plugin to paper over bad hosting or a bloated theme. Caching helps a well-built site run faster. It can’t compensate for fundamentally slow infrastructure.

3. Optimize images — serve WebP and AVIF

Images are almost always the biggest payload on a WordPress page. In 2020, JPEG and PNG were the defaults. In 2026, you should be serving WebP at minimum, and AVIF where browser support allows. Both formats are significantly smaller than JPEG at the same visual quality.

How to do it:

4. Use a CDN — Cloudflare is the obvious starting point

A Content Delivery Network caches your static assets (images, CSS, JavaScript) at edge servers close to your visitors worldwide. Without a CDN, every asset request travels all the way to your origin server, regardless of where the visitor is.

Cloudflare has a free tier that handles CDN, basic DDoS protection, and some performance optimizations for most sites. For WordPress specifically, the Cloudflare plugin integrates cache purging so pages clear when you publish or update content.

If you need more aggressive edge caching or want the CDN integrated with your hosting, providers like Kinsta and WP Engine bundle their own CDN. Verify what’s included in your specific hosting plan.

5. Audit and trim your plugins

Every active plugin adds PHP execution time, database queries, and potentially extra CSS/JS on every page load. Run a plugin audit:

  1. Deactivate plugins you don’t actively use.
  2. Use Query Monitor (free WordPress plugin) to see which plugins are running the most database queries or causing PHP errors.
  3. Replace multi-feature heavy plugins with leaner alternatives where you only need one capability.
  4. Check for plugins that inject scripts site-wide when they’re only needed on specific pages — some form plugins or chat widgets do this.

The goal isn’t to minimize plugin count for its own sake. It’s to ensure every active plugin is earning its place.

6. Choose a performance-optimized theme

Themes with elaborate animations, full-screen video headers, and dozens of bundled layout options load a lot of code the visitor never sees. This code still has to parse.

Pick a theme built for speed — lightweight frameworks like GeneratePress or Kadence have good track records. Then add features via plugins rather than choosing a theme that ships with everything built in.

If you’re using a page builder (Elementor, Bricks, and similar), test your Core Web Vitals scores carefully — some builders generate heavier markup than hand-coded pages. Newer builder versions have improved significantly, but verify with your own PSI scores.

7. Optimize the homepage

The homepage is usually the highest-traffic page and the one that sets first impressions. Specific tactics:

Read: How To Design A Landing Page: A Step By Step Guide

8. Additional optimizations worth implementing

These don’t usually have the same impact as the above, but they add up:

WordPress Speed — 2026 FAQ

What is the most impactful single change I can make to speed up WordPress?

For most sites, it’s either upgrading hosting or fixing image delivery. If you’re on shared hosting hitting performance walls, move to managed WordPress hosting. If you’re on decent hosting but images are unoptimized JPEGs, converting to WebP and implementing lazy loading will show immediate gains. Check PageSpeed Insights — it will tell you which issue dominates on your specific site.

Is Cloudflare free tier enough for WordPress speed?

For most small to medium sites, yes. Cloudflare’s free tier provides CDN, basic DDoS protection, and caching for static assets. Where you’ll hit limits is full-page caching (Cloudflare calls this “cache everything” and it requires configuration or a paid plan) and advanced image optimization features. Start with the free tier and the official Cloudflare WordPress plugin, then evaluate whether paid features are worth it for your traffic volume.

How do INP scores differ from the old FID metric?

FID (First Input Delay) only measured the delay before the browser started processing the first user interaction. INP (Interaction to Next Paint) measures the full time from any interaction — click, tap, keyboard input — to when the visual response appears. It’s a stricter, more representative measure of real-world responsiveness. Sites that passed FID sometimes fail INP. The fix is usually the same: reduce JavaScript execution time, defer non-critical scripts, and avoid long tasks on the main thread.

Should I use WebP or AVIF for WordPress images?

Use WebP as your baseline — browser support is effectively universal now. AVIF offers better compression (smaller files at the same quality) but browser support, while broad, isn’t complete for all combinations of device and OS as of 2026. Serve AVIF to browsers that support it via the <picture> element with AVIF as the first <source>, WebP as the fallback, and JPEG as the final fallback. Most modern image optimization plugins handle this automatically.

Related reading:

The shorter version

If you’re reading this because the workflow it describes is eating your week, that’s the kind of loop I build AI agents for. Two build slots open at a time.

Updated for May 2026

A short note from May 2026: the workflow this post describes was checked against the current state of the underlying tools and platforms. Where specific tools, UIs, or features have evolved, the structural advice still holds — the implementation will look slightly different in 2026. If you hit a step that doesn’t match what you see on screen, that’s likely a UI refresh, not a fundamental change in approach. Drop a note via the contact form and I’ll patch it explicitly.

Keep reading

Get the AI playbook in your inbox

Every Wednesday. 28,400+ operators. Zero fluff.

⌕
↵ ↵ to see all results esc esc to close