C — https://tradedoubler.com

Site Health

Score: 72 / 100

Based on 8 categories, 0 sections

Room to improve — your 9.0s load time is above Google's 2.5s 'Good' threshold.

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.

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

How is this calculated?

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

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

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

How the composite score is calculated

How you compare

Ecommerce · 454 peers

You 72

Avg 72

At average

0 50 100

Better than 38% of Ecommerce sites

CMS · 1028 peers

You 72

Avg 73

At average

0 50 100

Better than 25% of CMS sites

Top Priorities (5)

Content-Security-Policy header is missing

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

Security › Security Headers

Cookie '_wixAB3' is missing the Secure flag

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

Security › Cookie Security

No Content-Security-Policy header found

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

Security › Content Security Policy

Page weighs 16.5 MB (4.0 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget

36 link(s) with no accessible text

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

Accessibility › Link & Button Quality

View fix priority matrix

Fix Priority Matrix

5 findings

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%2Ftradedoubler.com)](https://beavercheck.com/results/268d7eec-b11e-48f0-887c-e006c9872321)

HTML

<a href="https://beavercheck.com/results/268d7eec-b11e-48f0-887c-e006c9872321"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Ftradedoubler.com" alt="BeaverCheck Score"></a>

Image URL

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

This badge auto-updates with your latest scan result.

What fixing these means

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

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

Your LCP is 9.0s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.

1 accessibility issue excludes users who rely on assistive technology.

Conversion Barriers

2 critical 5 warning

7 barrier(s) likely increasing bounce by ~28%.

Speed (2)

Page takes 9.0s to load

+12% bounce

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

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

Page feels frozen for 3.9s

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

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

Navigation (3)

41 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

2 broken link(s) on the page

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

₪1,500 investment → ₪19,649/month returns + ILS 500,000 risk avoided

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

Investment

₪1,500

5h · 5 findings

Monthly returns

₪19,649 /mo

~₪235,793 / year

Conversions recovered ₪19,646
Bandwidth savings ₪3.73

Regulatory risk avoided

ILS 500,000

if kept compliant

Privacy Protection Law ILS 500,000

Payback period

0 12mo 24mo

₪450 — 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

₪1,500

5.0 developer hours at ₪300/hr

Based on Israel rates (₪300/hr)

Quick wins

₪450 3 fixes in ~90 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

₪41,670 / month at risk

~₪500,045 / year if left unfixed

Compliance Risk

ILS 500,000

Privacy Protection Law

No privacy policy link detected
Privacy Protection Law: ILS 10,000 – ILS 500,000
Trackers detected but no cookie policy found
Privacy Protection Law: ILS 10,000 – ILS 500,000
Trackers detected but no privacy policy found
Privacy Protection Law: ILS 10,000 – ILS 500,000

+1 more

Bandwidth Waste

₪3.73 /mo

12586.8 MB/mo × 0.296 ILS/GB

Optimize transfer: save ~1.3 MB per page load
Saves ₪3.73/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.

5.09 s

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

9.03 s

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

3.92 s

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

0.013

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

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

25.55 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

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

Learn more ▾

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

Source: Google web.dev / Lighthouse

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
connect.facebook.net/en_US/fbevents.js	1200.0 s	96.6 KiB
/autoCurrencySwitcher/js/jquery.freecurrencies.min.js?rnd...	0.0 ms	63.1 KiB
cdn.cookiehub.eu/c2/50a28c89.js	86400.0 s	71.7 KiB
cdn.cookiehub.eu/c2/css/50a28c89.css	86400.0 s	10.8 KiB
/signals/config/420427622567315?v=2.9.303&r=stable&domain...	1200.0 s	3.9 KiB
/multiCurrencyPricing/js/currencies.js?rnd=5006721722	0.0 ms	3.4 KiB
/hq.js?key=e20800b2-9cb8-4f6f-8c88-2b2277abb5ff&__obr=htt...	0.0 ms	2.8 KiB

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.

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:34.4 source:map[type:text value:[unattributed]]] map[reflowTime:9.704 source:map[column:5850 line:3285 type:source-location url:https://www.tradedoubler.com/ 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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

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
cdn.cookiehub.eu/c2/50a28c89.js	71.7 KiB	1.5 s

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
How bonprix Combined Premium Visibility with 100%+ Growth `div#item-wrapper-93ed8064-a575-4313-85a2-5c645a64f6ab > div.gallery-item-content > picture#multi_picture_undefined > img.gallery-item-visible`	/media/d7b7e1_7b8b6c9364fd4edab2d951bb3bafbfa6~mv2.png/v1...	32.8 KiB	26.6 KiB
Matthias Stadelmeyer `div#item-wrapper-04713040-e45b-4e97-9416-b5bb52f44ca4 > div.gallery-item-content > picture > img#04713040-e45b-4e97-9416-b5bb52f44ca4`	/media/0241cd_c7f1a26e6c8f4282bc33c96d44b121b2~mv2.png/v1...	27.1 KiB	19.3 KiB
Marvin van der Sluis, Partner Development Manager `div#item-wrapper-9db04ef4-60be-49e6-952c-398aa220c341 > div.gallery-item-content > picture > img#9db04ef4-60be-49e6-952c-398aa220c341`	/media/be86d7_80550dfbdd26491f84726d8cc2c65797~mv2.jpeg/v...	25.3 KiB	17.5 KiB
Gertruda Ciuteikyte, Customer Success Director `div#item-wrapper-6c92184a-fd3c-4bf2-a449-c1af2fb36586 > div.gallery-item-content > picture > img#6c92184a-fd3c-4bf2-a449-c1af2fb36586`	/media/be86d7_deb5dfa87cd34fb7b067a26ec4a7add5~mv2.jpg/v1...	23.7 KiB	15.9 KiB

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

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.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.1 s

URL	Time Spent
tradedoubler.com/	1.1 s
www.tradedoubler.com/	0.0 ms

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 ▾

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: 600 ms 826.8 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-S97K1NBWTJ&cx=c&gtm=4e64h1	174.6 KiB	113.7 KiB
connect.facebook.net/en_US/fbevents.js	96.5 KiB	90.6 KiB
/services/pro-gallery-tpa/1.1514.0/WixProGalleryViewerWid...	208.3 KiB	71.7 KiB
www.googletagmanager.com/gtm.js?id=GTM-TGT39TK4	116.7 KiB	65.9 KiB
/services/communities-blog-ooi/1.3166.0/PostListViewerWid...	183.2 KiB	65.0 KiB
www.googletagmanager.com/gtm.js?id=GTM-WJV79Q6J	149.4 KiB	64.8 KiB
www.googletagmanager.com/gtag/js?id=G-S97K1NBWTJ	175.7 KiB	57.2 KiB
www.googletagmanager.com/gtag/js?id=AW-587743736&cx=c&gtm=4e64h1	136.6 KiB	55.0 KiB
www.googletagmanager.com/gtag/js?id=AW-508-974-2645&cx=c&gtm=4e64h1	134.1 KiB	54.4 KiB
/autoCurrencySwitcher/js/jquery.freecurrencies.min.js?rnd...	62.6 KiB	38.7 KiB
connect.facebook.net/en_US/fbevents.js	96.5 KiB	34.7 KiB
www.mlveda.com/WixApps/acsWix/script/acs_wix.js?id=acs_mlveda	52.7 KiB	34.4 KiB
/services/wix-thunderbolt/dist/group_6.8fc8a69c.chunk.min.js	55.9 KiB	34.3 KiB
/services/wix-thunderbolt/dist/motion.4dedec96.chunk.min.js	28.9 KiB	24.5 KiB
static.parastorage.com/services/wix-thunderbolt/dist/main.a5b51f31.bundle.min.js	54.9 KiB	21.9 KiB

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	2.7 s	750 ms	0.0 ms
www.tradedoubler.com/	2.6 s	437 ms	59 ms
static.parastorage.com/unpkg/react@18.3.1/umd/react.production.min.js	2.5 s	2.3 s	1.5 ms
cdn.cookiehub.eu/c2/50a28c89.js	731 ms	451 ms	41 ms
static.parastorage.com/unpkg/requirejs-bolt@2.3.6/requirejs.min.js	710 ms	705 ms	2.3 ms
www.googletagmanager.com/gtag/js?id=AW-508-974-2645&cx=c&gtm=4e64h1	523 ms	471 ms	45 ms
www.mlveda.com/WixApps/acsWix/script/acs_wix.js?id=acs_mlveda	459 ms	422 ms	35 ms
www.googletagmanager.com/gtm.js?id=GTM-WJV79Q6J	387 ms	323 ms	58 ms
www.googletagmanager.com/gtag/js?id=G-S97K1NBWTJ	382 ms	265 ms	68 ms
www.googletagmanager.com/gtag/js?id=AW-587743736&cx=c&gtm=4e64h1	372 ms	317 ms	49 ms
/services/pro-gallery-tpa/1.1514.0/WixProGalleryViewerWid...	293 ms	16 ms	145 ms
connect.facebook.net/en_US/fbevents.js	275 ms	140 ms	133 ms
static.parastorage.com/services/wix-thunderbolt/dist/main.a5b51f31.bundle.min.js	219 ms	159 ms	27 ms
/services/wix-thunderbolt/dist/group_2.2c8bde99.chunk.min.js	176 ms	169 ms	6.2 ms
www.googletagmanager.com/gtm.js?id=GTM-TGT39TK4	173 ms	130 ms	42 ms
/services/wix-thunderbolt/dist/thunderbolt-commons.b6ac63...	172 ms	133 ms	20 ms
/services/wix-thunderbolt/dist/group_6.8fc8a69c.chunk.min.js	134 ms	45 ms	32 ms
/services/editor-elements-library/dist/thunderbolt/rb_wix...	129 ms	116 ms	11 ms
/services/editor-elements-library/dist/thunderbolt/rb_wix...	126 ms	87 ms	36 ms
www.googletagmanager.com/gtag/js?id=G-S97K1NBWTJ&cx=c&gtm=4e64h1	116 ms	41 ms	75 ms
/services/communities-blog-ooi/1.3166.0/PostListViewerWid...	114 ms	8.0 ms	104 ms
static.parastorage.com/unpkg/react-dom@18.3.1/umd/react-dom.production.min.js	106 ms	67 ms	16 ms
/services/wix-thunderbolt/dist/animations.49c55ede.chunk....	96 ms	93 ms	2.1 ms
/services/wix-thunderbolt/dist/group_3.443a1623.chunk.min.js	83 ms	42 ms	40 ms
/services/tag-manager-client/1.1028.0/siteTags.bundle.min.js	77 ms	64 ms	1.4 ms
/services/editor-elements-library/dist/thunderbolt/rb_wix...	67 ms	47 ms	19 ms
/services/wix-thunderbolt/dist/group_5.19f45dc1.chunk.min.js	62 ms	44 ms	7.4 ms
/services/editor-elements-library/dist/thunderbolt/rb_wix...	57 ms	52 ms	3.2 ms
/services/cookie-consent-banner-for-uou/1.819.0//app.bund...	51 ms	43 ms	7.2 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	8.6 s
Other	2.9 s
Script Parsing & Compilation	1.3 s
Style & Layout	940 ms
Parse HTML & CSS	473 ms
Rendering	391 ms
Garbage Collection	331 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 50.3 KiB

URL	Transfer Size	Est Savings
/autoCurrencySwitcher/js/jquery.freecurrencies.min.js?rnd...	62.7 KiB	27.0 KiB
www.mlveda.com/WixApps/acsWix/script/acs_wix.js?id=acs_mlveda	52.7 KiB	23.3 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 30.3 KiB

URL	Transfer Size	Est Savings
.s__3mb942.oUUTDbO--madefor{--wbu-font-stack:var(--wix-font-stack); … } …	18.0 KiB	16.8 KiB
.sQHoZUY.orM9hcb--madefor{--wbu-font-stack:var(--wix-font-stack); … } …	15.0 KiB	13.5 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
www.tradedoubler.com/	267.6 KiB
/services/pro-gallery-tpa/1.1514.0/WixProGalleryViewerWid...	209.0 KiB
/services/communities-blog-ooi/1.3166.0/viewerScript.bund...	207.8 KiB
/services/communities-blog-ooi/1.3166.0/PostListViewerWid...	183.9 KiB
www.googletagmanager.com/gtag/js?id=G-S97K1NBWTJ	175.8 KiB
www.googletagmanager.com/gtag/js?id=G-S97K1NBWTJ&cx=c&gtm=4e64h1	174.7 KiB
www.googletagmanager.com/gtm.js?id=GTM-WJV79Q6J	149.5 KiB
www.googletagmanager.com/gtag/js?id=AW-587743736&cx=c&gtm=4e64h1	136.7 KiB
www.googletagmanager.com/gtag/js?id=AW-508-974-2645&cx=c&gtm=4e64h1	134.1 KiB
www.googletagmanager.com/gtm.js?id=GTM-TGT39TK4	117.0 KiB

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

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●User Timing marks and measures 576 user timings

●Avoid long main-thread tasks 20 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 200 ms

●Server Backend Latencies 270 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○Avoid non-composited animations

Accessibility

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

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
About cookies on this site We use cookies to enhance your browsing experience,… `body.device-mobile-optimized > div.ch2 > div.ch2-container > div#ch2-dialog`

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Antonio Matijevic, Head of Partner Development `div > div.item-link-wrapper > div#pgiedc665f81de44101a85938c8bec0a8b6_0 > div#item-action-edc665f8-1de4-4101-a859-38c8bec0a8b6`
Ignacio Maldonado Garcia `div > div.item-link-wrapper > div#pgi47a7c5e70a334a168ca83cd3bed8c78f_0 > div#item-action-47a7c5e7-0a33-4a16-8ca8-3cd3bed8c78f`

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

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
Allow all `div.ch2-container > div#ch2-dialog > div.ch2-dialog-actions > button.ch2-btn`
Deny all `div.ch2-container > div#ch2-dialog > div.ch2-dialog-actions > button.ch2-btn`

These are opportunities to improve the legibility of your content.

Names and labels

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > div > div#comp-m0dpwfxb > a.aeyn4z `div > div > div#comp-m0dpwfxb > a.aeyn4z`
div > div > div#comp-m0dosabq > a.aeyn4z `div > div > div#comp-m0dosabq > a.aeyn4z`
div > div > div#comp-m0dosabq7 > a.aeyn4z `div > div > div#comp-m0dosabq7 > a.aeyn4z`
div > div > div#comp-m0donala5 > a.aeyn4z `div > div > div#comp-m0donala5 > a.aeyn4z`
div > div > div#comp-m0dotss96 > a.aeyn4z `div > div > div#comp-m0dotss96 > a.aeyn4z`
div > div > div#comp-m0dotssa3 > a.aeyn4z `div > div > div#comp-m0dotssa3 > a.aeyn4z`
div > div > div#comp-m0dou277 > a.aeyn4z `div > div > div#comp-m0dou277 > a.aeyn4z`
div > div > div#comp-m0dou2784 > a.aeyn4z `div > div > div#comp-m0dou2784 > a.aeyn4z`
div > div > div#comp-m0doz8q6 > a.aeyn4z `div > div > div#comp-m0doz8q6 > a.aeyn4z`
div > div > div#comp-m0doz8q67 > a.aeyn4z `div > div > div#comp-m0doz8q67 > a.aeyn4z`
div > div > div#comp-m0dozh941 > a.aeyn4z `div > div > div#comp-m0dozh941 > a.aeyn4z`
div > div > div#comp-m0dq2i95 > a.aeyn4z `div > div > div#comp-m0dq2i95 > a.aeyn4z`
div > div > div#comp-m0nucwmq1 > a.aeyn4z `div > div > div#comp-m0nucwmq1 > a.aeyn4z`
div > div > div#comp-m0nucwmx > a.aeyn4z `div > div > div#comp-m0nucwmx > a.aeyn4z`
div > div > div#comp-m0nucwmz1 > a.aeyn4z `div > div > div#comp-m0nucwmz1 > a.aeyn4z`
div > div > div#comp-m0nucwn11 > a.aeyn4z `div > div > div#comp-m0nucwn11 > a.aeyn4z`
div > div > div#comp-m0nucwne > a.aeyn4z `div > div > div#comp-m0nucwne > a.aeyn4z`
div > div > div#comp-m0nucwnf1 > a.aeyn4z `div > div > div#comp-m0nucwnf1 > a.aeyn4z`
div > div > div#comp-m0nucwng8 > a.aeyn4z `div > div > div#comp-m0nucwng8 > a.aeyn4z`
div > div > div#comp-m0nucwnp2 > a.aeyn4z `div > div > div#comp-m0nucwnp2 > a.aeyn4z`
div > div > div#comp-m0nucwnr1 > a.aeyn4z `div > div > div#comp-m0nucwnr1 > a.aeyn4z`
div > div > div#comp-m0nucwns7 > a.aeyn4z `div > div > div#comp-m0nucwns7 > a.aeyn4z`
div > div > div#comp-m0nucwnu > a.aeyn4z `div > div > div#comp-m0nucwnu > a.aeyn4z`

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.

○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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

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

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

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

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○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

○Form elements have associated labels

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

○`[lang]` attributes have a valid value

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

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
www.tradedoubler.com/v1/bulk/report-exposures	`Failed to load resource: the server responded with a status of 403 ()`

●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

SEO

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

Content Best Practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
www.tradedoubler.com/brands	Learn More
www.tradedoubler.com/for-publishers	Learn More
www.tradedoubler.com/privacy-policy#cookies	Learn more
www.tradedoubler.com/privacy-policy#cookies	Learn more
www.tradedoubler.com/privacy-policy#cookies	Learn more

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

○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 are crawlable

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

1.54 s

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

2.14 s

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

444 ms

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

0.021

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

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

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
connect.facebook.net/en_US/fbevents.js	1200.0 s	96.6 KiB
/autoCurrencySwitcher/js/jquery.freecurrencies.min.js?rnd...	0.0 ms	63.1 KiB
cdn.cookiehub.eu/c2/50a28c89.js	86400.0 s	71.7 KiB
cdn.cookiehub.eu/c2/css/50a28c89.css	86400.0 s	10.8 KiB
/signals/config/420427622567315?v=2.9.303&r=stable&domain...	1200.0 s	3.9 KiB
/multiCurrencyPricing/js/currencies.js?rnd=297783285	0.0 ms	3.4 KiB
/hq.js?key=e20800b2-9cb8-4f6f-8c88-2b2277abb5ff&__obr=htt...	0.0 ms	2.8 KiB

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:45.97 source:map[column:26 line:2319 type:source-location url:https://www.tradedoubler.com/ urlProvider:network]]]

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:0.371 source:map[column:30 line:1647 type:source-location url:https://www.tradedoubler.com/ urlProvider:network]] map[reflowTime:45.97 source:map[column:27 line:2322 type:source-location url:https://www.tradedoubler.com/ urlProvider:network]] map[reflowTime:36.823 source:map[type:text value:[unattributed]]]]

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.

title: Preconnected origins

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

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
cdn.cookiehub.eu/c2/50a28c89.js	71.7 KiB	330 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
Media Markt logo `div.Ry6CMm > div.lhsOLD > wow-image#img_undefined > img`	/media/0241cd_eef30fa53d154789a177f5b8dc0f72c7~mv2.png/v1...	6.6 KiB	4.6 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: 557 ms

URL	Time Spent
tradedoubler.com/	557 ms
www.tradedoubler.com/	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

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: 120 ms 852.5 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-S97K1NBWTJ&cx=c&gtm=4e64h1	174.6 KiB	113.8 KiB
connect.facebook.net/en_US/fbevents.js	96.5 KiB	90.6 KiB
/services/pro-gallery-tpa/1.1514.0/WixProGalleryViewerWid...	208.3 KiB	73.5 KiB
/services/communities-blog-ooi/1.3166.0/PostListViewerWid...	183.2 KiB	69.6 KiB
www.googletagmanager.com/gtm.js?id=GTM-TGT39TK4	116.7 KiB	65.9 KiB
www.googletagmanager.com/gtm.js?id=GTM-WJV79Q6J	149.4 KiB	64.8 KiB
www.googletagmanager.com/gtag/js?id=G-S97K1NBWTJ	175.7 KiB	57.2 KiB
www.googletagmanager.com/gtag/js?id=AW-587743736&cx=c&gtm=4e64h1	136.6 KiB	54.8 KiB
www.googletagmanager.com/gtag/js?id=AW-508-974-2645&cx=c&gtm=4e64h1	134.1 KiB	53.3 KiB
/autoCurrencySwitcher/js/jquery.freecurrencies.min.js?rnd...	62.6 KiB	38.7 KiB
connect.facebook.net/en_US/fbevents.js	96.5 KiB	35.1 KiB
www.mlveda.com/WixApps/acsWix/script/acs_wix.js?id=acs_mlveda	52.7 KiB	34.4 KiB
/services/wix-thunderbolt/dist/group_6.8fc8a69c.chunk.min.js	55.9 KiB	34.3 KiB
/services/wix-thunderbolt/dist/motion.4dedec96.chunk.min.js	28.9 KiB	24.5 KiB
static.parastorage.com/services/wix-thunderbolt/dist/main.a5b51f31.bundle.min.js	54.9 KiB	22.0 KiB
/services/wix-thunderbolt/dist/thunderbolt-commons.b6ac63...	41.5 KiB	20.1 KiB

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	681 ms	218 ms	0.0 ms
static.parastorage.com/unpkg/react@18.3.1/umd/react.production.min.js	608 ms	559 ms	0.4 ms
www.tradedoubler.com/	453 ms	121 ms	19 ms
cdn.cookiehub.eu/c2/50a28c89.js	199 ms	121 ms	10 ms
static.parastorage.com/unpkg/requirejs-bolt@2.3.6/requirejs.min.js	193 ms	192 ms	0.6 ms
www.googletagmanager.com/gtag/js?id=AW-508-974-2645&cx=c&gtm=4e64h1	137 ms	123 ms	11 ms
www.mlveda.com/WixApps/acsWix/script/acs_wix.js?id=acs_mlveda	110 ms	101 ms	7.9 ms
www.googletagmanager.com/gtag/js?id=AW-587743736&cx=c&gtm=4e64h1	108 ms	94 ms	12 ms
www.googletagmanager.com/gtag/js?id=G-S97K1NBWTJ	95 ms	75 ms	19 ms
www.googletagmanager.com/gtm.js?id=GTM-WJV79Q6J	93 ms	76 ms	16 ms
connect.facebook.net/en_US/fbevents.js	74 ms	40 ms	34 ms
www.googletagmanager.com/gtm.js?id=GTM-TGT39TK4	64 ms	44 ms	19 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	2.2 s
Other	531 ms
Script Parsing & Compilation	327 ms
Style & Layout	206 ms
Parse HTML & CSS	123 ms
Garbage Collection	73 ms
Rendering	24 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 50.3 KiB

URL	Transfer Size	Est Savings
/autoCurrencySwitcher/js/jquery.freecurrencies.min.js?rnd...	62.7 KiB	27.0 KiB
www.mlveda.com/WixApps/acsWix/script/acs_wix.js?id=acs_mlveda	52.7 KiB	23.3 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 32.2 KiB

URL	Transfer Size	Est Savings
.s__3mb942.oUUTDbO--madefor{--wbu-font-stack:var(--wix-font-stack); … } …	18.4 KiB	18.4 KiB
.sQHoZUY.orM9hcb--madefor{--wbu-font-stack:var(--wix-font-stack); … } …	15.3 KiB	13.8 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
www.tradedoubler.com/	264.0 KiB
/services/pro-gallery-tpa/1.1514.0/WixProGalleryViewerWid...	209.0 KiB
/services/communities-blog-ooi/1.3166.0/viewerScript.bund...	207.8 KiB
/services/communities-blog-ooi/1.3166.0/PostListViewerWid...	183.9 KiB
www.googletagmanager.com/gtag/js?id=G-S97K1NBWTJ	175.8 KiB
www.googletagmanager.com/gtag/js?id=G-S97K1NBWTJ&cx=c&gtm=4e64h1	174.7 KiB
www.googletagmanager.com/gtm.js?id=GTM-WJV79Q6J	149.5 KiB
www.googletagmanager.com/gtag/js?id=AW-587743736&cx=c&gtm=4e64h1	136.7 KiB
www.googletagmanager.com/gtag/js?id=AW-508-974-2645&cx=c&gtm=4e64h1	134.1 KiB
www.googletagmanager.com/gtm.js?id=GTM-TGT39TK4	117.0 KiB

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

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●User Timing marks and measures 570 user timings

●Avoid long main-thread tasks 9 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 200 ms

●Server Backend Latencies 260 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○Avoid non-composited animations

Accessibility

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
About cookies on this site We use cookies to enhance your browsing experience,… `body > div.ch2 > div.ch2-container > div#ch2-dialog`

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

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
Allow all `div.ch2-container > div#ch2-dialog > div.ch2-dialog-actions > button.ch2-btn`
Deny all `div.ch2-container > div#ch2-dialog > div.ch2-dialog-actions > button.ch2-btn`

These are opportunities to improve the legibility of your content.

Names and labels

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > div > div#comp-m0donal81 > a.aeyn4z `div > div > div#comp-m0donal81 > a.aeyn4z`
div > div > div#comp-m0dpvayn > a.aeyn4z `div > div > div#comp-m0dpvayn > a.aeyn4z`
div > div > div#comp-m0donala5 > a.aeyn4z `div > div > div#comp-m0donala5 > a.aeyn4z`
div > div > div#comp-m0donal95 > a.aeyn4z `div > div > div#comp-m0donal95 > a.aeyn4z`
div > div > div#comp-m0dpwfxb > a.aeyn4z `div > div > div#comp-m0dpwfxb > a.aeyn4z`
div > div > div#comp-m0dosabp > a.aeyn4z `div > div > div#comp-m0dosabp > a.aeyn4z`
div > div > div#comp-m0dosabq > a.aeyn4z `div > div > div#comp-m0dosabq > a.aeyn4z`
div > div > div#comp-m0dosabq7 > a.aeyn4z `div > div > div#comp-m0dosabq7 > a.aeyn4z`
div > div > div#comp-m0dotss83 > a.aeyn4z `div > div > div#comp-m0dotss83 > a.aeyn4z`
div > div > div#comp-m0dotss96 > a.aeyn4z `div > div > div#comp-m0dotss96 > a.aeyn4z`
div > div > div#comp-m0dotssa3 > a.aeyn4z `div > div > div#comp-m0dotssa3 > a.aeyn4z`
div > div > div#comp-m0dpzfn1 > a.aeyn4z `div > div > div#comp-m0dpzfn1 > a.aeyn4z`
div > div > div#comp-m0dpyu2r > a.aeyn4z `div > div > div#comp-m0dpyu2r > a.aeyn4z`
div > div > div#comp-m0dou275 > a.aeyn4z `div > div > div#comp-m0dou275 > a.aeyn4z`
div > div > div#comp-m0dou277 > a.aeyn4z `div > div > div#comp-m0dou277 > a.aeyn4z`
div > div > div#comp-m0dou2784 > a.aeyn4z `div > div > div#comp-m0dou2784 > a.aeyn4z`
div > div > div#comp-m0doz8q5 > a.aeyn4z `div > div > div#comp-m0doz8q5 > a.aeyn4z`
div > div > div#comp-m0doz8q6 > a.aeyn4z `div > div > div#comp-m0doz8q6 > a.aeyn4z`
div > div > div#comp-m0doz8q67 > a.aeyn4z `div > div > div#comp-m0doz8q67 > a.aeyn4z`
div > div > div#comp-m0dq3aom > a.aeyn4z `div > div > div#comp-m0dq3aom > a.aeyn4z`
div > div > div#comp-m0dozh922 > a.aeyn4z `div > div > div#comp-m0dozh922 > a.aeyn4z`
div > div > div#comp-m0dozh934 > a.aeyn4z `div > div > div#comp-m0dozh934 > a.aeyn4z`
div > div > div#comp-m0dozh941 > a.aeyn4z `div > div > div#comp-m0dozh941 > a.aeyn4z`
div > div > div#comp-m0dq2i95 > a.aeyn4z `div > div > div#comp-m0dq2i95 > a.aeyn4z`
div > div > div#comp-m0nucwmq1 > a.aeyn4z `div > div > div#comp-m0nucwmq1 > a.aeyn4z`
div > div > div#comp-m0nucwmx > a.aeyn4z `div > div > div#comp-m0nucwmx > a.aeyn4z`
div > div > div#comp-m0nucwmz1 > a.aeyn4z `div > div > div#comp-m0nucwmz1 > a.aeyn4z`
div > div > div#comp-m0nucwn11 > a.aeyn4z `div > div > div#comp-m0nucwn11 > a.aeyn4z`
div > div > div#comp-m0nucwne > a.aeyn4z `div > div > div#comp-m0nucwne > a.aeyn4z`
div > div > div#comp-m0nucwnf1 > a.aeyn4z `div > div > div#comp-m0nucwnf1 > a.aeyn4z`
div > div > div#comp-m0nucwng8 > a.aeyn4z `div > div > div#comp-m0nucwng8 > a.aeyn4z`
div > div > div#comp-m0nucwnp2 > a.aeyn4z `div > div > div#comp-m0nucwnp2 > a.aeyn4z`
div > div > div#comp-m0nucwnr1 > a.aeyn4z `div > div > div#comp-m0nucwnr1 > a.aeyn4z`
div > div > div#comp-m0nucwns7 > a.aeyn4z `div > div > div#comp-m0nucwns7 > a.aeyn4z`
div > div > div#comp-m0nucwnu > a.aeyn4z `div > div > div#comp-m0nucwnu > a.aeyn4z`

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
English `div > div > div#comp-m06trlsj > div.q6zugB`

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

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

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

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

●`[aria-hidden="true"]` elements do not contain focusable descendents

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

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○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

○Form elements have associated labels

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

○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
www.tradedoubler.com/v1/bulk/report-exposures	`Failed to load resource: the server responded with a status of 403 ()`

●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

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.tradedoubler.com/brands	Learn More
www.tradedoubler.com/for-publishers	Learn More
www.tradedoubler.com/privacy-policy#cookies	Learn more
www.tradedoubler.com/privacy-policy#cookies	Learn more
www.tradedoubler.com/privacy-policy#cookies	Learn more

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

○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 are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Results for https://tradedoubler.com

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Speed (2)

Trust (2)

Navigation (3)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Payback period

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Contrast

Names and labels

Best Practices

General

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Contrast

Names and labels

Best practices

Best Practices

General

SEO

Content Best Practices

Keyboard Shortcuts