How to Speed Up WordPress Sites for Tradies
All 32 steps, with my settings and before-and-after tests.
If you buy through an affiliate link on this page, I may earn a commission at no extra cost to you.
The short version
- Measure first: real visitors' speeds in Google PageSpeed Insights, then a real phone test. How to measure
- Server and hosting: a host near your customers, PHP 8.3+ (WordPress's language), compression on. Steps 1 to 9
- Caching and CDN: ready-made copies of your pages, kept close to your visitors. Steps 10 and 11
- Images, scripts, fonts: small images, delayed scripts, less style code (CSS), fewer font files. Steps 12 to 16
- My own test: delaying scripts took my old WordPress home page's SpeedLab phone score from 78 to 100. Step 14
- Theme and plugins: a light theme, no heavy page builder or spare plugins. Steps 17 to 23
- Database and admin: old data, the Heartbeat API (admin check-ins), bloat and a few settings. Steps 24 to 30
- WooCommerce: load the store's scripts only on the pages that sell. Steps 31 and 32
- Do it yourself: every step here, with a backup, a test copy (staging) and lots of testing.
- Hiring someone? The warning signs, and the good signs to look for instead. See the signs
- Or let me look after it: Website Care, with hosting and Google PageSpeed Insights checks, from $120 a month + GST. How it works
What a fast WordPress site looks like
A slow site sends visitors to a competitor before they've read a word, and Google measures how fast your pages feel to real people. It calls the three main measures Core Web Vitals: how soon the main content shows, how quickly the page answers a tap or click, and how still it stays as it loads, with nothing jumping around.
In my experience, most slow WordPress sites come down to the hosting first, then a heavy theme or page builder, big images and a pile of scripts loading before anyone taps. This guide has every step I know to fix that. I first wrote it in January 2024, with my own WordPress site as the test case. This site has since moved off WordPress, so the dated tests and screenshots are from its WordPress days, but the WordPress sites I host, like Barnes Family Roof Plumbing's and Ascent Garage Doors', still run on Rocket.net and Perfmatters. I checked every price and version in November 2026.
What's in the Lighthouse score
| Measure | Good | Poor | What it is |
|---|---|---|---|
| Largest Contentful Paint | 2.5 s or less | Over 4 s | When the biggest thing on screen appears |
| Interaction to Next Paint | 200 ms or less | Over 500 ms | How quickly the page responds when you tap, click or type |
| Cumulative Layout Shift | 0.1 or less | Over 0.25 | How much the page jumps as it loads |
| Time to First Byte | 0.8 s or less | Over 1.8 s | How fast the server answers (not a Core Web Vital) |
Time to First Byte isn't a Core Web Vital, but a slow server answer makes a good Largest Contentful Paint hard, so that's where step 1 starts.
How to measure your speed
Measure before you change anything, so you know what each step did.
- Check real visitsGoogle PageSpeed Insights shows real visitors' speeds if it has them, and a simulated phone test.
- Test on a real phoneWebPageTest or SpeedLab, on your customers' kind of device, from near them: the closest to real use.
- Test your server from afarSpeed Vitals' Time to First Byte test shows if far-off customers need a content delivery network (CDN).
- Read the adviceWork through what each tool recommends, starting with the items that matter most.
- Work through the stepsThen work through the 32 steps, testing each change so you know what it did.
- Test more than onceA few runs each time, on both phones and desktops, for one page of each kind you have.
| Tool | What it shows | Cost |
|---|---|---|
| Google PageSpeed Insights | 28 days of real visits where Google has them, and a simulated phone test | Free |
| Lighthouse | The same lab test in Chrome's developer tools, and on a staging copy too | Free |
| WebPageTest | A detailed lab test that shows how the page loads, step by step | Free; paid plans too |
| BrowserStack SpeedLab | Lighthouse on real phones and desktops, five runs at once | Free |
| Speed Vitals | Your server's answer time from up to 40 places, 30 on the free plan | 15 free tests a week |
Real-user data in Google PageSpeed Insights covers the last 28 days, so any fix you make takes up to four weeks to show up there. Small sites often have no real-user data at all, and then the lab test is what you have to go on.
| Setting | What I used |
|---|---|
| Tool | BrowserStack SpeedLab |
| Page | The home page of this site, back when it ran on WordPress |
| Location | Australia |
| Connection | 4G Slow: 1.6 Mbps down, 768 Kbps up and a 150 ms round trip |
| Device | A real Samsung Galaxy S10 Plus, Android 9, Chrome 120, 412 x 722 px |
| CPU power | At full power, not slowed down |
| Runs | Five tests each time, judged on the median result of the five |
Part 1: Server and hosting
Most of the speed comes from here, so fix these before anything on the page.
Step 1: Get better WordPress hosting
What it does: sets the pace for your whole site and matters most, as everything else runs on top of your server. A slow one holds back every other fix you make, however well you make it.
My hosting checklist
| Check | What good looks like |
|---|---|
| Server location | In your customers' country, ideally in the same city as them |
| Storage | NVMe drives, which read and write faster than older disks |
| Protocols | HTTP/2 and HTTP/3, the newer ways browsers fetch a page |
| Compression | Brotli, with Gzip as the fallback (step 4) |
| CPU and RAM | Enough for your traffic and plugins, from a host who says how much |
| Object caching | Redis, for fewer database queries (step 10) |
| CDN | Full-page caching near visitors, like Cloudflare Enterprise (step 11) |
| PHP | 8.3 or later, the version WordPress recommends (step 3) |
| Database | MariaDB 10.11+ or MySQL 8.0+. I prefer MariaDB of the two |
| Uptime | At least 99.9% |
| Security | DNS-level protection, like Cloudflare. Malware scanning is a bonus |
| Support | Live chat, 24 hours a day, 7 days a week |
What good looks like
- A server in your customers' country, ideally your city.
- Managed WordPress hosting that sets all this up for you.
- A plan that says how much CPU and RAM you actually get.
- Object caching, a CDN and Brotli included in the plan.
- Uptime of at least 99.9%, and live chat any hour.
Where people go wrong
- Cheap shared hosting with low limits on CPU and RAM.
- A server overseas when your customers are in Australia.
- Reading a host's biggest plan as if it's the one you get.
- Expecting a plugin to make up for a slow server.
CPU: the brain
- Runs WordPress, your theme and all of your plugins
- More cores run more jobs at once
- Too few, and jobs queue up, slow the site or crash it
RAM: the helper
- Holds data ready for the CPU to use
- Saves a trip to the disk every time
- More RAM means more held in memory, and a faster server
I use and recommend Rocket.net. The WordPress sites I host run on it, like Barnes Family Roof Plumbing's, and Cloudflare's Enterprise network comes with every plan. It has a data centre in Sydney as well. Plans start at US$30 a month, or US$25 billed yearly. The first month is US$1, and there's a 30-day money-back guarantee if it's not for you. Its pricing page lists CPU and RAM only for its Enterprise plans, like Enterprise 2's 32 CPU cores and 128 GB of RAM at US$1,299 a month, so ask before you buy a smaller one.
Most WordPress owners are better off with managed hosting like Rocket.net, which handles most of the checklist for you. If you're a developer who'd rather run your own server, my 2024 picks were a control panel like GridPane, my favourite, or RunCloud, ServerPilot or SpinupWP, on a server from Vultr, also my favourite, or DigitalOcean, Linode or Google Cloud Platform. AWS was my least favourite of all.
Step 2: Use Cloudflare for DNS
What it does: speeds up the DNS lookup that finds your server's IP address from your domain name. It's not a huge difference, but every millisecond counts, and it's free to do.
DNS lookup time
What good looks like
- Cloudflare's free DNS, wherever your domain is registered.
- The grey cloud, "DNS only", when you only want the DNS.
- DNS kept on Cloudflare even when your host has Cloudflare.
- A .com registered at Cloudflare, which sells domains at cost.
Where people go wrong
- Leaving DNS with your registrar, like GoDaddy or Namecheap.
- The orange cloud on by mistake when you meant DNS only.
- Forgetting your host can't edit DNS records in your account.
- Trying to register a .com.au at Cloudflare. You can't.
I use Cloudflare's DNS for every client I look after, whoever hosts them and wherever their domain is registered. Registering your domain at GoDaddy or Namecheap is fine; their DNS is where you lose time. You can register a .com at Cloudflare too, and it says it sells domains at or below what the registries charge it. It doesn't offer .au domains, though its DNS works fine for them.
In my experience, Cloudflare's changes reach visitors in minutes, not days, which helps avoid downtime in a move, and it's easier with several sites. The catch is you manage it yourself, so your host will usually ask you to make the changes, unless you add your host as a user on your account.
Grey cloud: DNS only
- Cloudflare answers the DNS lookup
- Visitors go straight to your server
- Your server's address is public
Orange cloud: proxied
- Traffic runs through Cloudflare
- Adds Cloudflare's caching, firewall and attack protection
- Only for records that point to your site (A, AAAA, CNAME)
Cloudflare has a guide to adding a site. If you move to Rocket.net, it sets up Cloudflare Enterprise's CDN for you, which is far better than the CDN on Cloudflare's free plan, and you still keep your DNS on Cloudflare.
Step 3: Use the latest supported PHP version
What it does: runs WordPress's code faster. PHP is the language WordPress is written in, and WordPress's own Site Health says newer versions get regular security updates and "may increase your site's performance" too.
| PHP | Released | Security fixes until | Use it? |
|---|---|---|---|
| 8.5 | 20 Nov 2025 | 31 Dec 2029 | Yes, once your theme and plugins pass a test on a staging copy |
| 8.4 | 2024 | 31 Dec 2028 | Yes |
| 8.3 | 2023 | 31 Dec 2027 | Yes, the lowest WordPress recommends |
| 8.2 | 2022 | 31 Dec 2026 | Move off it soon |
| 8.1 and older | Before 2022 | Ended | No |
What good looks like
- PHP 8.3 or later, the lowest WordPress recommends.
- The newest version your host offers that your site passes.
- A version that still gets security fixes from php.net.
- Tested on a staging copy before you switch the live site.
- The previous version back on if a theme or plugin breaks.
Where people go wrong
- Still on PHP 8.1 or older, which get no security fixes at all.
- Staying on 8.2, which stops getting fixes in December 2026.
- Switching the live site without testing your plugins.
- Ignoring Site Health when it flags your PHP version.
Step 4: Compress with Brotli or Gzip
What it does: shrinks the HTML, CSS and JavaScript code behind each page before your server sends it out. If your files aren't compressed, you're missing out on some serious speed gains.
| Cloudflare plan | Compression it uses by default |
|---|---|
| Free | Zstandard |
| Pro | Brotli |
| Business | Brotli |
| Enterprise | Gzip |
What good looks like
- Brotli where you can. It compresses further than Gzip.
- Gzip as the fallback, as Google Lighthouse recommends.
- Zstandard is fine too. It's on Cloudflare's Free plan.
- Tested with Gift of Speed's Gzip test.
- Or with "Enable text compression" in Google PageSpeed Insights.
Where people go wrong
- No compression at all, so every file goes out full size.
- Assuming your host turned it on without checking.
- Gzip only, when your host or CDN can already do Brotli.
Gzip is the most widely used, and Brotli is the newer one that makes smaller files. The WordPress version of this site used Brotli. Cloudflare Enterprise defaults to Gzip, but Rocket.net's setup lists Brotli, and Cloudflare explains how to send Brotli from your web server in its post on Brotli.
Step 5: Raise the memory limit
What it does: gives WordPress, your theme and plugins enough memory to run at full speed. The limit stops one script hogging the server, so you want it high enough, not unlimited. Errors about exhausted memory, slow pages and broken plugins can all be a low limit, or a plugin using it all up, so check which before you raise it.
| Setting | Default | What I set |
|---|---|---|
| WP_MEMORY_LIMIT | 40M (64M on multisite) | At least 256M |
| WP_MAX_MEMORY_LIMIT | 256M | 512M for imports. 1GB on the WordPress version of this site |
| PHP memory_limit | 128M | Set by your host |
If WordPress can't raise its limit, PHP's own memory limit is the one that counts.
What good looks like
- WP_MEMORY_LIMIT at 256M or more for the front end.
- WP_MAX_MEMORY_LIMIT higher still, for a faster back end.
- Set in wp-config.php, or by your host if you're unsure.
- Or in .htaccess or php.ini, the server's settings files.
Where people go wrong
- Leaving WordPress at its 40M default on a busy site.
- Raising the limit to hide a plugin that eats memory.
- Writing the names in lower case. They go in capitals.
- Setting it higher than your host's PHP limit allows.
define( 'WP_MEMORY_LIMIT', '256M' );define( 'WP_MAX_MEMORY_LIMIT', '512M' );WP_MAX_MEMORY_LIMIT sets the memory for everything in the admin area. In my experience, most hosts set it the same as WP_MEMORY_LIMIT, so raise it yourself if you want a faster back end. .htaccess is the settings file on Apache servers, and php.ini is PHP's own settings file. The other PHP limits, for imports and uploads, are in the table under step 32.
Step 6: Use a server cron job
What it does: takes scheduled jobs off your page loads. WP-Cron, WordPress's built-in scheduler, checks for jobs on every visit, so on a busy site it fires constantly and loads your server. Server cron runs them on a timer.
WP-Cron checks for jobs on every page load, so it runs often when the site is busy and not at all when it's quiet. A server cron job runs every 5 minutes, busy or not.
What good looks like
- A server cron job calling wp-cron.php every 5 minutes.
- WP-Cron turned off in wp-config.php once that runs.
- WP Crontrol, a free plugin, to check the jobs still fire.
- Your host setting it up for you, if you'd rather not.
Where people go wrong
- Turning WP-Cron off before the server job is set up.
- Leaving both running, which wastes server time.
- A host that can't add a server cron. Time to move.
*/5 * * * * wget -q -O - https://YOUR_SITE_URL/wp-cron.php?doing_wp_cron >/dev/null 2>&1define( 'DISABLE_WP_CRON', true );WP-Cron is what WordPress uses for its background jobs: checking for updates, publishing scheduled posts and running plugins' own jobs. On a quiet site the problem flips the other way, and the jobs wait for the next visit. With neither WP-Cron nor a server cron running, scheduled posts and update checks stop without any warning. WordPress's handbook explains WP-Cron and shows the same server cron setup, and Kinsta has a guide to turning WP-Cron off and using a server cron instead.
Step 7: Use an SMTP provider
What it does: sends your site's emails, like quote requests and order confirmations, through a proper email service (an SMTP provider), not your server's PHP mail. It takes load off the server, and you should have it anyway so emails arrive.
| Option | Cost | Notes |
|---|---|---|
| Your host's own email sending | Included | The best WordPress hosts already have it turned on for you |
| Cloudways "Email delivery" | US$2.30 a month for 25,000 emails | An add-on run by Elastic Email |
| Brevo, free plan | Free | Up to 300 emails a day, once Brevo approves the account |
| Brevo Starter | US$9 a month | Or US$97 for a year, and plans start from 5,000 emails a month |
What good looks like
- Your host's own email sending service, if it has one.
- An add-on from your host, like Cloudways' Elastic Email.
- Brevo's free plan, for sending up to 300 emails a day.
- A plugin like WP Mail SMTP to connect it to WordPress.
- A test form sent after every change.
Where people go wrong
- WordPress's default PHP mail, straight from your server.
- Never checking whether the emails actually arrive.
I've had a good experience with Brevo. Barnes Family Roof Plumbing's quote forms send through it, connected to WordPress with FluentSMTP. There's more on hosts that include email sending in my WordPress hosting guide.
Step 8: Block bad bots
What it does: stops bots you don't want from using your server. Good bots, like Google's crawler, index your pages. Bad ones steal content, scrape emails, try passwords, click ads, attempt card fraud, skew analytics and launch attacks.
Over half of Internet traffic in 2026 wasn't human
| Option | What to know |
|---|---|
| Cloudflare Enterprise | Comes with Rocket.net's hosting plans; the best way I know to do it |
| Fastly Bot Management | Bot blocking from Fastly, another CDN. Price on request |
| BBQ Firewall | A free plugin that blocks bad bots. It used to be called Block Bad Queries |
| 7G Firewall rules | Rules for .htaccess or NGINX. Its author has since released 8G |
| Blackhole for Bad Bots | A free plugin, but its page says not to use it on a site with caching |
What good looks like
- Cloudflare Enterprise, which comes with Rocket.net's plans.
- Fastly's bot management, if your site already uses Fastly.
- A free plugin like BBQ Firewall.
- 7G or 8G firewall rules in .htaccess, or NGINX's settings.
- Blackhole for Bad Bots, only on a site without caching.
Where people go wrong
- Blocking Google's crawler by accident.
- Blackhole for Bad Bots on a cached site. It says not to.
- Cloudflare's free plan in front of a site that's already fast.
I don't recommend Cloudflare's free plan in front of a site that's already fast. It blocks some bad bots, but it can slow the site down: when I tested Free and Pro on the WordPress version of this site, pages came from Singapore, not Australia. Cloudflare itself says Free traffic is served wherever there's spare room. If Rocket.net isn't open to you, though, Free with the Super Page Cache plugin is still on my caching list in step 11.
Step 9: Choose your redirect method
What it does: decides where your 301 redirects run: the server, or WordPress with a plugin. A 301 sends an old page address to its new one for good. Both work; it's a judgement call on how many you have and your server's strength.
In .htaccess
- Each redirect runs faster than it would in WordPress
- But the server reads every rule before every page
- Thousands of rules can slow down Time to First Byte
In a plugin
- Easier for most WordPress admins
- Rules sit in the database, not in a file read before every page
- But every redirect adds more queries to the database
What good looks like
- Under about 1,000 redirects, either way is fine for speed.
- A cheap server: .htaccess, to save database queries.
- A strong server with a huge list: a redirect plugin.
- NGINX rewrite rules if your server runs NGINX, not Apache.
Where people go wrong
- Thousands of rules in .htaccess, read before every page.
- Keeping thousands of redirects you no longer need.
The WordPress version of this site used .htaccess for its 301 redirects. If you have 10,000 redirects, ask first whether they all need to be there.
Part 2: Caching and CDN
Caching saves rebuilding each page. A CDN keeps the copy close to your visitors.
Step 10: Use caching
What it does: keeps ready-made copies of your pages, so WordPress doesn't rebuild each one every visit. Few steps do more. Server-side caching saves your host work; client-side caching, in the browser, saves downloads on return visits.
Five layers of caching
- VisitorBrowser cacheFiles kept in the visitor's browser, so a second page needs fewer downloads
- Near themCDN cacheCopies kept in data centres close to visitors, from images and files up to whole pages
- Your serverPage cacheEach page saved as finished HTML, so WordPress doesn't build it again
- Your serverObject cacheDatabase answers kept in memory, like Redis, so WordPress asks less often
- Your serverOPcachePHP's compiled code kept ready, so it isn't compiled on every visit
Each caching layer is a separate setting, often in a different place.
What good looks like
- OPcache on. It's PHP's own, and built in from PHP 8.5.
- An object cache like Redis on stores, courses and members.
- Redis Object Cache to start, ideally Object Cache Pro.
- A page cache from your host, or a plugin like WP Rocket.
- No cache expiry at all on a site that rarely changes.
- An expiry of about 10 hours on a site that changes often.
- Browser caching on. WP Rocket turns it on at activation.
Where people go wrong
- An object cache on cheap hosting with little RAM.
- Assuming WordPress handles OPcache. PHP does.
- No page cache, so WordPress builds every page every time.
Before PHP 8.5, OPcache depends on your host, so ask them first. Not every host has page caching either, which is where WP Rocket comes in. Object caching matters most where WordPress stores things about people: WooCommerce, courses like LearnDash and memberships like MemberPress. On cheap hosting with little RAM, it can speed up the back end but slow or crash the rest. The WordPress version of this site just ran the free Redis Object Cache plugin, and with no course or member sign-ups, it didn't need Object Cache Pro.
Step 11: Use a CDN
What it does: keeps copies of your site in data centres near your visitors, which is why it's called a content delivery network. With full-page caching it serves whole pages from there, which helps a national or global audience most. Its firewall keeps your site safe and takes load off your server.
| Plan | Price | APO (whole-page caching) | Priority |
|---|---|---|---|
| Free | US$0 | US$5 a month | Served where there's spare room |
| Pro | US$20 a month yearly, US$25 monthly | Included | Below Enterprise |
| Business | US$200 a month yearly, US$250 monthly | Included | Below Enterprise |
| Enterprise | By contract | Included | Served first, closest to visitors |
Priority is who Cloudflare serves first when it's busy, from its own blog.
What good looks like
- Full-page caching near visitors, not just images and files.
- Rocket.net, which has Cloudflare Enterprise built in.
- Cloudflare APO: US$5 a month on Free, included from Pro.
- Cloudflare Free with the Super Page Cache plugin.
- Fastly's free tier, up to 100 GB a month in each region.
- The WordPress admin, wp-admin, left out of the cache.
- Your Time to First Byte tested from other countries.
Where people go wrong
- Thinking Cloudflare caches your pages by default. It doesn't.
- Without APO, a rule or a plugin, it caches files, not pages.
- "Cache everything" rules on a host with its own cache layers.
- Expecting Free or Pro to match Enterprise's priority.
Picture customers in Perth on a site hosted in Sydney: every page crosses the country. A CDN serves them from a data centre nearby, like Cloudflare's in Perth. Cloudflare is in 348 cities, 14 in Oceania, including Sydney, Melbourne, Brisbane, Perth, Adelaide, Canberra and Hobart.
My caching order
- 1Rocket.netCloudflare Enterprise built in
- 2Cloudflare + APOUS$5 a month on Free, plus the Super Page Cache plugin
- 3Cloudflare onlyFree, with the Super Page Cache plugin
- 4FastlyFree up to 100 GB a month, per region
Rocket.net does free migrations, so you can see your site on its full-page caching before you move. Test both versions' Time to First Byte, how fast the server answers, with Speed Vitals' TTFB test, and then compare them.
My second option is APO with two plugins: Cloudflare for WordPress, which APO needs, and Super Page Cache. APO serves your whole WordPress site from Cloudflare's network using Cloudflare Workers, code that runs on Cloudflare's servers, and it's a better way to cache whole pages than "cache everything" rules. IdeaSpot's video shows how to set up the Super Page Cache plugin.
Fastly is last because WordPress.org says its plugin hasn't been tested with the last three WordPress releases and may no longer be maintained, and Fastly prices its bot management and firewall on request. Its free tier covers 100 GB a month in each region.
Part 3: Images, scripts, fonts
What each page loads. Lighter pages show sooner, on any host.
Step 12: Optimise images and video
What it does: shrinks what's usually the heaviest part of a page. Images and videos are often a page's biggest files, so making them smaller is one of the best ways to speed up WordPress.
| Image | Width to upload | Why |
|---|---|---|
| Full-screen | 1920 px | Covers a large desktop screen |
| Featured | 1200 px | Google Discover recommends at least 1200 px wide images |
| Product | 600 to 2000 px | Smaller for speed, bigger for detail |
| In a post | Wider than its space | Sharper on retina screens. Mine were 1200 px for an 860 px space |
WordPress then makes: 2048 1536 1024 768 300 150 px wide
What good looks like
- Each image under 100 KB, or 200 KB if 100 looks blurry.
- Resized before upload: 1920 px full screen, 1200 px featured.
- SVG for icons and logos. PNG for transparent backgrounds.
- PNG for product images and any that need more detail.
- PNG for text on an image, where it looks sharper.
- JPG for most other photos.
- Smaller WebP and AVIF copies, made by a plugin like Imagify.
- Squoosh first for every last KB, then Imagify for the rest.
- The top (hero) image preloaded at high priority, the logo too.
- Each preload with the image's own sizes, so it loads once.
- Everything below the first screen lazy-loaded, with Perfmatters.
- Width and height on every image, so the page never jumps.
Where people go wrong
- Lazy-loading the hero image. Google says never do that.
- A preload without the image's sizes. Phones get two copies.
- A 4,000 px photo uploaded straight from a phone.
- Squeezing images down until they start to look blurry.
- Imagify's lossless setting on WebP. My files got bigger.
WordPress makes its smaller sizes for you, and WooCommerce adds its own from your settings, like 600 px for products and 100 px for gallery thumbnails. For the biggest gain, cut each image to the widest it shows on screen.
Retina screens show twice the detail, so my old WordPress site used 1200 px images in an 860 px space: heavier, still under 100 KB, and much sharper, though not perfect. Cutting another 30% or so wasn't worth blurry images. For Google Discover, the feed of articles in Google's app, Google's page recommends images at least 1200 px wide.
One image, three formats
The AVIF came out at about half the size of the PNG I started with. I used Imagify for this. It served the AVIF where the browser could take it, then the WebP, then the original image. Converted this way, a PNG's WebP copy ends up about the same size as a JPG of the same image, only sharper. Use Imagify's smart compression. For the most savings, run images through Squoosh before you upload.

Above and below the fold
On screen when the page opens
The fold
A preload tells the browser to fetch a file before the others. I preload everything above the fold, the logo included, on every site I build or look after. It's what Brian Jackson, Perfmatters' co-founder, recommends too, and in my experience it makes the biggest image on the page show up sooner.
Google's web.dev says never lazy-load that image. WordPress 6.3 and later give it high priority, which WordPress says typically improves Largest Contentful Paint by 5 to 10%, and skip lazy loading on the first images for you.
Do it right, though. On the WordPress version of this site, a hero preload without the image's sizes made phones download it twice, 24.9 KB extra, when I checked in October 2026. The fix is the image's own sizes in the preload.
In Perfmatters, each preload is a row with the file, the page it's for and a priority. Perfmatters says to set high for the main image, the one Largest Contentful Paint measures, and auto is fine for the other preloads. Perfmatters can also add any missing width and height to your images.
How I handle video
- No video above the fold if you can possibly avoid it.
- If it must go above the fold, upload it, don't embed it.
- Compressed first with HandBrake, and exported as WebM.
- Below the fold: a YouTube or Vimeo embed, lazy-loaded.
YouTube and Vimeo embeds bring their own scripts, so I lazy-load them with Perfmatters until visitors scroll near.
Step 13: Don't use image sliders
What it does: saves a page full of big images and the scripts to animate them. Slider plugins often load their scripts on every page, so they slow the whole site, not just the slider page.
A slider plugin
- Its scripts often load on every page
- Several big images to download
- Animations that lag on a slow phone
One strong photo
- One image, preloaded
- Nothing extra to load anywhere else
- Says what you do straight away
What good looks like
- No slider if you can do without one.
- No animations you can do without. I prefer sites without.
- Kadence Blocks' free Advanced Gallery for a simple slider.
- MetaSlider if you need a plugin. It's the best I've found.
- Few animations, and compressed images, in any slider.
- A background video self-hosted, short and compressed.
Where people go wrong
- Using Revolution Slider. Try MetaSlider.
- A slider of high-resolution images on a slow connection.
- A YouTube or Vimeo background video, with its scripts.
- Animations that lag, so a fast scroll feels broken.
Kadence Blocks' free Advanced Gallery does carousels and sliders; its Advanced Slider is a paid Pro block, and the Kadence theme has no slider of its own. MetaSlider also clashed less with optimisation plugins than others I tried.
Step 14: Delay and trim JavaScript
What it does: holds scripts back until the visitor first moves, taps or scrolls, so the page shows and responds first. The less JavaScript that loads before then, the better.
Delaying JavaScript
78100 SpeedLab score
What good looks like
- Defer JavaScript and Delay All Scripts, in Perfmatters.
- Menus and anything needed at once left out of the delay.
- Scripts that add words or links to the page left out too.
- Google Analytics and Google Tag Manager loaded after the page.
- A small script that catches an early tap on a phone link.
- Plugins switched off on pages that never use them.
- Forms embedded as a JavaScript snippet, so they can be delayed.
- If you minify, use Perfmatters or your theme, and test each page.
Where people go wrong
- Delaying everything and not testing what's broken.
- Making tracking wait for a tap. Some visits go uncounted.
- Content that only loads on a tap. Google never taps.
- Minifying without checking your theme. It can break styles.
- Waiting for Cloudflare to minify. It stopped in 2024.
Other pages and posts gave almost the same results. The big change was in Time to Interactive, how long the page took to be ready to use: 4.28 s down to 1.15 s on a real phone. Lighthouse no longer scores it, and Total Blocking Time was already under 1 ms: 0.89 ms, then 0.02 ms.
The SpeedLab reports
Before: 78

After: 100

What it saved
It delayed a lot of third-party software without removing any of it: Google Tag Manager, Google Analytics, Get Lasso, MailerLite and social sharing on posts. So you don't have to remove scripts that call outside services: delay them, then test the site properly. I'd leave tracking out of that delay now. A visitor who leaves without tapping anything is never counted, so let Google Tag Manager and Google Analytics load just after the page, with only a short wait. On some sites I look after, a tiny script records phone or email taps made before tracking has loaded.

Google's web.dev suggests async and defer (ways to load scripts without holding up the page) rather than waiting for a tap. I keep Perfmatters' Delay JavaScript on the WordPress sites I look after because it's key to a fast first load. Google says it won't load content that needs a tap, swipe or click, so anything that adds content has to load without one.
Minifying strips the spaces and comments out of code to make it smaller, but it can break a theme's styles. I rarely did it with a plugin, preferring Cloudflare's setting instead, until Cloudflare ended Auto Minify on 5 August 2024. I often turn whole plugins off, scripts and all, in Perfmatters' Script Manager. A contact form plugin only needs the pages that show the form, and on the WordPress version of this site, Novashare, the social sharing plugin, only loaded on posts. Embedded as a JavaScript snippet, a form below the fold or in a popup can be delayed too.
Step 15: Remove unused CSS
What it does: cuts the CSS, the style code, a page loads but never uses: fewer requests and less to download. It helps most on sites with heavy themes and page builders that load design features on every page, whether it uses them or not.
CSS and plugins: savings
What good looks like
- Perfmatters' Remove Unused CSS, with used CSS saved to a file.
- Exclusions added for anything that breaks, like menus.
- Perfmatters' list of common exclusions checked first.
- Whole plugins off on pages that never use them.
- Every change tested on a staging copy before the live site.
Where people go wrong
- Turning it on and not checking menus, comments or tables.
- Switching off single CSS files you don't understand.
- Going overboard: turning off a plugin a page still needs.
- Expecting big gains on a site that is already lean.
| SpeedLab | Before | After |
|---|---|---|
| Score | 100 | 100 |
| Largest Contentful Paint | 1.16 s | 1.14 s |
| Speed Index | 1.48 s | 1.49 s |
| First Contentful Paint | 0.95 s | 0.95 s |
| Time to Interactive | 1.13 s | 1.12 s |
| Total Blocking Time | 0.02 ms | 0.01 ms |
The SpeedLab reports
Before

After


Saved to a file, the used CSS can be cached, and the rest waits for a tap. My exclusions won't be yours: they depend on your theme and plugins. If something breaks, find the file to exclude, and if you can't, Perfmatters' support is always happy to help. The WordPress version of this site was already lean, so it gained less here than from delaying JavaScript; on a heavy page builder and theme, I'd expect far more.
Step 16: Optimise fonts
What it does: decides how fast your words appear. First choose between system fonts, the fastest option, and a custom font that matches your branding, then make that font load fast.
| Fonts | Speed | Branding |
|---|---|---|
| System | Fastest: nothing to download | The font the visitor's device already has |
| Self-hosted | Fast and preloaded, with no jump if the stand-in (fallback) font is matched | Your own font, from your site |
| Google-hosted | Slower: another server to connect to before your text shows | Your own font, from Google's servers |
What good looks like
- System fonts for the most speed. Nothing to download.
- A custom font hosted on your site, not on Google.
- For system fonts, Perfmatters turns Google Fonts off in one click.
- Perfmatters hosts Google Fonts on your site in one click.
- The one or two font files the first screen uses, preloaded.
- font-display: optional, so a late font never moves text.
- Fallback (stand-in) fonts matched to your font's size and spacing.
- WOFF2 files, cut down to the characters you use.
Where people go wrong
- Fonts loading from Google's servers on every page.
- Preloading every font file, used or not.
- A custom font with no matched fallback. The text jumps.
"Optional" sounds as if the font might not show. It means the browser waits about 100 ms for it, then uses the matched fallback font for that view, instead of swapping your font in late and moving the text around.
- Hosting fonts yourself might not help much on slow, cheap shared hosting.
- It could even slow the site down: one more reason for better hosting, step 1.

System fonts are the ones visitors already see all over their device, so they can't be preloaded: they're already there, the ultimate preload. When I first wrote this guide, I'd noticed Shopify's checkout pages using system fonts, I'd guess because they know fast pages make sales.
Part 4: Theme and plugins
What your site is built from. A lean build needs less of everything else.
Step 17: Use a lightweight theme
What it does: means less CSS and JavaScript on every page. Most themes are built for design options, not speed, and more options usually mean more and bigger files. A few get it right.
| Theme | Active installs | My experience |
|---|---|---|
| Kadence | 500,000+ | The WordPress version of this site moved to it, and Barnes and Ascent's WordPress sites run on it |
| GeneratePress | 500,000+ | This site's theme back when I first wrote this guide in 2024 |
| Blocksy | 300,000+ | I haven't used it myself, but I've heard really good things about it |
What good looks like
- A light, block-based theme like Kadence or GeneratePress.
- Design options you use turned on, and the rest left off.
Where people go wrong
- A ThemeForest theme with a million options you never use.
- Every design option turned on, whether used or not.
- A light theme with a heavy page builder loaded on top.
What else it gives you
- Faster pages for visitors.
- Less load on your server.
- Fewer clashes with your plugins.
- Usually better security as well, from its leaner code.
- A design that works on phones.
Barnes Family Roof Plumbing and Ascent Garage Doors both run on Kadence, Rocket.net and Perfmatters. In my experience, steer well clear of themes sold on ThemeForest: they come with so many options they bloat.
Step 18: Avoid heavy page builders
What it does: keeps your pages and editor light. Divi, WPBakery and Elementor often load features on pages that don't use them; the block editor with a light block plugin doesn't.
A page builder
- Divi, WPBakery, Elementor and the like
- Design features often load on pages that don't use them
- A slower editor for you, too
The block editor
- WordPress's own editor, from its Gutenberg project
- With GenerateBlocks or Kadence Blocks for layouts
- Loads only what each page uses
What good looks like
- GeneratePress with GenerateBlocks, installed together.
- Or Kadence with Kadence Blocks, installed together.
- Or just the standard block editor that comes with WordPress.
- A faster editor for you, and a faster site for your visitors.
Where people go wrong
- Unloading builder files blind. Styles and features can break.
- Testing those changes on the live site.
Keeping a page builder?
I call this polishing a turd. It helps, but a light theme and block editor fix the cause.
Step 19: Limit your plugins
What it does: cuts your server's work on every visit. Fewer plugins isn't always faster, but resource-hungry ones can slow a site badly on weak hosting, and crash it if they use it all up.
| Kind of plugin | Why it slows the site |
|---|---|
| Security scanners | Regular scans use your server's CPU |
| Backup plugins | Automatic backups run on your own server |
| Image optimisers | Some compress images on your own server, not on theirs |
| Broken link checkers | They keep scanning every page |
| Analytics dashboards | They pull reports into WordPress you could read elsewhere |
| Translation plugins | Many build pages on the fly, per visitor |
On cheap shared hosting, any of them can slow or crash a site.
What good looks like
- Only plugins your site really needs.
- Unused ones turned off and deleted.
- Leftover data checked in the database after you delete one.
- Fewer clashes between WordPress, theme and plugins.
- Less load on your server, and a faster admin area.
- A faster front end for visitors, too.
Where people go wrong
- Counting plugins instead of checking what they do.
- Deactivating a plugin but leaving it installed on the site.
- Thinking a deleted plugin is gone. Its data often isn't.
- Plugins scanning or processing in the background, nonstop.
Even plugins that aren't heavy use some of your server. When you delete one, check your database for any autoloaded data it left behind (step 24): you'd be surprised how many deleted plugins still load it on every page.
Step 20: Remove slow plugins
What it does: finds the plugins making the most database queries (requests for stored data) or using the most CPU, your server's processing power, then removes or swaps them for faster ones. It matters most on cheap hosting with low limits.

What good looks like
- Query Monitor installed to find slow plugins and errors.
- Notices, deprecated warnings and slow queries checked first.
- All caching off while you check, object caching too.
- Queries by Component, under Database Queries, sorted by time.
- Any plugin taking over 0.05 seconds looked at closely.
- Any plugin much slower than the rest looked at too.
- Queries by Caller for the detail behind each one.
- Analytics read in Google Analytics, not in WordPress.
- Scanners like Broken Link Checker run once, then removed.
- Plugin and theme features you don't use switched off.
Where people go wrong
- Checking queries with caching on. Most queries hide.
- Analytics dashboards inside WordPress you never need.
- Scanners like Wordfence running all day, every day.
- Language plugins and others that build pages on the fly.
With object caching on, that same post loaded queries from just two plugins, Get Lasso and Novashare, which is why you check with object caching turned off. FacetWP has a good Query Monitor guide for speeding up a site.
To go further, use application performance monitoring (APM), like New Relic, to see where each page load spends its time. Some managed hosts, like WP Engine, can turn it on for you: ask yours, or see my WordPress hosting guide.
Or use New Relic's WordPress quickstart yourself: the first 100 GB of data each month is free.
Step 21: Use quality plugins
What it does: starts you on plugins built with speed in mind, so there's less to fix later. Look for ones that are lightweight, not crammed with features, free of ads and easy on the CPU.
| Job | My pick |
|---|---|
| Speed | Perfmatters (step 22) |
| Social sharing | Novashare |
| SEO | The SEO Framework in 2024. Slim SEO on the last WordPress sites I built |
| Theme | Kadence, GeneratePress or Blocksy, all light themes (step 17) |
| Comments | WordPress's own comments, no plugin |
What good looks like
- Lightweight, with only the features that you actually need.
- No ads in your WordPress dashboard.
- Easy on your server's CPU.
- Updated recently and tested with your WordPress.
- Plenty of active installs and good ratings on WordPress.org.
Where people go wrong
- A plugin packed with features that you'll never use.
- One that hasn't been updated in a long time, or ever.
- Trusting any plugin: WordPress says quality varies.
Knowing what to look for doesn't make light plugins easy to find, so these are the ones I picked where most choices are bloated. Ascent Garage Doors runs Slim SEO, the plugin that sets its page titles and descriptions.
Step 22: Use Perfmatters
What it does: does much of this guide from one plugin. I highly recommend it: most of the sites I host run it, and most of the settings on this page are in it, from scripts to fonts.
| Feature | What it does | Steps |
|---|---|---|
| Features | Turns off unused extras, like Dashicons (admin icons), XML-RPC and jQuery Migrate | 26 |
| Login URL | Changes the login address, for sites not behind Cloudflare | 27 |
| Snippets | Header, body or footer code: tracking scripts, email marketing popups | 14 |
| JavaScript | Delays, defers and minifies scripts | 14 |
| CSS | Removes unused CSS and minifies the rest | 15 |
| Script Manager | Turns plugins and files off on pages that don't need them | 14, 15 |
| Fonts | Hosts Google Fonts on your own site, or turns them off completely | 16 |
| Lazy loading | Images, videos and embeds (iframes), lazy-loaded as the visitor scrolls near | 12 |
| Preloads | Images, videos, fonts, audio and other files above the fold, first | 12, 16 |
| Database | Cleans it up daily, weekly or monthly, whichever you like | 24 |
| Heartbeat | Tames Heartbeat and limits revisions | 25 |
| WooCommerce | Its scripts and cart fragments | 31, 32 |
What good looks like
- One plugin for scripts, CSS, fonts, preloads and more.
- Database clean-ups on a schedule. I did mine monthly.
- Help from the two founders, Brett and Brian Jackson.
- A 30-day money-back guarantee if you change your mind.
Where people go wrong
- Turning everything on at once without testing as you go.
- Copying settings from another site exactly as they are.
- Delay and unused CSS on, with no exclusions checked.
Not sure about a setting, or one's causing trouble? Brett and Brian at Perfmatters give great support, and they're usually happy to set the plugin up for you too. Brian Jackson linked here from his newsletter in February 2024, calling it "an excellent post on how to speed up WordPress".
Step 23: Keep your software updated
What it does: keeps WordPress, your theme and your plugins current. New versions often bring speed and security fixes, and updates are essential for WordPress security too.
The safe order for updates
- 1Back up firstA server backup, before anything changes
- 2Update on stagingA copy of the site, so the live one is safe
- 3Test itKey pages, forms and checkout
- 4Update livePush the copy, or run the same updates
- 5Test againSend the forms, click the key pages
What good looks like
- Updates run once a month, not the moment each one lands.
- A couple of weeks after a release, so others find the bugs.
- A backup before every update, staging copy included.
- Updates on a staging copy first, and then the live site.
- Run by hand, so you can see exactly what changed.
- Forms tested and key pages clicked through after.
Where people go wrong
- Updating a plugin marked "Untested with your version" blind.
- Trusting less-known or newly sold plugins, often full of extras.
- Automatic updates that nobody checks afterwards.
- Visual checks that don't test your forms or emails.
Why monthly? Quality plugins are tested with WordPress, not with your theme and every other plugin. A clash often needs another update, which waits for someone to report it, so waiting two weeks or so usually saves the headache.
Automatic updates with visual checks can miss a broken form, and by the time you find out, you've likely lost a customer already. The key pages are your home page, service pages and contact page, plus any shop or blog.
Part 5: Database and admin
The back end you work in, and the settings behind every page. Steps 28 to 30 matter on sites with hundreds of posts.
Step 24: Clean up your database
What it does: removes data WordPress loads for no reason. A new, lean site won't gain much; one that's years old, rebuilt or full of plugin trials usually will, its back end most.
Autoload check in SQL
SELECT 'autoloaded data in KiB' AS name,ROUND(SUM(LENGTH(option_value)) / 1024)AS valueFROM wp_optionsWHERE autoload IN('yes', 'on', 'auto-on', 'auto')UNIONSELECT 'autoloaded data count', COUNT(*)FROM wp_optionsWHERE autoload IN('yes', 'on', 'auto-on', 'auto')UNION(SELECT option_name,LENGTH(option_value)FROM wp_optionsWHERE autoload IN('yes', 'on', 'auto-on', 'auto')ORDER BY LENGTH(option_value)DESC LIMIT 30)Every option in the wp_options table can be set to autoload, which loads it on every page. New options over 150 KB no longer autoload unless a plugin asks for it, but you'll still find autoloaded options from plugins you deleted long ago. The easy way to check is Autoload Checker: it's free, and easier than SQL. I've used it only once, for this guide; delete it when you're done. For more detail, Kinsta has a longer guide to autoloaded data.

What good looks like
- Autoloaded data first, the biggest win on a bloated site.
- Under 800 KB: Site Health warns above that, since 6.6.
- Options from deleted plugins dropped, in phpMyAdmin.
- Deleted plugins' tables too (WP-Optimize was my 2024 pick).
- Old revisions deleted, which mostly frees up space.
- Revisions limited: 5 on my old site, 15 on Ascent's.
- Expired transients, auto drafts, trash and spam cleared.
- A full backup before any change.
Where people go wrong
- Deleting an unknown option. Search its name, or leave it alone.
- Touching the database without taking a full backup first.
- An old query that misses the newer autoload values.
Revisions are the earlier versions WordPress keeps each time you update a page. I raised Ascent's limit from 5 to 15 after four rounds of changes to one page in a day left only one earlier version to go back to. Perfmatters can also clear old revisions on a schedule, with auto drafts, trashed posts, spam and trashed comments, and all transients, the temporary data WordPress and plugins store.
Step 25: Tame the Heartbeat API
What it does: cuts the background requests WordPress makes while you're logged in. Heartbeat saves drafts, locks a post someone else is editing and shows live dashboard stats, and every beat uses CPU, which cheap shared hosting lacks.
| Setting | WordPress | My advice | Old site, 2024 |
|---|---|---|---|
| Where it runs | No setting | Only when editing | Only when editing |
| How often | 15 to 120 s | 60 s | 15 s |
| Autosave | 60 s | 2 min or more | 2 min |
What good looks like
- Heartbeat on only while editing posts and pages.
- Its frequency raised from every 15 seconds to every 60.
- Autosave every 2 minutes or more, not every 60 seconds.
- All three set in Perfmatters.
Where people go wrong
- Heartbeat running on the front end for nothing.
- Turning it off everywhere, autosaves and post locks too.
- Leaving it running at full speed on low-powered hosting.

Step 26: Remove admin bloat
What it does: speeds up your WordPress back end by switching off admin features you don't use, with a plugin like Disable Bloat for WordPress & WooCommerce, which has a free version.
| Section | What I turned on |
|---|---|
| Admin panel | Hide the update notice from any users who aren't admins |
| Site performance | Load the comments script only if needed |
| Site performance | Stop URLs in comments turning into links |
| WordPress core | Turn off automatic theme updates |
| WordPress core | Turn off automatic plugin updates |
| Other plugins | Remove the Jetpack install notice |
What good looks like
- Disable Bloat's free version, which covers the basics.
- Update notices hidden from users who aren't admins.
- The comments script only where comments show.
- Automatic updates off, if you update by hand monthly.
- Perfmatters for Dashicons, XML-RPC and jQuery Migrate.
Where people go wrong
- Switching off a feature without knowing what uses it.
- Automatic updates off, and then nobody doing the updates.
- Expecting the free version to do it all. It's limited.
- Dashicons: the icons in the WordPress admin.
- XML-RPC: an old way for other apps to post to your WordPress site.
- jQuery Migrate: a script that keeps older jQuery code working.
Step 27: Optimise your settings
What it does: fine-tunes WordPress with a few settings I change on most sites, and clears out what you're no longer using, like old themes and plugins you've left installed.
| Setting | Wording | My choice |
|---|---|---|
| Notify blogs | "Attempt to notify any blogs linked to from the article" | Off |
| Pingbacks | "Allow link notifications from other blogs (pingbacks and trackbacks)" | Off |
| Avatars | "Don't show Avatars" | On, if you have no comments or authors |
| Approval | "An administrator must always approve the comment" | On |
WordPress says a post with many links slows publishing while it notifies every site.
What good looks like
- Pingbacks off, both ways: to other blogs and from them.
- Avatars turned off if you have no comments or authors.
- Comments approved by hand, so they stay under control.
- Unused themes and plugins removed.
- A custom login URL, like /custom, not /wp-login.php.
Where people go wrong
- The standard login page wide open to password guessing.
- Pingbacks slowing down publishing a post with many links.
A custom login URL helps stop brute-force login attempts and the "429 Too Many Requests" errors they bring, and Perfmatters can set it. Behind Cloudflare, like on Rocket.net, you won't need it: Cloudflare protects a login page better, so on a host with it built in, let it do the job.
Step 28: Shorten your archive pages
What it does: speeds up blog and category pages that list hundreds or thousands of posts, by showing fewer on each page. The fewer posts a page lists, the faster it loads.
All on one page
- Hundreds or thousands of posts all loading at once
- Slow to open, slow to scroll
20 to 30 a page
- Quick to load
- Then page 2, page 3 and so on
What good looks like
- 20 to 30 posts a page, not thousands.
- Set under Settings, Reading.
- Page numbers, so browsing is easy.
Where people go wrong
- Every post on one page.
- So few posts a page that browsing becomes a chore.
Step 29: Add a search bar
What it does: cuts needless page loads on a site with hundreds or thousands of pages and posts. People search for what they want instead of clicking through page after page.
No search bar
- Visitors click through page after page
- Every page they open is another load on your server
- Some give up and go back to Google
A search bar
- One search, one page of results
- Far fewer page loads
- They find the post and stay
What good looks like
- A simple search bar where visitors look for posts.
- Fewer page loads, which means less load on your server.
Where people go wrong
- Endless clicking through archives to find one post.
- Visitors who give up and pick a competitor on Google.
Step 30: Paginate your comments
What it does: keeps posts with hundreds or thousands of comments fast, by splitting the comments into pages, so each load carries a few dozen of them rather than thousands.
Every comment
- Thousands of comments in every load
- The post slows down as it gets popular
30 a page
- "Break comments into pages", under Settings, Discussion
- The rest a click away
What good looks like
- Comments in pages, say 30 a page.
- Set under Settings, Discussion.
Part 6: WooCommerce
For stores only. A shop's scripts belong on its shop pages.
Step 31: Limit WooCommerce scripts
What it does: stops WooCommerce's scripts loading on pages that don't sell anything. Your home, about and blog pages don't need them, only product, cart, checkout and similar pages.
Where its scripts load
Still loads on
- Product
- Cart
- Checkout
- Account
- Category
- Shop
Switched off on
- Home
- About
- Blog
- Contact
What good looks like
- Perfmatters' WooCommerce Disable Scripts setting on.
- Or Script Manager, page by page, for finer control.
- Add to cart, the cart and checkout tested afterwards.
Where people go wrong
- A cart icon in the header that breaks without its scripts.
- No test order after the change.

- You'll find Disable Scripts under Perfmatters, then General, then WooCommerce.
- Husky Gifts ran a store back then, and I had it on and left cart fragments alone.
Step 32: Sort out cart fragments
What it does: deals with "Get Refreshed Fragments", which updates the cart count without a reload. It was known for slowing stores down; WooCommerce changed where it loads in 2023.
Before version 7.8
- Cart fragments loaded on every page
- An extra request on every page, even with an empty cart
From 7.8, June 2023
- Mainly where the Cart widget shows
- Or anywhere a plugin or your own code asks for it
- The Mini-Cart block doesn't use it at all
What good looks like
- WooCommerce 7.8 or later, which no longer loads it everywhere.
- WooCommerce's Mini-Cart block, which doesn't use it.
- Already delaying all scripts? You won't need to turn it off.
Where people go wrong
- Turning it off while your header still shows a cart count.
- Old advice written for WooCommerce before 7.8.
- Perfmatters can turn it off, but I'd rather delay just that script, cart-fragments.min.js.
- If you do turn it off completely, in Perfmatters or with your own code, turn on WooCommerce's option to send shoppers to the cart after adding, so they're not left wondering why the cart count on the page didn't move.
Slow back end, forms, imports or checkout?
The steps that matter most for each, with the settings I use.
Slow back end
Slow forms
- Better hosting and Object Cache Pro, steps 1 and 10
- A light theme and only a few plugins, steps 17 and 19
- Plugins the form doesn't need switched off, step 14
- A clean database, step 24
- Perfmatters and the Disable Bloat plugin, steps 22 and 26
- The latest PHP, step 3
- MariaDB, my pick over MySQL
- WP_MEMORY_LIMIT set to 256M or more, as in step 5
- PHP limits raised, as in the table below
Slow imports
- A host with more CPU and RAM, step 1
- WP_MAX_MEMORY_LIMIT, like 512M
- max_execution_time and max_input_time, like 600 s
- max_input_vars, like 100000
- upload_max_filesize and post_max_size bigger than your file
Slow checkout
- Better hosting and Object Cache Pro, steps 1 and 10
- Only plugins your store needs, step 19
- A light theme, step 17
- Plugins the checkout doesn't need switched off, step 31
- A clean database, step 24
- Perfmatters and the Disable Bloat plugin, steps 22 and 26
- The latest PHP, step 3
- MariaDB, my pick over MySQL
- WP_MEMORY_LIMIT set to 256M or more, as in step 5
- PHP limits raised, as in the table below
On the checkout page itself
- A simple checkout page, with no sidebar beside the form.
- A review or testimonial nearby, but not too many.
- No social media widgets.
- Only the form fields you really need.
| Setting | PHP default | For imports | Husky Gifts | Old site, 2024 |
|---|---|---|---|---|
| max_input_vars | 1000 | 100000 | 100000 | 100000 |
| max_input_time | -1 (uses max_execution_time) | 600 s | 600 s | 30 s |
| max_execution_time | 30 s | 600 s | 600 s | 60 s |
| upload_max_filesize | 2M | Bigger than the file | ||
| post_max_size | 8M | Bigger than the file | ||
| WP_MAX_MEMORY_LIMIT | 256M (WordPress) | 512M | 1GB |
- max_execution_time caps how long a script runs, max_input_time how long it reads input, and max_input_vars how many fields it takes.
- Tools, Site Health, Info, Media handling shows your largest upload and post sizes.
- If imports still crawl with these set, the server itself is short of CPU or RAM.
What it costs
Doing it yourself costs mostly time. Cloudflare's DNS is free, Perfmatters starts at US$29.95 a year and Rocket.net at US$30 a month. Budget for a staging copy, a backup before every change and plenty of testing after each one.
If you'd rather hand it over, I look after speed through Website Care. I don't sell speed work on its own. The WordPress sites I host run on Rocket.net with Cloudflare, most with Perfmatters. Every site gets monthly updates with a backup first and the forms tested after, and I track its speed in Google PageSpeed Insights and keep it fast. Act Fast Plumbing's site loaded in about a second after I sped it up, in my June 2023 GTmetrix test. Website Care is from $120 a month + GST with hosting, or $95 a month + GST on yours. Website Care Plus, for sites that take payments, bookings or logins, is from $220 a month + GST.
If your site's built on a heavy page builder, fixing the cause means a light theme and the block editor, step 18, and that's a rebuild. A new website starts from $5,000 + GST, then goes onto Essentials or Growth, my monthly plans, which both include Website Care.
| Part | Do it yourself? |
|---|---|
| 1. Server and hostingPicking a host, yes. Setup is your host's job | Partly |
| 2. Caching and CDNCaching layers and a CDN that work together | Usually not |
| 3. Images, scripts, fontsImages, yes. Scripts and CSS need testing | Partly |
| 4. Theme and pluginsA theme and plugins, plus monthly updates | Yes |
| 5. Database and adminSettings, yes. The database needs care | Partly |
| 6. WooCommerceTest orders after every change to checkout | Usually not |
Spotting good speed work
Your host, a developer or me on Website Care: this is what I'd look for.
| A warning sign | A good sign |
|---|---|
| Shows one score from one test | Tests a few times on a phone, page by page, not once |
| Promises a perfect 100 or a ranking | Goes by real users' Core Web Vitals |
| Stacks several caching plugins | One tool per job, working together |
| Changes your live site first | Backs up and tests on staging first |
| Lazy-loads the hero image | Preloads what shows first, at high priority, never lazy |
| Breaks enquiry tracking to win speed | Keeps every form and phone tap counted, the first tap included |
How I look after WordPress sites: Website Care.
More speed questions
Why is my WordPress site slow?
Usually the hosting first, then a heavy theme or page builder, big images and a pile of scripts loading before anyone taps. Measure first, then work through the parts in order, starting with the server in part 1.
Do I need a score of 100?
No. My home page scored 100 in SpeedLab when I first wrote this guide, and it looks good, but it's a lab test. What counts is real visitors passing Core Web Vitals. I still make sites as fast as I can, because a fast site is nicer to use.
Do I need a CDN if my customers are all in Australia?
Yes, though an Australian server matters most. With full-page caching, a CDN serves pages from near your visitors, and its firewall eases your server's load. Cloudflare is in seven Australian cities, Perth to Hobart, but when I tested its Free and Pro plans, pages came from Singapore. That's why Rocket.net, with Cloudflare Enterprise built in, is first on my caching list in step 11: Enterprise traffic is served first when Cloudflare is busy.
Can you speed up my site?
Yes, through Website Care, as I don't sell speed work as a one-off job. With my hosting, your site moves onto Rocket.net, which is step 1 and matters most, and most of the sites I host run Perfmatters too. Then I track it in Google PageSpeed Insights and keep it fast. If it's built on a heavy page builder, fixing the cause means a rebuild, and that's a new website, from $5,000 + GST.
Written by Max Jacobs
I'm a civil engineer turned web designer, based in Geelong, VIC. I've built websites and run marketing since 2015, and I don't hand the work to juniors: the person you email does it.
Hand it over to me?
Website Care, with hosting and Google PageSpeed Insights checks, from $120 a month + GST.
Start your enquiryI check your site first.

