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
buydomains.com/main-OVVU4IZK.js	0.0 ms	119.4 KiB
buydomains.com/chunk-5BFX54KQ.js	0.0 ms	69.8 KiB
connect.facebook.net/en_US/bundle/sdk.js/	1200.0 s	77.8 KiB
buydomains.com/application.css	0.0 ms	53.7 KiB
cdn.cookielaw.org/scripttemplates/202502.1.0/otBannerSdk.js	86400.0 s	114.9 KiB
buydomains.com/chunk-73U2IERN.js	0.0 ms	38.6 KiB
buydomains.com/img/main/bd_domain_image.webp?	0.0 ms	30.1 KiB
buydomains.com/chunk-3EXHFM7O.js	0.0 ms	27.8 KiB
buydomains.com/img/hero/homeOpen.webp?	0.0 ms	17.2 KiB
buydomains.com/img/main/temp-screen-karmakarma.webp	0.0 ms	16.3 KiB
buydomains.com/chunk-XZH6MTXO.js	0.0 ms	15.0 KiB
buydomains.com/polyfills-B6TNHZQ6.js	0.0 ms	13.7 KiB
buydomains.com/img/logo-footer.svg	0.0 ms	13.2 KiB
buydomains.com/img/logo-header.svg	0.0 ms	13.2 KiB
buydomains.com/img/main/thmb-vid-premium-domainsHome.webp?version=2024-10-16-1	0.0 ms	8.9 KiB
/static-scripts/sites/14c6de8f682ef4a27da4f9a05784a723/ac...	60.0 s	8.8 KiB
buydomains.com/chunk-ICNIFSXY.js	0.0 ms	8.5 KiB
buydomains.com/chunk-O7MYZHFR.js	0.0 ms	8.3 KiB
buydomains.com/js/vendor/ua-parser.min.js	0.0 ms	8.2 KiB
buydomains.com/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/main.js?	14400.0 s	11.7 KiB
buydomains.com/chunk-PILWSARR.js	0.0 ms	7.6 KiB
wsv3cdn.audioeye.com/bootstrap.js?h=14c6de8f682ef4a27da4f9a05784a723	3600.0 s	9.3 KiB
/v2/scripts/loader.js?h=14c6de8f682ef4a27da4f9a05784a723&...	60.0 s	6.8 KiB
apps.usw2.pure.cloud/journey/messenger-plugins/offersHelper.min.js	600.0 s	5.5 KiB
buydomains.com/chunk-B6EHG77Y.js	0.0 ms	4.7 KiB
connect.facebook.net/en_US/sdk.js	1200.0 s	5.1 KiB
buydomains.com/chunk-DQH5FFAZ.js	0.0 ms	4.1 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js	86400.0 s	9.1 KiB
mta.newfold.com/snippets/media/bell.mp3	691200.0 s	29.5 KiB
buydomains.com/chunk-XHCFP3BY.js	0.0 ms	2.0 KiB
buydomains.com/chunk-SNQG4NMC.js	0.0 ms	1.8 KiB
buydomains.com/chunk-TPA2U6FS.js	0.0 ms	1.7 KiB
buydomains.com/chunk-DATPHDTX.js	0.0 ms	1.4 KiB
buydomains.com/chunk-6DDMLFLQ.js	0.0 ms	1.3 KiB
buydomains.com/chunk-VYAXRZUQ.js	0.0 ms	1.1 KiB
mta.newfold.com/snippets/js/web-chat.js	691200.0 s	8.6 KiB
buydomains.com/chunk-NAZDGGLG.js	0.0 ms	804 B
buydomains.com/chunk-GAL4ENT6.js	0.0 ms	754 B
buydomains.com/img/mobile/main/bg-main-hilight-fade.webp?	0.0 ms	737 B
buydomains.com/chunk-U4TT4242.js	0.0 ms	718 B
wsmcdn.audioeye.com/aem.js	120.0 s	669 B
buydomains.com/chunk-N63NN5VI.js	0.0 ms	587 B
buydomains.com/chunk-E7OB66FC.js	0.0 ms	584 B
buydomains.com/img/mobile/main/bg-case-study-fade.webp	0.0 ms	549 B
buydomains.com/chunk-6SLXIL44.js	0.0 ms	319 B
buydomains.com/chunk-BFRO4LNK.js	0.0 ms	309 B
mta.newfold.com/snippets/loader.js?snippet=/js/web-chat.js	691200.0 s	2.5 KiB

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]

items: [map[node:map[type:text value:Total] score:0.647937] map[node:map[boundingRect:map[bottom:628 height:434 left:10 right:402 top:195 width:391] lhId:page-1-DIV nodeLabel:About Cookies By visiting this Site, you agree to our Terms of Use, including i… path:1,HTML,1,BODY,28,DIV,1,DIV selector:body.content-loaded > div#onetrust-consent-sdk > div#onetrust-banner-sdk snippet:<div id="onetrust-banner-sdk" class="otCenterRounded default vertical-align-content" tabindex="0" role="dialog" aria-labelledby="onetrust-policy-title" aria-modal="true"> type:node] score:0.647937]]

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:50.857 source:map[type:text value:[unattributed]]]]

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:283.589 label:Time to first byte subpart:timeToFirstByte] map[duration:2566.569 label:Resource load delay subpart:resourceLoadDelay] map[duration:236.848 label:Resource load duration subpart:resourceLoadDuration] map[duration:56.589 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-DIV

nodeLabel: YOUR BUSINESS STARTS HERE BUY A PREMIUM DOMAIN AND OPEN YOUR DOORS - BUYDOMAIN…

path: 1,HTML,1,BODY,3,APP-ROOT,2,APP-HOMEPAGE,1,DIV

selector: body.content-loaded > app-root > app-homepage > div#home-page-billboard

snippet: <div _ngcontent-ng-c456721984="" id="home-page-billboard" class="contain-billboardHome container-layout">

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

nodeLabel: YOUR BUSINESS STARTS HERE BUY A PREMIUM DOMAIN AND OPEN YOUR DOORS - BUYDOMAIN…

path: 1,HTML,1,BODY,3,APP-ROOT,2,APP-HOMEPAGE,1,DIV

selector: body.content-loaded > app-root > app-homepage > div#home-page-billboard

snippet: <div _ngcontent-ng-c456721984="" id="home-page-billboard" class="contain-billboardHome container-layout">

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

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
karmakarma.com Case Study `div.inner-home-case > p.intro-case-study > a#case-study-img > img.float-left`	buydomains.com/img/main/temp-screen-karmakarma.webp	16.2 KiB	5.6 KiB

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

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

Element	Layout shift score
About Cookies By visiting this Site, you agree to our Terms of Use, including i… `body.content-loaded > div#onetrust-consent-sdk > div#onetrust-banner-sdk`	0.648

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

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: 420 ms 68.0 KiB

URL	Transfer Size	Est Savings
apps.usw2.pure.cloud/genesys-bootstrap/genesys.min.js	157.2 KiB	68.0 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: 150 ms 47.8 KiB

URL	Transfer Size	Est Savings
buydomains.com/application.css	53.6 KiB	47.8 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.9 s 547.9 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtm.js?id=GTM-NL5LTF	168.2 KiB	90.9 KiB
apps.usw2.pure.cloud/genesys-bootstrap/genesys.min.js	157.2 KiB	80.1 KiB
buydomains.com/main-OVVU4IZK.js	119.3 KiB	78.1 KiB
cdn.cookielaw.org/scripttemplates/202502.1.0/otBannerSdk.js	114.8 KiB	69.7 KiB
wsv3cdn.audioeye.com/static-scripts/v2/2026-04-08/startup.bundle.js	123.5 KiB	63.6 KiB
connect.facebook.net/en_US/bundle/sdk.js/	77.6 KiB	53.7 KiB
/static-scripts/m/audioeye-scanner-esm/v11.0.44/audioeye-...	80.3 KiB	37.3 KiB
buydomains.com/chunk-5BFX54KQ.js	69.8 KiB	27.4 KiB
wsv3cdn.audioeye.com/static-scripts/v2/2026-04-08/smartrems.bundle.js	37.9 KiB	26.4 KiB
buydomains.com/chunk-3EXHFM7O.js	27.8 KiB	20.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
buydomains.com/polyfills-B6TNHZQ6.js	1.9 s	1.7 s	0.7 ms
Unattributable	1.2 s	352 ms	0.0 ms
buydomains.com/	676 ms	123 ms	25 ms
connect.facebook.net/en_US/bundle/sdk.js/	445 ms	286 ms	35 ms
buydomains.com/cdn-cgi/challenge-platform/scripts/jsd/main.js	342 ms	328 ms	3.7 ms
buydomains.com/chunk-73U2IERN.js	318 ms	101 ms	0.9 ms
buydomains.com/chunk-PILWSARR.js	315 ms	305 ms	0.3 ms
www.googletagmanager.com/gtm.js?id=GTM-NL5LTF	312 ms	228 ms	70 ms
cdn.cookielaw.org/scripttemplates/202502.1.0/otBannerSdk.js	248 ms	78 ms	67 ms
apps.usw2.pure.cloud/genesys-bootstrap/genesys.min.js	222 ms	122 ms	5.1 ms
wsv3cdn.audioeye.com/static-scripts/v2/2026-04-08/startup.bundle.js	171 ms	119 ms	49 ms
wsv3cdn.audioeye.com/static-scripts/v2/2026-04-08/smartrems.bundle.js	114 ms	96 ms	17 ms
wsv3cdn.audioeye.com/static-scripts/v2/2026-04-08/compliance.bundle.js	91 ms	82 ms	6.4 ms
/v2/scripts/loader.js?h=14c6de8f682ef4a27da4f9a05784a723&...	55 ms	49 ms	2.8 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	4.1 s
Other	1.2 s
Style & Layout	678 ms
Script Parsing & Compilation	314 ms
Parse HTML & CSS	126 ms
Garbage Collection	106 ms
Rendering	62 ms

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

●Document request latency

●Optimize DOM size

●Font display

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

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

●User Timing marks and measures 42 user timings

●Avoid long main-thread tasks 20 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 190 ms

●Server Backend Latencies 560 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

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

○INP breakdown

○Avoid non-composited animations

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

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 Cookies By visiting this Site, you agree to our Terms of Use, including i… `body.content-loaded > div#onetrust-consent-sdk > div#onetrust-banner-sdk > div.ot-sdk-container`

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
.com ▾ `div.inner-billboard > app-search-bar > div.search-form > div.select-tld`

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
.com ▾ `div.inner-billboard > app-search-bar > div.search-form > div.select-tld`

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.

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
Categories `li.f-nav-container > ul.nav-footer > li > a#track-footer-categories`
Success Stories `li.f-nav-container > ul.nav-footer > li > a#track-footer-success-stories`
About Premium Domains `li.f-nav-container > ul.nav-footer > li > a#track-footer-about-premium-domains`
About `li.f-nav-container > ul.nav-footer > li > a#track-footer-about-us`
Careers `li.f-nav-container > ul.nav-footer > li > a#track-footer-careers`
Contact `li.f-nav-container > ul.nav-footer > li > a#track-footer-contact`
Policies `li.f-nav-container > ul.nav-footer > li > a#track-footer-policies`

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

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

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

●`[role]` values are valid

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

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●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

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

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Links have a discernible name

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

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

○`[accesskey]` values are unique

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

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

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

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

○ARIA IDs are unique

○No form fields have multiple labels

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

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

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

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

○Identical links have the same purpose.

○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

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
karmakarma.com Case Study `div.inner-home-case > p.intro-case-study > a#case-study-img > img.float-left`	buydomains.com/img/main/temp-screen-karmakarma.webp	366 x 200 (1.83)	325 x 200 (1.63)
play video `div#feature > div#container-feature-thumb > a#track-homepage-video-img-open > img#vd-thmb-vid-premium-domainsHome`	buydomains.com/img/main/thmb-vid-premium-domainsHome.webp?version=2024-10-16-1	266 x 139 (1.91)	278 x 149 (1.87)

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Displayed size	Actual size	Expected size
play video `div#feature > div#container-feature-thumb > a#track-homepage-video-img-open > img#vd-thmb-vid-premium-domainsHome`	buydomains.com/img/main/thmb-vid-premium-domainsHome.webp?version=2024-10-16-1	266 x 139	278 x 149	399 x 209

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	buydomains.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	buydomains.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge	buydomains.com/cdn-cgi/challenge-platform/scripts/jsd/main.js

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy

●Uses HTTPS

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●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

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`

●Document has a valid `rel=canonical`

○robots.txt is valid