Skip to content
Audit Complete

Results for https://sportradar.com

Visit site
Spain Spain · Madrid Completed: Apr 16, 2026 18:18 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C75

Site Health

Score: 75 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Several missing protections leave your users and data exposed.

Major barriers for users with disabilities — up to 15% of your audience.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Rich content metadata — your pages look great everywhere.

Heavier than average — reducing page weight saves energy and bandwidth.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

WordPress sites average 74
At average
Better than 50% of WordPress sites See full WordPress benchmark →
Amazon Route 53 sites average 72
At average
Better than 73% of Amazon Route 53 sites See full Amazon Route 53 benchmark →

Top Priorities (5)

1

'unsafe-eval' found in script source

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
2

'unsafe-inline' found in script source

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
3

Page weighs 8.8 MB (7.7 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
4

13 link(s) with no accessible text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality
5

2 button(s) with no accessible text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

2

High impact, low effort — start here.

Strategic

3

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fsportradar.com)](https://beavercheck.com/results/cf42905d-1e91-4907-9360-6e22ed9969a4)
<a href="https://beavercheck.com/results/cf42905d-1e91-4907-9360-6e22ed9969a4"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fsportradar.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fsportradar.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 2.7s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

2 security gaps detected — browsers may warn visitors about your site.
Your LCP is 2.7s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.
2 accessibility issues exclude users who rely on assistive technology.
B
Could reach Estimate based on resolving critical issues

Conversion Barriers

1 critical 5 warning

6 barrier(s) likely increasing bounce by ~20%.

Speed (1)

Page loads in 2.7s

+5% bounce

Every additional 100ms above 2.5s costs conversions — you're 191ms over

Fix: Target <2.5s LCP: defer non-critical scripts and optimize the hero image

Trust (1)

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Content (1)

Content is hard to read

+2% bounce

Graduate-level reading difficulty — limits the addressable audience for product or blog pages

Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60

Navigation (3)

14 link(s) with generic text ("click here", "read more")

+1% bounce

Screen-reader users navigating by link list see no context — and search engines can't infer relevance

Fix: Rewrite with descriptive phrases that identify the destination

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

3 broken link(s) on the page

+5% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

£450 investment → £282/month returns + GBP 18,050,000 risk avoided

Payback period: ~2 months First-year ROI: +652%

Investment

£450

6h · 5 findings

Monthly returns

£282 /mo

~£3,386 / year

  • Conversions recovered £281
  • Bandwidth savings £1.54

Regulatory risk avoided

GBP 18,050,000

if kept compliant

  • UK GDPR GBP 17,500,000
  • PECR GBP 500,000
  • Equality Act 2010 GBP 50,000

Payback period

0 12mo 24mo

£75 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

£450

6.0 developer hours at £75/hr

Based on United Kingdom rates (£75/hr)

Quick wins
£75 2 fixes in ~60 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
£ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

£1,504,168 / month at risk

~£18,050,018 / year if left unfixed

Compliance Risk

£18,050,000

UK GDPRPECREquality Act 2010
  • No privacy policy link detected
    UK GDPR: GBP 10,000 – GBP 17,500,000
  • Trackers detected but no cookie policy found
    UK GDPR: GBP 10,000 – GBP 17,500,000
  • Trackers detected but no cookie policy found
    PECR: GBP 1,000 – GBP 500,000

+11 more

Bandwidth Waste

£1.54 /mo

24371.9 MB/mo × 0.063 GBP/GB

  • Optimize transfer: save ~2.4 MB per page load
    Saves £1.54/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

96
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
74
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
77
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.12 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

2.69 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

62 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.008

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.12 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

2.73 s

Detailed Report

Audit breakdown by category with detailed findings.

96

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG
nodeLabel: section#sr_section_1 > div.homeBanner__img > picture.mobile-var > img#ODc4OjExOQ==-1
path: 1,HTML,1,BODY,6,SECTION,0,DIV,1,PICTURE,0,IMG
selector: section#sr_section_1 > div.homeBanner__img > picture.mobile-var > img#ODc4OjExOQ==-1
snippet: <img alt="" nitro-lazy-src="https://cdn-ileimjk.nitrocdn.com/sKgCfsiSczlMciqAtVqCggydSDKvnOYp/assets/i…" class="lazyloaded" decoding="async" nitro-lazy-empty="" id="ODc4OjExOQ==-1" data-nitro-empty-id="ODc4OjExOQ==-1" src="https://cdn-ileimjk.nitrocdn.com/sKgCfsiSczlMciqAtVqCggydSDKvnOYp/assets/i…">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates
value: No additional origins are good candidates for preconnecting

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
nitroscripts.com/sKgCfsiSczlMciqAtVqCggydSDKvnOYp600.0 s963 B

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
div.mbl-sub__body > div.hub-mbl__top > a.hub__ctas__item > img#NzQ4OjE1OA==-1 div.mbl-sub__body > div.hub-mbl__top > a.hub__ctas__item > img#NzQ4OjE1OA==-1
/sKgCfsiSczlMciqAtVqCggydSDKvnOYp/assets/images/optimized...19.8 KiB4.2 KiB
body.home > header.header > a.header__logo > img#MjEzOjE2OQ==-1 body.home > header.header > a.header__logo > img#MjEzOjE2OQ==-1
/sKgCfsiSczlMciqAtVqCggydSDKvnOYp/assets/images/optimized...4.9 KiB4.1 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Diagnostics

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
div.how-mbl__dropdowns > div.how-mbl__dropdowns__item > button.how-mbl__dropdowns__item__head > img#NjMwOjE3OQ==-1
/sKgCfsiSczlMciqAtVqCggydSDKvnOYp/assets/images/source/re...
div.how-mbl__dropdowns > div.how-mbl__dropdowns__item > button.how-mbl__dropdowns__item__head > img#NzA0OjE3OQ==-1
/sKgCfsiSczlMciqAtVqCggydSDKvnOYp/assets/images/source/re...
div.how-mbl__dropdowns > div.how-mbl__dropdowns__item > button.how-mbl__dropdowns__item__head > img#NjcxOjE3OQ==-1
/sKgCfsiSczlMciqAtVqCggydSDKvnOYp/assets/images/source/re...
div.how-mbl__dropdowns > div.how-mbl__dropdowns__item > button.how-mbl__dropdowns__item__head > img#NTgzOjE3Nw==-1
/sKgCfsiSczlMciqAtVqCggydSDKvnOYp/assets/images/source/re...
div.mbl-sub__body > div.who-mbl__top > a.who-mbl__top__item > img#Nzg5OjE2OA==-1 div.mbl-sub__body > div.who-mbl__top > a.who-mbl__top__item > img#Nzg5OjE2OA==-1
/sKgCfsiSczlMciqAtVqCggydSDKvnOYp/assets/images/source/re...
div.mbl-sub__body > div.who-mbl__top > a.who-mbl__top__item > img#NzkzOjE2OA==-1 div.mbl-sub__body > div.who-mbl__top > a.who-mbl__top__item > img#NzkzOjE2OA==-1
/sKgCfsiSczlMciqAtVqCggydSDKvnOYp/assets/images/source/re...
div.mbl-sub__body > div.who-mbl__top > a.who-mbl__top__item > img#Nzk3OjE2OA==-1 div.mbl-sub__body > div.who-mbl__top > a.who-mbl__top__item > img#Nzk3OjE2OA==-1
/sKgCfsiSczlMciqAtVqCggydSDKvnOYp/assets/images/source/re...

More information about the performance of your application. These numbers don't directly affect the Performance score.

Time to Interactive 2.7 s
Max Potential First Input Delay 80 ms
Layout shift culprits
Document request latency
Optimize DOM size
Font display
Forced reflow
LCP breakdown
Modern HTTP
Render blocking requests
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Reduce unused CSS
Reduce unused JavaScript
JavaScript execution time 0.3 s
Minimizes main-thread work 1.9 s
Avoid long main-thread tasks 3 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 60 ms
Server Backend Latencies 40 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 60 ms
Avoid large layout shifts 2 layout shifts found
INP breakdown
User Timing marks and measures
Avoid non-composited animations
74

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.home > header.header > div.header__mbl > button.header__mbl__region body.home > header.header > div.header__mbl > button.header__mbl__region

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.how-mbl__dropdowns > div.how-mbl__dropdowns__item > button.how-mbl__dropdowns__item__head > img#NTgzOjE3Nw==-1
div.how-mbl__dropdowns > div.how-mbl__dropdowns__item > button.how-mbl__dropdowns__item__head > img#NjMwOjE3OQ==-1
div.how-mbl__dropdowns > div.how-mbl__dropdowns__item > button.how-mbl__dropdowns__item__head > img#NjcxOjE3OQ==-1
div.how-mbl__dropdowns > div.how-mbl__dropdowns__item > button.how-mbl__dropdowns__item__head > img#NzA0OjE3OQ==-1

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.home > header.header > a.header__logo body.home > header.header > a.header__logo
div.header__mbl__nav > div > div.header__mbl__nav__foot > a.header__mbl__nav__foot__item div.header__mbl__nav > div > div.header__mbl__nav__foot > a.header__mbl__nav__foot__item
div.header__mbl__nav > div > div.header__mbl__nav__foot > a.header__mbl__nav__foot__item div.header__mbl__nav > div > div.header__mbl__nav__foot > a.header__mbl__nav__foot__item
div.header__mbl__nav > div > div.header__mbl__nav__foot > a.header__mbl__nav__foot__item div.header__mbl__nav > div > div.header__mbl__nav__foot > a.header__mbl__nav__foot__item
div.header__mbl__nav > div > div.header__mbl__nav__foot > a.header__mbl__nav__foot__item div.header__mbl__nav > div > div.header__mbl__nav__foot > a.header__mbl__nav__foot__item
div.header__mbl__nav > div > div.header__mbl__nav__foot > a.header__mbl__nav__foot__item div.header__mbl__nav > div > div.header__mbl__nav__foot > a.header__mbl__nav__foot__item
body.home > section#sr_section_1 > div.container > a#scroll-button body.home > section#sr_section_1 > div.container > a#scroll-button
div.footer__top--socialLink > ul.d__flex > li > a div.footer__top--socialLink > ul.d__flex > li > a
div.footer__top--socialLink > ul.d__flex > li > a div.footer__top--socialLink > ul.d__flex > li > a
div.footer__top--socialLink > ul.d__flex > li > a div.footer__top--socialLink > ul.d__flex > li > a
div.footer__top--socialLink > ul.d__flex > li > a div.footer__top--socialLink > ul.d__flex > li > a
div.footer__top--socialLink > ul.d__flex > li > a div.footer__top--socialLink > ul.d__flex > li > a

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Latest Case Study div.hub__featured > div.hub__featured__list > a.hub__featured__list__item > h6
Reimagining immersive experiences for sports fans and bettors section#sr_section_1 > div.container > div.homeBanner__heading > h4.main__subtitle
The Window for World Cup Audience Growth Is Open and It Won’t Be for Long a.text-decoration-none > div.newsCard__bottom > div.newsCard__bottom--newstitle > h5.color__black

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Imprint footer.footer > div.footer__bottom > div.container > a
Privacy Notice footer.footer > div.footer__bottom > div.container > a
Cookie Notice footer.footer > div.footer__bottom > div.container > a
Report a Security Vulnerability footer.footer > div.footer__bottom > div.container > a
Ethics Hotline footer.footer > div.footer__bottom > div.container > a
Sitemap footer.footer > div.footer__bottom > div.container > a

These items highlight common accessibility best practices.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]` values are valid
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`[aria-hidden="true"]` elements do not contain focusable descendents
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[accesskey]` values are unique
`[aria-*]` attributes match their roles
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements use only permitted ARIA attributes
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Elements with visible text labels have matching accessible names.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
96

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
div.header__mbl__nav > div > div.header__mbl__nav__top > img#NTY1OjE5Ng==-1 div.header__mbl__nav > div > div.header__mbl__nav__top > img#NTY1OjE5Ng==-1
/sKgCfsiSczlMciqAtVqCggydSDKvnOYp/assets/images/optimized...217 x 46 (4.72)599 x 194 (3.09)
Uses HTTPS
Avoids deprecated APIs
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No browser errors logged to the console
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Ensure proper origin isolation with COOP
Mitigate clickjacking with XFO or CSP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Use a strong HSTS policy
77

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destinationLink Text
sportradar.com/privacy-notice/here

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.how-mbl__dropdowns > div.how-mbl__dropdowns__item > button.how-mbl__dropdowns__item__head > img#NTgzOjE3Nw==-1
div.how-mbl__dropdowns > div.how-mbl__dropdowns__item > button.how-mbl__dropdowns__item__head > img#NjMwOjE3OQ==-1
div.how-mbl__dropdowns > div.how-mbl__dropdowns__item > button.how-mbl__dropdowns__item__head > img#NjcxOjE3OQ==-1
div.how-mbl__dropdowns > div.how-mbl__dropdowns__item > button.how-mbl__dropdowns__item__head > img#NzA0OjE3OQ==-1

Format your HTML in a way that enables crawlers to better understand your app’s content.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Get in touch section#contact > div.container > div.getintouch__content > a#show_form

To appear in search results, crawlers need access to your app.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
robots.txt is valid
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

100
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
88
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
100
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
85
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

360 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

819 ms

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.015

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

657 ms

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

824 ms

Detailed Report

Audit breakdown by category with detailed findings.

100

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-VIDEO
nodeLabel: section#sr_section_1 > div.homeBanner__img > div.embed-container > video
path: 1,HTML,1,BODY,6,SECTION,0,DIV,0,DIV,0,VIDEO
selector: section#sr_section_1 > div.homeBanner__img > div.embed-container > video
snippet: <video autoplay="" muted="" loop="" playsinline="" src="https://sportradar.com/wp-content/uploads/2025/11/sr_header-website-2025_v…" type="video/mp4">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates
value: No additional origins are good candidates for preconnecting

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
nitroscripts.com/sKgCfsiSczlMciqAtVqCggydSDKvnOYp600.0 s960 B

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
div.header__nav__item__dropdown > div.hub__ctas > a.hub__ctas__item > img#NDU0OjE0Mg==-1 div.header__nav__item__dropdown > div.hub__ctas > a.hub__ctas__item > img#NDU0OjE0Mg==-1
/sKgCfsiSczlMciqAtVqCggydSDKvnOYp/assets/images/optimized...19.8 KiB13.1 KiB
div.header__nav__item__dropdown > div.how__cta > a.how__cta__box > img#NDM1OjEzNw==-1 div.header__nav__item__dropdown > div.how__cta > a.how__cta__box > img#NDM1OjEzNw==-1
/sKgCfsiSczlMciqAtVqCggydSDKvnOYp/assets/images/optimized...15.1 KiB11.5 KiB
body.home > header.header > a.header__logo > img#MjEzOjE2OQ==-1 body.home > header.header > a.header__logo > img#MjEzOjE2OQ==-1
/sKgCfsiSczlMciqAtVqCggydSDKvnOYp/assets/images/optimized...4.9 KiB4.6 KiB
body.home > header.header > a.header__logo > img#MjE0OjE4NQ==-1 body.home > header.header > a.header__logo > img#MjE0OjE4NQ==-1
/sKgCfsiSczlMciqAtVqCggydSDKvnOYp/assets/images/optimized...4.9 KiB4.6 KiB
div.header__nav__item__dropdown > div.hub__ctas > a.hub__ctas__item > img#NDYyOjE0Mg==-1 div.header__nav__item__dropdown > div.hub__ctas > a.hub__ctas__item > img#NDYyOjE0Mg==-1
/sKgCfsiSczlMciqAtVqCggydSDKvnOYp/assets/images/optimized...6.6 KiB4.4 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Diagnostics

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
div.how__select > div.how__select__list > p.how__select__list__item > img#MjMwOjE3MA==-1 div.how__select > div.how__select__list > p.how__select__list__item > img#MjMwOjE3MA==-1
/sKgCfsiSczlMciqAtVqCggydSDKvnOYp/assets/images/source/re...
div.how__select > div.how__select__list > p.how__select__list__item > img#MjM4OjE3MA==-1 div.how__select > div.how__select__list > p.how__select__list__item > img#MjM4OjE3MA==-1
/sKgCfsiSczlMciqAtVqCggydSDKvnOYp/assets/images/source/re...
div.how__select > div.how__select__list > p.how__select__list__item > img#MjM0OjE3MA==-1 div.how__select > div.how__select__list > p.how__select__list__item > img#MjM0OjE3MA==-1
/sKgCfsiSczlMciqAtVqCggydSDKvnOYp/assets/images/source/re...
div.how__select > div.how__select__list > p.how__select__list__item > img#MjI2OjE2OA==-1 div.how__select > div.how__select__list > p.how__select__list__item > img#MjI2OjE2OA==-1
/sKgCfsiSczlMciqAtVqCggydSDKvnOYp/assets/images/source/re...
div.who__about__list > a.who__about__list__item > div > img#NDk4OjE4MA==-1 div.who__about__list > a.who__about__list__item > div > img#NDk4OjE4MA==-1
/sKgCfsiSczlMciqAtVqCggydSDKvnOYp/assets/images/source/re...
div.who__about__list > a.who__about__list__item > div > img#NTA0OjE4MA==-1 div.who__about__list > a.who__about__list__item > div > img#NTA0OjE4MA==-1
/sKgCfsiSczlMciqAtVqCggydSDKvnOYp/assets/images/source/re...
header.header__regions > div.header__regions__content > button.header__regions__link > img#MTc3OjEyMA==-1 header.header__regions > div.header__regions__content > button.header__regions__link > img#MTc3OjEyMA==-1
/sKgCfsiSczlMciqAtVqCggydSDKvnOYp/assets/images/optimized...
div.who__about__list > a.who__about__list__item > div > img#NTEwOjE4MA==-1 div.who__about__list > a.who__about__list__item > div > img#NTEwOjE4MA==-1
/sKgCfsiSczlMciqAtVqCggydSDKvnOYp/assets/images/source/re...

More information about the performance of your application. These numbers don't directly affect the Performance score.

Layout shift culprits
Document request latency
Optimize DOM size
Font display
Forced reflow
LCP breakdown
Modern HTTP
Render blocking requests
Optimize viewport for mobile
Time to Interactive 0.8 s
Max Potential First Input Delay 20 ms
Minify CSS
Minify JavaScript
Reduce unused CSS
Reduce unused JavaScript
JavaScript execution time 0.1 s
Minimizes main-thread work 0.5 s
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 50 ms
Server Backend Latencies 50 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 80 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
User Timing marks and measures
Avoid long main-thread tasks
Avoid non-composited animations
88

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Latest Case Study div.hub__featured > div.hub__featured__list > a.hub__featured__list__item > h6
Reimagining immersive experiences for sports fans and bettors section#sr_section_1 > div.container > div.homeBanner__heading > h4.main__subtitle
The Window for World Cup Audience Growth Is Open and It Won’t Be for Long a.text-decoration-none > div.newsCard__bottom > div.newsCard__bottom--newstitle > h5.color__black

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.home > header.header > a.header__logo body.home > header.header > a.header__logo
body.home > section#sr_section_1 > div.container > a#scroll-button body.home > section#sr_section_1 > div.container > a#scroll-button
div.footer__top--socialLink > ul.d__flex > li > a div.footer__top--socialLink > ul.d__flex > li > a
div.footer__top--socialLink > ul.d__flex > li > a div.footer__top--socialLink > ul.d__flex > li > a
div.footer__top--socialLink > ul.d__flex > li > a div.footer__top--socialLink > ul.d__flex > li > a
div.footer__top--socialLink > ul.d__flex > li > a div.footer__top--socialLink > ul.d__flex > li > a
div.footer__top--socialLink > ul.d__flex > li > a div.footer__top--socialLink > ul.d__flex > li > a

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Imprint footer.footer > div.footer__bottom > div.container > a
Privacy Notice footer.footer > div.footer__bottom > div.container > a
Cookie Notice footer.footer > div.footer__bottom > div.container > a
Do Not Sell or Share My Personal Information or Limit Use of My Sensitive Perso… footer.footer > div.footer__bottom > div.container > a

These items highlight common accessibility best practices.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]` values are valid
Buttons have an accessible name
Image elements have `[alt]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`[aria-hidden="true"]` elements do not contain focusable descendents
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Document has a main landmark.
Deprecated ARIA roles were not used
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Identical links have the same purpose.
`[accesskey]` values are unique
`[aria-*]` attributes match their roles
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements use only permitted ARIA attributes
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Elements with visible text labels have matching accessible names.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
100

Best Practices

Uses HTTPS
Avoids deprecated APIs
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No browser errors logged to the console
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Ensure proper origin isolation with COOP
Mitigate clickjacking with XFO or CSP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Use a strong HSTS policy
85

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destinationLink Text
sportradar.com/privacy-notice/here

Format your HTML in a way that enables crawlers to better understand your app’s content.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Get in touch section#contact > div.container > div.getintouch__content > a#show_form

To appear in search results, crawlers need access to your app.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback