www.orange.fr/portail speed test — 20 Oct 2026

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

https://www.orange.fr/portail

20 October 2026 at 12:54 UTC · Free test · report pt_b02048df6a47
Grade
A
90/100
Performance88/100
Structure92/100

14 audit(s) passed, 2 need work

First byte (TTFB)651 msmeasured from this server
Fully loaded1.39 sfirst byte + slowest asset
Requests6document + assets
Page weight140.6 KBcompressed transfer
HTML document490 Bgzip
ProtocolHTTP/2Apache
Third-party140.1 KBother hosts

Where the first byte went

  • DNS lookup 70 ms 11%
  • TCP connect 181 ms 28%
  • Server wait 401 ms 62%

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 byteslower than 67% of 4,999 pages tested here651 ms against a median of 448 ms
Page weightlighter than 84% of 4,999 pages tested here140.6 KB against a median of 650.5 KB
Fully loadedfaster than 78% of 4,999 pages tested here1.39 s against a median of 1.84 s
Requestssends fewer requests than 92% of 4,999 pages tested here6 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 took 651 ms. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
  • The page transfers 140.6 KB over 6 request(s), which is lean. Javascript files are 69% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/2, so the assets share a connection instead of opening one each.
  • 100% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
  • The largest element took 3.20 s to paint, past the 2.5 s threshold: usually a hero image that is too big or a render-blocking script in front of it.
  • Layout shift is 0.802 (good is under 0.1): something without a reserved size is loading late - an image, an ad, or a font swap.
  • The main thread was blocked for 110 ms in total, which is not enough to feel.

Fix first: Server response time (TTFB) - Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

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.orange.fr
Mobile 390 × 844 · 65.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 paint3.20 sgood is under 2.5 s
Cumulative layout shift0.802under 0.1 is stable
Total blocking time110 mslong tasks during load
First contentful paint1.90 sfirst content on screen
Browser page weight3.57 MB134 request(s), scripts included
Largest contentful paint3.20 s
Needs improvementgood under 2.5 s, poor over 4 s
Cumulative layout shift0.802
Poorgood under 0.1, poor over 0.25
Total blocking time110 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 1 request
96.6 KB 69%
Css 1 request
37.8 KB 27%
Images 3 requests
5.7 KB 4%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 651 ms. Of that, 401 ms was the server thinking and 251 ms was connection setup. A first byte under 400 ms is what a visitor feels as instant.

Fix: Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

Avoid extra redirects

medium impact

2 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

JAVASCRIPThporange.cdn.s.woopic.com/sg1/sg1_accueils.452eb4fba183b2ffb9ea.js
740 ms
IMAGEShporange.cdn.s.woopic.com/sg1/favicon-16x16.png
675 ms
CSShporange.cdn.s.woopic.com/sg1/sg1_accueils.f246d259c6787a7543a5.css
668 ms
IMAGEShporange.cdn.s.woopic.com/sg1/favicon-32x32.png
650 ms
IMAGEShporange.cdn.s.woopic.com/sg1/apple-touch-icon.png
572 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://hporange.cdn.s.woopic.com/sg1/sg1_accueils.452eb4fba183b2ffb9ea.js?profile=hp 3rd partyjavascript200740 ms96.6 KB
https://hporange.cdn.s.woopic.com/sg1/favicon-16x16.png 3rd partyimages200675 ms275 B
https://hporange.cdn.s.woopic.com/sg1/sg1_accueils.f246d259c6787a7543a5.css 3rd partycss200668 ms37.8 KB
https://hporange.cdn.s.woopic.com/sg1/favicon-32x32.png 3rd partyimages200650 ms957 B
https://hporange.cdn.s.woopic.com/sg1/apple-touch-icon.png 3rd partyimages200572 ms4.5 KB
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.