Website review, no card needed

billboard.com logo

billboard.com website review

Visit site (opens in a new tab)Reviewed 12 October 202627 issues · 64 checks

This review found 27 issues worth fixing on billboard.com, 11 of them high impact, across 64 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
2.3 s1.9 sApr 18Oct 32.0 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20262.1 s
Apr 25, 20262.1 s
May 2, 20262.1 s
May 9, 20262.1 s
May 16, 20262.1 s
May 23, 20262.2 s
May 30, 20262.2 s
Jun 6, 20262.3 s
Jun 13, 20262.3 s
Jun 20, 20262.3 s
Jun 27, 20262.3 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.3 s
Aug 1, 20262.2 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.2 s
Aug 29, 20262.2 s
Sep 5, 20262.2 s
Sep 12, 20262.1 s
Sep 19, 20262.0 s
Sep 26, 20262.0 s
Oct 3, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
662 ms169 msApr 18Oct 3226 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026284 ms
Apr 25, 2026273 ms
May 2, 2026261 ms
May 9, 2026253 ms
May 16, 2026280 ms
May 23, 2026422 ms
May 30, 2026428 ms
Jun 6, 2026513 ms
Jun 13, 2026605 ms
Jun 20, 2026515 ms
Jun 27, 2026516 ms
Jul 4, 2026411 ms
Jul 11, 2026302 ms
Jul 18, 2026296 ms
Jul 25, 2026305 ms
Aug 1, 2026313 ms
Aug 8, 2026320 ms
Aug 15, 2026314 ms
Aug 22, 2026321 ms
Aug 29, 2026309 ms
Sep 5, 2026300 ms
Sep 12, 2026273 ms
Sep 19, 2026242 ms
Sep 26, 2026234 ms
Oct 3, 2026226 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

Speed

Not measured in this review.

Core Web Vitals

3 to fix67
  • Fails Core Web Vitals for real visitors

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

  • Real-user INP: 229 ms

    229 ms

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

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

4 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user CLS: 0.06

    0.06

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

  • Real-user TTFB: 702 ms

    702 ms

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

  • Tap response (INP) got 17% faster for real visitors

    -17%

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

Images and page weight

4 to fix25
  • Page weight: 5.4 MB

    5.4 MB

    Your homepage downloads 5.4 MB on a phone, 1.1 MB of it images (21%). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    lazyload-fallback.gif weighs 1,021 KiB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    995 KiB

    1 image is downloaded at several times the size a phone draws it, for example lazyload-fallback.gif at 1,250 px wide, shown at 67 px. Resized copies would save about 995 KiB.

  • 1 image in older formats

    1 image (1,021 KiB) is 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.

  • About 1.5 g of CO₂ per visit

    1.52 g

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

1 checks passed
  • Images load when needed

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

Accessibility

9 to fix88
  • Interactive controls must not be nested (8 elements)

    Interactive controls must not be nested: 8 elements on the page fail this check, rated serious by axe-core.

  • Hidden but focusable

    3 elements hidden from screen readers can still receive keyboard focus.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

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

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

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

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

  • 9 form fields without a label

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

  • 2 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 93 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

2 to fix85
  • No H1 headline

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

  • Meta description is short (42 characters)

    Your meta description is only 42 characters: “Music Charts, News, Photos &amp;amp; Video”. 70 to 160 characters is enough to sell the click.

  • 416 internal links, 90 external

    The homepage links to 416 pages on billboard.com and 90 external pages.

6 checks passed
  • Title: 46 characters

    Your title is a healthy 46 characters: “Billboard – Music Charts, News, Photos & Video”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and WebPage.

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

  • XML sitemap found

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

AI search readiness

2 to fix53
  • robots.txt blocks 3 AI answer engine crawlers

    3 of 6

    Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User) and 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.

  • 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 https://www.billboard.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 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.

1 checks passed
  • Text is in the HTML

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

Other pages

2 to fix90
  • 9 pages without a meta description

    https://www.billboard.com/charts, https://www.billboard.com/c/music, https://www.billboard.com/h/awards-news, https://www.billboard.com/pro, https://www.billboard.com/c/music/chart-beat and https://www.billboard.com/p/shop-billboard and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 11 pages without an H1

    https://www.billboard.com/charts, https://www.billboard.com/h/awards-news, https://www.billboard.com/pro, https://www.billboard.com/charts/hot-100, https://www.billboard.com/p/shop-billboard and https://www.billboard.com/p/mental-health-and-music and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages with very little text

    https://www.billboard.com/pro, https://www.billboard.com/charts/hot-100, https://www.billboard.com/c/espanol, https://www.billboard.com/music/chart-beat/taylor-swift-showgirl-14th-week-number-one-billboard-200-1236358728, https://www.billboard.com/music/chart-beat/beatles-drake-taylor-swift-top-ten-billboard-200-first-time-1236358742 and https://www.billboard.com/music/latin/rosalia-snl-reliquia-magnolias-performances-1236358663 have 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 166 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.

  • 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 15 pages that loaded have a <title>.

Best practices

2 to fix87
  • 8 small tap targets

    8 of 32 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 (in promise) NotSupportedError: Failed to execute 'browsingTopics' on 'Document': document.browsingTopics() is…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

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

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

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

3 checks passed
  • 10 calls to action

    The homepage has 10 calls to action, for example “Shop”, “Sign Up Sign Up” and “Contact Us”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Hotjar and LinkedIn Insight.

Privacy and tracking

  • 10 trackers load before any consent

    10

    Before a visitor clicks anything, the page loads Amazon Ads, Comscore, Criteo, Google Ads and Google Analytics and 5 mores (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.

  • 28 cookies set on arrival

    28

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

  • 96 other companies contacted

    Loading the homepage contacts 96 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 billboard.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 27 issues on billboard.com, including 3 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
billboard.com website review: scores and fixes