www.dashlane.com speed test — 20 Oct 2026

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

https://www.dashlane.com/

20 October 2026 at 13:52 UTC · Free test · report pt_c0b4b21938d3

Re-test this page Test your own site

Grade

99/100

Performance100/100

Structure98/100

15 audit(s) passed, 1 need work

First byte (TTFB)175 msmeasured from this server

Fully loaded1.49 sfirst byte + slowest asset

Requests26document + assets

Page weight114.2 KBcompressed transfer

HTML document49.8 KBgzip

ProtocolHTTP/3cloudflare

Where the first byte went

DNS lookup 53 ms 30%
TCP connect 3 ms 2%
Server wait 119 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 96% of 4,999 pages tested here175 ms against a median of 449 ms

Page weightlighter than 86% of 4,999 pages tested here114.2 KB against a median of 650.5 KB

Fully loadedfaster than 71% of 4,999 pages tested here1.49 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 175 ms, which is fast: almost all of the wait is the page itself, not the host.
The page transfers 114.2 KB over 26 request(s). Images files are 56% of it, so resize and recompress the largest images before anything else.
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 1.07 s, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.057), so nothing jumps under the reader's cursor.
The main thread was blocked for 306 ms, so taps and scrolling wait while scripts run.

Fix first: Avoid extra redirects - 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.

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.

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 paint1.07 sgood is under 2.5 s

Cumulative layout shift0.057under 0.1 is stable

Total blocking time306 mslong tasks during load

First contentful paint484 msfirst content on screen

Browser page weight4.85 MB160 request(s), scripts included

Failed requests8blocked or unreachable

Largest contentful paint1.07 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.057

Goodgood under 0.1, poor over 0.25

Total blocking time306 ms

Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests

64.4 KB 56%

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

Top issues

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.