D — https://abovedomains.com

Site Health

Score: 59 / 100

Based on 6 categories, 0 sections

Room to improve — your 8.1s load time is above Google's 2.5s 'Good' threshold.

Several missing protections leave your users and data exposed.

Major barriers for users with disabilities — up to 15% of your audience.

Good server performance with room for optimization.

Strong compliance posture across regulations.

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

How is this calculated?

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

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

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

How the composite score is calculated

How you compare

Apache sites average 72

-13 below average

See full Apache benchmark →

Top Priorities (5)

Content-Security-Policy header is missing

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

Security › Security Headers

Cookie '__tad' is missing the Secure flag

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

Security › Cookie Security

HSTS 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

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%2Fabovedomains.com)](https://beavercheck.com/results/00542843-da58-4a34-8d9d-885a39a8ed5f)

HTML

<a href="https://beavercheck.com/results/00542843-da58-4a34-8d9d-885a39a8ed5f"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fabovedomains.com" alt="BeaverCheck Score"></a>

Image URL

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

This badge auto-updates with your latest scan result.

What fixing these means

Your site has several issues that may be affecting user experience and business outcomes. 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.

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

1 accessibility issue excludes users who rely on assistive technology.

Conversion Barriers

3 critical 2 warning

5 barrier(s) likely increasing bounce by ~34%.

Speed (2)

Page takes 8.1s to load

+12% bounce

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

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

Page feels frozen for 932ms

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

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

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (1)

No viewport meta tag

+15% bounce

Mobile browsers render at desktop width and shrink — text unreadable, tap targets miniature

Fix: Add <meta name="viewport" content="width=device-width, initial-scale=1">

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

Return on Investment

AUD 385 investment → AUD 7,965/month returns + AUD 50,000,000 risk avoided

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

Investment

AUD 385

4h · 5 findings

Monthly returns

AUD 7,965 /mo

~AUD 95,578 / year

Conversions recovered AUD 7,963
Bandwidth savings AUD 1.39

Regulatory risk avoided

AUD 50,000,000

if kept compliant

Privacy Act 1988 AUD 50,000,000

Payback period

0 12mo 24mo

AUD 220 — 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

A$385

3.5 developer hours at A$110/hr

Based on Australia rates (A$110/hr)

Quick wins

A$220 4 fixes in ~120 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

A$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

AUD 4,166,668 / month at risk

~AUD 50,000,017 / year if left unfixed

Compliance Risk

AUD 50,000,000

Privacy Act 1988

No privacy policy link detected
Privacy Act 1988: AUD 66,000 – AUD 50,000,000

Bandwidth Waste

AUD 1.39 /mo

11264.2 MB/mo × 0.123 AUD/GB

Optimize transfer: save ~1.1 MB per page load
Saves AUD 1.39/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

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.

7.83 s

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

8.13 s

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

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

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

25.26 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
www.above.com/javascript/jquery-ui.js	0.0 ms	426.0 KiB
www.above.com/img/monetize.png	0.0 ms	410.9 KiB
www.above.com/img/home_bg_1.webp	0.0 ms	367.1 KiB
www.above.com/img/brokerage.jpg	0.0 ms	93.2 KiB
connect.facebook.net/en_US/fbevents.js	1200.0 s	96.4 KiB
www.above.com/js/jquery211.js	0.0 ms	82.5 KiB
js.hs-analytics.net/analytics/1776361800000/48120166.js	300.0 s	42.3 KiB
/signals/config/1135211415159824?v=2.9.298&r=stable&domai...	1200.0 s	44.3 KiB
www.above.com/img/logo-addme1.png	0.0 ms	36.5 KiB
js.usemessages.com/conversations-embed.js	600.0 s	32.5 KiB
js.hubspot.com/web-interactives-embed.js	600.0 s	28.1 KiB
js.hscollectedforms.net/collectedforms.js	300.0 s	26.0 KiB
js.hs-banner.com/v2/48120166/banner.js	300.0 s	23.6 KiB
js.hs-banner.com/v2/4372769/banner.js	300.0 s	23.2 KiB
www.above.com/css/fonts/open-sans-v40-latin-regular.woff2	0.0 ms	18.4 KiB
www.above.com/css/fonts/open-sans-v40-latin-600.woff2	0.0 ms	18.3 KiB
www.above.com/css/fonts/open-sans-v40-latin-700.woff2	0.0 ms	18.0 KiB
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
www.above.com/img/logo-beontop1.png	0.0 ms	13.1 KiB
www.above.com/img/auda-logo-white.svg	0.0 ms	11.6 KiB
www.above.com/css/aboveGlobal.css?1775627195	0.0 ms	11.5 KiB
www.above.com/js/swfobject.js?1745405498	0.0 ms	10.1 KiB
www.above.com/img/logo-help1.png	0.0 ms	9.8 KiB
www.above.com/img/ISM_ISO27001_white.svg	0.0 ms	8.5 KiB
snap.licdn.com/li.lms-analytics/insight.min.js	86400.0 s	18.7 KiB
www.above.com/css/jquery-ui.css	0.0 ms	6.4 KiB
www.above.com/img/above-logo-466.png	0.0 ms	5.7 KiB
www.above.com/img/logo-drop.png	0.0 ms	5.6 KiB
www.above.com/js/lity.min.js?1745405498	0.0 ms	5.0 KiB
www.above.com/img/icann-accredited-trans-56.png	0.0 ms	4.8 KiB
js.hsadspixel.net/pixels.js	600.0 s	4.0 KiB
www.above.com/js/login.js?1775713774	0.0 ms	2.3 KiB
www.above.com/js/capswarn.js?1745405498	0.0 ms	1.9 KiB
www.above.com/js/scrollwithtipsy.js?1745405498	0.0 ms	1.7 KiB
www.above.com/img/logo-trillion.svg	0.0 ms	1.6 KiB
www.above.com/css/indexStyles.css?1775627195	0.0 ms	1.6 KiB
www.above.com/css/lity.min.css	0.0 ms	1.2 KiB
js.hs-scripts.com/48120166.js	90.0 s	1.1 KiB
js.hs-scripts.com/4372769.js	90.0 s	893 B
www.above.com/img/search.svg	0.0 ms	776 B
/collect?v=2&fmt=js&pid=3546452&time=1776362130351&url=ht...	0.0 ms	693 B
kit.fontawesome.com/61d644614c.css	300.0 s	515 B
/tr/?id=1135211415159824&ev=PageView&dl=https%3A%2F%2Fwww...	0.0 ms	274 B
www.gstatic.com/recaptcha/api2/logo_48.png	604800.0 s	2.3 KiB
/a?v=3&t=l&pid=1903031376&rv=64f0&tag_exp=0~115616986~115...	0.0 ms	11 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
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	55 ms
ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-brands-400-0.woff2	50 ms
ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-brands-400-1.woff2	35 ms
ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-solid-900-1.woff2	30 ms

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:0.345 source:map[column:86058 line:25 type:source-location url:https://js.hs-analytics.net/analytics/1776361800000/48120166.js urlProvider:network]]]

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.above.com/javascript/jquery-ui.js	426.0 KiB	2.4 s
www.above.com/css/aboveGlobal.css?1775627195	11.5 KiB	299 ms
www.above.com/css/lity.min.css	1.2 KiB
www.above.com/css/indexStyles.css?1775627195	1.6 KiB
www.above.com/css/jquery-ui.css	6.4 KiB	299 ms
www.above.com/js/lity.min.js?1745405498	5.0 KiB
www.above.com/js/login.js?1775713774	2.3 KiB
www.above.com/js/scrollwithtipsy.js?1745405498	1.7 KiB
www.above.com/js/swfobject.js?1745405498	10.1 KiB	299 ms
www.above.com/js/jquery211.js	82.5 KiB	1.8 s
fonts.googleapis.com/css?family=Open+Sans:400,600,700&display=swap	1.9 KiB	896 ms
ajax.googleapis.com/ajax/libs/jqueryui/1.11.4/jquery-ui.min.js	63.6 KiB	2.1 s
fonts.googleapis.com/css?family=Roboto&display=swap	2.0 KiB	183 ms
ka-p.fontawesome.com/releases/v6.7.2/css/pro.min.css?token=61d644614c	80.9 KiB	1.9 s
/releases/v6.7.2/css/pro-v4-font-face.min.css?token=61d64...	1.8 KiB
ka-p.fontawesome.com/releases/v6.7.2/css/pro-v4-shims.min.css?token=61d644614c	4.1 KiB
/releases/v6.7.2/css/pro-v5-font-face.min.css?token=61d64...	7.1 KiB	153 ms
kit.fontawesome.com/61d644614c.css	515 B	818 ms
stackpath.bootstrapcdn.com/bootstrap/4.5.2/js/bootstrap.min.js	15.7 KiB	1.3 s
stackpath.bootstrapcdn.com/bootstrap/4.5.2/css/bootstrap.min.css	24.9 KiB	1.5 s
www.google.com/recaptcha/api.js?render=6Le8eZoUAAAAACvL0yuXhE6cd7XioIzzzi5a1br8	1.0 KiB	908 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
div.row > div.col-md-4 > div.pt-4 > img `div.row > div.col-md-4 > div.pt-4 > img`	www.above.com/img/monetize.png	410.5 KiB	379.7 KiB
div.row > div.col-md-4 > div.pt-4 > img `div.row > div.col-md-4 > div.pt-4 > img`	www.above.com/img/brokerage.jpg	93.0 KiB	53.9 KiB
ul > li > a > img `ul > li > a > img`	www.above.com/img/logo-addme1.png	36.3 KiB	35.2 KiB
ul > li > a > img `ul > li > a > img`	www.above.com/img/logo-beontop1.png	12.9 KiB	11.3 KiB
ul > li > a > img `ul > li > a > img`	www.above.com/img/logo-help1.png	9.7 KiB	7.4 KiB
div.footerlogos > ul > li > img `div.footerlogos > ul > li > img`	www.above.com/img/icann-accredited-trans-56.png	4.6 KiB	4.1 KiB

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.2 s

URL	Time Spent
abovedomains.com/	1.2 s
www.above.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.

Diagnostics

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 700 ms 142.8 KiB

URL	Transfer Size	Est Savings
www.above.com/javascript/jquery-ui.js	425.6 KiB	142.8 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: 600 ms 114.0 KiB

URL	Transfer Size	Est Savings
ka-p.fontawesome.com/releases/v6.7.2/css/pro.min.css?token=61d644614c	80.6 KiB	80.2 KiB
stackpath.bootstrapcdn.com/bootstrap/4.5.2/css/bootstrap.min.css	24.4 KiB	23.4 KiB
www.above.com/css/aboveGlobal.css?1775627195	11.3 KiB	10.5 KiB

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

Why this matters

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

Learn more ▾

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

Source: Google web.dev / Lighthouse

Estimated savings: 2.2 s 983.2 KiB

URL	Transfer Size	Est Savings
www.above.com/javascript/jquery-ui.js	425.6 KiB	373.8 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	361.8 KiB	177.0 KiB
www.googletagmanager.com/gtag/js?id=AW-318991084	134.0 KiB	102.3 KiB
www.googletagmanager.com/gtag/js?id=G-DQB7CZVNQD&cx=c&gtm=4e64f0	176.0 KiB	69.8 KiB
www.googletagmanager.com/gtm.js?id=GTM-KKGWZHB	138.0 KiB	62.7 KiB
www.googletagmanager.com/gtag/js?id=AW-318991084&cx=c&gtm=4e64f0	134.0 KiB	61.0 KiB
ajax.googleapis.com/ajax/libs/jqueryui/1.11.4/jquery-ui.min.js	63.0 KiB	56.7 KiB
www.above.com/js/jquery211.js	82.3 KiB	46.1 KiB
connect.facebook.net/en_US/fbevents.js	96.3 KiB	33.7 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.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	793 ms	673 ms	88 ms
Unattributable	768 ms	132 ms	0.0 ms
js.hs-analytics.net/analytics/1776361800000/48120166.js	558 ms	414 ms	8.5 ms
www.above.com/	334 ms	8.6 ms	4.8 ms
www.googletagmanager.com/gtag/js?id=G-DQB7CZVNQD&cx=c&gtm=4e64f0	278 ms	207 ms	70 ms
www.googletagmanager.com/gtm.js?id=GTM-KKGWZHB	262 ms	219 ms	40 ms
www.googletagmanager.com/gtag/js?id=AW-318991084&cx=c&gtm=4e64f0	218 ms	184 ms	32 ms
www.above.com/javascript/jquery-ui.js	204 ms	32 ms	54 ms
/signals/config/1135211415159824?v=2.9.298&r=stable&domai...	151 ms	132 ms	19 ms
connect.facebook.net/en_US/fbevents.js	151 ms	109 ms	40 ms
js.hscollectedforms.net/collectedforms.js	109 ms	94 ms	9.2 ms
www.above.com/js/swfobject.js?1745405498	80 ms	59 ms	1.3 ms
www.google-analytics.com/analytics.js	77 ms	48 ms	6.7 ms
www.above.com/js/jquery211.js	74 ms	48 ms	8.5 ms
js.usemessages.com/conversations-embed.js	68 ms	54 ms	11 ms
ka-p.fontawesome.com/releases/v6.7.2/css/pro.min.css?token=61d644614c	62 ms	0.0 ms	0.0 ms
js.hubspot.com/web-interactives-embed.js	61 ms	49 ms	7.8 ms
ajax.googleapis.com/ajax/libs/jqueryui/1.11.4/jquery-ui.min.js	57 ms	30 ms	25 ms
www.googletagmanager.com/gtag/js?id=AW-318991084	55 ms	23 ms	31 ms
snap.licdn.com/li.lms-analytics/insight.min.js	54 ms	42 ms	5.6 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.7 s
Other	695 ms
Script Parsing & Compilation	487 ms
Style & Layout	448 ms
Parse HTML & CSS	131 ms
Garbage Collection	92 ms
Rendering	71 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
www.above.com/javascript/jquery-ui.js	426.0 KiB
www.above.com/img/monetize.png	410.9 KiB
www.above.com/img/home_bg_1.webp	367.1 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	362.4 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	361.9 KiB
www.googletagmanager.com/gtag/js?id=G-DQB7CZVNQD&cx=c&gtm=4e64f0	176.1 KiB
www.googletagmanager.com/gtm.js?id=GTM-KKGWZHB	138.4 KiB
www.googletagmanager.com/gtag/js?id=AW-318991084&cx=c&gtm=4e64f0	134.0 KiB
www.googletagmanager.com/gtag/js?id=AW-318991084	134.0 KiB
connect.facebook.net/en_US/fbevents.js	96.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
div.row > div.col-md-4 > div.pt-4 > img `div.row > div.col-md-4 > div.pt-4 > img`	www.above.com/img/monetize.png
ul > li > a > img `ul > li > a > img`	www.above.com/img/logo-addme1.png
div.row > div.col-md-4 > div.pt-4 > img `div.row > div.col-md-4 > div.pt-4 > img`	www.above.com/img/brokerage.jpg
ul > li > a > img `ul > li > a > img`	www.above.com/img/logo-beontop1.png
nav.navbar > div.container > a.navbar-brand > img.logoimg `nav.navbar > div.container > a.navbar-brand > img.logoimg`	www.above.com/img/above-logo-466.png
ul > li > a > img `ul > li > a > img`	www.above.com/img/logo-help1.png
ul > li > a > img `ul > li > a > img`	www.above.com/img/auda-logo-white.svg
ul > li > a > img `ul > li > a > img`	www.above.com/img/logo-trillion.svg
ul > li > a > img `ul > li > a > img`	www.above.com/img/logo-drop.png
div.footerlogos > ul > li > img `div.footerlogos > ul > li > img`	www.above.com/img/ISM_ISO27001_white.svg
div.footerlogos > ul > li > img `div.footerlogos > ul > li > img`	www.above.com/img/icann-accredited-trans-56.png

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

●Layout shift culprits

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●User Timing marks and measures 106 user timings

●Avoid long main-thread tasks 20 long tasks found

●Network Requests

●Network Round Trip Times 150 ms

●Server Backend Latencies 210 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○LCP request discovery

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

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
Prices displayed in USD. See all prices here `div.contentdiv2 > div.contentdiv2_pad > div.container > div.text-center`
here `div.contentdiv2_pad > div.container > div.text-center > a.grey`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
List your domain names `div.container > div.contenttext3a > p > a.newbluelink`

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
nav.navbar > div.container > a.navbar-brand > img.logoimg `nav.navbar > div.container > a.navbar-brand > img.logoimg`
ul > li > a > img `ul > li > a > img`
ul > li > a > img `ul > li > a > img`
ul > li > a > img `ul > li > a > img`
ul > li > a > img `ul > li > a > img`
ul > li > a > img `ul > li > a > img`
div.footerlogos > ul > li > img `div.footerlogos > ul > li > img`
ul > li > a > img `ul > li > a > img`
div.footerlogos > ul > li > img `div.footerlogos > ul > li > img`

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
topsection > nav.navbar > div.container > a.navbar-brand `topsection > nav.navbar > div.container > a.navbar-brand`
div.footerlogos > ul > li > a `div.footerlogos > ul > li > a`
div.footerlogos > ul > li > a `div.footerlogos > ul > li > a`
div.footerlogos > ul > li > a `div.footerlogos > ul > li > a`
div.footerlogos > ul > li > a `div.footerlogos > ul > li > a`
div.footerlogos > ul > li > a `div.footerlogos > ul > li > a`
div.footerlogos > ul > li > a `div.footerlogos > ul > li > a`
div.container > div.row > div.col-lg-2 > a.mr-3 `div.container > div.row > div.col-lg-2 > a.mr-3`
div.container > div.row > div.col-lg-2 > a.mr-3 `div.container > div.row > div.col-lg-2 > a.mr-3`
div.container > div.row > div.col-lg-2 > a.mr-3 `div.container > div.row > div.col-lg-2 > a.mr-3`
div.container > div.row > div.col-lg-2 > a `div.container > div.row > div.col-lg-2 > a`

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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
head > meta `head > meta`

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
Escrow `div.row > div.col-md-3 > div.footerlinks > a`
FAQs `div.row > div.col-md-3 > div.footerlinks > a`
Domain Brokerage `div.row > div.col-md-3 > div.footerlinks > a`
Domain Acquisition `div.row > div.col-md-3 > div.footerlinks > a`
About Us `div.row > div.col-md-3 > div.footerlinks > a`
Our Team `div.row > div.col-md-3 > div.footerlinks > a`
Contact Us `div.row > div.col-md-3 > div.footerlinks > a`
Site Map `div.row > div.col-md-3 > div.footerlinks > a`
Careers `div.row > div.col-md-3 > div.footerlinks > a`
Log In `div.row > div.col-md-3 > div.footerlinks > a`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

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

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

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

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

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

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

●Buttons have an accessible name

●Input buttons have discernible text.

●Form elements have associated labels

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

●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

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

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

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

●Heading elements appear in a sequentially-descending order

●Identical links have the same purpose.

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

○`[accesskey]` values are unique

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

○Deprecated ARIA roles were not used

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

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

○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

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

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

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

○`[lang]` attributes have a valid value

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

○Elements with visible text labels have matching accessible names.

○`<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
AttributionReporting	connect.facebook.net/en_US/fbevents.js line 279, col 769

●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
www.above.com/registrar/domain-pricing.html	here
www.above.com/monetization.html	Learn More

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
nav.navbar > div.container > a.navbar-brand > img.logoimg `nav.navbar > div.container > a.navbar-brand > img.logoimg`
ul > li > a > img `ul > li > a > img`
ul > li > a > img `ul > li > a > img`
ul > li > a > img `ul > li > a > img`
ul > li > a > img `ul > li > a > img`
ul > li > a > img `ul > li > a > img`
div.footerlogos > ul > li > img `div.footerlogos > ul > li > img`
ul > li > a > img `ul > li > a > img`
div.footerlogos > ul > li > img `div.footerlogos > ul > li > img`

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

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

2.74 s

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

4.41 s

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

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

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

5.47 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
www.above.com/javascript/jquery-ui.js	0.0 ms	426.0 KiB
www.above.com/img/monetize.png	0.0 ms	410.9 KiB
www.above.com/img/home_bg_1.webp	0.0 ms	367.1 KiB
www.above.com/img/brokerage.jpg	0.0 ms	93.2 KiB
connect.facebook.net/en_US/fbevents.js	1200.0 s	96.4 KiB
www.above.com/js/jquery211.js	0.0 ms	82.5 KiB
js.hs-analytics.net/analytics/1776361800000/48120166.js	300.0 s	42.3 KiB
/signals/config/1135211415159824?v=2.9.298&r=stable&domai...	1200.0 s	44.3 KiB
www.above.com/img/logo-addme1.png	0.0 ms	36.5 KiB
js.usemessages.com/conversations-embed.js	600.0 s	32.5 KiB
js.hubspot.com/web-interactives-embed.js	600.0 s	28.2 KiB
js.hscollectedforms.net/collectedforms.js	300.0 s	26.0 KiB
js.hs-banner.com/v2/48120166/banner.js	300.0 s	23.6 KiB
js.hs-banner.com/v2/4372769/banner.js	300.0 s	23.2 KiB
www.above.com/css/fonts/open-sans-v40-latin-regular.woff2	0.0 ms	18.4 KiB
www.above.com/css/fonts/open-sans-v40-latin-600.woff2	0.0 ms	18.3 KiB
www.above.com/css/fonts/open-sans-v40-latin-700.woff2	0.0 ms	18.0 KiB
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
www.above.com/img/logo-beontop1.png	0.0 ms	13.1 KiB
www.above.com/img/auda-logo-white.svg	0.0 ms	11.6 KiB
www.above.com/css/aboveGlobal.css?1775627195	0.0 ms	11.5 KiB
www.above.com/js/swfobject.js?1745405498	0.0 ms	10.1 KiB
www.above.com/img/logo-help1.png	0.0 ms	9.8 KiB
www.above.com/img/ISM_ISO27001_white.svg	0.0 ms	8.5 KiB
snap.licdn.com/li.lms-analytics/insight.min.js	86400.0 s	18.7 KiB
www.above.com/css/jquery-ui.css	0.0 ms	6.4 KiB
www.above.com/img/above-logo-466.png	0.0 ms	5.7 KiB
www.above.com/img/logo-drop.png	0.0 ms	5.6 KiB
www.above.com/js/lity.min.js?1745405498	0.0 ms	5.0 KiB
www.above.com/img/icann-accredited-trans-56.png	0.0 ms	4.8 KiB
js.hsadspixel.net/pixels.js	600.0 s	4.0 KiB
www.above.com/js/login.js?1775713774	0.0 ms	2.3 KiB
www.above.com/js/capswarn.js?1745405498	0.0 ms	1.9 KiB
www.above.com/js/scrollwithtipsy.js?1745405498	0.0 ms	1.7 KiB
www.above.com/img/logo-trillion.svg	0.0 ms	1.6 KiB
www.above.com/css/indexStyles.css?1775627195	0.0 ms	1.6 KiB
www.above.com/css/lity.min.css	0.0 ms	1.2 KiB
js.hs-scripts.com/48120166.js	90.0 s	1.2 KiB
js.hs-scripts.com/4372769.js	90.0 s	889 B
www.above.com/img/search.svg	0.0 ms	776 B
/collect?v=2&fmt=js&pid=3546452&time=1776362148586&url=ht...	0.0 ms	718 B
kit.fontawesome.com/61d644614c.css	300.0 s	517 B
www.gstatic.com/recaptcha/api2/logo_48.png	604800.0 s	2.3 KiB
/tr/?id=1135211415159824&ev=PageView&dl=https%3A%2F%2Fwww...	0.0 ms	19 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
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	60 ms
ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-brands-400-1.woff2	50 ms
ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-solid-900-1.woff2	30 ms
ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-brands-400-0.woff2	30 ms

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:0.407 source:map[column:86058 line:25 type:source-location url:https://js.hs-analytics.net/analytics/1776361800000/48120166.js urlProvider:network]] map[reflowTime:0.215 source:map[type:text value:[unattributed]]]]

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
div.row > div.col-md-4 > div.pt-4 > img `div.row > div.col-md-4 > div.pt-4 > img`	www.above.com/img/monetize.png	410.5 KiB	399.7 KiB
div.row > div.col-md-4 > div.pt-4 > img `div.row > div.col-md-4 > div.pt-4 > img`	www.above.com/img/brokerage.jpg	93.0 KiB	75.9 KiB
ul > li > a > img `ul > li > a > img`	www.above.com/img/logo-addme1.png	36.3 KiB	36.0 KiB
ul > li > a > img `ul > li > a > img`	www.above.com/img/logo-beontop1.png	12.9 KiB	12.4 KiB
ul > li > a > img `ul > li > a > img`	www.above.com/img/logo-help1.png	9.7 KiB	8.9 KiB
ul > li > a > img `ul > li > a > img`	www.above.com/img/logo-drop.png	5.4 KiB	4.7 KiB
div.footerlogos > ul > li > img `div.footerlogos > ul > li > img`	www.above.com/img/icann-accredited-trans-56.png	4.6 KiB	4.2 KiB
nav.navbar > div.container > a.navbar-brand > img.logoimg `nav.navbar > div.container > a.navbar-brand > img.logoimg`	www.above.com/img/above-logo-466.png	5.5 KiB	4.1 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:1204.9110009765625 label:Time to first byte subpart:timeToFirstByte] map[duration:1014.0889990234375 label:Resource load delay subpart:resourceLoadDelay] map[duration:238.122 label:Resource load duration subpart:resourceLoadDuration] map[duration:125.018 label:Element render delay subpart:elementRenderDelay]]

lhId: page-8-DIV

nodeLabel: A Platform Built For Domain Investors Monetization Industry Best Payouts Unlimi…

path: 1,HTML,1,BODY,4,DIV,2,DIV,1,DIV,0,DIV

selector: div#wrapper > div#content1 > div.contentdiv1 > div.contentdiv1_bg

snippet: <div class="contentdiv1_bg">

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-8-DIV

nodeLabel: A Platform Built For Domain Investors Monetization Industry Best Payouts Unlimi…

path: 1,HTML,1,BODY,4,DIV,2,DIV,1,DIV,0,DIV

selector: div#wrapper > div#content1 > div.contentdiv1 > div.contentdiv1_bg

snippet: <div class="contentdiv1_bg">

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.above.com/css/aboveGlobal.css?1775627195	11.5 KiB	189 ms
www.above.com/css/jquery-ui.css	6.4 KiB
www.above.com/js/login.js?1775713774	2.3 KiB
www.above.com/javascript/jquery-ui.js	426.0 KiB	379 ms
www.above.com/js/lity.min.js?1745405498	5.0 KiB
www.above.com/js/jquery211.js	82.5 KiB	379 ms
www.above.com/js/scrollwithtipsy.js?1745405498	1.7 KiB
www.above.com/js/swfobject.js?1745405498	10.1 KiB	189 ms
ajax.googleapis.com/ajax/libs/jqueryui/1.11.4/jquery-ui.min.js	63.6 KiB	520 ms
www.above.com/css/lity.min.css	1.2 KiB
www.above.com/css/indexStyles.css?1775627195	1.6 KiB
fonts.googleapis.com/css?family=Roboto&display=swap	1.6 KiB	73 ms
fonts.googleapis.com/css?family=Open+Sans:400,600,700&display=swap	2.2 KiB	323 ms
ka-p.fontawesome.com/releases/v6.7.2/css/pro.min.css?token=61d644614c	80.7 KiB	408 ms
/releases/v6.7.2/css/pro-v5-font-face.min.css?token=61d64...	7.1 KiB
ka-p.fontawesome.com/releases/v6.7.2/css/pro-v4-shims.min.css?token=61d644614c	4.1 KiB
stackpath.bootstrapcdn.com/bootstrap/4.5.2/js/bootstrap.min.js	15.6 KiB	324 ms
www.google.com/recaptcha/api.js?render=6Le8eZoUAAAAACvL0yuXhE6cd7XioIzzzi5a1br8	1.0 KiB	337 ms
stackpath.bootstrapcdn.com/bootstrap/4.5.2/css/bootstrap.min.css	24.9 KiB	399 ms
kit.fontawesome.com/61d644614c.css	517 B	263 ms
/releases/v6.7.2/css/pro-v4-font-face.min.css?token=61d64...	1.9 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: 672 ms

URL	Time Spent
abovedomains.com/	672 ms
www.above.com/	0.0 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 190 ms 142.8 KiB

URL	Transfer Size	Est Savings
www.above.com/javascript/jquery-ui.js	425.6 KiB	142.8 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 113.7 KiB

URL	Transfer Size	Est Savings
ka-p.fontawesome.com/releases/v6.7.2/css/pro.min.css?token=61d644614c	80.6 KiB	80.2 KiB
stackpath.bootstrapcdn.com/bootstrap/4.5.2/css/bootstrap.min.css	24.4 KiB	23.0 KiB
www.above.com/css/aboveGlobal.css?1775627195	11.3 KiB	10.5 KiB

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

Why this matters

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

Learn more ▾

Source: Google web.dev / Lighthouse

Estimated savings: 380 ms 1.1 MiB

URL	Transfer Size	Est Savings
www.above.com/javascript/jquery-ui.js	425.6 KiB	373.8 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	361.8 KiB	177.0 KiB
www.googletagmanager.com/gtag/js?id=AW-16892477374&cx=c&gtm=4e64f1h2&bs=ctrl	134.0 KiB	102.3 KiB
www.googletagmanager.com/gtag/js?id=G-DQB7CZVNQD&cx=c&gtm=4e64f1h2&bs=ctrl	176.0 KiB	69.5 KiB
www.googletagmanager.com/gtm.js?id=GTM-KKGWZHB	138.0 KiB	64.2 KiB
www.googletagmanager.com/gtag/js?id=AW-16784246920&cx=c&gtm=4e64f1h2&bs=ctrl	146.2 KiB	62.8 KiB
www.googletagmanager.com/gtag/js?id=AW-16892477374	134.0 KiB	62.3 KiB
www.googletagmanager.com/gtag/js?id=AW-16892394087&cx=c&gtm=4e64f1h2&bs=ctrl	134.0 KiB	62.3 KiB
www.googletagmanager.com/gtag/js?id=AW-16777691387&cx=c&gtm=4e64f1h2&bs=ctrl	134.0 KiB	61.0 KiB
ajax.googleapis.com/ajax/libs/jqueryui/1.11.4/jquery-ui.min.js	63.0 KiB	56.7 KiB
www.above.com/js/jquery211.js	82.3 KiB	46.1 KiB
connect.facebook.net/en_US/fbevents.js	96.3 KiB	34.5 KiB

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
www.above.com/javascript/jquery-ui.js	426.0 KiB
www.above.com/img/monetize.png	410.9 KiB
www.above.com/img/home_bg_1.webp	367.1 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	362.4 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	361.9 KiB
www.googletagmanager.com/gtag/js?id=G-DQB7CZVNQD&cx=c&gtm=4e64f1h2&bs=ctrl	176.1 KiB
www.googletagmanager.com/gtag/js?id=AW-16784246920&cx=c&gtm=4e64f1h2&bs=ctrl	146.3 KiB
www.googletagmanager.com/gtm.js?id=GTM-KKGWZHB	138.4 KiB
www.googletagmanager.com/gtag/js?id=AW-16892477374&cx=c&gtm=4e64f1h2&bs=ctrl	134.0 KiB
www.googletagmanager.com/gtag/js?id=AW-16892394087&cx=c&gtm=4e64f1h2&bs=ctrl	134.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
div.row > div.col-md-4 > div.pt-4 > img `div.row > div.col-md-4 > div.pt-4 > img`	www.above.com/img/monetize.png
ul > li > a > img `ul > li > a > img`	www.above.com/img/logo-addme1.png
div.row > div.col-md-4 > div.pt-4 > img `div.row > div.col-md-4 > div.pt-4 > img`	www.above.com/img/brokerage.jpg
ul > li > a > img `ul > li > a > img`	www.above.com/img/logo-beontop1.png
nav.navbar > div.container > a.navbar-brand > img.logoimg `nav.navbar > div.container > a.navbar-brand > img.logoimg`	www.above.com/img/above-logo-466.png
ul > li > a > img `ul > li > a > img`	www.above.com/img/logo-help1.png
ul > li > a > img `ul > li > a > img`	www.above.com/img/auda-logo-white.svg
ul > li > a > img `ul > li > a > img`	www.above.com/img/logo-trillion.svg
ul > li > a > img `ul > li > a > img`	www.above.com/img/logo-drop.png
div.footerlogos > ul > li > img `div.footerlogos > ul > li > img`	www.above.com/img/ISM_ISO27001_white.svg
div.footerlogos > ul > li > img `div.footerlogos > ul > li > img`	www.above.com/img/icann-accredited-trans-56.png

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

●Max Potential First Input Delay 70 ms

●Layout shift culprits

●Optimize DOM size

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●User Timing marks and measures 6 user timings

●JavaScript execution time 0.7 s

●Minimizes main-thread work 1.4 s

●Avoid long main-thread tasks 4 long tasks found

●Network Requests

●Network Round Trip Times 150 ms

●Server Backend Latencies 210 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○Avoid non-composited animations

○Avoid large layout shifts

Accessibility

ARIA

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
About `div#navbarSupportedContent > ul.navbar-nav > li.nav-item > a#navbarDropdown`
Log In `div#navbarSupportedContent > ul.navbar-nav > li.nav-item > a#navbarDropdownMenuLink`

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
Prices displayed in USD. See all prices here `div.contentdiv2 > div.contentdiv2_pad > div.container > div.text-center`
here `div.contentdiv2_pad > div.container > div.text-center > a.grey`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
List your domain names `div.container > div.contenttext3a > p > a.newbluelink`

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
nav.navbar > div.container > a.navbar-brand > img.logoimg `nav.navbar > div.container > a.navbar-brand > img.logoimg`
ul > li > a > img `ul > li > a > img`
ul > li > a > img `ul > li > a > img`
ul > li > a > img `ul > li > a > img`
ul > li > a > img `ul > li > a > img`
ul > li > a > img `ul > li > a > img`
div.footerlogos > ul > li > img `div.footerlogos > ul > li > img`
ul > li > a > img `ul > li > a > img`
div.footerlogos > ul > li > img `div.footerlogos > ul > li > img`

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
topsection > nav.navbar > div.container > a.navbar-brand `topsection > nav.navbar > div.container > a.navbar-brand`
div.footerlogos > ul > li > a `div.footerlogos > ul > li > a`
div.footerlogos > ul > li > a `div.footerlogos > ul > li > a`
div.footerlogos > ul > li > a `div.footerlogos > ul > li > a`
div.footerlogos > ul > li > a `div.footerlogos > ul > li > a`
div.footerlogos > ul > li > a `div.footerlogos > ul > li > a`
div.footerlogos > ul > li > a `div.footerlogos > ul > li > a`
div.container > div.row > div.col-lg-2 > a.mr-3 `div.container > div.row > div.col-lg-2 > a.mr-3`
div.container > div.row > div.col-lg-2 > a.mr-3 `div.container > div.row > div.col-lg-2 > a.mr-3`
div.container > div.row > div.col-lg-2 > a.mr-3 `div.container > div.row > div.col-lg-2 > a.mr-3`
div.container > div.row > div.col-lg-2 > a `div.container > div.row > div.col-lg-2 > a`

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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
head > meta `head > meta`

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
Escrow `div.row > div.col-md-3 > div.footerlinks > a`
FAQs `div.row > div.col-md-3 > div.footerlinks > a`
Domain Brokerage `div.row > div.col-md-3 > div.footerlinks > a`
Domain Acquisition `div.row > div.col-md-3 > div.footerlinks > a`
About Us `div.row > div.col-md-3 > div.footerlinks > a`
Our Team `div.row > div.col-md-3 > div.footerlinks > a`
Contact Us `div.row > div.col-md-3 > div.footerlinks > a`
Site Map `div.row > div.col-md-3 > div.footerlinks > a`
Careers `div.row > div.col-md-3 > div.footerlinks > a`
Log In `div.row > div.col-md-3 > div.footerlinks > a`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

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

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

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

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

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

●Input buttons have discernible text.

●Form elements have associated labels

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

●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

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

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

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

●Heading elements appear in a sequentially-descending order

●Identical links have the same purpose.

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

○`[accesskey]` values are unique

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

○Deprecated ARIA roles were not used

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

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

○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

○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

○Buttons have an accessible name

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

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

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

○`[lang]` attributes have a valid value

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

○Elements with visible text labels have matching accessible names.

○`<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
AttributionReporting	connect.facebook.net/en_US/fbevents.js line 279, col 769

●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
www.above.com/registrar/domain-pricing.html	here
www.above.com/monetization.html	Learn More

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
nav.navbar > div.container > a.navbar-brand > img.logoimg `nav.navbar > div.container > a.navbar-brand > img.logoimg`
ul > li > a > img `ul > li > a > img`
ul > li > a > img `ul > li > a > img`
ul > li > a > img `ul > li > a > img`
ul > li > a > img `ul > li > a > img`
ul > li > a > img `ul > li > a > img`
div.footerlogos > ul > li > img `div.footerlogos > ul > li > img`
ul > li > a > img `ul > li > a > img`
div.footerlogos > ul > li > img `div.footerlogos > ul > li > img`

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

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`

Results for https://abovedomains.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 (2)

Usability (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

Contrast

Names and labels

Best practices

Best Practices

General

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Contrast

Names and labels

Best practices

Best Practices

General

SEO

Content Best Practices

Keyboard Shortcuts