Static Website Hosting: A UK Guide
How static website hosting works, what it costs, how the main platforms compare, and how to get a static HTML site live in the UK.
Static website hosting means serving pre-built HTML, CSS and JavaScript files directly to a visitor’s browser, with no database and no server-side code running on each request. It is the fastest, cheapest and most secure way to put a website online, and it suits everything from a single landing page to a documentation site built with Jekyll, Hugo, Astro or Eleventy.
This guide covers what static hosting is and how it differs from dynamic hosting, what it costs, how the main platforms compare, what UK businesses specifically need to consider, when to choose static over WordPress, and how to get a static HTML site live.
What Is Static Website Hosting?
Static website hosting is the process of serving fixed files, typically HTML, CSS, and JavaScript, directly from a server to a visitor’s browser. Unlike dynamic websites, there is no server-side processing, no database queries, and no code executing on the server at the point of each request. The files are simply stored and delivered as they are.
This can mean hand-coded HTML, or files generated by a static site generator such as Jekyll, Hugo, Astro, or Eleventy. Either way, the result is inherently fast, secure, and straightforward to manage.
Static vs dynamic hosting: the difference
The distinction is what happens between a visitor’s request and the page arriving in their browser.
| Static hosting | Dynamic hosting | |
|---|---|---|
| What is served | Pre-built HTML files | Pages assembled per request |
| Database | None required | Usually MySQL or similar |
| Server-side code | None at request time | PHP, Node, Python and so on |
| Typical speed | Fastest available | Depends on caching and tuning |
| Attack surface | Very small | Larger: CMS, plugins, database |
| Ongoing maintenance | Minimal | Regular updates required |
| Best for | Brochure sites, landing pages, docs, portfolios | Shops, memberships, frequently edited sites |
Who Is Static Hosting Suitable For?
Static website hosting is a good fit for a wide range of use cases, including:
- Portfolio websites and personal pages
- Blogs built with static site generators
- Documentation and knowledge bases
- Business landing pages and microsites
- Plain HTML brochure sites for small businesses
- Jamstack projects using tools such as Jekyll, Hugo, Gatsby, Astro, or Eleventy
If your site does not require server-side processing at runtime, static hosting is almost certainly the better choice.
The Benefits of Static Website Hosting
Speed
Because there is no backend processing involved, static files can be delivered to visitors almost instantly. When combined with a content delivery network (CDN), your files are served from edge locations close to the visitor, reducing latency further. This also makes static sites well placed on Core Web Vitals, where Largest Contentful Paint is heavily influenced by how quickly the server responds.
Security
Static sites have a significantly reduced attack surface compared to dynamic websites. With no database to inject, no admin login to brute-force, and no plugin vulnerabilities to exploit, there are far fewer weaknesses for attackers to target.
Lower Maintenance
Without a database or server-side application to manage, static websites require considerably less ongoing maintenance. There are no software updates to apply to a CMS, no database backups to configure, and fewer moving parts overall.
SEO Advantages
Page speed is a confirmed ranking factor for Google. Static websites, by nature of their fast load times and clean structure, are well-suited to performing well in search results. Pairing a static site with a custom domain, HTTPS, and good on-page practice gives you a strong technical foundation.
Cost
Static website hosting tends to be far more affordable than hosting dynamic sites. The resource requirements are lower, which means hosting providers can offer competitive pricing without sacrificing performance. For developer-maintained sites there is a workflow benefit too: a static site, particularly one built with a generator, works naturally with Git, so the entire site can live in a repository with changes tracked, reviewed, and deployed with a push.
How Much Does Static Website Hosting Cost?
Static hosting sits at the cheap end of the market, and for very small projects it can be free. The honest answer is that the price depends on what you need alongside the files.
- Free tiers exist on most of the developer-focused platforms. They are fine for personal projects and side projects, but usually come with bandwidth or build limits, no phone or ticket support, and restrictions on commercial use in some cases.
- Paid static hosting on a UK shared plan typically starts at a few pounds a month. At Switchweb, plans start from £39 per year and include SSD storage, a global CDN, free SSL and daily backups, with no build-minute or bandwidth metering to watch.
- Enterprise or high-traffic static hosting costs more, but usually because of the surrounding services, such as edge functions, preview environments and team seats, rather than the file serving itself.
One point worth weighing: a free tier that has to be upgraded the moment a campaign takes off is not necessarily cheaper than a low-cost plan with predictable annual pricing.
Static Hosting Platforms Compared
The main options fall into two camps: developer platforms built around Git deployment, and conventional hosting that serves static files alongside everything else. Free-tier allowances change regularly, so check the current terms before committing.
| Platform | Best for | Free tier | Watch out for |
|---|---|---|---|
| Cloudflare Pages | High-traffic static sites | Generous, with uncapped bandwidth at the time of writing | Build-count limits; ecosystem is Cloudflare-centric |
| Netlify | Jamstack builds and previews | Around 100 GB bandwidth and limited build minutes per month | Costs escalate quickly past the free tier |
| Vercel | Next.js and framework-driven sites | Around 100 GB bandwidth per month | Commercial use restrictions on the hobby plan |
| GitHub Pages | Documentation and open-source project sites | Free, roughly 1 GB site size and 100 GB soft bandwidth limit | Static only, no server-side anything, limited support |
| UK shared hosting (e.g. Switchweb) | Business sites, landing pages, mixed static and dynamic estates | None, but low fixed annual cost | Less opinionated about Git workflows than the platforms above |
The developer platforms are excellent if your workflow is already built around a repository and a build step. Conventional hosting tends to win when you want a UK company to call, email on the same domain, a control panel your team can use, and the option to add a WordPress install later without moving providers.
Static Website Hosting in the UK
If your audience is UK-based, a few things are worth checking beyond raw speed.
Where your files are served from
A CDN largely neutralises distance for static assets, but the origin still matters for the first request and for anything not yet cached at the edge. A UK or European origin keeps that first byte quick for British visitors.
Data protection and UK GDPR
A purely static site collects very little, which is one of its quiet advantages. As soon as you add a contact form, an email capture or analytics, you are processing personal data, and you need HTTPS, a lawful basis and a privacy notice. Knowing where your host processes and stores that data makes the compliance conversation much simpler.
Support in your timezone
Free platform tiers are typically community-supported. If a landing page goes down mid-campaign at 9am on a Tuesday, a UK support team you can actually reach is worth more than a saved subscription.
Domains and email
Most static platforms will happily point a .co.uk domain at your site, but they will not give you mailboxes. Businesses usually end up needing both, and keeping the domain, the site and the email with one UK provider removes a category of DNS problems entirely.
Static or WordPress: Which Should You Choose?
The static versus WordPress question comes up whenever someone starts a new site or reconsiders an existing one. Both are good choices in the right context; the difference is which fits the specific requirements of the site you are building.
WordPress generates pages dynamically: when someone visits, it queries a database, assembles the content, applies a theme, and delivers the result. The advantage is a flexible admin interface that lets non-technical users publish and edit content without touching code, backed by a vast plugin ecosystem covering contact forms, e-commerce, bookings, and memberships. The trade-off is additional complexity: a database, PHP, regular updates, and a larger attack surface. There is also a practical point that matters more than it might appear: most freelancers, agencies, and in-house teams are familiar with WordPress, so finding someone to build or maintain it is easier than finding someone comfortable with a less common static site generator.
Static is likely the better fit if:
- The site is primarily informational and updated infrequently
- The content publisher is comfortable with Markdown or basic file editing
- Performance and security are the primary concerns
- The site is developer-maintained and will live in version control
- It is a landing page, portfolio, documentation site, or simple brochure
WordPress is likely the better fit if:
- Non-technical staff need to publish and edit content independently
- The site needs e-commerce, bookings, memberships, or other plugin-dependent functionality
- A blog or news section needs regular updates
- The site will be handed to a client who expects a standard CMS
- Long-term maintenance will be done by a generalist rather than a developer
Some sites combine both: a static front end for speed and security, with a headless CMS behind it for content management. This is more complex to build and host, and generally only worth considering for sites with significant traffic and a development team to maintain the setup. If WordPress is the right fit for your project, our WordPress hosting guide covers what to look for.
Static WordPress hosting: converting WordPress to a static site
There is a middle path that suits a lot of brochure sites. You keep WordPress as the editing tool, then export the finished pages as flat HTML and serve those files instead of running WordPress publicly. Plugins such as Simply Static and WP2Static handle the export.
The appeal is obvious: the editing experience your team already knows, with the speed and reduced attack surface of static hosting. The trade-offs are real too. Anything that depends on PHP at runtime stops working, so contact forms, search, comments and WooCommerce all need a third-party replacement or need to go. Every content change requires a rebuild and redeploy rather than appearing instantly.
It works well for sites that are updated weekly rather than hourly and that have no transactional functionality. If your site relies on plugins doing work at request time, conventional WordPress hosting with good caching will get you most of the speed benefit with none of the disruption.
Hosting Landing Pages
Landing pages deserve a specific mention because they are one of the strongest use cases for static hosting. A landing page has one job: convert a visitor into an enquiry, a sign-up, or a sale, and everything that gets in the way of that has a direct cost in missed conversions.
Speed is a conversion factor
Landing pages usually sit at the end of paid traffic: a Google Ads campaign, an email send, a social media push. A page that takes more than a couple of seconds to load loses a proportion of visitors the campaign has already paid to send there. A static page with no database query or plugin overhead, served through a CDN, is typically the fastest option available.
Uptime during campaigns
Downtime while a time-sensitive campaign is running is expensive. Look for hosting with a genuine uptime commitment and infrastructure that handles traffic spikes without going offline. An SSL certificate is non-negotiable too: a browser security warning is a conversion killer, and any page collecting personal data through a form needs HTTPS under UK GDPR.
Builder or self-hosted?
Dedicated landing page builders such as Unbounce and Leadpages are optimised for creating pages quickly without developer involvement, handling hosting, SSL, and often A/B testing. The trade-off is a significant monthly cost and pages that sit outside your main website’s hosting environment, which can complicate analytics. If you already have a hosting plan, hosting a landing page alongside your main site costs nothing extra, keeps everything on your own domain (preserving the authority your main site has built), and gives you full control over tracking: Tag Manager, conversion pixels, and heatmap tools can all be added directly without the restrictions some builders impose on lower tiers. For most small businesses, self-hosting is the most cost-effective approach, provided the host is fast and reliable.
What to Look for in a Static Website Hosting Provider
Not all static hosting is created equal. When choosing a provider, consider the following:
Performance Infrastructure
Look for SSD-based storage and CDN integration as standard. These two factors have the most direct impact on load speed. Edge caching, which serves your static assets from servers geographically close to your visitors, is a further advantage worth seeking out.
SSL Certificates
Free SSL via Let’s Encrypt is now widely available and should be considered a baseline requirement. HTTPS is important for both security and search engine visibility.
Deployment Options
For developers, Git-based deployment is a significant convenience. Being able to push changes to a repository and have them go live automatically saves time and reduces the risk of manual errors. FTP and SFTP access remain useful for straightforward file management, and a browser-based file manager is often the quickest route for a one-page HTML site.
Support for Static Site Generators
If you are using a static site generator such as Jekyll, Hugo, Gatsby, or Astro, confirm that your hosting provider supports the build process or is compatible with your preferred deployment workflow. Many hosts serve the output happily but expect you to run the build yourself, either locally or in CI.
Reliability and Uptime
Check for a clear uptime commitment. Static files are simpler to serve reliably than dynamic sites, but a poor-quality host can still introduce unnecessary downtime.
How to Host a Static HTML Website: Step by Step
Getting a static website online is a straightforward process. For a hand-coded HTML site it takes well under an hour.
- Build the site locally. Either write the HTML, CSS and JavaScript directly, or run a static site generator to produce a folder of finished files. Make sure your homepage file is named
index.html. - Choose a hosting plan. Check it covers the storage, bandwidth and domain count you need, and that SSL is included rather than an extra.
- Upload the files. Use the control panel file manager for a small site, FTP or SFTP for a larger one, or a Git integration if you want deploys to happen automatically on push. Files go into the web root, usually
public_html. - Point your domain at the hosting. Update the nameservers or the A record at your registrar, then wait for DNS to propagate.
- Activate SSL and force HTTPS. Issue the certificate, then redirect HTTP traffic to HTTPS so there is only one version of each page.
- Test and go live. Check the site on mobile, confirm every internal link resolves, run a speed test, then submit your sitemap to Google Search Console.
Frequently Asked Questions
What is static website hosting?
Static website hosting serves pre-built HTML, CSS and JavaScript files straight to the browser, with no database and no server-side code running per request. Because there is nothing to assemble, pages are delivered faster and there is far less that can be attacked or that needs maintaining.
Is static website hosting free?
It can be. Several developer platforms offer free tiers that are adequate for personal and open-source projects, though they generally cap bandwidth or build minutes, exclude support, and sometimes restrict commercial use. Paid static hosting on a UK plan is inexpensive, starting from around £39 per year, and removes those limits.
Can I host a plain HTML website without a static site generator?
Yes. You can upload plain HTML, CSS, and JavaScript files and be live in minutes. Generators such as Jekyll, Hugo and Eleventy simply make larger sites easier to build and maintain by handling templates, navigation and repeated markup for you.
Is static website hosting suitable for large sites?
Yes. Static hosting scales well. Because files are served directly without backend processing, high traffic volumes are handled efficiently. A CDN makes this even more resilient.
Can I use a custom domain with static website hosting?
Yes. Most providers allow you to connect a custom domain and will issue a free SSL certificate through Let’s Encrypt. A custom domain is strongly recommended for both branding and SEO, and for landing pages it looks considerably more trustworthy than a builder subdomain.
What is the difference between static and dynamic hosting?
Dynamic hosting runs server-side code for each visitor request, querying databases and generating pages on the fly. Static hosting simply delivers pre-built files. Static is faster and simpler when your content does not need to change per request.
Can non-technical staff update a static site?
It depends on the setup. Editing raw HTML or Markdown files is manageable for some, but if staff need to publish content regularly without developer involvement, a CMS such as WordPress is usually the more practical choice, as covered in the comparison above.
Can I add a contact form to a static website?
Yes, but not with the site’s own server, since there is nothing running to process the submission. The usual approaches are a third-party form service that posts to its own endpoint, or hosting the static site on a plan that also supports a small server-side script for the form handler.
Does static hosting help SEO?
Indirectly, and meaningfully. Static sites tend to have excellent server response times and clean HTML, which helps Core Web Vitals and makes crawling straightforward. It is not a ranking factor in itself, but it removes a common category of technical problems.
For UK-based organisations looking for reliable static website hosting, Switchweb offers SSD-powered hosting with CDN integration, free SSL, and daily backups as standard, with plans starting from £39 per year and support for site types from single landing pages to full static generator projects.
Looking to get started on Switchweb? Take a look at our website hosting plans or message us about a free trial.
