www.shell.com speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 14:50 UTC. Grade A (97/100), with the screenshots, the timings and the fixes that matter.

https://www.shell.com/

20 October 2026 at 14:50 UTC · Free test · report pt_878ebcba567d
Grade
A
97/100
Performance98/100
Structure95/100

14 audit(s) passed, 2 need work

First byte (TTFB)265 msmeasured from this server
Fully loaded938 msfirst byte + slowest asset
Requests10document + assets
Page weight121.1 KBcompressed transfer
HTML document3.3 KBgzip
ProtocolHTTP/3Apache

Where the first byte went

  • DNS lookup 80 ms 30%
  • TCP connect 32 ms 12%
  • Server wait 153 ms 58%

Measured on the connection that fetched the HTML. Every other request on the page waits for the end of this bar before it can start.

How this page compares

First bytefaster than 82% of 4,999 pages tested here265 ms against a median of 449 ms
Page weightlighter than 86% of 4,999 pages tested here121.1 KB against a median of 650.5 KB
Fully loadedfaster than 93% of 4,999 pages tested here938 ms against a median of 1.84 s
Requestssends fewer requests than 88% of 4,999 pages tested here10 against a median of 26

Every report published here is in this comparison, so it is a reference population of pages tested from one server - not a benchmark of the whole web.

What these numbers mean

  • The first byte arrived in 265 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 121.1 KB over 10 request(s), which is lean. Fonts files are 49% of it, so subset the fonts and stop preloading the weights you do not render.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • The largest element painted at 656 ms, inside the 2.5 s Google calls good.
  • The main thread was blocked for 14 ms in total, which is not enough to feel.

Fix first: Cache static assets - Version filenames on change and serve them with a long max-age plus immutable. That is what makes a returning visitor fast.

Read on one shared server, not a visitor's phone: use it to compare pages against each other, not as a promise about every connection. We fix what these tests find.

Screenshot

What the page looks like

Loaded in headless Chromium on this server. Click an image to open it full size.

Mobile screenshot of www.shell.com
Mobile 390 × 844 · 122.3 KB · page is 6000 px tall

Browser render

The same URL loaded in a real browser, so these are the readings curl cannot produce. The grade above is still built from the server measurements.

Largest contentful paint656 msgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking time14 mslong tasks during load
First contentful paint520 msfirst content on screen
Browser page weight411.3 KB34 request(s), scripts included
Largest contentful paint656 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking time14 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Fonts 1 request
59.2 KB 49%
Javascript 1 request
43.6 KB 36%
Images 3 requests
9.2 KB 8%
Other 3 requests
5.1 KB 4%
Css 1 request
659 B 1%

Transfer size, compressed as sent. 10 request(s) in total, 121.1 KB across all of them.

Top issues

Cache static assets

medium impact

2 asset(s) answer without a Cache-Control max-age, so browsers revalidate them on every visit.

Fix: Version filenames on change and serve them with a long max-age plus immutable. That is what makes a returning visitor fast.

Avoid extra redirects

medium impact

1 redirect hop(s) before the page load started, each one a full round trip before the first byte.

Fix: Link to the canonical URL (and make sure http, the apex domain and www all point at it) so no visitor pays a redirect first.

Waterfall

Slowest requests

FONTSwww.shell.com/etc.clientlibs/amidala/clientlibs/them…
673 ms
OTHERwww.shell.com/etc.clientlibs/amidala/clientlibs/them…
635 ms
IMAGESwww.shell.com/etc.clientlibs/amidala/clientlibs/them…
572 ms
JAVASCRIPTwww.shell.com/etc.clientlibs/amidala/clientlibs/app.…
505 ms
IMAGESwww.shell.com/etc.clientlibs/amidala/clientlibs/them…
492 ms
OTHERwww.shell.com/.model.json
487 ms
CSSwww.shell.com/etc.clientlibs/amidala/clientlibs/them…
486 ms
IMAGESwww.shell.com/etc.clientlibs/amidala/clientlibs/them…
477 ms
OTHERwww.shell.com/.shelli18n.json
448 ms

Each bar is one request's own response time, scaled to the slowest. Assets were fetched in parallel, so the bars overlap in real time rather than stacking. first party third party

RequestTypeStatusTimeSize
https://www.shell.com/etc.clientlibs/amidala/clientlibs/theme-base/resources/fonts/shell-typeface-la-heavy-221208.woff2fonts200673 ms59.2 KB
https://www.shell.com/etc.clientlibs/amidala/clientlibs/theme-base/resources/favicon/manifest.jsonother200635 ms172 B
https://www.shell.com/etc.clientlibs/amidala/clientlibs/theme-base/resources/favicon/apple-touch-icon.pngimages200572 ms4.1 KB
https://www.shell.com/etc.clientlibs/amidala/clientlibs/app.min.ACSHASH0bc2854e6e6a136d0f15db62c82ab728.jsjavascript200505 ms43.6 KB
https://www.shell.com/etc.clientlibs/amidala/clientlibs/theme-base/resources/favicon/favicon.icoimages200492 ms4.5 KB
https://www.shell.com/.model.jsonother200487 ms4.1 KB
https://www.shell.com/etc.clientlibs/amidala/clientlibs/theme-base.ACSHASHb291465fc8d3c7bcefde74d34044b698.csscss200486 ms659 B
https://www.shell.com/etc.clientlibs/amidala/clientlibs/theme-base/resources/favicon/favicon.svgimages200477 ms691 B
https://www.shell.com/.shelli18n.jsonother200448 ms860 B
Report this page

The page is removed when the owner agrees. Sending this removes nothing by itself.

Run this test on your own site

The same engine, free, with the screenshots and the fixes. No account needed.