schema.org speed test — 20 Oct 2026

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

https://schema.org/

20 October 2026 at 14:39 UTC · Free test · report pt_7abc524c3c1c
Grade
A
96/100
Performance98/100
Structure92/100

14 audit(s) passed, 2 need work

First byte (TTFB)267 msmeasured from this server
Fully loaded696 msfirst byte + slowest asset
Requests7document + assets
Page weight48.4 KBcompressed transfer
HTML document3.0 KBgzip
ProtocolHTTP/3Google Frontend
Third-party30.3 KBother hosts

Where the first byte went

  • DNS lookup 92 ms 34%
  • TCP connect 36 ms 13%
  • Server wait 139 ms 52%

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 81% of 4,999 pages tested here267 ms against a median of 449 ms
Page weightlighter than 91% of 4,999 pages tested here48.4 KB against a median of 650.5 KB
Fully loadedfaster than 96% of 4,999 pages tested here696 ms against a median of 1.84 s
Requestssends fewer requests than 91% of 4,999 pages tested here7 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 267 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 48.4 KB over 7 request(s), which is lean. Javascript files are 63% 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.
  • 63% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
  • The largest element painted at 800 ms, inside the 2.5 s Google calls good.
  • Layout shift is 0.241 (good is under 0.1): something without a reserved size is loading late - an image, an ad, or a font swap.
  • The main thread was blocked for 3 ms in total, which is not enough to feel.

Fix first: Render-blocking resources - 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.

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 schema.org
Mobile 390 × 844 · 58.5 KB · page is 1703 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 paint800 msgood is under 2.5 s
Cumulative layout shift0.241under 0.1 is stable
Total blocking time3 mslong tasks during load
First contentful paint800 msfirst content on screen
Browser page weight396.9 KB19 request(s), scripts included
Largest contentful paint800 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.241
Needs improvementgood under 0.1, poor over 0.25
Total blocking time3 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 2 requests
30.7 KB 63%
Images 1 request
10.4 KB 21%
Css 3 requests
4.3 KB 9%

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

Top issues

Render-blocking resources

high impact

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

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

CSSschema.org/docs/prettify.css
429 ms
JAVASCRIPTajax.googleapis.com/ajax/libs/jquery/3.5.1/jquery.min.js
419 ms
JAVASCRIPTschema.org/docs/schemaorg.js
337 ms
CSSschema.org/docs/devnote.css
332 ms
IMAGESschema.org/docs/favicon.ico
297 ms
CSSschema.org/docs/schemaorg.css
297 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://schema.org/docs/prettify.csscss200429 ms523 B
https://ajax.googleapis.com/ajax/libs/jquery/3.5.1/jquery.min.js 3rd partyjavascript200419 ms30.3 KB
https://schema.org/docs/schemaorg.jsjavascript200337 ms367 B
https://schema.org/docs/devnote.csscss200332 ms98 B
https://schema.org/docs/favicon.icoimages200297 ms10.4 KB
https://schema.org/docs/schemaorg.csscss200297 ms3.7 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.