app.apuestasroyal.com speed test — 20 Oct 2026

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

https://app.apuestasroyal.com/

20 October 2026 at 16:27 UTC · Free test · report pt_7792107ad60d
Grade
A
93/100
Performance95/100
Structure89/100

12 audit(s) passed, 4 need work

First byte (TTFB)382 msmeasured from this server
Fully loaded1.08 sfirst byte + slowest asset
Requests11document + assets
Page weight855.6 KBcompressed transfer
HTML document670 Bbr
ProtocolHTTP/3cloudflare

Where the first byte went

  • DNS lookup 93 ms 24%
  • TCP connect 12 ms 3%
  • Server wait 278 ms 73%

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 59% of 4,999 pages tested here382 ms against a median of 449 ms
Page weightheavier than 58% of 4,999 pages tested here855.6 KB against a median of 650.3 KB
Fully loadedfaster than 91% of 4,999 pages tested here1.08 s against a median of 1.84 s
Requestssends fewer requests than 87% of 4,999 pages tested here11 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 382 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 855.6 KB over 11 request(s), which is lean. Javascript files are 59% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
  • 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 2.40 s, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.002), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 642 ms, so taps and scrolling wait while scripts run.

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

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 app.apuestasroyal.com
Mobile 390 × 844 · 57.1 KB · page is 2447 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 paint2.40 sgood is under 2.5 s
Cumulative layout shift0.002under 0.1 is stable
Total blocking time642 mslong tasks during load
First contentful paint1.22 sfirst content on screen
Browser page weight3.08 MB61 request(s), scripts included
Largest contentful paint2.40 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.002
Goodgood under 0.1, poor over 0.25
Total blocking time642 ms
Poorgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 1 request
508.2 KB 59%
Css 1 request
252.7 KB 30%
Images 5 requests
93.2 KB 11%
Html 2 requests
669 B 0%
Other 1 request
276 B 0%

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

Top issues

JavaScript weight

medium impact

1 JavaScript file(s) over 200 KB: assetindex-B0EU18mT.js (508.2 KB)

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

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.

Mobile viewport

medium impact

No viewport meta tag, so a phone renders the desktop layout scaled down.

Fix: Add a viewport meta tag with width=device-width and an initial scale of 1.

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.

Waterfall

Slowest requests

HTMLapp.apuestasroyal.com/https://pics.apuestasroyal.com/bingoag…
694 ms
OTHERapp.apuestasroyal.com/manifest.json
679 ms
IMAGESapp.apuestasroyal.com/icons/favicon-128x128.png
583 ms
IMAGESapp.apuestasroyal.com/icons/favicon-96x96.png
572 ms
IMAGESapp.apuestasroyal.com/favicon.ico
549 ms
JAVASCRIPTapp.apuestasroyal.com/assets/assetindex-B0EU18mT.js
545 ms
CSSapp.apuestasroyal.com/assets/assetindex-DOFfL3DC.css
529 ms
IMAGESapp.apuestasroyal.com/icons/favicon-16x16.png
529 ms
IMAGESapp.apuestasroyal.com/icons/favicon-32x32.png
526 ms
HTMLapp.apuestasroyal.com/cdn-cgi/scripts/7d0fa10a/cloudflare-st…
518 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://app.apuestasroyal.com/https://pics.apuestasroyal.com/bingoagover02a.jpghtml200694 ms669 B
https://app.apuestasroyal.com/manifest.jsonother200679 ms276 B
https://app.apuestasroyal.com/icons/favicon-128x128.pngimages200583 ms5.8 KB
https://app.apuestasroyal.com/icons/favicon-96x96.pngimages200572 ms3.9 KB
https://app.apuestasroyal.com/favicon.icoimages200549 ms81.9 KB
https://app.apuestasroyal.com/assets/assetindex-B0EU18mT.jsjavascript200545 ms508.2 KB
https://app.apuestasroyal.com/assets/assetindex-DOFfL3DC.csscss200529 ms252.7 KB
https://app.apuestasroyal.com/icons/favicon-16x16.pngimages200529 ms473 B
https://app.apuestasroyal.com/icons/favicon-32x32.pngimages200526 ms1.1 KB
https://app.apuestasroyal.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.jshtml404518 ms0 B
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.