www.respawn.com speed test — 20 Oct 2026

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

https://www.respawn.com:443/

20 October 2026 at 14:27 UTC · Free test · report pt_ca25b7db55bc
Grade
A
93/100
Performance95/100
Structure91/100

13 audit(s) passed, 3 need work

First byte (TTFB)400 msmeasured from this server
Fully loaded1.15 sfirst byte + slowest asset
Requests9document + assets
Page weight450.9 KBcompressed transfer
HTML document958 Bgzip
ProtocolHTTP/3AmazonS3
Third-party191.4 KBother hosts

Where the first byte went

  • DNS lookup 193 ms 48%
  • TCP connect 27 ms 7%
  • Server wait 180 ms 45%

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 56% of 4,999 pages tested here400 ms against a median of 449 ms
Page weightlighter than 62% of 4,999 pages tested here450.9 KB against a median of 650.5 KB
Fully loadedfaster than 89% of 4,999 pages tested here1.15 s against a median of 1.84 s
Requestssends fewer requests than 89% of 4,999 pages tested here9 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 400 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 450.9 KB over 9 request(s), which is lean. Javascript files are 77% 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.
  • 42% 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 908 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: 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 www.respawn.com
Mobile 390 × 844 · 91.4 KB · page is 844 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 paint908 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 paint908 msfirst content on screen
Browser page weight15.01 MB41 request(s), scripts included
Largest contentful paint908 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

Javascript 4 requests
348.1 KB 77%
Css 4 requests
101.8 KB 23%

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

Top issues

Render-blocking resources

high impact

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

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.

Third-party weight

low impact

5 third-party host(s) serve 191.4 KB of this page. Each one is another DNS lookup, TLS handshake and point of failure you do not control.

Fix: Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.

Waterfall

Slowest requests

CSSuse.typekit.net/pmw2oae.css
750 ms
JAVASCRIPTconsent.trustarc.com/notice
448 ms
JAVASCRIPTwww.respawn.com/js/app.c89118b2.js
425 ms
CSScdn.jsdelivr.net/npm/@mdi/[email protected]/css/materialdesignic…
387 ms
CSSfonts.googleapis.com/css
364 ms
JAVASCRIPTwww.respawn.com/js/chunk-vendors.9c542594.js
343 ms
JAVASCRIPTwww.googletagmanager.com/gtag/js
340 ms
CSSwww.respawn.com/css/app.51aefd57.css
337 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://use.typekit.net/pmw2oae.css 3rd partycss200750 ms1012 B
https://consent.trustarc.com/notice?domain=ea.com&js=nj&noticeType=bb&c=teconsent&gtm=1&pcookie 3rd partyjavascript200448 ms17.3 KB
https://www.respawn.com:443/js/app.c89118b2.jsjavascript200425 ms78.1 KB
https://cdn.jsdelivr.net/npm/@mdi/[email protected]/css/materialdesignicons.min.css 3rd partycss200387 ms50.5 KB
https://fonts.googleapis.com/css?family=Roboto:100,300,400,500,700,900 3rd partycss200364 ms262 B
https://www.respawn.com:443/js/chunk-vendors.9c542594.jsjavascript200343 ms130.4 KB
https://www.googletagmanager.com/gtag/js?id=UA-UA-920860-10 3rd partyjavascript200340 ms122.4 KB
https://www.respawn.com:443/css/app.51aefd57.csscss200337 ms50.1 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.