Most slow WordPress sites aren't slow because of the server. They're slow because each page loads 4 MB of images, 30 plugins' worth of scripts and three font families. The fixes are mostly free. The trick is doing them in the right order, so you don't spend an afternoon on something that saves 50 milliseconds.

Step 0: measure before you change anything

Open PageSpeed Insights, enter your home page and one important inner page (a product, a service page), and note:

  • Largest Contentful Paint (LCP) on mobile
  • The total page size and number of requests, under Diagnostics

Write these down. You'll test again after each step. If you don't know what LCP means, read Core Web Vitals in plain English first.

Also test from a phone on mobile data, not office Wi-Fi. That's how most of your Indian visitors see the site.

Step 1: turn on page caching

Without caching, WordPress builds every page from scratch: PHP runs, the database is queried, the theme assembles the HTML. With caching, the finished page is saved and served directly.

  • If your plan's cPanel shows LiteSpeed Web Cache Manager, install the free LiteSpeed Cache plugin. It's the fastest option on LiteSpeed servers.
  • Otherwise use WP Super Cache (free, simple) or WP Rocket (paid, easier).

Turn on page caching only, test, and check your site still works when logged out. Then explore other options one at a time.

Typical result: the server response time (TTFB) drops from 600–1200 ms to under 200 ms.

Step 2: fix your images

This is usually the biggest win. A photo straight from a phone is 3–5 MB. On a page that shows it at 800 pixels wide, it should be under 150 KB.

  • Resize before uploading: nothing wider than 2000 px.
  • Convert to WebP. See Optimise images for the web.
  • Make sure images below the first screen are lazy-loaded (WordPress does this by default since version 5.5).
  • Don't lazy-load the main banner image. That makes LCP worse.

Step 3: remove plugins you don't need

Go through Plugins and ask of each one: what would break if I deleted this? Common candidates:

  • Sliders on the home page (they're slow and few people look past the first slide)
  • Social sharing plugins that load scripts from five networks
  • "Under construction" or importer plugins left over from setup
  • Two plugins doing the same job (two SEO plugins, two caching plugins)

Deactivate, test the site, then delete.

Step 4: limit fonts and third-party scripts

Each Google Font family and weight is a separate download. Pick one family with two weights (regular and bold). Many themes have a setting to load fonts locally, which is faster than fetching them from Google.

Then look at scripts from other sites: chat widgets, Facebook pixel, heatmap tools, old analytics codes. Each one adds time and often runs before your content shows. Keep the ones you actually use.

Step 5: use a current PHP version

In cPanel, open Software → Select PHP Version (or MultiPHP Manager) and pick the newest version your theme and plugins support: PHP 8.2 or 8.3 at the time of writing. Newer PHP versions run WordPress noticeably faster than PHP 7.4. Test the site after switching; if anything breaks, switch back and update the plugin that broke.

Step 6: clean the database

Years of post revisions, spam comments and expired temporary data make the database bigger and some queries slower. WP-Optimize cleans this safely. Take a backup first.

When it really is the hosting

If after all this your TTFB is still high with caching on, or the site slows down only at busy times, you may be hitting your plan's CPU or memory limits. cPanel shows this under Metrics → Resource Usage. Open a ticket and send us a screenshot; we'll tell you honestly whether an upgrade would help or whether something on the site is the cause.

Stuck on a step?

Customers can open a ticket from the client area and an engineer will do it with you. Not a customer yet? Write to help@hostingdon.com or call +91 98002 55199.