D — https://dict.cc | BeaverCheck Audit

Site Health

Score: 69 / 100

Based on 8 categories, 0 sections

Your load time meets Google's 'Good' threshold — fine-tuning can still help.

Several missing protections leave your users and data exposed.

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

Well-optimized for search — your content is discoverable.

Good server performance with room for optimization.

Several regulatory requirements are not yet met.

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

Confiant · 21 peers

You 69

Avg 71

At average

0 50 100

Better than 4% of Confiant sites See full Confiant benchmark →

Funding Choices · 197 peers

You 69

Avg 71

At average

0 50 100

Better than 16% of Funding Choices sites See full Funding Choices benchmark →

Top Priorities (5)

/.svn/entries is publicly accessible

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

Security › Information Leakage

Content-Security-Policy header is missing

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

Security › Security Headers

HSTS header is missing

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

Security › Security Headers

No Content-Security-Policy header found

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

Security › Content Security Policy

2 image-in-link without alt text

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

Accessibility › Alt Text Quality

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%2Fdict.cc)](https://beavercheck.com/results/c16875e8-28a6-43bb-aae4-4e82349f27b6)

HTML

<a href="https://beavercheck.com/results/c16875e8-28a6-43bb-aae4-4e82349f27b6"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fdict.cc" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fdict.cc

This badge auto-updates with your latest scan result.

What fixing these means

Your site has several issues that may be affecting user experience and business outcomes. 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.

4 security gaps detected — browsers may warn visitors about your site.

1 accessibility issue excludes users who rely on assistive technology.

Could reach Estimate based on resolving critical issues

Conversion Barriers

1 critical 7 warning

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

Speed (1)

High main-thread blocking time

+2% bounce

Page is non-interactive for 586ms 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)

4 form field(s) without a label

+6% bounce

Screen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes

Fix: Associate every input with a visible <label for="…">; add autocomplete attributes

Content (1)

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

Navigation (3)

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

+1% bounce

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

Fix: Rewrite with descriptive phrases that identify the destination

No skip-to-content link

+1% bounce

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

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

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

€315 investment → €0.26/month returns + EUR 120,500,000 risk avoided

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

Investment

€315

4h · 5 findings

Monthly returns

€0.26 /mo

~€3.16 / year

Bandwidth savings €0.26

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

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

€315

3.5 developer hours at €90/hr

Based on Germany rates (€90/hr)

Quick wins

€180 4 fixes in ~120 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,003 / year if left unfixed

Compliance Risk

€120,500,000

ePrivacy DirectiveDSGVOEAA

No privacy policy link detected
DSGVO: EUR 10,000 – EUR 20,000,000
6 advertising/retargeting trackers detected
DSGVO: EUR 10,000 – EUR 20,000,000
Trackers detected but no cookie policy found
DSGVO: EUR 5,000 – EUR 10,000,000

+13 more

Bandwidth Waste

€0.26 /mo

3550.9 MB/mo × 0.074 EUR/GB

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

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

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.

1.69 s

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

1.69 s

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

586 ms

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

0.000

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

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

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

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

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.

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

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
c.amazon-adsystem.com/aax2/apstag.js	3600.0 s	91.0 KiB

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
m.dict.cc/sprites.css?v=22	1.3 KiB

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: 836 ms

URL	Time Spent
dict.cc/	836 ms
m.dict.cc/deen/	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

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

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
Unattributable	263 ms	17 ms	0.0 ms
cdn.snigelweb.com/prebid/9.43.0/prebid.js?v=18478-1776679187844	255 ms	204 ms	51 ms
m.dict.cc/deen/	234 ms	13 ms	3.9 ms
/pagead/managed/js/gpt/m202604160201/pubads_impl.js	211 ms	160 ms	49 ms
www.googletagmanager.com/gtag/js?id=G-QGHHZZFXXG	190 ms	148 ms	41 ms
adengine.snigelweb.com/dict.cc/18478-1776679187844/adngin.js	166 ms	146 ms	17 ms
cdn.snigelweb.com/adconsent/91/adconsent__tcfapi.js	139 ms	117 ms	3.8 ms
cdn.snigelweb.com/adengine/dict.cc/loader.js	124 ms	115 ms	2.1 ms
fundingchoicesmessages.google.com/i/22152718?ers=3	81 ms	76 ms	1.8 ms
securepubads.g.doubleclick.net/tag/js/gpt.js?network-code=22152718	73 ms	63 ms	8.6 ms
cdn1.anonymised.io/light/bundle.js?v=1.8.54	52 ms	40 ms	9.2 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.

Estimated savings: 0.0 ms 3.6 KiB

URL	Transfer Size	Est Savings
m.dict.cc/main.js?version=38	24.1 KiB	3.6 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: 0.0 ms 501.8 KiB

URL	Transfer Size	Est Savings
cdn.snigelweb.com/prebid/9.43.0/prebid.js?v=18478-1776679187844	198.0 KiB	150.2 KiB
/pagead/managed/js/gpt/m202604160201/pubads_impl.js	187.7 KiB	137.1 KiB
c.amazon-adsystem.com/aax2/apstag.js	90.5 KiB	89.0 KiB
www.googletagmanager.com/gtag/js?id=G-QGHHZZFXXG	162.0 KiB	65.3 KiB
adengine.snigelweb.com/dict.cc/18478-1776679187844/adngin.js	65.9 KiB	37.0 KiB
cdn1.anonymised.io/light/auth.js?v=1.8.54	27.0 KiB	23.3 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
Website CMP logo `div.sn-logo > div.sn-inner-logo > div#sn-back > img`	www.dict.cc/img/logo-dcc3.png

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

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Reduce unused CSS

●Avoids enormous network payloads Total size was 1,156 KiB

●User Timing marks and measures 5 user timings

●Minimizes main-thread work 2.0 s

●Avoid long main-thread tasks 10 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 60 ms

●Server Backend Latencies 40 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

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

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
dict.cc `div#h1-logo-and-search > div#h1-searchtools > div#h1-mobile-header-top > div#h1-mobile-logo`
DE/EN `div#h1-searchtools > div#h1-mobile-header-top > div#h1-mobile-choose-lang > div#h1-mobile-langmenubut`
Suche starten `div#maincontent > div#home_text > div > div`
BG `div#home_text > div > div > a.button1`
BS `div#home_text > div > div > a.button1`
CS `div#home_text > div > div > a.button1`
DA `div#home_text > div > div > a.button1`
EL `div#home_text > div > div > a.button1`
EN `div#home_text > div > div > a.button1`
EO `div#home_text > div > div > a.button1`
ES `div#home_text > div > div > a.button1`
FI `div#home_text > div > div > a.button1`
FR `div#home_text > div > div > a.button1`
HR `div#home_text > div > div > a.button1`
HU `div#home_text > div > div > a.button1`
IS `div#home_text > div > div > a.button1`
IT `div#home_text > div > div > a.button1`
LA `div#home_text > div > div > a.button1`
NL `div#home_text > div > div > a.button1`
NO `div#home_text > div > div > a.button1`
PL `div#home_text > div > div > a.button1`
PT `div#home_text > div > div > a.button1`
RO `div#home_text > div > div > a.button1`
RU `div#home_text > div > div > a.button1`
SK `div#home_text > div > div > a.button1`
SQ `div#home_text > div > div > a.button1`
SR `div#home_text > div > div > a.button1`
SV `div#home_text > div > div > a.button1`
TR `div#home_text > div > div > a.button1`
UK `div#home_text > div > div > a.button1`
Alle `div#home_text > div > div > a.button1`

These are opportunities to improve the legibility of your content.

Navigation

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Learn more why you are seeing this `div.sn-inner > div.sn-content > div.sn-tabs > h3`

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These are opportunities to improve the interpretation of your content by users in different locales.

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

●Image elements have `[alt]` attributes

●Form elements have associated labels

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

●Document has a `<title>` element

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

●Document has a main landmark.

○`[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

○Deprecated ARIA roles were not used

○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

○`[role]`s have all required `[aria-*]` attributes

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○`[role]` values are valid

○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

○Buttons have an accessible name

○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 a valid value for its `[lang]` attribute

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

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

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.

Source	Description
c.amazon-adsystem.com/aax2/apstag.js line 1, col 6076	`Uncaught Error: Unauthorized`

●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

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○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 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
Cookie-Einstellungen `div#maincontent > div#home_text > div > a`

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

Performance

Accessibility

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.

915 ms

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

1.16 s

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

13 ms

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

0.001

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

988 ms

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

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

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Protocol
www4.dict.cc/inc/dict.css?version=296	http/1.1
www4.dict.cc/inc/dict.js.utf8.php?version=773	http/1.1
www4.dict.cc/img/s3.gif	http/1.1
www4.dict.cc/img/l2.gif	http/1.1
www4.dict.cc/img/l1.gif	http/1.1
www4.dict.cc/img/ic_speech1.gif	http/1.1
www4.dict.cc/img/hr4.gif	http/1.1
www4.dict.cc/img/flags/us.png	http/1.1
www4.dict.cc/img/flags/de.png	http/1.1
www4.dict.cc/img/flags/ba.png	http/1.1
www4.dict.cc/img/flags/gb.png	http/1.1
www4.dict.cc/img/plus.gif	http/1.1
www4.dict.cc/img/flags/ru.png	http/1.1
www4.dict.cc/img/flags/it.png	http/1.1
www4.dict.cc/img/bg_langbar.jpg	http/1.1
www4.dict.cc/img/bg_orangebar.gif	http/1.1
www4.dict.cc/img/bg_subnav.gif	http/1.1
www4.dict.cc/img/favicons/favicon4.png	http/1.1

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
www4.dict.cc/inc/dict.js.utf8.php?version=773	38.0 KiB	358 ms
www4.dict.cc/inc/dict.css?version=296	2.4 KiB	289 ms
www.dict.cc/inc/gen/langpairs_1_1774632212.js.php	2.7 KiB

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
c.amazon-adsystem.com/aax2/apstag.js	3600.0 s	91.0 KiB
www.dict.cc/img/Flag_of_Ukraine.svg	0.0 ms	304 B
ad-delivery.net/px.gif?ch=2	86400.0 s	615 B
ad-delivery.net/px.gif?ch=1	86400.0 s	109 B

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

Diagnostics

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: 70 ms 567.5 KiB

URL	Transfer Size	Est Savings
cdn.snigelweb.com/prebid/9.43.0/prebid.js?v=18478-1776679187844	198.0 KiB	150.2 KiB
/pagead/managed/js/gpt/m202604170101/pubads_impl.js?cb=31...	187.4 KiB	135.4 KiB
c.amazon-adsystem.com/aax2/apstag.js	90.5 KiB	89.0 KiB
www.googletagmanager.com/gtag/js?id=G-QGHHZZFXXG	162.0 KiB	66.9 KiB
adengine.snigelweb.com/dict.cc/18478-1776679187844/adngin.js	66.3 KiB	37.1 KiB
pagead2.googlesyndication.com/pagead/js/adsbygoogle.js	54.1 KiB	35.2 KiB
www4.dict.cc/inc/dict.js.utf8.php?version=773	37.7 KiB	30.6 KiB
cdn1.anonymised.io/light/auth.js?v=1.8.54	27.0 KiB	23.2 KiB

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.

Estimated savings: 0.0 ms 7.2 KiB

URL	Transfer Size	Est Savings
www4.dict.cc/inc/dict.js.utf8.php?version=773	37.7 KiB	7.2 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
Website CMP logo `div.sn-logo > div.sn-inner-logo > div#sn-back > img`	www.dict.cc/img/logo-dcc3.png
BOSNIA AND HERZEGOVINA `div > a.noline > b > img`	www4.dict.cc/img/flags/ba.png
UNITED STATES `div > a.noline > b > img`	www4.dict.cc/img/flags/us.png
GREAT BRITAIN `div > a.noline > b > img`	www4.dict.cc/img/flags/gb.png
GERMANY `div > a.noline > b > img`	www4.dict.cc/img/flags/de.png
GERMANY `div > a.noline > b > img`	www4.dict.cc/img/flags/de.png
GERMANY `div > a.noline > b > img`	www4.dict.cc/img/flags/de.png
GERMANY `div > a.noline > b > img`	www4.dict.cc/img/flags/de.png
GERMANY `div > a.noline > b > img`	www4.dict.cc/img/flags/de.png
GERMANY `div > a.noline > b > img`	www4.dict.cc/img/flags/de.png
GERMANY `div > a.noline > b > img`	www4.dict.cc/img/flags/de.png
tbody > tr > td > img `tbody > tr > td > img`	www4.dict.cc/img/l2.gif
tbody > tr > td > img `tbody > tr > td > img`	www4.dict.cc/img/l2.gif
div > div > a.noline > img#icexplanation `div > div > a.noline > img#icexplanation`	www4.dict.cc/img/plus.gif

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

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: 282 ms

URL	Time Spent
dict.cc/	282 ms
www.dict.cc/	0.0 ms

●Time to Interactive 2.4 s

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●LCP breakdown

●Optimize viewport for mobile

●Max Potential First Input Delay 70 ms

●Minify CSS

●Reduce unused CSS

●Avoids enormous network payloads Total size was 1,237 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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 50 ms

●Server Backend Latencies 130 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

Accessibility

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
dict.cc `div > b > i > a.notranslate`
English-German Dictionary `tbody > tr > td > h1.mainheadline`
tr > td > div.noli666 > input.inp1 `tr > td > div.noli666 > input.inp1`
{adv} `tr > td.td3nl > a > var`
econ. `tbody > tr > td.td4nl > dfn`
jobs `tbody > tr > td.td4nl > dfn`
dict.cc: English-German and Multilingual Dictionary `body > div#maincontent > div > h2`
Multilingual `div#maincontent > div > h2 > a`
2025-11-14: `div#maincontent > div > div.news > em`
2025-11-06: `div#maincontent > div > div.news > em`
2025-05-28: `div#maincontent > div > div.news > em`
2025-03-15: `div#maincontent > div > div.news > em`
English-German dictionary developed to help you share your knowledge with other… `body > div#maincontent > div.aftertable`
More information `body > div#maincontent > div.aftertable > a`
Questions and Answers `body > div#maincontent > div.aftertable > a`
Advertisement `div#maincontent > div#recthomebot > div > span.noline`

These are opportunities to improve the legibility of your content.

Navigation

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Learn more why you are seeing this `div.sn-inner > div.sn-content > div.sn-tabs > h3`

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > div > a > img `div > div > a > img`
div > div > a > img `div > div > a > img`
div#maincontent > div > div.news > img `div#maincontent > div > div.news > img`
div#maincontent > div > div.news > img `div#maincontent > div > div.news > img`

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
tr > td > div.noli666 > input#sinp `tr > td > div.noli666 > input#sinp`

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
DE <> EN DE –> EN EN –> DE ----- DE <> EN ----- DE <> BG DE <> BS DE <> CS DE <… `td > div.noli666 > div > select#lpddbsf`

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
tbody > tr > td.td2nl > a `tbody > tr > td.td2nl > a`
tbody > tr > td.td2nl > a `tbody > tr > td.td2nl > a`
div > div > div > a `div > div > div > a`

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

Best practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Home `body > div#maincontent > div.orangebar > a`
New Website `body > div#maincontent > div.orangebar > a`
About `body > div#maincontent > div.orangebar > a`
Users `body > div#maincontent > div.orangebar > a`
Contribute! `body > div#maincontent > div.orangebar > a`
00:42 `tr > td.td4nl > b > a`
sweet {adj} [cute] `tbody > tr > td.td4nl > a`
gra `tr > td.td4nl > b > a`
Vee `tr > td.td4nl > b > a`
00:32 `tr > td.td3nl > b > a`
jdn./etw. aus dem Weg räumen [ugs.] [Redewendung] `tbody > tr > td.td3nl > a`
BHM `tr > td.td3nl > b > a`
pol `tr > td.td3nl > b > a`
04-22 `tr > td.td3nl > b > a`
per fortnight {adv} [esp. Br.] `tbody > tr > td.td3nl > a`
nit `tr > td.td3nl > b > a`
pol `tr > td.td3nl > b > a`
04-22 `tr > td.td4nl > b > a`
jdn. abwerben [z. B. Kunden] `tbody > tr > td.td4nl > a`
nit `tr > td.td4nl > b > a`
pol `tr > td.td4nl > b > a`
Voice: `tr > td.td2nl > b > a`

These items highlight common accessibility best practices.

Screen readers have features to make navigating tables easier. Ensuring that tables use the actual caption element instead of cells with the `[colspan]` attribute may improve the experience for screen reader users. Learn more about captions.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 4870 polarjud GreatFallsStatistics... 2 4214 Halmafelix 3 316… `body > div#maincontent > div > table.nopad`

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Time English German Checked by 00:42 sweet {adj} [cute] mausig [ugs.] gra Vee p… `body > div#maincontent > table`

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

●Input buttons have discernible text.

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

●Document has a `<title>` element

●Links are distinguishable without relying on color.

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

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

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●Document has a main landmark.

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA attributes are used as specified for the element's role

○Deprecated ARIA roles were not used

○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

○`[role]`s have all required `[aria-*]` attributes

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○`[role]` values are valid

○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

○Buttons have an accessible name

○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 a valid value for its `[lang]` attribute

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Elements with visible text labels have matching accessible names.

Best Practices

Browser Compatibility

Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Source	Description
c.amazon-adsystem.com/aax2/apstag.js line 1, col 6076	`Uncaught Error: Unauthorized`

●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

●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

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Detected JavaScript libraries

SEO

Content Best Practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
www.dict.cc/latest-verifications.php	More
www.dict.cc/?s=about%3A	More information

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > div > a > img `div > div > a > img`
div > div > a > img `div > div > a > img`
div#maincontent > div > div.news > img `div#maincontent > div > div.news > img`
div#maincontent > div > div.news > img `div#maincontent > div > div.news > img`

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

Crawling and Indexing

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Cookie Settings `tbody > tr > td.td1 > a`

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

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Results for https://dict.cc

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Speed (1)

Trust (2)

Usability (1)

Content (1)

Navigation (3)

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

Contrast

Navigation

Internationalization and localization

Best Practices

General

SEO

Crawling and Indexing

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Navigation

Internationalization and localization

Names and labels

Best practices

Best Practices

Browser Compatibility

General

SEO

Content Best Practices

Crawling and Indexing

Keyboard Shortcuts