my.games speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 14:06 UTC. Grade C (74/100), with the screenshots, the timings and the fixes that matter.

https://my.games/

20 October 2026 at 14:06 UTC · Free test · report pt_ff22f736ba49
Grade
C
74/100
Performance74/100
Structure74/100

10 audit(s) passed, 6 need work

First byte (TTFB)1.15 smeasured from this server
Fully loaded1.62 sfirst byte + slowest asset
Requests3document + assets
Page weight539.2 KBcompressed transfer
HTML document1.9 KBgzip
ProtocolHTTP/3nginx/1.27.5
Third-party537.4 KBother hosts

Where the first byte went

  • DNS lookup 120 ms 10%
  • TCP connect 209 ms 18%
  • Server wait 822 ms 71%

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 byteslower than 90% of 4,999 pages tested here1.15 s against a median of 448 ms
Page weightlighter than 56% of 4,999 pages tested here539.2 KB against a median of 650.5 KB
Fully loadedfaster than 63% of 4,999 pages tested here1.62 s against a median of 1.84 s
Requestssends fewer requests than 95% of 4,999 pages tested here3 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 took 1.15 s. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
  • The page transfers 539.2 KB over 3 request(s), which is lean. Javascript files are 84% 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.
  • 100% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.

Fix first: Server response time (TTFB) - Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

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 my.games
Mobile 390 × 844 · 2.7 KB · page is 844 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 paintnot reportedgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking timenone over 50 mslong tasks during load
First contentful paintnot reportedfirst content on screen
Browser page weight1.02 MB24 request(s), scripts included
Largest contentful paintnot reported
Goodgood 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

Javascript 1 request
451.3 KB 84%
Css 1 request
86.1 KB 16%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 1151 ms. Of that, 822 ms was the server thinking and 329 ms was connection setup. A first byte under 400 ms is what a visitor feels as instant.

Fix: Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

Compress text responses

high impact

2 text response(s) of 10 KB or more are sent uncompressed, and the document itself is not compressed. That is 537.4 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.

Cache static assets

medium impact

2 asset(s) answer without a Cache-Control max-age, so browsers revalidate them on every visit.

Fix: Version filenames on change and serve them with a long max-age plus immutable. That is what makes a returning visitor fast.

Third-party weight

medium impact

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

JavaScript weight

medium impact

1 JavaScript file(s) over 200 KB: D075okFX.js (451.3 KB)

Fix: Split routes, remove unused dependencies, and prefer a two-file build (one pinned library, one application bundle) over many small ones.

Waterfall

Slowest requests

CSSabout-mg-static.prod-my.games/b2c/_nuxt/entry.naxA36ZV.css
469 ms
JAVASCRIPTabout-mg-static.prod-my.games/b2c/_nuxt/D075okFX.js
360 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://about-mg-static.prod-my.games/b2c/_nuxt/entry.naxA36ZV.css 3rd partycss200469 ms86.1 KB
https://about-mg-static.prod-my.games/b2c/_nuxt/D075okFX.js 3rd partyjavascript200360 ms451.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.