Skip to content
Audit Complete

Results for https://maven.org

Visit site
Spain Spain · Madrid Completed: Apr 22, 2026 22:09 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

Decent speed, but optimizing further could improve engagement.

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.

Mostly compliant — a few items need attention.

Good content signals with minor gaps.

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

How is this calculated?

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

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

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

How the composite score is calculated

How you compare

Amazon Route 53 · 961 peers
You 74
·
Avg 72
At average
0 50 100
Better than 64% of Amazon Route 53 sites See full Amazon Route 53 benchmark →
Font Awesome · 501 peers
You 74
·
Avg 73
At average
0 50 100
Better than 59% of Font Awesome sites See full Font Awesome 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

No Content-Security-Policy header found

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

Security › Content Security Policy
3

Page weighs 11.9 MB (4.2 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
4

104 third-party resources (87% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory
5

115 HTTP requests — consider bundling or reducing

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

2

High impact, low effort — start here.

Strategic

3

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%2Fmaven.org)](https://beavercheck.com/results/f3cf2d93-5255-4696-bcdd-33c11c2a7887)
<a href="https://beavercheck.com/results/f3cf2d93-5255-4696-bcdd-33c11c2a7887"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fmaven.org" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fmaven.org

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 20.1s exceeds Google's 2.5s 'Good' threshold and the 3 performance issues below directly contribute to it. Addressing the critical issues below would have the most immediate impact on your user trust.

2 security gaps detected — browsers may warn visitors about your site.
Your LCP is 20.1s — fixing the 3 performance criticals could bring it under Google's 2.5s 'Good' threshold.

Conversion Barriers

4 critical 5 warning

9 barrier(s) likely increasing bounce by ~35%.

Speed (2)

Page takes 20.1s to load

+12% bounce

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

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

Page feels frozen for 1.5s

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

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

Trust (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)

Severe layout shift during page load

+6% bounce

Users mis-click when content jumps — converting intent into frustration

Fix: Reserve space for images, ads, and embeds with explicit width/height

Content (2)

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

Navigation (2)

No skip-to-content link

+1% bounce

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

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

76 broken link(s) on the page

+5% bounce

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

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

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

Return on Investment

€595 investment → €0.97/month returns + EUR 120,500,000 risk avoided

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

Investment

€595

7h · 5 findings

Monthly returns

€0.97 /mo

~€12 / year

  • Bandwidth savings €0.97

Regulatory risk avoided

EUR 120,500,000

if kept compliant

  • ePrivacy Directive EUR 100,000,000
  • GDPR EUR 20,000,000
  • EAA EUR 500,000

€85 — 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

€595

7.0 developer hours at €85/hr

Based on European Union rates (€85/hr)

Quick wins
€85 2 fixes in ~60 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

€10,041,668 / month at risk

~€120,500,012 / year if left unfixed

Compliance Risk

€120,500,000

ePrivacy DirectiveGDPREAA
  • No privacy policy link detected
    GDPR: EUR 10,000 – EUR 20,000,000
  • Trackers detected but no cookie policy found
    GDPR: EUR 5,000 – EUR 10,000,000
  • Trackers detected but no cookie policy found
    GDPR: EUR 10,000 – EUR 20,000,000

+6 more

Bandwidth Waste

€0.97 /mo

13126.2 MB/mo × 0.074 EUR/GB

  • Optimize transfer: save ~1.3 MB per page load
    Saves €0.97/mo

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

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

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

Fix 3 critical issues to capture this value

How this is calculated

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

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

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

Was this report useful?

Thanks for your feedback!

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

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

17
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
95
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.

3.47 s

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

20.05 s

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

1.51 s

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

0.489

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

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

26.97 s

Detailed Report

Audit breakdown by category with detailed findings.

17

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.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.489437] map[node:map[boundingRect:map[bottom:1531 height:627 left:0 right:412 top:904 width:412] lhId:page-3-DIV nodeLabel:Stop Reworking AI Code. Start Shipping It. Sonatype Guide gives AI coding assi… path:1,HTML,1,BODY,2,DIV,1,DIV,0,DIV,2,DIV selector:div.nx-page > div.nx-page-content > div.IndexPage-module-scss-module__m3x4hG__heroAndMain > div.GuideAd-module-scss-module__Kh82Wq__productWrapper snippet:<div class="GuideAd-module-scss-module__Kh82Wq__productWrapper"> type:node] score:0.449888] map[node:map[boundingRect:map[bottom:4452 height:4316 left:0 right:412 top:136 width:412] lhId:page-2-DIV nodeLabel:Find OSS Components As stewards of Central for nearly 20 years and inventors o… path:1,HTML,1,BODY,2,DIV,1,DIV selector:body.nx-body > div.nx-page > div.nx-page-content snippet:<div class="nx-page-content IndexPage-module-scss-module__m3x4hG__content"> type:node] score:0.039549]]

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
State Of The Software Supply Chain Report div.SccrAd-module-scss-module__cu9oPa__productContainer > div.SccrAd-module-scss-module__cu9oPa__container > div.SccrAd-module-scss-module__cu9oPa__image > img
central.sonatype.com/_next/static/media/SSCR26-book-mock.a6bdab2e.png444.7 KiB411.8 KiB
Help div.Footer-module-scss-module__yFPs5G__footerInner > div > ul > li.Footer-module-scss-module__yFPs5G__footerListItem
maven.org/assets/images/center-image.jpeg?v=1157.1 KiB34.7 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.

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

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

Lists the toplevel main thread tasks that executed during page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Collection of useful page vitals.

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

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: 6.3 s

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
Stop Reworking AI Code. Start Shipping It. Sonatype Guide gives AI coding assi… div.nx-page > div.nx-page-content > div.IndexPage-module-scss-module__m3x4hG__heroAndMain > div.GuideAd-module-scss-module__Kh82Wq__productWrapper
0.450
Find OSS Components As stewards of Central for nearly 20 years and inventors o… body.nx-body > div.nx-page > div.nx-page-content
0.040

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

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.

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks

Why this matters

Performance issues directly impact user engagement and conversion rates.

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: 320 ms 13.2 KiB
URLTransfer SizeEst Savings
central.sonatype.com/_next/static/chunks/32204ee6079875e1.css17.8 KiB13.2 KiB

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

Why this matters

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

Learn more

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

Source: Google web.dev / Lighthouse

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
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
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

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

Document request latency
Optimize DOM size
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 42 user timings
Avoid non-composited animations 2 animated elements found
Image elements have explicit `width` and `height`
Network Requests
Network Round Trip Times 170 ms
Server Backend Latencies 200 ms
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 220 ms
INP breakdown
95

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
Visit HeroDevs div.HeroDevsIndexAd-module-scss-module__uBZRbG__card > div.HeroDevsIndexAd-module-scss-module__uBZRbG__buttonWrapper > a.nx-text-link > span

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
Partner-Backed Support for OSS Component Security NEW div.HeroDevsIndexAd-module-scss-module__uBZRbG__container > div.HeroDevsIndexAd-module-scss-module__uBZRbG__textContainer > div.HeroDevsIndexAd-module-scss-module__uBZRbG__text > h3.nx-h3

These are opportunities to improve keyboard navigation in your application.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
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
Touch targets have sufficient size and spacing.
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[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
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.
`[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.
Elements with visible text labels have matching accessible names.
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 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)
State Of The Software Supply Chain Report div.SccrAd-module-scss-module__cu9oPa__productContainer > div.SccrAd-module-scss-module__cu9oPa__container > div.SccrAd-module-scss-module__cu9oPa__image > img
central.sonatype.com/_next/static/media/SSCR26-book-mock.a6bdab2e.png288 x 229 (1.26)972 x 613 (1.59)

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
Access to fetch at 'https://identity.sonatype.com/authorize?client_id=H6OeHHDPADwvGyY5oN6Oh82tPO0tqbsT&scope=openid%20profile%20email%20offline_access&response_type=code&redirect_uri=https%3A%2F%2Fcentral.sonatype.com%2Fapi%2Fauth%2Fcallback&audience=central-portal-api&nonce=7dIUi1l9aJ_lUwajkXxjHpeWt6jJN4z-8F5PDBXQOzs&state=eyJyZXR1cm5UbyI6Imh0dHBzOi8vY2VudHJhbC5zb25hdHlwZS5jb20vP3Ntbz10cnVlIn0&code_challenge_method=S256&code_challenge=TR97GU1ls9PGDjGnN_ZkLVvVOS_m1MpweY_LELYXY78' (redirected from 'https://central.sonatype.com/api/auth/login?_rsc=1r34m') from origin 'https://central.sonatype.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
ERROR TypeError: window.ga is not a function at d._next (https://maven.org/main-es2015.76540079f641857f2387.js:1:735442) at d.__tryOrUnsub (https://maven.org/main-es2015.76540079f641857f2387.js:1:66910) at d.next (https://maven.org/main-es2015.76540079f641857f2387.js:1:66131) at l._next (https://maven.org/main-es2015.76540079f641857f2387.js:1:65302) at l.next (https://maven.org/main-es2015.76540079f641857f2387.js:1:65076) at t.next (https://maven.org/main-es2015.76540079f641857f2387.js:1:367031) at d._next (https://maven.org/main-es2015.76540079f641857f2387.js:1:605562) at d.__tryOrUnsub (https://maven.org/main-es2015.76540079f641857f2387.js:1:66910) at d.next (https://maven.org/main-es2015.76540079f641857f2387.js:1:66131) at l._next (https://maven.org/main-es2015.76540079f641857f2387.js:1:65302)
Failed to load resource: net::ERR_FAILED

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.

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
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 clickjacking with XFO or CSP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Redirects HTTP traffic to HTTPS
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.

Link destinationLink Text
central.sonatype.com/partners/Learn 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
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`
robots.txt is valid

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

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

Core Web Vitals

Key metrics that affect user experience. — Desktop

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

1.05 s

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

3.27 s

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

75 ms

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

0.225

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

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

4.61 s

Detailed Report

Audit breakdown by category with detailed findings.

63

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.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.000445] map[node:map[boundingRect:map[bottom:1279 height:14 left:289 right:301 top:1265 width:12] lhId:page-1-svg nodeLabel:div.Card-module-scss-module__ivjD6a__card > header.ComponentCardHeader-module-scss-module__EmzniW__header > button.ComponentCardHeader-module-scss-module__EmzniW__iconCopyPurl > svg.svg-inline--fa path:1,HTML,1,BODY,2,DIV,1,DIV,0,DIV,3,MAIN,0,SECTION,0,DIV,1,UL,1,LI,0,DIV,0,HEADER,1,BUTTON,0,svg selector:div.Card-module-scss-module__ivjD6a__card > header.ComponentCardHeader-module-scss-module__EmzniW__header > button.ComponentCardHeader-module-scss-module__EmzniW__iconCopyPurl > svg.svg-inline--fa snippet:<svg aria-hidden="true" focusable="false" data-prefix="fas" data-icon="copy" class="svg-inline--fa fa-copy nx-icon" role="img" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 448 512"> type:node] score:0.000445]]
headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.224568] map[node:map[boundingRect:map[bottom:1025 height:388 left:0 right:1350 top:637 width:1350] lhId:page-8-DIV nodeLabel:Stop Reworking AI Code. Start Shipping It. Sonatype Guide gives AI coding assi… path:1,HTML,1,BODY,2,DIV,1,DIV,0,DIV,2,DIV selector:div.nx-page > div.nx-page-content > div.IndexPage-module-scss-module__m3x4hG__heroAndMain > div.GuideAd-module-scss-module__Kh82Wq__productWrapper snippet:<div class="GuideAd-module-scss-module__Kh82Wq__productWrapper"> type:node] score:0.169191] map[node:map[boundingRect:map[bottom:2069 height:1044 left:0 right:1350 top:1025 width:1350] lhId:page-2-MAIN nodeLabel:Most Popular Packages in Last 90 Days commons-rng-bom Version: 1.7 View all Pub… path:1,HTML,1,BODY,2,DIV,1,DIV,0,DIV,3,MAIN selector:div.nx-page > div.nx-page-content > div.IndexPage-module-scss-module__m3x4hG__heroAndMain > main.nx-page-main snippet:<main class="nx-page-main"> type:node] score:0.031484 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://central.sonatype.com/_next/static/media/open-sans-v18-latin-600.e16cc113.woff]] map[cause:Web font extra:map[type:url value:https://central.sonatype.com/_next/static/media/open-sans-v18-latin-700.ecc3257d.woff]] map[cause:Web font extra:map[type:url value:https://central.sonatype.com/_next/static/media/open-sans-v18-latin-regular.d772c311.woff]] map[cause:Web font extra:map[type:url value:https://central.sonatype.com/_next/static/media/open-sans-v18-latin-600italic.93da11fc.woff]]] type:subitems]] map[node:map[boundingRect:map[bottom:2069 height:1044 left:0 right:1350 top:1025 width:1350] lhId:page-2-MAIN nodeLabel:Most Popular Packages in Last 90 Days commons-rng-bom Version: 1.7 View all Pub… path:1,HTML,1,BODY,2,DIV,1,DIV,0,DIV,3,MAIN selector:div.nx-page > div.nx-page-content > div.IndexPage-module-scss-module__m3x4hG__heroAndMain > main.nx-page-main snippet:<main class="nx-page-main"> type:node] score:0.02033] map[node:map[boundingRect:map[bottom:2069 height:1044 left:0 right:1350 top:1025 width:1350] lhId:page-2-MAIN nodeLabel:Most Popular Packages in Last 90 Days commons-rng-bom Version: 1.7 View all Pub… path:1,HTML,1,BODY,2,DIV,1,DIV,0,DIV,3,MAIN selector:div.nx-page > div.nx-page-content > div.IndexPage-module-scss-module__m3x4hG__heroAndMain > main.nx-page-main snippet:<main class="nx-page-main"> type:node] score:0.003563]]

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-svg
nodeLabel: dl.ComponentCardMetadata-module-scss-module__8NHc_W__MetaDataContainer > div.MetadataItem-module-scss-module__FJ3FTq__metadataItem > dt.MetadataItem-module-scss-module__FJ3FTq__metadataTitleWrapper > svg.svg-inline--fa
path: 1,HTML,1,BODY,2,DIV,1,DIV,0,DIV,3,MAIN,0,SECTION,0,DIV,1,UL,1,LI,0,DIV,1,DIV,0,DL,1,DIV,0,DT,0,svg
selector: dl.ComponentCardMetadata-module-scss-module__8NHc_W__MetaDataContainer > div.MetadataItem-module-scss-module__FJ3FTq__metadataItem > dt.MetadataItem-module-scss-module__FJ3FTq__metadataTitleWrapper > svg.svg-inline--fa
snippet: <svg aria-hidden="true" focusable="false" data-prefix="fas" data-icon="calendar-days" class="svg-inline--fa fa-calendar-days fa-fw MetadataItem-module-scss-module__FJ3…" role="img" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 448 512">

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

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.

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
State Of The Software Supply Chain Report div.SccrAd-module-scss-module__cu9oPa__productContainer > div.SccrAd-module-scss-module__cu9oPa__container > div.SccrAd-module-scss-module__cu9oPa__image > img
central.sonatype.com/_next/static/media/SSCR26-book-mock.a6bdab2e.png444.7 KiB418.1 KiB
dl.ComponentCardMetadata-module-scss-module__8NHc_W__MetaDataContainer > div.MetadataItem-module-scss-module__FJ3FTq__metadataItem > dt.MetadataItem-module-scss-module__FJ3FTq__metadataTitleWrapper > svg.svg-inline--fa dl.ComponentCardMetadata-module-scss-module__8NHc_W__MetaDataContainer > div.MetadataItem-module-scss-module__FJ3FTq__metadataItem > dt.MetadataItem-module-scss-module__FJ3FTq__metadataTitleWrapper > svg.svg-inline--fa
maven.org/assets/images/center-image.jpeg?v=1157.1 KiB34.7 KiB

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

Lists the toplevel main thread tasks that executed during page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Collection of useful page vitals.

Why this matters

Performance issues directly impact user engagement and conversion rates.

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
Stop Reworking AI Code. Start Shipping It. Sonatype Guide gives AI coding assi… div.nx-page > div.nx-page-content > div.IndexPage-module-scss-module__m3x4hG__heroAndMain > div.GuideAd-module-scss-module__Kh82Wq__productWrapper
0.169
Most Popular Packages in Last 90 Days commons-rng-bom Version: 1.7 View all Pub… div.nx-page > div.nx-page-content > div.IndexPage-module-scss-module__m3x4hG__heroAndMain > main.nx-page-main
0.031
Most Popular Packages in Last 90 Days commons-rng-bom Version: 1.7 View all Pub… div.nx-page > div.nx-page-content > div.IndexPage-module-scss-module__m3x4hG__heroAndMain > main.nx-page-main
0.020
Most Popular Packages in Last 90 Days commons-rng-bom Version: 1.7 View all Pub… div.nx-page > div.nx-page-content > div.IndexPage-module-scss-module__m3x4hG__heroAndMain > main.nx-page-main
0.004
div.Card-module-scss-module__ivjD6a__card > header.ComponentCardHeader-module-scss-module__EmzniW__header > button.ComponentCardHeader-module-scss-module__EmzniW__iconCopyPurl > svg.svg-inline--fa div.Card-module-scss-module__ivjD6a__card > header.ComponentCardHeader-module-scss-module__EmzniW__header > button.ComponentCardHeader-module-scss-module__EmzniW__iconCopyPurl > svg.svg-inline--fa
0.000

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

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.

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks

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

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
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
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 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 13.2 KiB
URLTransfer SizeEst Savings
central.sonatype.com/_next/static/chunks/32204ee6079875e1.css17.8 KiB13.2 KiB

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

Document request latency
Optimize DOM size
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 42 user timings
Avoid non-composited animations 2 animated elements found
Image elements have explicit `width` and `height`
Network Requests
Network Round Trip Times 170 ms
Server Backend Latencies 30 ms
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 20 ms
INP breakdown
95

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
Visit HeroDevs div.HeroDevsIndexAd-module-scss-module__uBZRbG__card > div.HeroDevsIndexAd-module-scss-module__uBZRbG__buttonWrapper > a.nx-text-link > span

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
Partner-Backed Support for OSS Component Security NEW div.HeroDevsIndexAd-module-scss-module__uBZRbG__container > div.HeroDevsIndexAd-module-scss-module__uBZRbG__textContainer > div.HeroDevsIndexAd-module-scss-module__uBZRbG__text > h3.nx-h3

These are opportunities to improve keyboard navigation in your application.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
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
Touch targets have sufficient size and spacing.
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[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
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.
`[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.
Elements with visible text labels have matching accessible names.
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.
96

Best Practices

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
Access to fetch at 'https://identity.sonatype.com/authorize?client_id=H6OeHHDPADwvGyY5oN6Oh82tPO0tqbsT&scope=openid%20profile%20email%20offline_access&response_type=code&redirect_uri=https%3A%2F%2Fcentral.sonatype.com%2Fapi%2Fauth%2Fcallback&audience=central-portal-api&nonce=aIEJm2_XQY0-rfuNJddd8-i5gc0u8MIJ-Ne2M3Gh8kc&state=eyJyZXR1cm5UbyI6Imh0dHBzOi8vY2VudHJhbC5zb25hdHlwZS5jb20vP3Ntbz10cnVlIn0&code_challenge_method=S256&code_challenge=64qSr10yGwggIhIK3pOMfCONGHq2aiGDEGttlqg2sUE' (redirected from 'https://central.sonatype.com/api/auth/login?_rsc=1r34m') from origin 'https://central.sonatype.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
ERROR TypeError: window.ga is not a function at d._next (https://maven.org/main-es2015.76540079f641857f2387.js:1:735442) at d.__tryOrUnsub (https://maven.org/main-es2015.76540079f641857f2387.js:1:66910) at d.next (https://maven.org/main-es2015.76540079f641857f2387.js:1:66131) at l._next (https://maven.org/main-es2015.76540079f641857f2387.js:1:65302) at l.next (https://maven.org/main-es2015.76540079f641857f2387.js:1:65076) at t.next (https://maven.org/main-es2015.76540079f641857f2387.js:1:367031) at d._next (https://maven.org/main-es2015.76540079f641857f2387.js:1:605562) at d.__tryOrUnsub (https://maven.org/main-es2015.76540079f641857f2387.js:1:66910) at d.next (https://maven.org/main-es2015.76540079f641857f2387.js:1:66131) at l._next (https://maven.org/main-es2015.76540079f641857f2387.js:1:65302)
Failed to load resource: net::ERR_FAILED

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.

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
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 clickjacking with XFO or CSP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Redirects HTTP traffic to HTTPS
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.

Link destinationLink Text
central.sonatype.com/partners/Learn 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
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`
robots.txt is valid

Send Feedback