C — https://web.com | BeaverCheck Audit

Site Health

Score: 71 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Missing signals may be hurting your search visibility.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Good content signals with minor gaps.

Lean and efficient — low environmental impact per visit.

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

AngularJS · 324 peers

You 71

Avg 73

At average

0 50 100

Better than 24% of AngularJS sites See full AngularJS benchmark →

Cloudflare Turnstile · 337 peers

You 71

Avg 73

At average

0 50 100

Better than 23% of Cloudflare Turnstile sites See full Cloudflare Turnstile 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

1 link(s) with no accessible text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality

No H1 heading found

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Heading Hierarchy

No favicon or icon links detected

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Favicon & Branding

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%2Fweb.com)](https://beavercheck.com/results/031ba455-0efb-4ec9-bc53-6eee0a71c70f)

HTML

<a href="https://beavercheck.com/results/031ba455-0efb-4ec9-bc53-6eee0a71c70f"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fweb.com" alt="BeaverCheck Score"></a>

Image URL

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

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. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. 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.

3 accessibility issues exclude users who rely on assistive technology.

Conversion Barriers

2 critical 4 warning

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

Speed (2)

Page takes 9.4s to load

+12% bounce

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

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

Page feels frozen for 988ms

+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 (1)

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

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

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

Return on Investment

$550 investment → $6,232/month returns + USD 157,500 risk avoided

Payback period: < 1 month First-year ROI: +13496%

Investment

$550

6h · 5 findings

Monthly returns

$6,232 /mo

~$74,779 / year

Conversions recovered $6,231
Bandwidth savings $0.22

Regulatory risk avoided

USD 157,500

if kept compliant

ADA Title III USD 150,000
CCPA/CPRA USD 7,500

Payback period

0 12mo 24mo

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

$550

5.5 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins

$100 2 fixes in ~60 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

$13,125 / month at risk

~$157,503 / year if left unfixed

Compliance Risk

$157,500

ADA Title IIICCPA/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

+5 more

Bandwidth Waste

$0.22 /mo

2794.0 MB/mo × 0.080 USD/GB

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

100

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.

4.41 s

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

9.37 s

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

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

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

9.37 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
/etc.clientlibs/netsol/clientlibs/clientlib-footer.min.61...	0.0 ms	224.1 KiB
assets.adobedtm.com/530368109655/f1f8bc547915/launch-7859547d8660.min.js	3600.0 s	208.2 KiB
cdn.cookielaw.org/scripttemplates/202503.2.0/otBannerSdk.js	86400.0 s	117.4 KiB
/etc.clientlibs/clientlibs/granite/jquery.min.3e24d4d067a...	0.0 ms	35.7 KiB
www.web.com/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/main.js?	14400.0 s	13.4 KiB
www.web.com/sitegeneration/static/js/main.0b8c80c3.js	1382400.0 s	80.6 KiB
/etc.clientlibs/foundation/clientlibs/shared.min.e9d9a399...	0.0 ms	7.5 KiB
/etc.clientlibs/foundation/clientlibs/main.min.be53d5d2ac...	0.0 ms	3.9 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js	86400.0 s	9.1 KiB
/etc.clientlibs/clientlibs/granite/utils.min.899004cc02c3...	0.0 ms	3.6 KiB
/etc.clientlibs/netsol/clientlibs/clientlib-footer.min.c9...	0.0 ms	2.5 KiB
/etc.clientlibs/foundation/clientlibs/main.min.b4994788cf...	0.0 ms	2.4 KiB
/etc.clientlibs/clientlibs/granite/jquery/granite.min.011...	0.0 ms	2.0 KiB
/etc.clientlibs/core/wcm/components/image/v3/image/client...	0.0 ms	2.0 KiB
/530368109655/f1f8bc547915/0563f6e328b6/RC5041a97a0dc7412...	3600.0 s	621 B
/etc.clientlibs/foundation/clientlibs/jquery.min.dd9b395c...	0.0 ms	392 B
www.web.com/sitegeneration/static/css/main.1700c2af.css	1382400.0 s	3.6 KiB
/content/experience-fragments/netsol/site-header/master/j...	1382400.0 s	2.2 KiB
www.web.com/sitegeneration/icons/help-icon.svg	1382400.0 s	541 B
www.web.com/sitegeneration/icons/account-circle-icon.svg	1382400.0 s	431 B
www.web.com/sitegeneration/icons/arrow-up.svg	1382400.0 s	229 B

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-IMG

nodeLabel: art

path: 1,HTML,1,BODY,1,DIV,1,MAIN,1,SECTION,0,DIV,1,DIV,0,DIV,0,IMG

selector: div.vs-page-container > div.vs-page-content > div.vs-left-art > img.vs-left-img

snippet: <img alt="art" class="vs-left-img" src="https://www.register.com/search/assets/support-desktop-8.svg">

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
www.web.com/sitegeneration/static/css/main.1700c2af.css	3.6 KiB	151 ms
/css2?family=Open+Sans:ital,wght@0,300..800;1,300..800&di...	2.2 KiB	811 ms

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.

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: 756 ms

URL	Time Spent
web.com/	756 ms
www.web.com/	0.0 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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 ▾

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.4 s 210.6 KiB

URL	Transfer Size	Est Savings
assets.adobedtm.com/530368109655/f1f8bc547915/launch-7859547d8660.min.js	207.9 KiB	78.4 KiB
cdn.cookielaw.org/scripttemplates/202503.2.0/otBannerSdk.js	117.1 KiB	70.8 KiB
www.web.com/sitegeneration/static/js/main.0b8c80c3.js	80.5 KiB	38.4 KiB
/etc.clientlibs/clientlibs/granite/jquery.min.3e24d4d067a...	35.4 KiB	23.0 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
assets.adobedtm.com/530368109655/f1f8bc547915/launch-7859547d8660.min.js	563 ms	421 ms	122 ms
www.web.com/cdn-cgi/challenge-platform/scripts/jsd/main.js	419 ms	289 ms	4.0 ms
Unattributable	384 ms	59 ms	0.0 ms
/etc.clientlibs/netsol/clientlibs/clientlib-footer.min.61...	302 ms	191 ms	99 ms
www.web.com/sitegeneration/static/js/main.0b8c80c3.js	284 ms	227 ms	39 ms
cdn.cookielaw.org/scripttemplates/202503.2.0/otBannerSdk.js	223 ms	77 ms	60 ms
www.web.com/	146 ms	40 ms	2.2 ms
/etc.clientlibs/clientlibs/granite/jquery.min.3e24d4d067a...	115 ms	48 ms	13 ms
cdn.cookielaw.org/scripttemplates/otSDKStub.js	52 ms	34 ms	3.3 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	1.4 s
Other	419 ms
Script Parsing & Compilation	360 ms
Style & Layout	273 ms
Parse HTML & CSS	34 ms
Garbage Collection	29 ms
Rendering	27 ms

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
art `div.vs-page-container > div.vs-page-content > div.vs-left-art > img.vs-left-img`	www.register.com/search/assets/support-desktop-8.svg
Network Solutions Logo `header.ns-header > div.ns-header-container > a.ns-logo-link > img.ns-logo-img`	/content/experience-fragments/netsol/site-header/master/_...
arrow icon `section.prompt-suggestions-section > div.prompt-suggestions-container > button.suggestion-pill > img.pill-arrow-icon`	www.web.com/sitegeneration/icons/arrow-up.svg
arrow icon `section.prompt-suggestions-section > div.prompt-suggestions-container > button.suggestion-pill > img.pill-arrow-icon`	www.web.com/sitegeneration/icons/arrow-up.svg
arrow icon `section.prompt-suggestions-section > div.prompt-suggestions-container > button.suggestion-pill > img.pill-arrow-icon`	www.web.com/sitegeneration/icons/arrow-up.svg
arrow icon `section.prompt-suggestions-section > div.prompt-suggestions-container > button.suggestion-pill > img.pill-arrow-icon`	www.web.com/sitegeneration/icons/arrow-up.svg
arrow icon `section.prompt-suggestions-section > div.prompt-suggestions-container > button.suggestion-pill > img.pill-arrow-icon`	www.web.com/sitegeneration/icons/arrow-up.svg
arrow icon `section.prompt-suggestions-section > div.prompt-suggestions-container > button.suggestion-pill > img.pill-arrow-icon`	www.web.com/sitegeneration/icons/arrow-up.svg
arrow icon `section.prompt-suggestions-section > div.prompt-suggestions-container > button.suggestion-pill > img.pill-arrow-icon`	www.web.com/sitegeneration/icons/arrow-up.svg
arrow icon `section.prompt-suggestions-section > div.prompt-suggestions-container > button.suggestion-pill > img.pill-arrow-icon`	www.web.com/sitegeneration/icons/arrow-up.svg
arrow icon `section.prompt-suggestions-section > div.prompt-suggestions-container > button.suggestion-pill > img.pill-arrow-icon`	www.web.com/sitegeneration/icons/arrow-up.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

●Avoids enormous network payloads Total size was 910 KiB

●Avoid long main-thread tasks 8 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 200 ms

●Server Backend Latencies 420 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○User Timing marks and measures

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

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
All in one, working together for you `div.better-together-content > div.better-together-reasons > div.reason-item > h3.reason-title`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
header.ns-header > div.ns-header-container > nav.ns-nav > a.ns-nav-link `header.ns-header > div.ns-header-container > nav.ns-nav > a.ns-nav-link`
div.footerCenter > div.footerCenter__left > div.footerCenter__left__logo > a `div.footerCenter > div.footerCenter__left > div.footerCenter__left__logo > a`
div.footerCenter__right > div.footerCenter__right > div.footerCenter__right__item > a.footerCenter__right__item__link `div.footerCenter__right > div.footerCenter__right > div.footerCenter__right__item > a.footerCenter__right__item__link`
div.footerCenter__right > div.footerCenter__right > div.footerCenter__right__item > a.footerCenter__right__item__link `div.footerCenter__right > div.footerCenter__right > div.footerCenter__right__item > a.footerCenter__right__item__link`
div.footerCenter__right > div.footerCenter__right > div.footerCenter__right__item > a.footerCenter__right__item__link `div.footerCenter__right > div.footerCenter__right > div.footerCenter__right__item > a.footerCenter__right__item__link`
div.footerCenter__right > div.footerCenter__right > div.footerCenter__right__item > a.footerCenter__right__item__link `div.footerCenter__right > div.footerCenter__right > div.footerCenter__right__item > a.footerCenter__right__item__link`
div.footerCenter__right > div.footerCenter__right > div.footerCenter__right__item > a.footerCenter__right__item__link `div.footerCenter__right > div.footerCenter__right > div.footerCenter__right__item > a.footerCenter__right__item__link`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

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
.site .website .space Get your personal domain $1.99*/ first year `div.domain-search > div.domain-search__container > div#domainAd > a#domainAd`
Cookie Notice `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link`

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

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

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

●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

○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

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

○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.web.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	www.web.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge	www.web.com/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 clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

100

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.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○robots.txt is valid

○Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

Best Practices

100

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

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

1.80 s

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

74 ms

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

0.011

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

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

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

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
/etc.clientlibs/netsol/clientlibs/clientlib-footer.min.61...	0.0 ms	224.1 KiB
assets.adobedtm.com/530368109655/f1f8bc547915/launch-7859547d8660.min.js	3600.0 s	208.2 KiB
cdn.cookielaw.org/scripttemplates/202503.2.0/otBannerSdk.js	86400.0 s	117.4 KiB
/etc.clientlibs/clientlibs/granite/jquery.min.3e24d4d067a...	0.0 ms	35.9 KiB
www.web.com/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/main.js?	14400.0 s	12.1 KiB
www.web.com/sitegeneration/static/js/main.0b8c80c3.js	1382400.0 s	80.7 KiB
/etc.clientlibs/foundation/clientlibs/shared.min.e9d9a399...	0.0 ms	7.4 KiB
/etc.clientlibs/foundation/clientlibs/main.min.be53d5d2ac...	0.0 ms	3.7 KiB
/etc.clientlibs/clientlibs/granite/utils.min.899004cc02c3...	0.0 ms	3.6 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js	86400.0 s	9.1 KiB
/etc.clientlibs/netsol/clientlibs/clientlib-footer.min.c9...	0.0 ms	2.5 KiB
/etc.clientlibs/foundation/clientlibs/main.min.b4994788cf...	0.0 ms	2.2 KiB
/etc.clientlibs/core/wcm/components/image/v3/image/client...	0.0 ms	2.0 KiB
/etc.clientlibs/clientlibs/granite/jquery/granite.min.011...	0.0 ms	1.9 KiB
/etc.clientlibs/foundation/clientlibs/jquery.min.dd9b395c...	0.0 ms	622 B
/530368109655/f1f8bc547915/0563f6e328b6/RC5041a97a0dc7412...	3600.0 s	621 B
www.web.com/sitegeneration/static/css/main.1700c2af.css	1382400.0 s	3.5 KiB
/content/experience-fragments/netsol/site-header/master/j...	1382400.0 s	2.1 KiB
www.web.com/sitegeneration/icons/help-icon.svg	1382400.0 s	426 B
www.web.com/sitegeneration/icons/account-circle-icon.svg	1382400.0 s	407 B
www.web.com/sitegeneration/icons/arrow-up.svg	1382400.0 s	353 B

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-IMG

nodeLabel: art

path: 1,HTML,1,BODY,1,DIV,1,MAIN,1,SECTION,0,DIV,1,DIV,0,DIV,0,IMG

selector: div.vs-page-container > div.vs-page-content > div.vs-left-art > img.vs-left-img

snippet: <img alt="art" class="vs-left-img" src="https://www.register.com/search/assets/support-desktop-8.svg">

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.web.com/sitegeneration/static/css/main.1700c2af.css	3.5 KiB
/css2?family=Open+Sans:ital,wght@0,300..800;1,300..800&di...	2.2 KiB	273 ms

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.

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

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: 160 ms 210.5 KiB

URL	Transfer Size	Est Savings
assets.adobedtm.com/530368109655/f1f8bc547915/launch-7859547d8660.min.js	207.9 KiB	78.4 KiB
cdn.cookielaw.org/scripttemplates/202503.2.0/otBannerSdk.js	117.1 KiB	70.8 KiB
www.web.com/sitegeneration/static/js/main.0b8c80c3.js	80.6 KiB	38.3 KiB
/etc.clientlibs/clientlibs/granite/jquery.min.3e24d4d067a...	35.4 KiB	23.0 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
art `div.vs-page-container > div.vs-page-content > div.vs-left-art > img.vs-left-img`	www.register.com/search/assets/support-desktop-8.svg
Network Solutions Logo `header.ns-header > div.ns-header-container > a.ns-logo-link > img.ns-logo-img`	/content/experience-fragments/netsol/site-header/master/_...
arrow icon `section.prompt-suggestions-section > div.prompt-suggestions-container > button.suggestion-pill > img.pill-arrow-icon`	www.web.com/sitegeneration/icons/arrow-up.svg
arrow icon `section.prompt-suggestions-section > div.prompt-suggestions-container > button.suggestion-pill > img.pill-arrow-icon`	www.web.com/sitegeneration/icons/arrow-up.svg
arrow icon `section.prompt-suggestions-section > div.prompt-suggestions-container > button.suggestion-pill > img.pill-arrow-icon`	www.web.com/sitegeneration/icons/arrow-up.svg
arrow icon `section.prompt-suggestions-section > div.prompt-suggestions-container > button.suggestion-pill > img.pill-arrow-icon`	www.web.com/sitegeneration/icons/arrow-up.svg
arrow icon `section.prompt-suggestions-section > div.prompt-suggestions-container > button.suggestion-pill > img.pill-arrow-icon`	www.web.com/sitegeneration/icons/arrow-up.svg
arrow icon `section.prompt-suggestions-section > div.prompt-suggestions-container > button.suggestion-pill > img.pill-arrow-icon`	www.web.com/sitegeneration/icons/arrow-up.svg
arrow icon `section.prompt-suggestions-section > div.prompt-suggestions-container > button.suggestion-pill > img.pill-arrow-icon`	www.web.com/sitegeneration/icons/arrow-up.svg
arrow icon `section.prompt-suggestions-section > div.prompt-suggestions-container > button.suggestion-pill > img.pill-arrow-icon`	www.web.com/sitegeneration/icons/arrow-up.svg
arrow icon `section.prompt-suggestions-section > div.prompt-suggestions-container > button.suggestion-pill > img.pill-arrow-icon`	www.web.com/sitegeneration/icons/arrow-up.svg

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

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: 205 ms

URL	Time Spent
web.com/	205 ms
www.web.com/	0.0 ms

●Max Potential First Input Delay 110 ms

●Time to Interactive 1.9 s

●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

●Avoids enormous network payloads Total size was 909 KiB

●JavaScript execution time 0.4 s

●Minimizes main-thread work 0.8 s

●Avoid long main-thread tasks 2 long tasks found

●Avoid non-composited animations 1 animated element found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 200 ms

●Server Backend Latencies 260 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○User Timing marks and measures

Accessibility

Navigation

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
All in one, working together for you `div.better-together-content > div.better-together-reasons > div.reason-item > h3.reason-title`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.footerCenter > div.footerCenter__left > div.footerCenter__left__logo > a `div.footerCenter > div.footerCenter__left > div.footerCenter__left__logo > a`
div.footerCenter__right > div.footerCenter__right > div.footerCenter__right__item > a.footerCenter__right__item__link `div.footerCenter__right > div.footerCenter__right > div.footerCenter__right__item > a.footerCenter__right__item__link`
div.footerCenter__right > div.footerCenter__right > div.footerCenter__right__item > a.footerCenter__right__item__link `div.footerCenter__right > div.footerCenter__right > div.footerCenter__right__item > a.footerCenter__right__item__link`
div.footerCenter__right > div.footerCenter__right > div.footerCenter__right__item > a.footerCenter__right__item__link `div.footerCenter__right > div.footerCenter__right > div.footerCenter__right__item > a.footerCenter__right__item__link`
div.footerCenter__right > div.footerCenter__right > div.footerCenter__right__item > a.footerCenter__right__item__link `div.footerCenter__right > div.footerCenter__right > div.footerCenter__right__item > a.footerCenter__right__item__link`
div.footerCenter__right > div.footerCenter__right > div.footerCenter__right__item > a.footerCenter__right__item__link `div.footerCenter__right > div.footerCenter__right > div.footerCenter__right__item > a.footerCenter__right__item__link`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Domain Names Website Builder Hosting eCommerce Website Builder Google Workspace… `div.linklist2 > ul.linkListNew2__ul > li > ul.list-children`
Customer Service Accessibility Report Abuse Report Ethical Hacking Cookie setti… `div.linklist2 > ul.linkListNew2__ul > li > ul.list-children`
Network Solutions Blog WHOIS Search Site Map Website Grader Tools `div.linklist2 > ul.linkListNew2__ul > li > ul.list-children`
Affiliate Program Reseller Program Platinum Program `div.linklist2 > ul.linkListNew2__ul > li > ul.list-children`
About Us Why Choose Us Careers `div.linklist2 > ul.linkListNew2__ul > li > ul.list-children`

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

Best practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
.site .website .space Get your personal domain $1.99*/ first year `main > div.domain-search > div.domain-search__container > div#domainAd`

These items highlight common accessibility best practices.

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
.site .website .space Get your personal domain $1.99*/ first year `div.domain-search > div.domain-search__container > div#domainAd > a#domainAd`
Cookie Notice `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link`

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

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

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

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

●No element has a `[tabindex]` value greater than 0

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○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

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

○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.web.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	www.web.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge	www.web.com/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 clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

100

SEO

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○robots.txt is valid

○Document has a valid `rel=canonical`

Results for https://web.com

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

Content (2)

Navigation (1)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Payback period

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

Navigation

Names and labels

Best Practices

General

SEO

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Navigation

Names and labels

Tables and lists

Best practices

Best Practices

General

SEO

Keyboard Shortcuts