Sample Report · Technical Measurement · September 2026
This site will be up in two seconds. He doesn’t listen until after six.
This is a purely 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 September 12, 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 drivable; 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 homepageHomepage The first page of a website, which you see when you only type in the domain name. 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. “ResponsiveResponsive design A design that automatically adapts to the screen, from smartphones to wide desktop monitors.” 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; gray: until complete. Blue: same page, EQwise rebuilt, same measurement. The dotted line represents the 2.5-second standard.
| Page | Verdict | Operable (s) | Done (s) | Size (kB) | Requests |
|---|---|---|---|---|---|
| Reviews | replace | 12,6 | 15,9 | 11.124 | 188 |
| References | replace | 7,6 | 8,9 | 3.004 | 188 |
| Department A | replace | 7,3 | 11,3 | 5.892 | 172 |
| Department B | replace | 6,3 | 8,3 | 3.314 | 160 |
| Department C | replace | 5,9 | 8,3 | 4.693 | 215 |
| Articles | repair | 5,0 | 7,6 | 3.309 | 181 |
| Department D | repair | 3,7 | 5,7 | 1.653 | 134 |
| About Us | repair | 3,1 | 6,4 | 1.525 | 136 |
| Department 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 JavaScriptJavaScript A programming language that makes web pages interactive, such as a drop-down menu. 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 a custom image, weighs 586 kB across 17 requests and is interactive after 1.0 second. That’s a measured value, not an estimate.
Google’s Three Sizes
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, block time under 200 milliseconds, and jump under 0.1.
| Size | Phone, 4G | Desktop | Standard | What It Means |
|---|---|---|---|---|
| Largest element in the image | 2.2 s | 1.3 s reaches | ≤ 2.5 s | The page is up on time. That’s not the problem. |
| Blocking TimeBlocking time The time during loading when a page does not respond because it is processing code. | 259 ms isn’t enough | 2 ms takes | ≤ 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. |
| Long Jump | 0.09 net | 0 gets | ≤ 0.1 | Images without dimensions don’t take up space until they’re loaded. The text scrolls as you read. |
| Fully charged | 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 September 8 and again on September 15, using only status codesStatus Code A three-digit code used by a server to indicate whether a page has been found. and the sitemapSitemap A list of all your website's pages, specifically designed for search engines.. One finding was omitted from that second measurement, but it has been intentionally 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 titleH1 The main title of a page, as defined within the code.; Google and AI-generated answers can then infer what the page is about. One line in the templateTemplate A fixed layout used for an entire group of pages simultaneously. |
| 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 serverServer A computer that is always on and provides websites or other services to visitors. |
| 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 | Resolved: —five more on September 8; resolved by the customer on September 15. We remove any findings that have been resolved from the report. |
| Robots, canonicals, structured data | — | 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. This is an older format, often two to four times larger than the box they’re 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 | loads after authorization 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 September 3 and 12, there were 3 requests and 60 KB 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 links are gone.
- Nothing on a phone stands out except the screen, and the touch targets are large enough.
- No restrictions for search engines.
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 structure (chains, page builder, images) and not the server.
- The same page, without a page builder and with a custom image, 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 Console.
- 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 measurements taken between September 3 and 13, 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 September 8 and 15. This is an anonymized example of an actual measurement: the name, web address, and page names have been omitted or replaced with a description.
How fast does your site load on a phone?
The front page almost always loads faster than the store page 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.
