Speed Up WordPress on Shared Hosting: 10 Proven Methods

WordPress is flexible and easy to use, but as your site grows — more plugins, more images, more content — page load times tend to creep upward. This guide covers 10 practical methods to speed up WordPress on shared hosting that you can implement yourself without a developer, each producing measurable improvements on Google PageSpeed Insights.

Why WordPress Slows Down

Understanding the root causes helps you prioritize the right fixes. The most common culprits are:

• Too many plugins — every active plugin loads PHP code on every request. Poorly coded plugins can trigger dozens of extra database queries per page load.
• No caching — WordPress processes PHP and queries the database on every page view by default. Without a cache layer, every visitor triggers a full server computation.
• Unoptimized images — uploading camera photos directly at 3–5 MB each is the single most common cause of high page load times.
• Old PHP version — PHP 7.4 still running on many servers is significantly slower than PHP 8.1+ across every benchmark test.
• Heavy themes loading excess CSS/JS — some themes load dozens of scripts and stylesheets that create render-blocking resources on every page.

Measure First: Establish a Baseline

Before making any changes, record your current scores so you can measure the improvement from each step. The two recommended tools:

Record your LCP (Largest Contentful Paint), TTFB (Time to First Byte), and Total Page Size as your baseline. The goal is to reach LCP below 2.5 seconds — Google's "Good" threshold for Core Web Vitals, which directly influences search rankings.

1. Upgrade PHP to 8.1 or Higher

The PHP version running on your server has a direct impact on how fast WordPress processes each request. Benchmarks from Phoronix and Kinsta consistently show PHP 8.1 delivering 25–47% faster WordPress workloads compared to PHP 7.4, with PHP 8.2 and 8.3 offering further improvements.

On AsiaGB hosting with DirectAdmin, you can switch PHP versions in under one minute without contacting support:

If a plugin is incompatible with PHP 8.x, you will see a visible error right after switching — update that plugin or find a modern alternative before proceeding.

2. Install a Caching Plugin

A caching plugin is the single highest-impact change you can make to a WordPress site on shared hosting. Instead of processing PHP and querying the database for every visitor, the plugin saves the rendered output as a static HTML file and delivers it directly — dramatically reducing server load and response time.

W3 Total Cache

The most feature-complete free caching plugin available, supporting Page Cache, Object Cache, Database Cache, Browser Cache, Minification, and CDN integration all in one place. Best for users who want full control, though initial configuration takes more time than simpler alternatives.

LiteSpeed Cache

If your hosting runs the LiteSpeed web server (available on certain AsiaGB plans), LiteSpeed Cache operates at the native server level rather than just the PHP layer — making it measurably faster than W3 Total Cache and significantly easier to configure. Install it first if LiteSpeed is available.

3. Optimize Images: WebP and Compress Before Uploading

Images typically account for 50–80% of total page weight on a typical WordPress site. Optimizing images before upload delivers the most immediate and visible improvement in PageSpeed scores.

Compress Before Uploading with Squoosh or TinyPNG

Squoosh (squoosh.app) is a free web app from Google that lets you compress and convert images to WebP with no software installation required. TinyPNG (tinypng.com) is even simpler — drag and drop your files, download the results. Both reduce image sizes by 40–80% with no perceptible quality loss.

WebP Format

WebP is Google's image format that produces files 25–35% smaller than JPEG at equivalent visual quality. All modern browsers support WebP. Plugins like ShortPixel, Smush, or Imagify can convert your existing image library to WebP automatically and serve it to supported browsers with a JPEG fallback for older ones.

• Always compress images with Squoosh or TinyPNG before every upload
• Resize images to the display size before uploading — never upload a 4K image for an 800px display slot
• Lazy loading is enabled by default in WordPress 5.5+ — verify it is active under Settings → Media
• Use ShortPixel or Imagify to bulk-convert your existing image library to WebP

4. Remove Unnecessary Plugins

The rule is simple: every plugin is overhead, without exception. Even well-written plugins still load additional PHP code on every request. A poorly coded plugin can add 0.5–2 seconds to load time on its own.

How to identify and remove resource-heavy plugins:

• Install the free Query Monitor plugin to see database queries, PHP errors, and hook timing broken down per plugin
• Deactivate plugins one at a time and measure load time in GTmetrix to identify the worst offenders
• Delete plugins you are not using — a deactivated plugin still takes up disk space, even if it no longer loads code
• Security scanners, social share buttons, sliders, and page builders are typically the highest resource consumers; look for lighter alternatives

5. Use a CDN: Cloudflare Free Plan

A CDN (Content Delivery Network) is a global network of servers that caches your site's static files — images, CSS, JS — close to your visitors. Instead of every request reaching your server in Thailand, visitors in Europe or the US load those assets from a nearby server, dramatically reducing latency for international traffic.

Connecting Cloudflare to WordPress on AsiaGB

1. Sign up for a free Cloudflare account at cloudflare.com
2. Add your domain to Cloudflare and update your nameservers at your registrar to point to Cloudflare's nameservers
3. Wait for DNS propagation — typically 24–48 hours
4. Install the official "Cloudflare" plugin in WordPress and connect your account
5. Enable "Rocket Loader" and "Auto Minify" for JS, CSS, and HTML in the Cloudflare dashboard

Cloudflare's free plan also includes a free SSL certificate, basic DDoS protection, and full DNS management — making it the most valuable free tool available for WordPress on shared hosting.

6. Enable Gzip/Brotli Compression via .htaccess

Compression reduces the size of HTML, CSS, and JavaScript sent from the server to the browser by 60–80% with no impact on content quality. The browser decompresses the data automatically. Add the following code to your .htaccess file at the WordPress root (accessible via DirectAdmin's File Manager):

# Enable Gzip Compression
<IfModule mod_deflate.c>
  AddOutputFilterByType DEFLATE text/html text/plain text/xml
  AddOutputFilterByType DEFLATE text/css text/javascript
  AddOutputFilterByType DEFLATE application/javascript application/x-javascript
  AddOutputFilterByType DEFLATE application/json application/xml
  AddOutputFilterByType DEFLATE image/svg+xml
</IfModule>

# Enable Brotli (if server supports it)
<IfModule mod_brotli.c>
  AddOutputFilterByType BROTLI_COMPRESS text/html text/css application/javascript
</IfModule>

Verify that Gzip is active after saving .htaccess using gzipwtf.com or tools.pingdom.com.

7. Reduce Render-Blocking JS/CSS with defer and async

Synchronous JavaScript blocks the browser from rendering the page until that script fully loads and executes — leaving visitors staring at a blank or partially loaded screen. Using defer or async attributes eliminates this bottleneck.

defer vs async — which to use

• defer — downloads the script in parallel with HTML parsing, but waits to execute until parsing is complete. Use for scripts that depend on the DOM, such as analytics or sliders.
• async — downloads and executes the script immediately when loaded, regardless of HTML parsing state. Use for independent scripts such as ads or tracking pixels.

In WordPress, avoid editing script tags directly since updates will overwrite your changes. Use a plugin instead:

• Autoptimize — adds async/defer to JS, plus minification and concatenation
• WP Rocket (premium) — the easiest and most comprehensive option for non-technical users
• Asset CleanUp — granular per-page control over which scripts and styles load on each page

8. Database Optimization with WP-Optimize

Over time, the WordPress database accumulates significant overhead: post revisions, trashed items, expired transients, spam comments, and orphaned metadata. None of this is needed for your live site, but it slows down database queries and increases the database size unnecessarily.

Additionally, limit post revisions from the start by adding this line to wp-config.php:

// Limit post revisions to 3 versions per post
define('WP_POST_REVISIONS', 3);

9. Choose Hosting with SSD and PHP-FPM

All the optimizations above have limited effect if your hosting infrastructure relies on old HDD storage or runs PHP in CGI mode instead of PHP-FPM. The server's underlying hardware and configuration directly determines TTFB — the foundation of every page load.

• SSD storage — reads and writes data 3–5 times faster than HDD, directly reducing TTFB on every database query and file read
• PHP-FPM (FastCGI Process Manager) — manages PHP processes more efficiently than standard CGI, handles more concurrent requests, and uses less memory per request
• PHP 8.1+ support — the hosting control panel must allow you to select modern PHP versions
• Server location in Thailand or Asia — reduces latency for Thai visitors compared to servers hosted in Europe or the US

AsiaGB uses SSD storage on every server, supports PHP 8.1 / 8.2 / 8.3 via PHP-FPM, and hosts servers in Thailand — giving Thai visitors measurably lower TTFB compared to hosting providers using overseas infrastructure.

10. Measure Results and Set Performance Goals

After completing all optimization steps, re-run both Google PageSpeed Insights and GTmetrix and compare against your initial baseline. Target the following benchmarks:

Summary: Your WordPress Speed Checklist

You do not need to implement everything at once. Start with the highest-impact changes and work down the list, measuring after each step:

1. Measure baseline with PageSpeed Insights and GTmetrix
2. Upgrade PHP to 8.1 or 8.2 in DirectAdmin
3. Install LiteSpeed Cache or W3 Total Cache
4. Compress images and convert to WebP
5. Connect Cloudflare CDN
6. Enable Gzip compression in .htaccess
7. Remove unnecessary plugins
8. Add defer/async to JavaScript
9. Run WP-Optimize to clean the database
10. Measure again — target LCP below 2.5 seconds

A faster WordPress site does not just improve user experience — it directly improves your SEO ranking, lowers bounce rate, and increases conversion rate. The time invested in a single WordPress optimization session pays long-term dividends that compound over every subsequent visitor.