← All resources

The 50 biggest companies in Europe, and how fast their websites really are.

Every homepage from the top 50 of Fortune’s 2026 Europe 500, put through Google’s PageSpeed Insights three times and checked against what real visitors experience — on the same morning.

Europe’s 50 biggest companies took in $5.8 trillion in revenue between them, and every one of them has a corporate homepage that investors, journalists, job applicants and customers open first. So we measured them. We took the top 50 of Fortune’s 2026 Europe 500, ran each homepage through Google’s PageSpeed Insights on the mobile test three times, and set the lab score against Google’s own data on what real visitors experienced over the previous 28 days. The median score is 54 out of 100. Only one site reached Google’s green band, and that one turned out to be serving Google’s tools a different page from the one its visitors get. Real visitors fare better than the lab suggests, but fewer than half of these sites pass Google’s Core Web Vitals for them. The full table, the method and every caveat are below.

PageSpeed Insights speed score, mobile

Every bar is one corporate homepage on Google’s PageSpeed Insights mobile test, the median of three runs, scored out of 100. Google paints anything below 50 red and anything below 90 amber. Select a bar for its page weight and what real visitors experience.

97

Shell

Scored on a pre-rendered snapshot served only to Google’s tools; visitors get an empty page that builds itself with JavaScript.

Detail

  • No. 2 by revenue. Runs: 92 / 97 / 97.
  • Lab LCP 2.2 s; real-visitor LCP 3.0 s at the 75th percentile.
  • 200 KiB across 12 requests. Real visitors: fails Core Web Vitals on LCP and INP.

Median of three PageSpeed Insights runs per homepage, mobile strategy, Lighthouse 13.5.0, measured on 2 October 2026 between 08:07 and 08:35 UTC. Three sites could not be measured and are not shown; Gazprom has two valid runs instead of three.

All 50 companies

CompanyCountry
Shell2UK97 (pre-rendered)2.2 s3.0 s200 KiB12Fail
Volkswagen1Germany775.0 s2.5 s4,054 KiB26Fail
Electricité de France15France7010.2 s2.5 s1,995 KiB50Pass
Glencore3Switzerland705.6 s2.6 s2,753 KiB19Fail
Bosch Group22Germany697.1 s2.2 s2,303 KiB55Pass
Groupe BPCE40France685.3 s1.6 s2,499 KiB47Pass
TotalEnergies5France6810.1 s1.8 s1,952 KiB42Pass
Gazprom16Russia654.8 s2.2 s3,045 KiB34Pass
BNP Paribas10France646.3 s2.0 s2,311 KiB64Fail
EP Group43Czechia645.3 s2.7 s8,197 KiB87Fail
Christian Dior29France637.9 s2.1 s1,969 KiB51Pass
Société Générale23France637.2 s1.9 s5,530 KiB116Pass
Banco Bilbao Vizcaya Argentaria33Spain617.1 s2.2 s888 KiB61Fail
BP4UK6113.4 s1.6 s2,309 KiB55Pass
Barclays44UK605.7 s1.9 s9,469 KiB83Pass
HSBC Holdings11UK6010.3 s1.8 s1,774 KiB39Pass
UBS Group41Switzerland6010.2 s1.4 s1,458 KiB95Pass
BMW Group7Germany5911.8 s2.7 s3,858 KiB132Fail
Mercedes-Benz Group8Germany579.2 s2.7 s1,193 KiB106Fail
Allianz14Germany5615.6 s2.1 s2,905 KiB104Pass
Banco Santander9Spain559.5 s2.4 s10,080 KiB113Pass
REWE Group21Germany5518.7 s1.4 s6,844 KiB71Pass
Stellantis6Netherlands5516.7 s1.5 s3,795 KiB53Pass
JBS34Netherlands5426.9 s2.1 s6,180 KiB78Pass
Tesco24UK5320.8 s2.1 s6,434 KiB57Pass
Deutsche Bank46Germany5211.6 s2.4 s2,033 KiB61Pass
Engie39France5218.8 s2.1 s8,060 KiB75Fail
Royal Ahold Delhaize20Netherlands5218.7 s2.0 s3,190 KiB46Pass
E.ON31Germany5115.8 s7.8 s2,926 KiB213Fail
Siemens32Germany504.9 s3.2 s4,449 KiB130Fail
ING Group45Netherlands4839.6 s3.7 s13,543 KiB100Fail
AXA18France4720.0 s3.8 s4,211 KiB73Fail
DHL Group28Germany4715.8 s2.5 s2,490 KiB103Pass
Rosneft Oil26Russia4716.0 s3.1 s3,130 KiB117Fail
Crédit Agricole37France4613.4 s5.6 s2,115 KiB42Fail
Equinor19Norway4611.3 s2.8 s2,196 KiB63Fail
Roche Group42Switzerland4312.5 s3.4 s1,926 KiB51Fail
BASF47Germany4215.6 s2.9 s2,765 KiB117Fail
Deutsche Telekom13Germany427.6 s1.3 s1,102 KiB79Fail
Enel30Italy4213.4 s4.1 s2,664 KiB61Fail
ENI27Italy4116.3 s2.8 s3,599 KiB115Fail
Nestlé17Switzerland4014.8 s6.1 s2,543 KiB82Fail
Airbus38Netherlands3910.6 s2.2 s5,635 KiB51Fail
Carrefour25France387.4 s2.3 s993 KiB65Fail
Orlen48Poland3712.4 s2.3 s4,491 KiB40Fail
Lloyds Banking Group35UK2913.3 s1.3 s2,269 KiB57Pass
Bunge Global49Switzerland2615.7 s2.8 s2,421 KiB75Fail
Sberbank12Russia——————
Vinci36France——————
VTB Bank50Russia——————

Fortune rank is by revenue in the Fortune Europe 500, 2026. Speed score, lab LCP, page weight and requests: median of three PageSpeed Insights mobile runs on 2 October 2026. Real-visitor LCP and the Core Web Vitals verdict come from the Chrome UX Report for the whole site (origin), 75th percentile over the previous 28 days; “Pass” means LCP, INP and CLS are all in Google’s good range. A dash means the homepage could not be measured.

What we measured, and how

The list is the top 50 of the Fortune Europe 500 for 2026, published on 16 September 2026 and ranked by revenue. Volkswagen leads it at $363.1 billion, followed by Shell, Glencore, BP and TotalEnergies. For each company we tested the corporate homepage — volkswagen-group.com rather than a car configurator, group.mercedes-benz.com rather than a showroom — because that is the one site every company on the list has and the one it controls centrally.

Each homepage went through Google’s PageSpeed Insights on its mobile test three times, and we kept the median. Lighthouse, the engine behind it, simulates a mid-tier phone on a mobile network, and its score moves between runs on its own: Crédit Agricole returned 33, 46 and 61 on three consecutive runs of a page that did not change, and 16 of the 47 sites moved ten points or more between their best and worst run. A single run is a sample, not a measurement. We only counted a run when its timestamp was new, because PageSpeed sometimes re-serves a cached result.

The same response carries a second, very different set of numbers: the Chrome UX Report, Google’s record of what real Chrome users experienced on the whole site over the previous 28 days. That is the data Google uses for its Core Web Vitals assessment, and it is the column most studies leave out. We report both, because they disagree more than anyone would expect.

Everything was measured on the morning of 2 October 2026 from Google’s own servers, with Lighthouse 13.5.0. Before trusting any score, we checked that Google had received the real homepage and not an error page, a bot challenge or a cookie wall — which is how we found the one result in this study that does not mean what it says.

The headline numbers

The median homepage of Europe’s 50 biggest companies scores 54 out of 100 on Google’s mobile test. Seventeen of the 47 we could measure sit in Google’s red band below 50, 29 sit in the amber band, and one reaches green. The lowest scores belong to Bunge at 26, Lloyds Banking Group at 29, Orlen at 37, Carrefour at 38 and Airbus at 39.

The median homepage weighs 2,753 KiB across 64 requests, and in Lighthouse’s simulation its largest element takes 11.6 seconds to appear. Google’s target for that measure, Largest Contentful Paint, is 2.5 seconds. In the lab, exactly one homepage meets it.

The biggest companies in Europe do not have fast websites, and it is not for lack of budget. These are businesses with entire digital departments and agency rosters. Whatever is making their homepages slow, it is not that nobody could afford to fix it.

The 97 that isn’t: Shell

Shell tops the chart with 97, the only green score in the study, on a homepage of 200 KiB and 12 requests. That is so far from everybody else that we checked what Google had actually been sent. A normal phone browser asking for shell.com receives 9 KB of HTML with an empty body and not a single link: the page builds itself afterwards with JavaScript. The same request with Lighthouse’s user agent, or Googlebot’s, receives 95 KB of finished HTML with 53 links and a response header from Prerender.io, a service that renders pages in advance for crawlers.

So Shell’s 97 is the score of a pre-rendered snapshot that only Google’s tools are served; visitors never get that page. Google itself calls this technique, dynamic rendering, “a workaround and not a recommended solution”, and recommends server-side rendering, static rendering or hydration instead. It is not cloaking as long as the content matches, and there is no sign here that it does not. But it does mean the lab score measures the wrong page.

The real-visitor data agrees. Over the previous 28 days, Shell’s site failed Google’s Core Web Vitals for real visitors, with the largest element taking 3.0 seconds at the 75th percentile and taps taking 229 milliseconds to respond, both outside Google’s good range. We checked all 50 homepages the same way. Shell is the only one that sends Lighthouse a different page. Leave it out, and the best score in the study is Volkswagen’s 77.

The lab says 11.6 seconds. Real visitors say 2.3

The most striking thing in the data is how far apart the two kinds of measurement are. In Lighthouse’s simulation the median homepage needs 11.6 seconds for its largest element. Real visitors to the same sites wait 2.3 seconds at the 75th percentile. Seventeen companies have a lab LCP over ten seconds and a real-visitor LCP inside Google’s good range of 2.5 seconds.

Both numbers are honest; they measure different things. The lab loads the page once, with an empty cache, on a simulated mid-tier phone and a throttled mobile connection. The Chrome UX Report averages real Chrome users across the whole site over 28 days, and the people who open a corporate homepage are disproportionately investors, analysts and journalists on recent phones and office connections, many of them on their second or tenth visit. Lloyds Banking Group shows the gap at its widest: 29 in the lab, the second-lowest score in the study, yet its real visitors pass all three Core Web Vitals.

Even on the friendlier measure, most of these sites fall short. Twenty-one of the 47 pass all three Core Web Vitals for real visitors — 45%. Twenty-eight are in the good range for loading, 38 for responsiveness and 38 for layout stability. Of the ten biggest companies by revenue, four pass: BP, TotalEnergies, Stellantis and Banco Santander. Volkswagen, number one by revenue and best in the lab after Shell, misses on loading by 48 milliseconds.

Bigger companies do have faster sites, slightly

There is a relationship between size and speed, and it runs the way you would hope. Ranked by revenue and by speed score, the 47 companies show a rank correlation of 0.49: a moderate tendency for the bigger company to have the faster homepage. The ten biggest have a median score of 62.5; the other 37 a median of 51.

It is a tendency, not a rule. Glencore, third by revenue, scores 70; Nestlé, seventeenth, scores 40; Groupe BPCE at number 40 scores 68 and passes every real-visitor test. Whatever decides how fast these homepages are, it is something their web teams choose, not something their size hands them.

Page weight is not what slows them down. JavaScript is

The heaviest homepages are very heavy. ING’s weighs 13.2 MB, Banco Santander’s 9.8 MB and Barclays’ 9.2 MB; ten of the 47 are over 5 MB. The lightest real ones, setting Shell aside, are BBVA at 888 KiB, Carrefour at 993 KiB and Deutsche Telekom at 1,102 KiB.

Yet across these 47 sites, page weight barely predicts the score at all — what predicts it is how long the main thread is blocked by JavaScript. The rank correlation between weight and score is −0.08, close to nothing. Blocking time is where the slowest homepages stand out: Orlen’s main thread is blocked for 976 milliseconds, Airbus’s for 803, Siemens’ for 798, BASF’s for 787 and Nestlé’s for 763. Lighthouse treats 200 milliseconds as the threshold for good. Big images cost bandwidth; scripts that run before the page can respond cost the score.

This matches what we found when we speed-tested 40 agency websites: weight is the easiest thing to measure and rarely the whole story. The work that moves a score is in the server and the scripts, and the full method for getting to 100 is in how to get a 100 PageSpeed score.

Pages that jump, and taps that wait

Two of the three Core Web Vitals are about what happens after the page appears. Cumulative Layout Shift measures how much the layout jumps while it loads; Google’s good range is 0.1 or less. In the lab, Carrefour’s homepage scores 0.63, Bunge’s 0.54, Deutsche Telekom’s 0.46 and Lloyds Banking Group’s 0.44 — the kind of jump that moves a button just as someone goes to tap it.

Interaction to Next Paint measures how long the page takes to respond to a tap or a click, in real use; good is 200 milliseconds or less. Most of these sites manage it, but some do not by a long way. Real visitors to BBVA’s site wait 1,698 milliseconds for a response at the 75th percentile, more than eight times the target. Nestlé’s visitors wait 390 milliseconds and Siemens’ 387. On a corporate site that is mostly reading, a slow tap usually means a heavy script busy doing something else when the visitor reaches for the screen.

What the three metrics measure, and why Google chose them, is in Core Web Vitals explained.

By country and by sector

Splitting 47 sites by country leaves small groups, so treat this as a description rather than a league table. France’s ten companies have the best median score at 63. The UK’s six score 60, Germany’s twelve 53.5, the Netherlands’ five 52 and Switzerland’s five 43. The single Czech, Norwegian and Polish companies score 64, 46 and 37, which says something about EP Group, Equinor and Orlen and nothing about their countries.

By sector, the two biggest groups are almost level: fourteen financial companies have a median of 58 and fourteen energy companies 56.5. Food and drink is weakest, with Nestlé, JBS and Bunge at a median of 40. The pattern that matters is not between countries or industries; it is between individual web teams, which is where the decisions are made.

The three we could not measure

Three homepages did not produce a result, and we report them rather than quietly dropping them. Sberbank’s page never painted anything in Google’s test, three times out of three. VTB Bank’s could not be loaded at all from Google’s servers. Both are Russian banks, and both were tested from the same place as every other site, so we record them as unreachable from Google’s test machines, not as slow.

Vinci, the French construction group, is the odd one out. Its homepage loads normally from our office, in a browser and with Lighthouse’s user agent. Google’s servers were told, three times, that the page was not HTML at all — most likely bot protection treating Google’s data-centre addresses differently. The site may well be fast; from where Google measures, it is not there.

Gazprom produced two valid runs rather than three, and its median is the middle of two. We left it in, marked in the chart footnote, because two runs is still more than most published speed comparisons use.

Why a corporate homepage’s speed matters at all

None of these companies sells anything on its corporate homepage, so it is fair to ask whether any of this matters. It matters in three smaller ways. The homepage is the first impression for the people a company most wants to impress — investors, journalists, graduates deciding where to apply — and a page that takes eleven seconds on a phone in the lab is one some of them will close. Speed is also one of the signals Google uses for page experience: a tie-breaker in the results rather than a lever, but a tie-breaker on some of the most searched company names in the world.

The third is less obvious. Two of these homepages, Shell’s and Tesco’s, send almost no content in their HTML and build the page with JavaScript. Five more — Allianz, E.ON, Bunge, REWE Group and Nestlé — answered a plain request from our office with a bot challenge instead of the page. Google renders JavaScript and is let through. Many of the new AI crawlers do not run JavaScript at all, which is the subject of what AI crawlers actually send back. A page that is empty without scripts depends on every reader being able to run them.

For a smaller business the lesson is the reassuring one. If the biggest companies in Europe ship a median of 2.7 MB and fail real-visitor Core Web Vitals more often than not, a small company’s site can be faster than theirs with a few weeks of careful work. A fast site is a series of choices, not a budget line — the same thing we found in what popular websites have in common.

How to check your own site the same way

Open [PageSpeed Insights](https://pagespeed.web.dev/), enter your homepage and run it three times; take the middle score. Then look at the top section, “Discover what your real users are experiencing”. If your site has enough Chrome traffic, that is the Chrome UX Report, and it is the verdict Google uses for Core Web Vitals. If the two disagree, believe the real-visitor data about your visitors and the lab data about what to fix.

If the score is surprisingly high, check what Google was served. Open the “View treemap” or the final screenshot in the report and make sure it is your page, not a cookie wall, an error or a snapshot made for crawlers. If it is low, look at Total Blocking Time before page weight: in this study, scripts explained far more than bytes did.

If you want somebody else to do it, a technical audit covers exactly this ground, page by page. Or ask us about web development if the answer turns out to be a rebuild — it often is not.

Method, tools and sources

Every score in this article was measured on 2 October 2026 between 08:07 and 08:35 UTC through the PageSpeed Insights API, mobile strategy, three distinct runs per homepage, and can be reproduced with the tools below. The company list and ranks are Fortune’s.

Frequently asked questions

Want to know how your site compares?

We will measure it the same way — lab and real visitors — tell you what is slowing it down, and give you the fixes in priority order.