Website review, no card needed

redbullracing.com logo

redbullracing.com website review

Visit site (opens in a new tab)Reviewed 4 November 202639 issues · 84 checks

This review found 39 issues worth fixing on redbullracing.com, 14 of them high impact, across 84 checks. The most urgent: use efficient cache lifetimes. 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
3.9 s2.1 sMay 16Oct 312.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.7 s
May 23, 20262.7 s
May 30, 20262.7 s
Jun 6, 20262.6 s
Jun 13, 20262.6 s
Jun 20, 20263.0 s
Jun 27, 20263.2 s
Jul 4, 20263.4 s
Jul 11, 20263.4 s
Jul 18, 20263.3 s
Jul 25, 20263.0 s
Aug 1, 20263.2 s
Aug 8, 20263.5 s
Aug 15, 20263.7 s
Aug 22, 20263.7 s
Aug 29, 20263.0 s
Sep 5, 20263.0 s
Sep 12, 20262.8 s
Sep 19, 20262.6 s
Sep 26, 20262.8 s
Oct 3, 20262.5 s
Oct 10, 20262.3 s
Oct 17, 20262.3 s
Oct 24, 20262.4 s
Oct 31, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
191 ms158 msMay 16Oct 31185 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026186 ms
May 23, 2026180 ms
May 30, 2026179 ms
Jun 6, 2026181 ms
Jun 13, 2026184 ms
Jun 20, 2026180 ms
Jun 27, 2026179 ms
Jul 4, 2026174 ms
Jul 11, 2026171 ms
Jul 18, 2026170 ms
Jul 25, 2026177 ms
Aug 1, 2026178 ms
Aug 8, 2026182 ms
Aug 15, 2026187 ms
Aug 22, 2026178 ms
Aug 29, 2026186 ms
Sep 5, 2026186 ms
Sep 12, 2026183 ms
Sep 19, 2026180 ms
Sep 26, 2026170 ms
Oct 3, 2026164 ms
Oct 10, 2026162 ms
Oct 17, 2026176 ms
Oct 24, 2026179 ms
Oct 31, 2026185 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 redbullracing.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. redbullracing.com at 0.5 s0.5 s
  2. redbullracing.com at 0.9 s0.9 s
  3. redbullracing.com at 1.4 s1.4 s
  4. redbullracing.com at 1.9 s1.9 s
  5. redbullracing.com at 2.4 s2.4 s
  6. redbullracing.com at 2.8 s2.8 s
  7. redbullracing.com at 3.3 s3.3 s
  8. redbullracing.com at 3.8 s3.8 s

Speed

11 to fix46
  • Use efficient cache lifetimes

    7.9 s · 1.5 MB

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

  • Reduce unused JavaScript

    3.8 s · 937 KiB

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

  • Mobile performance score: 46

    46/100

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

  • Improve image delivery

    550 ms · 1.9 MB

    17 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 550 ms faster on a phone.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Optanon, Google Tag Manager and storyblok.com and others), adding 8.4 MB and 143 ms of main-thread time.

  • storyblok.com adds 0 ms

    0 ms

    storyblok.com costs a phone 0 ms of main-thread work and 7.0 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.

  • Render-blocking requests

    700 ms

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

  • 14 long tasks on the main thread

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

  • Main-thread work: 3.7 s

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

  • 1,611 HTML elements

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

  • redbull.com adds 0 ms

    0 ms

    redbull.com costs a phone 0 ms of main-thread work and 1.1 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.

  • Reduce unused CSS

    150 ms · 22 KiB

    About 22 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

    21 KiB

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

1 checks passed
  • Server response: 34 ms

    34 ms

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

Core Web Vitals

9 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: 17.6 s

    17.6 s

    Your largest element takes 17.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Get ready for the São Paulo Grand Prix 2026”.

  • Time to Interactive: 22.8 s

    22.8 s

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

  • Speed Index: 10.9 s

    10.9 s

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

  • First Contentful Paint: 3.7 s

    3.7 s

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • Total Blocking Time: 480 ms

    480 ms

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

  • 7 images without width and height

    7 images have no width and height attributes, so the layout jumps as each one loads.

  • 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 186 ms to 185 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

5 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

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

  • Real-user INP: 176 ms

    176 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Largest content (LCP) got 11% faster for real visitors

    -11%

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

  • Cumulative Layout Shift: 0.056

    0.056

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

Images and page weight

2 to fix64
  • Page weight: 10.5 MB in 170 requests

    10.5 MB

    Your homepage downloads 10.5 MB in 170 requests on a phone: images 8.3 MB (76), scripts 1.6 MB (34) and other files 286 KiB (39). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    max-verstappen-hungarian-grand-prix-2026 is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 3.0 g of CO₂ per visit

    2.98 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.98 g of CO₂e: 357.6 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

7 to fixGoogle 8390
  • 5 buttons without a name

    5 buttons have no accessible name, so screen readers announce just “button”.

  • Form elements must have labels (1 element)

    Form elements must have labels: 1 element on the page fails this check, rated critical by axe-core.

  • Links must have discernible text (4 elements)

    Links must have discernible text: 4 elements on the page fail this check, rated serious by axe-core.

  • Form elements should have a visible label (1 element)

    Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

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

  • Zoom is disabled

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

  • Alternative text of images should not be repeated as text (3 elements)

    Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 54 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

1 to fixGoogle 10096
  • No structured data

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

  • 58 internal links, 1 external

    The homepage links to 58 pages on redbullracing.com and 1 external page.

7 checks passed
  • Meta description: 113 characters

    Your meta description is 113 characters: “We're passionate about racing, our fans and we love what we do. Our goal is to continue to do things differently.”.

  • One H1 headline

    Your main headline reads: “Get ready for the São Paulo Grand Prix 2026”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Oracle Red Bull Racing | Official F1 Team, News & Updates”.

  • Canonical URL set

    The canonical URL is https://www.redbullracing.com/int-en.

  • 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 and points crawlers to your sitemap.

  • XML sitemap found

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

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

Other pages

6 to fix62
  • 2 pages without a title

    https://www.redbullracing.com/int-en/videos/behind-the-charge-singapore-2026 and https://www.redbullracing.com/int-en/overtakes-explained have no <title>, so Google invents the link text in results.

  • 2 pages share a title

    https://www.redbullracing.com/int-en and / all use the title “Oracle Red Bull Racing | Official F1 Team, News & Updates”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://www.redbullracing.com/int-en/galleries/through-the-years-brazil, https://www.redbullracing.com/int-en/videos/highlights-sunday-mexico-city-grand-prix-2026, https://www.redbullracing.com/int-en/videos/behind-the-charge-singapore-2026, https://www.redbullracing.com/int-en/overtakes-explained and https://www.redbullracing.com/int-en/projects/best-seats-in-the-house-2026 have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    / and https://www.redbullracing.com/int-en/fan-stories use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example /, whose canonical is https://www.redbullracing.com/int-en. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 7 pages without an H1

    https://www.redbullracing.com/int-en/races, https://www.redbullracing.com/int-en/team, https://www.redbullracing.com/int-en/cars, https://www.redbullracing.com/int-en/my-paddock, https://www.redbullracing.com/int-en/videos/behind-the-charge-singapore-2026 and https://www.redbullracing.com/int-en/overtakes-explained and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages with very little text

    /, https://www.redbullracing.com/int-en/team, https://www.redbullracing.com/int-en/cars, https://www.redbullracing.com/int-en/newsletter, https://www.redbullracing.com/int-en/races/sao-paulo-grand-prix-2026 and https://www.redbullracing.com/int-en/projects/best-seats-in-the-house-2026 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 51 found) and read each the way a search engine does.

2 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

Google 96100
  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix80
  • Thin social proof

    Social proof on the homepage: 35 customer or partner logos. 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 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.

  • About 428 words of copy

    The homepage carries about 428 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop”.

  • 1 call to action

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

2 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 redbullracing.com, 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
Analytics
Google Tag Manager
Hosting
Akamai

Company

Headquarters
Milton Keynes

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on redbullracing.com, including 20 speed issues, 1 SEO issue and 2 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