ifilo.net speed test — 20 Oct 2026

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

https://ifilo.net/

20 October 2026 at 16:12 UTC · Free test · report pt_048b61607c86
Grade
C
75/100
Performance71/100
Structure80/100

13 audit(s) passed, 3 need work

First byte (TTFB)1.17 smeasured from this server
Fully loaded2.42 sfirst byte + slowest asset
Requests15document + assets
Page weight456.5 KBcompressed transfer
HTML document2.1 KBgzip
ProtocolHTTP/3nginx
Third-party173.7 KBother hosts

Where the first byte went

  • DNS lookup 301 ms 26%
  • TCP connect 266 ms 23%
  • Server wait 599 ms 51%

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 90% of 4,999 pages tested here1.17 s against a median of 448 ms
Page weightlighter than 61% of 4,999 pages tested here456.5 KB against a median of 650.5 KB
Fully loadedslower than 71% of 4,999 pages tested here2.42 s against a median of 1.84 s
Requestssends fewer requests than 83% of 4,999 pages tested here15 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 1.17 s. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
  • The page transfers 456.5 KB over 15 request(s), which is lean. Javascript files are 49% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • 38% 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

Javascript 8 requests
225.0 KB 49%
Css 4 requests
188.8 KB 41%
Images 1 request
40.7 KB 9%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 1165 ms. Of that, 599 ms was the server thinking and 567 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 (3 script(s), 1 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

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

Waterfall

Slowest requests

JAVASCRIPTifilo.net/content/js/notificationHandler.js
1.25 s
CSSifilo.net/content/css/site/HZsFMazAmRMmLanding.css
1.22 s
CSSifilo.net/content/css/site/HZsFMazAmRMm.css
1.16 s
CSSifilo.net/content/dist/css/style.css
1.13 s
IMAGESifilo.net/content/image-site/favicon.ico
1.10 s
JAVASCRIPTifilo.net/content/js/site/HZsFMazAmRMmLanding.js
1.05 s
CSSifilo.net/content/min/41/vyuUjG9Gv.css
1.04 s
JAVASCRIPTifilo.net/content/js/site/HZsFMazAmRMm.js
988 ms
JAVASCRIPTpushstorm.ir/pushstorm-notification.js
981 ms
JAVASCRIPTifilo.net/content/min/41/vyuUjG9Gv.m.js
971 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://ifilo.net/content/js/notificationHandler.jsjavascript2001.25 s1.1 KB
https://ifilo.net/content/css/site/HZsFMazAmRMmLanding.css?v=1.0css2001.22 s317 B
https://ifilo.net/content/css/site/HZsFMazAmRMm.css?v=1.04css2001.16 s0 B
https://ifilo.net/content/dist/css/style.css?v=0619css2001.13 s154.5 KB
https://ifilo.net/content/image-site/favicon.icoimages2001.10 s40.7 KB
https://ifilo.net/content/js/site/HZsFMazAmRMmLanding.js?v=1.0javascript2001.05 s0 B
https://ifilo.net/content/min/41/vyuUjG9Gv.csscss2001.04 s34.0 KB
https://ifilo.net/content/js/site/HZsFMazAmRMm.js?v=1.0javascript200988 ms0 B
https://pushstorm.ir/pushstorm-notification.js?pushstorm_key=COM.PUSHSTORM.AS4484TE&v=8 3rd partyjavascript200981 ms7.7 KB
https://ifilo.net/content/min/41/vyuUjG9Gv.m.jsjavascript200971 ms7.4 KB
https://ifilo.net/content/dist/js/main.js?v=0619javascript200969 ms5.7 KB
https://ifilo.net/content/js/jquery-1.12.4.min.jsjavascript200939 ms37.1 KB
https://accounts.google.com/gsi/client 3rd partyhtml403691 ms0 B
https://www.googletagmanager.com/gtag/js?id=G-CD9KMSC3CB 3rd partyjavascript200240 ms166.1 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.