{"id":3311,"date":"2026-10-01T07:29:14","date_gmt":"2026-10-01T07:29:14","guid":{"rendered":"https:\/\/siteharbour.com\/blog\/?p=3311"},"modified":"2026-10-01T07:29:14","modified_gmt":"2026-10-01T07:29:14","slug":"speed-up-wordpress-shared-hosting","status":"publish","type":"post","link":"https:\/\/siteharbour.com\/blog\/speed-up-wordpress-shared-hosting\/","title":{"rendered":"How to Speed Up WordPress on Shared Hosting in 5 Easy Steps"},"content":{"rendered":"<p>To speed up WordPress on shared hosting, do five things in this order: make a backup, update PHP in cPanel, turn on the LiteSpeed Cache plugin, shrink your images, and remove plugins you no longer use. Together these fix the most common causes of a slow site. None of them needs coding, and each takes a few minutes.<\/p>\n<p>The steps are written for cPanel hosting on LiteSpeed servers, which is what SiteHarbour shared hosting uses. If your site is still slow afterwards, our guide on <a href=\"\/blog\/why-is-my-wordpress-website-slow\/\">why your WordPress site is slow<\/a> shows how to find the exact cause.<\/p>\n<h2>Step 1: Make a backup first<\/h2>\n<p>Every change below is safe, but a backup lets you undo anything in minutes. In cPanel, open <strong>Backup Wizard<\/strong>, choose <strong>Back Up<\/strong>, then <strong>Full Backup<\/strong> (or <strong>Home Directory<\/strong> and <strong>MySQL Databases<\/strong> separately), and download the files to your computer.<\/p>\n<div class=\"callout callout-warning\">\n<p><strong>Warning.<\/strong> Do not skip the backup. A new PHP version or plugin can occasionally clash with an old theme. With a backup that is a five-minute fix, and without one it can mean a lost site.<\/p>\n<\/div>\n<h2>Step 2: Update your PHP version<\/h2>\n<p>PHP is the engine that builds every WordPress page. Newer versions run the same code faster, and old versions stop receiving security fixes. This is often the biggest single speed gain, and it costs nothing.<\/p>\n<ol>\n<li>Log in to cPanel and open <strong>MultiPHP Manager<\/strong> under <strong>Software<\/strong>. If you see <strong>Select PHP Version<\/strong> instead, use that. The idea is the same.<\/li>\n<li>Tick the box next to your domain.<\/li>\n<li>In the <strong>PHP Version<\/strong> drop-down, pick the newest version your theme and plugins support. In most cases that is the latest 8.x release in the list.<\/li>\n<li>Click <strong>Apply<\/strong>.<\/li>\n<\/ol>\n<p>Now open your website and your <code>\/wp-admin<\/code> login in a new tab. If either shows an error, go back to cPanel, choose the previous PHP version and click <strong>Apply<\/strong>. The error is almost always an outdated plugin or theme, so update or replace it before you try again.<\/p>\n<h2>Step 3: Turn on LiteSpeed Cache<\/h2>\n<p>Without a cache, WordPress rebuilds every page for every visitor. A cache saves the finished page and serves that copy instead, which is much faster. Our servers run LiteSpeed, so the free LiteSpeed Cache plugin can work with the server directly.<\/p>\n<ol>\n<li>In WordPress, go to <strong>Plugins<\/strong>, then <strong>Add New<\/strong>.<\/li>\n<li>Search for <strong>LiteSpeed Cache<\/strong> by LiteSpeed Technology, then click <strong>Install Now<\/strong> and <strong>Activate<\/strong>.<\/li>\n<li>Open <strong>LiteSpeed Cache<\/strong>, then <strong>Cache<\/strong>, and check that <strong>Enable Cache<\/strong> is set to <strong>ON<\/strong>. That is normally the default, and for most sites it is all you need.<\/li>\n<\/ol>\n<div class=\"callout callout-tip\">\n<p><strong>Tip.<\/strong> Use only one caching plugin. If you already have another one (WP Super Cache, W3 Total Cache and similar), deactivate it before you activate LiteSpeed Cache, or the two will conflict.<\/p>\n<\/div>\n<p>Leave the other settings alone for now. Switching on advanced options you do not understand is the most common way a cache plugin breaks a layout. If something looks wrong later, use <strong>Purge All<\/strong> in the plugin menu at the top of your dashboard to clear the saved pages.<\/p>\n<h2>Step 4: Shrink your images<\/h2>\n<p>Large photos are the usual reason a page is heavy. A single phone photo can be several megabytes, while an image in a blog post only needs about 100 to 200 KB.<\/p>\n<ul>\n<li><strong>New images:<\/strong> resize and compress them before you upload. A free browser tool such as Squoosh (squoosh.app) does both. A width of about 1600 pixels is plenty for a full-width image.<\/li>\n<li><strong>Images already on your site:<\/strong> use an image optimization plugin. LiteSpeed Cache includes one that works through QUIC.cloud and has a free allowance. Check the current limit on its settings page.<\/li>\n<\/ul>\n<h2>Step 5: Remove plugins and themes you do not use<\/h2>\n<p>Every active plugin can add code that runs on each page load. Unused ones add risk and clutter without helping you.<\/p>\n<ol>\n<li>Go to <strong>Plugins<\/strong>, then <strong>Installed Plugins<\/strong>.<\/li>\n<li>For each plugin, ask whether you still use it. If not, click <strong>Deactivate<\/strong>, then <strong>Delete<\/strong>.<\/li>\n<li>Go to <strong>Appearance<\/strong>, then <strong>Themes<\/strong>, and delete themes you do not use. Keep your active theme and one default WordPress theme as a fallback.<\/li>\n<\/ol>\n<p>Sliders, social feeds, related-posts widgets and page-builder add-ons tend to cost the most, so review those first.<\/p>\n<h2>How to check that it worked<\/h2>\n<p>Test the same page before and after your changes at <a href=\"https:\/\/pagespeed.web.dev\" rel=\"nofollow noopener\">PageSpeed Insights<\/a>, so the results are comparable.<\/p>\n<div class=\"callout callout-tip\">\n<p><strong>Tip.<\/strong> Test twice. The first visit after clearing the cache is always slower, because the page has to be built and saved. The second test shows the cached speed your visitors get.<\/p>\n<\/div>\n<h2>Common mistakes to avoid<\/h2>\n<ul>\n<li><strong>Changing everything at once.<\/strong> If you update PHP, install a cache and compress images in one sitting and something breaks, you cannot tell which change caused it. Make one change, check your site, then move on to the next.<\/li>\n<li><strong>Testing while logged in.<\/strong> WordPress treats you differently from a visitor, and caching is often switched off for logged-in users. Open your site in a private or incognito window to see what visitors really get.<\/li>\n<li><strong>Installing two cache plugins.<\/strong> They fight over the same job and can leave you with a broken layout or stale pages. Keep one.<\/li>\n<li><strong>Uploading full-size photos.<\/strong> A 5 MB image resized by the browser is still a 5 MB download. Resize before you upload.<\/li>\n<li><strong>Keeping plugins &#8220;just in case&#8221;.<\/strong> If you have not used a plugin in months, it is costing you speed and adding a security risk for no benefit.<\/li>\n<\/ul>\n<h2>How often to repeat these checks<\/h2>\n<p>Speed is not a one-time job, because sites slowly pick up new plugins, bigger images and more content. A short monthly routine is enough: update WordPress, your theme and your plugins, check in MultiPHP Manager that you are still on a current PHP version, delete anything you no longer use, and run one PageSpeed test on your home page and one on a blog post. If the scores drop, you will know it is something recent and can look at what changed.<\/p>\n<h2>Still slow?<\/h2>\n<p>If the site is still slow after these five steps, the cause is usually specific, such as one heavy plugin, a large database or a traffic spike. Follow the checks in <a href=\"\/blog\/why-is-my-wordpress-website-slow\/\">Why Is My WordPress Site Slow?<\/a> to find it. If your site has outgrown its plan, you can compare options on our <a href=\"\/shared-hosting\">shared hosting page<\/a>.<\/p>\n<h2>Frequently asked questions<\/h2>\n<h3>Is LiteSpeed Cache really free?<\/h3>\n<p>Yes, the plugin is free. Some optional features, such as image optimization, use the QUIC.cloud service, which has its own free allowance and paid tiers. The basic page cache needs neither.<\/p>\n<h3>Will updating PHP break my site?<\/h3>\n<p>Usually not, but an old plugin or theme can fail on a newer version. That is why Step 1 is a backup. If you see an error, switch back to the previous version in MultiPHP Manager and update the plugin that caused it.<\/p>\n<h3>Do I need to know how to code?<\/h3>\n<p>No. Every step uses cPanel or the WordPress dashboard.<\/p>\n<h3>How much faster will my site be?<\/h3>\n<p>It depends on what was slowing it down. Test before and after on the same page. A cached page on a current PHP version is typically much faster than an uncached one on an old version.<\/p>\n<h3>Can I do this without a plugin?<\/h3>\n<p>Partly. Updating PHP and removing unused plugins need no plugin at all, and a separate guide covers the rest using cPanel tools only.<\/p>\n<p>The short version: back up, update PHP in cPanel, enable LiteSpeed Cache, compress your images, delete plugins you do not use, then test the same page before and after.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Five easy cPanel steps to make a slow WordPress site faster on shared hosting: PHP version, LiteSpeed Cache, image size and unused plugins.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[13],"tags":[53,54,19,55,52],"class_list":["post-3311","post","type-post","status-publish","format-standard","hentry","category-web-hosting","tag-cpanel","tag-litespeed","tag-shared-hosting","tag-speed","tag-wordpress"],"_links":{"self":[{"href":"https:\/\/siteharbour.com\/blog\/wp-json\/wp\/v2\/posts\/3311","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/siteharbour.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/siteharbour.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/siteharbour.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/siteharbour.com\/blog\/wp-json\/wp\/v2\/comments?post=3311"}],"version-history":[{"count":1,"href":"https:\/\/siteharbour.com\/blog\/wp-json\/wp\/v2\/posts\/3311\/revisions"}],"predecessor-version":[{"id":3312,"href":"https:\/\/siteharbour.com\/blog\/wp-json\/wp\/v2\/posts\/3311\/revisions\/3312"}],"wp:attachment":[{"href":"https:\/\/siteharbour.com\/blog\/wp-json\/wp\/v2\/media?parent=3311"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/siteharbour.com\/blog\/wp-json\/wp\/v2\/categories?post=3311"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/siteharbour.com\/blog\/wp-json\/wp\/v2\/tags?post=3311"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}