# 12 Ways to Speed Up Your WordPress Site

Author: Fatih Emin Çakıroğlu (https://fatihemincakiroglu.com)
Source: https://fatihemincakiroglu.com/en/wordpress-site-hizi
Published: 2026-09-26
Updated: 2026-09-26

A slow WordPress site rarely has a single cause. The picture I see most in audits is all of these at once: weak shared hosting, a heavy page builder theme, more than thirty plugins and uncompressed images. One caching plugin hides this but does not fix it.

The 12 ways below start at the server and move toward the front end. Measure before and after each step, or you will not know what worked. I checked plugin names on WordPress.org pages as of November 2026.

> Short answer: For WordPress speed, first check field data in PageSpeed Insights and the Core Web Vitals report in Search Console. Then update hosting and PHP, add page caching, serve images at the right size and format, cut unnecessary plugin and heavy theme weight, sort out fonts and a CDN, and clean the database.

## Measure first, then fix

Speed work uses two kinds of data. Field data comes from real Chrome users (Chrome UX Report) and shows the experience Google evaluates. Lab data (Lighthouse) is measured in a single test environment and helps find the cause of a problem.

**WordPress speed measurement loop**
1. **Check field data**: Find which URL groups have issues in the Search Console Core Web Vitals report.
2. **Pick page types**: Take one sample URL each from the home, category, product and blog templates.
3. **Diagnose**: Use PageSpeed Insights and Lighthouse to identify the LCP element and long tasks.
4. **Change one thing**: If you change several settings at once you cannot separate their effects.
5. **Measure again**: Lab results change at once; field data changes over weeks.

The thresholds: LCP at most 2.5 seconds, INP at most 200 milliseconds, CLS at most 0.1. I cover measurement differences and each metric in [Core Web Vitals](https://fatihemincakiroglu.com/en/core-web-vitals-2025). Mobile scores are usually worse than desktop; [mobile SEO](https://fatihemincakiroglu.com/en/mobil-seo) covers mobile-specific checks.

## Speeding up WordPress on the server side

### 1. Improve hosting and server response time

If the server sends the first byte late, every front-end improvement sits on top of that delay. The server response time warning and TTFB in PageSpeed Insights are the first signs. Server location and your plan's resource limits (CPU, memory, processes) are decisive.

### 2. Update your PHP version

WordPress's official requirements page recommends PHP 8.3 or higher, and MySQL 8.0 or MariaDB 10.11 or higher for the database. Older versions still run but have reached end of life. Test theme and plugin compatibility on a staging site before upgrading.

### 3. Add page caching

Page caching serves ready HTML instead of running PHP and database queries on every visit. Options include Automattic's WP Super Cache, LiteSpeed Cache on LiteSpeed servers (its page cache needs a LiteSpeed-compatible server), or WP-Optimize, which combines caching, images and database cleanup. Many managed hosts provide their own server cache; in that case do not add a second caching plugin.

### 4. Use a persistent object cache

A persistent object cache such as Redis or Memcached keeps the results of repeated database queries in memory. It makes a real difference on sites where logged-in users, the cart and the admin area cannot be page cached. Ask your host whether they offer it.

> **Speculative loading** Since WordPress 6.8, prefetch with conservative eagerness is enabled by default for logged-out visitors. The next page starts loading when a user begins clicking a link. Core filters let you change the setting.

## Speeding up WordPress with images

### 5. Serve images at the right size and format

Uploading a 4000-pixel file for an image shown at 400 pixels on a phone is the most common mistake. Resize and compress images before uploading. Since WordPress 6.5 you can upload AVIF if your server's image library supports it, and for WebP conversion you can use the Performance Lab team's Modern Image Formats plugin or WP-Optimize. File names and alt text are covered in [image SEO](https://fatihemincakiroglu.com/en/gorsel-seo).

### 6. Exclude the LCP image from lazy loading

WordPress adds lazy loading to images by default, but the large image at the top of the screen (usually the LCP element) should not load late. If your theme or page builder adds loading="lazy" to it, remove it and prioritize it with fetchpriority="high". The Performance Lab team's Image Prioritizer plugin aims to automate this prioritization.

## Reducing theme, plugin and code weight

### 7. Audit plugin load

The problem is not the number of plugins but how much code and how many queries they run on each page. The Query Monitor plugin shows slow and duplicate database queries, HTTP API calls and which plugin they come from. Delete unused plugins and remove one of any two that do the same job. For choosing an SEO plugin, see the [WordPress SEO plugins](https://fatihemincakiroglu.com/en/en-iyi-wordpress-seo-eklentileri) comparison.

### 8. Choose a lightweight theme

Page builder themes can add large CSS and JavaScript files to every page. On a new project, starting with a lightweight or block theme is easier than optimizing later. Switching themes on an existing site is a big job, so first turn off unused modules in the theme settings.

### 9. Tidy up CSS and JavaScript

Minifying, deferring non-critical JavaScript and removing unused CSS reduce render-blocking resources. Combine and defer settings can break menus, forms or sliders, so test the page by hand after each change. Long JavaScript tasks are usually the root cause of INP issues; see [JavaScript SEO](https://fatihemincakiroglu.com/en/javascript-seo).

### 10. Optimize fonts

Host font files on your own server, load only the weights you use and use font-display: swap. Preload the main heading font so text does not appear late. When subsetting, keep the character sets your languages need (Turkish letters such as ğ, ş and ı sit in latin-ext); otherwise those letters render in a fallback font and can cause layout shift (CLS).

## Delivery and database

### 11. Use a CDN

A CDN delivers static files from servers close to the visitor. The effect is clearer when visitors come from many cities and countries. For LiteSpeed Cache users, the QUIC.cloud CDN option integrates with the plugin; other sites can use their host's CDN or an independent provider.

### 12. Clean the database

Post revisions, expired transients, spam comments and autoloaded options left by removed plugins pile up over the years and slow queries. WP-Optimize can schedule this cleanup. Always take a database backup first.

## Which step improves which metric?

| Symptom | Affected metric | Related steps |
| --- | --- | --- |
| The page starts loading late | TTFB, LCP | 1, 2, 3, 4, 11 |
| The main image appears late | LCP | 5, 6, 11 |
| Clicks respond slowly | INP | 7, 8, 9 |
| Content shifts while loading | CLS | 5, 10 |
| Admin and cart are slow | Server time | 2, 4, 7, 12 |

**Priority on a typical shared-hosting WordPress site**
- Page caching: 9points
- Image size and format: 8points
- Hosting and PHP version: 8points
- Plugin audit: 7points
- CSS and JavaScript: 6points
- Fonts: 4points
_Impact score (1-10), the author's assessment. The order on your site depends on your measurements._

## Speed for WooCommerce stores

Cart, checkout and account pages are personal, so they must be excluded from page caching; that makes server and object caching more important for stores. Filtered category pages and many product variations increase database load. Store-specific technical settings are in [WooCommerce SEO](https://fatihemincakiroglu.com/en/woocommerce-seo), and the general framework is in the [ecommerce SEO guide](https://fatihemincakiroglu.com/en/e-ticaret-seo).

> **Caching and the cart** If a caching plugin caches the cart or checkout page, customers may see each other's carts. After setup, always test that these pages are excluded.

## Making speed gains last

Speed is not a one-off project; every new plugin, theme update or campaign image can undo the gains. I repeat these checks monthly:

- [ ] Is there a new failing URL group in the Search Console Core Web Vitals report?
- [ ] Do recently added plugins produce slow queries in Query Monitor?
- [ ] Are newly uploaded images the right size?
- [ ] Are PHP and WordPress up to date?
- [ ] Does the cache exclude cart and checkout pages?

For a full checklist of related technical issues, see the [technical SEO guide](https://fatihemincakiroglu.com/en/teknik-seo). To tackle speed and conversion together, see [performance and growth](https://fatihemincakiroglu.com/en/performance-growth), [ecommerce SEO consulting](https://fatihemincakiroglu.com/en/ecommerce-seo-consulting) for stores, or [SEO consulting](https://fatihemincakiroglu.com/en/seo-consulting) for a technical audit, or [book an intro call](https://fatihemincakiroglu.com/en/book-a-call).

## Frequently Asked Questions

### Can a page rank well without a PageSpeed Insights score of 100?

Yes. The lab score is a diagnostic tool; Google's page experience assessment relies on field data. The goal is not a perfect score but passing Core Web Vitals thresholds for real users.

### How many plugins are too many?

There is no fixed number. One heavy plugin can slow a site more than ten light ones. Look at the real load shown in Query Monitor and PageSpeed Insights, not the count.

### When do speed improvements show up in Search Console?

The Core Web Vitals report uses field data, so changes appear within a few weeks. You can track a fix with the report's validation feature. Lab tests change immediately.

### Is a free caching plugin enough?

For most small and mid-sized sites a free caching plugin is enough. The real difference comes from hosting resources and correct configuration. On managed hosting, check the server's own cache first.

### Can a speed plugin break my site?

Yes, especially CSS and JavaScript combine and defer settings can break menus, forms and sliders. Turn settings on one at a time and test key pages after each step. Make changes on a staging site first if possible.

---
Please attribute as: "Fatih Emin Çakıroğlu (fatihemincakiroglu.com)". Original: https://fatihemincakiroglu.com/en/wordpress-site-hizi
