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

Site Health

Score: 72 / 100

Based on 8 categories, 0 sections

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

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Strong compliance posture across regulations.

Good content signals with minor gaps.

Reasonable footprint with room for optimization.

How is this calculated?

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

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

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

How the composite score is calculated

How you compare

Sanity sites average 74

At average

Better than 23% of Sanity sites See full Sanity benchmark →

Sanity.io sites average 74

At average

Better than 23% of Sanity.io sites See full Sanity.io benchmark →

Top Priorities (5)

Content-Security-Policy 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

Page weighs 15.0 MB (5.0 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget

3 button(s) with no accessible text

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

Accessibility › Link & Button Quality

5 image-only link(s) without alt text

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

Accessibility › Link & Button Quality

View fix priority matrix

Fix Priority Matrix

5 findings

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%2Fbraze.com)](https://beavercheck.com/results/0ca3035b-675f-4451-b385-2e72e4d0b67a)

HTML

<a href="https://beavercheck.com/results/0ca3035b-675f-4451-b385-2e72e4d0b67a"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fbraze.com" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fbraze.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 4.5s 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 4.5s — 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

2 critical 4 warning

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

Speed (2)

Page takes 4.5s to load

+12% bounce

Users abandon at ~3s — you're 2.0s 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

Content (1)

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, …)

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

$600 investment → $3,399/month returns + USD 157,500 risk avoided

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

Investment

$600

6h · 5 findings

Monthly returns

$3,399 /mo

~$40,786 / year

Conversions recovered $3,398
Bandwidth savings $1.26

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

Custom rate

$ /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,515 / 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

+4 more

Bandwidth Waste

$1.26 /mo

15693.6 MB/mo × 0.080 USD/GB

Optimize transfer: save ~1.6 MB per page load
Saves $1.26/mo

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

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue

Current bounce (est.)

After fixes (est.)

Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

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

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

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

Was this report useful?

Thanks for your feedback!

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

Checking for existing audit...

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

100

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.

2.48 s

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

4.51 s

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

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

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

30.80 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

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

Learn more ▾

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

Source: Google web.dev / Lighthouse

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

title: Preconnected origins

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
www.braze.com/_next/static/css/2a290a58f3e16127.css	3.9 KiB
www.braze.com/_next/static/css/6ec5e54ae379e487.css	567 B
www.braze.com/_next/static/css/0208c5d20ea31a74.css	22.9 KiB	300 ms
www.braze.com/_next/static/css/8c505d4c5b522e44.css	687 B

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
js.qualified.com/qualified.js?token=JDB423wPwpJxCWhB	60.0 s	116.4 KiB
assets.qualified.com/packs/media/Inter-SemiBold.fcb100c7.woff2	0.0 ms	103.6 KiB
assets.qualified.com/packs/media/Inter-Regular.f1f0c35b.woff2	0.0 ms	97.2 KiB
cdn.cookielaw.org/scripttemplates/202603.1.0/otBannerSdk.js	86400.0 s	129.9 KiB
/logos/0dd4f746-1f64-4873-a21b-7c3769d0789e/018f78f1-9e82...	86400.0 s	57.3 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js	86400.0 s	9.1 KiB
cdn.cookielaw.org/logos/static/powered_by_logo.svg	86400.0 s	2.6 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
[Homepage EN] BrazeAI SIZZLE `div.flex > div.shrink-0 > div.mask-none > img.size-full`	/_next/image?url=https%3A%2F%2Fcdn.sanity.io%2Fimages%2Fb...	156.3 KiB	137.5 KiB
a man and a woman are sitting next to each other with a bicycle in the backgrou… `div.switchback-image-wrapper > div.flex > div.switchback-entrance > img.size-full`	/_next/image?url=https%3A%2F%2Fcdn.sanity.io%2Fimages%2Fb...	186.0 KiB	129.5 KiB
A phone display an IAM simple survey. `div.switchback-image-wrapper > div.flex > div.switchback-entrance > img.size-full`	/_next/image?url=https%3A%2F%2Fcdn.sanity.io%2Fimages%2Fb...	59.8 KiB	41.4 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

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

URL	Time Spent
braze.com/	880 ms
www.braze.com/	0.0 ms

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: 310 ms 37.6 KiB

URL	Transfer Size	Est Savings
	21.4 KiB	19.0 KiB
www.braze.com/_next/static/css/0208c5d20ea31a74.css	22.7 KiB	18.6 KiB

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

Why this matters

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

Learn more ▾

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

Source: Google web.dev / Lighthouse

Estimated savings: 310 ms 1.3 MiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/destination?id=AW-377070085&cx=c&gtm=4e64f0	143.4 KiB	70.6 KiB
www.googletagmanager.com/gtag/destination?id=AW-442792952&cx=c&gtm=4e64f0	143.4 KiB	70.6 KiB
www.googletagmanager.com/gtag/destination?id=AW-377020443&cx=c&gtm=4e64f0	143.4 KiB	70.6 KiB
www.googletagmanager.com/gtag/destination?id=AW-10807555083&cx=c&gtm=4e64f0	144.6 KiB	70.5 KiB
www.googletagmanager.com/gtag/destination?id=AW-834039424&cx=c&gtm=4e64f0	145.6 KiB	70.4 KiB
www.googletagmanager.com/gtag/js?id=G-KZ5Y9ZLHBH&cx=c&gtm=4e64f0	176.3 KiB	69.7 KiB
cdn.cookielaw.org/scripttemplates/202603.1.0/otBannerSdk.js	129.7 KiB	69.1 KiB
www.googletagmanager.com/gtag/destination?id=AW-10792001175&cx=c&gtm=4e64f0	137.3 KiB	68.6 KiB
www.googletagmanager.com/gtag/js?id=AW-16651568214&cx=c&gtm=4e64f0	145.6 KiB	64.8 KiB
www.googletagmanager.com/gtag/destination?id=DC-10732055&cx=c&gtm=4e64f0	129.2 KiB	64.7 KiB
www.googletagmanager.com/gtag/destination?id=DC-11477521&cx=c&gtm=4e64f0	129.2 KiB	64.7 KiB
www.googletagmanager.com/gtag/destination?id=DC-14616612&cx=c&gtm=4e64f0	129.7 KiB	64.5 KiB
www.googletagmanager.com/gtm.js?id=GTM-W3ZW3HBZ	175.3 KiB	62.7 KiB
www.googletagmanager.com/gtag/js?id=DC-14785063&cx=c&gtm=4e64f0	129.3 KiB	61.6 KiB
www.braze.com/_next/static/chunks/3700.7c0f9a0e997be605.js	65.6 KiB	58.0 KiB
js.qualified.com/qualified.js?token=JDB423wPwpJxCWhB	115.8 KiB	57.5 KiB
www.braze.com/_next/static/chunks/3167-f3f93f6fdaf6cc06.js	62.1 KiB	48.3 KiB
js.qualified.com/packs/js/multimodal_v2-f8a905b1.js	93.6 KiB	47.9 KiB
www.braze.com/_next/static/chunks/7503-7127dcddd7851b33.js	51.7 KiB	42.6 KiB
www.braze.com/_next/static/chunks/1768-5fcb5b1c5c38ad53.js	51.1 KiB	37.9 KiB
www.braze.com/_next/static/chunks/9655-9cf4d6fd682e42b0.js	34.9 KiB	27.2 KiB
www.braze.com/_next/static/chunks/7367-2d92a8ba2de1f430.js	31.0 KiB	25.1 KiB
www.braze.com/_next/static/chunks/1765-5b13eb50492324c5.js	50.3 KiB	25.0 KiB
www.braze.com/_next/static/chunks/7922-78508f6b0e4503ff.js	28.2 KiB	24.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.braze.com/	2.4 s	267 ms	154 ms
Unattributable	1.0 s	142 ms	0.0 ms
www.braze.com/_next/static/chunks/0ee1daaf-04c05354e4ae8146.js	701 ms	330 ms	19 ms
www.googletagmanager.com/gtag/destination?id=AW-10807555083&cx=c&gtm=4e64f0	679 ms	637 ms	34 ms
cdn.cookielaw.org/scripttemplates/202603.1.0/otBannerSdk.js	663 ms	564 ms	53 ms
www.braze.com/_next/static/chunks/2621-3cee99791bf035c9.js	525 ms	492 ms	23 ms
www.googletagmanager.com/gtm.js?id=GTM-W3ZW3HBZ	520 ms	328 ms	59 ms
js.qualified.com/qualified.js?token=JDB423wPwpJxCWhB	448 ms	385 ms	40 ms
www.braze.com/_next/static/chunks/1765-5b13eb50492324c5.js	339 ms	53 ms	22 ms
www.googletagmanager.com/gtag/js?id=G-KZ5Y9ZLHBH&cx=c&gtm=4e64f0	207 ms	164 ms	42 ms
www.googletagmanager.com/gtag/js?id=AW-16651568214&cx=c&gtm=4e64f0	160 ms	114 ms	44 ms
www.googletagmanager.com/gtag/destination?id=AW-377070085&cx=c&gtm=4e64f0	152 ms	115 ms	35 ms
www.googletagmanager.com/gtag/js?id=DC-14785063&cx=c&gtm=4e64f0	150 ms	119 ms	27 ms
www.googletagmanager.com/gtag/destination?id=AW-834039424&cx=c&gtm=4e64f0	143 ms	111 ms	31 ms
www.googletagmanager.com/gtag/destination?id=AW-377020443&cx=c&gtm=4e64f0	142 ms	112 ms	28 ms
www.googletagmanager.com/gtag/destination?id=AW-442792952&cx=c&gtm=4e64f0	141 ms	109 ms	32 ms
www.googletagmanager.com/gtag/destination?id=DC-14616612&cx=c&gtm=4e64f0	139 ms	102 ms	36 ms
www.googletagmanager.com/gtag/destination?id=AW-10792001175&cx=c&gtm=4e64f0	137 ms	109 ms	28 ms
js.qualified.com/packs/js/multimodal_v2-f8a905b1.js	136 ms	102 ms	31 ms
www.googletagmanager.com/gtag/destination?id=DC-10732055&cx=c&gtm=4e64f0	134 ms	106 ms	27 ms
www.googletagmanager.com/gtag/destination?id=DC-11477521&cx=c&gtm=4e64f0	129 ms	100 ms	24 ms
www.braze.com/_next/static/chunks/6324-7f3e526a359eaeb6.js	117 ms	103 ms	13 ms
/_next/static/chunks/app/[locale]/[[...slug]]/layout-0a49...	101 ms	100 ms	0.4 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	4.9 s
Other	2.2 s
Script Parsing & Compilation	973 ms
Style & Layout	791 ms
Rendering	465 ms
Garbage Collection	185 ms
Parse HTML & CSS	90 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 reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages with WebSocket cannot enter back/forward cache.	Pending browser support
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable
Back/forward cache is disabled because WebSocket has been used.	Not actionable

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
assets.qualified.com/packs/js/widget/sandboxed/messenger-9c325980.js	803.4 KiB
/_next/image?url=https%3A%2F%2Fcdn.sanity.io%2Fimages%2Fb...	186.4 KiB
www.googletagmanager.com/gtag/js?id=G-KZ5Y9ZLHBH&cx=c&gtm=4e64f0	176.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-W3ZW3HBZ	175.6 KiB
/_next/image?url=https%3A%2F%2Fcdn.sanity.io%2Fimages%2Fb...	156.7 KiB
www.googletagmanager.com/gtag/js?id=AW-16651568214&cx=c&gtm=4e64f0	145.7 KiB
www.googletagmanager.com/gtag/destination?id=AW-834039424&cx=c&gtm=4e64f0	145.6 KiB
www.googletagmanager.com/gtag/destination?id=AW-10807555083&cx=c&gtm=4e64f0	144.6 KiB
www.googletagmanager.com/gtag/destination?id=AW-377070085&cx=c&gtm=4e64f0	143.5 KiB
www.googletagmanager.com/gtag/destination?id=AW-377020443&cx=c&gtm=4e64f0	143.5 KiB

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

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 5 user timings

●Avoid long main-thread tasks 20 long tasks found

●Avoid non-composited animations 7 animated elements found

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

●Network Requests

●Network Round Trip Times 70 ms

●Server Backend Latencies 120 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
AI assistant `body.__variable_97c7bb > q-focus-sentinel > div`
After AI assistant `body.__variable_97c7bb > q-focus-sentinel > div`
AI assistant, start `div#qualified-multimodal-host > div`
AI assistant, end `div#qualified-multimodal-host > div`

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.

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
Braze Data Platform `div.flex > div.flex > div.text-black > h4`

These are opportunities to improve keyboard navigation in your application.

Best practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Go to slide 1 `div.flex > div.w-full > div.flex > button.relative`
Go to slide 2 `div.flex > div.w-full > div.flex > button.relative`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Braze is a Leader in the 2025 Gartner® Magic Quadrant™ for Multichannel Marketi… `div.slick-track > div.slick-slide > div > a.h-full`
Cookie Policy `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link`

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

●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

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

●Links have a discernible name

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

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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

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

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

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

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

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

○Input buttons have discernible text.

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

○Form elements have associated labels

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

○`[lang]` attributes have a valid value

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

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

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

100

Best Practices

●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 browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Detected JavaScript libraries

SEO

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

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.braze.com/product	Learn More

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

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

100

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.

746 ms

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

1.76 s

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

206 ms

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

0.142

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

2.22 s

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

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

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]

items: [map[node:map[type:text value:Total] score:1e-05] map[node:map[boundingRect:map[bottom:54 height:38 left:67 right:147 top:17 width:80] lhId:page-5-A nodeLabel:Homepage path:1,HTML,1,BODY,2,HEADER,0,NAV,0,A selector:body.__variable_97c7bb > header#site-header > nav#main-nav-container > a.flex snippet:<a data-event-name="Header" data-event-label="Logo" aria-label="Homepage" class="flex shrink-0 grow-0 basis-20 items-center xl:mr-10" href="/"> type:node] score:1e-05 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:54 height:38 left:67 right:147 top:17 width:80] lhId:page-17-IMG nodeLabel:braze path:1,HTML,1,BODY,2,HEADER,0,NAV,0,A,0,IMG selector:header#site-header > nav#main-nav-container > a.flex > img.block snippet:<img alt="braze" loading="lazy" width="100" height="32" decoding="async" data-nimg="1" class="block" style="color:transparent" srcset="/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Flogo.83f6bcb4.png&w=128&q=75 …" src="https://www.braze.com/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Flogo.83f…"> type:node]]] type:subitems]]]

items: [map[node:map[type:text value:Total] score:0.142222] map[score:0.142222 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://assets.qualified.com/packs/media/Inter-roman.var.b2129c00.woff2]]] type:subitems]]]

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

items: [map[reflowTime:5.91 source:map[type:text value:[unattributed]]]]

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
div.w-full > div.animate-trustbar-slide > div.flex > div.shrink-0 `div.w-full > div.animate-trustbar-slide > div.flex > div.shrink-0`	/uploads/5e43334d993d0ebb0e5192e777689df497d9eda77714d89b...	145.3 KiB	145.1 KiB
	/_next/image?url=https%3A%2F%2Fcdn.sanity.io%2Fimages%2Fb...	144.0 KiB	135.9 KiB
	/_next/image?url=https%3A%2F%2Fcdn.sanity.io%2Fimages%2Fb...	134.9 KiB	127.3 KiB
Max `div.w-full > div.animate-trustbar-slide > div.flex > div.shrink-0`	/uploads/2C9CeY55ThqdDZTrgt7Faey2xbrnR5NKuNL2/a664ee85f10...	117.4 KiB	117.2 KiB
[Homepage EN] BrazeAI SIZZLE `div.flex > div.shrink-0 > div.mask-none > img.size-full`	/_next/image?url=https%3A%2F%2Fcdn.sanity.io%2Fimages%2Fb...	71.6 KiB	43.6 KiB
div.w-full > div.animate-trustbar-slide > div.flex > div.shrink-0 `div.w-full > div.animate-trustbar-slide > div.flex > div.shrink-0`	/uploads/3f5b99f0a70a73b19c637b188a921942c1ed4358a0efdd92...	25.3 KiB	25.0 KiB
a man and a woman are sitting next to each other with a bicycle in the backgrou… `div.switchback-image-wrapper > div.flex > div.switchback-entrance > img.size-full`	/_next/image?url=https%3A%2F%2Fcdn.sanity.io%2Fimages%2Fb...	65.4 KiB	15.5 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-2-IMG

nodeLabel: [Homepage EN] BrazeAI SIZZLE

path: 1,HTML,1,BODY,3,MAIN,1,DIV,0,DIV,0,SECTION,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,1,IMG

selector: div.flex > div.shrink-0 > div.mask-none > img.size-full

snippet: <img alt="[Homepage EN] BrazeAI SIZZLE" loading="lazy" width="900" height="900" decoding="async" data-nimg="1" class="size-full object-center transition-all duration-300 object-contain" style="color:transparent" srcset="/_next/image?url=https%3A%2F%2Fcdn.sanity.io%2Fimages%2Fb7pblshe%2Fmarketi…" src="https://www.braze.com/_next/image?url=https%3A%2F%2Fcdn.sanity.io%2Fimages…">

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

title: Preconnected origins

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

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
assets.qualified.com/packs/media/Inter-roman.var.b2129c00.woff2	0.0 ms	222.3 KiB
js.qualified.com/qualified.js?token=JDB423wPwpJxCWhB	60.0 s	116.4 KiB
assets.qualified.com/packs/media/Inter-SemiBold.fcb100c7.woff2	0.0 ms	103.9 KiB
assets.qualified.com/packs/media/Inter-Regular.f1f0c35b.woff2	0.0 ms	96.9 KiB
cdn.cookielaw.org/scripttemplates/202603.1.0/otBannerSdk.js	86400.0 s	129.9 KiB
/logos/0dd4f746-1f64-4873-a21b-7c3769d0789e/018f78f1-9e82...	86400.0 s	57.3 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js	86400.0 s	9.1 KiB
cdn.cookielaw.org/logos/static/powered_by_logo.svg	86400.0 s	2.7 KiB
/a?v=3&t=l&pid=1847101846&rv=64f0&tag_exp=0~115938466~115...	0.0 ms	11 B

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
www.braze.com/_next/static/css/8c505d4c5b522e44.css	646 B
www.braze.com/_next/static/css/0208c5d20ea31a74.css	22.9 KiB
www.braze.com/_next/static/css/2a290a58f3e16127.css	3.9 KiB
www.braze.com/_next/static/css/6ec5e54ae379e487.css	588 B

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

URL	Time Spent
braze.com/	330 ms
www.braze.com/	0.0 ms

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

Element	Layout shift score
	0.142
Homepage `body.__variable_97c7bb > header#site-header > nav#main-nav-container > a.flex`	0.000

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 34.4 KiB

URL	Transfer Size	Est Savings
	21.4 KiB	18.8 KiB
www.braze.com/_next/static/css/0208c5d20ea31a74.css	22.7 KiB	15.7 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 ▾

Source: Google web.dev / Lighthouse

Estimated savings: 130 ms 1.3 MiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/destination?id=AW-377020443&cx=c&gtm=4e64f0	143.4 KiB	70.5 KiB
www.googletagmanager.com/gtag/destination?id=AW-10807555083&cx=c&gtm=4e64f0	144.6 KiB	70.4 KiB
www.googletagmanager.com/gtag/destination?id=AW-442792952&cx=c&gtm=4e64f0	143.4 KiB	70.4 KiB
www.googletagmanager.com/gtag/destination?id=AW-834039424&cx=c&gtm=4e64f0	145.6 KiB	70.0 KiB
www.googletagmanager.com/gtag/destination?id=AW-377070085&cx=c&gtm=4e64f0	143.4 KiB	69.8 KiB
cdn.cookielaw.org/scripttemplates/202603.1.0/otBannerSdk.js	129.7 KiB	69.1 KiB
www.googletagmanager.com/gtag/js?id=G-KZ5Y9ZLHBH&cx=c&gtm=4e64f0	176.3 KiB	69.0 KiB
www.googletagmanager.com/gtag/destination?id=AW-10792001175&cx=c&gtm=4e64f0	137.3 KiB	68.5 KiB
www.googletagmanager.com/gtag/destination?id=DC-11477521&cx=c&gtm=4e64f0	129.2 KiB	64.7 KiB
www.googletagmanager.com/gtag/destination?id=DC-14616612&cx=c&gtm=4e64f0	129.7 KiB	64.5 KiB
www.googletagmanager.com/gtag/js?id=AW-16651568214&cx=c&gtm=4e64f0	145.6 KiB	63.8 KiB
www.googletagmanager.com/gtag/destination?id=DC-10732055&cx=c&gtm=4e64f0	129.3 KiB	63.2 KiB
www.googletagmanager.com/gtm.js?id=GTM-W3ZW3HBZ	175.3 KiB	62.6 KiB
www.googletagmanager.com/gtag/js?id=DC-14785063&cx=c&gtm=4e64f0	129.3 KiB	62.4 KiB
www.braze.com/_next/static/chunks/3700.7c0f9a0e997be605.js	65.5 KiB	58.0 KiB
js.qualified.com/qualified.js?token=JDB423wPwpJxCWhB	115.8 KiB	57.3 KiB
www.braze.com/_next/static/chunks/3167-f3f93f6fdaf6cc06.js	62.1 KiB	48.3 KiB
js.qualified.com/packs/js/multimodal_v2-f8a905b1.js	93.3 KiB	47.8 KiB
www.braze.com/_next/static/chunks/7503-7127dcddd7851b33.js	51.7 KiB	42.6 KiB
www.braze.com/_next/static/chunks/1768-5fcb5b1c5c38ad53.js	51.1 KiB	37.9 KiB
www.braze.com/_next/static/chunks/9655-9cf4d6fd682e42b0.js	34.8 KiB	27.2 KiB
www.braze.com/_next/static/chunks/7367-2d92a8ba2de1f430.js	31.0 KiB	25.1 KiB
www.braze.com/_next/static/chunks/1765-5b13eb50492324c5.js	50.3 KiB	25.0 KiB
www.braze.com/_next/static/chunks/7922-78508f6b0e4503ff.js	28.2 KiB	24.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.braze.com/	809 ms	95 ms	52 ms
Unattributable	414 ms	120 ms	0.0 ms
www.googletagmanager.com/gtm.js?id=GTM-W3ZW3HBZ	202 ms	140 ms	17 ms
cdn.cookielaw.org/scripttemplates/202603.1.0/otBannerSdk.js	184 ms	159 ms	12 ms
www.braze.com/_next/static/chunks/0ee1daaf-04c05354e4ae8146.js	178 ms	93 ms	4.8 ms
www.braze.com/_next/static/chunks/2621-3cee99791bf035c9.js	170 ms	161 ms	3.7 ms
js.qualified.com/qualified.js?token=JDB423wPwpJxCWhB	144 ms	122 ms	8.9 ms
www.googletagmanager.com/gtag/destination?id=AW-10807555083&cx=c&gtm=4e64f0	143 ms	129 ms	11 ms
www.braze.com/_next/static/chunks/1765-5b13eb50492324c5.js	121 ms	21 ms	5.8 ms
www.googletagmanager.com/gtag/js?id=AW-16651568214&cx=c&gtm=4e64f0	118 ms	105 ms	12 ms
js.qualified.com/packs/js/multimodal_v2-f8a905b1.js	74 ms	61 ms	7.4 ms
www.googletagmanager.com/gtag/js?id=G-KZ5Y9ZLHBH&cx=c&gtm=4e64f0	73 ms	58 ms	15 ms
www.googletagmanager.com/gtag/destination?id=DC-10732055&cx=c&gtm=4e64f0	62 ms	51 ms	11 ms
www.googletagmanager.com/gtag/destination?id=AW-442792952&cx=c&gtm=4e64f0	60 ms	50 ms	9.5 ms
www.googletagmanager.com/gtag/destination?id=DC-11477521&cx=c&gtm=4e64f0	54 ms	44 ms	10 ms
www.googletagmanager.com/gtag/destination?id=AW-834039424&cx=c&gtm=4e64f0	53 ms	43 ms	9.6 ms
www.googletagmanager.com/gtag/destination?id=AW-377070085&cx=c&gtm=4e64f0	53 ms	42 ms	11 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.8 s
Other	715 ms
Style & Layout	303 ms
Script Parsing & Compilation	290 ms
Rendering	135 ms
Garbage Collection	51 ms
Parse HTML & CSS	29 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 reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages with WebSocket cannot enter back/forward cache.	Pending browser support
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable
Back/forward cache is disabled because WebSocket has been used.	Not actionable

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
assets.qualified.com/packs/js/widget/sandboxed/messenger-9c325980.js	803.2 KiB
assets.qualified.com/packs/media/Inter-roman.var.b2129c00.woff2	222.3 KiB
www.googletagmanager.com/gtag/js?id=G-KZ5Y9ZLHBH&cx=c&gtm=4e64f0	176.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-W3ZW3HBZ	175.6 KiB
/uploads/5e43334d993d0ebb0e5192e777689df497d9eda77714d89b...	145.7 KiB
www.googletagmanager.com/gtag/js?id=AW-16651568214&cx=c&gtm=4e64f0	145.7 KiB
www.googletagmanager.com/gtag/destination?id=AW-834039424&cx=c&gtm=4e64f0	145.6 KiB
www.googletagmanager.com/gtag/destination?id=AW-10807555083&cx=c&gtm=4e64f0	144.6 KiB
/_next/image?url=https%3A%2F%2Fcdn.sanity.io%2Fimages%2Fb...	144.3 KiB
www.googletagmanager.com/gtag/destination?id=AW-377070085&cx=c&gtm=4e64f0	143.5 KiB

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

●Max Potential First Input Delay 80 ms

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 124 user timings

●Avoid long main-thread tasks 16 long tasks found

●Avoid non-composited animations 3 animated elements found

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

●Network Requests

●Network Round Trip Times 70 ms

●Server Backend Latencies 110 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

Accessibility

ARIA

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
AI assistant `body.__variable_97c7bb > q-focus-sentinel > div`
After AI assistant `body.__variable_97c7bb > q-focus-sentinel > div`
AI assistant, start `div#qualified-multimodal-host > div`
AI assistant, end `div#qualified-multimodal-host > div`

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.

Navigation

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Braze Data Platform `div.flex > div.flex > div.text-black > h4`

These are opportunities to improve keyboard navigation in your application.

Best practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Go to slide 1 `div.flex > div.w-full > div.flex > button.relative`
Go to slide 2 `div.flex > div.w-full > div.flex > button.relative`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Braze is a Leader in the 2025 Gartner® Magic Quadrant™ for Multichannel Marketi… `div.slick-track > div.slick-slide > div > a.h-full`
Cookie Policy `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link`

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

●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

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

●Links have a discernible name

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

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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

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

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

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

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

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

○Input buttons have discernible text.

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

○Form elements have associated labels

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

○`[lang]` attributes have a valid value

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

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

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

100

Best Practices

●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 browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Detected JavaScript libraries

SEO

Content Best Practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
www.braze.com/product	Learn More

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

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

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

Content (1)

Navigation (1)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Payback period

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Navigation

Best practices

Best Practices

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Navigation

Best practices

Best Practices

SEO

Content Best Practices

Keyboard Shortcuts