Skip to content
Audit Complete

Results for https://datenschutz-generator.de

Visit site
DE · EUR (€) · Estimated Applicable regulations: DSGVO · ePrivacy Directive · EAA Dev cost: €90/hr How jurisdiction is detected
E-commerce Tracking: purchases
Spain Spain · Madrid Completed: Apr 21, 2026 23:14 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)
C79

Site Health

Score: 79 / 100

Based on 8 categories, 0 sections

Fast site — your users get a smooth experience.

Several missing protections leave your users and data exposed.

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.

Rich content metadata — your pages look great everywhere.

Lean and efficient — low environmental impact per visit.

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 · 356 peers
You 79
·
Avg 72
+7 above average
0 50 100
Better than 95% of Cart Functionality sites See full Cart Functionality benchmark →
WooCommerce · 45 peers
You 79
·
Avg 75
At average
0 50 100
Better than 75% of WooCommerce sites See full WooCommerce benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

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

Security › Security Headers
2

HSTS header is missing

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

Security › Security Headers
3

No Content-Security-Policy header found

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

Security › Content Security Policy
4

12 button(s) with no accessible text

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

Accessibility › Link & Button Quality
5

2 image-only link(s) without alt 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

3

High impact, low effort — start here.

Strategic

2

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%2Fdatenschutz-generator.de)](https://beavercheck.com/results/b399234b-869f-44c6-a831-34d999dc05a3)
<a href="https://beavercheck.com/results/b399234b-869f-44c6-a831-34d999dc05a3"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fdatenschutz-generator.de" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fdatenschutz-generator.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 user trust.

3 security gaps detected — browsers may warn visitors about your site.
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 ~23%.

Speed (1)

Page takes 6.6s to load

+12% bounce

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

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

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

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

€405 investment → €4,069/month returns + EUR 20,500,000 risk avoided

Payback period: < 1 month First-year ROI: +11957%

Investment

€405

4h · 5 findings

Monthly returns

€4,069 /mo

~€48,832 / year

  • Conversions recovered €4,069
  • Bandwidth savings €0.23

Regulatory risk avoided

EUR 20,500,000

if kept compliant

  • DSGVO EUR 20,000,000
  • EAA EUR 500,000

Payback period

0 12mo 24mo

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

€405

4.5 developer hours at €90/hr

Based on Germany rates (€90/hr)

Quick wins
€135 3 fixes in ~90 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,708,334 / month at risk

~€20,500,003 / year if left unfixed

Compliance Risk

€20,500,000

DSGVOEAA
  • No privacy policy link detected
    DSGVO: EUR 10,000 – EUR 20,000,000
  • Privacy Policy not detected
    DSGVO: EUR 10,000 – EUR 20,000,000
  • Multiple <main> landmarks (2 found)
    EAA: EUR 1,000 – EUR 500,000

+3 more

Bandwidth Waste

€0.23 /mo

3127.9 MB/mo × 0.074 EUR/GB

  • Optimize transfer: save ~313 KB per page load
    Saves €0.23/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.

68
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
82
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.
92
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.

2.83 s

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

6.61 s

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

100 ms

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

0.019

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

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

6.62 s

Detailed Report

Audit breakdown by category with detailed findings.

68

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 forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:38.753 source:map[column:13494 line:531 type:source-location url:https://datenschutz-generator.de/ urlProvider:network]]]

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.

URLTransfer SizeDuration
/wp-admin/admin-ajax.php?action=wp_dynamic_css&handle=ato...4.9 KiB
datenschutz-generator.de/wp-includes/js/jquery/jquery.min.js?ver=3.7.129.9 KiB183 ms
/wp-content/plugins/woocommerce-german-market/js/WooComme...2.6 KiB
datenschutz-generator.de/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.15.0 KiB
/wp-content/cache/min/1/wp-content/plugins/cart-upsell-fo...629 B
/wp-content/plugins/borlabs-cookie/assets/javascript/borl...1.5 KiB
/wp-content/cache/borlabs-cookie/1/borlabs-cookie-config-...13.2 KiB
/wp-content/cache/min/1/wp-content/cache/borlabs-cookie/1...12.8 KiB183 ms
/wp-content/cache/min/1/wp-content/plugins/woocommerce/as...2.8 KiB
/wp-content/cache/min/1/wp-content/plugins/woocommerce-pa...308 B
/wp-content/cache/min/1/wp-content/plugins/woocommerce-pr...995 B
/wp-content/cache/min/1/wp-content/plugins/woo-discount-r...595 B
/wp-content/plugins/woocommerce-german-market/css/fronten...2.0 KiB
/wp-content/cache/min/1/wp-content/plugins/woocommerce-pr...1.4 KiB
/wp-content/cache/background-css/1/datenschutz-generator....512 B
/wp-content/themes/wordpress-theme-atomion-child/style.cs...500 B
/wp-content/cache/min/1/wp-content/plugins/woocommerce-ge...310 B
/wp-content/cache/min/1/wp-content/themes/wordpress-theme...22.3 KiB
/wp-content/cache/min/1/wp-content/themes/wordpress-theme...35.8 KiB183 ms
/wp-content/cache/background-css/1/datenschutz-generator....5.3 KiB
/wp-content/cache/min/1/wp-includes/css/dashicons.min.css...35.2 KiB183 ms
datenschutz-generator.de/wp-includes/css/jquery-ui-dialog.min.css?ver=6.9.41.7 KiB
/wp-content/cache/background-css/1/datenschutz-generator....25.4 KiB367 ms
/wp-content/cache/min/1/wp-content/plugins/font-awesome-4...7.2 KiB
/wp-content/cache/min/1/wp-content/plugins/woocommerce-ge...588 B
/wp-content/cache/min/1/wp-content/plugins/woocommerce-ge...605 B
/wp-content/cache/min/1/wp-content/plugins/woocommerce-ge...347 B
/wp-content/cache/min/1/wp-content/plugins/cart-upsell-fo...517 B
/wp-content/cache/min/1/wp-content/plugins/dsg-rapidmail-...959 B
/wp-content/cache/min/1/wp-content/plugins/woocommerce-ge...611 B

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

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.

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: 420 ms 124.6 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.

CategoryTime Spent
Other867 ms
Script Evaluation863 ms
Style & Layout550 ms
Rendering373 ms
Parse HTML & CSS123 ms
Script Parsing & Compilation112 ms

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Max Potential First Input Delay 80 ms
Use efficient cache lifetimes
Layout shift culprits
Document request latency
Optimize DOM size
Font display
Improve image delivery
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Avoids enormous network payloads Total size was 1,018 KiB
JavaScript execution time 0.8 s
Avoid long main-thread tasks 10 long tasks found
Avoid non-composited animations 11 animated elements found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 30 ms
Server Backend Latencies 20 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
LCP request discovery
User Timing marks and measures
82

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
div.grw-row > div.rpi-slides-root > div.grw-content-inner > button.rpi-ltgt div.grw-row > div.rpi-slides-root > div.grw-content-inner > button.rpi-ltgt
div.grw-row > div.rpi-slides-root > div.grw-content-inner > button.rpi-ltgt div.grw-row > div.rpi-slides-root > div.grw-content-inner > button.rpi-ltgt

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.right > div#dsg-welcome-switch-2-premiumxxx > label > input#dsg_bwurlchk_input div.right > div#dsg-welcome-switch-2-premiumxxx > label > input#dsg_bwurlchk_input

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Kostenlose Datenschutzerklärung div.entry-content > div#dsg-lazy-load-wrap-1 > div.dsg-butons-start-box > div.col1
Premium Datenschutzerklärung div.entry-content > div#dsg-lazy-load-wrap-1 > div.dsg-butons-start-box > div.col2
div.right > div#dsg-welcome-switch-2-premiumxxx > label > input#dsg_bwurlchk_input div.right > div#dsg-welcome-switch-2-premiumxxx > label > input#dsg_bwurlchk_input
Bundle-Angebot p > a.dsg-prg-link > span.dsg-discount-flag > span
Kostenlose Datenschutzerklärung div.entry-content > div#dsg-lazy-load-wrap-1 > div.dsg-butons-start-box > div.col1
Premium Datenschutzerklärung div.entry-content > div#dsg-lazy-load-wrap-1 > div.dsg-butons-start-box > div.col2
Datenschutzerklärung Kostenlos Premium div#dsg-categories-boxes-wrap > div.category-content-general > a.dsg-category-box > span.text
Kostenlos a.dsg-category-box > span.text > div.dsg-catego-label > div.dsg-catego-label-free
Premium a.dsg-category-box > span.text > div.dsg-catego-label > div.dsg-catego-label-free
Verarbeitungsverzeichnis Premium div#dsg-categories-boxes-wrap > div.category-content-general > a.dsg-category-box > span.text
Premium a.dsg-category-box > span.text > div.dsg-catego-label > div.dsg-catego-label-free
Impressum Kostenlos Premium div#dsg-categories-boxes-wrap > div.category-content-general > a.dsg-category-box > span.text
Kostenlos a.dsg-category-box > span.text > div.dsg-catego-label > div.dsg-catego-label-free
Premium a.dsg-category-box > span.text > div.dsg-catego-label > div.dsg-catego-label-free
AGB Premium div#dsg-categories-boxes-wrap > div.category-content-general > a.dsg-category-box > span.text
Premium a.dsg-category-box > span.text > div.dsg-catego-label > div.dsg-catego-label-free
Widerrufsbelehrung Kostenlos Premium div#dsg-categories-boxes-wrap > div.category-content-general > a.dsg-category-box > span.text
Kostenlos a.dsg-category-box > span.text > div.dsg-catego-label > div.dsg-catego-label-free
Premium a.dsg-category-box > span.text > div.dsg-catego-label > div.dsg-catego-label-free
Kostenlose Datenschutzerklärung div.entry-content > div#dsg-lazy-load-wrap-1 > div.dsg-butons-start-box > div.col1
Premium Datenschutzerklärung div.entry-content > div#dsg-lazy-load-wrap-1 > div.dsg-butons-start-box > div.col2
certready.eu div#certready_main > div.right > p > a

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
certready.eu div#certready_main > div.right > p > a

These are opportunities to improve the legibility of your content.

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-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
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 attributes are used as specified for the element's role
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
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
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
Skip links are focusable.
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
`button`, `link`, and `menuitem` elements have accessible names
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 with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[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
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
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
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.
96

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
ReferenceError: video is not defined at https://datenschutz-generator.de/wp-content/cache/min/1/wp-content/plugins/ts-dsg/js/frontend-general.js?ver=1776363875:118:899
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 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 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
92

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 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
Ohne Scan starten div#dsg-welcome-switch-2-premiumxxx > div.dsg_bwurlchk_form_urlscan-buttpne > div.dsg-start-link-sub-wrap > a.dsg_start_link_premium
Bundle-Angebot div#all_bundles > div.right > p > a.dsg-prg-link

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
Links have descriptive text
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

97
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
79
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.
92
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.

700 ms

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

964 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.011

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

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

972 ms

Detailed Report

Audit breakdown by category with detailed findings.

97

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 forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:46.729 source:map[column:13494 line:533 type:source-location url:https://datenschutz-generator.de/ urlProvider:network]]]

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: div.right > div.dsg-video-outer > div.dsg-video-wrap > video#dsg-video
path: 1,HTML,1,BODY,0,DIV,3,MAIN,0,DIV,0,DIV,3,DIV,1,DIV,0,DIV,0,DIV,0,VIDEO
selector: div.right > div.dsg-video-outer > div.dsg-video-wrap > video#dsg-video
snippet: <video id="dsg-video" poster="https://datenschutz-generator.de/wp-content/plugins/ts-dsg/videos/begruess…" playsinline="">

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

URLTransfer SizeDuration
/wp-admin/admin-ajax.php?action=wp_dynamic_css&handle=ato...4.9 KiB
datenschutz-generator.de/wp-includes/js/jquery/jquery.min.js?ver=3.7.129.9 KiB
/wp-content/cache/borlabs-cookie/1/borlabs-cookie-config-...13.2 KiB71 ms
/wp-content/cache/min/1/wp-content/plugins/cart-upsell-fo...629 B
/wp-content/plugins/woocommerce-german-market/js/WooComme...2.6 KiB
datenschutz-generator.de/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.15.0 KiB
/wp-content/plugins/borlabs-cookie/assets/javascript/borl...1.5 KiB
/wp-content/cache/min/1/wp-content/themes/wordpress-theme...35.8 KiB
/wp-content/cache/min/1/wp-includes/css/dashicons.min.css...35.2 KiB71 ms
/wp-content/cache/min/1/wp-content/plugins/woocommerce-pr...995 B
/wp-content/cache/min/1/wp-content/plugins/woocommerce-pa...308 B
/wp-content/cache/min/1/wp-content/plugins/woocommerce/as...2.8 KiB
/wp-content/cache/min/1/wp-content/plugins/woo-discount-r...595 B
/wp-content/plugins/woocommerce-german-market/css/fronten...2.0 KiB
/wp-content/cache/min/1/wp-content/plugins/woocommerce-ge...310 B
/wp-content/themes/wordpress-theme-atomion-child/style.cs...500 B
/wp-content/cache/min/1/wp-content/plugins/woocommerce-pr...1.4 KiB
/wp-content/cache/min/1/wp-content/cache/borlabs-cookie/1...12.8 KiB
/wp-content/cache/background-css/1/datenschutz-generator....512 B
/wp-content/cache/min/1/wp-content/themes/wordpress-theme...22.3 KiB71 ms
/wp-content/cache/background-css/1/datenschutz-generator....5.3 KiB
datenschutz-generator.de/wp-includes/css/jquery-ui-dialog.min.css?ver=6.9.41.7 KiB
/wp-content/cache/background-css/1/datenschutz-generator....25.4 KiB
/wp-content/cache/min/1/wp-content/plugins/font-awesome-4...7.2 KiB
/wp-content/cache/min/1/wp-content/plugins/woocommerce-ge...605 B
/wp-content/cache/min/1/wp-content/plugins/cart-upsell-fo...517 B
/wp-content/cache/min/1/wp-content/plugins/woocommerce-ge...588 B
/wp-content/cache/min/1/wp-content/plugins/dsg-rapidmail-...959 B
/wp-content/cache/min/1/wp-content/plugins/woocommerce-ge...347 B
/wp-content/cache/min/1/wp-content/plugins/woocommerce-ge...611 B

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

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.

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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: 0.0 ms 124.6 KiB

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

Use efficient cache lifetimes
Layout shift culprits
Document request latency
Optimize DOM size
Font display
Improve image delivery
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Time to Interactive 1.0 s
Max Potential First Input Delay 20 ms
Minify CSS
Avoids enormous network payloads Total size was 1,242 KiB
JavaScript execution time 0.2 s
Minimizes main-thread work 0.8 s
Avoid non-composited animations 11 animated elements found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 30 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 80 ms
Avoid large layout shifts 2 layout shifts found
INP breakdown
User Timing marks and measures
Avoid long main-thread tasks
79

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
div.grw-row > div.rpi-slides-root > div.grw-content-inner > button.rpi-ltgt div.grw-row > div.rpi-slides-root > div.grw-content-inner > button.rpi-ltgt
div.grw-row > div.rpi-slides-root > div.grw-content-inner > button.rpi-ltgt div.grw-row > div.rpi-slides-root > div.grw-content-inner > button.rpi-ltgt

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.right > div#dsg-welcome-switch-2-premiumxxx > label > input#dsg_bwurlchk_input div.right > div#dsg-welcome-switch-2-premiumxxx > label > input#dsg_bwurlchk_input

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
GENERATOREN div.menu-main-container > ul#primary-menu > li#menu-item-4081 > a
SHOP div.menu-main-container > ul#primary-menu > li#menu-item-20223 > a
NEWS & RATGEBER div.menu-main-container > ul#primary-menu > li#menu-item-4495 > a
FAQ & KONTAKT div.menu-main-container > ul#primary-menu > li#menu-item-2627 > a
DR. SCHWENKE div.menu-main-container > ul#primary-menu > li#menu-item-2776 > a
KUNDENKONTO div.menu-main-container > ul#primary-menu > li#menu-item-23447 > a
Kostenlose Datenschutzerklärung div.entry-content > div#dsg-lazy-load-wrap-1 > div.dsg-butons-start-box > div.col1
Premium Datenschutzerklärung div.entry-content > div#dsg-lazy-load-wrap-1 > div.dsg-butons-start-box > div.col2
div.right > div#dsg-welcome-switch-2-premiumxxx > label > input#dsg_bwurlchk_input div.right > div#dsg-welcome-switch-2-premiumxxx > label > input#dsg_bwurlchk_input
Bundle-Angebot p > a.dsg-prg-link > span.dsg-discount-flag > span
Kostenlose Datenschutzerklärung div.entry-content > div#dsg-lazy-load-wrap-1 > div.dsg-butons-start-box > div.col1
Premium Datenschutzerklärung div.entry-content > div#dsg-lazy-load-wrap-1 > div.dsg-butons-start-box > div.col2
Datenschutzerklärung Kostenlos Premium div#dsg-categories-boxes-wrap > div.category-content-general > a.dsg-category-box > span.text
Kostenlos a.dsg-category-box > span.text > div.dsg-catego-label > div.dsg-catego-label-free
Premium a.dsg-category-box > span.text > div.dsg-catego-label > div.dsg-catego-label-free
Verarbeitungsverzeichnis Premium div#dsg-categories-boxes-wrap > div.category-content-general > a.dsg-category-box > span.text
Premium a.dsg-category-box > span.text > div.dsg-catego-label > div.dsg-catego-label-free
Impressum Kostenlos Premium div#dsg-categories-boxes-wrap > div.category-content-general > a.dsg-category-box > span.text
Kostenlos a.dsg-category-box > span.text > div.dsg-catego-label > div.dsg-catego-label-free
Premium a.dsg-category-box > span.text > div.dsg-catego-label > div.dsg-catego-label-free
AGB Premium div#dsg-categories-boxes-wrap > div.category-content-general > a.dsg-category-box > span.text
Premium a.dsg-category-box > span.text > div.dsg-catego-label > div.dsg-catego-label-free
Widerrufsbelehrung Kostenlos Premium div#dsg-categories-boxes-wrap > div.category-content-general > a.dsg-category-box > span.text
Kostenlos a.dsg-category-box > span.text > div.dsg-catego-label > div.dsg-catego-label-free
Premium a.dsg-category-box > span.text > div.dsg-catego-label > div.dsg-catego-label-free
Kostenlose Datenschutzerklärung div.entry-content > div#dsg-lazy-load-wrap-1 > div.dsg-butons-start-box > div.col1
Premium Datenschutzerklärung div.entry-content > div#dsg-lazy-load-wrap-1 > div.dsg-butons-start-box > div.col2
certready.eu div#certready_main > div.right > p > a

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
certready.eu div#certready_main > div.right > p > a

These are opportunities to improve the legibility of your content.

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
Go to page 0 div.grw-content-inner > div.rpi-dots-wrap > div.rpi-dots > button.rpi-dot
Go to page 1 div.grw-content-inner > div.rpi-dots-wrap > div.rpi-dots > button.rpi-dot

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-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
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 attributes are used as specified for the element's role
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
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
No element has a `[tabindex]` value greater than 0
Heading elements appear in a sequentially-descending order
Skip links are focusable.
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
`button`, `link`, and `menuitem` elements have accessible names
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 with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[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
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
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
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.
96

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
ReferenceError: video is not defined at https://datenschutz-generator.de/wp-content/cache/min/1/wp-content/plugins/ts-dsg/js/frontend-general.js?ver=1776363875:118:899
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 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 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
92

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 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
Ohne Scan starten div#dsg-welcome-switch-2-premiumxxx > div.dsg_bwurlchk_form_urlscan-buttpne > div.dsg-start-link-sub-wrap > a.dsg_start_link_premium
Bundle-Angebot div#all_bundles > div.right > p > a.dsg-prg-link

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
Links have descriptive text
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback