superbet.ro speed test — 20 Oct 2026

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

https://superbet.ro/

20 October 2026 at 14:23 UTC · Free test · report pt_d5d0ee283839
Grade
D
65/100
Performance47/100
Structure91/100

15 audit(s) passed, 1 need work

First byte (TTFB)5.23 smeasured from this server
Fully loaded6.08 sfirst byte + slowest asset
Requests6document + assets
Page weight160.2 KBcompressed transfer
HTML document2.6 KBgzip
ProtocolHTTP/3AmazonS3

Where the first byte went

  • DNS lookup 5.11 s 98%
  • TCP connect 21 ms 0%
  • Server wait 100 ms 2%

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 99% of 4,999 pages tested here5.23 s against a median of 448 ms
Page weightlighter than 82% of 4,999 pages tested here160.2 KB against a median of 650.5 KB
Fully loadedslower than 96% of 4,999 pages tested here6.08 s against a median of 1.84 s
Requestssends fewer requests than 92% of 4,999 pages tested here6 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 5.23 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 160.2 KB over 6 request(s), which is lean. Javascript files are 98% 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.
  • The largest element took 2.54 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.
  • Layout stayed still (CLS 0.007), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 738 ms, so taps and scrolling wait while scripts run.

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.

Desktop screenshot of superbet.ro
Desktop 1366 × 768 · 309.6 KB · page is 1141 px tall
Mobile screenshot of superbet.ro
Mobile 390 × 844 · 121.9 KB · page is 2346 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.54 sgood is under 2.5 s
Cumulative layout shift0.007under 0.1 is stable
Total blocking time738 mslong tasks during load
First contentful paint1.28 sfirst content on screen
Browser page weight4.41 MB89 request(s), scripts included
Failed requests4blocked or unreachable
Largest contentful paint2.54 s
Needs improvementgood under 2.5 s, poor over 4 s
Cumulative layout shift0.007
Goodgood under 0.1, poor over 0.25
Total blocking time738 ms
Poorgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 5 requests
157.6 KB 98%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 5227 ms. Of that, 100 ms was the server thinking and 5127 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.

Waterfall

Slowest requests

JAVASCRIPTsuperbet.ro/static/js/fetchConfig/translations
854 ms
JAVASCRIPTsuperbet.ro/static/js/fetchConfig/app
423 ms
JAVASCRIPTsuperbet.ro/static/js/gtm.js
336 ms
JAVASCRIPTsuperbet.ro/static/js/fetchConfig/social
315 ms
JAVASCRIPTsuperbet.ro/static/js/index.d93f0201.js
287 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://superbet.ro/static/js/fetchConfig/translationsjavascript200854 ms96.4 KB
https://superbet.ro/static/js/fetchConfig/appjavascript200423 ms11.3 KB
https://superbet.ro/static/js/gtm.jsjavascript200336 ms1.7 KB
https://superbet.ro/static/js/fetchConfig/socialjavascript200315 ms438 B
https://superbet.ro/static/js/index.d93f0201.jsjavascript200287 ms47.9 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.