Does an audio player slow your page down? What to check before you add one

A technical team's first objection, when you offer to add an audio player, is not about price or about the voice. It is: will this slow my pages down? The worry is fair. A badly built third-party script blocks rendering, delays the text from appearing, drags down the speed metrics Google looks at, and an article that takes an extra second to show loses readers before the first sentence. Adding an audio player should cost none of that. Here is what makes the difference, and how to check it on your own pages rather than take our word for it.

A script that does not block rendering

The first point is how the script loads. The WeDispatch player relies on a light, asynchronous script: the browser keeps painting your article while it fetches it, instead of waiting. The text appears first, the player after, without ever delaying the moment the reader sees and can read the content. That is the difference between a script that sits in the critical rendering path and a script that lives beside it. A player that blocks rendering costs you on the largest contentful paint, the metric engines watch; an asynchronous player leaves it alone. The page loads as if the player were not there, then the player arrives.

The audio is not in the page, it is on a CDN

The second point is the audio file itself. A 1,000-word article weighs a few megabytes as audio, and it would be absurd to make the page carry that weight. It does not: the file is served from a content delivery network (CDN), with a year of caching, and it is only downloaded when the listener presses "Listen". As long as nobody starts playback, the page loads only the button, not the sound. That is what lets you voice a whole site without adding weight to a single page for visitors who come only to read. Storage and retention of the files are on our side, which also spares you from provisioning space or managing a cache.

The case of platforms that refuse any third-party script

Some large newsrooms go further: their rules flatly forbid any third-party script, and the iframe is ruled out too because it escapes indexing. For them, the real performance guarantee is loading nothing from an external domain at all. That is the role of the server-side composition block: we return only data, your engine produces the HTML, and our JavaScript is concatenated with yours rather than loaded from us. The render budget is measured, on the order of one hundred and forty milliseconds on a fresh instance and zero on a page already served thanks to the declared cache. Nothing is called from our domain at runtime: the page's performance stays entirely under your team's control, which is exactly what they ask for.

How to check it yourself

None of these claims are worth anything without measurement, and the measurement is within reach. Open a page with the player in your browser's developer tools, network tab, and look at two things: when the player's script loads relative to the text appearing, and whether the audio file downloads before you have clicked "Listen". A performance auditing tool like the one built into your browser gives you the rest: compare the page's score with and without the player, and watch the largest contentful paint in particular, since that is where a blocking script does its damage. Run the test twice, once on a cold load and once on a repeat visit, so the cache effect is visible rather than guessed. The gap, if it is done right, should sit within measurement noise. It is also a good moment to decide where to place the player, a topic covered in how to add audio without touching your WordPress theme. The general rule fits in one sentence: a well-built audio player shows up when you listen, never in the load time. If you see the opposite, it is not the audio that is at fault, it is the way it was wired in.

Read next

• An audio player in the page or in an iframe: what that choice decides
• Image captions and photo credits: what French text to speech does with them
• Footnotes and note markers: what French text to speech does with them