www.haberler.com speed test — 20 Oct 2026

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

https://www.haberler.com/

20 October 2026 at 12:44 UTC · Free test · report pt_3eba2b2ab580
Grade
C
70/100
Performance60/100
Structure86/100

13 audit(s) passed, 3 need work

First byte (TTFB)1.88 smeasured from this server
Fully loaded2.88 sfirst byte + slowest asset
Requests26document + assets
Page weight97.2 KBcompressed transfer
HTML document73.4 KBbr
ProtocolHTTP/3cloudflare

Where the first byte went

  • DNS lookup 44 ms 2%
  • TCP connect 13 ms 1%
  • Server wait 1.83 s 97%

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 97% of 4,999 pages tested here1.88 s against a median of 448 ms
Page weightlighter than 87% of 4,999 pages tested here97.2 KB against a median of 650.5 KB
Fully loadedslower than 81% of 4,999 pages tested here2.88 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 1.88 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 97.2 KB over 26 request(s).
  • The HTML itself arrives br-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • The largest element painted at 720 ms, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.005), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 515 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.

Mobile screenshot of www.haberler.com
Mobile 390 × 844 · 140.8 KB · page is 6000 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 paint720 msgood is under 2.5 s
Cumulative layout shift0.005under 0.1 is stable
Total blocking time515 mslong tasks during load
First contentful paint280 msfirst content on screen
Browser page weight5.30 MB357 request(s), scripts included
Failed requests19blocked or unreachable
Largest contentful paint720 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.005
Goodgood under 0.1, poor over 0.25
Total blocking time515 ms
Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests
23.8 KB 24%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 1883 ms. Of that, 1825 ms was the server thinking and 57 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.

Avoid extra redirects

medium impact

1 redirect hop(s) before the page load started, each one a full round trip before the first byte.

Fix: Link to the canonical URL (and make sure http, the apex domain and www all point at it) so no visitor pays a redirect first.

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.

Waterfall

Slowest requests

IMAGESwww.haberler.com/mstatic/assets/img/headericons/campaig…
999 ms
IMAGESwww.haberler.com/mstatic/assets/img/headericons/haberle…
991 ms
IMAGESwww.haberler.com/mstatic/assets/img/headericons/all-clo…
983 ms
IMAGESwww.haberler.com/mstatic/assets/img/headericons/all-red…
982 ms
IMAGESwww.haberler.com/mstatic/assets/img/headericons/mobile-…
982 ms
IMAGESwww.haberler.com/mstatic/assets/img/headericons/mobil-s…
981 ms
IMAGESwww.haberler.com/mstatic/assets/img/headericons/hotel_c…
980 ms
IMAGESwww.haberler.com/mstatic/assets/img/headericons/ads_cli…
978 ms
IMAGESwww.haberler.com/mstatic/assets/img/headericons/bar_cha…
977 ms
IMAGESwww.haberler.com/mstatic/assets/img/headericons/breakin…
972 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://www.haberler.com/mstatic/assets/img/headericons/campaign.svgimages200999 ms951 B
https://www.haberler.com/mstatic/assets/img/headericons/haberler.svgimages200991 ms369 B
https://www.haberler.com/mstatic/assets/img/headericons/all-close.svgimages200983 ms755 B
https://www.haberler.com/mstatic/assets/img/headericons/all-red.svgimages200982 ms498 B
https://www.haberler.com/mstatic/assets/img/headericons/mobile-hamburger.svgimages200982 ms496 B
https://www.haberler.com/mstatic/assets/img/headericons/mobil-search.svgimages200981 ms578 B
https://www.haberler.com/mstatic/assets/img/headericons/hotel_class.svgimages200980 ms921 B
https://www.haberler.com/mstatic/assets/img/headericons/ads_click.svgimages200978 ms1.2 KB
https://www.haberler.com/mstatic/assets/img/headericons/bar_chart_4_bars.svgimages200977 ms771 B
https://www.haberler.com/mstatic/assets/img/headericons/breaking_news.svgimages200972 ms822 B
https://www.haberler.com/mstatic/assets/img/headericons/haberler_white.svgimages200971 ms1.4 KB
https://www.haberler.com/mstatic/assets/img/headericons/boat_railway.svgimages200966 ms1.6 KB
https://www.haberler.com/mstatic/assets/img/headericons/mobile-search-close.svgimages200962 ms717 B
https://www.haberler.com/mstatic/assets/img/headericons/bookmark_heart.svgimages200956 ms763 B
https://www.haberler.com/mstatic/assets/img/headericons/allcategory_new.svgimages200956 ms492 B
https://www.haberler.com/mstatic/assets/img/headericons/crisis_alert.svgimages200954 ms1.8 KB
https://www.haberler.com/mstatic/assets/img/headericons/globe_location_pin.svgimages200953 ms1.5 KB
https://www.haberler.com/mstatic/assets/img/headericons/world-cup.svgimages200952 ms1.2 KB
https://www.haberler.com/mstatic/assets/img/headericons/Kripto.svgimages200949 ms1.0 KB
https://www.haberler.com/mstatic/assets/img/headericons/search_new.svgimages200949 ms576 B
https://www.haberler.com/mstatic/assets/img/headericons/sports_and_outdoors.svgimages200948 ms2.0 KB
https://www.haberler.com/mstatic/assets/img/headericons/globe.svgimages200948 ms843 B
https://www.haberler.com/mstatic/assets/img/headericons/account_balance.svgimages200948 ms821 B
https://www.haberler.com/mstatic/assets/img/headericons/auto_awesome_motion.svgimages200947 ms1017 B
https://www.haberler.com/mstatic/assets/img/headericons/border_color.svgimages200947 ms929 B
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.