www.moengage.com speed test — 20 Oct 2026

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

https://www.moengage.com/

20 October 2026 at 12:58 UTC · Free test · report pt_e5b00883f69a

Re-test this page Test your own site

Grade

93/100

Performance96/100

Structure88/100

12 audit(s) passed, 4 need work

First byte (TTFB)292 msmeasured from this server

Fully loaded1.86 sfirst byte + slowest asset

Requests26document + assets

Page weight408.7 KBcompressed transfer

HTML document82.5 KBbr

ProtocolHTTP/3cloudflare

Third-party326.2 KBother hosts

Where the first byte went

DNS lookup 48 ms 16%
TCP connect 5 ms 2%
Server wait 239 ms 82%

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

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

Fully loadedslower than 51% of 4,999 pages tested here1.86 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 292 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 408.7 KB over 26 request(s). Images files are 80% 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.
80% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
The largest element took 5.21 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.

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.

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 paint5.21 sgood is under 2.5 s

Cumulative layout shift0.000under 0.1 is stable

Total blocking timenone over 50 mslong tasks during load

First contentful paint5.21 sfirst content on screen

Browser page weight5.64 MB303 request(s), scripts included

Largest contentful paint5.21 s

Poorgood under 2.5 s, poor over 4 s

Cumulative layout shift0.000

Goodgood under 0.1, poor over 0.25

Total blocking timenone over 50 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests

326.2 KB 80%

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

Top issues

Render-blocking resources

high impact

3 render-blocking resource(s) in the document head (1 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.

Third-party weight

medium impact

1 third-party host(s) serve 326.2 KB of this page. Each one is another DNS lookup, TLS handshake and point of failure you do not control.

Fix: Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.

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.

Strict-Transport-Security

low impact

HSTS is not set, so the first visit on a hostile network can still be downgraded to HTTP.

Fix: Send Strict-Transport-Security with a max-age of at least six months. Add includeSubDomains once every subdomain is HTTPS.