C — https://www.sonarqube.org

Site Health

Score: 73 / 100

Based on 8 categories, 0 sections

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.

Top Priorities (5)

Content-Security-Policy header is missing

Security › Security Headers

HSTS header is missing

Security › Security Headers

No Content-Security-Policy header found

Security › Content Security Policy

1 image(s) missing alt attribute

Accessibility › Alt Text Quality

184 HTTP requests — consider bundling or reducing

Performance › Page Weight Budget

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.sonarqube.org)](https://beavercheck.com/results/3c641422-940e-3042-73b5-53f0278963e4)

HTML

<a href="https://beavercheck.com/results/3c641422-940e-3042-73b5-53f0278963e4"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.sonarqube.org" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fwww.sonarqube.org

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

Best Practices

SEO

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.06 s

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

4.38 s

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

2.23 s

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

0.000

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

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

20.42 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

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

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

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

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.

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:31.702 source:map[column:1.718812e+06 line:2 type:source-location url:https://www.sonarsource.com/app-3172a3c071dab32cddeb.js 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:86.563 source:map[type:text value:[unattributed]]] map[reflowTime:1.87 source:map[column:160776 line:0 type:source-location url:https://www.sonarsource.com/c8f7fe3b0e41be846d5687592cf2018ff6e22687-72ade12da2482d7c03c6.js urlProvider:network]] map[reflowTime:0.868 source:map[column:24326 line:0 type:source-location url:https://www.sonarsource.com/9992b78b14a71d8bd0cb414cb513094ce8a2a21b-d9edb2884d1c598d72cc.js urlProvider:network]] map[reflowTime:31.702 source:map[column:55 line:885 type:source-location url:https://www.googletagmanager.com/gtm.js?id=GTM-56V34P9 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

	URL	Resource Size	Est Savings
section.css-hpd81o > div.css-9y8f5k > picture.css-gmxnb1 > img.css-nrwp77 `section.css-hpd81o > div.css-9y8f5k > picture.css-gmxnb1 > img.css-nrwp77`	/ef593040-b591-0198-9506-ed88b30bc023/38955c91-7420-4a34-...	97.7 KiB	89.8 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

lhId: page-0-IMG

nodeLabel: section.css-hpd81o > div.css-9y8f5k > picture.css-gmxnb1 > img.css-nrwp77

path: 1,HTML,1,BODY,3,DIV,0,DIV,3,MAIN,0,DIV,12,SECTION,0,DIV,0,PICTURE,3,IMG

selector: section.css-hpd81o > div.css-9y8f5k > picture.css-gmxnb1 > img.css-nrwp77

snippet: <img decoding="async" alt="" loading="eager" srcset="https://assets-eu-01.kc-usercontent.com:443/ef593040-b591-0198-9506-ed88b3…" width="2240" height="1260" class="css-nrwp77 ed0xv1y0">

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.

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.

URL	Transfer Size	Duration
js.navattic.com/embeds.js	6.2 KiB	828 ms

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

Request	Cache TTL	Transfer Size
euob.sd19403.sonarsource.com/sxp/i/ec9ce1449fc9fe8879e7b666ca8b5629.js	43200.0 s	44.5 KiB
js.navattic.com/embeds.js	1800.0 s	6.2 KiB
cdn.equalweb.com/core/5.2.0/accessibility.js	2204800.0 s	15.5 KiB

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

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

Estimated savings: 913 ms

URL	Time Spent
www.sonarqube.org/	913 ms
www.sonarsource.com/products/sonarqube/	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.

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.

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.

URL	Total CPU Time	Script Evaluation	Script Parse
www.sonarsource.com/products/sonarqube/	1.7 s	79 ms	7.2 ms
Unattributable	1.5 s	50 ms	0.0 ms
www.sonarsource.com/app-3172a3c071dab32cddeb.js	1.3 s	671 ms	202 ms
www.sonarsource.com/framework-61f603174610bdecf74e.js	1.2 s	1.1 s	12 ms
euob.sd19403.sonarsource.com/sxp/i/ec9ce1449fc9fe8879e7b666ca8b5629.js	884 ms	702 ms	14 ms
/c8f7fe3b0e41be846d5687592cf2018ff6e22687-72ade12da2482d7...	541 ms	445 ms	73 ms
www.sonarsource.com/commons-8890b03468a586edcd23.js	525 ms	397 ms	30 ms
www.googletagmanager.com/gtag/js?id=G-9JZ0GZ5TC6&cx=c&gtm=4e6460	519 ms	434 ms	77 ms
www.googletagmanager.com/gtm.js?id=GTM-56V34P9	436 ms	295 ms	54 ms
www.googletagmanager.com/gtag/js?id=AW-757017194&cx=c&gtm=4e6460	143 ms	103 ms	38 ms
cdn.equalweb.com/core/5.2.0/accessibility.js	140 ms	119 ms	7.5 ms
www.sonarsource.com/webpack-runtime-5334ed217ab4da055f48.js	67 ms	14 ms	1.0 ms
www.sonarsource.com/8833ea00-e34c0439f77f61bc800e.js	57 ms	1.8 ms	54 ms
www.sonarsource.com/7150-562f96acdb25ef8bcfc1.js	51 ms	31 ms	19 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

Category	Time Spent
Script Evaluation	4.6 s
Other	2.1 s
Style & Layout	1.5 s
Script Parsing & Compilation	668 ms
Parse HTML & CSS	233 ms
Rendering	174 ms
Garbage Collection	149 ms

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

Estimated savings: 0.0 ms 651.5 KiB

URL	Transfer Size	Est Savings
/c8f7fe3b0e41be846d5687592cf2018ff6e22687-72ade12da2482d7...	266.5 KiB	157.6 KiB
/035c3a5dbce655498ebf426080fef9033b4583db-393df6d1dadc0f6...	109.2 KiB	88.1 KiB
www.sonarsource.com/8833ea00-e34c0439f77f61bc800e.js	229.7 KiB	86.7 KiB
www.googletagmanager.com/gtag/js?id=AW-757017194&cx=c&gtm=4e6460	131.6 KiB	82.3 KiB
www.googletagmanager.com/gtm.js?id=GTM-56V34P9	177.9 KiB	75.9 KiB
www.sonarsource.com/commons-8890b03468a586edcd23.js	115.0 KiB	58.2 KiB
www.googletagmanager.com/gtag/js?id=G-9JZ0GZ5TC6&cx=c&gtm=4e6460	177.5 KiB	55.8 KiB
www.sonarsource.com/app-3172a3c071dab32cddeb.js	259.8 KiB	46.9 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

URL	Transfer Size
www.sonarsource.com/8833ea00-e34c0439f77f61bc800e.js	284.5 KiB
/c8f7fe3b0e41be846d5687592cf2018ff6e22687-72ade12da2482d7...	266.7 KiB
www.sonarsource.com/app-3172a3c071dab32cddeb.js	262.3 KiB
/ef593040-b591-0198-9506-ed88b30bc023/99827c23-f90b-4b51-...	259.0 KiB
www.googletagmanager.com/gtm.js?id=GTM-56V34P9	178.3 KiB
www.googletagmanager.com/gtag/js?id=G-9JZ0GZ5TC6&cx=c&gtm=4e6460	177.6 KiB
www.sonarsource.com/page-data/sq/d/3914656367.json	151.5 KiB
www.googletagmanager.com/gtag/js?id=AW-757017194&cx=c&gtm=4e6460	131.7 KiB
www.sonarsource.com/page-data/sq/d/809387045.json	118.3 KiB
www.sonarsource.com/commons-8890b03468a586edcd23.js	115.5 KiB

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

	URL
language switcher `div#language-switcher > div.react-select__control > div.css-tj0ab2 > img`	www.sonarsource.com/assets/icon_language.svg

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

●Layout shift culprits

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●User Timing marks and measures 11 user timings

●Avoid long main-thread tasks 20 long tasks found

●Avoid non-composited animations 5 animated elements found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 40 ms

●Server Backend Latencies 160 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 170 ms

○INP breakdown

○Avoid large layout shifts

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 parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Failing Elements
Products SonarQube products SonarQube Cloud Cloud-based static analysis tool fo… `nav.css-1fp82pj > ul.css-b5wfk1 > li.css-1j936iw > div.css-1r874ck`
Why Sonar Use cases AI code quality Validate AI code for security and quality D… `nav.css-1fp82pj > ul.css-b5wfk1 > li.css-1j936iw > div.css-1r874ck`
Developers For developers Developer hub Learning center Commitment to open sour… `nav.css-1fp82pj > ul.css-b5wfk1 > li.css-1j936iw > div.css-1r874ck`
Resources Get started Onboarding hub Learning center Interactive demos Communit… `nav.css-1fp82pj > ul.css-b5wfk1 > li.css-1j936iw > div.css-1r874ck`
Company Learn about Sonar About Us Our customers Partners Events hub Newsroom C… `nav.css-1fp82pj > ul.css-b5wfk1 > li.css-1y53taa > div.css-1r874ck`
SonarQube SonarQube Industry leading products SonarQube Server SonarQube Cloud … `section.css-mf87fb > div.css-jlorxn > div.css-17nla5q > ul.css-y25j1f`

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Failing Elements
div.css-1nbar7y > section.css-1bavp3g > div.css-psrmlu > div `div.css-1nbar7y > section.css-1bavp3g > div.css-psrmlu > div`
div.css-1nbar7y > section.css-1d19qss > div.css-p8qmoh > div `div.css-1nbar7y > section.css-1d19qss > div.css-p8qmoh > div`

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.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Failing Elements
SonarQube SonarQube Industry leading products SonarQube Server SonarQube Cloud … `div.css-jlorxn > div.css-17nla5q > ul.css-y25j1f > li.css-10mbhcw`
Download `div.css-jlorxn > div.css-17nla5q > ul.css-y25j1f > li.css-10mbhcw`
Docs `div.css-jlorxn > div.css-17nla5q > ul.css-y25j1f > li.css-10mbhcw`
Pricing `div.css-jlorxn > div.css-17nla5q > ul.css-y25j1f > li.css-10mbhcw`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Failing Elements
SAST `div.swiper > div.swiper-wrapper > div.swiper-slide > li#tab:R1ak3ah:0`
Taint analysis `div.swiper > div.swiper-wrapper > div.swiper-slide > li#tab:R1ak3ah:1`
Secrets detection `div.swiper > div.swiper-wrapper > div.swiper-slide > li#tab:R1ak3ah:2`
IaC scanning `div.swiper > div.swiper-wrapper > div.swiper-slide > li#tab:R1ak3ah:3`
Advanced SAST `div.swiper > div.swiper-wrapper > div.swiper-slide > li#tab:R1ak3ah:4`
SCA `div.swiper > div.swiper-wrapper > div.swiper-slide > li#tab:R1ak3ah:5`

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.

Failing Elements
Control item 0 `section.css-1lxt3h6 > div.css-167fs54 > div.css-13n7hpy > button.css-1b2yhzm`
Control item 1 `section.css-1lxt3h6 > div.css-167fs54 > div.css-13n7hpy > button.css-17t6fdk`
Control item 2 `section.css-1lxt3h6 > div.css-167fs54 > div.css-13n7hpy > button.css-17t6fdk`
Control item 3 `section.css-1lxt3h6 > div.css-167fs54 > div.css-13n7hpy > button.css-17t6fdk`
Website Terms of Use `div.css-1go16d5 > ul.css-6w0507 > li.css-1dsq0w7 > a.e1u9akvp0`
Privacy Notice `div.css-1go16d5 > ul.css-6w0507 > li.css-1dsq0w7 > a.e1u9akvp0`
Cookie Policy `div.css-1go16d5 > ul.css-6w0507 > li.css-1dsq0w7 > a.e1u9akvp0`
Trust center `div.css-1go16d5 > ul.css-6w0507 > li.css-1dsq0w7 > a.e1u9akvp0`
Your Privacy Choices `div.css-1go16d5 > ul.css-6w0507 > li.css-1dsq0w7 > button.e1u9akvp0`
UK Modern Slavery Act Statement `div.css-1go16d5 > ul.css-6w0507 > li.css-1dsq0w7 > a.e1u9akvp0`
Unsubscribe `div.css-1go16d5 > ul.css-6w0507 > li.css-1dsq0w7 > button.e1u9akvp0`
Accessibility `div.css-1go16d5 > ul.css-6w0507 > li.css-1dsq0w7 > button.e1u9akvp0`

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

●`[role]`s are contained by their required parent element

●`[role]` values are valid

●`[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.

●`[accesskey]` values are unique

●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

●`<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>`).

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Image elements do not have `[alt]` attributes that are redundant text.

●Identical links have the same purpose.

○`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 the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○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

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

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Deprecation / Warning	Source
SharedStorage	euob.sd19403.sonarsource.com/sxp/i/ec9ce1449fc9fe8879e7b666ca8b5629.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

Source	Description
about:srcdoc line 1, col 0	`Executing inline script violates the following Content Security Policy directive 'script-src 'nonce-IANARvNcsNB1xqUOnRwaiGG4ys+/q2wT' 'unsafe-eval' 'strict-dynamic' 'unsafe-inline' 'self' https: http:'. Note that 'unsafe-inline' is ignored if either a hash or nonce value is present in the source list. The action has been blocked.`

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Issue type
Content security policy

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.

●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

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

SEO

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

Content Best Practices

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

Link destination	Link Text
www.sonarsource.com/products/sonarqube/cloud/	Learn more
www.sonarsource.com/products/sonarqube/server/	Learn more
www.sonarsource.com/solutions/automated-code-review/	Learn more
www.sonarsource.com/solutions/ai/ai-codefix/	Learn more
www.sonarsource.com/knowledge/languages/go/	Go

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

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

Best Practices

SEO

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.09 s

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

1.15 s

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

240 ms

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

0.000

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

1.43 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.81 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

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

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

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

lhId: page-0-IMG

nodeLabel: section.css-hpd81o > div.css-9y8f5k > picture.css-gmxnb1 > img.css-nrwp77

path: 1,HTML,1,BODY,3,DIV,0,DIV,3,MAIN,0,DIV,12,SECTION,0,DIV,0,PICTURE,3,IMG

selector: section.css-hpd81o > div.css-9y8f5k > picture.css-gmxnb1 > img.css-nrwp77

snippet: <img decoding="async" alt="" loading="eager" srcset="https://assets-eu-01.kc-usercontent.com:443/ef593040-b591-0198-9506-ed88b3…" width="2240" height="1260" class="css-nrwp77 ed0xv1y0">

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.

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.

URL	Transfer Size	Duration
js.navattic.com/embeds.js	6.2 KiB	293 ms

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

Request	Cache TTL	Transfer Size
euob.sd19403.sonarsource.com/sxp/i/ec9ce1449fc9fe8879e7b666ca8b5629.js	43200.0 s	44.5 KiB
js.navattic.com/embeds.js	1800.0 s	6.2 KiB
cdn.equalweb.com/core/5.2.0/accessibility.js	2204800.0 s	15.5 KiB

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

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

Estimated savings: 362 ms

URL	Time Spent
www.sonarqube.org/	362 ms
www.sonarsource.com/products/sonarqube/	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.

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.

Diagnostics

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

Category	Time Spent
Script Evaluation	976 ms
Other	553 ms
Style & Layout	298 ms
Script Parsing & Compilation	218 ms
Parse HTML & CSS	47 ms
Garbage Collection	37 ms
Rendering	36 ms

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

Estimated savings: 0.0 ms 762.2 KiB

URL	Transfer Size	Est Savings
/c8f7fe3b0e41be846d5687592cf2018ff6e22687-72ade12da2482d7...	266.6 KiB	157.7 KiB
www.googletagmanager.com/gtag/js?id=G-9JZ0GZ5TC6	177.6 KiB	110.6 KiB
/035c3a5dbce655498ebf426080fef9033b4583db-393df6d1dadc0f6...	109.2 KiB	88.1 KiB
www.sonarsource.com/8833ea00-e34c0439f77f61bc800e.js	229.7 KiB	86.7 KiB
www.googletagmanager.com/gtag/js?id=AW-757017194&cx=c&gtm=4e6460	131.6 KiB	82.2 KiB
www.googletagmanager.com/gtm.js?id=GTM-56V34P9	177.9 KiB	75.9 KiB
www.sonarsource.com/commons-8890b03468a586edcd23.js	115.0 KiB	58.1 KiB
www.googletagmanager.com/gtag/js?id=G-9JZ0GZ5TC6&cx=c&gtm=4e6460	177.5 KiB	55.6 KiB
www.sonarsource.com/app-3172a3c071dab32cddeb.js	259.8 KiB	47.4 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

URL	Transfer Size
www.sonarsource.com/8833ea00-e34c0439f77f61bc800e.js	284.6 KiB
/c8f7fe3b0e41be846d5687592cf2018ff6e22687-72ade12da2482d7...	266.7 KiB
www.sonarsource.com/app-3172a3c071dab32cddeb.js	262.3 KiB
/ef593040-b591-0198-9506-ed88b30bc023/99827c23-f90b-4b51-...	259.0 KiB
www.googletagmanager.com/gtm.js?id=GTM-56V34P9	178.3 KiB
www.googletagmanager.com/gtag/js?id=G-9JZ0GZ5TC6	177.6 KiB
www.googletagmanager.com/gtag/js?id=G-9JZ0GZ5TC6&cx=c&gtm=4e6460	177.6 KiB
www.sonarsource.com/page-data/sq/d/3914656367.json	151.5 KiB
www.googletagmanager.com/gtag/js?id=AW-757017194&cx=c&gtm=4e6460	131.7 KiB
www.sonarsource.com/page-data/sq/d/809387045.json	118.3 KiB

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

	URL
language switcher `div#language-switcher > div.react-select__control > div.css-tj0ab2 > img`	www.sonarsource.com/assets/icon_language.svg

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

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●User Timing marks and measures 11 user timings

●JavaScript execution time 1.0 s

●Avoid long main-thread tasks 3 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 40 ms

●Server Backend Latencies 160 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 60 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○Avoid non-composited animations

Accessibility

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Failing Elements
Interactive demos `section.css-l1sqrk > ul.css-hpgf8j > li > a.etli69q0`
Pricing `section.css-l1sqrk > ul.css-hpgf8j > li > a.etli69q0`
ROI calculator `section.css-l1sqrk > ul.css-hpgf8j > li > a.etli69q0`
Contact sales `section.css-l1sqrk > ul.css-hpgf8j > li > a.etli69q0`

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Failing Elements
SonarQube products SonarQube Cloud Cloud-based static analysis tool for your CI… `nav.css-1fp82pj > ul.css-b5wfk1 > li.css-1j936iw > div.css-1r874ck`
Get started Onboarding hub Learning center Interactive demos Community SonarQub… `nav.css-1fp82pj > ul.css-b5wfk1 > li.css-1j936iw > div.css-1r874ck`
SonarQube Industry leading products SonarQube Server SonarQube Cloud SonarQube … `section.css-mf87fb > div.css-jlorxn > div.css-17nla5q > ul.css-y25j1f`

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Failing Elements
div.css-1nbar7y > section.css-1bavp3g > div.css-psrmlu > div `div.css-1nbar7y > section.css-1bavp3g > div.css-psrmlu > div`
div.css-1nbar7y > section.css-1d19qss > div.css-p8qmoh > div `div.css-1nbar7y > section.css-1d19qss > div.css-p8qmoh > div`

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.

Contrast

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

Failing Elements
Interactive demos `section.css-l1sqrk > ul.css-hpgf8j > li > a.etli69q0`
Pricing `section.css-l1sqrk > ul.css-hpgf8j > li > a.etli69q0`
ROI calculator `section.css-l1sqrk > ul.css-hpgf8j > li > a.etli69q0`
Contact sales `section.css-l1sqrk > ul.css-hpgf8j > li > a.etli69q0`

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Failing Elements
SonarQube Industry leading products SonarQube Server SonarQube Cloud SonarQube … `div.css-jlorxn > div.css-17nla5q > ul.css-y25j1f > li.css-10mbhcw`
Download `div.css-jlorxn > div.css-17nla5q > ul.css-y25j1f > li.css-10mbhcw`
Docs `div.css-jlorxn > div.css-17nla5q > ul.css-y25j1f > li.css-10mbhcw`
Pricing `div.css-jlorxn > div.css-17nla5q > ul.css-y25j1f > li.css-10mbhcw`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Navigation

Failing Elements
SAST `div.swiper > div.swiper-wrapper > div.swiper-slide > li#tab:R1ak3ah:0`
Taint analysis `div.swiper > div.swiper-wrapper > div.swiper-slide > li#tab:R1ak3ah:1`
Secrets detection `div.swiper > div.swiper-wrapper > div.swiper-slide > li#tab:R1ak3ah:2`
IaC scanning `div.swiper > div.swiper-wrapper > div.swiper-slide > li#tab:R1ak3ah:3`
Advanced SAST `div.swiper > div.swiper-wrapper > div.swiper-slide > li#tab:R1ak3ah:4`
SCA `div.swiper > div.swiper-wrapper > div.swiper-slide > li#tab:R1ak3ah:5`

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.

Failing Elements
Website Terms of Use `div.css-1go16d5 > ul.css-6w0507 > li.css-1dsq0w7 > a.e1u9akvp0`

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-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]`s are contained by their required parent element

●`[role]` values are valid

●`[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.

●`[accesskey]` values are unique

●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

●`<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>`).

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Image elements do not have `[alt]` attributes that are redundant text.

●Identical links have the same purpose.

○`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 the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○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

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

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Deprecation / Warning	Source
SharedStorage	euob.sd19403.sonarsource.com/sxp/i/ec9ce1449fc9fe8879e7b666ca8b5629.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

Source	Description
about:srcdoc line 1, col 0	`Executing inline script violates the following Content Security Policy directive 'script-src 'nonce-dcfLEEc5pM/R+gXIK08HH0188B08sLRF' 'unsafe-eval' 'strict-dynamic' 'unsafe-inline' 'self' https: http:'. Note that 'unsafe-inline' is ignored if either a hash or nonce value is present in the source list. The action has been blocked.`

Issue type
Content security policy

●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

●Ensure CSP is effective against XSS attacks

●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

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

SEO

Content Best Practices

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

Link destination	Link Text
www.sonarsource.com/products/sonarqube/cloud/	Learn more
www.sonarsource.com/products/sonarqube/server/	Learn more
www.sonarsource.com/solutions/automated-code-review/	Learn more
www.sonarsource.com/solutions/ai/ai-codefix/	Learn more
www.sonarsource.com/knowledge/languages/go/	Go

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

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Browse & Analyze

Learn

Results for https://www.sonarqube.org

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Tables and lists

Navigation

Best practices

Best Practices

General

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Contrast

Tables and lists

Navigation

Best practices

Best Practices

General

SEO

Content Best Practices

Keyboard Shortcuts