WordPress

How to make WordPress fast: a PageSpeed checklist with Ninza Speed

5 min read By Cloud Ninza

A fast WordPress site is mostly three things: not running WordPress for every visit, small images, and scripts that wait their turn. Here is the order to fix them in.

In short To make WordPress fast: turn on a server page cache so most visits never start WordPress; serve images as WebP at the size they are shown; delay or defer JavaScript and remove what you do not use; load the main image first and fonts with swap; clean the database; and choose a light theme and few plugins. Ninza Speed, free on every Cloud Ninza plan, does the cache, WebP, script, font and database parts from one page, and runs Google PageSpeed tests in wp-admin.

Measure first

Test your home page and your most visited page at pagespeed.web.dev, on mobile — the score Google uses. Note the four numbers that matter: Largest Contentful Paint (main content visible, aim under 2.5 s), Interaction to Next Paint (responsiveness, under 200 ms), Cumulative Layout Shift (stability, under 0.1) and Total Blocking Time. Ninza Speed’s Speed test tab runs the same test inside wp-admin.

1. Page cache: the biggest win

Without a cache, every visit runs PHP and dozens of database queries to build a page that has not changed. With Ninza Speed’s server page cache on, nginx answers from a stored copy in milliseconds. Turn it on (Ninza Plugins → Ninza Speed → Page cache), choose 2–30 minutes for shops and news, hours for brochure sites, and keep Purge on changes and Warm up on. Logged-in users, carts, checkout and account pages are never cached.

2. Images

  • Convert to WebP: Images tab → Convert all now; new uploads are converted automatically. Typically 25–55% smaller.
  • Upload at the size shown — resize huge photos before uploading.
  • Keep Main image first on so the LCP image loads with high priority and is never lazy.
  • Give every image width and height (WordPress does for media library images) to avoid layout shift.

3. JavaScript

JavaScript usually decides the mobile score. Turn on Delay JavaScript in the Optimise tab: scripts wait for the first scroll, tap or key press (or 10 seconds). Then click through your site: the mobile menu, sliders, popups, forms, cart. If something only works after scrolling, add part of its script address to Never delay or defer. If Delay is too aggressive for your theme, use Defer instead.

  • Remove plugins you do not need — each adds scripts and styles to every page.
  • Limit third-party scripts: one analytics tool, chat widgets only where needed.
  • YouTube and Vimeo previews save about 1 MB per embedded video.

4. Fonts and CSS

  • Use one or two font families and few weights.
  • Keep Font swap on so text shows immediately.
  • Turn off unused page-builder widgets and theme modules — less CSS to download.

5. Database and server

  • Database tab: remove revisions, spam, trash and expired transients; switch on the weekly clean-up.
  • Use a current PHP version (8.3 or newer when your plugins support it) — Domains → PHP version.
  • Keep WooCommerce order and session tables healthy with its own tools.
  • Heartbeat at 60–120 seconds in wp-admin reduces background load.

6. Cloudflare and CDN

Cloudflare in front of your site serves static files from nearby locations. With a cache-purge token in Ninza Speed’s Cloudflare tab, both caches clear together. Keep SSL on Full (strict).

7. Theme choice matters most

No plugin can fully rescue a heavy theme with sliders, animations and many scripts on every page. If your mobile score stays low after the steps above, look at what PageSpeed lists under Reduce unused JavaScript and CSS — the names usually point to the theme or a builder add-on. A lightweight theme with blocks often scores far better.

After each change

  • Purge the cache (admin bar → Purge cache).
  • Test the page twice (the first test may warm the cache).
  • Click through menus, forms and checkout on a phone.
  • Note the scores so you know what helped.

What a good result looks like

With a page cache on, a cached WordPress page is usually answered by the server in well under 100 milliseconds instead of half a second to several seconds. With WebP images at the right size and delayed scripts, a light theme typically reaches green Core Web Vitals on mobile. Heavy builder themes improve a lot but may stay amber because of the amount of CSS and JavaScript they load everywhere.

WooCommerce stores

  • Product, category and home pages are cached for guests; cart, checkout and account pages never are.
  • Disable cart fragments on pages without a mini-cart if your theme allows it — it is an extra request on every page.
  • Keep product images square and consistent, converted to WebP.
  • Clean expired sessions and transients from the database regularly (Ninza Speed’s weekly clean-up).
  • Test checkout after turning on Delay JavaScript; exclude payment scripts if needed.

Page builders

Elementor, Divi and similar builders load their own scripts and styles. Turn off widgets and features you do not use in the builder’s settings, use its own performance options (such as loading CSS per page), avoid sliders above the fold, and replace heavy animated sections with simple blocks. If Delay JavaScript affects a builder’s menus or popups, add its frontend script name to Never delay or defer.

Troubleshooting

  • A change does not show: purge the cache from the admin bar; check Cloudflare is purged too.
  • Layout broken after Minify HTML: switch it off — some themes rely on whitespace.
  • Menu works only after scrolling: exclude its script from delay.
  • Score drops for a day: third-party scripts vary; test several times and look at trends.
  • See the page without optimisations: add ?ninza-speed-off to the address.

Why speed also helps SEO and AI answers

Google uses Core Web Vitals as part of its page experience signals, and on mobile the difference between a 1.5-second and a 5-second page is visible in bounce rates and conversions. Speed also affects how much of your site is crawled: a fast server lets Googlebot and Bingbot fetch more pages in the same time, so new content is found sooner. AI fetchers that read pages during an answer have short time limits; a page served from cache in milliseconds is read completely, while a slow one may be skipped.

That is why Ninza Speed and Search Master work best together: one makes every page quick to deliver, the other makes it easy to understand and quote.

Key takeaways

The short version, for anyone skimming:

  • A server page cache is the single biggest speed gain for WordPress.
  • WebP at the right size and the main image first fix most LCP problems.
  • Delay JavaScript gives the largest mobile improvement — test interactive parts after turning it on.
  • Fewer plugins, fewer third-party scripts and a light theme matter more than any setting.
  • Ninza Speed does all the settings from one page, free on every Cloud Ninza plan.
Host it with us

WordPress Hosting from ₹1,788/year

WordPress on India-hosted cloud servers, installed for you — the latest release or the version your site needs. Latest WordPress or your chosen version · PHP 8.3, 8.4 or 8.5 · Free SSL certificate.

Ready when you are

Hosting from ₹149 a month on servers in India

WordPress, static HTML, PHP, Node.js, Python and Java plans with free SSL and your choice of version. Create your account, pick a plan and pay by UPI, card or netbanking; your hosting is created automatically and you get your login by email, usually within minutes.

Questions

Questions on this topic

What is the best cache plugin for WordPress?

One that caches at the server, purges precisely and never caches logged-in users or carts. On Cloud Ninza that is Ninza Speed, free on every plan, using the nginx page cache built into our servers.

Can WordPress score 100 on PageSpeed?

Light sites often can on desktop and come close on mobile. Heavy themes and third-party scripts (chat, ads, several trackers) usually set the ceiling.

Why is my WordPress site slow?

Most often: no page cache, oversized images, too many plugins and scripts, a heavy theme or an old PHP version.

Does Delay JavaScript break sites?

It can delay something that should run at once, like a menu or reCAPTCHA. Add it to Never delay or defer, or use Defer instead.

Are WebP images supported everywhere?

All modern browsers support WebP. Ninza Speed keeps the originals for any browser that does not.

Should I use two cache plugins?

No. Two caching or optimisation plugins can conflict and break pages. Keep one.

Does the page cache affect WooCommerce?

Product and category pages are cached for guests; carts, checkout, account pages and logged-in users always get fresh pages.

Does speed affect SEO?

Yes. Page experience is a Google ranking signal, slow pages lose visitors, and AI fetchers read fast pages more completely.