www.yaplakal.com speed test — 20 Oct 2026

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

https://www.yaplakal.com/

20 October 2026 at 14:40 UTC · Free test · report pt_06f9db5a4ca4
Grade
D
66/100
Performance67/100
Structure65/100

9 audit(s) passed, 7 need work

First byte (TTFB)798 msmeasured from this server
Fully loaded5.95 sfirst byte + slowest asset
Requests26document + assets
Page weight815.4 KBcompressed transfer
HTML document32.5 KBgzip
ProtocolHTTP/3nginx
Third-party742.0 KBother hosts

Where the first byte went

  • DNS lookup 83 ms 10%
  • TCP connect 173 ms 22%
  • Server wait 541 ms 68%

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 76% of 4,999 pages tested here798 ms against a median of 448 ms
Page weightheavier than 57% of 4,999 pages tested here815.4 KB against a median of 650.3 KB
Fully loadedslower than 95% of 4,999 pages tested here5.95 s against a median of 1.84 s
Requestssends more requests than 100% of 4,999 pages tested here26 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 798 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 815.4 KB over 26 request(s). Images files are 96% 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.
  • 91% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.

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.

No screenshot for this report.

The headless browser did not capture this page when the test ran, so only the server measurements are shown.

Page weight by type

What the page is made of

Images 22 requests
782.3 KB 96%
Html 3 requests
486 B 0%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 798 ms. Of that, 541 ms was the server thinking and 256 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

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

Image delivery and format

medium impact

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

Cache static assets

medium impact

10 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 742.0 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

IMAGESs00.yaplakal.com/pics/pics_preview/2/9/9/21339992.jpg
5.16 s
IMAGESs00.yaplakal.com/pics/pics_preview/6/0/1/21339106.jpg
5.16 s
IMAGESs00.yaplakal.com/pics/pics_preview/0/4/0/21340040.jpg
5.16 s
IMAGESs00.yaplakal.com/pics/pics_preview/8/3/1/21340138.jpg
5.15 s
IMAGESs00.yaplakal.com/pics/pics_preview/4/0/2/21339204.jpg
5.15 s
IMAGESs00.yaplakal.com/pics/pics_preview/0/7/1/21340170.jpg
5.15 s
IMAGESs00.yaplakal.com/pics/pics_preview/6/6/8/21339866.jpg
5.15 s
IMAGESs00.yaplakal.com/pics/pics_preview/9/0/9/21339909.jpg
5.15 s
IMAGESs00.yaplakal.com/pics/pics_preview/8/3/7/21339738.jpg
5.15 s
IMAGESs00.yaplakal.com/pics/pics_preview/3/9/9/21339993.jpg
5.15 s

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://s00.yaplakal.com/pics/pics_preview/2/9/9/21339992.jpg 3rd partyimages2005.16 s124.7 KB
https://s00.yaplakal.com/pics/pics_preview/6/0/1/21339106.jpg 3rd partyimages2005.16 s78.3 KB
https://s00.yaplakal.com/pics/pics_preview/0/4/0/21340040.jpg 3rd partyimages05.16 s0 B
https://s00.yaplakal.com/pics/pics_preview/8/3/1/21340138.jpg 3rd partyimages2005.15 s86.6 KB
https://s00.yaplakal.com/pics/pics_preview/4/0/2/21339204.jpg 3rd partyimages05.15 s0 B
https://s00.yaplakal.com/pics/pics_preview/0/7/1/21340170.jpg 3rd partyimages05.15 s0 B
https://s00.yaplakal.com/pics/pics_preview/6/6/8/21339866.jpg 3rd partyimages2005.15 s154.0 KB
https://s00.yaplakal.com/pics/pics_preview/9/0/9/21339909.jpg 3rd partyimages2005.15 s89.6 KB
https://s00.yaplakal.com/pics/pics_preview/8/3/7/21339738.jpg 3rd partyimages2005.15 s70.9 KB
https://s00.yaplakal.com/pics/pics_preview/3/9/9/21339993.jpg 3rd partyimages2005.15 s65.1 KB
https://s00.yaplakal.com/pics/pics_preview/0/4/1/21340140.jpg 3rd partyimages2005.15 s39.4 KB
https://s00.yaplakal.com/pics/pics_preview/4/9/5/21338594.jpg 3rd partyimages2005.15 s31.4 KB
https://www.yandex.ru/cycounter?www.yaplakal.com 3rd partyimages2005.15 s1.5 KB
https://www.yaplakal.com/html/static/video-loader.gifimages2001.54 s12.5 KB
https://www.yaplakal.com/html/static/trans.gifimages2001.53 s49 B
https://www.yaplakal.com/html/static/logo-white.pngimages2001.52 s1.2 KB
https://www.yaplakal.com/html/static/top-logo.pngimages2001.52 s13.5 KB
https://www.yaplakal.com/html/smm/ok.pngimages2001.51 s2.0 KB
https://www.yaplakal.com/html/static/ajax-loader.gifimages2001.51 s404 B
https://www.yaplakal.com/html/static/18only.pngimages2001.51 s4.7 KB
https://yapfiles.ru/files/3624369/dzen1.png 3rd partyhtml3011.51 s162 B
https://yapfiles.ru/files/3624364/max1.png 3rd partyhtml3011.50 s162 B
https://www.yaplakal.com/html/smm/tg1.pngimages2001.50 s2.8 KB
https://yapfiles.ru/files/3624363/x2.png 3rd partyhtml3011.49 s162 B
https://www.yaplakal.com/html/smm/vk.pngimages2001.48 s3.6 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.