Skip to main content
.com domains from $2.99 — free WHOIS privacy on every name

Performance profile · Music Teachers

Music teachers: an embedded player is the heaviest thing on the page

The recording of your playing is the most persuasive thing on the site and, embedded the usual way, the most expensive thing on the page.

The short answer

For a music teacher the largest single performance item is the embedded player, because a streaming embed pulls a whole player framework from a third-party server on every page load, whether or not the visitor presses play.

Keep the recording and change how it loads. Show a static thumbnail with a play button and fetch the real player only on the first click, and never upload audio or video files to the hosting account itself, where they consume storage and bandwidth without any of the benefits a streaming platform brings. Measure both versions and the difference is usually the biggest single win on the site. Plans start at $2.42/mo.

By the HostingFast team · Reviewed 15 August 2026

Free

Migration in at no charge

24/7

Human answers, all hours

Daily

Daily backup taken

$0

Setup fees, none

Parents cannot evaluate a diploma, but they can hear whether you play well. That makes a short recording the most persuasive item on a music teacher's site, and it is exactly the right thing to have there.

The cost arrives in how it is embedded. A standard streaming embed loads a player framework, its scripts and often a font before the visitor has decided to listen, from servers your host has no control over. On a page that is otherwise text and one photograph, that embed can be the majority of the weight.

There is a well-established fix and it takes ten minutes. This page covers the measurement, the fix, and the second question nobody asks: whether the audio should be on your hosting at all.

Measure the page with and without the embed

Take a baseline of the page carrying your recording, on a mobile profile. Then remove the embed and retest. That difference is what the player costs, and on a lean teaching site it is often the majority of the total. Sort the network panel by domain while you are there — you will see how much of the page is being fetched from somewhere that is not your server.

This is the clearest case in this whole catalogue of a change with a large, measurable payoff. Two runs, one number, and a decision you can defend to anybody who asks.

Load the player only when asked

The fix is a facade: show a static thumbnail image with a play button drawn on it, and fetch the real embed on the first click. Visitors who listen get the full player after a moment; the majority who read the page and leave never pay for it at all.

Several themes and small plugins do this out of the box. Whichever route you take, retest afterwards — one change, one measurement, median of three lab runs — because a facade implemented badly can end up loading both the placeholder and the player.

Do not put the media files on your hosting

It is tempting to upload the MP3 or the video directly. Do not. A streaming platform handles encoding, adaptive bitrates and delivery from infrastructure built for that job. Files served from a hosting account consume storage and bandwidth and still arrive slowly for anyone far from the origin.

Our platform runs from London, which is a 5–15ms round trip for a British audience and 250–290ms for one in Australia. Cached pages hold up across that distance; a large media file served straight from the origin does not. That gap is precisely what streaming platforms exist to close.

Then the ordinary work, in order

With the embed dealt with, the rest is routine: WebP output for the photographs, dimensions matched to their containers, lazy-loading below the fold, and no plugin assets on pages that do not use the feature. All of that is either built in here or free to do.

The enquiry form is the exception, as ever. It is a POST, it never caches, and it runs PHP and the database directly — so time the submission itself and confirm the message reaches an inbox. NVMe storage and a current PHP release are what decide that request.

A support engineer picking up at whatever hour the question lands

Keep the recording, drop the cost

Instrumental and vocal teachers, peripatetic staff and small music schools are running text-and-photograph sites with one heavyweight component bolted on.

LiteSpeed caching in the server, NVMe storage and built-in WebP conversion look after the rest of the page. A facade takes care of the embed.

  • Cached pages that never touch PHP for a reading visitor
  • WebP conversion built in for the photographs
  • NVMe storage and current PHP on every tier
  • Staging clones for testing a facade implementation

Why HostingFast

Standard on every plan

The page without the player is quick

Server-level caching, NVMe and WebP conversion are all on by default, so the text-and-photograph part of the site needs no work.

A London origin for a UK audience

Cached pages reach British and Irish visitors on a 5–15ms round trip, well inside 200ms of TTFB.

Room to test the facade

Staging clones let you implement the click-to-load player, measure both versions, and push the one that won.

Enquiry posts on real hardware

Form submissions never cache. NVMe and a current PHP release are standard, which is where that request is decided.

Mail on your own domain

Spam and virus screening plus webmail, IMAP, POP and SMTP, so an enquiry reaches you between lessons.

No setup fee, flat renewal

Nothing to pay to start, and the renewal bills at the figure you ordered at.

Quick Start

From order to online

  1. 1

    Baseline the page carrying your recording

    Mobile profile, field vitals and TTFB. Note how many requests are going to a domain that is not yours.

  2. 2

    Remove the embed and retest

    That difference is the player's price. It is usually the largest single number you will find on a teaching site.

  3. 3

    Reinstate it behind a click

    Static thumbnail with a play button, real player fetched on first interaction. Retest to confirm the saving survived implementation.

  4. 4

    Then do the ordinary work

    WebP output, container-matched dimensions, lazy-loading, and no unused plugin assets. One change at a time.

Built In

Loaded onto every plan

  • LiteSpeed caching compiled into the web server
  • WebP image conversion built in at no extra cost
  • NVMe SSD storage on every tier
  • Per-site PHP version switching from the control panel
  • Staging environments for testing a click-to-load player
  • Daily backups with a self-service restore
  • Free SSL on every plan, reissued automatically
  • Webmail plus IMAP, POP and SMTP on every mailbox
  • 99.9% uptime as the target, monitored around the clock
  • Zero setup charges, and free migration by our engineers

Frequently Asked

What people ask us most often

How much does an embedded player actually cost my page?

Measure it and you will know in five minutes. Take a baseline, remove the embed, retest. On a lean teaching site the player framework, its scripts and often a font are frequently the majority of the page weight, and all of it loads whether or not the visitor presses play.

Can I keep the recording without the penalty?

Yes, with a facade. Show a static thumbnail with a play button and load the real embed on the first click. Anyone who wants to listen gets the player after a moment; everyone who reads and leaves never downloads it. Retest afterwards, because a badly implemented facade can end up loading both.

Should I upload the audio file to my hosting instead?

No. A streaming platform handles encoding, adaptive bitrates and delivery from infrastructure designed for exactly that. A file served from a hosting account uses your storage and bandwidth and still arrives slowly for distant listeners — our origin is in London, a 5–15ms round trip for a UK audience and 250–290ms for one in Australia.

Does a teaching site ever need more than the entry plan?

Rarely. The pages are light once the embed is handled, caching sits in the server and NVMe storage is on every tier, so the entry plan is usually generous. If that changes, plan upgrades happen in the client area with no migration and no downtime, so there is nothing to over-buy against.

Keep reading

Changing hosts? Run through our checklist first.

A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.

You'll get the checklist email, then occasional pointers on keeping a site running fast. Unsubscribe the moment you want out — the privacy policy covers the rest.

Weigh the player, then load it late.

LiteSpeed, NVMe and built-in WebP from $2.42/mo, with no setup fee at either end.

View SSL Certificates — Built for Music Teachers plans