Skip to content
Audit Complete

Results for https://agilent.com

Visit site
Spain Spain · Madrid Completed: Apr 22, 2026 23:53 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

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

Site Health

Score: 74 / 100

Based on 8 categories, 0 sections

Fast site — your users get a smooth experience.

Good foundation, but a few gaps could be exploited.

Several issues make your site difficult for assistive technology users.

Solid SEO basics — a few optimizations could boost rankings.

Solid infrastructure — fast server responses across the board.

Several regulatory requirements are not yet met.

Missing metadata means poor previews on social media and search.

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

Apple · 1227 peers
You 74
·
Avg 72
At average
0 50 100
Better than 58% of Apple sites See full Apple benchmark →
Google Search Console · 3591 peers
You 74
·
Avg 73
At average
0 50 100
Better than 56% of Google Search Console sites See full Google Search Console benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

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

Security › Security Headers
2

HSTS header is missing

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

Security › Security Headers
3

No Content-Security-Policy header found

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

Security › Content Security Policy
4

No <main> landmark found

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

Accessibility › Landmark Structure
5

No favicon or icon links detected

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

Accessibility › Favicon & Branding
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

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%2Fagilent.com)](https://beavercheck.com/results/d07f4f5a-0fc4-42eb-adbc-058e50e4b18b)
<a href="https://beavercheck.com/results/d07f4f5a-0fc4-42eb-adbc-058e50e4b18b"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fagilent.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fagilent.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.
2 accessibility issues exclude users who rely on assistive technology.

Conversion Barriers

1 critical 9 warning

10 barrier(s) likely increasing bounce by ~34%.

Speed (2)

Page loads in 3.7s

+5% bounce

Every additional 100ms above 2.5s costs conversions — you're 1.2s over

Fix: Target <2.5s LCP: defer non-critical scripts and optimize the hero image

High main-thread blocking time

+2% bounce

Page is non-interactive for 213ms after first paint

Fix: Defer third-party scripts and split large bundles

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

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

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

Usability (1)

No viewport meta tag

+15% bounce

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

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

Content (4)

No Open Graph tags

+2% bounce

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

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

No structured data

+2% bounce

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

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

Thin content

+3% bounce

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

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

Content is hard to read

+2% bounce

Graduate-level reading difficulty — limits the addressable audience for product or blog pages

Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60

Navigation (1)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

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

Return on Investment

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

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

Investment

$450

4h · 5 findings

Monthly returns

$2,233 /mo

~$26,793 / year

  • Conversions recovered $2,233
  • Bandwidth savings $0.27

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

$150 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

$450

4.5 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins
$150 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$13,125 / month at risk

~$157,503 / 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

$0.27 /mo

3371.7 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~337 KB per page load
    Saves $0.27/mo

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

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

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

Fix 5 critical issues to capture this value

How this is calculated

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

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

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

Was this report useful?

Thanks for your feedback!

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

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

84
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
93
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
92
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.

1.98 s

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

3.69 s

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

213 ms

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

0.006

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

2.48 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.00 s

Detailed Report

Audit breakdown by category with detailed findings.

84

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.

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.

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-0-IMG
nodeLabel: Agilent Cytation 9 lab instrument beside a monitor displaying a colorful 3D mol…
path: 1,HTML,1,BODY,2,MAIN,0,DIV,0,DIV,0,DIV,0,DIV,0,UL,0,LI,0,DIV,0,DIV,2,DIV,0,PICTURE,3,IMG
selector: div.responsive-media > div.responsive-media__mobile > picture > img
snippet: <img loading="eager" alt="Agilent Cytation 9 lab instrument beside a monitor displaying a colorful 3…" src="https://www.agilent.com/media_17cdb5db8f60377ea9779cfc7c37a9ca00b0d53a9.av…" width="375" height="244" fetchpriority="high">

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

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
Stainless steel bioreactor used in CDMO services. p.button-container > a.agt-link > picture > img
/media_158c4e9d3e071f99c8dc3271557923a72d24d9e28.avif?wid...74.7 KiB73.6 KiB
p.button-container > a.agt-link > picture > img p.button-container > a.agt-link > picture > img
/media_199bad8f3b5667cf5ab053e70175e8812ae9df4e8.avif?wid...38.0 KiB35.6 KiB
1290 Infinity III LC System Photos/System with High-Speed Pump Multisampler MCT… p.button-container > a.agt-link > picture > img
/media_1d6df48f0c8ca659abebbd03a37bddcd074ca0b2e.png?widt...27.6 KiB26.6 KiB
Person in gloves services an instrument. p.button-container > a.agt-link > picture > img
/media_121b2f70f08998bbaa6a0048abc820ecd2bfd45ad.avif?wid...27.7 KiB24.2 KiB
Three small, clear glass vials arranged on a white background. Two vials are st… p.button-container > a.agt-link > picture > img
/media_1bf8619fbd085e3d2f7235c99e3121fc2ca2b03df.png?widt...23.0 KiB22.2 KiB
Pathology stain displayed on a computer monitor screen. p.button-container > a.agt-link > picture > img
/media_120a1f6443f110774fd09ba2a090a67132c63c068.avif?wid...23.2 KiB21.4 KiB
Variety of HPLC columns with a box stating AdvanceBio Family of Bio HPLC columns div.promo-card > p > picture > img
/media_18321fc2bfd656903e7d049263392d9cd9fd2466a.avif?wid...22.8 KiB19.6 KiB
Computer screen showing a data analysis software interface p.button-container > a.agt-link > picture > img
/media_1525e6fdeed4c9a00ff9be452473ef591f750061f.avif?wid...17.6 KiB16.4 KiB
Boxes and glass ampules of Agilent organic chemical standards displayed on a wh… div.promo-card > p > picture > img
/media_1c7afbc188baa2ef8bd50cc7be9471430461e927c.avif?wid...18.6 KiB16.0 KiB
Laboratory setup featuring an Agilent 5900 ICP-OES instrument. p.button-container > a.agt-link > picture > img
/media_1b68c12f03461e217350c040e33ab3c7e06696be5.png?widt...15.9 KiB14.9 KiB
Illustration of a man and woman in white lab coats in a lab setting. div.promo-card > p > picture > img
/media_1e6b08034c69f8d57001969a2e4d6e51fb57db768.avif?wid...17.0 KiB14.6 KiB
div.header__top-bar-cell-one > a.header__logo-link > picture.header__logo-image > img div.header__top-bar-cell-one > a.header__logo-link > picture.header__logo-image > img
/en/shared/media_1a92fff34fea91be153e179e41d714b2b5e185ee...14.8 KiB6.3 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.7 s
URLTime Spent
agilent.com/901 ms
www.agilent.com/774 ms
www.agilent.com/en0.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.

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 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: 150 ms 102.1 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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 Evaluation1.9 s
Other904 ms
Style & Layout525 ms
Rendering139 ms
Parse HTML & CSS99 ms
Garbage Collection58 ms
Script Parsing & Compilation54 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
Internal error.Not actionable

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 5.7 KiB
URLTransfer SizeEst Savings
www.agilent.com/scripts/aem.js16.9 KiB5.7 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 21.0 KiB
URLTransfer SizeEst Savings
21.0 KiB21.0 KiB

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

Layout shift culprits
Optimize DOM size
Font display
Forced reflow
LCP breakdown
Modern HTTP
Render blocking requests
Optimize viewport for mobile
Minify CSS
Avoids enormous network payloads Total size was 1,098 KiB
Avoid long main-thread tasks 10 long tasks found
Image elements have explicit `width` and `height`
Network Requests
Network Round Trip Times 10 ms
Server Backend Latencies 200 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 30 ms
Avoid large layout shifts 3 layout shifts found
INP breakdown
User Timing marks and measures
Avoid non-composited animations
93

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
SPAIN div.header__top-bar > div.header__top-bar-cell-two > div.header__button-with-links > button#langButton
PRODUCTS div.header__top-bar > div.header__top-bar-cell-third > div.header__nav-section > button.header__nav-section-button
APPLICATIONS & INDUSTRIES div.header__top-bar > div.header__top-bar-cell-third > div.header__nav-section > button.header__nav-section-button
TRAINING & EVENTS div.header__top-bar > div.header__top-bar-cell-third > div.header__nav-section > button.header__nav-section-button
SERVICES div.header__top-bar > div.header__top-bar-cell-third > div.header__nav-section > button.header__nav-section-button
SUPPORT & RESOURCES div.header__top-bar > div.header__top-bar-cell-third > div.header__nav-section > button.header__nav-section-button
ORDER CENTER nav#nav > div.header__top-bar > div.header__top-bar-cell-third > a.header__nav-section-button
ABOUT AGILENT div.header__top-bar > div.header__top-bar-cell-third > div.header__button-with-links > button
CONTACT US nav#nav > div.header__top-bar > div.header__top-bar-cell-third > a.header__contact-us
Worldwide Emails div.default-content-wrapper > div.footer__email > p.button-container > a.agt-link
Worldwide Numbers div.default-content-wrapper > div.footer__phone > p.button-container > a.agt-link

These are opportunities to improve the legibility of your content.

Names and labels

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
nav#nav > div.header__top-bar > div.header__top-bar-cell-one > a.header__logo-link nav#nav > div.header__top-bar > div.header__top-bar-cell-one > a.header__logo-link
div.default-content-wrapper > ul > li > a div.default-content-wrapper > ul > li > a

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

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
SPAIN div.header__top-bar > div.header__top-bar-cell-two > div.header__button-with-links > button#langButton
Browse HPLC Columns div.promo-card > p.button-container > strong > a.agt-button
See more div.promo-card > p.button-container > strong > a.agt-button
View the catalog div.promo-card > p.button-container > strong > a.agt-button
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.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
ARIA input fields have accessible names
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[accesskey]` values are unique
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
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.
92

Best Practices

User Experience

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLDisplayed sizeActual sizeExpected size
Shopping cart div.header__top-bar > div.header__top-bar-cell-two > a.header__cart-link > img
www.agilent.com/icons/header/cart.webp24 x 2224 x 2236 x 33

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
failed to load block header TypeError: Cannot read properties of null (reading 'addEventListener') at userIconClick (https://www.agilent.com/blocks/header/header.js:627:18) at Module.decorate (https://www.agilent.com/blocks/header/header.js:753:29) at async https://www.agilent.com/scripts/aem.js:456:11
failed to load module for blocks/header/header TypeError: Cannot read properties of null (reading 'addEventListener') at userIconClick (https://www.agilent.com/blocks/header/header.js:627:18) at Module.decorate (https://www.agilent.com/blocks/header/header.js:753:29) at async https://www.agilent.com/scripts/aem.js:456:11
Failed to load resource: the server responded with a status of 404 ()
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
Page has the HTML doctype
Properly defines charset
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
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

92
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
87
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
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.

658 ms

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

1.05 s

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

48 ms

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

0.029

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

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

1.97 s

Detailed Report

Audit breakdown by category with detailed findings.

92

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
/signals/config/1796800113755229?v=2.9.303&r=stable&domai...1200.0 s117.7 KiB
/termH/pR9g7/GTwS/fCtA/85/pfbakQVaD93w/HSxDCj0C/QTADEyw/N...21600.0 s154.8 KiB
connect.facebook.net/en_US/fbevents.js1200.0 s96.6 KiB
assets.adobedtm.com/e33534db9273/702ed640b08a/launch-7418bb649f52.min.js3600.0 s106.1 KiB
www.agilent.com/chat/js/connect.js0.0 ms9.7 KiB
tags.srv.stackadapt.com/events.js5.0 s7.7 KiB
snap.licdn.com/li.lms-analytics/insight.min.js86400.0 s18.7 KiB
www.agilent.com/akam/13/7b6bf01521600.0 s9.4 KiB
www.agilent.com/cs/agilent_scripts/check-browser-compatibility.js81548.0 s6.1 KiB
/e33534db9273/702ed640b08a/7e7283df10ec/RC04d334246ab0481...3600.0 s2.1 KiB
www.agilent.com/chat/js/asset/css/bot.css0.0 ms1.5 KiB
www.agilent.com/logos/static/powered_by_logo.svg42617.0 s3.0 KiB
/e33534db9273/702ed640b08a/7e7283df10ec/RC0b06d560bc8c482...3600.0 s1.3 KiB
/collect?v=2&fmt=js&pid=1881716&time=1776901987403&url=ht...0.0 ms697 B
/e33534db9273/702ed640b08a/7e7283df10ec/RCcda71fda9631422...3600.0 s725 B
www.agilent.com/cs/agilent_scripts/supported-browser-config.json.js71326.0 s1.3 KiB
/e33534db9273/702ed640b08a/7e7283df10ec/RC7c4a0d4e77c5481...3600.0 s715 B
/e33534db9273/702ed640b08a/7e7283df10ec/RC835e238456e44be...3600.0 s714 B
/e33534db9273/702ed640b08a/7e7283df10ec/RC489a501bab544f8...3600.0 s641 B
/e33534db9273/702ed640b08a/7e7283df10ec/RCee9bb333b7b9406...3600.0 s623 B
/e33534db9273/702ed640b08a/7e7283df10ec/RC30f965364eaa49d...3600.0 s566 B
/e33534db9273/702ed640b08a/7e7283df10ec/RC95ffccb72f894d6...3600.0 s554 B
/e33534db9273/702ed640b08a/7e7283df10ec/RCa380f638b67046c...3600.0 s535 B
www.agilent.com/cs/agilent_scripts/ot-banner.js80106.0 s929 B
/e33534db9273/702ed640b08a/7e7283df10ec/RCf52683a20349453...3600.0 s466 B
/e33534db9273/702ed640b08a/7e7283df10ec/RC252a77b4f50b41e...3600.0 s464 B
www.agilent.com/cs/agilent_scripts/supported-browser.json.js25605.0 s548 B
www.agilent.com/cs/agilent_scripts/target-prehiding-aem.js29582.0 s357 B

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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-0-IMG
nodeLabel: Agilent Cytation 9 lab instrument beside a monitor displaying a colorful 3D mol…
path: 1,HTML,1,BODY,2,MAIN,0,DIV,0,DIV,0,DIV,0,DIV,0,UL,0,LI,0,DIV,0,DIV,0,DIV,0,PICTURE,3,IMG
selector: div.responsive-media > div.responsive-media__desktop > picture > img
snippet: <img loading="eager" alt="Agilent Cytation 9 lab instrument beside a monitor displaying a colorful 3…" src="https://www.agilent.com/media_15b06ce0f5e0623620b00c5607c628c41015e70b6.av…" width="1668" height="500" fetchpriority="high">

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

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
Stainless steel bioreactor used in CDMO services. p.button-container > a.agt-link > picture > img
/media_158c4e9d3e071f99c8dc3271557923a72d24d9e28.avif?wid...287.6 KiB287.4 KiB
p.button-container > a.agt-link > picture > img p.button-container > a.agt-link > picture > img
/media_199bad8f3b5667cf5ab053e70175e8812ae9df4e8.avif?wid...112.4 KiB111.6 KiB
1290 Infinity III LC System Photos/System with High-Speed Pump Multisampler MCT… p.button-container > a.agt-link > picture > img
/media_1d6df48f0c8ca659abebbd03a37bddcd074ca0b2e.png?widt...94.2 KiB93.9 KiB
Three small, clear glass vials arranged on a white background. Two vials are st… p.button-container > a.agt-link > picture > img
/media_1bf8619fbd085e3d2f7235c99e3121fc2ca2b03df.png?widt...87.4 KiB87.2 KiB
Boxes and glass ampules of Agilent organic chemical standards displayed on a wh… div.promo-card > p > picture > img
/media_1c7afbc188baa2ef8bd50cc7be9471430461e927c.avif?wid...72.7 KiB72.4 KiB
Laboratory setup featuring an Agilent 5900 ICP-OES instrument. p.button-container > a.agt-link > picture > img
/media_1b68c12f03461e217350c040e33ab3c7e06696be5.png?widt...55.5 KiB55.2 KiB
Variety of HPLC columns with a box stating AdvanceBio Family of Bio HPLC columns div.promo-card > p > picture > img
/media_18321fc2bfd656903e7d049263392d9cd9fd2466a.avif?wid...53.3 KiB53.0 KiB
Computer screen showing a data analysis software interface p.button-container > a.agt-link > picture > img
/media_1525e6fdeed4c9a00ff9be452473ef591f750061f.avif?wid...47.6 KiB47.2 KiB
Illustration of a man and woman in white lab coats in a lab setting. div.promo-card > p > picture > img
/media_1e6b08034c69f8d57001969a2e4d6e51fb57db768.avif?wid...40.9 KiB40.7 KiB
Gas chromatograph/mass spectrometry instrument with autosampler, injection towe… p.button-container > a.agt-link > picture > img
/media_1b73979da7a4b22fdd4f9b33ad4271a8b05ac3b64.avif?wid...40.6 KiB40.6 KiB
Person in gloves services an instrument. p.button-container > a.agt-link > picture > img
/media_121b2f70f08998bbaa6a0048abc820ecd2bfd45ad.avif?wid...27.7 KiB26.2 KiB
A blue background featuring four electronic devices—a tablet, smartphone, anoth… p.service__image-wrapper > a > picture > img
/media_14996339d0cfb254d746c9ce5d8c89f095c4ab2bb.avif?wid...30.6 KiB24.9 KiB
Pathology stain displayed on a computer monitor screen. p.button-container > a.agt-link > picture > img
/media_120a1f6443f110774fd09ba2a090a67132c63c068.avif?wid...23.2 KiB22.3 KiB
div.header__top-bar-cell-one > a.header__logo-link > picture.header__logo-image > img div.header__top-bar-cell-one > a.header__logo-link > picture.header__logo-image > img
/en/shared/media_1a92fff34fea91be153e179e41d714b2b5e185ee...14.8 KiB6.3 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Diagnostics

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

Why this matters

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

Learn more

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

Source: Google web.dev / Lighthouse

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
Internal error.Not actionable

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 40.5 KiB
URLTransfer SizeEst Savings
cdnjs.cloudflare.com/ajax/libs/jquery/3.7.1/jquery.js67.9 KiB34.7 KiB
www.agilent.com/scripts/aem.js16.9 KiB5.7 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 18.4 KiB
URLTransfer SizeEst Savings
21.0 KiB18.4 KiB

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

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: 576 ms
URLTime Spent
agilent.com/353 ms
www.agilent.com/223 ms
www.agilent.com/en0.0 ms
Max Potential First Input Delay 120 ms
Time to Interactive 2.0 s
Layout shift culprits
Optimize DOM size
Font display
Forced reflow
LCP breakdown
Modern HTTP
Render blocking requests
Optimize viewport for mobile
Minify CSS
Avoids enormous network payloads Total size was 2,665 KiB
JavaScript execution time 0.8 s
Minimizes main-thread work 1.9 s
Avoid long main-thread tasks 3 long tasks found
Image elements have explicit `width` and `height`
Network Requests
Network Round Trip Times 100 ms
Server Backend Latencies 170 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 20 ms
Avoid large layout shifts 15 layout shifts found
INP breakdown
User Timing marks and measures
Avoid non-composited animations
87

Accessibility

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

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ABOUT AGILENT div.header__top-bar > div.header__top-bar-cell-two > div.header__button-with-links > button
CONTACT US nav#nav > div.header__top-bar > div.header__top-bar-cell-two > a.header__contact-us
SPAIN div.header__top-bar > div.header__top-bar-cell-two > div.header__button-with-links > button#langButton
ACCOUNT div.header__top-bar > div.header__top-bar-cell-two > a.header__login-button > span.account
PRODUCTS div.header__top-bar > div.header__top-bar-cell-third > div.header__nav-section > button.header__nav-section-button
APPLICATIONS & INDUSTRIES div.header__top-bar > div.header__top-bar-cell-third > div.header__nav-section > button.header__nav-section-button
TRAINING & EVENTS div.header__top-bar > div.header__top-bar-cell-third > div.header__nav-section > button.header__nav-section-button
SERVICES div.header__top-bar > div.header__top-bar-cell-third > div.header__nav-section > button.header__nav-section-button
SUPPORT & RESOURCES div.header__top-bar > div.header__top-bar-cell-third > div.header__nav-section > button.header__nav-section-button
ORDER CENTER nav#nav > div.header__top-bar > div.header__top-bar-cell-third > a.header__nav-section-button
Worldwide Emails div.default-content-wrapper > div.footer__email > p.button-container > a.agt-link
Worldwide Numbers div.default-content-wrapper > div.footer__phone > p.button-container > a.agt-link
Cookie Policy div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
Reject All Cookies div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-reject-all-handler
Accept All Cookies div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-accept-btn-handler

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Other sites div.default-content-wrapper > address.footer__address > p > a

These are opportunities to improve the legibility of your content.

Names and labels

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
nav#nav > div.header__top-bar > div.header__top-bar-cell-one > a.header__logo-link nav#nav > div.header__top-bar > div.header__top-bar-cell-one > a.header__logo-link
Agilent Technologies nav#nav > div.header__top-bar > div.header__top-bar-cell-third > a.header__logo-spark
div.default-content-wrapper > ul > li > a div.default-content-wrapper > ul > li > a

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

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
Agilent Technologies nav#nav > div.header__top-bar > div.header__top-bar-cell-third > a.header__logo-spark
Company Information div > ul > li > a
Investor Relations div > ul > li > a
Community Relations div > ul > li > a
Working with Agilent div > ul > li > a
University Relations div > ul > li > a
Literature Library div > ul > li > a
Video Library div > ul > li > a
Events div > ul > li > a
E-Seminars div > ul > li > a
Training Courses div > ul > li > a
E-Newsletters div > ul > li > a
Android Mobile Apps div > ul > li > a
iOS Mobile Apps div > ul > li > a
Buy Online div > ul > li > a
Quick Order div > ul > li > a
My Account div > ul > li > a
My Favorites div > ul > li > a
My Orders div > ul > li > a
Where to Buy div > ul > li > a
Agilent Community div > ul > li > a
Technical Support div > ul > li > a
On-site Services div > ul > li > a
Avida Biomed div > ul > li > a
Biovectra div > ul > li > a
E-MSion div > ul > li > a

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
SPAIN div.header__top-bar > div.header__top-bar-cell-two > div.header__button-with-links > button#langButton
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
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.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
ARIA input fields have accessible names
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Heading elements appear in a sequentially-descending order
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[accesskey]` values are unique
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
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)
A laboratory setting featuring a white microscope with a black eyepiece and adj… div > div.quickorder__media-wrapper > picture > img
/media_11e5e905508fd1a6f45b6e74bb21cfc7d886208ce.avif?wid...611 x 302 (2.02)770 x 373 (2.06)

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
Access to fetch at 'https://cdn.cookielaw.org/logos/static/ot_guard_logo.svg' from origin 'https://www.agilent.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Failed to load resource: net::ERR_FAILED
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
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
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
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