Web hosting for djs — A press pack download is a bandwidth line item

A DJ's site is read by two audiences with different needs. Promoters and event bookers want proof and a way to enquire. Everyone else wants to listen. The same page has to serve both without either of them waiting.

The technical characteristic that defines these sites is delegation: the mixes live on somebody else's platform, embedded in your page, along with their player code. That is the right call for audio, but it means most of your page weight is decided by a third party.

So the discipline is a budget. Decide what the front page is allowed to weigh and how responsive it has to be, then fit the embeds, the press pack and the form inside that figure rather than adding them and hoping.

An embedded player is somebody else's JavaScript, executing on your main thread while your page is trying to become interactive. One is usually fine. A wall of six on the front page is why a site feels sticky under a thumb even though it looks finished.

Put one player on the front page and move the rest to a listening page of their own. Better still, use a facade — a static image of the player that loads the real embed only when it is clicked. That pattern removes the whole cost from the initial load and no visitor has ever complained about it.

Everything else on the site is marketing. The form is the transaction. Test it end to end from the live site — submit a real enquiry with a date, a venue and an event type, and confirm both your notification and the sender's acknowledgement land in an inbox rather than a spam folder.

Outbound mail goes through MailChannels here, with SPF, DKIM and DMARC configured on the domain, which is what stops an automated acknowledgement being filtered. Keep the reply-to address on your own domain, and check the whole path again after any plugin update.