wordunscrambler.me speed test — 20 Oct 2026

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

https://wordunscrambler.me/

20 October 2026 at 16:24 UTC · Free test · report pt_91cd1f000485
Grade
A
94/100
Performance95/100
Structure92/100

14 audit(s) passed, 2 need work

First byte (TTFB)380 msmeasured from this server
Fully loaded881 msfirst byte + slowest asset
Requests7document + assets
Page weight322.9 KBcompressed transfer
HTML document4.1 KBgzip
ProtocolHTTP/3nginx/1.14.2 + Phusion Passenger(R) 6.0.8
Third-party308.3 KBother hosts

Where the first byte went

  • DNS lookup 85 ms 22%
  • TCP connect 65 ms 17%
  • Server wait 230 ms 61%

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 60% of 4,999 pages tested here380 ms against a median of 449 ms
Page weightlighter than 70% of 4,999 pages tested here322.9 KB against a median of 650.5 KB
Fully loadedfaster than 94% of 4,999 pages tested here881 ms against a median of 1.84 s
Requestssends fewer requests than 91% of 4,999 pages tested here7 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 380 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 322.9 KB over 7 request(s), which is lean. Javascript files are 96% 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/3, so the assets share a connection instead of opening one each.
  • 95% 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 440 ms, inside the 2.5 s Google calls good.
  • The main thread was blocked for 42 ms in total, which is not enough to feel.

Fix first: Compress text responses - Turn on brotli (preferred) or gzip for text/css, javascript and text/html in the web server. This is the cheapest win available on almost any site.

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 wordunscrambler.me
Mobile 390 × 844 · 58.2 KB · page is 3195 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 paint440 msgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking time42 mslong tasks during load
First contentful paint440 msfirst content on screen
Browser page weight1.19 MB119 request(s), scripts included
Failed requests4blocked or unreachable
Largest contentful paint440 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking time42 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 3 requests
309.6 KB 96%
Images 2 requests
6.2 KB 2%
Css 1 request
3.0 KB 1%

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

Top issues

Compress text responses

high impact

1 text response(s) of 10 KB or more are sent uncompressed, and the document itself is not compressed. That is 131.3 KB of compressible text.

Fix: Turn on brotli (preferred) or gzip for text/css, javascript and text/html in the web server. This is the cheapest win available on almost any site.

Third-party weight

medium impact

2 third-party host(s) serve 308.3 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.

Waterfall

Slowest requests

IMAGESwordunscrambler.me/images/favicon.png
501 ms
JAVASCRIPTwordunscrambler.me/cdn/script-v10.js
493 ms
JAVASCRIPTwww.googletagmanager.com/gtag/js
461 ms
IMAGESwordunscrambler.me/images/wsm_logo.png
459 ms
CSSwordunscrambler.me/cdn/style-v39.css
452 ms
JAVASCRIPTsecurepubads.g.doubleclick.net/tag/js/gpt.js
391 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://wordunscrambler.me/images/favicon.pngimages200501 ms1.2 KB
https://wordunscrambler.me/cdn/script-v10.jsjavascript200493 ms1.3 KB
https://www.googletagmanager.com/gtag/js?id=G-8DWNLPX6CN 3rd partyjavascript200461 ms177.0 KB
https://wordunscrambler.me/images/wsm_logo.pngimages200459 ms5.0 KB
https://wordunscrambler.me/cdn/style-v39.csscss200452 ms3.0 KB
https://securepubads.g.doubleclick.net/tag/js/gpt.js 3rd partyjavascript200391 ms131.3 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.