Website review, no card needed

Forbes logo

forbes.com website review

Visit site (opens in a new tab)Reviewed 12 October 202641 issues · 87 checks

This review found 41 issues worth fixing on forbes.com, 19 of them high impact, across 87 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

Read the full growth playbook for Forbes

  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
2.0 s1.4 sApr 18Oct 31.8 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20261.5 s
Apr 25, 20261.5 s
May 2, 20261.5 s
May 9, 20261.6 s
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.8 s
Jun 20, 20261.8 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
199 ms163 msApr 18Oct 3193 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026167 ms
Apr 25, 2026170 ms
May 2, 2026172 ms
May 9, 2026175 ms
May 16, 2026179 ms
May 23, 2026179 ms
May 30, 2026181 ms
Jun 6, 2026184 ms
Jun 13, 2026186 ms
Jun 20, 2026188 ms
Jun 27, 2026192 ms
Jul 4, 2026195 ms
Jul 11, 2026193 ms
Jul 18, 2026192 ms
Jul 25, 2026188 ms
Aug 1, 2026185 ms
Aug 8, 2026186 ms
Aug 15, 2026187 ms
Aug 22, 2026186 ms
Aug 29, 2026186 ms
Sep 5, 2026186 ms
Sep 12, 2026187 ms
Sep 19, 2026190 ms
Sep 26, 2026189 ms
Oct 3, 2026193 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 forbes.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. forbes.com at 1.0 s1.0 s
  2. forbes.com at 1.9 s1.9 s
  3. forbes.com at 2.9 s2.9 s
  4. forbes.com at 3.8 s3.8 s
  5. forbes.com at 4.8 s4.8 s
  6. forbes.com at 5.8 s5.8 s
  7. forbes.com at 6.7 s6.7 s
  8. forbes.com at 7.7 s7.7 s

Speed

10 to fix37
  • Reduce unused JavaScript

    5.3 s · 1.9 MB

    About 1.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.3 s faster on a phone.

  • Google CDN adds 1.6 s

    1.6 s

    Google CDN costs a phone 1.6 s of main-thread work and 2.6 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 37

    37/100

    Your mobile performance score is 37 (desktop: 70). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 7.4 s

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

  • 5,309 HTML elements

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google CDN, forbesimg.com and Other Google APIs/SDKs and others), adding 4.2 MB and 2.6 s of main-thread time.

  • Improve image delivery

    1.0 MB

    6 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • forbesimg.com adds 747 ms

    747 ms

    forbesimg.com costs a phone 747 ms of main-thread work and 874 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.

  • 20 long tasks on the main thread

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

  • Other Google APIs/SDKs adds 158 ms

    158 ms

    Other Google APIs/SDKs costs a phone 158 ms of main-thread work and 584 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.

  • Use efficient cache lifetimes

    200 ms · 117 KiB

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

  • Legacy JavaScript

    150 ms · 31 KiB

    Polyfills for old browsers add 31 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Render-blocking requests

    150 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

  • Phones get a much slower page than desktops

    Desktop scores 70 but mobile only 37. 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.

1 checks passed
  • Server response: 17 ms

    17 ms

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

Core Web Vitals

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

  • First Contentful Paint: 11.7 s

    11.7 s

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

  • Largest Contentful Paint: 23.2 s

    23.2 s

    Your largest element takes 23.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “America’s Top Architects: A California House By Aidlin Darl…”.

  • Time to Interactive: 29.3 s

    29.3 s

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

  • Speed Index: 11.7 s

    11.7 s

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

  • Total Blocking Time: 786 ms

    786 ms

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

  • Real-user INP: 234 ms

    234 ms

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

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

    +23%

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

  • Real-user TTFB: 897 ms

    897 ms

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

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

    +13%

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

4 checks passed
  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix18
  • Page weight: 7.4 MB in 117 requests

    7.4 MB

    Your homepage downloads 7.4 MB in 117 requests on a phone: scripts 2.9 MB (38), other files 2.3 MB (20) and images 1.3 MB (33). Under 2 MB keeps phones on slow connections fast.

  • 21 images far larger than shown

    2.0 MB

    21 images are downloaded at several times the size a phone draws them, for example forbes_daily.png at 5,490 px wide, shown at 311 px. Resized copies would save about 2.0 MB.

  • 1 image over 500 KB

    forbes_daily.png weighs 987 KiB. On a phone connection a single image that size takes seconds.

  • 21 images in older formats

    21 images (2.8 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 21 images below the first screen load straight away

    21 images further down the page (2.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.1 g of CO₂ per visit

    2.10 g

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

Accessibility

6 to fixGoogle 8991
  • Images must have alternative text (1 element)

    Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

  • 6 tap targets too small

    6 tap targets are too small or too close together to hit reliably with a finger.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

    All page content should be contained by landmarks: 208 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.

  • 19 form fields without a label

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

  • Headings skip levels

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

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

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

1 checks passed
  • 43 automated accessibility rules passed

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

SEO

3 to fixGoogle 9285
  • Title is short (6 characters)

    Your title is only 6 characters: “Forbes”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • One H1 headline

    Your <h1> is empty.

  • 808 internal links, 89 external

    The homepage links to 808 pages on forbes.com and 89 external pages.

5 checks passed
  • Meta description: 123 characters

    Your meta description is 123 characters: “Forbes is a global media company, focusing on business, investing, technology, entrepreneurship, leadership, and lifest…”.

  • Canonical URL set

    The canonical URL is https://www.forbes.com/.

  • Structured data in place

    Structured data found: Organization.

  • 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://www.forbes.com/news_sitemap.xml.

AI search readiness

1 to fix65
  • robots.txt blocks 1 AI answer engine crawler

    1 of 6

    Your robots.txt shuts out Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

  • No llms.txt

    There is no https://www.forbes.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.

  • Opted out of AI training for 4 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

2 checks passed
  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

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

Other pages

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    5 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 5 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 5 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 22 small tap targets

    22 of 61 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 “Uncaught TypeError: Cannot read properties of undefined (reading 'register')”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix67
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • About 2,533 words of copy

    The homepage carries about 2,533 words of visible text.

4 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Sign Up For Newsletters”, “How to Start a Business” and “Contact Us”.

  • 19 short forms

    19 short forms (1 field at most) are right on the homepage.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 6 email links.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 12 trackers load before any consent

    12

    Before a visitor clicks anything, the page loads Amazon Ads, Comscore, Criteo, Google Ads and Google Analytics and 7 mores (measured from a US location before any click). A consent tool (Ketch) is installed; check it blocks these until visitors agree where the law requires it.

  • 41 cookies set on arrival

    41

    Opening the homepage sets 41 cookies, 1 of them by other companies (measured from a US location before any click).

  • 87 other companies contacted

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

1 checks passed
  • Consent tool: Ketch

    A consent management tool (Ketch) 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 forbes.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on forbes.com, including 19 speed issues, 3 SEO issues and 5 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