Website review, no card needed

tradingeconomics.com logo

tradingeconomics.com website review

Visit site (opens in a new tab)Reviewed 11 October 202638 issues · 86 checks

This review found 38 issues worth fixing on tradingeconomics.com, 12 of them high impact, across 86 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.7 s1.1 sApr 18Oct 33.4 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20261.9 s
Apr 25, 20261.9 s
May 2, 20261.9 s
May 9, 20261.8 s
May 16, 20261.7 s
May 23, 20261.6 s
May 30, 20261.4 s
Jun 6, 20261.4 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.4 s
Jul 25, 20261.4 s
Aug 1, 20261.4 s
Aug 8, 20261.7 s
Aug 15, 20262.2 s
Aug 22, 20262.8 s
Aug 29, 20263.3 s
Sep 5, 20263.4 s
Sep 12, 20263.4 s
Sep 19, 20263.4 s
Sep 26, 20263.4 s
Oct 3, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
146 ms127 msApr 18Oct 3140 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026130 ms
Apr 25, 2026129 ms
May 2, 2026130 ms
May 9, 2026131 ms
May 16, 2026132 ms
May 23, 2026135 ms
May 30, 2026137 ms
Jun 6, 2026136 ms
Jun 13, 2026136 ms
Jun 20, 2026138 ms
Jun 27, 2026138 ms
Jul 4, 2026140 ms
Jul 11, 2026142 ms
Jul 18, 2026141 ms
Jul 25, 2026140 ms
Aug 1, 2026139 ms
Aug 8, 2026139 ms
Aug 15, 2026140 ms
Aug 22, 2026142 ms
Aug 29, 2026144 ms
Sep 5, 2026144 ms
Sep 12, 2026142 ms
Sep 19, 2026141 ms
Sep 26, 2026140 ms
Oct 3, 2026140 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of tradingeconomics.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tradingeconomics.com at 4.3 s4.3 s
  2. tradingeconomics.com at 8.7 s8.7 s
  3. tradingeconomics.com at 13.0 s13.0 s
  4. tradingeconomics.com at 17.4 s17.4 s
  5. tradingeconomics.com at 21.7 s21.7 s
  6. tradingeconomics.com at 26.1 s26.1 s
  7. tradingeconomics.com at 30.4 s30.4 s
  8. tradingeconomics.com at 34.8 s34.8 s

Speed

9 to fix61
  • Use efficient cache lifetimes

    1.8 s · 514 KiB

    3 files are served with short cache lifetimes, so returning visitors download them again (514 KiB).

  • Reduce unused JavaScript

    1.6 s · 292 KiB

    About 292 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.

  • Render-blocking requests

    1.1 s

    5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

  • Mobile performance score: 61

    61/100

    Your mobile performance score is 61 (desktop: 95). Pages that score under 90 lose visitors before the first paint.

  • 4 third-party services on the page

    4 third-party services load with your homepage (cloudfront.net, Google Tag Manager and Cloudflare CDN and others), adding 1.2 MB and 443 ms of main-thread time.

  • Improve image delivery

    350 ms · 78 KiB

    1 image could be 78 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

  • Minify JavaScript

    310 ms · 55 KiB

    55 KiB could be saved by minifying JavaScript.

  • cloudfront.net adds 212 ms

    212 ms

    cloudfront.net costs a phone 212 ms of main-thread work and 872 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • 1,702 HTML elements

    The page has 1,702 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Reduce unused CSS

    160 ms · 17 KiB

    About 17 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 160 ms faster on a phone.

  • 6 long tasks on the main thread

    6 long tasks block the main thread while loading, the longest for 103 ms. During a long task the page ignores taps.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Phones get a much slower page than desktops

    Desktop scores 95 but mobile only 61. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 checks passed
  • Main-thread work: 1.4 s

    A phone's processor spends 1.4 s on main-thread work while loading, 595 ms of it running JavaScript. That is comfortably low.

  • Server response: 16 ms

    16 ms

    Your server sent the HTML in 16 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 9.3 s

    9.3 s

    Your largest element takes 9.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “US Consumer Sentiment Deteriorates The University of Michig…”.

  • First Contentful Paint: 3.6 s

    3.6 s

    The first text or image appears after 3.6 s on a phone. Good is under 1.8 s.

  • Time to Interactive: 9.3 s

    9.3 s

    The page becomes fully interactive after 9.3 s. Good is under 3.8 s.

  • Largest content (LCP) got 82% slower for real visitors

    +82%

    Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 1.9 s to 3.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Speed Index: 5.6 s

    5.6 s

    Visually, the page fills in at 5.6 s (Speed Index). Good is under 3.4 s.

  • Tap response (INP) held steady for real visitors

    +8%

    Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 130 ms to 140 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.3 s

    1.3 s

    Real visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 104 ms

    104 ms

    Real visitors wait 104 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.0 s

    1.0 s

    Real visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 501 ms

    501 ms

    Real visitors wait 501 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Total Blocking Time: 177 ms

    177 ms

    Scripts block the page for only 177 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.003

    0.003

    The layout barely moves while loading (CLS 0.003, good is under 0.1).

Images and page weight

100
  • About 0.4 g of CO₂ per visit

    0.37 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.37 g of CO₂e: 44.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Page weight: 1.3 MB in 79 requests

    1.3 MB

    Your homepage downloads 1.3 MB in 79 requests on a phone: scripts 564 KiB (5), images 500 KiB (1) and fonts 119 KiB (1). That is a lean page.

Accessibility

9 to fixGoogle 8888
  • 7 text elements with low contrast

    7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • <svg> elements with an img or image role must have alternative text (1 element)

    <svg> elements with an img or image role must have alternative text: 1 element on the page fails this check, rated serious by axe-core.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Table header text should not be empty (1 element)

    Table header text should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

  • <td> elements in a large <table> do not have table headers.

    <td> elements in a large <table> do not have table headers. (1 element).

2 checks passed
  • Every image has alt text

    All 2 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9281
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 6 links with vague text

    6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 319 internal links, 23 external

    The homepage links to 319 pages on tradingeconomics.com and 23 external pages.

5 checks passed
  • Meta description: 148 characters

    Your meta description is 148 characters: “View more than 20 million economic indicators for 196 countries. Get free indicators, Historical Data, Charts, News and…”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “TRADING ECONOMICS | 20 million INDICATORS FROM 196 COUNTRIES”.

  • Canonical URL set

    The canonical URL is https://tradingeconomics.com/.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://tradingeconomics.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://tradingeconomics.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,690 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix86
  • 2 pages share a title

    https://tradingeconomics.com/crypto and https://tradingeconomics.com/forecast/crypto all use the title “Crypto Currencies - Live Exchange Rate Price Quote Data”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://tradingeconomics.com/crypto and https://tradingeconomics.com/forecast/crypto use the same meta description. A description written for each page earns more clicks.

  • 11 pages without an H1

    https://tradingeconomics.com/calendar, https://tradingeconomics.com/stream, https://tradingeconomics.com/commodities, https://tradingeconomics.com/stocks, https://tradingeconomics.com/shares and https://tradingeconomics.com/currencies and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 194 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9679
  • 24 small tap targets

    24 of 50 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Scrolls sideways on phones

    On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://d2n2sd20z6hutz.cloudfront.net/stylesheet-dark.min.css' from origin 'https://tradin…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 1,286 words of copy

    The homepage carries about 1,286 words of visible text.

3 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Pricing” and “Contact”.

  • 1 short form

    A short form (3 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 cookies (measured from a US location before any click).

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 10 other companies contacted

    Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at tradingeconomics.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Analytics

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on tradingeconomics.com, including 14 speed issues, 4 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25