www.mailerlite.com speed test — 20 Oct 2026

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

https://www.mailerlite.com/

20 October 2026 at 13:58 UTC · Free test · report pt_3654c0cad9a9

Re-test this page Test your own site

Grade

93/100

Performance95/100

Structure91/100

13 audit(s) passed, 3 need work

First byte (TTFB)303 msmeasured from this server

Fully loaded2.14 sfirst byte + slowest asset

Requests26document + assets

Page weight888.3 KBcompressed transfer

HTML document43.9 KBbr

ProtocolHTTP/3cloudflare

Third-party124.5 KBother hosts

Where the first byte went

DNS lookup 85 ms 28%
TCP connect 55 ms 18%
Server wait 163 ms 54%

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

Page weightheavier than 59% of 4,999 pages tested here888.3 KB against a median of 650.3 KB

Fully loadedslower than 62% of 4,999 pages tested here2.14 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 first byte arrived in 303 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 888.3 KB over 26 request(s). Images files are 95% 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.
The largest element painted at 584 ms, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.038), so nothing jumps under the reader's cursor.
The main thread was blocked for 185 ms in total, which is not enough to feel.

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.mailerlite.com — **Desktop** 1366 × 768 · 83.4 KB · page is 6000 px tall

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

Cumulative layout shift0.038under 0.1 is stable

Total blocking time185 mslong tasks during load

First contentful paint564 msfirst content on screen

Browser page weight2.30 MB59 request(s), scripts included

Failed requests1blocked or unreachable

Largest contentful paint584 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.038

Goodgood under 0.1, poor over 0.25

Total blocking time185 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests

844.4 KB 95%

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

Top issues

Render-blocking resources

high impact

4 render-blocking resource(s) in the document head (2 script(s), 2 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.

Total page weight

medium impact

The page transfers 888.3 KB across 26 request(s), with the document itself at 43.9 KB.

Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.

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.