gboxlab.com speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 13:17 UTC. Grade E (57/100), with the screenshots, the timings and the fixes that matter.

https://gboxlab.com/

20 October 2026 at 13:17 UTC · Free test · report pt_1695191d1d69
Grade
E
57/100
Performance52/100
Structure64/100

10 audit(s) passed, 6 need work

First byte (TTFB)1.24 smeasured from this server
Fully loaded6.28 sfirst byte + slowest asset
Requests24document + assets
Page weight1.13 MBcompressed transfer
HTML document5.1 KBbr
ProtocolHTTP/3cloudflare
Third-party198.6 KBother hosts

Where the first byte went

  • DNS lookup 127 ms 10%
  • TCP connect 40 ms 3%
  • Server wait 1.08 s 87%

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 92% of 4,999 pages tested here1.24 s against a median of 448 ms
Page weightheavier than 66% of 4,999 pages tested here1.13 MB against a median of 650.3 KB
Fully loadedslower than 96% of 4,999 pages tested here6.28 s against a median of 1.84 s
Requestssends fewer requests than 76% of 4,999 pages tested here24 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.24 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 1.13 MB over 24 request(s). Images files are 57% 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.
  • The largest element painted at 148 ms, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.001), so nothing jumps under the reader's cursor.

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 gboxlab.com
Mobile 390 × 844 · 68.5 KB · page is 2324 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 paint148 msgood is under 2.5 s
Cumulative layout shift0.001under 0.1 is stable
Total blocking timenone over 50 mslong tasks during load
First contentful paint148 msfirst content on screen
Browser page weight2.06 MB62 request(s), scripts included
Largest contentful paint148 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.001
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 12 requests
660.6 KB 57%
Javascript 7 requests
456.2 KB 40%
Css 4 requests
32.9 KB 3%

Transfer size, compressed as sent. 24 request(s) in total, 1.13 MB across all of them.

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 1242 ms. Of that, 1075 ms was the server thinking and 167 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.

Image delivery and format

high impact

1 image(s) over 200 KB and 3 large image(s) still served as JPEG or PNG.

Fix: Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.

Render-blocking resources

high impact

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

Total page weight

medium impact

The page transfers 1.13 MB across 24 request(s), with the document itself at 5.1 KB.

Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.

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.

Waterfall

Slowest requests

IMAGESgboxlab.com/img/bg_04.png
5.03 s
IMAGESgboxlab.com/img/bg_02.png
5.03 s
IMAGESgboxlab.com/img/logo_02.png
5.03 s
CSScdn.staticfile.org/twitter-bootstrap/3.3.7/css/bootstrap.…
5.03 s
IMAGESgboxlab.com/img//beta_version_guide.png
5.03 s
IMAGESgboxlab.com/img/tg.png
5.03 s
JAVASCRIPTgboxlab.com/js/element.js
5.03 s
JAVASCRIPTgboxlab.com/js/vue.js
5.03 s
CSSgboxlab.com/css/animate.css
5.03 s
CSSgboxlab.com/css/index.css
5.03 s

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://gboxlab.com/img/bg_04.pngimages2005.03 s182.2 KB
https://gboxlab.com/img/bg_02.pngimages2005.03 s181.3 KB
https://gboxlab.com/img/logo_02.pngimages2005.03 s48.8 KB
https://cdn.staticfile.org/twitter-bootstrap/3.3.7/css/bootstrap.min.css 3rd partycss2005.03 s23.3 KB
https://gboxlab.com/img//beta_version_guide.pngimages2005.03 s2.4 KB
https://gboxlab.com/img/tg.pngimages2005.03 s971 B
https://gboxlab.com/js/element.jsjavascript2005.03 s146.4 KB
https://gboxlab.com/js/vue.jsjavascript2005.03 s103.4 KB
https://gboxlab.com/css/animate.css?v=4.4css2005.03 s6.2 KB
https://gboxlab.com/css/index.css?v=20240723css2005.03 s2.0 KB
https://gboxlab.com/css/navbar.css?v=20240815css2005.03 s1.4 KB
https://gboxlab.com/favicon.icoimages2005.03 s949 B
https://gboxlab.com/img/index_alert_icon.pngimages2005.03 s516 B
https://gboxlab.com/js/body.js?v=4.4javascript2005.03 s69 B
https://cdn.staticfile.org/twitter-bootstrap/3.3.7/js/bootstrap.min.js 3rd partyjavascript05.03 s0 B
https://gboxlab.com/img/about/Instagram.png?v=1.0images2005.02 s20.8 KB
https://gboxlab.com/img/about/facebook.png?v=1.0images2005.02 s14.5 KB
https://cdn.staticfile.org/jquery/1.12.4/jquery.min.js 3rd partyjavascript05.02 s0 B
https://gboxlab.com/img/about/Youtube.png?v=1.0images2001.02 s4.7 KB
https://gboxlab.com/js/jquery-3.6.0.min.jsjavascript2001.02 s31.2 KB
https://gboxlab.com/img/bg_05.pngimages2001.01 s200.1 KB
https://gboxlab.com/img/about/Twitter.png?v=20240819images2001.01 s3.4 KB
https://www.googletagmanager.com/gtag/js?id=G-0WMMW9Y290 3rd partyjavascript200946 ms175.2 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.