We measured 40 agency websites.

Every agency in this study sells search performance. Most of them sell page speed explicitly — it is on their services pages, in their pitch decks and in their own blog posts about Core Web Vitals. So we measured their websites. Not their clients’ websites: their own. 37 of the best-known SEO and digital agencies in Germany and Romania, plus our own three domains, 40 sites in total, each measured twice over: what the homepage weighs, and what Google’s own PageSpeed Insights says about it across three consecutive runs.

Google PageSpeed Insights speed score, mobile

Every bar is one homepage on Google’s PageSpeed Insights, scored out of 100 on its mobile test. Google paints anything below 50 red and anything below 90 amber: only 3 of the 37 agency sites reach green. Select a bar for what that site weighs.

Every site we measured

Sorted by speed score, highest first — click any column heading to reorder. Speed and the three category scores come from Google PageSpeed Insights on mobile; every agency site in the field was measured three times and its median is shown, and Level UI’s own domains score 100 in all four. Page weight and requests: Lighthouse 12.8.2, mobile preset, measured 7 September 2026. “A11y” is accessibility, “Practices” is Google’s best-practices audit.

What we measured, and how many times

We loaded 40 homepages: 22 German agencies, 15 Romanian ones, and our own three domains. Each was measured twice over. Lighthouse 12.8.2 on its mobile preset gave us total page weight and the number of network requests. Google’s PageSpeed Insights gave us the four scores it publishes — performance, accessibility, best practices and SEO — and we ran it three times per site.

**Page weight and request count are properties of the website.** They are what the server chose to send. Run the test from Bucharest or Berlin, on a busy laptop or an idle one, and you get the same answer. That is why they lead the table.

**A PageSpeed performance score is not like that, and this is the part most comparisons get wrong.** It is lab data measured on Google’s machines, under whatever load those machines are under when your request arrives. Webdigital returned 77 / 63 / 46 across three consecutive runs — a 31-point spread on a page that did not change between them. 18 of the 40 sites moved ten points or more between their best and worst run.

So every PageSpeed number in this article is the **median of three runs**, and the table says so. If you run one of these sites yourself and get a different number, that is the tool, not a contradiction — run it three times and compare the middle value. The other three categories behave differently: accessibility, best practices and SEO are deterministic rule checks, and they returned the same score on nearly every pass.

Everything here was measured on 7 September 2026. Sites change. If you are reading this months later, re-run it — the method is in the sources at the bottom and takes about two minutes per site.

The lightest site in the study weighs 322 KiB. The heaviest weighs 189.5 MB.

The median agency site in this study ships 1,642 KiB across 92 requests. The German median is 1,522 KiB; the Romanian median is 2,376 KiB.

Wingmen at 342 KiB is the lightest agency site here, and it lands within 20 KiB of ours — proof that a light agency site is a choice rather than a constraint. At the other end, eprofessional ships 33.6 MB, and Kubis Interactive ships 189.5 MB across 879 requests — dozens of individual PNG files over two megabytes each, on a homepage. That is not a configuration mistake anyone made once; it is a site nobody has opened a network panel on.

For context, Kubis Interactive’s homepage alone would exhaust a 150 MB mobile data allowance in a single visit, with change owed. On a metered connection, opening it costs the visitor money.

What Google’s own speed test says about agency websites

The median competitor in this study scores 56 out of 100 for mobile performance. Google colours anything below 50 red and anything below 90 amber. 13 of the 37 agency sites — 35 per cent of them — sit in the red band, 21 sit in the amber, and 3 reach green at 90 or above. The best competitor is Wingmen at 93; the lowest is Xivic at 29.

**The other three categories are the more damning ones, precisely because they do not move between runs.** Accessibility, best practices and SEO are rule checks: the same page gets the same score every time, so there is no server load to blame. The competitor medians are 89 for accessibility, 96 for best practices and 100 for SEO.

3 of the 37 agency sites scored 100 on all three at once. SEO is where the field does best — the median there is 100, and that category is a floor rather than a ceiling: it checks that a page has a title and a meta description, that its links are crawlable, that its images carry alt text, and that canonical and hreflang are valid. Accessibility is where the field loses it, at a median of 89. That is not a ranking argument — it is the part of the audit that says some visitors cannot use the page at all.

Where we came out, and why that is not the point

Our three domains take the first three places on page weight: 322 KiB and 26 requests for the lightest, against a competitor median of 1,642 KiB and 92 requests. That is 5.1× lighter and 3.5× fewer requests than the middle of the field.

On PageSpeed our three domains take the first three places as well: levelui.com, levelui.ro and levelui.de each score 100 for speed, accessibility, best practices and SEO. The best competitor is Wingmen at 93, and the median agency site scores 56.

We are in the table because a study that measures everyone except its author is worth nothing. But the ranking is not the finding. The finding is that the median agency site is 5.1 times heavier than it needs to be, that the floor is already occupied by Wingmen, and that the categories nobody can blame on server load are the ones most of this industry is quietly failing.

There is nothing clever behind our own number. It is a full marketing site: a portfolio, a priced catalogue you can browse, a cart, three languages. It is light because every image is a modern format at a sane resolution, because the JavaScript that is not needed for the first screen is not downloaded for the first screen, and because nothing third-party loads unless a visitor asks for it. We wrote up the specifics in how to get a 100 PageSpeed score and what the metrics actually mean in Core Web Vitals explained.

How to check your own site in two minutes

Open your homepage in Chrome, press F12, go to the Network tab, tick “Disable cache”, and reload. The status bar at the bottom gives you both of the numbers this study leads with: how many requests, and how many bytes transferred. Compare that against the table above.

Then run [PageSpeed Insights](https://pagespeed.web.dev/) on the same URL three times and take the middle score. One run tells you very little — 18 of the 40 sites here moved ten points or more between their best and worst run.

If you are over a megabyte, the cause is almost always one of three things, in this order: uncompressed images, a font family loaded in six weights when the design uses two, and a tag manager pulling in analytics, chat, heatmaps and a cookie banner before anything is visible. In this study the heaviest sites were heavy for the first reason by a wide margin.

None of that needs a rebuild. It needs somebody to look. If you would rather we looked, our technical audit covers exactly this ground, and the SEO audit is free.

Method and tools

Everything in this article was measured on 7 September 2026 and can be reproduced with freely available tools. The full list of sites is in the table above.

• Google Lighthouse 12.8.2 ↗

  Run from the command line against each homepage, mobile preset, one run per site. Page weight is the total-byte-weight audit; request count is the length of the network-requests list.

• PageSpeed Insights ↗

  Run three times per homepage on the mobile strategy, collecting all four categories. The published figure is the median of the three runs.

• Lighthouse performance scoring ↗

  Google’s own documentation on why performance scores vary between runs of the same page, and why a single run should not be treated as a measurement.