Curated guide

Add the Broadband Speed Test to a Website

Set up the legacy AuditMyPC broadband speed test on a website, with notes on hosting files, activation, and common setup errors.

Problem Summary

The archive pattern behind this guide is simple: site owners wanted the AuditMyPC speed test running on their own site, but the install stalled halfway. Sometimes only the download side worked. Sometimes the widget stayed blank. Other times the embed showed up, but the required support files were missing or never finished uploading.

Across threads like download-speed-not-activated, adding-speed-meter-to-my-web-page, and using-a-free-web-hosting-site-for-the-php-files, the recurring mistake was treating the test like a single snippet instead of a small package of files, scripts, and activation checks that all had to line up on the live server. That workflow is preserved here because it explains the old support cases, not because it is a current default way to add a speed test to a site.

Comment Highlights

One installation only worked halfway because the user could not upload the required zip package, which left the download side incomplete even though the page itself loaded.
Another case came down to the page-building software modifying the embed code after the user pasted it in, which made the published page behave differently from the original instructions.
A host change resolved one thread outright, which is strong evidence that the problem was not only the embed code. The hosting environment mattered.
A later follow-up reported results that looked accurate across multiple computers after the install was corrected, which helps separate setup failure from general distrust of the test itself in that archived setup.

Likely Causes

Required files were not all uploaded to the live server, or they were uploaded to the wrong public directory.
The site was published through a tool or editor that rewrote the embed code or changed paths after the user pasted the original snippet.
The hosting account did not support the server-side files the test expected, especially where PHP support or file placement was limited.
The site had not completed the expected authorization or domain activation step, so the visible embed and the server-side checks were out of sync.

What Still Applies

Treat a third-party test widget as a small application, not just a pasted block of markup. Verify every asset path on the published page in Broadband Speed Test Help.
If the install partially works, compare the live page against the file list the tool expects instead of assuming the visual embed is enough.
When the install is in place but results still fail, the next places to check are Speed Test Upload Error and Speed Test Logging Setup.
If the install problem only appears once the test is placed into WordPress, use WordPress Speed Test Integration instead of treating it as a generic hosting failure.
If the widget behaves differently between the editor and the live site, inspect the published HTML and file paths rather than trusting the builder UI.

Legacy Notes

This guide is based on an older hosted-test workflow with older browser and plugin assumptions. Keep the install logic, but treat the exact embed format and runtime expectations as legacy.

Some archive threads refer to older hosting products and file bundles that no longer exist in the same form. The durable part is the troubleshooting sequence: file placement, runtime support, activation, and live-path verification, not the exact package layout from the archive.

If you are adding a speed test to a new public site today, use a current supported service rather than trying to recreate the archived package exactly.

Related Guides

curated-guide

Parent Hub

hub

Broadband Speed Test Help

Legacy support hub for the AuditMyPC broadband speed test, covering installation, uploads, logging, and embed problems.