cnnamador.com speed test — 20 Oct 2026

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

https://cnnamador.com/

20 October 2026 at 15:57 UTC · Free test · report pt_cdcf031436ea
Grade
C
79/100
Performance73/100
Structure88/100

14 audit(s) passed, 2 need work

First byte (TTFB)1.05 smeasured from this server
Fully loaded2.68 sfirst byte + slowest asset
Requests26document + assets
Page weight651.9 KBcompressed transfer
HTML document35.2 KBbr
ProtocolHTTP/3cloudflare
Third-party176.2 KBother hosts

Where the first byte went

  • DNS lookup 86 ms 8%
  • TCP connect 23 ms 2%
  • Server wait 937 ms 89%

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 87% of 4,999 pages tested here1.05 s against a median of 448 ms
Page weightlighter than 50% of 4,999 pages tested here651.9 KB against a median of 650.3 KB
Fully loadedslower than 77% of 4,999 pages tested here2.68 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.05 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 651.9 KB over 26 request(s). Javascript files are 46% 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.
  • 27% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
  • The largest element painted at 1.61 s, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.040), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 59 ms in total, which is not enough to feel.

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 cnnamador.com
Desktop 1366 × 768 · 859.7 KB · page is 4583 px tall
Mobile screenshot of cnnamador.com
Mobile 390 × 844 · 179.5 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 paint1.61 sgood is under 2.5 s
Cumulative layout shift0.040under 0.1 is stable
Total blocking time59 mslong tasks during load
First contentful paint1.30 sfirst content on screen
Browser page weight1.22 MB66 request(s), scripts included
Largest contentful paint1.61 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.040
Goodgood under 0.1, poor over 0.25
Total blocking time59 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 5 requests
296.8 KB 46%
Images 18 requests
280.7 KB 43%
Css 1 request
38.9 KB 6%
Other 1 request
176 B 0%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 1047 ms. Of that, 937 ms was the server thinking and 109 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.

Cache static assets

medium impact

1 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

OTHERcnnamador.com/static/favicons/bkp/manifest.json
1.63 s
IMAGEScnnamador.com/static/favi/apple-touch-icon-76x76.png
967 ms
IMAGEScnnamador.com/static/favi/apple-touch-icon-72x72.png
966 ms
IMAGEScnnamador.com/static/favi/web-app-manifest-192x192.png
962 ms
IMAGEScnnamador.com/static/favi/apple-touch-icon-60x60.png
952 ms
IMAGEScnnamador.com/static/favi/apple-touch-icon-57x57.png
950 ms
IMAGEScnnamador.com/static/favi/favicon-96x96.png
945 ms
IMAGEScnnamador.com/static/favi/favicon-16x16.png
945 ms
IMAGEScnnamador.com/static/favi/favicon-32x32.png
937 ms
JAVASCRIPTwww.googletagmanager.com/gtag/js
933 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://cnnamador.com/static/favicons/bkp/manifest.jsonother2001.63 s176 B
https://cnnamador.com/static/favi/apple-touch-icon-76x76.pngimages200967 ms6.3 KB
https://cnnamador.com/static/favi/apple-touch-icon-72x72.pngimages200966 ms5.7 KB
https://cnnamador.com/static/favi/web-app-manifest-192x192.pngimages200962 ms36.3 KB
https://cnnamador.com/static/favi/apple-touch-icon-60x60.pngimages200952 ms4.3 KB
https://cnnamador.com/static/favi/apple-touch-icon-57x57.pngimages200950 ms4.1 KB
https://cnnamador.com/static/favi/favicon-96x96.pngimages200945 ms12.9 KB
https://cnnamador.com/static/favi/favicon-16x16.pngimages200945 ms869 B
https://cnnamador.com/static/favi/favicon-32x32.pngimages200937 ms1.7 KB
https://www.googletagmanager.com/gtag/js?id=G-X1WTZBCVSM 3rd partyjavascript200933 ms176.2 KB
https://cnnamador.com/static/js/main.min.js?v=fhgfuhd6gjavascript200932 ms84.4 KB
https://cnnamador.com/static/favicons/favicon-16x16.pngimages200932 ms869 B
https://cnnamador.com/static/css/main.css?v=ghdgetdgdgh564hfcss200931 ms38.9 KB
https://cnnamador.com/static/favi/apple-touch-icon-114x114.pngimages200929 ms11.8 KB
https://cnnamador.com/static/favi/favicon.icoimages200927 ms5.7 KB
https://cnnamador.com/static/images/assets/logo/logo-robot.pngimages200925 ms7.0 KB
https://cnnamador.com/static/favi/favicon.svgimages200924 ms110.9 KB
https://cnnamador.com/static/js/jquery.min.js?v=hdgdgffjavascript200923 ms29.2 KB
https://cnnamador.com/static/favi/apple-touch-icon.pngimages200918 ms33.1 KB
https://cnnamador.com/static/favi/apple-touch-icon-144x144.pngimages200912 ms17.0 KB
https://cnnamador.com/static/js/jquery.easy-autocomplete.min.js?v=225xxxjghdyrjavascript200911 ms5.7 KB
https://cnnamador.com/static/favi/apple-touch-icon-120x120.pngimages200910 ms12.8 KB
https://cnnamador.com/static/js/custom.js?v=55255xx23hfgfjavascript200907 ms1.3 KB
https://cnnamador.com/static/favi/apple-touch-icon-96x96.pngimages200904 ms8.9 KB
https://cnnamador.com/img/livescnn.svgimages200903 ms443 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.