C — https://cpanel.net | BeaverCheck Audit

Site Health

Score: 78 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Good foundation, but a few gaps could be exploited.

Mostly accessible, but some users still face barriers.

Well-optimized for search — your content is discoverable.

Good server performance with room for optimization.

Strong compliance posture across regulations.

Rich content metadata — your pages look great everywhere.

Reasonable footprint with room for optimization.

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

WooCommerce sites average 76

At average

Better than 50% of WooCommerce sites See full WooCommerce benchmark →

WordPress sites average 74

At average

Better than 75% of WordPress sites See full WordPress benchmark →

Top Priorities (5)

Content-Security-Policy header is missing

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

Security › Security Headers

No Content-Security-Policy header found

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

Security › Content Security Policy

77 third-party resources (100% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory

Cross-Origin-Embedder-Policy header is missing

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

Security › Security Headers

Cross-Origin-Opener-Policy header is missing

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

Security › Security Headers

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fcpanel.net)](https://beavercheck.com/results/4f691fd4-b888-41ce-b8ca-aeca8fcbd3f0)

HTML

<a href="https://beavercheck.com/results/4f691fd4-b888-41ce-b8ca-aeca8fcbd3f0"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fcpanel.net" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fcpanel.net

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 13.3s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Addressing the critical issues below would have the most immediate impact on your user trust.

4 security gaps detected — browsers may warn visitors about your site.

Your LCP is 13.3s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.

Could reach Estimate based on resolving critical issues

Conversion Barriers

3 critical 3 warning

6 barrier(s) likely increasing bounce by ~29%.

Speed (2)

Page takes 13.3s to load

+12% bounce

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

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

Page feels frozen for 1.1s

+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

Content (1)

Content is hard to read

+2% bounce

Graduate-level reading difficulty — limits the addressable audience for product or blog pages

Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60

Navigation (1)

10 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

$400 investment → $0.34/month returns + USD 7,500 risk avoided

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

Investment

$400

4h · 5 findings

Monthly returns

$0.34 /mo

~$4.07 / year

Bandwidth savings $0.34

Regulatory risk avoided

USD 7,500

if kept compliant

CCPA/CPRA USD 7,500

$200 — 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

$400

4.0 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins

$200 4 fixes in ~120 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$625 / month at risk

~$7,504 / year if left unfixed

Compliance Risk

$7,500

CCPA/CPRA

No privacy policy link detected
CCPA/CPRA: USD 2,500 – USD 7,500
Trackers detected but no cookie policy found
CCPA/CPRA: USD 2,500 – USD 7,500
Trackers detected but no privacy policy found
CCPA/CPRA: USD 2,500 – USD 7,500

Bandwidth Waste

$0.34 /mo

4239.7 MB/mo × 0.080 USD/GB

Optimize transfer: save ~424 KB per page load
Saves $0.34/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

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

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

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.

6.37 s

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

13.27 s

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

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

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

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

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.

Request	Cache TTL	Transfer Size
web.cmp.usercentrics.eu/ui/TvGdprCmpView.f8e69ac0.js	3600.0 s	29.4 KiB
/dcdn/settings.js?a=935671&settings_type=4&ts=1776359155&...	1800.0 s	16.7 KiB
web.cmp.usercentrics.eu/ui/loader.js	3600.0 s	15.7 KiB
www.cpanel.net/cdn-cgi/challenge-platform/h/g/scripts/jsd/b0a7532ac8ec/main.js?	14400.0 s	12.3 KiB
cdn.equalweb.com/core/5.1.13/accessibility.js	2204800.0 s	15.3 KiB
app.usercentrics.eu/session/1px.png?settingsId=PJ69cPpIj3bskN	1800.0 s	1.0 KiB
static.addtoany.com/menu/page.js	86400.0 s	2.2 KiB
/eu01/v.gif?cd=0&a=935671&d=cpanel.net&u=DF858FB763B58ADB...	43200.0 s	147 B

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
www.cpanel.net/wp-content/themes/bricks/assets/fonts/ionicons/ionicons.woff2	25 ms
/wp-content/themes/bricks/assets/fonts/fontawesome/fa-bra...	20 ms

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
Screenshot of web hosting management interfaces, showing a WHM dashboard and a … `section#brxe-fxgovh > div#brxe-hklecu > div.brxe-block > img.brxe-image`	www.cpanel.net/wp-content/uploads/2025/07/latest-Home-Hero-Image-768x536.webp	39.9 KiB	30.9 KiB
See What’s Next in Hosting - Get the 2026 Web Hosting Trends Report Download Now `body.home > header#brx-header > div#brxe-0fc72e`	www.cpanel.net/wp-content/uploads/2025/12/banner-bg-mobile.png	18.5 KiB	12.6 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:364.2399998779297 label:Time to first byte subpart:timeToFirstByte] map[duration:1205.0670001220703 label:Resource load delay subpart:resourceLoadDelay] map[duration:19.091 label:Resource load duration subpart:resourceLoadDuration] map[duration:990.121 label:Element render delay subpart:elementRenderDelay]]

lhId: page-2-SECTION

nodeLabel: Simplify Server & Website Management Streamline your workflow with cPanel’s po…

path: 1,HTML,1,BODY,7,MAIN,0,SECTION

selector: body.home > main#brx-content > section#brxe-fxgovh

snippet: <section id="brxe-fxgovh" class="brxe-section">

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-2-SECTION

nodeLabel: Simplify Server & Website Management Streamline your workflow with cPanel’s po…

path: 1,HTML,1,BODY,7,MAIN,0,SECTION

selector: body.home > main#brx-content > section#brxe-fxgovh

snippet: <section id="brxe-fxgovh" class="brxe-section">

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.

URL	Transfer Size	Duration
/wp-content/themes/bricks/assets/css/libs/swiper-layer.mi...	1.5 KiB	495 ms
www.cpanel.net/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.1	4.8 KiB	334 ms
www.cpanel.net/wp-includes/js/jquery/jquery.min.js?ver=3.7.1	29.3 KiB	979 ms
www.cpanel.net/wp-content/plugins/add-to-any/addtoany.min.css?ver=1.16	717 B	495 ms
/wp-content/themes/bricks/assets/css/frontend-layer.min.c...	20.0 KiB	818 ms
/wp-content/themes/bricks/assets/css/libs/isotope-layer.m...	506 B	173 ms
/wp-content/themes/bricks/assets/css/libs/ionicons-layer....	4.7 KiB	657 ms
/wp-content/themes/bricks/assets/css/libs/splide-layer.mi...	1.2 KiB	173 ms
www.cpanel.net/wp-content/themes/bricks-child/style.css?ver=1.002	407 B	495 ms
/wp-content/themes/bricks/assets/css/libs/font-awesome-6-...	4.7 KiB	657 ms

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 915 ms

URL	Time Spent
cpanel.net/	915 ms
www.cpanel.net/	0.0 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Reduce unused 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

Estimated savings: 1.5 s 230.5 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtm.js?id=GTM-WB4LHQ4	169.2 KiB	64.9 KiB
www.googletagmanager.com/gtag/js?id=G-JD73TMP2E6&cx=c&gtm=4e64f0&bs=ctrl	178.1 KiB	61.1 KiB
web.cmp.usercentrics.eu/ui/v/3.114.0/WebSdk.lib.c9b98563.js	56.0 KiB	35.7 KiB
www.cpanel.net/wp-content/themes/bricks/assets/js/bricks.min.js?ver=1774532260	34.1 KiB	26.5 KiB
www.cpanel.net/wp-content/themes/bricks/assets/js/libs/swiper.min.js?ver=8.4.4	37.2 KiB	21.2 KiB
static.addtoany.com/menu/modules/core.ydpp7jcu.js	25.8 KiB	21.1 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
www.cpanel.net/	1.6 s	805 ms	158 ms
Unattributable	604 ms	49 ms	0.0 ms
www.googletagmanager.com/gtag/js?id=G-JD73TMP2E6&cx=c&gtm=4e64f0&bs=ctrl	594 ms	421 ms	80 ms
www.cpanel.net/wp-content/themes/bricks/assets/js/bricks.min.js?ver=1774532260	492 ms	270 ms	17 ms
www.cpanel.net/cdn-cgi/challenge-platform/scripts/jsd/main.js	377 ms	344 ms	3.4 ms
www.googletagmanager.com/gtm.js?id=GTM-WB4LHQ4	372 ms	296 ms	66 ms
web.cmp.usercentrics.eu/ui/v/3.114.0/WebSdk.lib.c9b98563.js	186 ms	142 ms	38 ms
cdn.equalweb.com/core/5.1.13/accessibility.js	157 ms	116 ms	7.7 ms
web.cmp.usercentrics.eu/ui/v/3.114.0/UcGdprCmpView.c071ab9b.js	136 ms	47 ms	10 ms
www.cpanel.net/wp-includes/js/jquery/jquery.min.js?ver=3.7.1	110 ms	94 ms	10 ms
www.cpanel.net/wp-content/themes/bricks/assets/js/libs/swiper.min.js?ver=8.4.4	89 ms	4.5 ms	16 ms
web.cmp.usercentrics.eu/ui/v/3.114.0/GdprCmpController.98dde46a.js	61 ms	36 ms	4.2 ms
web.cmp.usercentrics.eu/ui/v/3.114.0/getToastifyStyle.4f0a73d7.js	53 ms	52 ms	0.5 ms
web.cmp.usercentrics.eu/ui/loader.js	51 ms	25 ms	6.8 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	2.8 s
Other	917 ms
Style & Layout	593 ms
Script Parsing & Compilation	469 ms
Garbage Collection	111 ms
Parse HTML & CSS	110 ms
Rendering	87 ms

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 17.2 KiB

URL	Transfer Size	Est Savings
.overlay { --color-cmp-overlay: #333333; --feature-overlay-opacity: 0.7; } …	18.6 KiB	17.2 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
cPanel `div#brxe-aydtju > div#brxe-atbyoo > a#brxe-pjqalq > img.bricks-site-logo`	www.cpanel.net/wp-content/uploads/2025/06/logo-cPanel-footer.svg
cPanel `div#brxe-221d17 > div#brxe-538b27 > a#brxe-c20ab9 > img.bricks-site-logo`	www.cpanel.net/wp-content/uploads/2025/06/logo-cPanel-header.svg

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

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,380 KiB

●User Timing marks and measures 5 user timings

●Avoid long main-thread tasks 16 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 40 ms

●Server Backend Latencies 110 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○Avoid non-composited animations

○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 roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Streamline your workflow with cPanel’s powerful automation, flexible customizat… `section#brxe-fxgovh > div#brxe-hklecu > div#brxe-xygklq > div#brxe-jwutys`

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Accept All `footer#uc-cmp-footer > div.buttons > div.buttons-row > button#accept`
Deny `footer#uc-cmp-footer > div.buttons > div.buttons-row > button#deny`

These are opportunities to improve the legibility of your content.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Press for Accessibility for blind people who use screen readers `div#INDquickAccess > ul > li > button.INDshortcutBtn`
Press for Accessibility menu `div#INDquickAccess > ul > li > button`

These are opportunities to improve keyboard navigation in your application.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Download Now `header#brx-header > div#brxe-0fc72e > div.brxe-div > a#brxe-nawhgc`
Sign Up `section.brxe-section > div#brxe-jdctqd > div#brxe-mquilc > a#brxe-exsnpk`
Partner Requirements `ul#brxe-itryer > li > div.content > a`
Support Agreement `ul#brxe-itryer > li > div.content > a`

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

●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

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

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

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

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Touch targets have sufficient size and spacing.

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

●Identical links have the same purpose.

○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

○Form elements have associated labels

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
SharedStorage	www.cpanel.net/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	www.cpanel.net/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge	www.cpanel.net/cdn-cgi/challenge-platform/scripts/jsd/main.js

●Uses HTTPS

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

SEO

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

Content Best Practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
/blog/products/the-next-evolution-of-cpanel-built-in-ai-f...	Read More

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

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

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

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

1.81 s

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

16 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.68 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.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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 ▾

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.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-SECTION

nodeLabel: Simplify Server & Website Management Streamline your workflow with cPanel’s po…

path: 1,HTML,1,BODY,7,MAIN,0,SECTION

selector: body.home > main#brx-content > section#brxe-fxgovh

snippet: <section id="brxe-fxgovh" class="brxe-section">

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.

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.

URL	Transfer Size	Duration
www.cpanel.net/wp-includes/js/jquery/jquery.min.js?ver=3.7.1	29.3 KiB	278 ms
www.cpanel.net/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.1	4.8 KiB	169 ms
/wp-content/themes/bricks/assets/css/libs/isotope-layer.m...	506 B	169 ms
/wp-content/themes/bricks/assets/css/libs/font-awesome-6-...	4.7 KiB	169 ms
/wp-content/themes/bricks/assets/css/frontend-layer.min.c...	20.0 KiB	223 ms
www.cpanel.net/wp-content/plugins/add-to-any/addtoany.min.css?ver=1.16	717 B	169 ms
/wp-content/themes/bricks/assets/css/libs/splide-layer.mi...	1.2 KiB	169 ms
/wp-content/themes/bricks/assets/css/libs/ionicons-layer....	4.7 KiB	169 ms
/wp-content/themes/bricks/assets/css/libs/swiper-layer.mi...	1.5 KiB	169 ms
www.cpanel.net/wp-content/themes/bricks-child/style.css?ver=1.002	407 B	169 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
web.cmp.usercentrics.eu/ui/TvGdprCmpView.f8e69ac0.js	3600.0 s	29.4 KiB
/dcdn/settings.js?a=935671&settings_type=4&ts=1776359155&...	1800.0 s	16.6 KiB
web.cmp.usercentrics.eu/ui/loader.js	3600.0 s	15.7 KiB
www.cpanel.net/cdn-cgi/challenge-platform/h/g/scripts/jsd/b0a7532ac8ec/main.js?	14400.0 s	13.4 KiB
cdn.equalweb.com/core/5.1.13/accessibility.js	2204800.0 s	15.3 KiB
static.addtoany.com/menu/page.js	86400.0 s	2.2 KiB
app.usercentrics.eu/session/1px.png?settingsId=PJ69cPpIj3bskN	1800.0 s	1.0 KiB
/eu01/v.gif?cd=0&a=935671&d=cpanel.net&u=DB352F70FD1951C4...	43200.0 s	147 B

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
www.cpanel.net/wp-content/themes/bricks/assets/fonts/ionicons/ionicons.woff2	20 ms
/wp-content/themes/bricks/assets/fonts/fontawesome/fa-bra...	20 ms

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
Screenshot of web hosting management interfaces, showing a WHM dashboard and a … `section#brxe-fxgovh > div#brxe-hklecu > div.brxe-block > img.brxe-image`	www.cpanel.net/wp-content/uploads/2025/07/latest-Home-Hero-Image-1024x715.webp	61.3 KiB	38.3 KiB

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 334 ms

URL	Time Spent
cpanel.net/	334 ms
www.cpanel.net/	0.0 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

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

Why this matters

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

Learn more ▾

Source: Google web.dev / Lighthouse

Estimated savings: 80 ms 230.4 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtm.js?id=GTM-WB4LHQ4	169.2 KiB	64.3 KiB
www.googletagmanager.com/gtag/js?id=G-JD73TMP2E6&cx=c&gtm=4e64f0	178.1 KiB	61.8 KiB
web.cmp.usercentrics.eu/ui/v/3.114.0/WebSdk.lib.c9b98563.js	56.0 KiB	35.7 KiB
www.cpanel.net/wp-content/themes/bricks/assets/js/bricks.min.js?ver=1774532260	34.1 KiB	26.5 KiB
static.addtoany.com/menu/modules/core.ydpp7jcu.js	25.8 KiB	21.1 KiB
www.cpanel.net/wp-content/themes/bricks/assets/js/libs/swiper.min.js?ver=8.4.4	37.2 KiB	21.1 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 13.4 KiB

URL	Transfer Size	Est Savings
.overlay { --color-cmp-overlay: #333333; --feature-overlay-opacity: 0.7; } …	14.3 KiB	13.4 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
cPanel `div#brxe-aydtju > div#brxe-atbyoo > a#brxe-pjqalq > img.bricks-site-logo`	www.cpanel.net/wp-content/uploads/2025/06/logo-cPanel-footer.svg
cPanel `div#brxe-221d17 > div#brxe-538b27 > a#brxe-c20ab9 > img.bricks-site-logo`	www.cpanel.net/wp-content/uploads/2025/06/logo-cPanel-header.svg

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

●Max Potential First Input Delay 80 ms

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,385 KiB

●User Timing marks and measures 5 user timings

●JavaScript execution time 0.7 s

●Minimizes main-thread work 1.3 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 360 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○Avoid non-composited animations

○Avoid large layout shifts

Accessibility

ARIA

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Streamline your workflow with cPanel’s powerful automation, flexible customizat… `section#brxe-fxgovh > div#brxe-hklecu > div#brxe-xygklq > div#brxe-jwutys`

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Deny `footer#uc-cmp-footer > div.buttons > div.buttons-row > button#deny`
Accept All `footer#uc-cmp-footer > div.buttons > div.buttons-row > button#accept`

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Facebook link (opens in a new tab) `div#brxe-wywpre > div#brxe-aydtju > ul#brxe-llnnrz > li.repeater-item`
Twitter X link (opens in a new tab) `div#brxe-wywpre > div#brxe-aydtju > ul#brxe-llnnrz > li.repeater-item`
Instagram link (opens in a new tab) `div#brxe-wywpre > div#brxe-aydtju > ul#brxe-llnnrz > li.repeater-item`
LinkedIn link (opens in a new tab) `div#brxe-wywpre > div#brxe-aydtju > ul#brxe-llnnrz > li.repeater-item`
YouTube link (opens in a new tab) `div#brxe-wywpre > div#brxe-aydtju > ul#brxe-llnnrz > li.repeater-item`
Reddit link (opens in a new tab) `div#brxe-wywpre > div#brxe-aydtju > ul#brxe-llnnrz > li.repeater-item`

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

Navigation

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Press enter for Accessibility for blind people who use screen readers `div#INDquickAccess > ul > li > button.INDshortcutBtn`
Press enter for Keyboard Navigation `div#INDquickAccess > ul > li > button`
Press enter for Accessibility menu `div#INDquickAccess > ul > li > button`

These are opportunities to improve keyboard navigation in your application.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Download Now `header#brx-header > div#brxe-0fc72e > div.brxe-div > a#brxe-nawhgc`
Sign Up `section.brxe-section > div#brxe-jdctqd > div#brxe-mquilc > a#brxe-exsnpk`
Partner Requirements `ul#brxe-itryer > li > div.content > a`
Support Agreement `ul#brxe-itryer > li > div.content > a`

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●`[accesskey]` values are unique

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

●Touch targets have sufficient size and spacing.

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

●Identical links have the same purpose.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

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

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

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

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

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

○ARIA IDs are unique

○No form fields have multiple labels

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

○Form elements have associated labels

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
SharedStorage	www.cpanel.net/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	www.cpanel.net/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge	www.cpanel.net/cdn-cgi/challenge-platform/scripts/jsd/main.js

●Uses HTTPS

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

SEO

Content Best Practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
/blog/products/the-next-evolution-of-cpanel-built-in-ai-f...	Read More

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

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Results for https://cpanel.net

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Speed (2)

Trust (2)

Content (1)

Navigation (1)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Contrast

Navigation

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

General

SEO

Content Best Practices

Keyboard Shortcuts