like.video speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 13:19 UTC. Grade C (75/100), with the screenshots, the timings and the fixes that matter.

https://like.video/

20 October 2026 at 13:19 UTC · Free test · report pt_6cba7a83d7c4
Grade
C
75/100
Performance76/100
Structure74/100

11 audit(s) passed, 5 need work

First byte (TTFB)994 msmeasured from this server
Fully loaded2.30 sfirst byte + slowest asset
Requests16document + assets
Page weight885.3 KBcompressed transfer
HTML document2.6 KBbr
ProtocolHTTP/3nginx
Third-party880.8 KBother hosts

Where the first byte went

  • DNS lookup 70 ms 7%
  • TCP connect 225 ms 23%
  • Server wait 699 ms 70%

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 byteslower than 85% of 4,999 pages tested here994 ms against a median of 448 ms
Page weightheavier than 59% of 4,999 pages tested here885.3 KB against a median of 650.3 KB
Fully loadedslower than 68% of 4,999 pages tested here2.30 s against a median of 1.84 s
Requestssends fewer requests than 83% of 4,999 pages tested here16 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 took 994 ms. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
  • The page transfers 885.3 KB over 16 request(s). Javascript files are 86% 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.
  • 99% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
  • The largest element took 5.28 s to paint, past the 2.5 s threshold: usually a hero image that is too big or a render-blocking script in front of it.
  • Layout stayed still (CLS 0.001), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 347 ms, so taps and scrolling wait while scripts run.

Fix first: Server response time (TTFB) - Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

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 like.video
Desktop 1366 × 768 · 1,008.8 KB · page is 768 px tall
Mobile screenshot of like.video
Mobile 390 × 844 · 278.2 KB · page is 1087 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 paint5.28 sgood is under 2.5 s
Cumulative layout shift0.001under 0.1 is stable
Total blocking time347 mslong tasks during load
First contentful paint5.28 sfirst content on screen
Browser page weight2.54 MB73 request(s), scripts included
Largest contentful paint5.28 s
Poorgood under 2.5 s, poor over 4 s
Cumulative layout shift0.001
Goodgood under 0.1, poor over 0.25
Total blocking time347 ms
Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 9 requests
762.3 KB 86%
Css 2 requests
111.2 KB 13%
Images 2 requests
5.9 KB 1%
Html 1 request
3.3 KB 0%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 994 ms. Of that, 699 ms was the server thinking and 295 ms was connection setup. A first byte under 400 ms is what a visitor feels as instant.

Fix: Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

Render-blocking resources

high impact

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

Total page weight

medium impact

The page transfers 885.3 KB across 16 request(s), with the document itself at 2.6 KB.

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

Third-party weight

medium impact

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

JavaScript weight

medium impact

1 JavaScript file(s) over 200 KB: chunk-common.2e0a630b.js (390.8 KB)

Fix: Split routes, remove unused dependencies, and prefer a two-file build (one pinned library, one application bundle) over many small ones.

Waterfall

Slowest requests

IMAGESlike.video/favicon2019.ico
1.31 s
OTHERmc.yandex.ru/watch/88184725
1.08 s
IMAGESstatic-web.likeevideo.com/as/likee-static/likee_logo/share_icon_…
1.08 s
JAVASCRIPTstatic-act.like-video.com/live/lk-java-assets/page-homepage-pc/j…
905 ms
JAVASCRIPTstatic-act.like-video.com/live/comm/libs/common-vendor/1.1.0/com…
871 ms
JAVASCRIPTstatic-web.likeevideo.com/as/common-static/libs/hive-myTrack.lik…
853 ms
JAVASCRIPTstatic-act.like-video.com/live/lk-java-assets/page-homepage-pc/s…
811 ms
JAVASCRIPTstatic-act.like-video.com/live/lk-java-assets/page-homepage-pc/s…
804 ms
JAVASCRIPTstatic-act.like-video.com/live/comm/libs/assets-load-monitor/2.5…
801 ms
JAVASCRIPTstatic-act.like-video.com/live/lk-java-assets/page-homepage-pc/s…
797 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://like.video/favicon2019.icoimages2001.31 s2.0 KB
https://mc.yandex.ru/watch/88184725 3rd partyother3021.08 s0 B
https://static-web.likeevideo.com/as/likee-static/likee_logo/share_icon_logo_192.png 3rd partyimages2001.08 s4.0 KB
https://static-act.like-video.com/live/lk-java-assets/page-homepage-pc/js/chunk-vendors.1984546a.js 3rd partyjavascript200905 ms172.3 KB
https://static-act.like-video.com/live/comm/libs/common-vendor/1.1.0/common_vendor.min.js 3rd partyjavascript200871 ms88.3 KB
https://static-web.likeevideo.com/as/common-static/libs/hive-myTrack.likee.ru.js 3rd partyjavascript200853 ms704 B
https://static-act.like-video.com/live/lk-java-assets/page-homepage-pc/static/js/easeljs.min.js 3rd partyjavascript200811 ms52.2 KB
https://static-act.like-video.com/live/lk-java-assets/page-homepage-pc/static/js/tweenjs.min.js 3rd partyjavascript200804 ms11.2 KB
https://static-act.like-video.com/live/comm/libs/assets-load-monitor/2.5.6/assets-load-monitor-init.min.js 3rd partyjavascript200801 ms26.7 KB
https://static-act.like-video.com/live/lk-java-assets/page-homepage-pc/static/js/fingerprint2.min.js 3rd partyjavascript200797 ms12.7 KB
https://static-act.like-video.com/live/lk-java-assets/page-homepage-pc/css/chunk-common.96932f5b.css 3rd partycss200793 ms96.9 KB
https://static-act.like-video.com/live/lk-java-assets/page-homepage-pc/css/index_simple.7262e8b4.css 3rd partycss200793 ms14.3 KB
https://static-act.like-video.com/live/comm/libs/common-config/like/index-2.0.js.html 3rd partyhtml200784 ms3.3 KB
https://static-act.like-video.com/live/lk-java-assets/page-homepage-pc/js/index_simple.1dc0f1c5.js 3rd partyjavascript200746 ms7.4 KB
https://static-act.like-video.com/live/lk-java-assets/page-homepage-pc/js/chunk-common.2e0a630b.js 3rd partyjavascript200721 ms390.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.