Website review, no card needed

companiesmarketcap.com logo

companiesmarketcap.com website review

Visit site (opens in a new tab)Reviewed 26 October 202637 issues · 87 checks

This review found 37 issues worth fixing on companiesmarketcap.com, 10 of them high impact, across 87 checks. The most urgent: main-thread work: 10.2 s. 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
1.1 s983 msMay 9Oct 241.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.0 s
May 16, 20261.0 s
May 23, 20261.1 s
May 30, 20261.1 s
Jun 6, 20261.1 s
Jun 13, 20261.1 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 20261.1 s
Aug 1, 20261.1 s
Aug 8, 20261.1 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.0 s
Sep 12, 20261.0 s
Sep 19, 20261.0 s
Sep 26, 20261.0 s
Oct 3, 20261.0 s
Oct 10, 20261.0 s
Oct 17, 20261.0 s
Oct 24, 20261.0 s
Real-visitor tap response (INP)75th percentile, phones
179 ms154 msMay 9Oct 24165 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026157 ms
May 16, 2026157 ms
May 23, 2026162 ms
May 30, 2026164 ms
Jun 6, 2026162 ms
Jun 13, 2026165 ms
Jun 20, 2026165 ms
Jun 27, 2026169 ms
Jul 4, 2026172 ms
Jul 11, 2026174 ms
Jul 18, 2026176 ms
Jul 25, 2026174 ms
Aug 1, 2026171 ms
Aug 8, 2026167 ms
Aug 15, 2026164 ms
Aug 22, 2026165 ms
Aug 29, 2026167 ms
Sep 5, 2026169 ms
Sep 12, 2026170 ms
Sep 19, 2026171 ms
Sep 26, 2026170 ms
Oct 3, 2026171 ms
Oct 10, 2026169 ms
Oct 17, 2026165 ms
Oct 24, 2026165 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 companiesmarketcap.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. companiesmarketcap.com at 0.9 s0.9 s
  2. companiesmarketcap.com at 1.7 s1.7 s
  3. companiesmarketcap.com at 2.6 s2.6 s
  4. companiesmarketcap.com at 3.5 s3.5 s
  5. companiesmarketcap.com at 4.3 s4.3 s
  6. companiesmarketcap.com at 5.2 s5.2 s
  7. companiesmarketcap.com at 6.0 s6.0 s
  8. companiesmarketcap.com at 6.9 s6.9 s

Speed

11 to fix66
  • Main-thread work: 10.2 s

    A phone's processor spends 10.2 s on main-thread work while loading, 4.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 3,329 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (fuseplatform.net, Google/Doubleclick Ads and Rubicon Project and others), adding 1.5 MB and 1.9 s of main-thread time.

  • Mobile performance score: 66

    66/100

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

  • 20 long tasks on the main thread

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

  • Use efficient cache lifetimes

    626 KiB

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

  • fuseplatform.net adds 499 ms

    499 ms

    fuseplatform.net costs a phone 499 ms of main-thread work and 352 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.

  • Google/Doubleclick Ads adds 461 ms

    461 ms

    Google/Doubleclick Ads costs a phone 461 ms of main-thread work and 510 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.

  • Rubicon Project adds 439 ms

    439 ms

    Rubicon Project costs a phone 439 ms of main-thread work and 141 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.

  • Render-blocking requests

    450 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

  • Reduce unused JavaScript

    388 KiB

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

  • Legacy JavaScript

    24 KiB

    Polyfills for old browsers add 24 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.

  • Improve image delivery

    5 KiB

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

1 checks passed
  • Server response: 112 ms

    112 ms

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

Core Web Vitals

5 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: 39.6 s

    39.6 s

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

  • Total Blocking Time: 2.5 s

    2.5 s

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

  • Speed Index: 6.0 s

    6.0 s

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

  • Real-user INP: 212 ms

    212 ms

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

  • Tap response (INP) held steady for real visitors

    +5%

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

7 checks passed
  • 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 CLS: 0.02

    0.02

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 611 ms

    611 ms

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

  • Cumulative Layout Shift: 0.023

    0.023

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

  • First Contentful Paint: 1.0 s

    1.0 s

    The first text or image appears after 1.0 s, inside the 1.8 s “good” threshold.

  • Largest Contentful Paint: 1.1 s

    1.1 s

    Your largest element renders in 1.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Largest Companies by Marketcap”.

Images and page weight

1 to fix85
  • Page weight: 2.3 MB in 1,183 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 1,183 requests on a phone: scripts 1.3 MB (51), other files 502 KiB (517) and images 296 KiB (408). Under 2 MB keeps phones on slow connections fast.

  • About 0.7 g of CO₂ per visit

    0.65 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

8 to fixGoogle 8488
  • 199 text elements with low contrast

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

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (529 elements)

    All page content should be contained by landmarks: 529 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

  • Headings skip levels

    Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.

  • <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 210 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

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

SEO

2 to fixGoogle 9292
  • No structured data

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

  • No XML sitemap

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 256 internal links, 3 external

    The homepage links to 256 pages on companiesmarketcap.com and 3 external pages.

6 checks passed
  • Meta description: 92 characters

    Your meta description is 92 characters: “Ranking the world's top companies by market cap, market value, revenue and many more metrics”.

  • One H1 headline

    Your main headline reads: “Largest Companies by Marketcap”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Companies ranked by Market Cap - CompaniesMarketCap.com”.

  • Canonical URL set

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

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

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://companiesmarketcap.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,318 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 9 pages share a title

    /, https://companiesmarketcap.com/eur, https://companiesmarketcap.com/inr, https://companiesmarketcap.com/gbp, https://companiesmarketcap.com/cad and https://companiesmarketcap.com/aud and 3 others all use the title “Companies ranked by Market Cap - CompaniesMarketCap.com”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 8 pages share a meta description

    https://companiesmarketcap.com/eur, https://companiesmarketcap.com/inr, https://companiesmarketcap.com/gbp, https://companiesmarketcap.com/cad, https://companiesmarketcap.com/aud and https://companiesmarketcap.com/nzd and 2 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 197 found) and read each the way a search engine does.

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

  • 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

3 to fixGoogle 5485
  • 29 third-party cookies

    29 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 18 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Mixed content”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 874 words of copy

    The homepage carries about 874 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Price to Book”.

  • 1 call to action

    The homepage has 1 call to action, for example “Price to Book”.

  • 1 short form

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

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Amazon Ads, Criteo, Google Ads, The Trade Desk and Xandr (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.

  • 14 cookies set on arrival

    14

    Opening the homepage sets 14 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.

  • 65 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2025.

Stack

Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on companiesmarketcap.com, including 16 speed issues, 2 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