Home/Speed tests/algolianet.com

algolianet.com speed test — 20 Oct 2026

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

https://algolianet.com/

20 October 2026 at 14:19 UTC · Free test · report pt_95eb46f0263b
Grade
A
98/100
Performance100/100
Structure94/100

14 audit(s) passed, 2 need work

Share this reportXWhatsAppLinkedInFacebookTelegramRedditEmail
First byte (TTFB)162 msmeasured from this server
Fully loaded162 msfirst byte + slowest asset
Requests1document + assets
Page weight123 Bcompressed transfer
HTML document123 Bgzip
ProtocolHTTP/3cloudflare

Where the first byte went

  • DNS lookup 85 ms 52%
  • TCP connect 6 ms 4%
  • Server wait 71 ms 44%

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 97% of 4,999 pages tested here162 ms against a median of 449 ms
Page weightlighter than 99% of 4,999 pages tested here123 B against a median of 650.5 KB
Fully loadedfaster than 100% of 4,999 pages tested here162 ms against a median of 1.84 s
Requestssends fewer requests than 98% of 4,999 pages tested here1 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 server answered in 162 ms, which is fast: almost all of the wait is the page itself, not the host.
  • The page transfers 123 B over 1 request(s), which is lean.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • The main thread was blocked for 382 ms, so taps and scrolling wait while scripts run.

Fix first: Mobile viewport - Add a viewport meta tag with width=device-width and an initial scale of 1.

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 algolianet.com
Mobile 390 × 844 · 2.7 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 paintnot reportedgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking time382 mslong tasks during load
First contentful paint944 msfirst content on screen
Browser page weight30.42 MB384 request(s), scripts included
Failed requests10blocked or unreachable
Largest contentful paintnot reported
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking time382 ms
Needs improvementgood under 200 ms, poor over 600 ms

Top issues

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.

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.

Run a website speed testHave it fixed