C — https://on24.com | BeaverCheck Audit

Site Health

Score: 71 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Good foundation, but a few gaps could be exploited.

Several issues make your site difficult for assistive technology users.

Solid SEO basics — a few optimizations could boost rankings.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Missing metadata means poor previews on social media and search.

Lean and efficient — low environmental impact per visit.

How is this calculated?

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

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

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

How the composite score is calculated

How you compare

Cloudflare Bot Management · 302 peers

You 71

Avg 74

At average

0 50 100

Better than 12% of Cloudflare Bot Management sites See full Cloudflare Bot Management benchmark →

HTTP/3 · 855 peers

You 71

Avg 74

At average

0 50 100

Better than 12% of HTTP/3 sites See full HTTP/3 benchmark →

Top Priorities (5)

Content-Security-Policy header is missing

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

Security › Security Headers

HSTS header is missing

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

Security › Security Headers

No Content-Security-Policy header found

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

Security › Content Security Policy

No <main> landmark found

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

Accessibility › Landmark Structure

No favicon or icon links detected

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

Accessibility › Favicon & Branding

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%2Fon24.com)](https://beavercheck.com/results/bd1cd1c7-df20-4260-bea9-aebc1a16d50e)

HTML

<a href="https://beavercheck.com/results/bd1cd1c7-df20-4260-bea9-aebc1a16d50e"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fon24.com" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fon24.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. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

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

2 accessibility issues exclude users who rely on assistive technology.

Conversion Barriers

3 critical 6 warning

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

Speed (2)

Page takes 18.7s to load

+12% bounce

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

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

Page feels frozen for 2.5s

+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

Usability (1)

No viewport meta tag

+15% bounce

Mobile browsers render at desktop width and shrink — text unreadable, tap targets miniature

Fix: Add <meta name="viewport" content="width=device-width, initial-scale=1">

Content (3)

No Open Graph tags

+2% bounce

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

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

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Thin content

+3% bounce

Under 300 words — visitors bounce looking for substance, search engines rank competitors first

Fix: Add a substantive FAQ, product detail, or case-study section

Navigation (1)

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

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

Return on Investment

$450 investment → $0.45/month returns + USD 157,500 risk avoided

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

Investment

$450

4h · 5 findings

Monthly returns

$0.45 /mo

~$5.40 / year

Bandwidth savings $0.45

Regulatory risk avoided

USD 157,500

if kept compliant

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

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

$450

4.5 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins

$150 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

$13,125 / month at risk

~$157,505 / 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
Privacy Policy not detected
CCPA/CPRA: USD 2,500 – USD 7,500
No <main> landmark found
ADA Title III: USD 25,000 – USD 150,000

+2 more

Bandwidth Waste

$0.45 /mo

5620.4 MB/mo × 0.080 USD/GB

Optimize transfer: save ~562 KB per page load
Saves $0.45/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.98 s

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

18.75 s

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

2.50 s

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

0.000

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

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

18.88 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
cdn.cookielaw.org/scripttemplates/202502.1.0/otBannerSdk.js	86400.0 s	114.9 KiB
/signals/config/7150223215068358?v=2.9.303&r=stable&domai...	1200.0 s	44.8 KiB
scripts.clarity.ms/0.8.59/clarity.js	86400.0 s	26.2 KiB
communications.on24.com/rs/848-AHN-047/images/rwts.js	60.0 s	10.2 KiB
cdn.bizible.com/scripts/bizible.js	86400.0 s	25.2 KiB
player.vimeo.com/api/player.js?ver=2.15.0	1800.0 s	9.0 KiB
player.vimeo.com/api/player.js	1800.0 s	9.0 KiB
snap.licdn.com/li.lms-analytics/insight.min.js	86400.0 s	18.7 KiB
/scripttemplates/otSDKStub.js?did=91a3f79f-025e-4891-af24...	86400.0 s	9.1 KiB
script.crazyegg.com/pages/scripts/0070/0386.js	300.0 s	2.7 KiB
/attribution_tracking/conversions/793.js?p=https://www.on...	0.0 ms	2.2 KiB
/logos/88567b1d-ea01-46ec-9c7b-ab089dc20793/a03f4daf-8132...	86400.0 s	4.1 KiB
munchkin.marketo.net/munchkin.js	0.0 ms	1.2 KiB
communications.on24.com/rs/848-AHN-047/images/rw_blindform_tracker.js	60.0 s	1.1 KiB
cdn.cookielaw.org/logos/static/powered_by_logo.svg	86400.0 s	2.5 KiB
communications.on24.com/rs/848-AHN-047/images/VimeoVideoTrackingCode.js	60.0 s	922 B
/collect?v=2&fmt=js&pid=659460&time=1776817120308&li_adsI...	0.0 ms	270 B

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.

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:329.847 label:Time to first byte subpart:timeToFirstByte] map[duration:2205.575 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-H1

nodeLabel: ON24 Announces Integration with LinkedIn® to Drive Next Generation of Event Mar…

path: 1,HTML,1,BODY,6,DIV,0,MAIN,1,SECTION,1,DIV,0,DIV,2,DIV,0,DIV,0,H1

selector: div.slick-slide > div.v3-module__inner > div.v3-anim-hero__slide__text > h1

snippet: <h1>

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

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
/wp-content/cache/min/1/ajax/libs/paginationjs/2.6.0/pagi...	1.8 KiB	493 ms
/wp-content/cache/min/1/wp-content/themes/ON24/dist/asset...	86.9 KiB	2.1 s
/wp-content/cache/min/1/ajax/libs/slick-carousel/1.8.1/sl...	1.2 KiB	493 ms
/wp-content/plugins/sitepress-multilingual-cms/templates/...	1.1 KiB	493 ms
/wp-content/cache/min/1/wp-content/plugins/wp-accessibili...	1.7 KiB

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
Screenshot 2026 02 24 at 7.05.00 PM `div.c-video > div.c-video__iframe-container > div.c-video__lazy > img.c-video__lazy-poster`	/wp-content/uploads/2026/02/Screenshot-2026-02-24-at-7.05...	176.5 KiB	163.4 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: 906 ms

URL	Time Spent
on24.com/	906 ms
www.on24.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 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 102.7 KiB

URL	Transfer Size	Est Savings
/wp-content/cache/min/1/wp-content/themes/ON24/dist/asset...	86.2 KiB	83.2 KiB
	19.8 KiB	19.5 KiB

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

Why this matters

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

Learn more ▾

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

Source: Google web.dev / Lighthouse

Estimated savings: 1.2 s 454.0 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/destination?id=G-EPVQ5FZV49&cx=c&gtm=4e64h1	172.9 KiB	69.6 KiB
cdn.cookielaw.org/scripttemplates/202502.1.0/otBannerSdk.js	114.8 KiB	64.8 KiB
www.googletagmanager.com/gtag/js?id=G-3BPFZFSGR0&cx=c&gtm=4e64h1	157.8 KiB	61.8 KiB
www.googletagmanager.com/gtm.js?id=GTM-NKPS2G	180.2 KiB	60.1 KiB
www.googletagmanager.com/gtag/js?id=AW-1069574889&cx=c&gtm=4e64h1	143.6 KiB	56.0 KiB
www.googletagmanager.com/gtag/js?id=DC-9855888	129.8 KiB	54.2 KiB
connect.facebook.net/en_US/fbevents.js	96.5 KiB	33.6 KiB
/pages/versioned/commontransformations-scripts/df70602680...	71.7 KiB	33.0 KiB
code.jquery.com/jquery-3.6.0.min.js?ver=3.6.0	30.2 KiB	20.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	1.4 s	204 ms	0.0 ms
www.googletagmanager.com/gtm.js?id=GTM-NKPS2G	952 ms	856 ms	60 ms
www.on24.com/	920 ms	216 ms	19 ms
www.googletagmanager.com/gtag/js?id=G-3BPFZFSGR0&cx=c&gtm=4e64h1	855 ms	795 ms	45 ms
/pages/versioned/commontransformations-scripts/df70602680...	508 ms	445 ms	20 ms
www.googletagmanager.com/gtag/destination?id=G-EPVQ5FZV49&cx=c&gtm=4e64h1	382 ms	323 ms	54 ms
scripts.clarity.ms/0.8.59/clarity.js	257 ms	191 ms	7.9 ms
cdn.cookielaw.org/scripttemplates/202502.1.0/otBannerSdk.js	243 ms	172 ms	52 ms
/signals/config/7150223215068358?v=2.9.303&r=stable&domai...	217 ms	161 ms	18 ms
www.googletagmanager.com/gtag/js?id=AW-1069574889&cx=c&gtm=4e64h1	216 ms	168 ms	46 ms
connect.facebook.net/en_US/fbevents.js	192 ms	144 ms	47 ms
j.6sc.co/6si.min.js	190 ms	150 ms	6.6 ms
www.googletagmanager.com/gtag/js?id=DC-9855888	186 ms	139 ms	35 ms
cdn.bizible.com/scripts/bizible.js	183 ms	165 ms	9.6 ms
snap.licdn.com/li.lms-analytics/insight.min.js	114 ms	86 ms	21 ms
/pages/versioned/tracking-scripts/158692313dc4b9f2e28d9e9...	109 ms	96 ms	11 ms
code.jquery.com/jquery-3.6.0.min.js?ver=3.6.0	106 ms	62 ms	25 ms
static.ads-twitter.com/uwt.js	97 ms	91 ms	4.4 ms
communications.on24.com/rs/848-AHN-047/images/rwts.js	77 ms	70 ms	7.4 ms
/scripttemplates/otSDKStub.js?did=91a3f79f-025e-4891-af24...	77 ms	62 ms	2.6 ms
/wp-content/cache/min/1/wp-content/themes/ON24/dist/asset...	71 ms	0.0 ms	0.0 ms
munchkin.marketo.net/165/munchkin.js	55 ms	14 ms	32 ms
script.crazyegg.com/pages/scripts/0070/0386.js	52 ms	40 ms	0.9 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	5.8 s
Other	1.4 s
Script Parsing & Compilation	546 ms
Parse HTML & CSS	399 ms
Style & Layout	330 ms
Garbage Collection	177 ms
Rendering	25 ms

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
Personalize Scale `li.v3-cards-and-bullets__col > div.v3-card__icon > picture.fly-picture > img.fly-picture__img`	www.on24.com/wp-content/uploads/2025/07/Personalize_Scale.svg

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

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●User Timing marks and measures 17 user timings

●Avoid long main-thread tasks 20 long tasks found

●Page didn't prevent back/forward cache restoration

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

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

○Avoid large layout shifts

Accessibility

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

ARIA

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ON24 Announces Integration with LinkedIn® to Drive Next Generation of Event Mar… `div#page-container > main#v3-modules > section#v3-anim-hero-19 > div.v3-anim-hero__slick`

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.v3-module__inner > div.v3-htwm__tabs > nav.v3-htwm__tabs__nav > select.v3-htwm__tabs__nav__mobile-dropdown `div.v3-module__inner > div.v3-htwm__tabs > nav.v3-htwm__tabs__nav > select.v3-htwm__tabs__nav__mobile-dropdown`

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.c-video > div.c-video__iframe-container > div.c-video__lazy > a.c-video__lazy-play `div.c-video > div.c-video__iframe-container > div.c-video__lazy > a.c-video__lazy-play`
div.c-video > div.c-video__iframe-container > div.c-video__lazy > a.c-video__lazy-play `div.c-video > div.c-video__iframe-container > div.c-video__lazy > a.c-video__lazy-play`

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
footer.footer > div.footer-row > div.footer-misc-links > ul `footer.footer > div.footer-row > div.footer-misc-links > ul`

These are opportunities to improve the experience of reading tabular or list data using 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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

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

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

●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

○Elements with `role="dialog"` or `role="alertdialog"` 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

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

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

○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

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
AttributionReporting	snap.licdn.com/li.lms-analytics/insight.min.js

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.on24.com/	`Failed to find a valid digest in the 'integrity' attribute for resource 'https://player.vimeo.com/api/player.js?ver=2.15.0' with computed SHA-256 integrity 'uF4awf3XMGV+RExBccE4vxZDCtxbaXJx++b06Mj+wl0='. The resource has been blocked.`
www.on24.com/wp-content/themes/ON24/images/v3/form-select-chevron.svg	`Failed to load resource: the server responded with a status of 404 ()`
	ReferenceError: MktoForms2 is not defined at <anonymous>:1:292 at <anonymous>:2:56 at https://www.googletagmanager.com/gtm.js?id=GTM-NKPS2G:983:429 at uR (https://www.googletagmanager.com/gtm.js?id=GTM-NKPS2G:985:31) at Md.tR (https://www.googletagmanager.com/gtm.js?id=GTM-NKPS2G:982:92) at Md.<anonymous> (https://www.googletagmanager.com/gtm.js?id=GTM-NKPS2G:371:187) at k.apply (https://www.googletagmanager.com/gtm.js?id=GTM-NKPS2G:297:466) at fb (https://www.googletagmanager.com/gtm.js?id=GTM-NKPS2G:260:719) at eb (https://www.googletagmanager.com/gtm.js?id=GTM-NKPS2G:260:470) at Md.<anonymous> (https://www.googletagmanager.com/gtm.js?id=GTM-NKPS2G:321:473)
communications.on24.com/rs/848-AHN-047/images/rw_blindform_tracker.js line 1, col 0	`Uncaught ReferenceError: MktoForms2 is not defined`

●Uses HTTPS

●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

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

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.on24.com/press-releases/cvent-closes-acquisition-of-on24/	Read more
www.on24.com/platform/on24-linkedin-integration/?utm_cta=home-hero	LEARN MORE
www.on24.com/platform/on24-ai-propel-plus/?utm_cta=home-hero	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

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○robots.txt is valid

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

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

1.27 s

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

225 ms

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

0.022

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

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

4.39 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
cdn.cookielaw.org/scripttemplates/202502.1.0/otBannerSdk.js	86400.0 s	114.9 KiB
/signals/config/7150223215068358?v=2.9.303&r=stable&domai...	1200.0 s	44.8 KiB
scripts.clarity.ms/0.8.59/clarity.js	86400.0 s	26.2 KiB
cdn.bizible.com/scripts/bizible.js	86400.0 s	25.2 KiB
communications.on24.com/rs/848-AHN-047/images/rwts.js	60.0 s	10.1 KiB
player.vimeo.com/api/player.js?ver=2.15.0	1800.0 s	9.0 KiB
player.vimeo.com/api/player.js	1800.0 s	9.0 KiB
snap.licdn.com/li.lms-analytics/insight.min.js	86400.0 s	18.7 KiB
/scripttemplates/otSDKStub.js?did=91a3f79f-025e-4891-af24...	86400.0 s	9.1 KiB
script.crazyegg.com/pages/scripts/0070/0386.js	300.0 s	2.7 KiB
/attribution_tracking/conversions/793.js?p=https://www.on...	0.0 ms	2.2 KiB
/logos/88567b1d-ea01-46ec-9c7b-ab089dc20793/a03f4daf-8132...	86400.0 s	4.1 KiB
munchkin.marketo.net/munchkin.js	0.0 ms	1.2 KiB
communications.on24.com/rs/848-AHN-047/images/rw_blindform_tracker.js	60.0 s	1.2 KiB
cdn.cookielaw.org/logos/static/powered_by_logo.svg	86400.0 s	2.5 KiB
communications.on24.com/rs/848-AHN-047/images/VimeoVideoTrackingCode.js	60.0 s	919 B
/collect?v=2&fmt=js&pid=659460&time=1776817159774&li_adsI...	0.0 ms	271 B
/tr/?id=7150223215068358&ev=PageView&dl=https%3A%2F%2Fwww...	0.0 ms	19 B

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
/wp-content/cache/min/1/ajax/libs/paginationjs/2.6.0/pagi...	1.8 KiB	161 ms
/wp-content/cache/min/1/ajax/libs/slick-carousel/1.8.1/sl...	1.2 KiB	161 ms
/wp-content/cache/min/1/wp-content/themes/ON24/dist/asset...	86.9 KiB	361 ms
/wp-content/plugins/sitepress-multilingual-cms/templates/...	1.1 KiB	161 ms
/wp-content/cache/min/1/wp-content/plugins/wp-accessibili...	1.7 KiB

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
Screenshot 2026 02 24 at 7.05.00 PM `div.c-video > div.c-video__iframe-container > div.c-video__lazy > img.c-video__lazy-poster`	/wp-content/uploads/2026/02/Screenshot-2026-02-24-at-7.05...	176.5 KiB	144.5 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: 363 ms

URL	Time Spent
on24.com/	363 ms
www.on24.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 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: 30 ms 102.4 KiB

URL	Transfer Size	Est Savings
/wp-content/cache/min/1/wp-content/themes/ON24/dist/asset...	86.2 KiB	82.8 KiB
	19.8 KiB	19.6 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
www.on24.com/	556 ms	59 ms	4.1 ms
Unattributable	315 ms	44 ms	0.0 ms
www.googletagmanager.com/gtm.js?id=GTM-NKPS2G	274 ms	244 ms	18 ms
www.googletagmanager.com/gtag/js?id=AW-1069574889&cx=c&gtm=4e64h1	215 ms	202 ms	10 ms
/pages/versioned/commontransformations-scripts/df70602680...	152 ms	138 ms	6.6 ms
www.googletagmanager.com/gtag/destination?id=G-EPVQ5FZV49&cx=c&gtm=4e64h1	131 ms	99 ms	16 ms
scripts.clarity.ms/0.8.59/clarity.js	126 ms	106 ms	4.1 ms
www.googletagmanager.com/gtag/js?id=G-3BPFZFSGR0&cx=c&gtm=4e64h1	84 ms	58 ms	24 ms
/signals/config/7150223215068358?v=2.9.303&r=stable&domai...	69 ms	56 ms	6.0 ms
cdn.cookielaw.org/scripttemplates/202502.1.0/otBannerSdk.js	64 ms	47 ms	12 ms
www.googletagmanager.com/gtag/js?id=DC-9855888	61 ms	46 ms	14 ms
connect.facebook.net/en_US/fbevents.js	56 ms	33 ms	9.1 ms
cdn.bizible.com/scripts/bizible.js	54 ms	49 ms	2.5 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	1.6 s
Other	558 ms
Style & Layout	151 ms
Script Parsing & Compilation	150 ms
Parse HTML & CSS	108 ms
Rendering	50 ms
Garbage Collection	47 ms

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

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/destination?id=G-EPVQ5FZV49&cx=c&gtm=4e64h1	172.9 KiB	69.6 KiB
cdn.cookielaw.org/scripttemplates/202502.1.0/otBannerSdk.js	114.8 KiB	64.8 KiB
www.googletagmanager.com/gtag/js?id=G-3BPFZFSGR0&cx=c&gtm=4e64h1	157.8 KiB	61.6 KiB
www.googletagmanager.com/gtm.js?id=GTM-NKPS2G	180.2 KiB	60.1 KiB
www.googletagmanager.com/gtag/js?id=AW-1069574889&cx=c&gtm=4e64h1	143.6 KiB	56.1 KiB
www.googletagmanager.com/gtag/js?id=DC-9855888	130.0 KiB	54.0 KiB
connect.facebook.net/en_US/fbevents.js	96.5 KiB	34.0 KiB
/pages/versioned/commontransformations-scripts/df70602680...	71.7 KiB	33.0 KiB
code.jquery.com/jquery-3.6.0.min.js?ver=3.6.0	30.2 KiB	20.9 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
Revenue Growth `li.v3-cards-and-bullets__col > div.v3-card__icon > picture.fly-picture > img.fly-picture__img`	www.on24.com/wp-content/uploads/2025/07/Revenue_Growth.svg
Connected Insights `li.v3-cards-and-bullets__col > div.v3-card__icon > picture.fly-picture > img.fly-picture__img`	www.on24.com/wp-content/uploads/2025/07/Connected-Insights.svg
Continuous Engagement `li.v3-cards-and-bullets__col > div.v3-card__icon > picture.fly-picture > img.fly-picture__img`	www.on24.com/wp-content/uploads/2025/07/Continuous_Engagement.svg
Personalize Scale `li.v3-cards-and-bullets__col > div.v3-card__icon > picture.fly-picture > img.fly-picture__img`	www.on24.com/wp-content/uploads/2025/07/Personalize_Scale.svg

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

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●User Timing marks and measures 17 user timings

●Avoid long main-thread tasks 7 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 80 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 180 ms

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

Accessibility

ARIA

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ON24 Announces Integration with LinkedIn® to Drive Next Generation of Event Mar… `div#page-container > main#v3-modules > section#v3-anim-hero-19 > div.v3-anim-hero__slick`

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
Introducing ON24 AI Propel+ `div.v3-module__inner > div.v3-anim-hero__indicators__row > div.v3-anim-hero__indicators__indicator > h3`
Scale AI-powered campaigns from one event, instantly. `div.v3-module__inner > div.v3-anim-hero__indicators__row > div.v3-anim-hero__indicators__indicator > p`
Propel Pipeline and drive 3X More Meetings with AI `div.v3-module__inner > div.v3-anim-hero__indicators__row > div.v3-anim-hero__indicators__indicator > h3`
Accelerate pipeline with AI-powered customer journeys. `div.v3-module__inner > div.v3-anim-hero__indicators__row > div.v3-anim-hero__indicators__indicator > p`
AI That Lifts Digital Engagement for Advisors `div.v3-module__inner > div.v3-anim-hero__indicators__row > div.v3-anim-hero__indicators__indicator > h3`
Deepen advisor and client relations with AI engagement `div.v3-module__inner > div.v3-anim-hero__indicators__row > div.v3-anim-hero__indicators__indicator > p`
Increase HCP Impact With Intelligent AI `div.v3-module__inner > div.v3-anim-hero__indicators__row > div.v3-anim-hero__indicators__indicator > h3`
Boost HCP engagement with  AI-driven experiences. `div.v3-module__inner > div.v3-anim-hero__indicators__row > div.v3-anim-hero__indicators__indicator > p`

These are opportunities to improve the legibility of your content.

Navigation

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Announcing ON24 + LinkedIn Integration `div.v3-module__inner > div.v3-anim-hero__indicators__row > div.v3-anim-hero__indicators__indicator > h3`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.c-video > div.c-video__iframe-container > div.c-video__lazy > a.c-video__lazy-play `div.c-video > div.c-video__iframe-container > div.c-video__lazy > a.c-video__lazy-play`
div.c-video > div.c-video__iframe-container > div.c-video__lazy > a.c-video__lazy-play `div.c-video > div.c-video__iframe-container > div.c-video__lazy > a.c-video__lazy-play`

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.footer-row > div.footer-info > div.footer-misc-links > ul `div.footer-row > div.footer-info > div.footer-misc-links > ul`

These are opportunities to improve the experience of reading tabular or list data using 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
div.menu-resources-container > ul#menu-resources > li#menu-item-267306 > a `div.menu-resources-container > ul#menu-resources > li#menu-item-267306 > a`
div.menu-customers-container > ul#menu-customers > li#menu-item-266562 > a `div.menu-customers-container > ul#menu-customers > li#menu-item-266562 > a`
div.menu-customers-container > ul#menu-customers > li#menu-item-266563 > a `div.menu-customers-container > ul#menu-customers > li#menu-item-266563 > a`
div.menu-customers-container > ul#menu-customers > li#menu-item-266564 > a `div.menu-customers-container > ul#menu-customers > li#menu-item-266564 > a`
div.menu-customers-container > ul#menu-customers > li#menu-item-266565 > a `div.menu-customers-container > ul#menu-customers > li#menu-item-266565 > a`
div.menu-customers-container > ul#menu-customers > li#menu-item-266566 > a `div.menu-customers-container > ul#menu-customers > li#menu-item-266566 > a`
div.menu-customers-container > ul#menu-customers > li#menu-item-266567 > a `div.menu-customers-container > ul#menu-customers > li#menu-item-266567 > a`
div.menu-customers-container > ul#menu-customers > li#menu-item-266568 > a `div.menu-customers-container > ul#menu-customers > li#menu-item-266568 > a`
div.menu-customers-container > ul#menu-customers > li#menu-item-266569 > a `div.menu-customers-container > ul#menu-customers > li#menu-item-266569 > a`

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

●Form elements have associated labels

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

●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

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

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

●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

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

○Elements with `role="dialog"` or `role="alertdialog"` 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

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

○Links are distinguishable without relying on color.

○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

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
AttributionReporting	snap.licdn.com/li.lms-analytics/insight.min.js

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.on24.com/	`Failed to find a valid digest in the 'integrity' attribute for resource 'https://player.vimeo.com/api/player.js?ver=2.15.0' with computed SHA-256 integrity 'uF4awf3XMGV+RExBccE4vxZDCtxbaXJx++b06Mj+wl0='. The resource has been blocked.`
	ReferenceError: MktoForms2 is not defined at <anonymous>:1:292 at <anonymous>:2:56 at https://www.googletagmanager.com/gtm.js?id=GTM-NKPS2G:983:429 at uR (https://www.googletagmanager.com/gtm.js?id=GTM-NKPS2G:985:31) at Md.tR (https://www.googletagmanager.com/gtm.js?id=GTM-NKPS2G:982:92) at Md.<anonymous> (https://www.googletagmanager.com/gtm.js?id=GTM-NKPS2G:371:187) at k.apply (https://www.googletagmanager.com/gtm.js?id=GTM-NKPS2G:297:466) at fb (https://www.googletagmanager.com/gtm.js?id=GTM-NKPS2G:260:719) at eb (https://www.googletagmanager.com/gtm.js?id=GTM-NKPS2G:260:470) at Md.<anonymous> (https://www.googletagmanager.com/gtm.js?id=GTM-NKPS2G:321:473)
communications.on24.com/rs/848-AHN-047/images/rw_blindform_tracker.js line 1, col 0	`Uncaught ReferenceError: MktoForms2 is not defined`

●Uses HTTPS

●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

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

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.on24.com/press-releases/cvent-closes-acquisition-of-on24/	Read more
www.on24.com/platform/on24-linkedin-integration/?utm_cta=home-hero	LEARN MORE
www.on24.com/platform/on24-ai-propel-plus/?utm_cta=home-hero	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

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○robots.txt is valid

Results for https://on24.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)

Usability (1)

Content (3)

Navigation (1)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Names and labels

Tables and lists

Best Practices

General

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Contrast

Navigation

Names and labels

Tables and lists

Best practices

Best Practices

General

SEO

Content Best Practices

Keyboard Shortcuts