myshopline.com speed test — 20 Oct 2026

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

https://myshopline.com/

20 October 2026 at 16:18 UTC · Free test · report pt_8311ab470e51
Grade
B
87/100
Performance94/100
Structure76/100

12 audit(s) passed, 4 need work

First byte (TTFB)325 msmeasured from this server
Fully loaded799 msfirst byte + slowest asset
Requests9document + assets
Page weight1.23 MBcompressed transfer
HTML document1.7 KBgzip
ProtocolHTTP/3APISIX
Third-party1.23 MBother hosts

Where the first byte went

  • DNS lookup 59 ms 18%
  • TCP connect 76 ms 23%
  • Server wait 190 ms 58%

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 69% of 4,999 pages tested here325 ms against a median of 449 ms
Page weightheavier than 69% of 4,999 pages tested here1.23 MB against a median of 650.3 KB
Fully loadedfaster than 95% of 4,999 pages tested here799 ms 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 325 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 1.23 MB over 9 request(s), which is lean. Images files are 100% of it, so resize and recompress the largest images before anything else.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • 100% 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 768 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.

Mobile screenshot of myshopline.com
Mobile 390 × 844 · 96.0 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 paint768 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 paint748 msfirst content on screen
Browser page weight497.6 KB9 request(s), scripts included
Largest contentful paint768 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 5 requests
1.23 MB 100%
Css 2 requests
1.8 KB 0%

Transfer size, compressed as sent. 9 request(s) in total, 1.23 MB 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.

Total page weight

medium impact

The page transfers 1.23 MB across 9 request(s), with the document itself at 1.7 KB.

Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.

Cache static assets

medium impact

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

Third-party weight

medium impact

3 third-party host(s) serve 1.23 MB 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

CSSfonts.googleapis.com/css
474 ms
JAVASCRIPTwww.googletagmanager.com/gtag/js
428 ms
IMAGEScdn.myshopline.com/t/stage/homepage/apple-favicon.png
399 ms
IMAGEScdn.myshopline.com/t/stage/homepage/assets/banner-image-5…
359 ms
IMAGEScdn.myshopline.com/t/stage/homepage/assets/banner-image.a…
346 ms
IMAGEScdn.myshopline.com/t/stage/homepage/favicon.png
339 ms
IMAGEScdn.myshopline.com/t/stage/homepage/logo.png
336 ms
CSScdn.myshopline.com/t/stage/homepage/assets/index.9a39a303…
332 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://fonts.googleapis.com/css?family=Roboto:100,100italic,300,300italic,regular,italic,500,500italic,700,700italic,900,900italic%7CBebas+Neue:regular%7CBebas+Neue:regular%7CRoboto:100,100italic,300,300italic,regular,italic,500,500italic,700,700italic,900,900italic&subset=latin,latin-ext,latin,latin-ext,cyrillic,cyrillic-ext,greek,greek-ext,latin,latin-ext,vietnamese 3rd partycss200474 ms0 B
https://www.googletagmanager.com/gtag/js?id=UA-236862378-1 3rd partyjavascript200428 ms0 B
https://cdn.myshopline.com/t/stage/homepage/apple-favicon.png 3rd partyimages200399 ms12.5 KB
https://cdn.myshopline.com/t/stage/homepage/assets/banner-image-500.e2f7a16d.png 3rd partyimages200359 ms42.1 KB
https://cdn.myshopline.com/t/stage/homepage/assets/banner-image.a49bd27e.png 3rd partyimages200346 ms1.17 MB
https://cdn.myshopline.com/t/stage/homepage/favicon.png 3rd partyimages200339 ms1.4 KB
https://cdn.myshopline.com/t/stage/homepage/logo.png 3rd partyimages200336 ms4.1 KB
https://cdn.myshopline.com/t/stage/homepage/assets/index.9a39a303.css 3rd partycss200332 ms1.8 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.