Sample Report · Technical Measurement · September 2026
This site will be up in two seconds. It only responds after six.
This is a genuine technical report, with the client’s name removed. For each finding, the recommendation is listed as: replace, repair, leave as is, or withdrawn. The last one is included on purpose.
The same front page, the same day
Desktop · Broadband93
Phone · 4G65
GTmetrix performance score on the homepage, both on 12 September 2026. Chrome 142, Lighthouse 12.6.1. Phone on an iPhone 13 profile with 4G (9/5 Mbps, 125 ms), desktop on broadband (20/5 Mbps, 25 ms). Name, address and page names have been omitted; the figures have not been adjusted.
The Essence in Four Numbers
Operable
6.0 s
until a tap triggers an action, on average over nine pages on 4G. Standard: 2.5 s
Slowest page
12.6 s
to interactive; the fastest of the nine achieves 2.7 s
From third parties
63 %
JavaScript on the home page: tag manager, heat maps, pixels
Double H1
441
Pages with two main titles, the sitemap, and service pages combined
The homepage scores an A on desktop. If you only measure that, you won’t see the problem. The pages customers visit to be convinced are two to six times slower than the homepage. On a phone, the site doesn’t respond to a tap until well over four seconds have passed.
Five sections, each with a rating
Speed: nine pages, one connection
Nine pages, measured within ten minutes of each other using the same 4G profile. “Interactive” refers to the moment the page responds to a tap; “ready” is when it stops loading and moving. Not a single page meets the 2.5-second standard.
Seconds until it’s ready to use and until it’s done, nine pages on 4G
Black: currently operable; grey: until complete. Blue: same page, EQwise rebuilt, same measurement. The dotted line represents the 2.5-second standard.
| Page | Verdict | Operable (s) | Done (s) | Weight (kB) | Requests |
|---|---|---|---|---|---|
| Reviews | replace | 12.6 | 15.9 | 11.124 | 188 |
| References | replace | 7.6 | 8.9 | 3.004 | 188 |
| Service A | replace | 7.3 | 11.3 | 5.892 | 172 |
| Service B | replace | 6.3 | 8.3 | 3.314 | 160 |
| Service C | replace | 5.9 | 8.3 | 4.693 | 215 |
| Articles | repair | 5.0 | 7.6 | 3.309 | 181 |
| Service D | repair | 3.7 | 5.7 | 1.653 | 134 |
| About Us | repair | 3.1 | 6.4 | 1.525 | 136 |
| Service E | repair | 2.7 | 6.2 | 2.091 | 142 |
- Reviews: Reduce Image Size and Lazy Load
- References: same recipe
- Service A: nearly 7 MB of images on a page where someone is considering an expensive service
Where the weight is.
The reviews page consists of nine-tenths images: 9,907 kB across 69 files, for 49 customer quotes. In addition, there are 745 kB of JavaScript across 86 files and 201 kB of fonts across 6 files. The same page, rebuilt without a page builderPage builder An additional program in WordPress that allows you to build pages by dragging and dropping components. and with correctly sized images, weighs 586 kB across 17 requests and is interactive after 1.0 second. That’s a measured value, not an estimate.
Google’s three metrics
The metrics that Google itself uses, on the homepage, on a phone and on a desktop. Google’s standards are: the largest element on the screen within 2.5 seconds, blocking timeBlocking time The time during loading when a page does not respond because it is processing code. under 200 milliseconds, and layout shift under 0.1.
| Metric | Phone, 4G | Desktop | Standard | What It Means |
|---|---|---|---|---|
| Largest element in view | 2.2 s meets | 1.3 s meets | ≤ 2.5 s | The page is up on time. That’s not the problem. |
| Blocking Time | 259 ms fails | 2 ms meets | ≤ 200 ms | On a phone, there are times when a tap doesn’t do anything: the page is processing scripts. Nine days earlier, this took 6 ms. The site is growing. |
| Layout shift | 0.09 just meets | 0 meets | ≤ 0.1 | Images without dimensions don’t take up space until they’re loaded. The text shifts as you read. |
| Fully loaded | 6.3 s | 3.0 s | Guideline 3 s | On a desktop, it’s right at the limit; on a phone, it’s well beyond it. |
What Google Knows About the Site
Measured on 8 September and again on 15 September, using only status codesStatus Code A three-digit code used by a server to indicate whether a page has been found. and the sitemap. One finding no longer applied at the second measurement, and it has been deliberately left in.
| Finding | Number | Verdict |
|---|---|---|
| Pages in the sitemap, with the date of the last update | 201 | Leave it as is the sitemap is correct and is being updated |
| Pages with more than one main heading, the sitemap, and service pages combined | 441 | Fix the title appears in the top bar and in the text, both as the main title; Google and AI-generated answers can then infer what the page is about. One line in the template |
| Service cards arriving via a detour | 13 of 35 | repair seven services have been renamed, six cards are missing a slash; every click requires an extra trip to the server |
| Two different services at the same address | 1 pair | fix one of the two links doesn’t work when you click on it |
| Service cards linking to a page that doesn’t exist | 5 → 0 | Withdrawn five more on 8 September; resolved by the customer on 15 September. We remove any findings that have been resolved from the report. |
| Robots, canonicals, structured dataStructured data Additional information in the code that tells search engines and AI exactly what is on a page. | — | Leave it as is No blockages found |
On a phone
The same homepage, the same day, a phone versus a desktop. The difference isn’t in the image but in the processing power required to render the page on a phone. Consider the 919 elements that the browser has to recalculate with every movement and the 259 milliseconds during which a tap does nothing. In addition, there are seven separate files for a single font.
- Images are imported at desktop size and are resized by the phone itself. They are in an older format, often two to four times larger than the box they sit in. Recommendation: Replace with a modern format that fits the screen.
- Nothing is cut off at 375 and 390 px, and the buttons are large enough for a thumb. Verdict: keep it.
- The page doesn’t respond to a tap until well over four seconds have passed, even though it’s already readable after two seconds. In the meantime, visitors keep tapping, thinking the site is broken. Recommendation: Load third-party scripts only after the initial render.
What a visitor doesn’t see but does feel
Together, these five reasons explain why a faster server wouldn’t help.
| Finding | Number | Verdict |
|---|---|---|
| Dependency chains: files that wait for each other, like a line at a checkout counter | 99 chains, 137 requests | Replace with a single central source for layout and code, without any intermediate steps. A rebuilt page has two of them |
| Third-party scripts before the first page view: tag manager 345 kB, heatmaps 65, ad pixel 40, pop-ups 18, CRM 3 | 471 kB · 63% of all JavaScript | repair loads after consent and after the first view. This is a marketing decision, not a fundamental problem: no rebuild will fix it |
| Variable server response time: sometimes the page is already loaded, sometimes it is generated on the fly | factor 5 | repair a collection of ready-to-use pages that stays up to date |
| The same page, twice as slow: three desktop measurements with all settings identical yielded 1.7 s and 3.9 s | factors 2.3 and 34 | repair same cause; a continuous measurement makes it visible on the day it happens |
| The site is growing without any changes to its content: between 3 and 12 September, 3 requests and 60 kB were added | +60 kB in 9 days | repair a fixed test setup that runs monthly |
What Does Meet the Standard
You can tell just as well what’s good as what isn’t; that determines what you can leave alone.
- On desktop, the homepage meets all three of Google’s metrics: 1.3 s, 2 ms, 0.
- The sitemap is complete and up to date, and the content is kept current.
- When services were renamed, redirects were set up; the broken linksBroken link A link that points to a page that no longer exists. are gone.
- Nothing falls outside the screen on a phone, and tap targets are large enough.
- No restrictions for search enginesSearch engine A website used to search the internet, such as Google or Bing..
What This Does and Does Not Prove
What it proves
- These nine pages take 2.7 to 12.6 seconds to become interactive on a 4G connection. This is due to the page structureInformation Architecture The way in which all pages and information on a website are organised and interconnected. (chains, page builder, images) and not the server.
- The same page, without a page builder and with correctly sized images, is interactive after one second: measured across nine rebuilt pages, 0.9 to 1.0 s.
What It Doesn’t Prove
- Whether each visitor sees exactly these numbers depends on their device and connection. To determine this, we need the visitor data from Search ConsoleGoogle Search Console A free service from Google that shows how your website is performing in search results..
- The entire site loads in one second: pages with video or an order form are 200 to 300 kB larger.
Here’s how the measurements were taken
A service provider with over 200 pages on WordPress, using a page builder, operating in an English-speaking market. Eighteen GTmetrix measurementsGTmetrix An online measurement tool that tests how quickly a web page loads. taken between 3 and 13 September 2026: Amsterdam and London, Chrome 142, Lighthouse 12.6.1. Testing was conducted using an iPhone 13 profile on 4G (9/5 Mbps, 125 ms) and a desktop on broadband (20/5 Mbps, 25 ms).
Status codes and sitemap on 8 and 15 September. This is an anonymised example of an actual measurement: the name, web address, and page names have been omitted or replaced with a description.
Nine pages were measured within ten minutes of each other using the same 4G profile. The eighteen speed measurements were taken from Amsterdam and London, on a phone profile and on a desktop. They fell between 3 and 13 September 2026. Status codes and sitemap were measured on 8 and 15 September 2026. The report covers a single site of over two hundred pages.
How fast does your site load on a phone?
The front door is almost always faster than the shop behind it. On this site, the time it took for a visitor to be able to do something ranged from 2.7 to 12.6 seconds, on the same connection and on the same day. You can’t see that difference in a single measurement of the front page.
Written by
