Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
/termH/pR9g7/GTwS/fCtA/85/pfbakQVaD93w/HSxDCj0C/QTADEyw/N...	21600.0 s	154.8 KiB
www.agilent.com/akam/13/7b6bf015	21600.0 s	9.4 KiB
www.agilent.com/cs/agilent_scripts/target-prehiding-aem.js	29599.0 s	357 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,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.

	URL	Resource Size	Est Savings
Stainless steel bioreactor used in CDMO services. `p.button-container > a.agt-link > picture > img`	/media_158c4e9d3e071f99c8dc3271557923a72d24d9e28.avif?wid...	74.7 KiB	73.6 KiB
p.button-container > a.agt-link > picture > img `p.button-container > a.agt-link > picture > img`	/media_199bad8f3b5667cf5ab053e70175e8812ae9df4e8.avif?wid...	38.0 KiB	35.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 KiB	26.6 KiB
Person in gloves services an instrument. `p.button-container > a.agt-link > picture > img`	/media_121b2f70f08998bbaa6a0048abc820ecd2bfd45ad.avif?wid...	27.7 KiB	24.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 KiB	22.2 KiB
Pathology stain displayed on a computer monitor screen. `p.button-container > a.agt-link > picture > img`	/media_120a1f6443f110774fd09ba2a090a67132c63c068.avif?wid...	23.2 KiB	21.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 KiB	19.6 KiB
Computer screen showing a data analysis software interface `p.button-container > a.agt-link > picture > img`	/media_1525e6fdeed4c9a00ff9be452473ef591f750061f.avif?wid...	17.6 KiB	16.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 KiB	16.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 KiB	14.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 KiB	14.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 KiB	6.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

URL	Time Spent
agilent.com/	901 ms
www.agilent.com/	774 ms
www.agilent.com/en	0.0 ms

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 150 ms 102.1 KiB

URL	Transfer Size	Est Savings
www.agilent.com/scripts/coveo/headless/commerce/headless.esm.js	102.3 KiB	73.1 KiB
/termH/pR9g7/GTwS/fCtA/85/pfbakQVaD93w/HSxDCj0C/QTADEyw/N...	154.6 KiB	29.0 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
/termH/pR9g7/GTwS/fCtA/85/pfbakQVaD93w/HSxDCj0C/QTADEyw/N...	1.2 s	1.1 s	41 ms
Unattributable	857 ms	247 ms	0.0 ms
www.agilent.com/blocks/header/header.js	693 ms	158 ms	0.2 ms
www.agilent.com/en	359 ms	18 ms	1.3 ms
www.agilent.com/scripts/aem.js	211 ms	159 ms	0.4 ms
www.agilent.com/akam/13/7b6bf015	145 ms	111 ms	5.8 ms
www.agilent.com/blocks/fragment/fragment.js	85 ms	71 ms	0.1 ms
www.agilent.com/blocks/search/search.js	75 ms	64 ms	0.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.

Category	Time Spent
Script Evaluation	1.9 s
Other	904 ms
Style & Layout	525 ms
Rendering	139 ms
Parse HTML & CSS	99 ms
Garbage Collection	58 ms
Script Parsing & Compilation	54 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
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

URL	Transfer Size	Est Savings
www.agilent.com/scripts/aem.js	16.9 KiB	5.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

URL	Transfer Size	Est Savings
	21.0 KiB	21.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

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.

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.

	URL	Displayed size	Actual size	Expected size
Shopping cart `div.header__top-bar > div.header__top-bar-cell-two > a.header__cart-link > img`	www.agilent.com/icons/header/cart.webp	24 x 22	24 x 22	36 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.

Source	Description
www.agilent.com/scripts/aem.js line 790, col 14	`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`
www.agilent.com/scripts/aem.js line 459, col 16	`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`
www.agilent.com/en-es/placeholders.json	`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

SEO

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

Content Best Practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
www.agilent.com/home/more-countries	More
www.agilent.com/en/product/cell-analysis/cytation-9-orthogonal-cell-analysis	Learn more
www.agilent.com/about/sustainable-lab-solutions/en/index.html	See more
www.agilent.com/about/esg/en	Read more
/en/product/oligo-pools-oligo-gmp-manufacturing/oligonucl...	Read more

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

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`