SEOking

Website audit report

redbull.com

73
/ 100
C · Needs work

1 critical and 5 high-severity issues found across 133 checks.

Checks run
133
Passed
83
Failed
42
Pages crawled
12

Scanned 2026-09-06T03:58:06+00:00 · 4 host IPs · cert expires in 174 days

This report is not offered to search engines. It is reachable by link only. If you own redbull.com you can publish or delete it.

How you compare

Measured against every site SEOking has audited: a corpus that grows with each scan and cannot be reconstructed after the fact.

Your position

53th percentile of 32 sites audited. The average site scores 73, the median 72.

The most unusual thing you fail

No dead-end pages

95% of the sites we have audited get this right and yours does not. Of everything on this report, it is the fault that most sets you apart from your competition, which makes it the first thing worth fixing.

Inbox Trust Index

Our own measure of whether your domain is trusted by the systems that decide if mail reaches an inbox. No other website audit reports this. It is built from BounceZero's deliverability platform.

93
/ 100
Excellent

Your domain is configured the way the top tier of senders are.

Measured against our corpus

Deliverability here is inconsistent — a meaningful share of addresses fail. Mailbox quality at your domain ranks in the 72nd percentile of domains we have verified enough addresses at to judge.

First measured 2026-07-16.

How your page actually renders

Loaded in a real browser at phone size. This is close to what a visitor and Google's renderer see.

Screenshot of redbull.com on a mobile viewport
390 × 844 viewport
Largest paint
0.8s
Layout shift
0
Requests
142
Words rendered
348
JS errors
1
Failed resources
3

Your plan

The 42 faults on this report come from 16 underlying causes. Fixing a cause fixes everything under it, so this is ordered by score returned per unit of work, not by severity alone.

The 7 quickest steps here take you from 73 to about 81. That is 8 points for changes measured in minutes and hours, not weeks.

  1. 1. Stop JavaScript overriding the indexing directives

    Development work · days to weeks→ 76/100

    A canonical or noindex injected at runtime silently overrides what the server said, and the served HTML still looks correct to anyone reading the source.

    Fixes 2 findings: JavaScript does not rewrite indexing directives · The title survives rendering

  2. 2. Make the structured data qualify

    Template change · a few hours→ 80/100

    Rich results — ratings, prices, FAQs, breadcrumbs — are what turn a listing into an advert, and they are decided by whether a few required properties are present. Markup that is invalid or incomplete is work already done that currently earns nothing.

    Fixes 6 findings: The business is a describable entity · Content is marked up to be answered · The business is identified in structured data · Breadcrumbs are marked up · Site-wide search is declared · The entity links out to its profiles

  3. 3. Harden DNS and hosting

    Server or CDN config · under an hour→ 83/100

    Resilience and reputation work — lower urgency, but cheap while you are already in these systems.

    Fixes 5 findings: No JavaScript errors on load · All page resources load successfully · Certificate surface is proportionate · DNSSEC enabled · CAA record restricts certificate issuance

  4. 4. Point the site's own authority at the pages that earn

    Template change · a few hours→ 86/100

    Internal links decide which of your pages search engines treat as important, and the decision is usually an accident of navigation design. It costs nothing to change and it changes what ranks.

    Fixes 4 findings: Every page is linked from somewhere · Every page is linked from another · Each page covers a distinct subject · No dead-end pages

  5. 5. Complete the security headers

    Server or CDN config · under an hour→ 87/100

    All set in the same place — your web server or CDN. Half of them are single lines.

    Fixes 4 findings: HSTS header · Content Security Policy header · Cookies are protected · Referrer policy header

  6. 6. Close the takeover and impersonation gaps

    DNS edit · minutes→ 88/100

    A subdomain pointing at a service that released it can be claimed by anyone, who then publishes on your domain. Deleting the record costs nothing and closes it immediately.

    Fixes 1 finding: No lookalike domain can send mail as your brand

  7. 7. Fix what search engines are allowed to see

    Server or CDN config · under an hour→ 90/100

    These decide whether your pages can appear at all. Nothing else on this report matters until they are right.

    Fixes 2 findings: XML sitemap published · No long redirect chains

  8. 8. Write the titles and descriptions

    Content work · days→ 92/100

    Your title and description are the advert Google runs for you, free, every time someone searches.

    Fixes 4 findings: Page titles are unique · Every page has a meta description · Meta descriptions are unique · One H1 per page

  9. 9. Remaining individual fixes

    Mixed · varies→ 94/100

    These do not share a root cause with anything else on the report.

    Fixes 3 findings: Title is the same before and after JavaScript · Navigation is present on every page · No phrase is repeated unnaturally

  10. 10. Fix email authentication

    DNS edit · minutes→ 95/100

    These are all records in your DNS. One editing session fixes every one of them, and it is the change most likely to stop your mail being filtered.

    Fixes 2 findings: MTA-STS policy published · TLS reporting enabled

  11. 11. Reduce what the page has to load

    Development work · days to weeks→ 96/100

    Image and script weight drive every speed metric you are failing. This is the slowest fix here and the one with the longest tail.

    Fixes 3 findings: Images declare width and height · Reasonable number of requests · Images load lazily

  12. 12. Stop wasting the crawl

    Server or CDN config · under an hour→ 97/100

    Filter and session URLs generate unlimited addresses, and every redirect hop is a request that returns nothing. Both spend the budget that should be recrawling pages that earn money.

    Fixes 1 finding: Pages are reached without redirect chains

  13. 13. Fix the page on a phone

    Template change · a few hours→ 98/100

    Google indexes the mobile version of your site, and these are measured in a real phone-sized browser rather than inferred. A page that scrolls sideways or needs pinching to read loses the visitor before the content matters.

    Fixes 1 finding: Tap targets are big enough to hit

  14. 14. Show who stands behind the content

    Content work · days→ 99/100

    Google's guidance asks who produced a page and why they should be trusted. For advice, health, legal or financial topics an anonymous, undated page competes badly against a named one.

    Fixes 2 findings: There is a route to who you are · A publisher is declared in structured data

  15. 15. Decide whether AI assistants may cite you

    Server or CDN config · under an hour→ 99/100

    A growing share of questions are answered without a results page. Being quotable is a distribution channel, and it is usually blocked by a plugin default rather than a decision.

    Fixes 1 finding: A curated summary is published for assistants

  16. 16. Strengthen thin pages

    Content work · days→ 100/100

    Pages with little unique content rarely rank and can hold back how the whole site is judged.

    Fixes 1 finding: Pages have enough content

Fix these first

Ranked by severity, then by how much score each returns.

  1. critical

    1. JavaScript does not rewrite indexing directives

    +9 pts

    JavaScript changes the directives Google acts on after the page loads. The served HTML looks correct to anyone reading the source, and Google indexes what rendering produced — so a canonical or noindex injected at runtime silently overrides everything the server said.

    canonical: served 'https://www.redbull.com/ie-en', rendered 'https://www.redbull.com/fr-fr'

    How to fix: Emit the final canonical and robots directives server-side. Nothing that decides indexing should depend on a script running.

  2. high

    2. No lookalike domain can send mail as your brand

    +8 pts

    We generated and checked 53 plausible misspellings and variants of your domain. 8 of the 21 registered variants has mail servers configured, so it is technically able to send email that reads as yours to anyone skimming a sender address. Many such domains are entirely unrelated businesses that happen to have a similar name — this is a risk to be aware of and to defend against, not evidence that anyone is doing anything.

    dedbull.com   [mail configured]
    rdbull.com   [mail configured]
    rebull.com   [mail configured]
    redbu1l.com   [mail configured]
    reddbull.com   [mail configured]
    redgull.com   [mail configured]
    redull.com   [mail configured]
    reedbull.com   [mail configured]

    How to fix: Publish DMARC at enforcement so mail claiming to be your domain is rejected outright — that is the defence that works regardless of who owns a lookalike. Then register the closest unregistered variants; they cost a few pounds a year and are the cheapest brand protection available.

  3. high

    3. Page titles are unique

    +6 pts

    2 pages share 1 duplicated title(s). Google treats near-identical pages as competing with each other, and usually indexes only one.

    2× Red Bull Energy Drink – Gives You Wiiings
    2 affected URLs

    How to fix: Give every page a title describing that page specifically.

  4. high

    4. Every page is linked from somewhere

    +6 pts

    4 of 11 crawled pages had no internal link pointing at them. Search engines discover pages by following links, so an unlinked page is found late or not at all — and passes on none of its authority.

    4 affected URLs

    How to fix: Link these from a relevant parent page, your navigation, or a hub page.

  5. high

    5. The business is a describable entity

    +6 pts

    No Organization or Person markup. An assistant that cannot name the entity behind the site will describe the business from fragments, or not at all, which is how a competitor becomes the answer.

    How to fix: Add Organization JSON-LD with name, url, logo and sameAs links, so the description an assistant gives of the business is the one you wrote.

Full results

Security & trust

Whether the connection, certificate and headers hold up.

7 passed · 4 failed
78%
  • ✕
    HSTS headermedium

    Missing. Tells browsers to only ever connect over HTTPS.

    Send Strict-Transport-Security: max-age=31536000; includeSubDomains

  • ✕
    Content Security Policy headermedium

    Missing. Limits where scripts may load from, which is the main defence against injected code and card skimmers.

    Add a Content-Security-Policy header, starting in report-only mode.

  • ✕
    Cookies are protectedmedium

    Cookies are set without the Secure and/or HttpOnly flags, so they can be read by scripts or sent over insecure connections.

    rb_geolocation=ie; path=/

    Add Secure, HttpOnly and SameSite to every cookie you set.

  • ✕
    Referrer policy headerlow

    Missing. Controls how much of your URL is leaked to other sites.

    Send Referrer-Policy: strict-origin-when-cross-origin

  • ✓
    Served over HTTPS

    Secure connection working.

  • ✓
    HTTP redirects to HTTPS

    Plain HTTP requests are redirected to the secure version.

  • ✓
    No insecure mixed content

    All resources load securely.

  • ✓
    Certificate is not near expiry

    Certificate valid for another 174 days (expires 2027-02-27).

  • ✓
    Modern TLS version

    Negotiated TLSv1.3.

  • ✓
    MIME sniffing protection header

    MIME sniffing protection is set.

  • ✓
    Clickjacking protection header

    Clickjacking protection is set.

Email deliverability

Whether your mail reaches inboxes or spam folders.

8 passed · 2 failed
94%
  • ✕
    MTA-STS policy publishedlow

    No MTA-STS policy, so mail to you can be delivered unencrypted if an attacker strips TLS.

    Publish an MTA-STS policy and the _mta-sts TXT record.

  • ✕
    TLS reporting enabledlow

    No TLS-RPT record, so delivery-encryption failures go unreported.

    Publish a _smtp._tls TXT record with a reporting address.

  • ✓
    DKIM signing is configured

    DKIM keys published on selector(s): selector1, k1.

  • ✓
    Domain can receive email

    1 mail server(s) configured.

  • ✓
    SPF ends with a fail qualifier

    Ends in -all (hard fail) — the strictest setting.

  • ✓
    SPF stays under the lookup limit

    The record forces about 3 DNS lookups. Comfortably within the limit of 10.

  • ✓
    DMARC reports are collected

    Aggregate reports are being sent to a reporting address.

  • ✓
    Exactly one SPF record

    One SPF record, as required.

  • ✓
    DMARC policy is enforced

    DMARC policy is p=reject.

  • ✓
    BIMI logo published

    BIMI record present — your logo can appear beside your emails.

Speed & Core Web Vitals

How fast real visitors experience the site.

7 passed · 2 failed · 1 skipped
82%
  • ✕
    Images declare width and heightmedium

    2 of 25 images declare dimensions. Images without dimensions cause the page to jump as they load, which is what Cumulative Layout Shift measures.

    Set width and height attributes on every image.

  • ✕
    Images load lazilylow

    1 of 25 images use lazy loading.

    Add loading="lazy" to images below the fold.

  • –
    Core Web Vitals from real users

    Not available: PageSpeed is rate-limiting or unavailable; not measured (retrying in 75s). This usually means the site does not yet have enough Chrome traffic for Google to report field data. Lab measurements below still apply.

  • ✓
    Compression enabled

    Served with gzip compression.

  • ✓
    Server responds quickly

    Median response across 12 page(s) was 181 ms.

  • ✓
    Homepage HTML is not oversized

    Homepage HTML is 847 KB.

  • ✓
    Reasonable number of scripts

    1 external script file(s) on the homepage.

  • ✓
    Browser caching is allowed

    Pages may be cached by browsers and CDNs.

  • ✓
    Images use a modern format

    All 5 image(s) are JPEG or PNG, with no WebP or AVIF alternative. WebP is typically 25-35% smaller at the same quality and is supported by every current browser — on image-led pages this is usually the single largest saving available, and images are what Largest Contentful Paint measures.

  • ✓
    Images are sized for the device

    325 of 382 image(s) provide a srcset.

Search fundamentals

The tags, files and signals search engines read first.

29 passed · 8 failed · 2 skipped
82%
  • ✕
    The business is a describable entityhigh

    No Organization or Person markup. An assistant that cannot name the entity behind the site will describe the business from fragments, or not at all, which is how a competitor becomes the answer.

    Add Organization JSON-LD with name, url, logo and sameAs links, so the description an assistant gives of the business is the one you wrote.

  • ✕
    Content is marked up to be answeredhigh

    No FAQPage, HowTo or QAPage markup. When an assistant answers a question about this service, the page has nothing structured to be cited from, so the citation goes to whoever wrote the answer block.

    Add FAQPage schema for the questions the page answers (the answer must appear as visible text, not only in the markup) and HowTo for process content.

  • ✕
    XML sitemap publishedmedium

    No XML sitemap. Google has to discover your pages by following links, which means deeper pages may never be crawled.

    0 URLs

    Publish sitemap.xml and reference it from robots.txt.

  • ✕
    The business is identified in structured datamedium

    No Organization markup. This is what Google assembles a knowledge panel from — the box with your logo, name and links that appears beside branded searches — and what connects your site to your social profiles. Without it Google infers your identity from third parties instead of from you.

    Add Organization JSON-LD with name, url, logo and sameAs links to your social profiles.

  • ✕
    Breadcrumbs are marked upmedium

    No BreadcrumbList markup. Google replaces the raw URL in your listing with a readable breadcrumb trail when this is present, which is more legible and measurably more clickable — and it is one of the cheapest rich results to earn.

    Add BreadcrumbList JSON-LD to every page below the homepage.

  • ✕
    The entity links out to its profileslow

    No entity markup to attach profiles to.

    Add sameAs URLs to the Google Business Profile, LinkedIn, X and any other profiles the business owns.

  • ✕
    Site-wide search is declaredlow

    No WebSite markup. With a SearchAction it can give you a search box directly inside your Google listing for branded queries.

    Add WebSite JSON-LD, with potentialAction/SearchAction if the site has its own search.

  • ✕
    A curated summary is published for assistantslow

    No /llms.txt. It is a short, plain-text map of what a site is and which pages matter — a convention some assistants read to decide what to quote, and cheap to publish. It is not yet a standard anyone is obliged to honour, so treat it as a low-cost bet rather than a requirement.

    Publish /llms.txt: a heading, one paragraph describing the business, and a linked list of your most important pages.

  • –
    Search Console connected

    Not measured — not configured on this instance. Connecting Search Console adds what no crawl can see: the queries this site already appears for, where it ranks, and how many people click. It is read-only and can be disconnected at any time.

  • –
    Current search visibility

    Not measured — ranking data is not configured on this instance.

  • ✓
    Homepage is indexable

    Homepage is open to indexing.

  • ✓
    Mobile viewport declared

    Mobile viewport is declared.

  • ✓
    Homepage title is present and well sized

    Title is 41 characters.

  • ✓
    Homepage meta description is present

    Description is 149 characters.

  • ✓
    Homepage canonical is correct

    Canonical points at this page.

  • ✓
    Structured data present

    Structured data found: WebPage.

  • ✓
    robots.txt does not block the site

    robots.txt present and open to search engines.

  • ✓
    Canonicals point at indexable pages

    Every canonical points at a page that is allowed to be indexed.

  • ✓
    Language links point both ways

    Every hreflang reference is reciprocated by the page it names.

  • ✓
    Canonical targets are live pages

    Canonical targets all return 200.

  • ✓
    Structured data parses

    All structured data blocks are valid JSON.

  • ✓
    Noindex directives are readable

    No page relies on a directive Google is blocked from reading.

  • ✓
    Language codes are valid

    Every hreflang value is a valid language or language-region code.

  • ✓
    Marked-up content qualifies for rich results

    Every marked-up entity carries the properties Google requires.

  • ✓
    Most crawled pages are indexable

    11 of 11 crawled page(s) (100%) can actually be indexed.

  • ✓
    Each page lists itself

    Every page with hreflang annotations includes itself.

  • ✓
    Language links point at indexable pages

    Every hreflang target is a live, indexable page.

  • ✓
    No canonical chains

    No canonical points at a page that then canonicals somewhere else.

  • ✓
    Structured data is in the served HTML

    All structured data is present in the HTML the server sends.

  • ✓
    AI assistants can cite this site

    Every major assistant is allowed to read and cite these pages.

  • ✓
    Pages are close to the homepage

    Every crawled page sits within four levels of the homepage (deepest: 4).

  • ✓
    Social preview configured

    9 Open Graph tags found.

  • ✓
    A default version is declared

    An x-default version is declared for visitors whose language matches none of your versions.

  • ✓
    URLs are readable

    URLs use lowercase, hyphenated, extension-free paths.

  • ✓
    Content is not served behind query parameters

    0 of 12 crawled URLs carry query parameters other than tracking tags.

  • ✓
    Page language declared

    Language attribute present.

  • ✓
    Link previews are configured for X/Twitter

    4 twitter: tag(s) found.

  • ✓
    Structured data in use

    2 structured data object(s) across 12 page(s): WebPage.

  • ✓
    Model-training access is stated

    No model-training crawler is blocked, so this content may be used to train future models. This is a business decision rather than an SEO one, and it is separate from being cited in answers: refusing training does not remove you from AI results, and allowing it does not put you in them.

Content & structure

Whether pages are unique, linked and crawlable.

14 passed · 14 failed
52%

Local business signals

What Google needs to place you in map results.

0 passed · 0 failed · 1 skipped
100%
  • –
    Local business signals

    Not applicable — nothing on this site indicates a physical location customers visit: no address, phone link, opening hours, map or local business markup. Local search checks are skipped and do not affect the score. If you do serve customers from premises, publishing an address and phone number is the place to start.

Infrastructure

DNS, hosting and delivery configuration.

10 passed · 5 failed · 3 skipped
70%
  • ✕
    No lookalike domain can send mail as your brandhigh

    We generated and checked 53 plausible misspellings and variants of your domain. 8 of the 21 registered variants has mail servers configured, so it is technically able to send email that reads as yours to anyone skimming a sender address. Many such domains are entirely unrelated businesses that happen to have a similar name — this is a risk to be aware of and to defend against, not evidence that anyone is doing anything.

    dedbull.com   [mail configured]
    rdbull.com   [mail configured]
    rebull.com   [mail configured]
    redbu1l.com   [mail configured]
    reddbull.com   [mail configured]
    redgull.com   [mail configured]
    redull.com   [mail configured]
    reedbull.com   [mail configured]

    Publish DMARC at enforcement so mail claiming to be your domain is rejected outright — that is the defence that works regardless of who owns a lookalike. Then register the closest unregistered variants; they cost a few pounds a year and are the cheapest brand protection available.

  • ✕
    Pages are reached without redirect chainsmedium

    2 page(s) are reached through two or more redirects (10 redirect requests across this crawl). Every hop is a request that returns no content, so a three-hop chain triples what it costs to reach one page — and the usual cause is a stack of old rules: http to https, then non-www to www, then an old path to a new one, each added separately.

    https://redbull.com/ → https://www.redbull.com/ → https://www.redbull.com/ie-en
    https://www.redbull.com/ie-en/energydrink/red-bull-pink-edition-sugarfree → https://redbull.com/ie-en/energydrink/products/red-bull-pink-edition-sugarfree → https://www.redbull.com/ie-en/energydrink/p
    2 affected URLs

    Collapse every chain to a single redirect from the original URL straight to the final one, and update internal links to point at the destination rather than relying on the redirect.

  • ✕
    Certificate surface is proportionatemedium

    679 hostname(s) appear in this domain's public certificate history, issued by Let's Encrypt, COMODO CA Limited. A large certified surface is a large attack surface, and every one of those names is public — certificate transparency is a permanent, searchable log.

    Retire certificates for hosts you no longer run, and prefer wildcard certificates where you genuinely need many subdomains.

  • ✕
    DNSSEC enabledlow

    DNSSEC is not enabled, so DNS answers for your domain can't be cryptographically verified.

    Enable DNSSEC at your DNS provider.

  • ✕
    CAA record restricts certificate issuancelow

    No CAA record, so any certificate authority may issue certificates for your domain.

    Publish a CAA record naming the certificate authority you use.

  • –
    Mail server IP is not blacklisted

    Not checked: the blocklists declined queries from this resolver, so reputation could not be confirmed either way. This is excluded from your score rather than guessed at.

  • –
    Server log analysis

    Not measured — no log file supplied. Server logs are the only source that shows what Googlebot actually fetched rather than what it could fetch: which pages it spends its crawl on, which it has never asked for, and what it receives when it does.

  • –
    Whole-site analysis

    Not measured — no whole-site crawl has been run for this domain. The audit above reasons from a sample of pages chosen to cover each template, which describes how the site is built. It cannot say how many of the site's pages are indexable, which templates are thin across every instance, or what sits too deep to be crawled — those are counts, and a sample cannot produce one.

  • ✓
    Redundant nameservers

    6 nameserver(s) configured.

  • ✓
    No subdomain can be taken over

    Checked 25 subdomain(s); none point at a cloud service that has released them.

  • ✓
    No staging or development sites are publicly indexable

    Certificate transparency lists 679 hostname(s) for this domain and none of the development-style hosts are both live and open to indexing.

  • ✓
    No unbounded URL spaces

    No filter, session or calendar URLs that would generate an unbounded space were found.

  • ✓
    Crawled URLs return content

    0 of 12 URL(s) followed during this crawl returned a redirect or an error (0%).

  • ✓
    Certificate is not shared with unrelated domains

    Your certificate covers only your own domain.

  • ✓
    Internal links pass authority

    0 internal link(s) are marked nofollow.

  • ✓
    Software versions are not disclosed

    No version numbers advertised in response headers.

  • ✓
    Hosting network identified

    Served from AS20940 (AKAMAI-ASN1 Akamai International B.V.), announced in 23.48.23.0/24 — a block of 256 addresses.

  • ✓
    What this audit examined

    12 page(s) were examined, chosen to cover 11 of the 13 distinct page templates found across 12 known URLs. Pages are sampled by template rather than in sitemap order, because the first pages of a sitemap are usually all the same kind — a sample of one template would describe that template rather than the site. Findings below therefore apply to the templates listed, and a fault in a template is normally a fault on every page built from it.

Off-page authority

Who links to this site, with what text, and how that compares.

0 passed · 0 failed · 1 skipped
100%
  • –
    Off-page profile

    Not measured — off-page data is not configured on this instance.

What Google's renderer sees

The site loaded in a real browser, the way a visitor and a crawler get it.

8 passed · 7 failed
60%
  • ✕
    JavaScript does not rewrite indexing directivescritical

    JavaScript changes the directives Google acts on after the page loads. The served HTML looks correct to anyone reading the source, and Google indexes what rendering produced — so a canonical or noindex injected at runtime silently overrides everything the server said.

    canonical: served 'https://www.redbull.com/ie-en', rendered 'https://www.redbull.com/fr-fr'

    Emit the final canonical and robots directives server-side. Nothing that decides indexing should depend on a script running.

  • ✕
    No JavaScript errors on loadmedium

    1 JavaScript error(s) fire when the page loads. Broken scripts commonly break booking forms, menus and tracking without anything looking wrong.

    unable to load font [object Object] JSHandle@object

    Open your browser's console on the live site and fix what it reports.

  • ✕
    All page resources load successfullymedium

    3 resource(s) failed to load. Missing images and stylesheets are visible to customers; missing scripts break features.

    https://smart-components-api.redbull.com/report-usage?package=rb-occasions-carousel&importType=npm&version=5.7.0&platform=www.redbull.com&location=htt (failed)
    https://smart-components-api.redbull.com/report-usage?package=rb-occasions-carousel&importType=npm&version=5.7.0&platform=www.redbull.com&location=htt (failed)
    https://smart-components-api.redbull.com/report-usage?package=rb-footer&importType=npm&version=5.7.0&platform=www.redbull.com&location=https%3A%2F%2Fw (failed)
    3 affected URLs

    Fix or remove these URLs.

  • ✕
    Tap targets are big enough to hitmedium

    20 of 36 tappable element(s) are smaller than 48x48 pixels, and 10 sit closer than 8 pixels to a neighbour. On a phone that means links and buttons that are hard to hit without zooming, and mis-taps on a checkout or contact button cost conversions directly.

    Aller au contenu (160x36)
    Menu (32x32)
    Connexion (28x28)
    Prenez votre envol : Red Bull Wings Cup  (44x24)
    Caliste, le prodige de la Karmine Corp (20x24)

    Give tappable elements at least 48x48 CSS pixels and 8 pixels of spacing — usually padding on the link rather than a bigger font.

  • ✕
    Title is the same before and after JavaScriptmedium

    JavaScript rewrites the page title after load. Google usually indexes the served title, so the one you see in the browser may not be the one shown in search results.

    served:   Red Bull Energy Drink – Gives You Wiiings
    rendered: Red Bull Energy Drink – Donne des Aiiiles

    Set the final title server-side rather than changing it in script.

  • ✕
    The title survives renderingmedium

    The title tag changes after JavaScript runs. Google usually indexes the rendered title, but rendering is queued separately and can lag the first crawl, so for a while the served title is what appears in results.

    served:   Red Bull Energy Drink – Gives You Wiiings
    rendered: Red Bull Energy Drink – Donne des Aiiiles

    Render the final title server-side.

  • ✕
    Reasonable number of requestsmedium

    The page made 142 network requests to load. Each is a round trip, and on mobile data they add up quickly.

    Remove unused third-party tags, and combine or lazy-load the rest.

  • ✓
    Content is in the HTML, not built by JavaScript

    The served HTML contains 313 words and the rendered page 348 — the content is present before JavaScript runs.

  • ✓
    The mobile page matches the desktop page

    What the server sends a phone matches what it sends a desktop browser.

  • ✓
    Largest Contentful Paint under 2.5s (lab)

    Measured 0.8s on a simulated phone viewport. Google's threshold for 'good' is 2.5s.

  • ✓
    Navigation links are crawlable without JavaScript

    29 links in the served HTML, 24 after rendering — navigation is discoverable.

  • ✓
    Layout stays stable while loading (lab)

    Cumulative Layout Shift measured at 0.000 (good is 0.1 or less).

  • ✓
    The page fits the screen

    The page fits the mobile viewport with no sideways scrolling.

  • ✓
    No excessive JavaScript blocking

    0 long JavaScript task(s) blocked the main thread while loading.

  • ✓
    Body text is legible on a phone

    0 of 69 text block(s) render below 12px on a mobile viewport.

Scan details

Final URLhttps://www.redbull.com/ie-en
Host IPs23.48.23.21, 23.48.23.59, 2a02:26f0:1b00::5c7b:ed08, 2a02:26f0:1b00::5c7b:ed92
Pages crawled12 of 12 attempted
Sitemap URLs0
Nameserversns15.ultradns2.com, ns15.ultradns2.org, pdns91.ultradns.biz, pdns91.ultradns.com, pdns91.ultradns.net, pdns91.ultradns.org
Mail serversredbull-com.mail.protection.outlook.com
DKIM selectorsselector1, k1
Mail server IPs52.101.68.25, 52.101.68.21, 52.101.68.10
TLSTLSv1.3 · TLS_AES_256_GCM_SHA384 · issued by Sectigo Limited
Detected stackcustom / Akamai / other-dns · mail on Microsoft 365
Browser renderCamoufox (stealth Firefox) · 9.5s · 348 words, 24 links after JavaScript
12 URLs crawled
  • https://www.redbull.com/ie-en
  • https://www.redbull.com/ie-en
  • https://www.redbull.com/ie-en/energydrink
  • https://www.redbull.com/ie-en/daniel-wiffen-facts
  • https://www.redbull.com/ie-en/athletes
  • https://www.redbull.com/ie-en/events
  • https://www.redbull.com/ie-en/energydrink/products/red-bull-editions-energy-drinks
  • https://www.redbull.com/ie-en/energydrink/products/red-bull-energy-drink
  • https://www.redbull.com/ie-en/energydrink/products/red-bull-summer-edition
  • https://www.redbull.com/ie-en/energydrink/products/red-bull-pink-edition-sugarfree
  • https://www.redbull.com/ie-en/events/red-bull-wings-cup-ireland-2026
  • https://www.redbull.com/ie-en/projects/red-bull-turn-it-up-ireland-2026

Want these fixed?

BounceZero Ltd does this work: technical remediation, local SEO and email deliverability. Tell us what you want fixed and we'll reply with what it takes. No call required, no obligation.

We only email you about this request. No list, no newsletter.

Watch this site

We re-audit on a schedule and email you only when a check that was passing starts failing. That is usually a recent change to the site or its DNS, and it is findable while still fresh. No digest, no newsletter.

Monitoring means repeatedly fetching your site and emailing about it, so we ask you to prove you own redbull.com first.