Start by measuring
Before changing anything, run your site through PageSpeed Insights and note the scores. According to web.dev, the metrics are Largest Contentful Paint (loading), Interaction to Next Paint (responsiveness) and Cumulative Layout Shift (visual stability). The commonly used "good" targets are:
| Metric | What it measures | Good |
|---|---|---|
| LCP | How fast the main content appears | 2.5 seconds or less |
| INP | How quickly the page responds to taps and clicks | 200 ms or less |
| CLS | How much the layout jumps around | 0.1 or less |
Test your homepage and busiest inner page on mobile, which is what most Indian visitors use.
1. Turn on page caching
The single biggest win. Without caching, WordPress runs PHP and queries the database on every visit; with it, a ready-made page goes out.
On a LiteSpeed host, use the free LiteSpeed Cache plugin; its documentation explains that LSCache works at server level, making it faster than PHP-based caching. Elsewhere, use one standard caching plugin, never two.
2. Shrink your images
Large images are the most common reason for a poor LCP score.
- Resize images to the size they're displayed at (a 4000px photo in an 800px slot is wasted data)
- Compress them and serve WebP where possible
- Lazy-load images below the fold, but not your main hero image, or it will load late and hurt LCP
- Set width and height on images so the layout doesn't jump, which helps CLS
3. Use a supported PHP version
Newer PHP versions are faster and still get security fixes. The official PHP supported versions page shows each branch gets active support and then security-only support before reaching end of life. PHP 8.1 reached end of life on 31 December 2025, so if you're on 8.1 or older, switch to a supported version from your hosting control panel. Test on a staging copy first if your site uses older plugins.
4. Cut down plugins
Every active plugin can add code to every page. Ask of each one:
- Do I still use this?
- Does another plugin already do the same thing?
- Does it load scripts on pages that don't need them?
Delete what you don't need. Swapping a heavy theme for a lightweight one often beats any tweak.
5. Clean the database
WordPress piles up post revisions, spam comments, expired transients and leftover plugin tables. A cleanup plugin, or the tool inside LiteSpeed Cache, removes them. Back up first.
6. Set browser caching and use a CDN
Browser caching tells returning visitors' browsers to reuse files like images and CSS instead of downloading them again. cPanel's advanced WordPress optimisation guide shows how to add expiry rules in .htaccess, and also suggests using a CDN. Caching plugins often handle this for you.
7. Check your resource usage
On shared hosting, your account has limits for CPU, memory and simultaneous processes. If pages are slow only at busy times, open Resource Usage in cPanel. If you're regularly hitting limits even after caching, it may be time for a bigger plan. Our post on when to upgrade from shared hosting to a VPS explains the signs.
Quick checklist
- One page caching plugin, turned on
- Images resized, compressed and in WebP
- Hero image not lazy-loaded
- Supported PHP version
- Unused plugins removed
- Database cleaned after a backup
- Retest with PageSpeed Insights
WhyShared's shared hosting runs WordPress on LiteSpeed with LSCache and NVMe storage in Singapore, covering the server side. The steps above handle the rest.
Frequently asked questions
Can WordPress be fast on shared hosting?
Yes. With page caching, optimised images and a lean set of plugins, WordPress on good shared hosting can load quickly for most traffic levels.
Which caching plugin should I use?
If your host uses LiteSpeed, use LiteSpeed Cache. Otherwise pick one well-maintained caching plugin and don't stack several.
Why is my WordPress admin slow but the site is fast?
The admin area isn't cached, so it depends on PHP, database speed and your plugins. Heavy plugins and old PHP versions are the usual culprits.
Does a CDN help Indian visitors?
It helps most when visitors are spread across regions or countries. If your server is already in India and your audience is local, caching and image optimisation usually matter more.