Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

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

Performance issues directly impact user engagement and conversion rates.

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
oss.nameclub.com/public/domain/logo/28.com.png	14400.0 s	116.1 KiB
www.dynadot.com/web-static/fonts/switzer/fonts/Switzer-Variable.woff2	14400.0 s	42.4 KiB
www.dynadot.com/web-static/footer/icann.png	14400.0 s	31.5 KiB
oss.nameclub.com/public/domain/logo/travel.io.png	14400.0 s	29.7 KiB
oss.dynadot.com/public/telemetry-sdk/telemetry-sdk-dynadot-prod-v1.2.3.min.js	0.0 ms	20.1 KiB
www.dynadot.com/web-static/lottie/nameclub-loading.gif	14400.0 s	29.5 KiB
oss.nameclub.com/public/domain/logo/xfinance.com.png	14400.0 s	29.4 KiB
oss.nameclub.com/public/domain/logo/contractor.ai.png	14400.0 s	28.6 KiB
oss.nameclub.com/public/domain/logo/loans.net.png	14400.0 s	25.7 KiB
oss.nameclub.com/public/domain/logo/ai.news.png	14400.0 s	25.5 KiB
www.dynadot.com/web-static/fonts/swansea/fonts/SwanseaBold-D0ox.woff	14400.0 s	24.9 KiB
oss.nameclub.com/public/domain/logo/x.info.png	14400.0 s	24.6 KiB
oss.nameclub.com/public/domain/logo/sh.com.png	14400.0 s	23.2 KiB
oss.nameclub.com/public/domain/logo/heated.com.png	14400.0 s	21.8 KiB
oss.nameclub.com/public/domain/logo/robot.ai.png	14400.0 s	21.8 KiB
oss.nameclub.com/public/domain/logo/master.ai.png	14400.0 s	21.8 KiB
oss.nameclub.com/public/domain/logo/invest.ai.png	14400.0 s	21.7 KiB
oss.nameclub.com/public/domain/logo/tb.com.png	14400.0 s	21.3 KiB
oss.nameclub.com/public/domain/logo/hotdeal.com.png	14400.0 s	20.7 KiB
oss.nameclub.com/public/domain/logo/b.ai.png	14400.0 s	20.0 KiB
www.dynadot.com/web-static/fonts/switzer/fonts/Switzer-Semibold.woff2	14400.0 s	19.3 KiB
www.dynadot.com/web-static/fonts/switzer/fonts/Switzer-Medium.woff2	14400.0 s	19.3 KiB
oss.nameclub.com/public/domain/logo/ts.com.png	14400.0 s	16.8 KiB
www.dynadot.com/web-static/footer/namePros.png	14400.0 s	16.3 KiB
oss.nameclub.com/public/domain/logo/tomspasta.com.png	14400.0 s	15.9 KiB
oss.nameclub.com/public/domain/logo/beanie.com.png	14400.0 s	15.4 KiB
www.dynadot.com/web-static/footer/Domaining.png	14400.0 s	14.5 KiB
www.dynadot.com/web-static/common/navbar/mask_group.webp	14400.0 s	11.7 KiB
oss.nameclub.com/public/domain/logo/1.bond.png	14400.0 s	11.1 KiB
oss.nameclub.com/public/domain/logo/sparring.com.png	14400.0 s	10.5 KiB
www.dynadot.com/web-static/home/chatbot_bubble.png	14400.0 s	2.8 KiB
www.dynadot.com/web-static/home/ai-search-icon.png	14400.0 s	1.4 KiB
www.dynadot.com/web-static/home/bulk-search-icon.png	14400.0 s	1.1 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
www.dynadot.com/web/assets/fa-brands-400.BQ2oD0jK.woff2	40 ms
www.dynadot.com/web/assets/fa-solid-900.DyU82RFF.woff2	30 ms
www.dynadot.com/web/assets/fa-light-300.jnjlYqOj.woff2	20 ms
www.dynadot.com/web/assets/fa-regular-400.BnLtqlLh.woff2	15 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:109.357 source:map[type:text value:[unattributed]]]]

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

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

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.dynadot.com/web/assets/domain-search-result.pNi21U7b.css	11.6 KiB
www.dynadot.com/web/assets/layout.C7QULfbs.css	5.2 KiB	150 ms
www.dynadot.com/web/assets/home-page.DhaA9KLz.css	3.9 KiB
www.dynadot.com/web/assets/common.D3VNEIco.css	6.3 KiB
www.dynadot.com/web/assets/domain-search-page.Doy1Lqog.css	2.0 KiB
www.dynadot.com/web/assets/entry.DqQqnkO4.css	9.1 KiB

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
Logo for 28.com domain `div.dyna-card > div.dyna-card-cover > div.dyna-img > img.cover`	oss.nameclub.com/public/domain/logo/28.com.png	115.3 KiB	103.6 KiB
ICANN `div.other > div.registry-img > div > img`	www.dynadot.com/web-static/footer/icann.png	31.3 KiB	30.5 KiB
div.dyna-card > div.dyna-card-cover > div.dyna-img > img.loading `div.dyna-card > div.dyna-card-cover > div.dyna-img > img.loading`	www.dynadot.com/web-static/lottie/nameclub-loading.gif	29.3 KiB	28.1 KiB
Logo for travel.io domain `div.dyna-card > div.dyna-card-cover > div.dyna-img > img.cover`	oss.nameclub.com/public/domain/logo/travel.io.png	29.0 KiB	20.3 KiB
Logo for XFinance.com domain `div.dyna-card > div.dyna-card-cover > div.dyna-img > img.cover`	oss.nameclub.com/public/domain/logo/xfinance.com.png	28.6 KiB	20.1 KiB
Logo for Contractor.ai domain `div.dyna-card > div.dyna-card-cover > div.dyna-img > img.cover`	oss.nameclub.com/public/domain/logo/contractor.ai.png	27.8 KiB	19.5 KiB
Logo for Loans.net domain `div.dyna-card > div.dyna-card-cover > div.dyna-img > img.cover`	oss.nameclub.com/public/domain/logo/loans.net.png	24.9 KiB	17.5 KiB
Logo for ai.news domain `div.dyna-card > div.dyna-card-cover > div.dyna-img > img.cover`	oss.nameclub.com/public/domain/logo/ai.news.png	24.8 KiB	17.4 KiB
Logo for x.info domain `div.dyna-card > div.dyna-card-cover > div.dyna-img > img.cover`	oss.nameclub.com/public/domain/logo/x.info.png	23.8 KiB	16.7 KiB
Logo for sh.com domain `div.dyna-card > div.dyna-card-cover > div.dyna-img > img.cover`	oss.nameclub.com/public/domain/logo/sh.com.png	22.4 KiB	15.7 KiB
NamePros `div.other > div.registry-img > div > img`	www.dynadot.com/web-static/footer/namePros.png	16.1 KiB	15.1 KiB
Logo for heated.com domain `div.dyna-card > div.dyna-card-cover > div.dyna-img > img.cover`	oss.nameclub.com/public/domain/logo/heated.com.png	21.1 KiB	14.8 KiB
Logo for robot.ai domain `div.dyna-card > div.dyna-card-cover > div.dyna-img > img.cover`	oss.nameclub.com/public/domain/logo/robot.ai.png	21.0 KiB	14.8 KiB
Logo for Master.ai domain `div.dyna-card > div.dyna-card-cover > div.dyna-img > img.cover`	oss.nameclub.com/public/domain/logo/master.ai.png	21.0 KiB	14.8 KiB
Logo for invest.ai domain `div.dyna-card > div.dyna-card-cover > div.dyna-img > img.cover`	oss.nameclub.com/public/domain/logo/invest.ai.png	21.0 KiB	14.7 KiB
Logo for tb.com domain `div.dyna-card > div.dyna-card-cover > div.dyna-img > img.cover`	oss.nameclub.com/public/domain/logo/tb.com.png	20.5 KiB	14.4 KiB
Logo for hotdeal.com domain `div.dyna-card > div.dyna-card-cover > div.dyna-img > img.cover`	oss.nameclub.com/public/domain/logo/hotdeal.com.png	19.9 KiB	14.0 KiB
Domaining `div.other > div.registry-img > div > img`	www.dynadot.com/web-static/footer/Domaining.png	14.4 KiB	13.7 KiB
Logo for b.ai domain `div.dyna-card > div.dyna-card-cover > div.dyna-img > img.cover`	oss.nameclub.com/public/domain/logo/b.ai.png	19.2 KiB	13.5 KiB

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 928 ms

URL	Time Spent
dynadot.com/	928 ms
www.dynadot.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 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: 150 ms 70.9 KiB

URL	Transfer Size	Est Savings
@font-face{font-display:swap;font-family:Swansea;font-style:normal;font-weight:100 900; … } …	42.9 KiB	38.7 KiB
.dyna-text-wrapper[data-v-6007d8c8]{display:-webkit-box;overflow:hidden;width:100%; … } …	21.7 KiB	20.7 KiB
www.dynadot.com/web/assets/domain-search-result.pNi21U7b.css	11.5 KiB	11.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

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 2.5 s 565.8 KiB

URL	Transfer Size	Est Savings
www.dynadot.com/web/assets/common-79fyDEoK.js	416.6 KiB	250.4 KiB
www.dynadot.com/web/assets/layout-D6EobSRS.js	139.3 KiB	91.0 KiB
www.dynadot.com/web/assets/domain-search-result-CgZN4ubQ.js	73.6 KiB	70.6 KiB
www.googletagmanager.com/gtag/js?id=G-MKL2SL0CKG&cx=c&gtm=4e64h1	156.9 KiB	66.1 KiB
www.googletagmanager.com/gtag/js?id=G-S0L3BZSLYB	171.9 KiB	57.0 KiB
www.dynadot.com/web/assets/entry-DVwagWUy.js	70.8 KiB	30.6 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.dynadot.com/	3.0 s	449 ms	5.6 ms
www.dynadot.com/web/assets/common-79fyDEoK.js	1.9 s	1.7 s	11 ms
Unattributable	1.1 s	26 ms	0.0 ms
www.googletagmanager.com/gtag/js?id=G-S0L3BZSLYB	893 ms	721 ms	79 ms
www.googletagmanager.com/gtag/js?id=G-MKL2SL0CKG&cx=c&gtm=4e64h1	494 ms	426 ms	64 ms
oss.dynadot.com/public/telemetry-sdk/telemetry-sdk-dynadot-prod-v1.2.3.min.js	84 ms	51 ms	12 ms
hm.baidu.com/hm.js?8d89fe6af9a6ffe400e00d2cd224c669	60 ms	52 ms	4.1 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	3.4 s
Other	2.2 s
Style & Layout	837 ms
Rendering	613 ms
Parse HTML & CSS	248 ms
Script Parsing & Compilation	195 ms
Garbage Collection	140 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
The page has an unload handler in the main frame.	Actionable
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

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

●Layout shift culprits

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 2,241 KiB

●User Timing marks and measures 70 user timings

●Avoid long main-thread tasks 14 long tasks found

●Avoid non-composited animations 2 animated elements found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 200 ms

●Server Backend Latencies 320 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.nav-right > div > div > button.btn `div.nav-right > div > div > button.btn`
div.nav-right > div.navbar-right-shopping-cart > a.dyna-tooltip__trigger > button.btn `div.nav-right > div.navbar-right-shopping-cart > a.dyna-tooltip__trigger > button.btn`
div.navbar > div.nav-right > div.navbar-mega-btn > button.mega-switch-btn `div.navbar > div.nav-right > div.navbar-mega-btn > button.mega-switch-btn`
div.mega-menu-mobile > div.dynadot-logo > div.mega-top-btn-bar > button.mega-switch-btn `div.mega-menu-mobile > div.dynadot-logo > div.mega-top-btn-bar > button.mega-switch-btn`

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
nav > div.navbar > div.ctl-logo > a.router-link-active `nav > div.navbar > div.ctl-logo > a.router-link-active`
div.navbar > div.nav-right > div.navbar-right-shopping-cart > a.dyna-tooltip__trigger `div.navbar > div.nav-right > div.navbar-right-shopping-cart > a.dyna-tooltip__trigger`
div.mega-menu-mobile > div.dynadot-logo > div > a.router-link-active `div.mega-menu-mobile > div.dynadot-logo > div > a.router-link-active`
div.dynadot-logo > div.mega-top-btn-bar > div.person-bar > a `div.dynadot-logo > div.mega-top-btn-bar > div.person-bar > a`
div.footer-content > div.footer-gather > div.footer-logo > a.router-link-active `div.footer-content > div.footer-gather > div.footer-logo > a.router-link-active`
div.footer-content > div.footer-gather > div.footer-icon > a `div.footer-content > div.footer-gather > div.footer-icon > a`
div.footer-content > div.footer-gather > div.footer-icon > a `div.footer-content > div.footer-gather > div.footer-icon > a`
div.footer-content > div.footer-gather > div.footer-icon > a `div.footer-content > div.footer-gather > div.footer-icon > a`
div.footer-content > div.footer-gather > div.footer-icon > a `div.footer-content > div.footer-gather > div.footer-icon > a`
div.footer-content > div.footer-gather > div.footer-icon > a `div.footer-content > div.footer-gather > div.footer-icon > a`
div.footer-content > div.footer-gather > div.footer-icon > a `div.footer-content > div.footer-gather > div.footer-icon > a`
div.app-icon > span > span > a `div.app-icon > span > span > a`
div.app-icon > span > span > a `div.app-icon > span > span > 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

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
div.app-icon > span > span > a `div.app-icon > span > span > a`
div.app-icon > span > span > a `div.app-icon > span > span > a`

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

●Image elements have `[alt]` attributes

●Form elements have associated labels

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

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

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

●Elements use only permitted ARIA attributes

●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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

○`[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 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 buttons have discernible text.

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

○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

○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

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

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

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

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

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
Unload event listeners are deprecated and will be removed.	hm.baidu.com/hm.js?8d89fe6af9a6ffe400e00d2cd224c669 line 1, col 274

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
www.clarity.ms/tag/vqnmvzb3vk	`Uncaught TypeError: a[c] is not a function`

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
www.dynadot.com/web/assets/layout-D6EobSRS.js
www.dynadot.com/web/assets/domain-search-result-CgZN4ubQ.js
www.dynadot.com/web/assets/common-79fyDEoK.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 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

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

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

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`