Website review, no card needed

statista.com logo

statista.com website review

Visit site (opens in a new tab)Reviewed 29 October 202628 issues · 78 checks

This review found 28 issues worth fixing on statista.com, 4 of them high impact, across 78 checks. The most urgent: render-blocking requests. 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
4.3 s1.5 sMay 9Oct 241.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.0 s
May 16, 20263.3 s
May 23, 20262.7 s
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 13, 20262.4 s
Jun 20, 20262.4 s
Jun 27, 20262.4 s
Jul 4, 20262.4 s
Jul 11, 20262.4 s
Jul 18, 20262.3 s
Jul 25, 20262.4 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.3 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.2 s
Sep 19, 20262.1 s
Sep 26, 20262.0 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.9 s
Oct 24, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
220 ms165 msMay 9Oct 24214 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026182 ms
May 16, 2026180 ms
May 23, 2026179 ms
May 30, 2026178 ms
Jun 6, 2026177 ms
Jun 13, 2026177 ms
Jun 20, 2026177 ms
Jun 27, 2026178 ms
Jul 4, 2026178 ms
Jul 11, 2026178 ms
Jul 18, 2026175 ms
Jul 25, 2026171 ms
Aug 1, 2026171 ms
Aug 8, 2026172 ms
Aug 15, 2026174 ms
Aug 22, 2026179 ms
Aug 29, 2026181 ms
Sep 5, 2026185 ms
Sep 12, 2026187 ms
Sep 19, 2026187 ms
Sep 26, 2026188 ms
Oct 3, 2026191 ms
Oct 10, 2026195 ms
Oct 17, 2026206 ms
Oct 24, 2026214 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 statista.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. statista.com at 0.4 s0.4 s
  2. statista.com at 0.8 s0.8 s
  3. statista.com at 1.1 s1.1 s
  4. statista.com at 1.5 s1.5 s
  5. statista.com at 1.9 s1.9 s
  6. statista.com at 2.3 s2.3 s
  7. statista.com at 2.6 s2.6 s
  8. statista.com at 3.0 s3.0 s

Speed

7 to fix80
  • Render-blocking requests

    1.8 s

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

  • Mobile performance score: 80

    80/100

    Your mobile performance score is 80. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    450 ms · 106 KiB

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

  • 6 long tasks on the main thread

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

  • Google Tag Manager adds 289 ms

    289 ms

    Google Tag Manager costs a phone 289 ms of main-thread work and 205 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.

  • 2,716 HTML elements

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

  • Optanon adds 138 ms

    138 ms

    Optanon costs a phone 138 ms of main-thread work and 365 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.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Optanon and statcdn.com and others), adding 861 KiB and 467 ms of main-thread time.

  • Reduce unused JavaScript

    246 KiB

    About 246 KiB of JavaScript is downloaded but never used on this page.

  • Use efficient cache lifetimes

    178 KiB

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

  • Improve image delivery

    96 KiB

    5 images could be 96 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    27 KiB

    Polyfills for old browsers add 27 KiB JavaScript that modern phones do not need.

  • 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.7 s

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

  • Server response: 34 ms

    34 ms

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

Core Web Vitals

8 to fix67
  • Fails Core Web Vitals for real visitors

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

  • Time to Interactive: 8.5 s

    8.5 s

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

  • Real-user INP: 281 ms

    281 ms

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

  • Real-user TTFB: 864 ms

    864 ms

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

  • Speed Index: 5.4 s

    5.4 s

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Largest Contentful Paint: 3.0 s

    3.0 s

    Your largest element takes 3.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Empowering people with data”.

  • Total Blocking Time: 298 ms

    298 ms

    Scripts block taps and scrolling for 298 ms in total while the page loads. Good is under 200 ms.

  • Tap response (INP) got 16% slower for real visitors

    +16%

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

5 checks passed
  • Real-user LCP: 1.7 s

    1.7 s

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

  • 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.7 s

    1.7 s

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

  • Largest content (LCP) got 49% faster for real visitors

    -49%

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

  • Cumulative Layout Shift: 0.072

    0.072

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

Images and page weight

1 to fix90
  • 1 image far larger than shown

    34 KiB

    1 image is downloaded at several times the size a phone draws it, for example b_Non-ConI+clients,+other+industries.webp at 1,720 px wide, shown at 350 px. Resized copies would save about 34 KiB.

  • 1 image below the first screen load straight away

    1 image further down the page (54 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.4 g of CO₂ per visit

    0.39 g

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

2 checks passed
  • Page weight: 1.4 MB in 56 requests

    1.4 MB

    Your homepage downloads 1.4 MB in 56 requests on a phone: scripts 747 KiB (18), images 230 KiB (18) and other files 182 KiB (12). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

1 to fixGoogle 10099
  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate 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).

2 checks passed
  • Every image has alt text

    All 21 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

5 to fixGoogle 9279
  • Title is long (84 characters)

    Your title is 84 characters, so Google will cut it off around 60: “Statista - The Statistics Portal for Market Data, Market Research and Market Studies”.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No XML sitemap

    No XML sitemap at https://www.statista.com/sitemap/, so Google discovers your pages only by following links.

  • 15 links with vague text

    15 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 set, so this is minor.

  • 206 internal links, 22 external

    The homepage links to 206 pages on statista.com and 22 external pages.

4 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “Find statistics, consumer survey results and industry studies from over 22,500 sources on over 60,000 topics on the int…”.

  • One H1 headline

    Your main headline reads: “Empowering people with data”.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

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

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no /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 (2,530 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix98
  • 11 pages share a meta description

    /markets/415/consumer-goods-fmcg, /markets/413/e-commerce, /markets/2535/economy-politics, /markets/408/energy-environment, /markets/412/health-pharma-medtech and /markets/424/internet and 5 others use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

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

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

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

2 to fixGoogle 9687
  • 6 small tap targets

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

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “[Vue warn]: Error in updated hook: "TypeError: Cannot read properties of undefined (reading 'children')" found in ---> …”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 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,934 words of copy

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

4 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Book a demo”, “Register now” and “Buy now”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 3 customer or partner logos, 10 trust badges and “more than 23,000 companies”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 4 cookies set on arrival

    4

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

  • 5 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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 statista.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Tag Manager
Hosting
CloudFront

Hiring

Hiring
25 open roles
Teams
Revenue (9), Data (4), Tech (4), Finance (3)
Job board
ashby

Company

Founded
2007
Headquarters
Hamburg

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on statista.com, including 15 speed issues, 5 SEO issues and 2 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