www.deepl.com/en speed test — 20 Oct 2026

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

https://www.deepl.com/en

20 October 2026 at 12:29 UTC · Free test · report pt_f179af983401

Re-test this page Test your own site

Grade

95/100

Performance100/100

Structure88/100

14 audit(s) passed, 2 need work

First byte (TTFB)152 msmeasured from this server

Fully loaded1.21 sfirst byte + slowest asset

Requests26document + assets

Page weight125.7 KBcompressed transfer

HTML document39.2 KBbr

ProtocolHTTP/3cloudflare

Third-party86.4 KBother hosts

Where the first byte went

DNS lookup 47 ms 31%
TCP connect 1 ms 1%
Server wait 104 ms 68%

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 98% of 4,999 pages tested here152 ms against a median of 449 ms

Page weightlighter than 85% of 4,999 pages tested here125.7 KB against a median of 650.5 KB

Fully loadedfaster than 87% of 4,999 pages tested here1.21 s against a median of 1.84 s

Requestssends more requests than 100% of 4,999 pages tested here26 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 server answered in 152 ms, which is fast: almost all of the wait is the page itself, not the host.
The page transfers 125.7 KB over 26 request(s). Images files are 69% of it, so resize and recompress the largest images before anything else.
The HTML itself arrives br-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
69% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
The largest element painted at 428 ms, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.002), so nothing jumps under the reader's cursor.
The main thread was blocked for 404 ms, so taps and scrolling wait while scripts run.

Fix first: Render-blocking resources - Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

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.

Desktop screenshot of www.deepl.com — **Desktop** 1366 × 768 · 251.5 KB · page is 6000 px tall

Mobile screenshot of www.deepl.com — **Mobile** 390 × 844 · 73.5 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 paint428 msgood is under 2.5 s

Cumulative layout shift0.002under 0.1 is stable

Total blocking time404 mslong tasks during load

First contentful paint428 msfirst content on screen

Browser page weight2.28 MB148 request(s), scripts included

Largest contentful paint428 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.002

Goodgood under 0.1, poor over 0.25

Total blocking time404 ms

Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 8 requests

86.4 KB 69%

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

Top issues

Render-blocking resources

high impact

16 render-blocking resource(s) in the document head (1 script(s), 15 stylesheet(s)). The page cannot paint until each one arrives.

Fix: Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

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.