Website review, no card needed

foofighters.com logo

foofighters.com website review

Visit site (opens in a new tab)Reviewed 4 November 202629 issues · 61 checks

This review found 29 issues worth fixing on foofighters.com, 14 of them high impact, across 61 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 s2.5 sMay 16Oct 313.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.0 s
May 23, 20263.1 s
May 30, 20263.1 s
Jun 6, 20263.0 s
Jun 13, 20262.7 s
Jun 20, 20263.0 s
Jun 27, 20263.2 s
Jul 4, 20263.5 s
Jul 11, 20263.7 s
Jul 18, 20263.9 s
Jul 25, 20264.0 s
Aug 1, 20264.1 s
Aug 8, 20264.0 s
Aug 15, 20263.8 s
Aug 22, 20263.7 s
Aug 29, 20263.6 s
Sep 5, 20263.4 s
Sep 12, 20263.5 s
Sep 19, 20263.6 s
Sep 26, 20263.6 s
Oct 3, 20263.6 s
Oct 10, 20263.6 s
Oct 17, 20263.7 s
Oct 24, 20263.7 s
Oct 31, 20263.8 s
Real-visitor tap response (INP)75th percentile, phones
92 ms83 msMay 16Oct 3184 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202685 ms
May 23, 202685 ms
May 30, 202688 ms
Jun 6, 202690 ms
Jun 13, 202691 ms
Jun 20, 202691 ms
Jun 27, 202690 ms
Jul 4, 202689 ms
Jul 11, 202689 ms
Jul 18, 202689 ms
Jul 25, 202690 ms
Aug 1, 202690 ms
Aug 8, 202690 ms
Aug 15, 202691 ms
Aug 22, 202691 ms
Aug 29, 202691 ms
Sep 5, 202690 ms
Sep 12, 202687 ms
Sep 19, 202687 ms
Sep 26, 202687 ms
Oct 3, 202686 ms
Oct 10, 202685 ms
Oct 17, 202685 ms
Oct 24, 202684 ms
Oct 31, 202684 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 foofighters.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix60
  • Render-blocking requests

    3.2 s

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

  • Reduce unused JavaScript

    1.5 s · 272 KiB

    About 272 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

  • Mobile performance score: 60

    60/100

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

  • Improve image delivery

    350 ms · 92 KiB

    1 image could be 92 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

  • Use efficient cache lifetimes

    300 ms · 34 KiB

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

  • Google Tag Manager adds 229 ms

    229 ms

    Google Tag Manager costs a phone 229 ms of main-thread work and 296 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, Cookiebot and Adobe TypeKit and others), adding 377 KiB and 321 ms of main-thread time.

  • 3 long tasks on the main thread

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

2 checks passed
  • Main-thread work: 0.7 s

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

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

9 to fix33
  • 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.

  • Real-user CLS: 0.30

    0.30

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

  • Real-user FCP: 3.5 s

    3.5 s

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

  • Largest Contentful Paint: 8.8 s

    8.8 s

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

  • First Contentful Paint: 4.9 s

    4.9 s

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

  • Time to Interactive: 8.9 s

    8.9 s

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

  • Speed Index: 6.1 s

    6.1 s

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

  • Real-user LCP: 3.7 s

    3.7 s

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

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

    +22%

    Over the last 25 four-week periods to 2026-10-31, 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).

  • Tap response (INP) held steady for real visitors

    -1%

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

4 checks passed
  • Real-user INP: 87 ms

    87 ms

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

  • Real-user TTFB: 433 ms

    433 ms

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

  • Total Blocking Time: 80 ms

    80 ms

    Scripts block the page for only 80 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

100
  • About 0.4 g of CO₂ per visit

    0.37 g

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

1 checks passed
  • Page weight: 1.3 MB in 28 requests

    1.3 MB

    Your homepage downloads 1.3 MB in 28 requests on a phone: images 675 KiB (3), scripts 593 KiB (13) and fonts 37 KiB (2). That is a lean page.

Accessibility

3 to fixGoogle 8494
  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • 6 links without text

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

1 checks passed
  • 24 automated accessibility rules passed

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

SEO

6 to fixGoogle 9267
  • robots.txt blocks all crawlers

    Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

  • No H1 headline

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

  • Title is short (4 characters)

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

  • Meta description is short (32 characters)

    Your meta description is only 32 characters: “Official website of Foo Fighters”. 70 to 160 characters is enough to sell the click.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • 3 links crawlers can't follow

    3 links have no real href, so search engines can't follow them.

4 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • Open Graph tags complete

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

  • XML sitemap found

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

AI search readiness

100
  • No llms.txt

    There is no https://foofighters.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, 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.

  • Organization data: 4 of 6 facts

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

Best practices

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • 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 direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 21 words

    The homepage has only about 21 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) 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).

  • 6 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
E-commerce
Shopify Plus
Analytics
Google Tag Manager
Hosting
Cloudflare

Company

Founded
1995

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on foofighters.com, including 15 speed issues, 6 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