Embedding a speed test on a website

Embedding a speed test adds a page dependency: iframe or JavaScript, network requests, caching and logging. An embedded speed test or IP widget should be evaluated for HTTPS/CSP compatibility, performance budget, availability and the technical data visible to the third party.

What to test before publishing

Test responsive layout, loading behaviour, blocked third-party requests and the privacy notice. Do not pass secrets or personal data in query strings. For an IP widget, remember that a public IP is network metadata and can appear in server logs.

The detail that matters

An embedded test can generate substantial traffic, so do not auto-start it unexpectedly on metered connections. Reserve layout space, explain that the test transfers data, use HTTPS, and verify that third-party failure does not break navigation or the surrounding page. To see the corresponding 2ip widget in practice, open 2ip speed-test widget.