chocolateplatform.com speed test — 20 Oct 2026

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

https://chocolateplatform.com/

20 October 2026 at 15:26 UTC · Free test · report pt_2ba1248465d3
Grade
A
91/100
Performance95/100
Structure85/100

12 audit(s) passed, 4 need work

First byte (TTFB)396 msmeasured from this server
Fully loaded901 msfirst byte + slowest asset
Requests5document + assets
Page weight474.4 KBcompressed transfer
HTML document962 Bno compression
ProtocolHTTP/3server not sent
Third-party259 Bother hosts

Where the first byte went

  • DNS lookup 60 ms 15%
  • TCP connect 87 ms 22%
  • Server wait 249 ms 63%

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 57% of 4,999 pages tested here396 ms against a median of 449 ms
Page weightlighter than 60% of 4,999 pages tested here474.4 KB against a median of 650.5 KB
Fully loadedfaster than 94% of 4,999 pages tested here901 ms against a median of 1.84 s
Requestssends fewer requests than 93% of 4,999 pages tested here5 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 396 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 474.4 KB over 5 request(s), which is lean. Javascript files are 91% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • The largest element painted at 1.14 s, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.003), so nothing jumps under the reader's cursor.

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.

Desktop screenshot of chocolateplatform.com
Desktop 1366 × 768 · 616.8 KB · page is 3991 px tall
Mobile screenshot of chocolateplatform.com
Mobile 390 × 844 · 264.5 KB · page is 6000 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 paint1.14 sgood is under 2.5 s
Cumulative layout shift0.003under 0.1 is stable
Total blocking timenone over 50 mslong tasks during load
First contentful paint1.14 sfirst content on screen
Browser page weight174.4 KB6 request(s), scripts included
Largest contentful paint1.14 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.003
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
431.1 KB 91%
Css 2 requests
39.4 KB 8%
Images 1 request
3.0 KB 1%

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

Top issues

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 470.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.

Render-blocking resources

high impact

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

Cache static assets

medium impact

3 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.

JavaScript weight

medium impact

1 JavaScript file(s) over 200 KB: index-DPeMutJH.js (431.1 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

JAVASCRIPTchocolateplatform.com/assets/index-DPeMutJH.js
505 ms
CSSchocolateplatform.com/assets/index-awsfIF9Z.css
452 ms
IMAGESchocolateplatform.com/favicon.png
384 ms
CSSfonts.googleapis.com/css2
269 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://chocolateplatform.com/assets/index-DPeMutJH.jsjavascript200505 ms431.1 KB
https://chocolateplatform.com/assets/index-awsfIF9Z.csscss200452 ms39.1 KB
https://chocolateplatform.com/favicon.pngimages200384 ms3.0 KB
https://fonts.googleapis.com/css2?family=Inter:wght@300;400;500;600;700;800&display=swap 3rd partycss200269 ms259 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.