Website Speed Test
Measure how fast your server responds and how heavy your page is, then get plain-language fixes. Honest measurements, no made-up score.
Test your page speed
Measure how your server and files behave, with plain-language fixes. No account, no stored data.
What usually makes local business sites slow
| Cause | What it does | Typical fix |
|---|---|---|
| Slow server response | Nothing can load until the first byte arrives. | Page caching, better hosting, fewer heavy plugins. |
| Oversized images | Photos straight from a phone or camera can be several megabytes. | Resize to the displayed size, compress, use WebP or AVIF. |
| Uncompressed text files | CSS and JavaScript travel at several times their needed size. | Turn on gzip or Brotli. |
| Scripts that block the page | The browser waits for them before it draws anything. | Add defer or async, remove unused plugins. |
| No browser caching | Returning visitors download everything again. | Send long Cache-Control lifetimes for static files. |
| Many third-party widgets | Chat, tracking and font services each add connections you do not control. | Keep only the ones that earn their place. |
How to use the results
- Run the test on the pages that matter: the homepage, your main service page and a location page.
- Test more than once. A cold server cache can make the first request look slower than normal.
- Start with the items marked to fix, then the ones to review. Notes are for context.
- Re-test after each change so you know what helped.
- Check real-visitor data in Google Search Console and PageSpeed Insights before deciding the site is fast or slow.
What a good result should show
A public page address such as https://example.com/services/, or a page's HTML pasted from View page source. Press Load sample HTML to try a made-up page with common problems.
A time-to-first-byte figure with a breakdown of where the time went, the measured download size, findings grouped into server response, page weight, files and caching, and how the page loads, plus a table of every file measured.
A server and file check, not a Core Web Vitals test
Core Web Vitals describe how a page feels to real visitors and need a real browser. This tool times your server and measures your files from our server. It gives no overall score on purpose, because a single number would imply a precision it cannot have. For lab and field Core Web Vitals use Google PageSpeed Insights and the Core Web Vitals report in Search Console.
How the test runs
- Request the page. Our server follows any redirects one step at a time, timing each, and records DNS, connection, secure connection, server wait and download.
- Repeat twice. The final page is requested two more times. The tool reports the median, so one unusually slow or fast request does not mislead you.
- Read the HTML. The tool lists the stylesheets, scripts, images and preloads in the page, and notes which scripts block rendering and which images lack dimensions.
- Measure the files. Up to 30 of those files are fetched, a few at a time, to record the real bytes sent, compression and cache headers. Private and non-web addresses are never contacted.
- Apply rules of thumb. The findings compare your numbers with published guidance where it exists, such as web.dev's time-to-first-byte bands, and with plain DigitalBaloch rules of thumb elsewhere. Each finding says which it is.
How the thresholds are set
| Check | Pass | Review | Fix |
|---|---|---|---|
| Time to first byte | 0.8 s or less | Up to 1.8 s | Over 1.8 s |
| Measured download | 1.5 MB or less | Up to 3 MB | Over 3 MB |
| Files in the HTML | 50 or fewer | 51 to 80 | Over 80 |
| Blocking scripts in the head | None | 1 or 2 | 3 or more |
| Image size | Flagged when a single image is over 200 KB | ||
The time-to-first-byte bands follow web.dev guidance. The page-weight, request-count and image-size lines are DigitalBaloch rules of thumb for local service sites, not Google thresholds.
Limits worth knowing
- No browser runs, so no JavaScript executes and nothing is rendered. Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift are not measured.
- Timings are taken from our server. A visitor far away, on a phone or on a slow network will see different numbers.
- Only files named in the HTML are measured, up to 30. Fonts, background images and anything loaded later by CSS or scripts are not counted, so real page weight is usually higher.
- Our test client may negotiate a different protocol than a modern browser, so the HTTP version shown is a hint, not proof.
- The "Time it from my device" button times only how long your browser waits for a first reply. The browser hides sizes and headers from that kind of request.
- Fetching a live URL needs the DigitalBaloch PHP service. On a static host the Paste HTML tab and the device check still work.
Related SEO tools
SEO Website Audit Tool
Audit one page for on-page, technical and local SEO issues.
Open tool →Meta Tag Analyzer
Review title, description, canonical, robots and social tags.
Open tool →Internal Link Checker
Find broken and weak internal links.
Open tool →XML Sitemap Generator
Build an XML sitemap from a URL list.
Open tool →Website Speed Test questions
Why is there no speed score?
A single score implies a precision this tool cannot honestly offer. It does not run your page in a browser, so it cannot calculate the metrics Google's score is built from. It shows measured timings and file sizes plus findings you can act on.
Is this the same as Google PageSpeed Insights?
No. PageSpeed Insights loads your page in a real browser and reports Core Web Vitals-related lab metrics and real-visitor data. This tool measures server response, transfer sizes, compression and caching from our server. They are complementary, and the report has a button that opens your page in PageSpeed Insights.
What is a good time to first byte?
web.dev suggests 0.8 seconds or less is good and over 1.8 seconds is poor. Our figure includes connection setup and is measured from our server, so a visitor's number will differ.
Why do my numbers change between tests?
Server load, caches and network conditions vary from moment to moment. The tool takes the median of three requests to reduce the noise, but small differences between runs are normal.
Why might the page weight look low?
Only files named directly in the HTML, up to 30, are measured. Fonts, images set in CSS and files loaded by JavaScript are not included, so the real page can be heavier. The report says how many files were measured out of how many were found.
What should I fix first?
Server response time, then image sizes, then compression and caching, then render-blocking scripts. The report orders findings by severity, and the items marked to fix come first.
What does "Time it from my device" do?
It makes three requests from your own browser and times how long it waits for the first reply. It is a rough check that includes your own network. It cannot see file sizes or headers because browsers hide them from cross-site requests.
Does speed affect Local SEO?
Page experience is one of many signals, and speed mainly helps by keeping visitors from leaving before they call or enquire. Treat speed work as protecting conversions, not as a guaranteed ranking boost.
Is my page or data stored?
No. The page is fetched, analysed and discarded. Pasted HTML never leaves your browser. Only a short-lived, hashed request counter is kept to prevent abuse.
Turn this report into a fix plan.
Our Local SEO team can review your results, fix the issues that matter and track the calls and enquiries that follow.