odysee.com speed test — 20 Oct 2026

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

https://odysee.com/

20 October 2026 at 16:24 UTC · Free test · report pt_37ad2397633f
Grade
A
96/100
Performance99/100
Structure92/100

14 audit(s) passed, 2 need work

First byte (TTFB)222 msmeasured from this server
Fully loaded745 msfirst byte + slowest asset
Requests13document + assets
Page weight555.2 KBcompressed transfer
HTML document3.0 KBbr
ProtocolHTTP/3cloudflare
Third-party161.7 KBother hosts

Where the first byte went

  • DNS lookup 65 ms 29%
  • TCP connect 22 ms 10%
  • Server wait 135 ms 61%

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 89% of 4,999 pages tested here222 ms against a median of 449 ms
Page weightlighter than 55% of 4,999 pages tested here555.2 KB against a median of 650.5 KB
Fully loadedfaster than 95% of 4,999 pages tested here745 ms against a median of 1.84 s
Requestssends fewer requests than 85% of 4,999 pages tested here13 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 222 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 555.2 KB over 13 request(s), which is lean. Javascript files are 43% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
  • The HTML itself arrives br-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • 29% 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 1.99 s, inside the 2.5 s Google calls good.
  • The main thread was blocked for 39 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 odysee.com
Mobile 390 × 844 · 357.3 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.99 sgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking time39 mslong tasks during load
First contentful paint1.64 sfirst content on screen
Browser page weight7.48 MB333 request(s), scripts included
Failed requests1blocked or unreachable
Largest contentful paint1.99 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking time39 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 2 requests
237.5 KB 43%
Fonts 6 requests
176.9 KB 32%
Css 3 requests
128.7 KB 23%
Images 1 request
9.1 KB 2%

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

Top issues

Render-blocking resources

high impact

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

IMAGESodysee.com/public/favicon_128.png
523 ms
JAVASCRIPTodysee.com/public/assets/index-AQKzyGV3.js
515 ms
FONTSodysee.com/public/font/v1/400i.woff
514 ms
CSSodysee.com/public/assets/index-CYLAGbJ8.css
513 ms
JAVASCRIPTcdn.jsdelivr.net/npm/@farcaster/miniapp-sdk/dist/index.…
511 ms
CSSodysee.com/public/assets/credit-amount-CF01a0_Y.css
509 ms
FONTSodysee.com/public/font/v1/300i.woff
506 ms
CSSodysee.com/public/assets/counter-CKq6Kc0z.css
505 ms
FONTSodysee.com/public/font/v1/700i.woff
501 ms
FONTSodysee.com/public/font/v1/700.woff
498 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://odysee.com/public/favicon_128.pngimages200523 ms9.1 KB
https://odysee.com/public/assets/index-AQKzyGV3.jsjavascript200515 ms75.8 KB
https://odysee.com/public/font/v1/400i.wofffonts200514 ms29.8 KB
https://odysee.com/public/assets/index-CYLAGbJ8.csscss200513 ms128.3 KB
https://cdn.jsdelivr.net/npm/@farcaster/miniapp-sdk/dist/index.min.js 3rd partyjavascript200511 ms161.7 KB
https://odysee.com/public/assets/credit-amount-CF01a0_Y.csscss200509 ms182 B
https://odysee.com/public/font/v1/300i.wofffonts200506 ms31.3 KB
https://odysee.com/public/assets/counter-CKq6Kc0z.csscss200505 ms240 B
https://odysee.com/public/font/v1/700i.wofffonts200501 ms31.8 KB
https://odysee.com/public/font/v1/700.wofffonts200498 ms29.3 KB
https://odysee.com/public/font/v1/400.wofffonts200495 ms26.8 KB
https://odysee.com/public/font/v1/300.wofffonts200490 ms28.0 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.