Skip to content
Audit Complete

Results for https://datadoghq.com

Visit site
Blog / Content Tracking: engaged readers
Netherlands Netherlands · Amsterdam Completed: Apr 16, 2026 18:15 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

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

Site Health

Score: 76 / 100

Based on 8 categories, 0 sections

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

Good foundation, but a few gaps could be exploited.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Rich content metadata — your pages look great everywhere.

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

How is this calculated?

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

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

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

How the composite score is calculated

How you compare

Alpine.js sites average 81
At average
Better than 33% of Alpine.js sites See full Alpine.js benchmark →
Amazon Route 53 sites average 72
At average
Better than 81% of Amazon Route 53 sites See full Amazon Route 53 benchmark →

Top Priorities (5)

1

1 image-only link(s) without alt text

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

Accessibility › Link & Button Quality
2

2 button(s) with no accessible text

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

Accessibility › Link & Button Quality
3

2 image(s) missing alt attribute

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

Accessibility › Alt Text Quality
4

is missing width/height — may cause layout shift

Performance issues directly impact user engagement and conversion rates.

Performance › Image Optimization
5

177 third-party resources (100% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

0

High impact, low effort — start here.

Nothing in this quadrant — good news.

Strategic

5

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fdatadoghq.com)](https://beavercheck.com/results/6d84b63e-6cc0-4d93-a1a7-4c731f489456)
<a href="https://beavercheck.com/results/6d84b63e-6cc0-4d93-a1a7-4c731f489456"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fdatadoghq.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fdatadoghq.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 18.8s exceeds Google's 2.5s 'Good' threshold and the 2 performance issues below directly contribute 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 audience reach.

3 accessibility issues exclude users who rely on assistive technology.
Your LCP is 18.8s — fixing the 2 performance criticals could bring it under Google's 2.5s 'Good' threshold.

Conversion Barriers

3 critical 2 warning

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

Speed (2)

Page takes 18.8s to load

+12% bounce

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

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

Page feels frozen for 3.9s

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

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

Trust (1)

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Navigation (2)

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

3 broken link(s) on the page

+5% bounce

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

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

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

Return on Investment

$850 investment → $0.96/month returns + USD 157,500 risk avoided

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

Investment

$850

8h · 5 findings

Monthly returns

$0.96 /mo

~$12 / year

  • Bandwidth savings $0.96

Regulatory risk avoided

USD 157,500

if kept compliant

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

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

$850

8.5 developer hours at $100/hr

Based on United States rates ($100/hr)

Cost by category

Cost by effort level

Adjust assumptions
$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$13,126 / month at risk

~$157,512 / 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
  • 3 advertising/retargeting trackers detected
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no cookie policy found
    CCPA/CPRA: USD 2,500 – USD 7,500

+11 more

Bandwidth Waste

$0.96 /mo

11990.3 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~1.2 MB per page load
    Saves $0.96/mo

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

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

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

Fix 3 critical issues to capture this value

How this is calculated

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

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

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

Was this report useful?

Thanks for your feedback!

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

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

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

Core Web Vitals

Key metrics that affect user experience.

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

6.42 s

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

18.76 s

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

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

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

22.73 s

Detailed Report

Audit breakdown by category with detailed findings.

26

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.

RequestCache TTLTransfer Size
transcend-cdn.com/cm/dc241cd4-6477-4f2b-86c0-6bcb51869e28/ui.js60.0 s98.7 KiB
connect.facebook.net/en_US/fbevents.js1200.0 s96.4 KiB
transcend-cdn.com/cm/dc241cd4-6477-4f2b-86c0-6bcb51869e28/airgap.js60.0 s55.0 KiB
lp.datadoghq.com/js/forms2/js/forms2.min.js14400.0 s67.5 KiB
/signals/config/2233705693599817?v=2.9.298&r=stable&domai...1200.0 s46.8 KiB
www.redditstatic.com/ads/pixel.js60.0 s19.0 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
tag.demandbase.com/705a93ad66faead7.min.js3600.0 s18.3 KiB
tlzqr.datadoghq.com/load1500.0 s13.7 KiB
s.yimg.jp/images/listing/tool/cv/ytag.js600.0 s11.8 KiB
ml314.com/tag.aspx?16320263600.0 s12.7 KiB
a.quora.com/qevents.js14400.0 s14.7 KiB
nexus.ensighten.com/choozle/17899/Bootstrap.js300.0 s9.8 KiB
snap.licdn.com/li.lms-analytics/insight.min.js86400.0 s18.7 KiB
cdn.cr-relay.com/v1/site/a5d49f07-b6b8-4458-bfc0-d11e773eae89/signals.js3600.0 s7.2 KiB
transcend-cdn.com/cm/dc241cd4-6477-4f2b-86c0-6bcb51869e28/cm.css60.0 s4.1 KiB
www.influ2.com/tracker?clid=d0432e0c-03f7-481a-be93-582d8e11bede0.0 ms2.6 KiB
/index.php/form/getForm?munchkinId=875-UVY-685&form=2029&...0.0 ms2.5 KiB
lp.datadoghq.com/js/forms2/css/forms2.css14400.0 s2.7 KiB
munchkin.marketo.net/munchkin.js0.0 ms1.2 KiB
/p/vt/?clid=d0432e0c-03f7-481a-be93-582d8e11bede&dt=Cloud...0.0 ms823 B
cdn.zeroclick.ai/scripts/conversion.js3600.0 s980 B
lp.datadoghq.com/js/forms2/css/forms2-theme-shadow.css14400.0 s1.0 KiB
/collect?v=2&fmt=js&pid=74631&time=1776363193901&url=http...0.0 ms695 B
/rp.gif?ts=1776363194100&id=t2_naasd&event=PageVisit&m.it...0.0 ms666 B
cdn.zeroclick.ai/scripts/zc-global-min.js3600.0 s758 B
in.ml314.com/ud.ashx?topiclimit=&cb=1632026&v=2.8.2.2570.0 ms482 B
partners.tremorhub.com/sync?UIDM=9be67bcf-a561-431b-bcb3-d236817f7e5c0.0 ms393 B
/_/ad/d45c4d6ee1c840da8f6a3212618f3e29/pixel?tag=ViewCont...0.0 ms271 B
insight.adsrvr.org/track/pxl/?adv=m5efvfi&ct=0:m4f44i8&fmt=30.0 ms148 B
lp.datadoghq.com/js/forms2/js/forms2.min.js14400.0 s0 B

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:36.371 source:map[column:31326 line:4 type:source-location url:https://lp.datadoghq.com/js/forms2/js/forms2.min.js urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:44.824 source:map[column:29268 line:6 type:source-location url:https://lp.datadoghq.com/js/forms2/js/forms2.min.js urlProvider:network]] map[reflowTime:88.128 source:map[column:29292 line:6 type:source-location url:https://lp.datadoghq.com/js/forms2/js/forms2.min.js urlProvider:network]] map[reflowTime:2.081 source:map[column:1099 line:7 type:source-location url:https://lp.datadoghq.com/js/forms2/js/forms2.min.js urlProvider:network]] map[reflowTime:28.587 source:map[column:9443 line:4 type:source-location url:https://lp.datadoghq.com/js/forms2/js/forms2.min.js urlProvider:network]] map[reflowTime:0.809 source:map[column:29061 line:5 type:source-location url:https://lp.datadoghq.com/js/forms2/js/forms2.min.js urlProvider:network]] map[reflowTime:0.449 source:map[column:30784 line:5 type:source-location url:https://lp.datadoghq.com/js/forms2/js/forms2.min.js urlProvider:network]] map[reflowTime:6.526 source:map[column:9465 line:4 type:source-location url:https://lp.datadoghq.com/js/forms2/js/forms2.min.js urlProvider:network]]]

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
div.tw-flex > div.desktop:tw-col-span-6 > picture.bg > img.w-100 div.tw-flex > div.desktop:tw-col-span-6 > picture.bg > img.w-100
/img/blog/state-of-devsecops/state-of-devsecops-2026/hero...345.5 KiB333.1 KiB
Infrastructure figure.mb-0 > a > picture > img.tw-w-full
/img/home-hostmap-static.png?format=png&auto=format&fit=m...203.5 KiB159.9 KiB
header.intro-header > div.tw-flex > div.section-video > video#datadog-video header.intro-header > div.tw-flex > div.section-video > video#datadog-video
/img/dd-homepage.jpg?width=1700&height=956&fit=crop&forma...99.5 KiB84.1 KiB
join our team div.desktop:tw-col-span-6 > figure.mb-0 > picture > img.tw-w-full
/img/home/careers_desktop.png?format=auto&auto=format&fit...99.1 KiB44.2 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-VIDEO
nodeLabel: header.intro-header > div.tw-flex > div.section-video > video#datadog-video
path: 1,HTML,1,BODY,2,HEADER,0,DIV,1,DIV,0,VIDEO
selector: header.intro-header > div.tw-flex > div.section-video > video#datadog-video
snippet: <video poster="https://corp.dd-static.net/img/dd-homepage.jpg?width=1700&amp;height=956&amp;fit=c…" id="datadog-video" playsinline="" autoplay="" muted="" loop="" preload="auto" data-play="true">

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.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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: 755 ms
URLTime Spent
datadoghq.com/755 ms
www.datadoghq.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: 750 ms 156.3 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

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.

URLTotal CPU TimeScript EvaluationScript Parse
www.redditstatic.com/ads/pixel.js7.2 s6.9 s10 ms
Unattributable2.9 s366 ms0.0 ms
lp.datadoghq.com/js/forms2/js/forms2.min.js1.6 s761 ms80 ms
/assets/search-bar.min.4b3ca96e97ab09bcf2aa2ead13cd9db005...1.3 s1.2 s77 ms
www.googletagmanager.com/gtm.js?id=GTM-WDC8G61.1 s900 ms111 ms
www.datadoghq.com/935 ms199 ms13 ms
www.googletagmanager.com/gtag/js?id=G-KN80RDFSQK&cx=c&gtm=4e64f0826 ms721 ms86 ms
/static/dd-libs.cfc0fc7c8131c38b026e93f283148dccf754cd8d3...622 ms426 ms35 ms
www.googletagmanager.com/gtag/js?id=AW-827913433&cx=c&gtm=4e64f0582 ms450 ms69 ms
cdn.vector.co/pixel.js449 ms411 ms31 ms
/assets/dd-browser-logs-rum.min.c13b7f7393bdb9f7ba21c37dc...420 ms382 ms15 ms
nexus.ensighten.com/choozle/17899/Bootstrap.js363 ms249 ms4.5 ms
transcend-cdn.com/cm/dc241cd4-6477-4f2b-86c0-6bcb51869e28/ui.js347 ms262 ms58 ms
/signals/config/2233705693599817?v=2.9.298&r=stable&domai...308 ms268 ms34 ms
connect.facebook.net/en_US/fbevents.js254 ms197 ms55 ms
cdn.calibermind.com/a.js249 ms208 ms38 ms
transcend-cdn.com/cm/dc241cd4-6477-4f2b-86c0-6bcb51869e28/airgap.js202 ms168 ms28 ms
/assets/alpine.min.9fb7fca9511674131f4a90d5aa06dbaf0fd1b7...162 ms150 ms7.2 ms
tag.demandbase.com/705a93ad66faead7.min.js146 ms131 ms10 ms
static.ads-twitter.com/uwt.js129 ms119 ms7.9 ms
cdn.cr-relay.com/v1/site/a5d49f07-b6b8-4458-bfc0-d11e773eae89/signals.js116 ms108 ms3.0 ms
snap.licdn.com/li.lms-analytics/insight.min.js109 ms98 ms8.6 ms
/choozle/17899/code/e6c979db0633b70f453eade0abb0f8e3.js?c...101 ms96 ms0.8 ms
www.google-analytics.com/analytics.js93 ms84 ms7.7 ms
bat.bing.com/bat.js92 ms76 ms8.2 ms
cdnjs.cloudflare.com/ajax/libs/crypto-js/4.1.1/crypto-js.min.js53 ms44 ms7.5 ms
/assets/home.min.48d76ac3800bfb0a88543e22c7a184a07d11d831...52 ms38 ms13 ms
ml314.com/tag.aspx?163202650 ms41 ms6.1 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.

CategoryTime Spent
Script Evaluation15.6 s
Other2.9 s
Style & Layout1.1 s
Script Parsing & Compilation880 ms
Garbage Collection500 ms
Parse HTML & CSS402 ms
Rendering63 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
join our team div.desktop:tw-col-span-6 > figure.mb-0 > picture > img.tw-w-full
/img/home/careers_desktop.png?format=auto&auto=format&fit...
Infrastructure figure.mb-0 > a > picture > img.tw-w-full
/img/home-hostmap-static.png?format=png&auto=format&fit=m...
div.tw-flex > div.desktop:tw-col-span-6 > picture.bg > img.w-100 div.tw-flex > div.desktop:tw-col-span-6 > picture.bg > img.w-100
/img/blog/state-of-devsecops/state-of-devsecops-2026/hero...
div.footer-menu > span.d-flex > a#transcend-footer-link > img div.footer-menu > span.d-flex > a#transcend-footer-link > img
imgix.datadoghq.com/img/icons/privacyoptions.svg?w=24&dpr=2
Log Management figure.mb-0 > a > picture > img.tw-w-full
APM figure.mb-0 > a > picture > img.tw-w-full
Security Monitoring figure.mb-0 > a > picture > img.tw-w-full
Network Monitoring figure.mb-0 > a > picture > img.tw-w-full
Synthetic Monitoring figure.mb-0 > a > picture > img.tw-w-full
Real User Monitoring figure.mb-0 > a > picture > img.tw-w-full
Serverless figure.mb-0 > a > picture > img.tw-w-full

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

Layout shift culprits
Optimize DOM size
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 5 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 230 ms
Server Backend Latencies 290 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 10 ms
INP breakdown
Avoid non-composited animations
Avoid large layout shifts
98

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.

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
2025 GARTNER® MAGIC QUADRANT™ div.container > div.row > div.text-container > h5

These are opportunities to improve keyboard navigation in your application.

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
SAVE THE DATE div.tw-flex > div.tw-relative > div.tw-relative > a.tw-flex
LEARN MORE div.container > div.row > div.text-container > a.rotating-banner-btn
LEARN MORE div.tw-flex > div.home-blog-bg > div.tw-container > a.tw-flex
LEARN MORE section > div.bg-gray-lightest > div.tw-container > a.tw-flex
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
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links 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
Touch targets have sufficient size and spacing.
Document has a main landmark.
Deprecated ARIA roles were not used
`<video>` elements contain a `<track>` element with `[kind="captions"]`
`[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
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
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
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
73

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
DASH Gradient Background div.tw-absolute > figure.mb-0 > picture > img.tw-w-full
/img/home/dash-gradient.jpg?format=jpg&auto=format&fit=ma...412 x 823 (0.50)850 x 546 (1.56)
Infrastructure div.desktop:tw-absolute > figure.mb-0 > picture > img.tw-w-full
/img/home-hostmap-static.png?format=png&auto=format&fit=m...804 x 416 (1.93)694 x 416 (1.67)
DataDog div.d-none > div > a.js-logo-download > img.bits-logo-lg
/img/dd_logo_n_70x75.png?ch=Width,DPR&fit=max&auto=format...140 x 75 (1.87)140 x 150 (0.93)
DataDog div.d-none > div > a.js-logo-download > img.datadog-text-logo-lg
/img/dd-logo-n-200.png?ch=Width,DPR&fit=max&auto=format&h...186 x 14 (13.29)186 x 28 (6.64)

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 / WarningSource
AttributionReporting

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.

SourceDescription
Failed to load resource: the server responded with a status of 451 ()
ZeroClick Error: No ZeroClick ID found
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
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
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
Use a strong HSTS policy
Mitigate clickjacking with XFO or CSP
92

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.

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

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

Core Web Vitals

Key metrics that affect user experience. — Desktop

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

1.01 s

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

1.92 s

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

340 ms

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

0.327

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

2.40 s

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

5.03 s

Detailed Report

Audit breakdown by category with detailed findings.

54

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.

RequestCache TTLTransfer Size
transcend-cdn.com/cm/dc241cd4-6477-4f2b-86c0-6bcb51869e28/ui.js60.0 s98.8 KiB
connect.facebook.net/en_US/fbevents.js1200.0 s96.4 KiB
transcend-cdn.com/cm/dc241cd4-6477-4f2b-86c0-6bcb51869e28/airgap.js60.0 s55.1 KiB
lp.datadoghq.com/js/forms2/js/forms2.min.js14400.0 s67.5 KiB
/signals/config/2233705693599817?v=2.9.298&r=stable&domai...1200.0 s46.8 KiB
www.redditstatic.com/ads/pixel.js60.0 s19.0 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
tag.demandbase.com/705a93ad66faead7.min.js3600.0 s18.3 KiB
tlzqr.datadoghq.com/load1500.0 s13.7 KiB
s.yimg.jp/images/listing/tool/cv/ytag.js600.0 s11.8 KiB
ml314.com/tag.aspx?16320263600.0 s12.7 KiB
a.quora.com/qevents.js14400.0 s14.8 KiB
nexus.ensighten.com/choozle/17899/Bootstrap.js300.0 s9.8 KiB
snap.licdn.com/li.lms-analytics/insight.min.js86400.0 s18.7 KiB
cdn.cr-relay.com/v1/site/a5d49f07-b6b8-4458-bfc0-d11e773eae89/signals.js3600.0 s7.2 KiB
transcend-cdn.com/cm/dc241cd4-6477-4f2b-86c0-6bcb51869e28/cm.css60.0 s4.1 KiB
www.influ2.com/tracker?clid=d0432e0c-03f7-481a-be93-582d8e11bede0.0 ms2.6 KiB
/index.php/form/getForm?munchkinId=875-UVY-685&form=2029&...0.0 ms2.5 KiB
lp.datadoghq.com/js/forms2/css/forms2.css14400.0 s2.7 KiB
munchkin.marketo.net/munchkin.js0.0 ms1.2 KiB
/p/vt/?clid=d0432e0c-03f7-481a-be93-582d8e11bede&dt=Cloud...0.0 ms842 B
cdn.zeroclick.ai/scripts/conversion.js3600.0 s980 B
lp.datadoghq.com/js/forms2/css/forms2-theme-shadow.css14400.0 s1.0 KiB
/collect?v=2&fmt=js&pid=74631&time=1776363270162&url=http...0.0 ms693 B
/rp.gif?ts=1776363270588&id=t2_naasd&event=PageVisit&m.it...0.0 ms666 B
cdn.zeroclick.ai/scripts/zc-global-min.js3600.0 s758 B
in.ml314.com/ud.ashx?topiclimit=&cb=1632026&v=2.8.2.2570.0 ms482 B
partners.tremorhub.com/sync?UIDM=5db7e926-b123-4811-bc2d-98cd9b8656160.0 ms392 B
/_/ad/d45c4d6ee1c840da8f6a3212618f3e29/pixel?tag=ViewCont...0.0 ms271 B
lp.datadoghq.com/js/forms2/js/forms2.min.js14400.0 s0 B

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:0.326943] map[node:map[boundingRect:map[bottom:1722 height:434 left:0 right:1350 top:1288 width:1350] lhId:page-7-DIV nodeLabel:DASH is Back on June 9-10, 2026 Join thousands of engineers, developers, and s… path:1,HTML,1,BODY,4,DIV selector:body.hydra > div.tw-flex snippet:<div class="tw-flex tw-flex-col tw-overflow-y-clip position-relative desktop:tw-grid d…"> type:node] score:0.324246 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://www.datadoghq.com/fonts/web-fonts/NationalWeb-BookItalic.woff2]]] type:subitems]] map[node:map[boundingRect:map[bottom:365 height:38 left:102 right:1248 top:327 width:1146] lhId:page-6-SPAN nodeLabel:See inside any stack, any app, at any scale, anywhere. path:1,HTML,1,BODY,2,HEADER,0,DIV,0,DIV,1,SPAN selector:header.intro-header > div.tw-flex > div.container > span.tw-block snippet:<span class="tw-block tw-text-subtitle-1--corp-ui tablet:tw-text-24 tablet:tw-leading-2…"> type:node] score:0.001442 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://www.datadoghq.com/fonts/web-fonts/NationalWeb-Book.woff2]]] type:subitems]] map[node:map[boundingRect:map[bottom:117 height:44 left:816 right:883 top:73 width:68] lhId:page-5-A nodeLabel:ABOUT path:1,HTML,1,BODY,1,DIV,0,NAV,0,DIV,0,DIV,2,UL,0,LI,0,A selector:div.d-none > ul.d-flex > li.dropdown > a.dropdown snippet:<a href="https://www.datadoghq.com/about/leadership/" class="dropdown"> type:node] score:0.001255]]

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:30.827 source:map[column:31326 line:4 type:source-location url:https://lp.datadoghq.com/js/forms2/js/forms2.min.js urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:23.459 source:map[column:92042 line:0 type:source-location url:https://www.datadoghq.com/static/dd-libs.cfc0fc7c8131c38b026e93f283148dccf754cd8d3e5ad027ef77c1b84c04d0a7265d7ca94b7475b930ba0e7e179b0ec3e1a73d10d09d79ca3cc6ed6971c09b95.js urlProvider:network]] map[reflowTime:32.318 source:map[type:text value:[unattributed]]] map[reflowTime:22.385 source:map[column:9443 line:4 type:source-location url:https://lp.datadoghq.com/js/forms2/js/forms2.min.js urlProvider:network]] map[reflowTime:1.136 source:map[column:29061 line:5 type:source-location url:https://lp.datadoghq.com/js/forms2/js/forms2.min.js urlProvider:network]] map[reflowTime:0.475 source:map[column:30784 line:5 type:source-location url:https://lp.datadoghq.com/js/forms2/js/forms2.min.js urlProvider:network]] map[reflowTime:6.701 source:map[column:9465 line:4 type:source-location url:https://lp.datadoghq.com/js/forms2/js/forms2.min.js urlProvider:network]] map[reflowTime:0.13 source:map[column:24761 line:6 type:source-location url:https://lp.datadoghq.com/js/forms2/js/forms2.min.js urlProvider:network]]]

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
div.tw-flex > div.desktop:tw-col-span-6 > picture.bg > img.w-100 div.tw-flex > div.desktop:tw-col-span-6 > picture.bg > img.w-100
/img/blog/state-of-devsecops/state-of-devsecops-2026/hero...345.5 KiB334.6 KiB
join our team div.desktop:tw-col-span-6 > figure.mb-0 > picture > img.tw-w-full
/img/home/careers_desktop.png?format=auto&auto=format&fit...231.6 KiB186.9 KiB
header.intro-header > div.tw-flex > div.section-video > video#datadog-video header.intro-header > div.tw-flex > div.section-video > video#datadog-video
/img/dd-homepage.jpg?width=1700&height=956&fit=crop&forma...99.5 KiB54.3 KiB
DASH 2025 div.desktop:tw-col-span-6 > figure.mb-0 > picture > img.tw-w-full
/img/home/post_dash_module_desktop_image.jpg?format=jpg&a...58.2 KiB46.6 KiB
From overview to deep details,&nbsp;fast details.last-of-type:[&_.long-button]:tw-mb-0 > div.desktop:tw-absolute > a.tw-hidden > video.home-product-video
/img/home-hostmap-static.png?w=804&fit=crop&fm=jpg&auto=f...44.5 KiB34.9 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-VIDEO
nodeLabel: header.intro-header > div.tw-flex > div.section-video > video#datadog-video
path: 1,HTML,1,BODY,2,HEADER,0,DIV,1,DIV,0,VIDEO
selector: header.intro-header > div.tw-flex > div.section-video > video#datadog-video
snippet: <video poster="https://corp.dd-static.net/img/dd-homepage.jpg?width=1700&amp;height=956&amp;fit=c…" id="datadog-video" playsinline="" autoplay="" muted="" loop="" preload="auto" data-play="true">

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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: 227 ms
URLTime Spent
datadoghq.com/227 ms
www.datadoghq.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.

ElementLayout shift score
DASH is Back on June 9-10, 2026 Join thousands of engineers, developers, and s… body.hydra > div.tw-flex
0.324
See inside any stack, any app, at any scale, anywhere. header.intro-header > div.tw-flex > div.container > span.tw-block
0.001
ABOUT div.d-none > ul.d-flex > li.dropdown > a.dropdown
0.001

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: 190 ms 154.8 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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation2.1 s
Other617 ms
Style & Layout258 ms
Script Parsing & Compilation229 ms
Parse HTML & CSS114 ms
Garbage Collection56 ms
Rendering42 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
join our team div.desktop:tw-col-span-6 > figure.mb-0 > picture > img.tw-w-full
/img/home/careers_desktop.png?format=auto&auto=format&fit...
div.tw-flex > div.desktop:tw-col-span-6 > picture.bg > img.w-100 div.tw-flex > div.desktop:tw-col-span-6 > picture.bg > img.w-100
/img/blog/state-of-devsecops/state-of-devsecops-2026/hero...
div.footer-menu > span.d-flex > a#transcend-footer-link > img div.footer-menu > span.d-flex > a#transcend-footer-link > img
imgix.datadoghq.com/img/icons/privacyoptions.svg?w=24&dpr=2
DataDog div.d-none > div > a.js-logo-download > img.bits-logo-lg
/img/dd_logo_n_70x75.png?ch=Width,DPR&fit=max&auto=format...

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

Optimize DOM size
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 12 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 260 ms
Server Backend Latencies 290 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 10 ms
INP breakdown
Avoid non-composited animations
91

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.

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
THE FORRESTER WAVE™: AIOPS PLATFORMS div.container > div.row > div.text-container > h5

These are opportunities to improve keyboard navigation in your application.

Names and labels

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Infrastructure details.last-of-type:[&_.long-button]:tw-mb-0 > div.desktop:tw-absolute > figure.mb-0 > a

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

Best practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Search toggle div.d-none > ul.d-flex > li#search-toggle > a.js-search-toggle
Open search bar. ul.d-flex > li#search-toggle > a.js-search-toggle > button
Infrastructure Monitoring div.d-flex > div.footer-menu > span.d-inline-flex > a.d-inline-block
Pricing div.d-flex > div.footer-menu > span.d-inline-flex > a.d-inline-block
Contact Us div.d-flex > div.footer-menu > span.d-inline-flex > a.d-inline-block
The Monitor div.d-flex > div.footer-menu > span.d-inline-flex > a.d-inline-block

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
SAVE THE DATE div.tw-flex > div.tw-relative > div.tw-relative > a.tw-flex
LEARN MORE div.container > div.row > div.text-container > a.rotating-banner-btn
LEARN MORE div.tw-flex > div.home-blog-bg > div.tw-container > a.tw-flex
LEARN MORE section > div.bg-gray-lightest > div.tw-container > a.tw-flex
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
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
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
`<video>` elements contain a `<track>` element with `[kind="captions"]`
`[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
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
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
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
73

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
DASH Gradient Background div.tw-absolute > figure.mb-0 > picture > img.tw-w-full
/img/home/dash-gradient.jpg?format=jpg&auto=format&fit=ma...675 x 940 (0.72)1512 x 974 (1.55)

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 / WarningSource
AttributionReporting

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.

SourceDescription
Failed to load resource: the server responded with a status of 451 ()
ZeroClick Error: No ZeroClick ID found
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
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
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
Use a strong HSTS policy
Mitigate clickjacking with XFO or CSP
92

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.

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`

Send Feedback