stretchoid.com speed test — 20 Oct 2026

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

https://stretchoid.com/

20 October 2026 at 14:42 UTC · Free test · report pt_cd7949b9b9b1
Grade
B
81/100
Performance84/100
Structure77/100

11 audit(s) passed, 5 need work

First byte (TTFB)228 msmeasured from this server
Fully loaded5.34 sfirst byte + slowest asset
Requests5document + assets
Page weight234.8 KBcompressed transfer
HTML document3.6 KBno compression
ProtocolHTTP/2nginx/1.28.3
Third-party33.2 KBother hosts

Where the first byte went

  • DNS lookup 51 ms 22%
  • TCP connect 40 ms 18%
  • Server wait 138 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 88% of 4,999 pages tested here228 ms against a median of 449 ms
Page weightlighter than 77% of 4,999 pages tested here234.8 KB against a median of 650.5 KB
Fully loadedslower than 91% of 4,999 pages tested here5.34 s 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 228 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 234.8 KB over 5 request(s), which is lean. Images files are 84% of it, so resize and recompress the largest images before anything else.
  • It runs over HTTP/2, so the assets share a connection instead of opening one each.
  • The largest element painted at 568 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: Image delivery and format - 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.

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 stretchoid.com
Desktop 1366 × 768 · 55.5 KB · page is 970 px tall
Mobile screenshot of stretchoid.com
Mobile 390 × 844 · 17.9 KB · page is 2159 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 paint568 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 paint568 msfirst content on screen
Browser page weight258.9 KB6 request(s), scripts included
Largest contentful paint568 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 1 request
196.5 KB 84%
Javascript 1 request
33.2 KB 14%
Css 1 request
1.6 KB 1%

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

Top issues

Image delivery and format

high impact

1 image(s) over 200 KB and 1 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

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

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

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.

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

IMAGESstretchoid.com/logo.png
5.12 s
CSSstretchoid.com/index.css
5.12 s
OTHERfonts.googleapis.com/css2
5.12 s
JAVASCRIPTajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js
228 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://stretchoid.com/logo.pngimages2005.12 s196.5 KB
https://stretchoid.com/index.csscss2005.12 s1.6 KB
https://fonts.googleapis.com/css2?family=Raleway&display=swap 3rd partyother05.12 s0 B
https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js 3rd partyjavascript200228 ms33.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.