Hi, @martinratinaud. When prerendering is enabled, for the majority of site traffic, nothing changes.
The difference occurs for site traffic where there is a
user-agent header sent which we triggers our prerendering service. For those requests, the following occurs:
So, this is not us “scraping” the page. This is the prerendering service responding to incoming HTTP requests with a
user-agent which indicates we should be prerendering for it (
user-agents like Twitterbot, Googlebot, Bingbot, etc.).
The prerendering service is only triggered in two cases:
- when a new deploy occurs the prerendering service is used to generate a screenshot of the deploy (regardless of whether prerendering is enabled or not)
- while prerendering is enabled, an external request is received with a
user-agent requiring prerendering
Our prerendering service runs your site’s code and does exactly what it says to do. It behaves no differently than any other web browser would when fetching the page, including any MP3s it loads.
Note, our prerendering service is a fork of prerender.io’s open source project below:
Their best practices page has a possible solution for this. The solution would be to run the following before loading the MP3s to indicate that the page is ready for prerendering:
window.prerenderReady = true;
If there are other questions about this, please let us know.