tradingeconomics.com speed test — 20 Oct 2026

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

https://tradingeconomics.com/

20 October 2026 at 13:32 UTC · Free test · report pt_87e4877af813
Grade
A
90/100
Performance97/100
Structure79/100

11 audit(s) passed, 5 need work

First byte (TTFB)306 msmeasured from this server
Fully loaded1.08 sfirst byte + slowest asset
Requests14document + assets
Page weight595.1 KBcompressed transfer
HTML document51.4 KBbr
ProtocolHTTP/3server not sent
Third-party541.6 KBother hosts

Where the first byte went

  • DNS lookup 53 ms 17%
  • TCP connect 46 ms 15%
  • Server wait 207 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 bytefaster than 73% of 4,999 pages tested here306 ms against a median of 449 ms
Page weightlighter than 53% of 4,999 pages tested here595.1 KB against a median of 650.5 KB
Fully loadedfaster than 91% of 4,999 pages tested here1.08 s against a median of 1.84 s
Requestssends fewer requests than 84% of 4,999 pages tested here14 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 arrived in 306 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 595.1 KB over 14 request(s), which is lean. Javascript files are 52% 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.
  • 91% 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 620 ms, inside the 2.5 s Google calls good.
  • The main thread was blocked for 24 ms in total, which is not enough to feel.

Fix first: Render-blocking resources - 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.

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 tradingeconomics.com
Mobile 390 × 844 · 226.6 KB · page is 4269 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 paint620 msgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking time24 mslong tasks during load
First contentful paint360 msfirst content on screen
Browser page weight720.6 KB15 request(s), scripts included
Largest contentful paint620 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking time24 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 4 requests
308.8 KB 52%
Images 4 requests
189.9 KB 32%
Css 4 requests
42.8 KB 7%
Html 1 request
2.1 KB 0%

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

Top issues

Render-blocking resources

high impact

5 render-blocking resource(s) in the document head (0 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 1 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

6 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

6 third-party host(s) serve 541.6 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.

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

HTMLtradingeconomics.com/cdn/ie/img/roundload.gif
772 ms
IMAGESd1koue9segiqoj.cloudfront.net/2023/California.jpg
764 ms
JAVASCRIPTwww.googletagmanager.com/gtag/js
643 ms
JAVASCRIPTcdnjs.cloudflare.com/ajax/libs/bootstrap/5.3.1/js/bootstrap…
643 ms
CSScdnjs.cloudflare.com/ajax/libs/bootstrap/5.2.3/css/bootstra…
643 ms
CSScdnjs.cloudflare.com/ajax/libs/bootstrap-icons/1.10.2/font/…
642 ms
IMAGESd3e5kp2e91w0k0.cloudfront.net/favicon.svg
600 ms
JAVASCRIPTcdnjs.cloudflare.com/ajax/libs/jquery/3.6.4/jquery.min.js
599 ms
CSSd2n2sd20z6hutz.cloudfront.net/stylesheet.min.css
599 ms
CSSd2n2sd20z6hutz.cloudfront.net/stylesheet-dark.min.css
599 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://tradingeconomics.com/cdn/ie/img/roundload.gifhtml200772 ms2.1 KB
https://d1koue9segiqoj.cloudfront.net/2023/California.jpg 3rd partyimages200764 ms172.5 KB
https://www.googletagmanager.com/gtag/js?id=G-SZ14JCTXWQ 3rd partyjavascript200643 ms160.7 KB
https://cdnjs.cloudflare.com/ajax/libs/bootstrap/5.3.1/js/bootstrap.bundle.min.js 3rd partyjavascript200643 ms20.7 KB
https://cdnjs.cloudflare.com/ajax/libs/bootstrap/5.2.3/css/bootstrap.min.css 3rd partycss200643 ms19.8 KB
https://cdnjs.cloudflare.com/ajax/libs/bootstrap-icons/1.10.2/font/bootstrap-icons.min.css 3rd partycss200642 ms9.6 KB
https://d3e5kp2e91w0k0.cloudfront.net/favicon.svg 3rd partyimages200600 ms941 B
https://cdnjs.cloudflare.com/ajax/libs/jquery/3.6.4/jquery.min.js 3rd partyjavascript200599 ms27.4 KB
https://d2n2sd20z6hutz.cloudfront.net/stylesheet.min.css 3rd partycss200599 ms10.6 KB
https://d2n2sd20z6hutz.cloudfront.net/stylesheet-dark.min.css 3rd partycss200599 ms2.8 KB
https://d3e5kp2e91w0k0.cloudfront.net/images/google-play.png 3rd partyimages200557 ms4.4 KB
https://d2bkl1xeetjryo.cloudfront.net/te-mini-widget.js?v=20250514 3rd partyjavascript200546 ms99.9 KB
https://d3e5kp2e91w0k0.cloudfront.net/images/appstore-lrg.svg 3rd partyimages200546 ms12.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.