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.

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.ancestrycdn.com/ui/2.69.0/font/ancestry-icon.woff2	45 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:36.503 source:map[type:text value:[unattributed]]]]

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: You’ve got questions. We’ve got ancestors.™ Curious about your family history?…

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

selector: div.cmp-container__container-content > div.aem-Grid > div.container > div.cmp-container

snippet: <div style="cursor: default;" data-cmp-is="ancestry-container" data-event-enabled="true" data-event-target-attribute-values="["href"]" data-visibility-no-activate="false" class="cmp-container container-media-73419e335b ">

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

value: No additional origins are good candidates for preconnecting

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
/etc.clientlibs/foundation/clientlibs/shared.min.ACSHASH6...	7.3 KiB
/etc.clientlibs/clientlibs/granite/utils.min.ACSHASH5536b...	3.8 KiB
/etc.clientlibs/core/wcm/components/form/text/v2/text/cli...	1.5 KiB
/etc.clientlibs/ancestry/clientlibs/clientlibs-components...	1.7 KiB
/etc.clientlibs/ancestry/clientlibs/clientlibs-components...	779 B
/etc.clientlibs/ancestry/clientlibs/clientlibs-components...	751 B
/etc.clientlibs/ancestry/clientlibs/clientlibs-components...	749 B
/etc.clientlibs/ancestry/clientlibs/clientlibs-components...	4.3 KiB
/etc.clientlibs/ancestry/clientlibs/clientlibs-components...	774 B
/etc.clientlibs/clientlibs/granite/jquery.min.ACSHASH83d7...	34.6 KiB
/etc.clientlibs/ancestry/clientlibs/clientlibs-components...	1.9 KiB
/etc.clientlibs/core/wcm/components/image/v2/image/client...	2.7 KiB
/etc.clientlibs/ancestry/clientlibs/clientlibs-components...	3.8 KiB
/etc.clientlibs/ancestry/clientlibs/clientlib-js-base.min...	43.8 KiB	600 ms
/etc.clientlibs/clientlibs/granite/jquery/granite.min.ACS...	2.1 KiB
/etc.clientlibs/ancestry/clientlibs/clientlib-global.min....	17.2 KiB
/etc.clientlibs/foundation/clientlibs/jquery.min.ACSHASHd...	726 B
/etc.clientlibs/ancestry/clientlibs/clientlibs-components...	1.6 KiB
/etc.clientlibs/ancestry/clientlibs/clientlib-clickableca...	1020 B
/etc.clientlibs/ancestry/clientlibs/clientlibs-components...	749 B
/etc.clientlibs/ancestry/clientlibs/clientlibs-components...	1.1 KiB
/shared-navigation/footer/ancestry/1.0/content/footer-4ec...	3.5 KiB
www.ancestrycdn.com/ui-static/lib/ajax-manager/2.1.0/ajax-manager.js	2.7 KiB
www.ancestrycdn.com/ui/2.69.0/css/core.css	26.6 KiB	921 ms
/etc.clientlibs/ancestry/clientlibs/clientlib-site-split....	28.7 KiB	450 ms
/etc.clientlibs/ancestry/clientlibs/clientlib-dependencie...	451 B	150 ms
/shared-navigation/footer/ancestry/1.0/content/footer-05e...	1.3 KiB

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
connect.facebook.net/en_US/fbevents.js	1200.0 s	96.6 KiB
/signals/config/1411840285724878?v=2.9.303&r=stable&domai...	1200.0 s	40.6 KiB
assets.revlifter.io/838e2ddb-68e7-4a26-a839-a090f3fd5cd7.js	0.0 ms	12.6 KiB
/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/...	14400.0 s	13.1 KiB
s.yimg.com/wi/ytc.js	0.0 ms	7.1 KiB
www.ancestry.com/Banners/API/Get/21?callback=callback177680855260329263754	0.0 ms	5.0 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 KiB
/SIE/?Q_ZID=ZN_ZLbq3hee0gRevdf	3600.0 s	4.6 KiB
/dxjsmodule/12.1a2b7192fd54e87d3971.chunk.js?Q_CLIENTVERS...	604800.0 s	35.8 KiB
/dxjsmodule/CoreModule.js?Q_CLIENTVERSION=2.46.0&Q_CLIENT...	604800.0 s	30.9 KiB
ct.pinterest.com/static/ct/token_create.js	7200.0 s	3.9 KiB
s.pinimg.com/ct/lib/main.10d2511a.js	1209600.0 s	27.3 KiB
/mit/api/geo/rd?sourceUrl=https%3A%2F%2Fwww.ancestry.com%...	0.0 ms	2.2 KiB
/dxjsmodule/37.7ea1ffe71ad8c0799cc1.chunk.js?Q_CLIENTVERS...	604800.0 s	18.6 KiB
s.pinimg.com/ct/core.js	7200.0 s	2.1 KiB
/dxjsmodule/1.bc67e778235741631577.chunk.js?Q_CLIENTVERSI...	604800.0 s	7.1 KiB
/1/4bd2ba109c?a=798977697&sa=1&v=1.268.0&t=Unnamed%20Tran...	0.0 ms	600 B
/dxjsmodule/7.f7df015b06d8a90ce822.chunk.js?Q_CLIENTVERSI...	604800.0 s	1.4 KiB
/tr/?id=1411840285724878&ev=PageView&dl=https%3A%2F%2Fwww...	0.0 ms	16 B
/tr/?id=1411840285724878&ev=NRV_PageView&dl=https%3A%2F%2...	0.0 ms	16 B

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

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.

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
ancestry.com/	1.2 s
www.ancestry.com/	0.0 ms

Diagnostics

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 3.7 KiB

URL	Transfer Size	Est Savings
/etc.clientlibs/ancestry/clientlibs/clientlib-site-split....	28.7 KiB	3.7 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: 290 ms 52.9 KiB

URL	Transfer Size	Est Savings
/etc.clientlibs/ancestry/clientlibs/clientlib-site-split....	28.0 KiB	27.8 KiB
www.ancestrycdn.com/ui/2.69.0/css/core.css	26.3 KiB	25.1 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: 1.5 s 767.3 KiB

URL	Transfer Size	Est Savings
/etc.clientlibs/ancestry/clientlibs/clientlib-site-split....	171.7 KiB	110.1 KiB
www.googletagmanager.com/gtag/js?id=G-4QT8FMEX30&cx=c&gtm=4e64h1	172.6 KiB	66.3 KiB
www.googletagmanager.com/gtag/js?id=G-LMK6K2LSJH&cx=c&gtm=4e64h1	159.1 KiB	64.5 KiB
www.googletagmanager.com/gtag/destination?id=DC-8889547&cx=c&gtm=4e64h1	131.5 KiB	62.0 KiB
www.googletagmanager.com/gtag/destination?id=AW-994238695&cx=c&gtm=4e64h1	141.8 KiB	59.7 KiB
www.googletagmanager.com/gtag/destination?id=AW-16499174463&cx=c&gtm=4e64h1	140.0 KiB	59.2 KiB
www.googletagmanager.com/gtag/destination?id=DC-10399626&cx=c&gtm=4e64h1	131.8 KiB	59.1 KiB
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMQ.js	109.2 KiB	55.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-PF2LHSF	195.7 KiB	45.4 KiB
connect.facebook.net/en_US/fbevents.js	96.5 KiB	34.9 KiB
www.ancestrycdn.com/tao/at/2.7.5/at.js	49.0 KiB	32.8 KiB
/etc.clientlibs/ancestry/clientlibs/clientlib-js-base.min...	43.1 KiB	30.1 KiB
/etc.clientlibs/clientlibs/granite/jquery.min.ACSHASH83d7...	33.8 KiB	22.6 KiB
/dxjsmodule/12.1a2b7192fd54e87d3971.chunk.js?Q_CLIENTVERS...	35.7 KiB	22.3 KiB
/dxjsmodule/CoreModule.js?Q_CLIENTVERSION=2.46.0&Q_CLIENT...	30.9 KiB	22.1 KiB
www.ancestrycdn.com/ui/2.69.0/js/core.js	30.1 KiB	21.0 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
www.ancestrycdn.com/webui-unifiedtracking/2.0.10/request-header-overrides.js	1.4 s	1.4 s	8.1 ms
www.ancestry.com/	1.1 s	474 ms	29 ms
www.googletagmanager.com/gtm.js?id=GTM-PF2LHSF	919 ms	818 ms	64 ms
Unattributable	696 ms	127 ms	0.0 ms
www.googletagmanager.com/gtag/destination?id=AW-994238695&cx=c&gtm=4e64h1	407 ms	291 ms	49 ms
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMQ.js	342 ms	281 ms	59 ms
www.googletagmanager.com/gtag/destination?id=AW-16499174463&cx=c&gtm=4e64h1	338 ms	285 ms	50 ms
www.googletagmanager.com/gtag/destination?id=DC-8889547&cx=c&gtm=4e64h1	329 ms	290 ms	36 ms
www.googletagmanager.com/gtag/js?id=G-4QT8FMEX30&cx=c&gtm=4e64h1	321 ms	275 ms	41 ms
www.ancestry.com/cdn-cgi/challenge-platform/scripts/jsd/main.js	303 ms	263 ms	2.2 ms
www.googletagmanager.com/gtag/js?id=G-LMK6K2LSJH&cx=c&gtm=4e64h1	287 ms	247 ms	38 ms
/dxjsmodule/12.1a2b7192fd54e87d3971.chunk.js?Q_CLIENTVERS...	286 ms	260 ms	16 ms
www.googletagmanager.com/gtag/destination?id=DC-10399626&cx=c&gtm=4e64h1	263 ms	233 ms	29 ms
www.ancestrycdn.com/tao/at/2.7.5/at.js	198 ms	160 ms	21 ms
s.pinimg.com/ct/lib/main.10d2511a.js	196 ms	168 ms	10 ms
/signals/config/1411840285724878?v=2.9.303&r=stable&domai...	144 ms	128 ms	16 ms
/etc.clientlibs/ancestry/clientlibs/clientlib-site-split....	139 ms	88 ms	51 ms
assets.revlifter.io/838e2ddb-68e7-4a26-a839-a090f3fd5cd7.js	130 ms	121 ms	3.3 ms
connect.facebook.net/en_US/fbevents.js	125 ms	96 ms	28 ms
www.ancestrycdn.com/webui-unifiedtracking/2.0.10/unified-tracking.js	124 ms	97 ms	10 ms
/mit/api/geo/rd?sourceUrl=https%3A%2F%2Fwww.ancestry.com%...	98 ms	65 ms	0.7 ms
s.yimg.com/wi/ytc.js	68 ms	61 ms	1.8 ms
/etc.clientlibs/clientlibs/granite/moment.min.ACSHASHb693...	67 ms	58 ms	8.1 ms
/etc.clientlibs/ancestry/clientlibs/clientlib-js-base.min...	61 ms	41 ms	15 ms
analytics.tiktok.com/i18n/pixel/static/identify_5cff1caf.js	50 ms	32 ms	18 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	6.8 s
Other	798 ms
Script Parsing & Compilation	708 ms
Style & Layout	397 ms
Parse HTML & CSS	154 ms
Garbage Collection	137 ms
Rendering	59 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

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
Ancestry Home `div.cmp-header__logo > div.cmp-image > a.cmp-image__link > img.cmp-image__image`	/content/experience-fragments/global-xf/header/en-us-acom...
finding your roots `div.aem-Grid > div.image > div.cmp-image > img.cmp-image__image`	data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7

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

●Layout shift culprits

●Optimize DOM size

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify JavaScript

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

●User Timing marks and measures 20 user timings

●Avoid long main-thread tasks 20 long tasks found

●Network Requests

●Network Round Trip Times 170 ms

●Server Backend Latencies 480 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○Avoid non-composited animations

○Avoid large layout shifts

Accessibility

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

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
Not sure what to do? `div.modal > div#geoModalCopy > div#geoModalBar > span.bold`
Relax, we’ll send you to Ancestry.fr in 10 seconds. `div.modal > div#geoModalCopy > div#geoModalBar > span`

These are opportunities to improve the legibility of your content.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

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

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

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

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

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

●`[role]` values are valid

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

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

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

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

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

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

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

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

●Links have a discernible name

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

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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

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

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

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

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

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

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

○ARIA IDs are unique

○No form fields have multiple labels

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

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

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

○Form elements have associated labels

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

○`[lang]` attributes have a valid value

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

○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.	www.ancestry.com/ line 2, col 11985
SharedStorage	www.ancestry.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	www.ancestry.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge	www.ancestry.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
AttributionReporting	www.ancestrycdn.com/webui-unifiedtracking/2.0.10/request-header-overrides.js

●Uses HTTPS

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

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

●Ensure CSP is effective against XSS attacks

●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

○Use a strong HSTS policy

○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.ancestry.com/c/ancestry-family	Learn more
www.ancestry.com/c/ancestry-family	Learn more
www.ancestry.com/dna/	Learn more
www.ancestry.com/dna/	Learn more

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

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○robots.txt is valid