Skip to content
https://arubanetworks.com

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

48

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.

RequestCache TTLTransfer Size
www.hpe.com/foElZxJAKex7p/jMzG_EG9k/wU1Yo/1N9JSDVmXmQ4pQ/biVUdhwB/anhxPHkw/E0sB21600.0 s182.9 KiB
www.hpe.com/content/dam/hpe/web-ui/js/hpe-generic-v3.38cac265c5cb.js600.0 s109.1 KiB
www.hpe.com/content/dam/hpe/web-ui/css/hpe-generic-v3.38cac265c5cb.css600.0 s46.0 KiB
cdn-app.pathfactory.com/production/jukebox-lite/current/jukebox.js0.0 ms20.3 KiB
www.hpe.com/content/dam/hpe/web-ui/js/critical-loader.38cac265c5cb.js600.0 s21.5 KiB
/content/dam/hpe/web-ui/js/components/core/esl-carousel.3...600.0 s16.0 KiB
tags.clickagy.com/data.js?rnd=62fe5c0e6ad960.0 ms14.0 KiB
js.adsrvr.org/up_loader.1.1.0.js0.0 ms12.2 KiB
/notice?domain=hpe.com&c=teconsent&gtm=1&country=us&langu...3600.0 s14.2 KiB
/content/dam/hpe/web-ui/js/components/core/media.provider...600.0 s10.7 KiB
/content/dam/hpe/web-ui/js/components/hpe-gn/gn-header-v4...600.0 s8.2 KiB
snap.licdn.com/li.lms-analytics/insight.min.js86400.0 s18.7 KiB
www.hpe.com/akam/13/51ec958521600.0 s9.9 KiB
js.zi-scripts.com/zi-tag.js0.0 ms5.9 KiB
/content/dam/hpe/shared-publishing/images-norend/0xx/02/0...301187.0 s30.7 KiB
www.hpe.com/content/dam/hpe/web-ui/js/components/hpe-share-async.38cac265c5cb.js600.0 s6.1 KiB
s2.go-mpulse.net/boomerang/EP6HW-6SA9L-6GGT5-VM3KF-TQAT9604800.0 s46.0 KiB
/content/dam/hpe/shared-publishing/images-norend/7xx/7295...374496.0 s23.7 KiB
cdn-app.pathfactory.com/production/jukebox-lite/current/307.js0.0 ms3.5 KiB
www.hpe.com/content/dam/hpe/web-ui/js/components/hpe.chat-api.js.38cac265c5cb.js10800.0 s4.5 KiB
/content/dam/hpe/web-ui/js/components/hpe-gn/search-box.3...10800.0 s4.2 KiB
/drift-public-prod/1529779/18046a50c4e28e16187ffe1de56554...0.0 ms2.9 KiB
/content/dam/hpe/shared-publishing/images-norend/screensh...374495.0 s16.4 KiB
/content/dam/hpe/shared-publishing/images-norend/products...374506.0 s16.1 KiB
/content/dam/hpe/web-ui/js/components/core/media.tracker....10800.0 s2.9 KiB
/content/dam/hpe/web-ui/js/components/unicorn/adaptive-ma...10800.0 s1.8 KiB
munchkin.marketo.net/munchkin.js0.0 ms1.2 KiB
js.adsrvr.org/universal_pixel.js0.0 ms957 B
/content/dam/hpe/shared-publishing/images-norend/products...374505.0 s5.6 KiB
/content/dam/hpe/web-ui/js/components/core/media.mixins.3...10800.0 s1.3 KiB
js.adsrvr.org/universal_pixel.js0.0 ms464 B
/collect?v=2&fmt=js&pid=9144&time=1776361161550&li_adsId=...0.0 ms452 B
pixel.everesttech.net/rlsa/134720.0 ms152 B
www.facebook.com/tr?id=656844501156995&ev=PageView&noscript=1&gtmcb=5012954540.0 ms19 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.

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:6.6 source:map[column:21521 line:1 type:source-location url:https://consent.trustarc.com/notice?domain=hpe.com&c=teconsent&gtm=1&country=us&language=en_us&js=nj&noticeType=bb&text=true&pcookie 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:34.171 source:map[column:59586 line:0 type:source-location url:https://www.hpe.com/content/dam/hpe/web-ui/js/critical-loader.38cac265c5cb.js urlProvider:network]] map[reflowTime:44.389 source:map[column:5251 line:0 type:source-location url:https://www.hpe.com/content/dam/hpe/web-ui/js/components/hpe-gn/gn-header-v4.38cac265c5cb.js urlProvider:network]] map[reflowTime:0.574 source:map[column:9685 line:0 type:source-location url:https://www.hpe.com/content/dam/hpe/web-ui/js/components/hpe-gn/gn-header-v4.38cac265c5cb.js urlProvider:network]] map[reflowTime:6.6 source:map[column:26648 line:0 type:source-location url:https://consent.trustarc.com/notice?domain=hpe.com&c=teconsent&gtm=1&country=us&language=en_us&js=nj&noticeType=bb&text=true&pcookie urlProvider:network]] map[reflowTime:1.959 source:map[column:27925 line:0 type:source-location url:https://consent.trustarc.com/notice?domain=hpe.com&c=teconsent&gtm=1&country=us&language=en_us&js=nj&noticeType=bb&text=true&pcookie urlProvider:network]] map[reflowTime:21.456 source:map[column:202424 line:3 type:source-location url:https://www.hpe.com/global/metrics/bootstrap/prod_wsdk.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
Portrait of a business person. div.image-column > div.typo5 > div.img-container > img.io-image
/content/dam/hpe/shared-publishing/images-norend/0xx/02/0...29.8 KiB24.2 KiB
Close up of unrecognizable man using computer in office with focus on male hand… div.cb-content > div.typo5 > div.img-container > img.io-image
/content/dam/hpe/shared-publishing/images-norend/7xx/7295...22.3 KiB18.1 KiB
HPE Aruba Networking Central dashboard. div.cb-content > div.typo5 > div.img-container > img.io-image
/content/dam/hpe/shared-publishing/images-norend/screensh...15.3 KiB12.4 KiB
HPE Aruba Networking CX 6000 Switch Series. div.cb-content > div.typo5 > div.img-container > img.io-image
/content/dam/hpe/shared-publishing/images-norend/products...15.2 KiB12.4 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-4-DIV
nodeLabel: main#content > div.adaptiveMarqueeComponent > hpe-adaptive-marquee.adaptive-marquee > div.bg-wrapper
path: 1,HTML,2,BODY,5,DIV,3,MAIN,2,DIV,2,HPE-ADAPTIVE-MARQUEE,1,DIV
selector: main#content > div.adaptiveMarqueeComponent > hpe-adaptive-marquee.adaptive-marquee > div.bg-wrapper
snippet: <div class="bg-wrapper default am-light-green ">

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
value: no origins were preconnected
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.

URLTransfer SizeDuration
www.hpe.com/content/dam/hpe/web-ui/css/hpe-generic-v3.38cac265c5cb.css46.0 KiB303 ms

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.

URLEst Savings
www.hpe.com/content/dam/hpe/web-ui/fonts/hpe-glyphicons.woff210 ms

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.5 s
URLTime Spent
www.arubanetworks.com/767 ms
arubanetworking.hpe.com/774 ms
www.hpe.com/us/en/networking/hpe-aruba-networking.html0.0 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 150 ms 40.3 KiB
URLTransfer SizeEst Savings
www.hpe.com/content/dam/hpe/web-ui/css/hpe-generic-v3.38cac265c5cb.css45.1 KiB40.3 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.

URLTotal CPU TimeScript EvaluationScript Parse
www.hpe.com/us/en/networking/hpe-aruba-networking.html1.8 s96 ms5.4 ms
Unattributable1.4 s197 ms0.0 ms
s2.go-mpulse.net/boomerang/EP6HW-6SA9L-6GGT5-VM3KF-TQAT91.3 s352 ms22 ms
www.hpe.com/foElZxJAKex7p/jMzG_EG9k/wU1Yo/1N9JSDVmXmQ4pQ/biVUdhwB/anhxPHkw/E0sB1.2 s1.1 s78 ms
www.hpe.com/content/dam/hpe/web-ui/js/hpe-generic-v3.38cac265c5cb.js1.1 s653 ms51 ms
js.driftt.com/include/1776361200000/un8c6h7cv2cr.js728 ms684 ms30 ms
/notice?domain=hpe.com&c=teconsent&gtm=1&country=us&langu...624 ms330 ms6.4 ms
www.hpe.com/content/dam/hpe/web-ui/js/critical-loader.38cac265c5cb.js355 ms173 ms10 ms
www.googletagmanager.com/gtag/js?id=AW-395091233&cx=c&gtm=4e64f0321 ms264 ms53 ms
www.googletagmanager.com/gtag/js?id=AW-609215616&cx=c&gtm=4e64f0303 ms247 ms52 ms
www.googletagmanager.com/gtm.js?id=GTM-N5B6RF33285 ms221 ms52 ms
www.hpe.com/global/metrics/launch/launch-marketing.min.js276 ms231 ms26 ms
www.googletagmanager.com/gtag/js?id=AW-977186894273 ms218 ms51 ms
/content/dam/hpe/web-ui/js/components/core/esl-carousel.3...216 ms156 ms7.3 ms
www.hpe.com/akam/13/51ec9585155 ms134 ms5.1 ms
consent.trustarc.com/asset/notice.js/v/v1.7-1729126 ms85 ms16 ms
blob:https://www.hpe.com/26d5c7cd-0ae0-41e6-be77-16fbcf93833a78 ms65 ms1.1 ms
www.googletagmanager.com/gtag/js?id=AW-977186894&cx=c&gtm=4e64f075 ms27 ms47 ms
snap.licdn.com/li.lms-analytics/insight.min.js74 ms63 ms6.5 ms
tags.clickagy.com/data.js?rnd=62fe5c0e6ad9673 ms49 ms14 ms
www.hpe.com/global/metrics/bootstrap/prod_wsdk.js69 ms37 ms28 ms
js.adsrvr.org/up_loader.1.1.0.js69 ms49 ms14 ms
www.hpe.com/global/metrics/chat/chat-init/chat-init.js62 ms53 ms8.0 ms
blob:https://www.hpe.com/fed728a2-99be-4e0a-b3cf-ced0b87c277058 ms53 ms1.0 ms
www.hpe.com/global/metrics/bootstrap/prod.js58 ms35 ms22 ms
cdn.amplitude.com/libs/analytics-browser-1.13.6-min.js.gz56 ms44 ms11 ms
static.ads-twitter.com/uwt.js51 ms43 ms6.0 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 Evaluation6.0 s
Other2.6 s
Style & Layout1.5 s
Script Parsing & Compilation694 ms
Rendering606 ms
Garbage Collection192 ms
Parse HTML & CSS182 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
The page has an unload handler in the main frame.Actionable
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
The page has an unload handler in a sub frame.Actionable
Pages with WebSocket cannot enter back/forward cache.Pending browser support
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.Not actionable

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: 0.0 ms 528.9 KiB
URLTransfer SizeEst Savings
www.googletagmanager.com/gtag/js?id=AW-977186894&cx=c&gtm=4e64f0134.0 KiB102.3 KiB
www.googletagmanager.com/gtm.js?id=GTM-N5B6RF33125.7 KiB60.9 KiB
www.googletagmanager.com/gtag/js?id=AW-977186894133.9 KiB56.5 KiB
www.googletagmanager.com/gtag/js?id=AW-609215616&cx=c&gtm=4e64f0141.8 KiB56.1 KiB
www.hpe.com/content/dam/hpe/web-ui/js/hpe-generic-v3.38cac265c5cb.js108.2 KiB55.2 KiB
www.googletagmanager.com/gtag/js?id=AW-395091233&cx=c&gtm=4e64f0141.3 KiB54.6 KiB
www.hpe.com/global/metrics/bootstrap/prod.js53.4 KiB45.4 KiB
www.hpe.com/foElZxJAKex7p/jMzG_EG9k/wU1Yo/1N9JSDVmXmQ4pQ/biVUdhwB/anhxPHkw/E0sB181.4 KiB36.7 KiB
js.driftt.com/include/1776361200000/un8c6h7cv2cr.js62.2 KiB31.8 KiB
www.hpe.com/global/metrics/bootstrap/prod_wsdk.js69.0 KiB29.4 KiB

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
●Avoids enormous network payloads Total size was 2,518 KiB
●User Timing marks and measures 18 user timings
●Avoid long main-thread tasks 20 long tasks found
●Avoid non-composited animations 18 animated elements found
●Image elements have explicit `width` and `height`
●Network Requests
●Network Round Trip Times 340 ms
●Server Backend Latencies 820 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
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
Privacy Statement div#truste-consent-track > div#truste-consent-content > div#truste-consent-text > a#truste-privacy-button
Manage Settings → div#truste-consent-track > div#truste-consent-content > div#truste-consent-text > a#truste-show-consent

These are opportunities to improve the legibility of your content.

Navigation

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Broad-based infrastructure div.sc-content > div.typo5 > div.txto-title-wrapper > h3.txto-title
HPE Aruba Networking Central div.cb-content > div.typo5 > div.txto-title-wrapper > h4.txto-title
AIOps div.sc-content > div.typo5 > div.txto-title-wrapper > h4.txto-title
New Wi-Fi 7 access points improve security and address AI and IoT challenges div#uc-card--266143106 > div.typo5 > div.txto-title-wrapper > h5.txto-title

These are opportunities to improve keyboard navigation in your application.

Best practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Do not Sell my Personal Information div.footer-docs-license > ul.footer-policies > li.footer-policy-link > a.footer-policy-title
Sitemap div.footer-docs-license > ul.footer-policies > li.footer-policy-link > a.footer-policy-title

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●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
●`[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
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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 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
○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.
○`<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 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
close icon div#truste-consent-track > div#truste-consent-content > button#truste-consent-close > img
consent.trustarc.com/get?name=trustarc-close.png16 x 1618 x 1824 x 24

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
Unload event listeners are deprecated and will be removed.
www.hpe.com/content/dam/hpe/web-ui/js/hpe-generic-v3.38cac265c5cb.js line 3, col 39784
AttributionReporting
snap.licdn.com/li.lms-analytics/insight.min.js

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
epsilon.6sense.com/v3/company/details
Failed to load resource: the server responded with a status of 401 ()
di.rlcdn.com/api/segment?pid=451196
Failed to load resource: the server responded with a status of 451 ()

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLMap URL
www.hpe.com/foElZxJAKex7p/jMzG_EG9k/wU1Yo/1N9JSDVmXmQ4pQ/biVUdhwB/anhxPHkw/E0sB
www.hpe.com/content/dam/hpe/web-ui/js/hpe-generic-v3.38cac265c5cb.jswww.hpe.com/content/dam/hpe/web-ui/js/hpe-generic-v3.38cac265c5cb.js.map
www.hpe.com/content/dam/hpe/web-ui/js/critical-loader.38cac265c5cb.jswww.hpe.com/content/dam/hpe/web-ui/js/critical-loader.38cac265c5cb.js.map
/content/dam/hpe/web-ui/js/components/unicorn/adaptive-ma.../content/dam/hpe/web-ui/js/components/unicorn/adaptive-ma...
www.hpe.com/content/dam/hpe/web-ui/js/components/hpe.chat-api.js.38cac265c5cb.js/content/dam/hpe/web-ui/js/components/hpe.chat-api.js.38c...
www.hpe.com/content/dam/hpe/web-ui/js/components/hpe-share-async.38cac265c5cb.js/content/dam/hpe/web-ui/js/components/hpe-share-async.38c...
/content/dam/hpe/web-ui/js/components/hpe-gn/search-box.3.../content/dam/hpe/web-ui/js/components/hpe-gn/search-box.3...
/content/dam/hpe/web-ui/js/components/hpe-gn/gn-header-v4.../content/dam/hpe/web-ui/js/components/hpe-gn/gn-header-v4...
/content/dam/hpe/web-ui/js/components/core/media.tracker..../content/dam/hpe/web-ui/js/components/core/media.tracker....
/content/dam/hpe/web-ui/js/components/core/media.provider.../content/dam/hpe/web-ui/js/components/core/media.provider...
/content/dam/hpe/web-ui/js/components/core/media.mixins.3.../content/dam/hpe/web-ui/js/components/core/media.mixins.3...
/content/dam/hpe/web-ui/js/components/core/esl-carousel.3.../content/dam/hpe/web-ui/js/components/core/esl-carousel.3...
●Uses HTTPS
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●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
○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.

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

To appear in search results, crawlers need access to your app.

○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 have descriptive text
●Links are crawlable
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback