Skip to content
https://netapp.com

Lighthouse Desktop

· 0 checks — Desktop 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.

58

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
assets.adobedtm.com/60287eadf1ee/29b76ec16604/launch-145d1b654f79.min.js3600.0 s191.5 KiB
transcend-cdn.com/cm/b2cde372-f099-421d-8158-13483effbe36/ui.js60.0 s93.2 KiB
connect.facebook.net/en_US/fbevents.js1200.0 s96.6 KiB
transcend-cdn.com/cm/b2cde372-f099-421d-8158-13483effbe36/airgap.js60.0 s52.9 KiB
/signals/config/227885908352743?v=2.9.303&r=stable&domain...1200.0 s45.0 KiB
www.netapp.com/static/css/critical.min.css?v=6391023364949123543600.0 s47.3 KiB
siteimproveanalytics.com/js/siteanalyze_59699.js86400.0 s90.9 KiB
i.ytimg.com/vi/CkNGp2WLxS8/sddefault.jpg7200.0 s43.4 KiB
v2.d41.co/tags/dnb_coretag_v6.min.js0.0 ms30.1 KiB
www.netapp.com/static/js/jquery.min.js?v=6391023364997207023600.0 s30.6 KiB
c.lytics.io/static/pathfora.min.js3600.0 s24.3 KiB
www.redditstatic.com/ads/pixel.js60.0 s19.0 KiB
www.netapp.com/static/css/non-critical.min.css?v=6391023364949932643600.0 s23.4 KiB
www.netapp.com/static/js/index.min.js?v=6391023364997004653600.0 s22.5 KiB
c.lytics.io/api/tag/9c4304af06cbdc8ccba6025bfb18eb8c/latest.min.js7200.0 s22.4 KiB
js.adsrvr.org/up_loader.1.1.0.js0.0 ms12.3 KiB
/api/personalize/9c4304af06cbdc8ccba6025bfb18eb8c/user/_u...0.0 ms8.3 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.netapp.com/static/js/load-drift.min.js?v=6391023364997409413600.0 s7.5 KiB
js.zi-scripts.com/zi-tag.js0.0 ms5.7 KiB
s.go-mpulse.net/boomerang/6FSMF-C9TB6-XLEBP-V5VVN-JCRY5604800.0 s56.1 KiB
www.netapp.com/static/js/adobe-analytics.min.js?v=6391023364954107113600.0 s5.5 KiB
transcend-cdn.com/cm/b2cde372-f099-421d-8158-13483effbe36/cm.css60.0 s4.2 KiB
c.lytics.io/static/pathfora.min.css3600.0 s4.6 KiB
cdn.mgln.ai/pixel.min.js14400.0 s3.0 KiB
trk.funnelfuel.io/netapp/events.js0.0 ms1.8 KiB
www.netapp.com/static/js/a11y-dialog.min.js?v=6391023364953904473600.0 s2.3 KiB
www.netapp.com/static/css/coveo-searchbox.min.css?v=6391023364948921473600.0 s2.0 KiB
trk.techtarget.com/tracking.js1200.0 s1.5 KiB
www.netapp.com/static/js/lazy-load.min.js?v=6391023364997207023600.0 s1.6 KiB
munchkin.marketo.net/munchkin.js0.0 ms1.2 KiB
c.lytics.io/api/experience/candidate/9c4304af06cbdc8ccba6025bfb18eb8c/config.js7200.0 s1.6 KiB
www.netapp.com/static/css/utility.min.css?v=6391023364950311733600.0 s1.5 KiB
js.adsrvr.org/universal_pixel.js0.0 ms959 B
/60287eadf1ee/29b76ec16604/c4220d8c57ea/RC8ed818e04214487...3600.0 s1.2 KiB
/60287eadf1ee/29b76ec16604/c4220d8c57ea/RC91ac17dc3e26482...3600.0 s1.1 KiB
/60287eadf1ee/29b76ec16604/c4220d8c57ea/RC205f83630671495...3600.0 s1.1 KiB
/60287eadf1ee/29b76ec16604/c4220d8c57ea/RC14ce982510eb493...3600.0 s973 B
/60287eadf1ee/29b76ec16604/c4220d8c57ea/RC7b82e4ddf2924b0...3600.0 s927 B
/eRhoXHgsNKquIDVvlDN-7V0-mpy73EdgGDYhvfYRnCopLov5Y8wwP8B8...86400.0 s1.8 KiB
/60287eadf1ee/29b76ec16604/c4220d8c57ea/RC1aeaef5586454cf...3600.0 s913 B
/eRhoXHgsNKquIDVvlDN-7V0-mpy73EdgGDYhvfYRnCopLov5Y8wwP8B8...86400.0 s1.7 KiB
/60287eadf1ee/29b76ec16604/c4220d8c57ea/RCa52e7dcca81d4ca...3600.0 s852 B
/60287eadf1ee/29b76ec16604/c4220d8c57ea/RCad229b776ea647f...3600.0 s835 B
/rp.gif?ts=1776901852849&id=t2_1scotpa2&event=PageVisit&m...0.0 ms666 B
/60287eadf1ee/29b76ec16604/c4220d8c57ea/RCcd3966af6c1d45e...3600.0 s793 B
/60287eadf1ee/29b76ec16604/c4220d8c57ea/RC0064ddfed6b34c2...3600.0 s789 B
/60287eadf1ee/29b76ec16604/c4220d8c57ea/RCf045efc3a3f04d1...3600.0 s780 B
/60287eadf1ee/29b76ec16604/c4220d8c57ea/RCc09609d807cd453...3600.0 s759 B
/60287eadf1ee/29b76ec16604/c4220d8c57ea/RC91572d1ba2e64ed...3600.0 s752 B
/60287eadf1ee/29b76ec16604/c4220d8c57ea/RCabe897884bb5490...3600.0 s739 B
/60287eadf1ee/29b76ec16604/c4220d8c57ea/RCa44db42256404ba...3600.0 s736 B
/60287eadf1ee/29b76ec16604/c4220d8c57ea/RC0d810538c05f49b...3600.0 s731 B
/60287eadf1ee/29b76ec16604/c4220d8c57ea/RC6ac31bf2aa6a40a...3600.0 s729 B
/60287eadf1ee/29b76ec16604/c4220d8c57ea/RC6d4575eb75ee441...3600.0 s708 B
/60287eadf1ee/29b76ec16604/c4220d8c57ea/RC4b282bcf3adf4fc...3600.0 s707 B
/60287eadf1ee/29b76ec16604/c4220d8c57ea/RC8e5f727282844ff...3600.0 s706 B
/60287eadf1ee/29b76ec16604/c4220d8c57ea/RC0745594d01234c6...3600.0 s703 B
/60287eadf1ee/29b76ec16604/c4220d8c57ea/RCb6e9848b213b42c...3600.0 s693 B
/60287eadf1ee/29b76ec16604/c4220d8c57ea/RCd22bf9ce882d436...3600.0 s691 B
/60287eadf1ee/29b76ec16604/c4220d8c57ea/RC10b92459e83a485...3600.0 s689 B
/60287eadf1ee/29b76ec16604/c4220d8c57ea/RC804fc942fc66423...3600.0 s673 B
/60287eadf1ee/29b76ec16604/c4220d8c57ea/RCd591e8dbcc5846a...3600.0 s666 B
/60287eadf1ee/29b76ec16604/c4220d8c57ea/RC122d52a7d7ba4e3...3600.0 s657 B
/60287eadf1ee/29b76ec16604/c4220d8c57ea/RC057e260d904f4e8...3600.0 s653 B
/60287eadf1ee/29b76ec16604/c4220d8c57ea/RC8edfcb1c4fc540a...3600.0 s621 B
/60287eadf1ee/29b76ec16604/c4220d8c57ea/RC2750a1e2f404496...3600.0 s615 B
static.doubleclick.net/instream/ad_status.js900.0 s495 B
/60287eadf1ee/29b76ec16604/c4220d8c57ea/RC237753adec9640f...3600.0 s483 B
/collect?v=2&fmt=js&pid=366161&time=1776901852714&li_adsI...0.0 ms270 B
/track/cmb/generic?ttd_pid=vnk1rqz&ttd_puid=ee0f7a28-bf7a...0.0 ms254 B
/tr/?id=227885908352743&ev=Lytics%20Audiences&dl=https%3A...0.0 ms19 B
/tr/?id=227885908352743&ev=Lytics%20Audiences&dl=https%3A...0.0 ms16 B
/tr/?id=227885908352743&ev=PageView&dl=https%3A%2F%2Fwww....0.0 ms16 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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:62.13 source:map[type:text value:[unattributed]]] map[reflowTime:0.167 source:map[column:9090 line:6 type:source-location url:https://assets.adobedtm.com/60287eadf1ee/29b76ec16604/launch-145d1b654f79.min.js urlProvider:network]] map[reflowTime:1.07 source:map[column:19672 line:2 type:source-location url:https://assets.adobedtm.com/60287eadf1ee/29b76ec16604/launch-145d1b654f79.min.js urlProvider:network]]]

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:719.921 label:Time to first byte subpart:timeToFirstByte] map[duration:3267.619 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-P
nodeLabel: By clicking “Accept all”, you agree to the storing of cookies on your device to…
path: 1,HTML,2,DIV,a,#document-fragment,0,DIV,2,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,P
selector: div.column-content > div > div > p.paragraph
snippet: <p class="paragraph">

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

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.

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.

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: 316 ms
URLTime Spent
netapp.com/316 ms
www.netapp.com/0.0 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

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.3 s
Other648 ms
Style & Layout255 ms
Script Parsing & Compilation224 ms
Rendering49 ms
Parse HTML & CSS44 ms
Garbage Collection42 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 WebSocket cannot enter back/forward cache.Pending browser support

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
Data Platform — Artificial Intelligence n-tabbed.n-tabbed-component > div.tab-content > div.tab-content-container > img
www.netapp.com/media/data-platform-artificial-intelligence_tcm19-159861.png
S&P Global logo li.n-logo-item > a > span.n-logo-container > img
www.netapp.com/media/sp-global-logo_tcm19-143207.png
Atruvia logo li.n-logo-item > a > span.n-logo-container > img
www.netapp.com/media/atruvia-logo_tcm19-143201.png
T-Systems logo li.n-logo-item > a > span.n-logo-container > img
www.netapp.com/media/t-systems-logo_tcm19-143273.png
World Wide Technology logo li.n-logo-item > a > span.n-logo-container > img
www.netapp.com/media/wwt-logo_tcm19-146038.png
Anaplan logo li.n-logo-item > a > span.n-logo-container > img
www.netapp.com/media/anaplan-logo_tcm19-143199.png
NVIDIA logo li.n-logo-item > a > span.n-logo-container > img
www.netapp.com/media/nvidia-logo_tcm19-143205.png

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

●Layout shift culprits
●Optimize DOM size
●Improve image delivery
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●User Timing marks and measures 10 user timings
●JavaScript execution time 1.0 s
●Avoid long main-thread tasks 6 long tasks found
●Avoid non-composited animations 20 animated elements found
●Network Requests
●Network Round Trip Times 70 ms
●Server Backend Latencies 530 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 530 ms
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○LCP request discovery
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.

ARIA

Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
NetApp uses cookies div.column-content > div > div > p#consent-dialog-title

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Navigation

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
From chaos to clarity n-superhero.n-unleash-genius > n-secondary > n-content > h3
NetApp AFX a > n-content > div.content-inner > h5
Downloads a > n-content > div.content-inner > h5

These are opportunities to improve keyboard navigation in your application.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
See our Cookie Policy for more information. div.footer-container > div.bottom-menu-container > div.bottom-menu-item-container > a.bottom-menu-item
○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]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
77

Best Practices

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
Unload event listeners are deprecated and will be removed.

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
A bad HTTP response code (403) was received when fetching the script.
Failed to load resource: the server responded with a status of 403 ()
www.netapp.com/ line 3095, col 8
ReferenceError: Coveo is not defined
www.netapp.com/ line 2633, col 0
Refused to execute script from 'https://www.netapp.com/static/js/coveo/CoveoJsSearch.Lazy.min.js' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled.
www.netapp.com/ line 8, col 1805
TypeError: Failed to register a ServiceWorker for scope ('https://www.netapp.com/') with script ('https://www.netapp.com/akam-sw.js'): A bad HTTP response code (403) was received when fetching the script.
●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
●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.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Cookie Settings section.n-footer-secondary > ul.n-footer-utility > li > a.tcm-sdk-show-settings

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
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`
○robots.txt is valid

Send Feedback