Speed up a slow server response
Fix slow responses, large pages and missing compression with caching, a current PHP version and sensible headers.

On this page
The health check times how long your server takes to deliver the page's HTML. Under 800 ms is good; over 2 seconds means visitors wait before anything appears.
1. Turn on page caching
Caching saves a ready-made copy of each page so the server doesn't rebuild it for every visitor.
- WordPress on Enet: install LiteSpeed Cache and enable it — usually the biggest single win. See speed up WordPress.
- Other PHP apps: use the app's built-in cache, or a reverse proxy cache.
2. Compress pages
Compressed HTML, CSS and JavaScript are typically 70% smaller.
- In cPanel open Software → Optimize Website and choose Compress All Content.
- Or add to
.htaccess:
<IfModule mod_deflate.c>
AddOutputFilterByType DEFLATE text/html text/css application/javascript application/json image/svg+xml
</IfModule>LiteSpeed servers also support Brotli automatically when compression is on.
3. Use a current PHP version
New PHP releases are much faster. Switch in PHP settings — test your site afterwards.
4. Slim the page
- HTML over 200 KB usually means inline scripts, page-builder bloat or huge menus.
- Remove plugins you don't use, and clean up old revisions and spam comments in the database.
5. Cache static files in the browser
<IfModule mod_expires.c>
ExpiresActive On
ExpiresByType image/webp "access plus 6 months"
ExpiresByType text/css "access plus 1 month"
ExpiresByType application/javascript "access plus 1 month"
</IfModule>Page status 5xx?
A 500, 502 or 503 means the server failed to build the page — see fix a 500 internal server error.
Was this article helpful?
Your vote helps us write better guides.
