Web Hosting for Online Tutors

Short answer: an online tutor’s website has an unusual split between who reads it and who uses your service. The parent decides, the child attends. That shapes what the site needs to do, and it means the most important hosting decisions are about what you keep off your server rather than what you put on it. An entry-level plan at around £39 a year is genuinely enough for most tutors.

The parent is the buyer, the student is the user

For most tutors working with school-age children, the person reading your website is not the person you will be teaching. A parent is deciding whether to trust you with their child’s confidence and their exam results, often late at night, usually on a phone, frequently after a disappointing report.

That means the site has to answer a specific set of questions quickly: what you teach, at what level, what it costs, whether you are DBS checked, and what a session actually looks like. Everything else is decoration.

It also means the site itself is small. Five or six pages, some text, a few photographs. There is no technical reason for it to be slow, and no reason to pay for capacity you will never use.

Keep student work and lesson recordings off your website

This is the single most important decision, and it is easy to get wrong because the alternative looks convenient.

Tutors accumulate material: past papers, worked solutions, marked essays, recorded sessions, progress notes. The tempting move is to put it all behind a login on your own site so students can access it between lessons. Three reasons not to.

• Recorded lessons are video, and shared hosting is not built to stream video. A one-hour session is a large file. Students on a phone will get buffering, and you may hit bandwidth limits. Use a video platform and share links, or keep recordings in your cloud storage.
• Marked work and progress notes are personal data about a child. Holding it in a WordPress database that you maintain part-time, alongside plugins you update when you remember, is a meaningful responsibility you do not need to take on.
• A login area turns a brochure site into an application. User accounts, more memory, caching that has to be configured correctly, and genuine attention to security. Our WordPress security checklist gives a sense of what that involves.

The simpler design is to let the website do marketing and let a cloud drive or your tutoring platform do delivery. Share a folder link per student. It costs nothing, it is easier to revoke when a student leaves, and nothing sensitive sits on a server you are responsible for.

Your enquiry form is the whole business

A tutor’s site has one conversion point, and it fails silently more often than people realise. The form submits, the parent sees a thank-you message, and the email never arrives. You never know it happened. You simply have a quiet month.

The cause is usually that WordPress sends mail through PHP by default, which gets filtered as spam or rejected, particularly if your domain has no authentication records.

• Send form mail through authenticated SMTP rather than PHP mail
• Set up SPF, DKIM and DMARC on your domain
• Send submissions to an address you check daily, not one you configured once
• Test it yourself monthly from a different device

Our guides to contact forms not sending emails and SPF, DKIM and DMARC cover both.

Keep the form short. Name, contact detail, subject, year group, what they are hoping to achieve. Anything about a diagnosis, an EHCP or a medical condition is better discussed in a first conversation than collected through a web form and left sitting in your database.

Booking: use a hosted service rather than a plugin

Tutoring is appointment-based, so scheduling is a genuine need. It is still not a reason to run a booking plugin.

A plugin inside WordPress holds your appointment data, needs updating, can break on a WordPress or PHP upgrade, and turns a small brochure site into a database-driven application. When it fails on a Sunday evening during exam season, you are the support desk.

A hosted scheduling service embeds with a snippet, adds almost no load, handles reminders and payment, and is someone else’s problem when it breaks. The practical consequence is that entry-level shared hosting stays sufficient.

Term time is not evenly spread

Tutoring demand is seasonal in a way most small service businesses are not. September, January, and the weeks before GCSEs and A levels produce concentrated bursts of enquiries. A results day or a documentary about tutoring can produce a spike overnight.

For a brochure site with a hosted booking widget, this is not really a hosting problem. Cached static pages absorb a burst of traffic easily. It only becomes a problem if you have built a login area or a booking plugin, because those pages cannot be cached and every visitor triggers real work on the server.

Another argument for keeping the site simple.

Speed, and what actually causes slowness

Most of your traffic arrives on a phone. A parent comparing three tutors will not wait six seconds for your page. In practice, slow tutor websites are almost never caused by the hosting plan. In order of impact:

• Unresized photographs. Images straight off a phone are three to five megabytes. Resize to around 1600px wide before uploading.
• Heavy page builders loading a full framework to render six pages.
• No caching, so pages that never change are rebuilt for every visitor.
• Embedded social feeds, which can add several seconds each.

Our plain English guide to Core Web Vitals explains how Google measures this.

Email on your own domain

An address at your own domain reads differently to a parent than a free webmail account, and it costs nothing extra on most hosting plans. It also means you keep the address if you change email provider later.

Set up the authentication records at the same time. Ten minutes of work that stops your invoices and replies landing in spam.

What plan you actually need

For a brochure site with a hosted scheduling widget: entry-level shared hosting. SSD storage, a CDN, free SSL, daily backups, email on your own domain. Around £39 a year, and there is no reason to pay more.

For a site with a student login area or a booking plugin: more PHP memory and proper caching, so the next tier up. Worth asking yourself first whether you need it.

Check the renewal price rather than the first-year offer. A plan at £2.99 a month renewing near £9 costs over £100 a year from year two. Our guide to cheap web hosting in the UK covers what to look for.

Frequently asked questions

Do I need special hosting for a tutoring website?

No. A standard shared plan with SSD storage, a CDN, free SSL and daily backups covers it. The requirement only changes if you host video or run a student login area, and both are better handled elsewhere.

Can I host recorded lessons on my website?

You can, but you should not. Video files are large and shared hosting is not built to stream them, so students will get buffering and you may hit bandwidth limits. Use a video platform and share links.

Where should I store marked work and progress notes?

In cloud storage or your tutoring platform, not in your WordPress database. It is easier to manage, easier to revoke access when a student leaves, and it keeps personal data about a child off a server you maintain part-time.

Why are my enquiry emails not arriving?

Usually because WordPress is sending through PHP mail and the message is being filtered. Authenticated SMTP plus SPF, DKIM and DMARC fixes most cases.

Will my site cope with a rush of enquiries in September?

A cached brochure site will handle it without trouble. A site with a login area or a booking plugin cannot be cached in the same way and will need more headroom.

Explore more

If you teach through an institution rather than independently, our guides to web hosting for language schools and web hosting for schools may fit better. If you sell recorded courses rather than live sessions, see web hosting for online coaches and educators. Our hosting plans start at £39 a year and renew at £39, with a free trial if you want to test your own pages for speed first.