# WordPress on shared hosting, the whole picture > Installing WordPress, moving one in, keeping it fast inside a free plan's limits, and fixing the handful of errors that account for most WordPress trouble. Source: https://cwp.sg/tutorials/wordpress-hosting/ Author: Ben Johnson Last verified: 2026-09-21 **In short:** - WordPress needs PHP and a MySQL database, both of which shared hosting provides. - You can install it in one click, or by hand for more control. - The limit you fight on a free plan is concurrent processes, not disk space. - Caching is the single biggest thing you can do, and it is free. - Most WordPress errors are one of a few known screens, each with a short fix. WordPress runs a large share of the web, and it runs perfectly well on ordinary shared hosting, because it needs exactly what shared hosting provides: PHP to run the code and a MySQL database to store the content. This page is the map of owning a WordPress site on a free or shared plan, from install to the errors you will meet. The thing to understand up front is where the limits are. On a free plan, disk space is rarely the problem. The ceiling you actually hit is how many things the site can do at once, and caching is what raises it. Everything below comes back to that. ## Getting it installed There are two ways in. Many hosts offer a one-click installer that sets up the database, the files, and the first admin account for you. It is the fastest path and the right one for most people. If you want to understand each part, or the installer is not available, you can do it by hand. The step-by-step is in [install WordPress manually](/tutorials/install-wordpress-manually/). If you are still deciding whether WordPress is the right tool at all, the [WordPress hosting guide](/guides/how-to-host-a-website/wordpress/) covers when it fits and when a simpler static site would serve you better. ## Moving an existing site in If you already have a WordPress site elsewhere, moving it is a database job plus a files job. You copy the files across over FTP, export the database from the old host, and [import the database](/tutorials/import-a-database/) on the new one. The one detail that catches people is the site's address stored inside the database, which has to match the new home or the site will not load correctly. ## Keeping it fast inside the limits This is the part that matters most on a free plan. Every time a visitor loads a page, WordPress runs PHP and queries the database to build that page. A plan allows only so many of those to happen at once. When too many arrive together, new visitors get a [508 resource limit](/errors/508-resource-limit-is-reached/) error, even though nothing is broken. Caching is the fix, and it changes everything. A caching plugin saves each built page and serves the saved copy to the next visitor, so most requests skip PHP and the database entirely. This can raise how much traffic the same plan handles by roughly ten times. It is free, it takes a few minutes, and it is the first thing to do before you ever consider paying for a bigger plan. ## The errors you will actually meet WordPress trouble tends to arrive as one of a few known screens, and each has a short fix. A completely blank page is the [white screen of death](/errors/white-screen-of-death/), almost always a plugin or theme conflict. Being bounced back to the login over and over is the [login redirect loop](/errors/wordpress-login-redirect-loop/), usually a settings or address mismatch. And a page that dies partway through building is often the [allowed memory size exhausted](/errors/allowed-memory-size-exhausted/) error, where a heavy plugin asked for more memory than the plan gives. None of these mean the site is lost. Each one is a recognised pattern with a documented fix, linked above. The other half of owning a WordPress site is keeping it updated. Most sites are broken into not by clever attacks but through a plugin nobody updated for a year. Turn on automatic updates for WordPress itself, keep plugins current, and remove any theme or plugin you are not using rather than leaving it dormant. On a shared server this is not just your problem: a compromised WordPress account can be used to attack its neighbours, which is why hosts watch for it and suspend fast. ## The whole WordPress setup, in order Putting a WordPress site on shared hosting, start to finish: 1. Install it, one click or by hand. 2. If you are moving an existing site, copy the files and import the database. 3. Turn on a caching plugin before you do anything else about speed. 4. Learn the three or four error screens so a blank page does not stop you. 5. Only think about a bigger plan after caching, not before. That is the whole picture. Each step links to its how-to, and step three is the one that saves the most people the most grief. --- Content Website Platform (cwp.sg) operates the free hosting it writes about; see https://cwp.sg/about/ for the methodology and the commercial disclosure.