Skip to content
Audit Complete

Results for https://conviva.com

Visit site
United Stated United Stated · New York Completed: Apr 16, 2026 17:53 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

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

Site Health

Score: 73 / 100

Based on 8 categories, 0 sections

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

Good foundation, but a few gaps could be exploited.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Rich content metadata — your pages look great everywhere.

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

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

Top Priorities (5)

1

Content-Security-Policy header is missing

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

Security › Security Headers
2

No Content-Security-Policy header found

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

Security › Content Security Policy
3

Page weighs 14.6 MB (5.4 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
4

12 image-only link(s) without alt text

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

Accessibility › Link & Button Quality
5

2 button(s) with no accessible text

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

Accessibility › Link & Button Quality
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

2

High impact, low effort — start here.

Strategic

3

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fconviva.com)](https://beavercheck.com/results/63a44165-a97b-4f54-9304-6603f0881781)
<a href="https://beavercheck.com/results/63a44165-a97b-4f54-9304-6603f0881781"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fconviva.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fconviva.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 6.4s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

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

Conversion Barriers

3 critical 3 warning

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

Speed (2)

Page takes 6.4s to load

+12% bounce

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

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

Page feels frozen for 2.1s

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

6 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

3 broken link(s) on the page

+5% bounce

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

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

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

Return on Investment

$600 investment → $4,788/month returns + USD 157,500 risk avoided

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

Investment

$600

6h · 5 findings

Monthly returns

$4,788 /mo

~$57,453 / year

  • Conversions recovered $4,786
  • Bandwidth savings $1.35

Regulatory risk avoided

USD 157,500

if kept compliant

  • ADA Title III USD 150,000
  • CCPA/CPRA USD 7,500

Payback period

0 12mo 24mo

$100 — 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

$600

6.0 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins
$100 2 fixes in ~60 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$13,126 / month at risk

~$157,516 / year if left unfixed

Compliance Risk

$157,500

ADA Title IIICCPA/CPRA
  • No privacy policy link detected
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no cookie policy found
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no privacy policy found
    CCPA/CPRA: USD 2,500 – USD 7,500

+5 more

Bandwidth Waste

$1.35 /mo

16832.6 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~1.7 MB per page load
    Saves $1.35/mo

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

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

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

Fix 5 critical issues to capture this value

How this is calculated

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

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

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

Was this report useful?

Thanks for your feedback!

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

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

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

Core Web Vitals

Key metrics that affect user experience.

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

2.83 s

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

6.35 s

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

2.12 s

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

0.035

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

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

27.49 s

Detailed Report

Audit breakdown by category with detailed findings.

42

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.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:64.426 source:map[column:56 line:22324 type:source-location url:https://www.conviva.ai/wp-content/themes/conviva2025/dist/js/site.js?ver=2.0.16 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:193.018 source:map[type:text value:[unattributed]]] map[reflowTime:0.175 source:map[column:53 line:17912 type:source-location url:https://www.conviva.ai/wp-content/themes/conviva2025/dist/js/site.js?ver=2.0.16 urlProvider:network]] map[reflowTime:0.688 source:map[column:30 line:17765 type:source-location url:https://www.conviva.ai/wp-content/themes/conviva2025/dist/js/site.js?ver=2.0.16 urlProvider:network]] map[reflowTime:0.402 source:map[column:51 line:17773 type:source-location url:https://www.conviva.ai/wp-content/themes/conviva2025/dist/js/site.js?ver=2.0.16 urlProvider:network]] map[reflowTime:0.321 source:map[column:45 line:17784 type:source-location url:https://www.conviva.ai/wp-content/themes/conviva2025/dist/js/site.js?ver=2.0.16 urlProvider:network]] map[reflowTime:254.709 source:map[column:49615 line:1 type:source-location url:https://www.conviva.ai/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:1.559 source:map[column:50335 line:1 type:source-location url:https://www.conviva.ai/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:0.525 source:map[column:50393 line:1 type:source-location url:https://www.conviva.ai/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:0.466 source:map[column:50457 line:1 type:source-location url:https://www.conviva.ai/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:36.004 source:map[column:49637 line:1 type:source-location url:https://www.conviva.ai/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:0.605 source:map[column:51395 line:1 type:source-location url:https://www.conviva.ai/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:64.426 source:map[column:38 line:22328 type:source-location url:https://www.conviva.ai/wp-content/themes/conviva2025/dist/js/site.js?ver=2.0.16 urlProvider:network]] map[reflowTime:28.992 source:map[column:292645 line:6 type:source-location url:https://cdn.cookielaw.org/scripttemplates/202511.1.0/otBannerSdk.js urlProvider:network]] map[reflowTime:0.153 source:map[column:292989 line:6 type:source-location url:https://cdn.cookielaw.org/scripttemplates/202511.1.0/otBannerSdk.js urlProvider:network]] map[reflowTime:0.659 source:map[column:27729 line:6 type:source-location url:https://cdn.cookielaw.org/scripttemplates/202511.1.0/otBannerSdk.js urlProvider:network]] map[reflowTime:24.025 source:map[column:280055 line:6 type:source-location url:https://cdn.cookielaw.org/scripttemplates/202511.1.0/otBannerSdk.js urlProvider:network]]]

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
div.grid-x > div.medium-5 > picture > img div.grid-x > div.medium-5 > picture > img
www.conviva.ai/wp-content/uploads/2026/04/SODE-Cover-Mock-1920x1332.png.webp378.0 KiB367.7 KiB
div#slick-slide33 > div.grid-x > div.medium-5 > img div#slick-slide33 > div.grid-x > div.medium-5 > img
www.conviva.ai/wp-content/uploads/2024/12/form-image.png71.2 KiB68.9 KiB
div.cell > div.img-container > picture > img div.cell > div.img-container > picture > img
www.conviva.ai/wp-content/uploads/2026/01/Virgin-Wines-Illustration.png.webp51.5 KiB39.9 KiB
div.medium-4 > div.post-panel > div.featured-image > div.img-container div.medium-4 > div.post-panel > div.featured-image > div.img-container
www.conviva.ai/wp-content/uploads/2026/02/Thumb-2-1024x485.png99.4 KiB18.6 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: 904 ms
URLTime Spent
conviva.com/904 ms
www.conviva.ai/0.0 ms

Diagnostics

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 9.8 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: 300 ms 86.7 KiB
URLTransfer SizeEst Savings
www.conviva.ai/wp-content/themes/conviva2025/dist/css/style.css?ver=6.9.472.8 KiB66.4 KiB
22.6 KiB20.2 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Style & Layout6.7 s
Other3.8 s
Script Evaluation3.6 s
Script Parsing & Compilation671 ms
Rendering643 ms
Parse HTML & CSS336 ms
Garbage Collection91 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
The page has an unload handler in a sub frame.Actionable

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

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

Learn more

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

Source: Google web.dev / Lighthouse

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
div#slick-slide33 > div.grid-x > div.medium-5 > img div#slick-slide33 > div.grid-x > div.medium-5 > img
www.conviva.ai/wp-content/uploads/2024/12/form-image.png
div#slick-slide31 > div.grid-x > div.medium-5 > img div#slick-slide31 > div.grid-x > div.medium-5 > img
/wp-content/uploads/2024/12/Conviva-Reimagines-Digital-Ex...
div.grid-x > div.cell > div.img-container > img div.grid-x > div.cell > div.img-container > img
www.conviva.ai/wp-content/uploads/2026/02/Frame-95936.svg
div.cell > div.img-container > picture > img div.cell > div.img-container > picture > img
www.conviva.ai/wp-content/uploads/2026/01/Virgin-Wines-Illustration.png.webp
div.grid-x > div.medium-5 > picture > img div.grid-x > div.medium-5 > picture > img
www.conviva.ai/wp-content/uploads/2026/04/SODE-Cover-Mock-1920x1332.png.webp
div#slick-slide32 > div.grid-x > div.medium-5 > img div#slick-slide32 > div.grid-x > div.medium-5 > img
/wp-content/uploads/2024/12/winter-2026_Leader_-Digital-A...
div#onetrust-policy > div#onetrust-policy-text > div.img-container > img div#onetrust-policy > div#onetrust-policy-text > div.img-container > img
www.conviva.com/wp-content/themes/conviva2025/assets/images/conviva-logo.svg
div.grid-x > div.slide-left > div.logo > img div.grid-x > div.slide-left > div.logo > img
www.conviva.ai/wp-content/uploads/2026/02/Group.svg
div.grid-x > div.slide-left > div.logo > img div.grid-x > div.slide-left > div.logo > img
www.conviva.ai/wp-content/uploads/2026/01/Virgin-Wines-Logo.svg
div.grid-x > div.slide-left > div.logo > img div.grid-x > div.slide-left > div.logo > img
www.conviva.ai/wp-content/uploads/2023/06/TelevisaUnivision_logo-1.svg
div.grid-x > div.slide-left > div.logo > img div.grid-x > div.slide-left > div.logo > img
www.conviva.ai/wp-content/uploads/2024/12/Channel-4-Logo.svg

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

Layout shift culprits
Optimize DOM size
LCP breakdown
Modern HTTP
Optimize viewport for mobile
User Timing marks and measures 12 user timings
Avoid long main-thread tasks 20 long tasks found
Avoid non-composited animations 389 animated elements found
Network Requests
Network Round Trip Times 70 ms
Server Backend Latencies 150 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 120 ms
Avoid large layout shifts 7 layout shifts found
INP breakdown
LCP request discovery
87

Accessibility

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

Names and labels

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.top-bar-right > ul.menu > li > button.menu-icon div.top-bar-right > ul.menu > li > button.menu-icon

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#onetrust-policy > div#onetrust-policy-text > div.img-container > img div#onetrust-policy > div#onetrust-policy-text > div.img-container > img

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.grid-container > div.top-bar-left > div.site-branding > a div.grid-container > div.top-bar-left > div.site-branding > a
div.medium-3 > ul.social-icons > li > a div.medium-3 > ul.social-icons > li > a
div.medium-3 > ul.social-icons > li > a div.medium-3 > ul.social-icons > li > a
div.medium-3 > ul.social-icons > li > a div.medium-3 > ul.social-icons > li > a

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

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
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<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
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
`[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
`<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.
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.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
96

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Description
ReferenceError: MktoForms2 is not defined at <anonymous>:1:1 at https://www.googletagmanager.com/gtm.js?id=GTM-KSF5BK8:938:429 at qR (https://www.googletagmanager.com/gtm.js?id=GTM-KSF5BK8:940:31) at Md.pR (https://www.googletagmanager.com/gtm.js?id=GTM-KSF5BK8:937:92) at Md.<anonymous> (https://www.googletagmanager.com/gtm.js?id=GTM-KSF5BK8:333:187) at k.apply (https://www.googletagmanager.com/gtm.js?id=GTM-KSF5BK8:259:466) at fb (https://www.googletagmanager.com/gtm.js?id=GTM-KSF5BK8:222:719) at eb (https://www.googletagmanager.com/gtm.js?id=GTM-KSF5BK8:222:470) at Md.<anonymous> (https://www.googletagmanager.com/gtm.js?id=GTM-KSF5BK8:283:473) at k.apply (https://www.googletagmanager.com/gtm.js?id=GTM-KSF5BK8:259:466)
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 DOM-based XSS with Trusted Types
Detected JavaScript libraries
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
77

SEO

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

Content Best Practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destinationLink Text
www.conviva.com/legal/#Cookie-PolicyMore 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#onetrust-policy > div#onetrust-policy-text > div.img-container > img div#onetrust-policy > div#onetrust-policy-text > div.img-container > img

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

Crawling and Indexing

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
li#menu-item-33443 > ul.vertical > li.js-drilldown-back > a li#menu-item-33443 > ul.vertical > li.js-drilldown-back > a
li#menu-item-35105 > ul.vertical > li.js-drilldown-back > a li#menu-item-35105 > ul.vertical > li.js-drilldown-back > a
li#menu-item-31498 > ul.vertical > li.js-drilldown-back > a li#menu-item-31498 > ul.vertical > li.js-drilldown-back > a
li#menu-item-32007 > ul.vertical > li.js-drilldown-back > a li#menu-item-32007 > ul.vertical > li.js-drilldown-back > a
li#menu-item-32104 > ul.vertical > li.js-drilldown-back > a li#menu-item-32104 > ul.vertical > li.js-drilldown-back > a
li#menu-item-24680 > ul.vertical > li.js-drilldown-back > a li#menu-item-24680 > ul.vertical > li.js-drilldown-back > a
li#menu-item-35107 > ul.vertical > li.js-drilldown-back > a li#menu-item-35107 > ul.vertical > li.js-drilldown-back > a
li#menu-item-35108 > ul.vertical > li.js-drilldown-back > a li#menu-item-35108 > ul.vertical > li.js-drilldown-back > a
li#menu-item-35109 > ul.vertical > li.js-drilldown-back > a li#menu-item-35109 > ul.vertical > li.js-drilldown-back > a
li#menu-item-28416 > ul.vertical > li.js-drilldown-back > a li#menu-item-28416 > ul.vertical > li.js-drilldown-back > 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`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

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

Core Web Vitals

Key metrics that affect user experience. — Desktop

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

898 ms

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

2.72 s

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

105 ms

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

0.007

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

1.45 s

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

5.05 s

Detailed Report

Audit breakdown by category with detailed findings.

81

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.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:66.823 source:map[column:86743 line:2 type:source-location url:https://www.conviva.ai/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 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:114.171 source:map[type:text value:[unattributed]]] map[reflowTime:0.147 source:map[column:53 line:17912 type:source-location url:https://www.conviva.ai/wp-content/themes/conviva2025/dist/js/site.js?ver=2.0.16 urlProvider:network]] map[reflowTime:0.618 source:map[column:30 line:17765 type:source-location url:https://www.conviva.ai/wp-content/themes/conviva2025/dist/js/site.js?ver=2.0.16 urlProvider:network]] map[reflowTime:0.421 source:map[column:51 line:17773 type:source-location url:https://www.conviva.ai/wp-content/themes/conviva2025/dist/js/site.js?ver=2.0.16 urlProvider:network]] map[reflowTime:0.373 source:map[column:45 line:17784 type:source-location url:https://www.conviva.ai/wp-content/themes/conviva2025/dist/js/site.js?ver=2.0.16 urlProvider:network]] map[reflowTime:202.913 source:map[column:49615 line:1 type:source-location url:https://www.conviva.ai/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:1.286 source:map[column:50335 line:1 type:source-location url:https://www.conviva.ai/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:0.42 source:map[column:50393 line:1 type:source-location url:https://www.conviva.ai/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:0.399 source:map[column:50457 line:1 type:source-location url:https://www.conviva.ai/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:19.246 source:map[column:49637 line:1 type:source-location url:https://www.conviva.ai/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:0.584 source:map[column:51395 line:1 type:source-location url:https://www.conviva.ai/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:30.632 source:map[column:292645 line:6 type:source-location url:https://cdn.cookielaw.org/scripttemplates/202511.1.0/otBannerSdk.js urlProvider:network]] map[reflowTime:0.69 source:map[column:292989 line:6 type:source-location url:https://cdn.cookielaw.org/scripttemplates/202511.1.0/otBannerSdk.js urlProvider:network]]]

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
div.grid-x > div.medium-5 > picture > img div.grid-x > div.medium-5 > picture > img
www.conviva.ai/wp-content/uploads/2026/04/SODE-Cover-Mock-1920x1332.png.webp378.0 KiB363.1 KiB
div#slick-slide33 > div.grid-x > div.medium-5 > img div#slick-slide33 > div.grid-x > div.medium-5 > img
www.conviva.ai/wp-content/uploads/2024/12/form-image.png71.2 KiB67.9 KiB
div.cell > div.img-container > picture > img div.cell > div.img-container > picture > img
www.conviva.ai/wp-content/uploads/2026/01/Virgin-Wines-Illustration.png.webp51.5 KiB37.2 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: 358 ms
URLTime Spent
conviva.com/358 ms
www.conviva.ai/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 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: 40 ms 85.1 KiB
URLTransfer SizeEst Savings
www.conviva.ai/wp-content/themes/conviva2025/dist/css/style.css?ver=6.9.472.8 KiB65.6 KiB
22.6 KiB19.5 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Style & Layout1.6 s
Other939 ms
Script Evaluation799 ms
Rendering179 ms
Script Parsing & Compilation166 ms
Parse HTML & CSS79 ms
Garbage Collection39 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
The page has an unload handler in a sub frame.Actionable

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 9.8 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.

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
div#slick-slide33 > div.grid-x > div.medium-5 > img div#slick-slide33 > div.grid-x > div.medium-5 > img
www.conviva.ai/wp-content/uploads/2024/12/form-image.png
div#slick-slide31 > div.grid-x > div.medium-5 > img div#slick-slide31 > div.grid-x > div.medium-5 > img
/wp-content/uploads/2024/12/Conviva-Reimagines-Digital-Ex...
div.swappable-frame > a > div.content-container > img div.swappable-frame > a > div.content-container > img
/wp-content/uploads/2024/12/Conviva-Reimagines-Digital-Ex...
div.cell > div.img-container > picture > img div.cell > div.img-container > picture > img
www.conviva.ai/wp-content/uploads/2026/01/Virgin-Wines-Illustration.png.webp
div.grid-x > div.cell > div.img-container > img div.grid-x > div.cell > div.img-container > img
www.conviva.ai/wp-content/uploads/2026/02/Frame-95936.svg
div.grid-x > div.medium-5 > picture > img div.grid-x > div.medium-5 > picture > img
www.conviva.ai/wp-content/uploads/2026/04/SODE-Cover-Mock-1920x1332.png.webp
div#slick-slide32 > div.grid-x > div.medium-5 > img div#slick-slide32 > div.grid-x > div.medium-5 > img
/wp-content/uploads/2024/12/winter-2026_Leader_-Digital-A...
div#onetrust-policy > div#onetrust-policy-text > div.img-container > img div#onetrust-policy > div#onetrust-policy-text > div.img-container > img
www.conviva.com/wp-content/themes/conviva2025/assets/images/conviva-logo.svg
div.grid-x > div.slide-left > div.logo > img div.grid-x > div.slide-left > div.logo > img
www.conviva.ai/wp-content/uploads/2026/02/Group.svg
div.grid-x > div.slide-left > div.logo > img div.grid-x > div.slide-left > div.logo > img
www.conviva.ai/wp-content/uploads/2026/01/Virgin-Wines-Logo.svg
div.grid-x > div.slide-left > div.logo > img div.grid-x > div.slide-left > div.logo > img
www.conviva.ai/wp-content/uploads/2023/06/TelevisaUnivision_logo-1.svg
div.grid-x > div.slide-left > div.logo > img div.grid-x > div.slide-left > div.logo > img
www.conviva.ai/wp-content/uploads/2024/12/Channel-4-Logo.svg

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

Layout shift culprits
Optimize DOM size
LCP breakdown
Modern HTTP
Optimize viewport for mobile
User Timing marks and measures 12 user timings
JavaScript execution time 0.8 s
Avoid long main-thread tasks 9 long tasks found
Avoid non-composited animations 398 animated elements found
Network Requests
Network Round Trip Times 60 ms
Server Backend Latencies 150 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 110 ms
Avoid large layout shifts 15 layout shifts found
INP breakdown
LCP request discovery
88

Accessibility

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

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.header-container > div.grid-container > div.top-bar-right > a#searchToggle div.header-container > div.grid-container > div.top-bar-right > a#searchToggle

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.

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.swappable-frame > a > div.content-container > img div.swappable-frame > a > div.content-container > img
div#onetrust-policy > div#onetrust-policy-text > div.img-container > img div#onetrust-policy > div#onetrust-policy-text > div.img-container > img

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.grid-container > div.top-bar-left > div.site-branding > a div.grid-container > div.top-bar-left > div.site-branding > a
div.medium-3 > ul.social-icons > li > a div.medium-3 > ul.social-icons > li > a
div.medium-3 > ul.social-icons > li > a div.medium-3 > ul.social-icons > li > a
div.medium-3 > ul.social-icons > li > a div.medium-3 > ul.social-icons > li > a

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

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<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
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
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 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
`<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.
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.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
96

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Description
ReferenceError: MktoForms2 is not defined at <anonymous>:1:1 at https://www.googletagmanager.com/gtm.js?id=GTM-KSF5BK8:938:429 at qR (https://www.googletagmanager.com/gtm.js?id=GTM-KSF5BK8:940:31) at Md.pR (https://www.googletagmanager.com/gtm.js?id=GTM-KSF5BK8:937:92) at Md.<anonymous> (https://www.googletagmanager.com/gtm.js?id=GTM-KSF5BK8:333:187) at k.apply (https://www.googletagmanager.com/gtm.js?id=GTM-KSF5BK8:259:466) at fb (https://www.googletagmanager.com/gtm.js?id=GTM-KSF5BK8:222:719) at eb (https://www.googletagmanager.com/gtm.js?id=GTM-KSF5BK8:222:470) at Md.<anonymous> (https://www.googletagmanager.com/gtm.js?id=GTM-KSF5BK8:283:473) at k.apply (https://www.googletagmanager.com/gtm.js?id=GTM-KSF5BK8:259:466)
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 DOM-based XSS with Trusted Types
Detected JavaScript libraries
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
77

SEO

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

Content Best Practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destinationLink Text
www.conviva.com/legal/#Cookie-PolicyMore 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.swappable-frame > a > div.content-container > img div.swappable-frame > a > div.content-container > img
div#onetrust-policy > div#onetrust-policy-text > div.img-container > img div#onetrust-policy > div#onetrust-policy-text > div.img-container > img

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

Crawling and Indexing

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
li#menu-item-33443 > ul.vertical > li.js-drilldown-back > a li#menu-item-33443 > ul.vertical > li.js-drilldown-back > a
li#menu-item-35105 > ul.vertical > li.js-drilldown-back > a li#menu-item-35105 > ul.vertical > li.js-drilldown-back > a
li#menu-item-31498 > ul.vertical > li.js-drilldown-back > a li#menu-item-31498 > ul.vertical > li.js-drilldown-back > a
li#menu-item-32007 > ul.vertical > li.js-drilldown-back > a li#menu-item-32007 > ul.vertical > li.js-drilldown-back > a
li#menu-item-32104 > ul.vertical > li.js-drilldown-back > a li#menu-item-32104 > ul.vertical > li.js-drilldown-back > a
li#menu-item-24680 > ul.vertical > li.js-drilldown-back > a li#menu-item-24680 > ul.vertical > li.js-drilldown-back > a
li#menu-item-35107 > ul.vertical > li.js-drilldown-back > a li#menu-item-35107 > ul.vertical > li.js-drilldown-back > a
li#menu-item-35108 > ul.vertical > li.js-drilldown-back > a li#menu-item-35108 > ul.vertical > li.js-drilldown-back > a
li#menu-item-35109 > ul.vertical > li.js-drilldown-back > a li#menu-item-35109 > ul.vertical > li.js-drilldown-back > a
li#menu-item-28416 > ul.vertical > li.js-drilldown-back > a li#menu-item-28416 > ul.vertical > li.js-drilldown-back > 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`

Send Feedback