How To Improve Server Response Time On Bluehost’s WordPress Hosting: A Common Item In Your Google PageSpeed Insights Report

Home » WordPress Hosting » How To Improve Server Response Time On Bluehost’s WordPress Hosting: A Common Item In Your Google PageSpeed Insights Report

Bluehost is infamous for slow server response times.

You can measure this in Google PageSpeed Insights or Bitcatcha, and Google recommends your server response time be under 200ms. Any higher than 1-2s and you’ve got a problem.

You can fix slow server response times on Bluehost by: configuring a cache plugin, avoiding high CPU plugins, using a CDN, cleaning your database, optimizing images, deleting unused plugins, using the Blackhole For Bad Bots plugin to stop spam bots, Heartbeat Control plugin, and making sure your hosting plan has enough server resources to handle your traffic/plugins.

Is Bluehost the problem? Probably… they’re owned by EIG who is known for cutting costs by packing too many people on the same server. At the end of the day, they’re known for being cheap (not fast). They are also rated poorly in Facebook polls. Try joining the WordPress Hosting Facebook Group and see what real, unbiased people are recommending for hosting. There are much better options than Bluehost. I use SiteGround and have 200ms response times, 100% GTmetrix scores, and .4s Pingdom load times. The reports speak for themselves.


1. Check Server Response Times

Check your own server response times using Bitcatcha. That’s mine… hehe.

Bitcatcha Server Speed Report

Or use Google PageSpeed Insights:

Reduce Server Response Time

As long as you’re with Bluehost, you are not alone:

Bluehost slow server response time

Slow Bluehost Server Response Time

Bluehost Server Response Time

Bluehost Crap Server Response Time

Bluehost Server Response Times



2. Upgrade To PHP 7+

Upgrading to a higher PHP version (in your cPanel) is one of the easiest ways to make your website faster, while also reducing server response times. Bluehost now supports PHP 7.2.

WordPress PHP Benchmarks


Bluehost Update PHP Version


3. Avoid High CPU Plugins

Too many plugins (or just 1 single high CPU plugin) can make or break your server response time (and load time). P3 used to be great at finding slow plugins, but now Query Monitor is best. Install the plugin and go to “Queries By Component” to view slowest loading plugins.

Query Monitor Slow Plugins

You can also use the GTmetrix Waterfall tab:

Slow WordPress Plugin

*Common culprits include related post, statistic, sitemap, chat, calendar, page builders, and plugins that run ongoing scans/processes or show high CPU in GTmetrix.

  1. AddThis
  2. AdSense Click Fraud Monitoring
  3. All-In-One Event Calendar
  4. Backup Buddy
  5. Beaver Builder
  6. Better WordPress Google XML Sitemaps
  7. Broken Link checker (use Dr. Link Check)
  8. Constant Contact for WordPress
  9. Contact Form 7
  10. Contextual Related Posts
  11. Digi Auto Links
  12. Disqus Comment System
  13. Divi Builder
  14. Essential Grid
  15. View Full List Of 65 Slow Plugins


4. Avoid External Resources

External resources can come from Google Maps, Analytics, Gravatars, social sharing plugins, comment plugins, and other sources. These pull requests from external resources and will increase server response times and destroy your GTmetrix + Pingdom reports. Obviously it’s best to avoid external resources all together, but I also left some common solutions below.


Prefetch DNS Requests – if you absolutely HAVE to use external resources, prefetching them helps browser anticipate them so they can load faster. Luke created an amazing list of common domains to prefetch. Copy all these (or just the ones you need) and add them to your site (most cache plugins have an option for this). Also include your CDN URL if you’re using StackPath, KeyCDN, BunnyCDN, or another CDN (except for Cloudflare which doesn’t use CDN URLs).




5. Configure A Cache Plugin

If you’re going the free route, I recommend either Swift Performance or WP Fastest Cache, and I have tutorials for both Swift and WPFC. But if you can drop the $49, WP Rocket is much better, is what I use, and was rated the #1 cache plugin in multiple Facebook polls. But why?

WP Rocket comes with many features most cache plugins don’t. That means if you were to use most other cache plugins, you would need to install about 6 extra plugins. If you’re like me, you only want to use 1 plugin. This is why WP Rocket yields better scores + load times in GTmetrix/Pingdom (it has more features, while reducing the number of plugins on your site).

  • Database cleanup (built-in to WP Rocket, or use WP-Optimize)
  • Heartbeat control (built-in to WP Rocket, or use Heartbeat Control)
  • Lazy load images/videos (built-in to WP Rocket, or use WP YouTube Lyte)
  • Host Google Analytics locally (built-in to WP Rocket, or use CAOS For Analytics)
  • Host Google Fonts locally (built-in to WP Rocket, or use CAOS For Fonts, or SHGF)
  • Integration with Cloudflare + other CDNs (built-in to WP Rocket, or use CDN Enabler)


2016 best cache plugin poll

2019 cache plugin poll

Swift vs WP Rocket

2016 cache plugin poll

Best cache plugins 2018 poll

wp rocket vs w3 totla cache

Most people do not configure their cache plugin correctly or take full advantage of it’s features. I highly recommend looking through my tutorials to make sure your setup is ideal.


6. Clean Database

Your database can accumulate junk files like deleted comments, spam comments, post revisions, expired transients, and other things that are causing your database to be bloated.

It’s best to clean your database about once every 1-2 weeks. You can use the WP-Optimize plugin to clean it, as well as schedule ongoing database cleanups. Just make sure you take a backup of your database before doing this, especially if this is your very first time cleaning it.

WP-Optimize Clean Database

If using WP Rocket, you don’t need WP-Optimize as this is built-in:



7. Heartbeat Control

The WordPress heartbeat API shows real-time plugin notifications and that other users are editing a post. While this sounds nice, it also consumes server resources by creating a request every 15-30 seconds. Use the Heartbeat Control plugin and limit it, or disable it completely.


Heartbeat Control

If using WP Rocket, you don’t need this plugin, as this is built-in:



8. CDN

A CDN (content delivery network) offloads resources to multiple data centers around the world. This put less stress on your server, but it also reduces the geographical distance between your server and visitor, and is a recommendation in the WordPress optimization guide. I recommend using Cloudflare which is a free CDN with 200+ data centers and there’s no reason you shouldn’t be using it. Cloudflare is only available on Bluehost’s share plan, while customers with VPS or a dedicated server will need to contact Bluehost and request it.

In your Bluehost cPanel, go to Domains > Cloudflare > Activate.

Bluehost Cloudflare

Bluehost Cloudflare Activation

If you want to go the extra step, you can configure a few settings in your Cloudflare dashboard.


And if you really want to go the extra mile, you can use multiple CDNs. Each CDN has their own set of data centers, and more data centers = faster delivery of your content and will offload even more resources. I personally use both Cloudflare (free) and StackPath ($10/month with free 30-day trial).


Step 1: Sign up for StackPath.

Step 2: In the dashboard, click the CDN tab, then create a StackPath CDN site. You will walk through a series of pages where StackPath will request your domain, find your server’s IP address, then create a CDN URL which you will copy/paste into your cache plugin. Easy peasy.





Step 3: Paste your StackPath CDN URL into your cache plugin (below is for WP Rocket). If your cache plugin does not have a field for a CDN URL, use the CDN Enabler plugin instead.


Step 4: In StackPath go to CDN → Cache Settings, then click Purge Everything


Step 5: Run your site in GTmetrix and “content delivery network” should be green in YSlow.

CDN GTmetrix YSlow


9. Block Bad Bots

You will never know if spam bots are hitting your site and consuming resources, unless you check. I found 2 spammy bots ( and were constantly hitting my site about every 3 seconds – I was spending server resources on literally nothing. Obviously Googlebot is OK, but you want to prevent spam bots from consuming resources.

Step 1: Install Wordfence.

Step 2: View your live traffic report (under Wordfence’s Tools settings). Look carefully for a solid minute to see which bots are hitting your site. If they look spammy, Google their hostname and see if other people are reporting them as spam. Make a list of all the spam bots.


Step 3: Go to Wordfence’s Blocking settings and add the spam bots here. Use asterisks to make sure you’re blocking all variations of that bot, otherwise this may not be effective.


Step 4: Go to your Blocking log and enjoy watching those spam bots get blocked.


If you don’t want to use Wordfence, the Blackhole For Bad Bots plugin does this automatically:

Blackhole for Bad Bots


10. Optimize Images

There are 3 primary ways to optimize images in GTmetrix. It will only show unoptimized images for the single page you test, so be sure to run your most important pages through it.


Serve scaled images – resize large images to be smaller. GTmetrix shows you all images that are too large, and the correct dimensions they should be resized to. Locate the image on your site, resize it to the correct dimensions, upload it, and replace the old image with the new one.

Specify images dimensions – means you need to add a width/height in the image’s HTML or CSS. The main WordPress editor will do this automatically, so these errors are usually caused by images located in page builders, widgets, and other areas of your website. Simply locate the image, view the image’s HTML, then add a width/height which GTmetrix provides you with.

Optimize images – losslessly compress images using a plugin like ShortPixel. You get 100 free credits each month (this is the my favorite image compression plugin and I have tried many including Imagify, Smush, EWW, and others). Install it, grab your API key from the ShortPixel website, then configure the settings. Set the image compression level to lossless. Go to your Media tab and optimize a couple images to make sure you’re happy with the quality. If you are, bulk compress all images on your site. I recommend taking a backup beforehand, just in case.


11. Use Lightweight Plugins

If you’re running high CPU plugins that cause slow server response times, you either need to delete them, or find alternative plugins that don’t consume as many resources. Here are some lightweight plugins I suggest, though in many cases, you need to do your own research/testing. View your Query Monitor report after installing EACH plugin to see how it impacts load times.

Social Sharing – WP Rocket’s test showed Social Media Feather, MonarchSimple Share Buttons Adder, and MashShare had the least amount of requests and fastest load times.


SlidersSoliloquy, LayerSlider, or Meteor Sliders.

CommentsDisqus Conditional Load.

PortfolioEnvira Gallery, FooGallery, or The Grid.

Analytics – Google Analytics and Search Console should be plenty. Just make sure you’re hosting Google Analytics locally (using WP Rocket, CAOS, or WP Disable).

Page BuildersWordPress Page Builder by MotoPress, but no page builder runs faster than the native WordPress Editor. Combine this with the Duplicator plugin and you shouldn’t need a page builder (including page builders built-in to WordPress themes). Unless your team absolutely refuses to learn a little HTML (the easiest coding language), avoid page builders.

StudioPress Plugins – lightweight plugins for the Genesis Framework.


12. Host Google Fonts Locally

If you see Google Font errors in your GTmetrix report, it means you need to host fonts locally.


Use can use the CAOS for Webfonts plugin:


Or Self-Hosted Google Fonts plugin is a good alternative, which automatically downloads all Google Fonts you’re using and adds them to your CSS, with having to configure any settings.



13. Host Google Analytics Locally

If you see Google Analytics errors in your GTmetrix report, it means you need to host your Google Analytics tracking code locally. The CAOS Analytics plugin does this automatically.



WP Rocket also has this feature.

WP Rocket Local Analytics


14. Retest Website

Head back to Google PageSpeed Insights or Bitcatcha and retest your website’s server response time. They should be much faster, considering we hit nearly everything impacting it.



15. Switch To Faster Hosting

If your server response time is still slow, it’s most definitely caused by Bluehost.

Before upgrading to their VPS or dedicated plan, do your research and look into what experienced people are recommending in the WordPress Hosting Facebook Group. Your co-worker might have their own suggestion, but these people know what they’re talking about.

I use SiteGround and have 200ms response times with 100% GTmetrix scores and .4s Pingdom load times. Do a hosting check, run your own tests, or click through my fast loading pages. They were rated the #1 host in 26 Facebook polls and are worlds better than EIG (Bluehost, HostGator), GoDaddy, and other hosts who pack too many people on the same server. There have been plenty of people who migrated and posted results on Facebook and Twitter. Tweet after tweet, post after post, poll after poll after poll, faster hosting will fix slow response times. They’re recommended by WordPress, do free migrations, and I use their semi-dedicated plan.


Bitcatcha Server Speed Report



People usually migrate because their speed technology can improve server response times by multiple seconds. Here are a few people who migrated to SiteGround and posted their results.

Switching To SiteGround

SiteGround Load Time Migration

Bluehost to SiteGround GTmetrix

HostGator To SiteGround

SiteGround GTmetrix

SiteGround Google PageSpeed Insights

100 Perfect Score On SiteGround

SiteGround Genesis

Speed Delivered By SiteGround

SiteGround GTmetrix Report

Reduced Load Times With SiteGround

New SiteGround Response Times

HostGator To SiteGround Migration

SiteGround Response Times On Joomla

Switched To SiteGround Hosting

SiteGround Rocket Imagify Combo

Joomla GTmetrix On SiteGround

SiteGround PageSpeed Insights

SiteGround On Joomla

SiteGround Reduced Load Times

SiteGround Speedy Hosting

New Pingdom Results On SiteGround

New SiteGround Response Time

SiteGround Response Time Improvement

2019 Hosting Poll
View Poll

SiteGround has 3 plans:


Higher plans include more server resources (#1 factor in the WordPress optimization guide). Here’s the full comparison chart, but GrowBig gives you about 2x more server resources than StartUp, and GoGeek is semi-dedicated hosting which gives you even more. GrowBig and up comes with a free migration, staging, advanced caching, and ability to host multiple websites. GoGeek comes with priority support. Their cloud hosting is quite the price jump at $80/month.

You can see this on the features page


I use SiteGround because…

  1. My GTmetrixPingdom reports speak for themselves
  2. My pages load instantly (click through them if you want)
  3. Fast speed technology (PHP 7.3, NGINX, SG Optimizer, Cloudflare)
  4. Recommended by Yoast, WordPress, Ivica from WordPress Speed Up
  5. Free Let’s Encrypt SSL, easy to use cPanel, and features for eCommerce
  6. WordPress support is unbeatable even without GoGeek’s priority support
  7. GrowBig comes with staging, more storage, and more server resources (scroll down to “we allocate the resources you need” and hover over the server tab)
  8. GoGeek comes with even more server resources, storage, priority support
  9. Free migrations, migrator plugin, and a 30-day money back guarantee
  10. Plenty of praise on Reddit, Facebook conversations, Twitter, TrustPilot
  11. Tons of praise on Facebook: #1, #2, #3, #4, #5, #6, #7#8, #9, #10#11
  12. Many people already migrated and posted results on Twitter: #1, #2, #3, #4, #5, #6#7, #8, #9, #10, #11, #12, #13, #14, #15, #16, #17, #18, #19, #20, #21, #22, #23, #24, #25, #26, #27, #28, #29, #30, #31, #32, #33, #34, #35, #36, #37

Affiliate Disclaimer – if you sign up for SiteGround using my affiliate link I will donate a good chunk at no cost to you. Each year I donate $3,000 to GoFundMe campaigns (2018 was to feed the hungry in Denver, 2017 was to Red Cross at Hurricane Harvey). Your support helps and I genuinely appreciate it. Either way, I would avoid Bluehost – join some Facebook groups and see the conversations, polls, tweets, and people who migrated from Bluehost to SiteGround. I refuse to recommend EIG/Bluehost’s awful hosting. Do your research, see who Yoast is using, and results of people who migrated.


Frequently Asked Questions

✅ How do I improve server response times?

Although you can lighten the load on your server with CDNs, upgrading PHP versions, and avoiding slow plugins, your server is ultimately controlled by your hosting. Unless your website is not optimized for speed whatsoever, you really shouldn't be getting server response time errors.

✅ How do I lighten the load on my server?

Using a good cache plugin like WP Rocket, configuring it correctly (including adding a CDN), upgrading PHP versions, and avoiding resource hungry plugins and third party scripts (eg. AdSense) can help lighten the load on your server.

✅ Will cache plugins improve server speed?

Yes, they should especially if you also use them to setup a CDN. Cache plugins should improve load times, GTmetrix scores, and server response times.

✅ Do I really need to upgrade hosting?

First, optimize your site. Then if you still have slow server response times, upgrading plans or consider moving to a faster host like SiteGround or Cloudways.

✅ Is it Bluehost's fault?

Many people have reported slow servers on Bluehost some people improve their load times by over 7 seconds when moving to another host. SiteGround (shared hosting) and Cloudways (cloud hosting) are 2 popular choices and were both rated highly on Facebook.

I hope this was helpful. If you have questions, drop me a comment.


Notify of
Inline Feedbacks
View all comments