C — https://rp-online.de | BeaverCheck Audit

Site Health

Score: 78 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Good foundation, but a few gaps could be exploited.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Good content signals with minor gaps.

Reasonable footprint with room for optimization.

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

Cart Functionality · 420 peers

You 78

Avg 72

+6 above average

0 50 100

Better than 92% of Cart Functionality sites See full Cart Functionality benchmark →

Bootstrap · 621 peers

You 78

Avg 73

At average

0 50 100

Better than 89% of Bootstrap sites See full Bootstrap benchmark →

Top Priorities (5)

2 link(s) with no accessible text

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

Accessibility › Link & Button Quality

31 button(s) with no accessible text

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

Accessibility › Link & Button Quality

9 image(s) missing alt attribute

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

Accessibility › Alt Text Quality

Soft 404: server returns HTTP 200 for non-existent pages

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

Accessibility › 404 Error Page

Cross-Origin-Embedder-Policy header is missing

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

Security › Security Headers

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Frp-online.de)](https://beavercheck.com/results/49062d57-d124-42ef-8639-05349b60594b)

HTML

<a href="https://beavercheck.com/results/49062d57-d124-42ef-8639-05349b60594b"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Frp-online.de" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Frp-online.de

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. 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 audience reach.

4 accessibility issues exclude users who rely on assistive technology.

1 security gap detected — browsers may warn visitors about your site.

Conversion Barriers

2 critical 7 warning

9 barrier(s) likely increasing bounce by ~31%.

Speed (2)

Page takes 16.5s to load

+12% bounce

Users abandon at ~3s — you're 14.0s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

High main-thread blocking time

+2% bounce

Page is non-interactive for 270ms after first paint

Fix: Defer third-party scripts and split large bundles

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

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

Usability (1)

Severe layout shift during page load

+6% bounce

Users mis-click when content jumps — converting intent into frustration

Fix: Reserve space for images, ads, and embeds with explicit width/height

Content (2)

No Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

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 (2)

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

1 broken link(s) on the page

+2% 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

€585 investment → €0.59/month returns + EUR 120,500,000 risk avoided

Payback period: > 2 years First-year ROI: -99%

Investment

€585

6h · 5 findings

Monthly returns

€0.59 /mo

~€7.04 / year

Bandwidth savings €0.59

Regulatory risk avoided

EUR 120,500,000

if kept compliant

ePrivacy Directive EUR 100,000,000
DSGVO EUR 20,000,000
EAA EUR 500,000

€45 — 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

€585

6.5 developer hours at €90/hr

Based on Germany rates (€90/hr)

Quick wins

€45 1 fixes in ~30 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

€ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

€10,041,667 / month at risk

~€120,500,007 / year if left unfixed

Compliance Risk

€120,500,000

ePrivacy DirectiveDSGVOEAA

No privacy policy link detected
DSGVO: EUR 10,000 – EUR 20,000,000
Trackers detected but no cookie policy found
DSGVO: EUR 5,000 – EUR 10,000,000
Trackers detected but no cookie policy found
DSGVO: EUR 10,000 – EUR 20,000,000

+8 more

Bandwidth Waste

€0.59 /mo

7920.2 MB/mo × 0.074 EUR/GB

Optimize transfer: save ~792 KB per page load
Saves €0.59/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

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

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

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

100

Best Practices

SEO

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.

10.38 s

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

16.51 s

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

270 ms

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

0.281

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

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

16.61 s

Detailed Report

Audit breakdown by category with detailed findings.

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.

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.

Request	Cache TTL	Transfer Size
news.google.com/swg/js/v1/swg-gaa.js	3000.0 s	27.5 KiB
rp-online.de/app/assets/dist/app.js?v=20260414161232	3600.0 s	11.8 KiB
widgets.opinary.com/embed.js	86400.0 s	11.2 KiB
news.google.com/swg/js/v1/swg-button.css	3000.0 s	5.1 KiB
rp-online.de/app/assets/dist/style.css?v=20260414161232	3600.0 s	4.8 KiB
d.rp-online.de/rp.js	3600.0 s	3.8 KiB
rp-online.de/app/assets/dist/rp-online.css?v=20260414161232	3600.0 s	3.0 KiB
www.npttech.com/advertising.js	28800.0 s	3.0 KiB
applets.ebxcdn.com/ebx.js	7200.0 s	1.0 KiB
rp-online.de/app/assets/dist/print.css?v=20260414161232	3600.0 s	486 B
data-497ecca600.rp-online.de/iomm/latest/bootstrap/stub.js	86400.0 s	685 B
data-043610b415.rp-online.de/iomm/latest/bootstrap/stub.js	86400.0 s	666 B

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]

items: [map[node:map[type:text value:Total] score:0.28063] map[node:map[boundingRect:map[bottom:660 height:254 left:17 right:395 top:406 width:378] lhId:page-1-CUSTOM-CARD nodeLabel:Weiter mit RP+ PremiumIch möchte die Inhalte der Rheinischen Post inkl. aller R… path:1,HTML,1,BODY,1,DIV,1,DIV,0,SECTION,2,DIV,2,CUSTOM-CARD selector:div.consent-flyout_container > section.consent-flyout__content > div.desktop:mt-6 > custom-card snippet:<custom-card> type:node] score:0.28063]]

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

value: no origins were preconnected

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

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
rp-online.de/app/assets/dist/style.css?v=20260414161232	4.8 KiB	480 ms
rp-online.de/app/assets/dist/rp-online.css?v=20260414161232	3.0 KiB	480 ms
rp-online.de/assets/skins/rp-online/styles.css?v=20260414161232	25.7 KiB	791 ms

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 8.0 s

URL	Time Spent
rp-online.de/	8.0 s
rp-online.de/info/consent/	0.0 ms

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

Element	Layout shift score
Weiter mit RP+ PremiumIch möchte die Inhalte der Rheinischen Post inkl. aller R… `div.consent-flyout_container > section.consent-flyout__content > div.desktop:mt-6 > custom-card`	0.281

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 24.7 KiB

URL	Transfer Size	Est Savings
rp-online.de/assets/skins/rp-online/styles.css?v=20260414161232	25.4 KiB	24.7 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 2.6 s 371.5 KiB

URL	Transfer Size	Est Savings
accounts.google.com/gsi/client	95.3 KiB	80.6 KiB
rp-online.de/assets/head.js?v=1774856308	98.2 KiB	69.1 KiB
www.googletagmanager.com/gtm.js?id=GTM-KJQSZW7Q	126.0 KiB	65.0 KiB
www.googletagmanager.com/gtag/js?id=G-Z4XDX2NETC&cx=c&gtm=4e64k0h1	149.6 KiB	63.2 KiB
news.google.com/swg/js/v1/swg.js	68.8 KiB	47.3 KiB
rp-online.de/assets/consent/consent-page.js?v=1774856308	45.9 KiB	23.7 KiB
rp-online.de/assets/piano.js?v=1774856308	38.6 KiB	22.4 KiB

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	919 ms
Other	569 ms
Script Parsing & Compilation	342 ms
Style & Layout	333 ms
Parse HTML & CSS	64 ms
Rendering	44 ms
Garbage Collection	20 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

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

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 2,578 KiB

●User Timing marks and measures 5 user timings

●JavaScript execution time 1.2 s

●Avoid long main-thread tasks 13 long tasks found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 310 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 260 ms

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam nec purus nec n… `body.bg-black-slightest > div.page-content`
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam nec purus nec n… `body.bg-black-slightest > div.page-content > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `div.page-content > div.row > div.column > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `div.page-content > div.row > div.column > div.row`

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam nec purus nec n… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam nec purus nec n… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam nec purus nec n… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `div.row > div.column > div.row > div.column`
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam nec purus nec n… `div.row > div.column > div.row > div.column`
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam nec purus nec n… `div.row > div.column > div.row > div.column`
body.bg-black-slightest > div.page-content > div.row > div.column `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
body.bg-black-slightest > div.page-content > div.row > div.column `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `div.row > div.column > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `div.row > div.column > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `div.row > div.column > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `div.page-content > div.row > div.column > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `div.row > div.column > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `div.row > div.column > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `div.row > div.column > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `div.page-content > div.row > div.column > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `div.row > div.column > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `div.row > div.column > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `div.row > div.column > div.row > div.column`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

○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

●`[role]` values are valid

●Buttons have an accessible name

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●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

●Links are distinguishable without relying on color.

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[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-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

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

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

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

○Identical links have the same purpose.

○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

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

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.

Crawling and Indexing

Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Blocking Directive Source
`head > meta`
`https://rp-online.de/robots.txt`

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

○Structured data is valid

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

○Image elements have `[alt]` attributes

○Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

100

Best Practices

SEO

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.

1.92 s

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

2.59 s

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

21 ms

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

0.076

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

1.92 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.72 s

Detailed Report

Audit breakdown by category with detailed findings.

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.

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 ▾

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.

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.

title: Preconnected origins

value: no origins were preconnected

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

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
rp-online.de/app/assets/dist/style.css?v=20260414161232	4.8 KiB	141 ms
rp-online.de/app/assets/dist/rp-online.css?v=20260414161232	3.0 KiB	141 ms
rp-online.de/assets/skins/rp-online/styles.css?v=20260414161232	25.7 KiB	141 ms

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.

Request	Cache TTL	Transfer Size
news.google.com/swg/js/v1/swg-gaa.js	3000.0 s	27.5 KiB
rp-online.de/app/assets/dist/app.js?v=20260414161232	3600.0 s	11.8 KiB
widgets.opinary.com/embed.js	86400.0 s	11.2 KiB
news.google.com/swg/js/v1/swg-button.css	3000.0 s	5.1 KiB
rp-online.de/app/assets/dist/style.css?v=20260414161232	3600.0 s	4.8 KiB
d.rp-online.de/rp.js	3600.0 s	3.8 KiB
rp-online.de/app/assets/dist/rp-online.css?v=20260414161232	3600.0 s	3.0 KiB
www.npttech.com/advertising.js	28800.0 s	3.0 KiB
applets.ebxcdn.com/ebx.js	7200.0 s	1.0 KiB
rp-online.de/app/assets/dist/print.css?v=20260414161232	3600.0 s	486 B

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.4 s

URL	Time Spent
rp-online.de/	1.4 s
rp-online.de/info/consent/	0.0 ms

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 24.7 KiB

URL	Transfer Size	Est Savings
rp-online.de/assets/skins/rp-online/styles.css?v=20260414161232	25.4 KiB	24.7 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

Source: Google web.dev / Lighthouse

Estimated savings: 260 ms 371.0 KiB

URL	Transfer Size	Est Savings
accounts.google.com/gsi/client	95.3 KiB	80.6 KiB
rp-online.de/assets/head.js?v=1774856308	98.2 KiB	69.2 KiB
www.googletagmanager.com/gtm.js?id=GTM-KJQSZW7Q	126.0 KiB	65.0 KiB
www.googletagmanager.com/gtag/js?id=G-Z4XDX2NETC&cx=c&gtm=4e64k0	149.6 KiB	63.4 KiB
news.google.com/swg/js/v1/swg.js	68.8 KiB	47.3 KiB
rp-online.de/assets/consent/consent-page.js?v=1774856308	45.9 KiB	23.7 KiB
rp-online.de/assets/piano.js?v=1774856308	38.6 KiB	21.7 KiB

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

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

●Max Potential First Input Delay 90 ms

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 2,165 KiB

●User Timing marks and measures 5 user timings

●JavaScript execution time 0.2 s

●Minimizes main-thread work 0.6 s

●Avoid long main-thread tasks 2 long tasks found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 20 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 30 ms

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

Accessibility

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam nec purus nec n… `body.bg-black-slightest > div.page-content`
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam nec purus nec n… `body.bg-black-slightest > div.page-content > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `div.page-content > div.row > div.column > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `div.page-content > div.row > div.column > div.row`

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam nec purus nec n… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam nec purus nec n… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam nec purus nec n… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `div.row > div.column > div.row > div.column`
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam nec purus nec n… `div.row > div.column > div.row > div.column`
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam nec purus nec n… `div.row > div.column > div.row > div.column`
body.bg-black-slightest > div.page-content > div.row > div.column `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
body.bg-black-slightest > div.page-content > div.row > div.column `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `div.row > div.column > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `div.row > div.column > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `div.row > div.column > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `div.page-content > div.row > div.column > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `div.row > div.column > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `div.row > div.column > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `div.row > div.column > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `body.bg-black-slightest > div.page-content > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `div.page-content > div.row > div.column > div.row`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `div.row > div.column > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `div.row > div.column > div.row > div.column`
Lorem ipsum dolor sit Amet consectetur adipiscing elit Lorem ipsum dolor sit am… `div.row > div.column > div.row > div.column`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

○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

●`[role]` values are valid

●Buttons have an accessible name

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●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

●Links are distinguishable without relying on color.

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[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-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

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

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

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

○Identical links have the same purpose.

○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

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

SEO

Crawling and Indexing

Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Blocking Directive Source
`head > meta`
`https://rp-online.de/robots.txt`

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

○Structured data is valid

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

○Image elements have `[alt]` attributes

○Document has a valid `rel=canonical`

Results for https://rp-online.de

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Speed (2)

Trust (2)

Usability (1)

Content (2)

Navigation (2)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Best Practices

SEO

Crawling and Indexing

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Best Practices

SEO

Crawling and Indexing

Keyboard Shortcuts