How To Speed Up A Slow Website On Bluehost’s WordPress Hosting

Have a slow WordPress site on Bluehost?

To speed up a slow Bluehost website, activate Cloudflare’s CDN and use PHP 7.4 in the Bluehost cPanel. Install a cache plugin, avoid high CPU plugins, and optimize your images, database, and fonts. Most importantly, optimize for core web vitals (a ranking factor in May, 2021). Many of my recommendations will improve web vitals and PageSpeed Insights scores.

However, Bluehost is notoriously slow. They overcrowd servers and use outdated speed technology. It’s well-known in the WordPress Facebook Hosting Group which I suggest joining. It’s a great place to get unbiased hosting feedback from knowledgeable people in this industry.

There’s an easy way to tell if Bluehost is slow: run your website through PageSpeed Insights to see if reduce server response time is in your report (Google flags your TTFB if it’s over 600ms). If you have a high server response time or TTFB, you can conclude that Bluehost is the problem. I suggest migrating to someone like Cloudways (DigitalOcean or Vultr HF) who was the #1 host in 18 Facebook polls, does free migrations, and is who most people use in that Facebook Group.

If you need help, leave your GTmetrix or PageSpeed Insights report in the comments and I’ll hit you up with a few suggestions. But if your TTFB is slow, do yourself a favor and get off Bluehost.

slow Bluehost

Join Facebook Groups to get unbiased feedback about Bluehost
GTmetrix Report - OMM
Hopefully we can get your report looking more like this


1. Check For Slow Server Response Times

Run your website through PageSpeed Insights to see if “reduce server response times” is in your report. If yes, this means your server is slow. A high number of WordPress sites on Bluehost have a slow server especially since Google recommends it should be under 600ms.

The only way to fix this is by lowering the amount of CPU consumed by your website (i.e. deleting high resource plugins and heavy page builders). Or upgrade your hosting to include more server resources (either with Bluehost or someone else) – but this is a top speed factor.

Reduce Server Response Time

Indicators Bluehost Is Slow

  • High server response time in PageSpeed Insights
  • High TTFB (time to first byte) in GTmetrix Timings tab
  • High PageSpeed and YSlow scores in GTmetrix, but a slow load time
  • 503 service unavailable errors which means the server is being overloaded

You may also want to read Bluehost’s resource usage section on their user agreement page. It says “Accounts with a large number of files (inode count in excess of 200,000) can have an adverse effect on server performance.” This means if your site is consuming lots of resources (from more traffic, slow plugins, etc), they throttle your bandwidth and slow down your site. Bluehost customers constantly complain about slow servers on Twitter and Bluehost forums.



2. Upgrade To PHP 8.0 In Bluehost’s cPanel

Bluehost now supports PHP 7.4.

Most WordPress users are running outdated PHP versions when upgrading can easily make your site 2-3x faster. Bluehost will not upgrade you automatically (because they don’t want to risk breaking your site) so you need to do this yourself as Bluehost releases new PHP versions.

How To Update PHP Version On Bluehost

  • Login to your Bluehost cPanel
  • Select the PHP Config option
  • Select PHP 7.4 and save changes

Bluehost PHP 7.3 1


3. Activate Cloudflare’s CDN

To add Cloudflare, login to Bluehost and go to Domains → Cloudflare → Activate.


Bluehost Cloudflare

This activates Cloudflare’s CDN (content delivery network) which hosts your website on 200+ data centers around the world, reducing the distance between your server and visitors. It also helps offload resources to their data centers (lightening the load on your server) while improving security. Registering your site on the actual Cloudflare website, logging into your Cloudflare dashboard, and configuring the speed tab and page rules can further improve speed.

The next 5 suggestions are from PageSpeed Insights and can improve core web vitals.


4. Optimize Your LCP Element

Largest contentful paint (LCP) is one of three metrics in core web vitals.

Check your PageSpeed Insights report and it will show your largest contentful paint element. It’s usually an image, background image, video, animation, or block-level element (i.e. H1 tag).

Usually though, it’s an image. In which case you should optimize that image as best you can. Below are a few ways to optimize your LCP element if it’s either an image or background image.

  • Preload the LCP image
  • Compress the LCP image
  • Use a faster format (i.e. WebP)
  • Serve the LCP image from your CDN
  • Exclude the LCP image from lazy load
  • Make sure the LCP image uses proper dimensions

Largest Contentful Paint WordPress Element - Background Image


5. Use Preload, Prefetch, Preconnect

Preload and preconnect are recommended in PageSpeed Insights. Prefetch can also be used to speed up third-party code. You can add these manually to your header.php file or use Pre* Party or Perfmatters. Some plugins only support these partially such as WP Rocket, Asset CleanUp, Autoptimize, and SG Optimizer. Check if your speed plugin(s) support browser resource hints.

Preload – instructs browsers to download something ASAP. Often used with the LCP element (i.e logo and background image) but can also be used for fonts, scripts, and styles. Test to make sure preload links have a positive impact on speed – since Google says to preload key requests.

<link rel='preload' href='/image.png' as='image'>
<link rel='preload' href='/style.css' as='style'>
<link rel='preload' href='/script.js' as='script'>
<link rel='preload' href='/font.woff2' as='font' crossorigin>

Prefetch – helps browsers anticipate third-party domains. Find which ones are loading on your site in the “reduce impact of third-party code” tab of PageSpeed Insights. Then prefetch them.

<link rel="prefetch" href="">
<link rel="prefetch" href="">
<link rel="prefetch" href="">
<link rel="prefetch" href="">
<link rel="prefetch" href="">

Preconnect – similar to prefetch but instead of just the DNS lookup (what prefetch does), it also includes TLS negotiations and TCP handshakes. It should be used sparingly (that’s why Google says to preconnect to required domains). It’s mostly only done with CDNs and third-party fonts.

<link rel="preconnect" href="" crossorigin>
<link rel="preconnect" href="" crossorigin>


6. Remove Unused CSS And JavaScript

Asset unloading plugins like Asset CleanUp and Perfmatters can remove unused CSS and JavaScript. Both can improve core web vitals and are recommended in PageSpeed Insights.

I use Perfmatters since the UI/UX is better, but it also costs money. The pro version of Asset CleanUp lets you unload custom CSS while Perfmatters (and Asset CleanUp free version) don’t.

Choose a plugin. If using Perfmatters, enable the script manager in settings. If using Asset CleanUp, enable test mode if you want to test unloading assets with breaking your live site.

Next, edit a page/post and view all CSS and JavaScript files that are being loaded. You may notice some individual files (or even entire plugins) are loading in places they don’t need to be.

  • Disable slider plugin on pages that don’t use sliders
  • Disable contact form plugin everywhere but contact page
  • Disable rich snippets plugin on pages that don’t use rich snippets
  • Disable affiliate link management plugin on pages that don’t use aff links
  • Disable social sharing plugin on all pages (since it’s usually for blog posts)

Page builders load lots of CSS and JavaScript which you may not be using. You may consider disabling elementor-sticky, dialog, share-link, swiper, animations, icons, and wp-block-library.



7. Eliminate Render-Blocking Resources

If you have render-blocking resources errors in PageSpeed Insights, Autoptimize and Async JavaScript will usually do the trick. Install Autoptimize with the settings shown below. Next, install Async JavaScript and click “apply defer” found in the settings. That’s all you need to do.

Optimize Aggregate JavaScript CSS

Render-blocking errors can also be from third-party code, heavy JavaScript, and configuration issues with your cache plugin. You should also try hosting font files locally and preloading them.


8. Fix Layout Shifts

Layout shifts happen when elements on your site shift, literally.

You can find them using Google’s layout shift debugger. It creates a GIF so you can visibly see shifting elements. Alternatively, look at the “avoid large layout shifts” PageSpeed Insights item.

Layout shifts happen for many reasons, but here are some common solutions:

Without Font-Display Swap:

With Font-Display Swap:
  • Specify dimensions of images, iframes, videos, and div code for advertisements. By reserving space, this prevents it from shifting other elements. WP Rocket also has an option to “add missing image dimensions.” Otherwise, common examples are below.
<img src="example.png" width="680" height="680" />
<iframe src="" width="680"
height="340" ></iframe>
<div class="ads" style="min-width: 300px; min-height: 250px;"></div>

Other ways to improve CLS:

  • Hont fonts locally and preload them
  • Use CSS transform properly in animations
  • Fix issues with WP Rocket’s optimize CSS delivery
  • Use transform: translate() to move elements instead of up, down, left right


9. Configure A Solid Cache Plugin

WP Rocket was rated #1 in numerous Facebook polls. That’s because it comes with more features than nearly any cache plugin (especially free ones like WP Fastest Cache or W3 Total Cache). I have tutorials for most cache plugins, but I personally use WP Rocket. Nitropack has gained popularity but it’s expensive, cheats scores, and doesn’t always improve actual load time. If you don’t use WP Rocket, you may need to install a few extra plugins for these optimizations.

  • Database cleanup – WP-Optimize
  • CSS/JS optimization – Autoptimize
  • Delay JavaScript execution – Flying Scripts
  • Host Google Analytics locally – Flying Analytics
  • CDN URL integration – BunnyCDN / CDN Enabler
  • Heartbeat control – Heartbeat Control / manual code
  • Lazy load images/videos – Optimole / WP YouTube Lyte
  • Preload links / instant page – Perfmatters or Flying Pages
  • Host Facebook Pixel locally – no plugin does this that I know
  • Prefetch/preload – Pre* Party Resource Hints / manual code
  • Font-display:swap – Swap Google Fonts Display / manual code

Get 10% off WP Rocket by signing up for their email list on their coupons page.

WP Rocket is #1 in most Facebook polls (click thumbnails to enlarge):


10. Find And Fix Slow Loading Plugins

Find Your Slowest Plugins – look through your GTmetrix report (especially the Waterfall chart) to find which plugins are causing issues with your load times. Delete or replace them if possible. Query Monitor and the WP Hive Chrome Extension can also be useful for finding slow plugins.

Slow WordPress Plugin Waterfall

Avoid Slow Plugins – avoid these 70+ infamously slow plugins.

  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
  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. Elementor
  15. View Full List Of 73 Slow Plugins

Minimize Plugins – deactivate and delete any plugins you don’t absolutely need.

Consolidate Plugins – use 1 plugin for multiple features, for example, use WP Rocket for nearly all speed optimizations instead of individual plugins like WP-Optimize or Heartbeat Control.


11. Remove Junk From Your Database

If you’re using WP Rocket for your cache plugin, you can skip this step since there’s an option to do this in the WP Rocket “database” settings. Otherwise WP-Optimize does the same thing… it cleans your database like your spam and trash folder, pingbacks, trackbacks, and potentially thousands of post revisions. Schedule a database cleanup every 2 weeks or so to keep it clean.

WP-Optimize Clean Database

WP-Optimize lets you delete tables left behind by old plugins which aren’t installed anymore.



12. Optimize Images

There are a few primary ways to optimize your images; some are found in GTmetrix, others are found in Google PageSpeed Insights. All of them will contribute to better scores and load times.

GTmetrix Image Optimizations

Properly Size Images – means images are too large and need to be resized. When expanded, GTmetrix tells you which images have errors and their correct dimensions. Your logo, sliders, blog, and any image on your website usually calls for specific dimensions which you should be resizing them too. Start with images that appear on multiple pages (eg. logo + sidebar images). It’s a good idea to create a cheat sheet of your image dimensions so you can resize images accordingly (content body width, widget width, sliders, featured images, carousel images, etc). This way, you or your designer can crop/resize images before uploading them to WordPress.

Losslessly Compress Images – this is “efficiently encode images” in PSI. It means you need to compress images using a plugin like ShortPixel (what I use), Imagify, or Smush. Set your compression level in the plugin settings and test a few images before bulk optimizing them, since you may see a slight reduction in quality. Most are free until you reach the monthly quota.

Lazy Load Images – same thing as “defer offscreen images” and can be done in most cache or image optimization plugins. You can also try the native lazy load built-in to WordPress 5.5. Remember to exclude all your above the fold images from lazy load since it’s counterintuitive.

Serve Images In Next-Gen Format – use a plugin like ShortPixel or WebP Converter For Media to convert your images to the faster WebP format. It can easily reduce image files sizes by 25%.


13. Optimize Google Fonts

Have you checked your font’s load times in GTmetrix Waterfall?

GTmetrix Font Files

There are many ways to optimize fonts:

  • Try preloading fonts
  • Add font-display: swap
  • Avoid .ttf (use woff instead)
  • Host fonts locally (try OMGF)
  • Be minimal with font families, weights, icons
  • Fix any font-related 4xx and 5xx errors in GTmetrix


14. Optimize Third-Party Code

Third-party code is anything loading on your site from another website.

It can be anything from embedded videos to Google Fonts, Analytics, AdSense, Tag Manager, Maps, or even social sharing buttons on your blog. These generate extra requests from outside websites and will slow down yours. While some third-party code can be optimized, others can’t.

  • Google Analytics – host locally using a plugin like CAOS, WP Rocket, Perfmatters, or Flying Analytics. CAOS and Perfmatters also let you use analytics-minimal.js which is 1.5 KB instead of roughly 51.5 KB from gtag.js v4 or gtag.js. It slightly reduces page weight.
  • Google AdSense – ads are a speed killer. You can try lazy loading or delaying it’s JavaScript. Remember to specify ad dimensions and avoid showing them above the fold.
  • Google Maps – lazy load iframes and only use a Google Map on the contact or locally optimized pages. Try taking a screenshot of the map and linking it to driving directions.
  • Google Tag Manager – using CAOS to host GTM locally, reduce tags, and avoid hard coding tags in the headers. Usually only benefits load times for large, unoptimized sites.
  • Google Fonts – host locally, add font-display: swap, reduce number of fonts/weights, test preloading them, and use woff. If they’re serving from, preconnect them.
  • CDNs – preconnect your CDN and if using Cloudflare, try disable Rocket Loader and apps.
  • Videos – lazy load + replace iframe with preview image in WP Rocket / WP YouTube Lyte.
  • Gravatars – host locally using WP User Avatar, delay Gravatars, and try caching them.
  • Social Media – disable social sharing buttons where they don’t load using an asset unloading plugin (such as Asset CleanUp), take a screenshot of social media posts and use that instead of embeds, limit number of posts in feeds, and use browser resource hints.

Third Party Usage

Delaying JavaScript using WP Rocket or Flying Scripts is an excellent way to optimize your third-party code. I personally do this for my comments (wpDiscuz) and Gravatars.

Delay JavaScript Execution


15. Remove WordPress And WooCommerce Bloat

By default, WordPress consumes resources with autosaves, post revisions, pingbacks, trackbacks, heartbeat API, jQuery migrate, and many other things you probably don’t need.

I use Perfmatters to disable these, or you can use Clearfy and Disable WooCommerce Bloat. However, Perfmatters does bloat removal and asset unloading, so it hits 2 birds with 1 stone.



16. Avoid Using Slow Page Builders On Shared Hosting

I’m mainly talking about Elementor and Divi.

Sure, you can optimize them by unloading unused assets and using Elementor experimental features like Optimized DOM Output and Improved Asset Unloading. But the bottom line is they add lots of extra CSS, JS, and div wrappers to your website which slows everything down.

See how many times Elementor is in the source code?


And how many extra files it loads?

Elementor Scripts

Combine heavy page builders with Bluehost’s hosting and it’s a recipe for a slow website. Many people in Facebook Groups are moving from Divi/Elementor to Gutenberg, GeneratePress, and Oxygen Builder. I moved my site from Elementor to Gutenberg and saw massive improvements.

Page builder migrations and polls on the fastest themes (click thumbnails to enlarge):


17. Consider Moving To Cloudways

Most hosting recommendations are garbage and I suggest joining the WordPress Hosting and WP Speed Matters group to get unbiased feedback because let’s be honest, we’re all affiliates.

  • SiteGround has a slow TTFB, CPU limits, support went downhill, among other issues. Unethical considering their community manager (Hristo) is an admin for this Facebook Group, and the TOS (sec. #9) prevents affiliates from using ‘SiteGround’ in bad reviews.
  • Hostinger writes fake reviews, votes for themselves in polls, also unethical.
  • GoDaddy is like my ex-girlfriend: lots of promises, but absolutely no delivery.
  • WP Engine used to be good, but most people left them and speed/support are awful.
  • EIG brands (Bluehost + HostGator) cram too many websites on slow, shared servers.

Regardless if you use my aff links, please don’t support unethical companies.

I use Cloudways (Vultr HF) who has always given me a fast TTFB and great GTmetrix results even on huge posts. You can click through my posts (most of them are very long) and they will load instantly. LiteSpeed is also popular which you can get through NameHero or A2 Hosting. I like NameHero’s Turbo Cloud plan which includes more RAM, NVME storage, and is still cheap.

Both are completely different setups. On Cloudways, I use WP Rocket with BunnyCDN. On a LiteSpeed hosting plan, you would be using the LiteSpeed Cache plugin with CDN. They’re both great setups and should give you a fast TTFB / server response time in GTmetrix, especially if you use my WP Rocket or LiteSpeed Cache tutorial to configure the ideal settings.

You can read my Cloudways review or NameHero review. NameHero is easier (cPanel, A+ support, email hosting) while Cloudways is a little “techier” but gives you better control of your server and has way more data centers in the US, India, UK, etc. Cloudways is monthly pricing with a free migration while NameHero has a 30-day refund policy and also has a free migration.

I switched from SiteGround to Cloudways in 2019. My response times were 2x faster, I was paying 1/2 the price of what I was on SiteGround, and had no CPU issues or high renewal prices.

Cloudways Shoutout

When in doubt, check Facebook polls:

Moving from SiteGround
eCommerce Hosting Poll

People who moved to Cloudways and posted results:

Cloudways Numbers

Hosting recommendations - Facebook thread

Cloudways Coupon Code
OMM25 gives 25% off your first 2 months at Cloudways


Frequently Asked Questions

Why is my website slow on Bluehost?

Bluehost is shared hosting and lacks server resources. These are needed to accomodate high CPU tasks like WooCommerce, AdSense, and even Elementor. Configuring a cache plugin with a CDN is one of the most effective ways to fix a slow website on Bluehost.

How to fix a slow server response time on Bluehost?

You can fix a slow server response time on Bluehost by upgrading to the latest PHP version, configuring a cache plugin with a CDN, and cleaning up your database. If these don't work, consider moving away from shared hosting.

Will upgrading plans improve load times?

Yes, but you should optimize your website first and consider alternative hosts. Bluehost's Optimized WordPress Hosting or VPS plans aren't nearly as fast as semi-dedicated or cloud hosting from other providers. Join some Facebook Groups and do your research.

Which WordPress speed plugins should I use?

WP Rocket, TinyPNG, and Perfmatters are 3 key WordPress speed plugins. If you're not using WP Rocket, you will need to install additional plugins to take care of Heartbeat Control, database cleanup, lazy loading, and hosting Google Fonts and Analytics locally.

Did this tutorial work?
Let me know in the comments and feel free to share your new load time! If you still have a slow WordPress site on Bluehost let me know about that too… I will gladly look into your GTmetrix + Pingdom report and send you a few suggestions (just please do what you can from this guide).

It’s a 28 minute video but definitely worth watching.

See Also: The Complete Guide to WordPress Speed Optimization


About Tom Dupuis

Tom Dupuis 2017Tom Dupuis writes WordPress speed and SEO tutorials out of his apartment in Denver, Colorado. In his spare time, he plays Rocket League and watches murder documentaries. Read his bio to learn 50 random and disturbing things about him.

Notify of
Oldest Most Voted
Inline Feedbacks
View all comments