Website review, no card needed

hbr.org logo

hbr.org website review

Visit site (opens in a new tab)Reviewed 13 November 202641 issues · 87 checks

This review found 41 issues worth fixing on hbr.org, 14 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.

  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.2 s2.8 sMay 23Nov 73.8 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20263.0 s
May 30, 20263.0 s
Jun 6, 20263.0 s
Jun 13, 20263.0 s
Jun 20, 20263.0 s
Jun 27, 20263.0 s
Jul 4, 20263.0 s
Jul 11, 20263.0 s
Jul 18, 20262.9 s
Jul 25, 20262.9 s
Aug 1, 20262.9 s
Aug 8, 20263.0 s
Aug 15, 20263.1 s
Aug 22, 20263.1 s
Aug 29, 20263.1 s
Sep 5, 20263.1 s
Sep 12, 20263.2 s
Sep 19, 20263.2 s
Sep 26, 20263.3 s
Oct 3, 20263.3 s
Oct 10, 20263.4 s
Oct 17, 20263.6 s
Oct 24, 20263.9 s
Oct 31, 20264.1 s
Nov 7, 20263.8 s
Real-visitor tap response (INP)75th percentile, phones
153 ms138 msMay 23Nov 7150 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026142 ms
May 30, 2026140 ms
Jun 6, 2026144 ms
Jun 13, 2026144 ms
Jun 20, 2026146 ms
Jun 27, 2026149 ms
Jul 4, 2026151 ms
Jul 11, 2026149 ms
Jul 18, 2026146 ms
Jul 25, 2026144 ms
Aug 1, 2026144 ms
Aug 8, 2026146 ms
Aug 15, 2026147 ms
Aug 22, 2026144 ms
Aug 29, 2026141 ms
Sep 5, 2026140 ms
Sep 12, 2026141 ms
Sep 19, 2026145 ms
Sep 26, 2026148 ms
Oct 3, 2026149 ms
Oct 10, 2026147 ms
Oct 17, 2026149 ms
Oct 24, 2026149 ms
Oct 31, 2026150 ms
Nov 7, 2026150 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 hbr.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hbr.org at 1.0 s1.0 s
  2. hbr.org at 2.1 s2.1 s
  3. hbr.org at 3.1 s3.1 s
  4. hbr.org at 4.2 s4.2 s
  5. hbr.org at 5.2 s5.2 s
  6. hbr.org at 6.3 s6.3 s
  7. hbr.org at 7.3 s7.3 s
  8. hbr.org at 8.3 s8.3 s

Speed

12 to fix17
  • Reduce unused JavaScript

    4.0 s · 1.4 MB

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

  • Use efficient cache lifetimes

    2.8 s · 1.0 MB

    50 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).

  • Mobile performance score: 17

    17/100

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

  • Main-thread work: 7.5 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google/Doubleclick Ads, Adobe Tag Manager and Integral Ad Science and others), adding 3.3 MB and 2.8 s of main-thread time.

  • Google/Doubleclick Ads adds 945 ms

    945 ms

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

  • Adobe Tag Manager adds 520 ms

    520 ms

    Adobe Tag Manager costs a phone 520 ms of main-thread work and 194 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.

  • Integral Ad Science adds 423 ms

    423 ms

    Integral Ad Science costs a phone 423 ms of main-thread work and 231 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 CDN adds 354 ms

    354 ms

    Google CDN costs a phone 354 ms of main-thread work and 743 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 Tag Manager adds 344 ms

    344 ms

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

    300 ms

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

  • 20 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 59 KiB

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

  • Legacy JavaScript

    150 ms · 56 KiB

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

  • Improve image delivery

    109 KiB

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

  • 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: 14 ms

    14 ms

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

Core Web Vitals

10 to fix100
  • 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.

  • Largest Contentful Paint: 14.2 s

    14.2 s

    Your largest element takes 14.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 34.9 s

    34.9 s

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

  • Speed Index: 12.7 s

    12.7 s

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

  • First Contentful Paint: 5.6 s

    5.6 s

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

  • Total Blocking Time: 1.9 s

    1.9 s

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

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

    +32%

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • Cumulative Layout Shift: 0.234

    0.234

    The layout shifts by 0.234 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Tap response (INP) held steady for real visitors

    +6%

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

3 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 155 ms

    155 ms

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

  • Real-user CLS: 0.05

    0.05

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

Images and page weight

1 to fix70
  • Page weight: 5.1 MB in 287 requests

    5.1 MB

    Your homepage downloads 5.1 MB in 287 requests on a phone: scripts 3.7 MB (79), other files 554 KiB (130) and fonts 357 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

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

  • About 1.5 g of CO₂ per visit

    1.46 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

3 to fixGoogle 9596
  • 10 tap targets too small

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

  • 58 links without text

    58 visible links have no text or label, so screen readers cannot say where they go.

  • 1 form field without a label

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

  • Headings skip levels

    Headings skip levels (h1 → h3), 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. (1 element).

2 checks passed
  • Every image has alt text

    All 4 images in the HTML carry an alt attribute.

  • 47 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: 47 passed and 2 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 10085
  • No structured data

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

  • No canonical URL

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

  • No social preview image

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

  • No XML sitemap

    No XML sitemap at https://hbr.org/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 incomplete here.

  • 210 internal links, 19 external

    The homepage links to 210 pages on hbr.org and 19 external pages.

4 checks passed
  • Meta description: 147 characters

    Your meta description is 147 characters: “Find new ideas and classic advice on strategy, innovation and leadership, for global leaders from the world's best busi…”.

  • One H1 headline

    Your main headline reads: “Leading After the Founder”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “Harvard Business Review - Ideas and Advice for Leaders”.

  • 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://hbr.org/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 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, 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, which the crawlers above handle.

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

Other pages

2 to fix93
  • 8 pages share a meta description

    https://hbr.org/subscriptions, https://hbr.org/the-latest, https://hbr.org/magazine, https://hbr.org/reading-lists, https://hbr.org/data-visuals and https://hbr.org/executive and 2 others use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://hbr.org/subscriptions and https://hbr.org/topic/managing-yourself have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://hbr.org/subscriptions has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 106 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 12 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 12 pages that loaded have a <title>.

Best practices

4 to fixGoogle 5474
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5795582&tm=al001&Ver=2&mid=cfdd8e16-468a-4b5a-bb31-abea2c60e4b7&bo=1&sid=550f7b70df2711f1b77189d7aababd2f&vid=550fbd60df2711f1a284bd622d988530&vids=1&msclkid=N&pi=9186.

  • 3 third-party cookies

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).

  • 3 JavaScript errors while loading

    3 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 (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    18 of 20 tappable elements near the top are at least 24 px.

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

    The homepage carries about 614 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: “Subscribe”.

  • 13 calls to action

    The homepage has 13 calls to action, for example “Subscribe”, “Sign Up” and “Read more about Cold Call”.

  • 1 short form

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

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Microsoft Ads and 1 more (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.

  • 53 cookies set on arrival

    53

    Opening the homepage sets 53 cookies, 3 of them by other companies (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.

  • 51 other companies contacted

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

Upkeep, stack and company

Stack

Framework
Next.js
Hosting
AWS

Company

Founded
1922
Headquarters
Boston

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on hbr.org, including 22 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