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
www.wassenaar.org/app/uploads/2025/06/2025-ETB-PLM-Chair-and-HOS-rev.jpg	0.0 ms	392.1 KiB
www.wassenaar.org/app/themes/wassenaar/dist/styles/main.css	0.0 ms	248.3 KiB
www.wassenaar.org/app/uploads/2020/01/WA_video.png	0.0 ms	247.3 KiB
www.wassenaar.org/app/uploads/2015/10/ammunition.jpg	0.0 ms	112.2 KiB
www.wassenaar.org/app/uploads/2015/10/rifles.jpg	0.0 ms	108.7 KiB
www.wassenaar.org/app/uploads/2026/03/outreach202601.jpeg	0.0 ms	107.7 KiB
www.wassenaar.org/app/uploads/2015/10/radar.jpg	0.0 ms	99.5 KiB
www.wassenaar.org/app/uploads/2015/10/customs.jpg	0.0 ms	99.0 KiB
www.wassenaar.org/app/uploads/2015/10/meeting.jpg	0.0 ms	97.4 KiB
www.wassenaar.org/app/uploads/2015/10/turbine.jpg	0.0 ms	93.0 KiB
www.wassenaar.org/app/uploads/2015/10/cpu.jpg	0.0 ms	92.7 KiB
www.wassenaar.org/app/uploads/2015/10/mortar.jpg	0.0 ms	90.4 KiB
www.wassenaar.org/app/uploads/2015/10/export.jpg	0.0 ms	84.5 KiB
www.wassenaar.org/app/uploads/2015/10/rocket.jpg	0.0 ms	81.8 KiB
www.wassenaar.org/app/uploads/2015/10/satellite.jpg	0.0 ms	79.9 KiB
www.wassenaar.org/app/themes/wassenaar/dist/fonts/entypo-fontello.woff?9870425	0.0 ms	41.0 KiB
www.wassenaar.org/wp/wp-includes/css/dashicons.min.css?ver=6.9.4	0.0 ms	36.4 KiB
www.wassenaar.org/app/uploads/2015/10/uav.jpg	0.0 ms	33.6 KiB
/app/themes/wassenaar/assets/scripts/jquery-3.5.1.min.js?...	0.0 ms	31.7 KiB
collector.wassenaar.org/matomo.js	0.0 ms	22.9 KiB
/app/themes/wassenaar/dist/fonts/glyphicons-halflings-reg...	0.0 ms	19.1 KiB
www.wassenaar.org/wp/wp-includes/css/dist/block-library/style.min.css?ver=6.9.4	0.0 ms	17.1 KiB
/app/plugins/wpsolr-pro/wpsolr/core/js/loadingoverlay/loa...	0.0 ms	13.2 KiB
www.wassenaar.org/app/themes/wassenaar/dist/scripts/main.js	0.0 ms	12.0 KiB
www.wassenaar.org/app/uploads/2024/04/in_wa.png	0.0 ms	10.5 KiB
www.wassenaar.org/app/plugins/cf7-conditional-fields/js/scripts.js?ver=2.6.8	0.0 ms	9.9 KiB
/app/plugins/wpsolr-pro/wpsolr/core/js/autocomplete_solr....	0.0 ms	8.6 KiB
/app/plugins/wpsolr-pro/wpsolr/core/js/devbridge/jquery.a...	0.0 ms	8.5 KiB
www.wassenaar.org/wp/wp-includes/js/wp-emoji-release.min.js?ver=6.9.4	0.0 ms	6.8 KiB
www.wassenaar.org/app/plugins/contact-form-7/includes/js/index.js?ver=6.1.5	0.0 ms	5.7 KiB
/app/themes/wassenaar/assets/scripts/jquery-migrate-3.3.0...	0.0 ms	5.4 KiB
www.wassenaar.org/app/plugins/contact-form-7/includes/swv/js/index.js?ver=6.1.5	0.0 ms	4.9 KiB
www.wassenaar.org/wp/wp-includes/js/dist/i18n.min.js?ver=c26c3dc7bed366793375	0.0 ms	3.7 KiB
www.wassenaar.org/wp/wp-includes/js/dist/hooks.min.js?ver=dd5603f07f9220ed27f1	0.0 ms	3.4 KiB
/app/plugins/wpsolr-pro/wpsolr/core/bower_components/jsur...	0.0 ms	3.0 KiB
www.wassenaar.org/app/plugins/wpsolr-pro/wpsolr/core/css/style.css?ver=22.4	0.0 ms	2.8 KiB
www.wassenaar.org/app/themes/wassenaar/dist/scripts/jquery.scrollTo.js	0.0 ms	2.7 KiB
www.wassenaar.org/app/plugins/contact-form-7/includes/css/styles.css?ver=6.1.5	0.0 ms	2.5 KiB
www.wassenaar.org/app/plugins/menu-image/includes/css/menu-image.css?ver=3.13	0.0 ms	2.3 KiB
www.wassenaar.org/app/plugins/cf7-conditional-fields/style.css?ver=2.6.8	0.0 ms	2.0 KiB
www.wassenaar.org/app/themes/wassenaar/dist/images/chevron_down.svg	0.0 ms	1.7 KiB
/app/plugins/sitepress-multilingual-cms/res/js/cookies/la...	0.0 ms	1.7 KiB
/app/themes/wassenaar/assets/scripts/contact-form-scripts...	0.0 ms	1.7 KiB
/app/plugins/sitepress-multilingual-cms/templates/languag...	0.0 ms	1.6 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.wassenaar.org/app/themes/wassenaar/dist/fonts/entypo-fontello.woff?9870425	175 ms
/app/themes/wassenaar/dist/fonts/glyphicons-halflings-reg...	175 ms
/s/opensans/v44/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu...	10 ms
/s/opensans/v44/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTSumu...	10 ms
/s/opensans/v44/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTUGmu...	5.0 ms

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

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
www.wassenaar.org/app/themes/wassenaar/dist/styles/main.css	248.3 KiB	1.5 s
/app/themes/wassenaar/assets/scripts/jquery-3.5.1.min.js?...	31.7 KiB	151 ms
/app/themes/wassenaar/assets/scripts/contact-form-scripts...	1.7 KiB
/app/themes/wassenaar/assets/scripts/jquery-migrate-3.3.0...	5.4 KiB
www.wassenaar.org/wp/wp-includes/css/dist/block-library/style.min.css?ver=6.9.4	17.1 KiB
www.wassenaar.org/app/plugins/cf7-conditional-fields/style.css?ver=2.6.8	2.0 KiB	151 ms
/app/plugins/sitepress-multilingual-cms/templates/languag...	1.6 KiB
www.wassenaar.org/app/plugins/wpsolr-pro/wpsolr/core/css/style.css?ver=22.4	2.8 KiB
www.wassenaar.org/wp/wp-includes/css/dashicons.min.css?ver=6.9.4	36.4 KiB	452 ms
www.wassenaar.org/app/plugins/contact-form-7/includes/css/styles.css?ver=6.1.5	2.5 KiB
www.wassenaar.org/app/plugins/menu-image/includes/css/menu-image.css?ver=3.13	2.3 KiB
fonts.googleapis.com/css?family=Open+Sans:400,300,600,700	2.3 KiB	760 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
section.widget_text > div.textwidget > a.video-link > img `section.widget_text > div.textwidget > a.video-link > img`	www.wassenaar.org/app/uploads/2025/06/2025-ETB-PLM-Chair-and-HOS-rev.jpg	390.2 KiB	322.9 KiB
section.widget_text > div.textwidget > a.video-link > img `section.widget_text > div.textwidget > a.video-link > img`	www.wassenaar.org/app/uploads/2020/01/WA_video.png	245.6 KiB	204.6 KiB
section.widget_text > div.textwidget > a.video-link > img `section.widget_text > div.textwidget > a.video-link > img`	www.wassenaar.org/app/uploads/2026/03/outreach202601.jpeg	106.1 KiB	40.8 KiB
section.widget > div.textwidget > a.glyphicon > img `section.widget > div.textwidget > a.glyphicon > img`	www.wassenaar.org/app/uploads/2024/04/in_wa.png	9.0 KiB	8.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: 1.2 s

URL	Time Spent
wassenaar.org/	1.2 s
www.wassenaar.org/	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

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: 670 ms 110.8 KiB

URL	Transfer Size	Est Savings
www.wassenaar.org/app/themes/wassenaar/dist/styles/main.css	246.8 KiB	60.3 KiB
www.wassenaar.org/wp/wp-includes/css/dashicons.min.css?ver=6.9.4	34.9 KiB	34.9 KiB
www.wassenaar.org/wp/wp-includes/css/dist/block-library/style.min.css?ver=6.9.4	15.6 KiB	15.5 KiB

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
Style & Layout	3.2 s
Rendering	1.9 s
Other	1.1 s
Script Evaluation	477 ms
Parse HTML & CSS	132 ms
Script Parsing & Compilation	82 ms

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: 0.0 ms 10.0 KiB

URL	Transfer Size	Est Savings
www.wassenaar.org/app/plugins/cf7-conditional-fields/js/scripts.js?ver=2.6.8	8.4 KiB	3.5 KiB
/app/plugins/wpsolr-pro/wpsolr/core/js/autocomplete_solr....	7.1 KiB	3.4 KiB
/app/plugins/wpsolr-pro/wpsolr/core/js/devbridge/jquery.a...	7.0 KiB	3.2 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
section.widget_text > div.textwidget > a.video-link > img `section.widget_text > div.textwidget > a.video-link > img`	www.wassenaar.org/app/uploads/2025/06/2025-ETB-PLM-Chair-and-HOS-rev.jpg
section.widget_text > div.textwidget > a.video-link > img `section.widget_text > div.textwidget > a.video-link > img`	www.wassenaar.org/app/uploads/2020/01/WA_video.png
section.widget_text > div.textwidget > a.video-link > img `section.widget_text > div.textwidget > a.video-link > img`	www.wassenaar.org/app/uploads/2026/03/outreach202601.jpeg
section.widget > div.textwidget > a.glyphicon > img `section.widget > div.textwidget > a.glyphicon > img`	www.wassenaar.org/app/uploads/2024/04/in_wa.png

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

●Max Potential First Input Delay 80 ms

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Reduce unused JavaScript

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

●JavaScript execution time 0.4 s

●Avoid long main-thread tasks 3 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 170 ms

●Server Backend Latencies 370 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid non-composited animations

○Avoid large layout shifts

Accessibility

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

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
Highlights `div.row > div.col-md-5 > section.widget > h3`
Statement issued by 2025 Plenary Chair `section.widget > div#recent-posts > div.item > a`
5 DECEMBER 2025 `section.widget > div#recent-posts > div.item > span.post-date`
List of Dual-Use Goods and Technologies & Munitions List (2025) Corr. `section.widget > div#recent-posts > div.item > a`
5 DECEMBER 2025 `section.widget > div#recent-posts > div.item > span.post-date`
Summary of Most Recent Changes to Lists Corr. `section.widget > div#recent-posts > div.item > a`
5 DECEMBER 2025 `section.widget > div#recent-posts > div.item > span.post-date`
Best Practice Guidelines on Internal Compliance Programmes `section.widget > div#recent-posts > div.item > a`
5 DECEMBER 2025 `section.widget > div#recent-posts > div.item > span.post-date`
READ MORE `main.main > div.row > div.col-md-5 > a.read-more`
Contact `main.main > div.row > div.col-md-5 > h3`
CONTACT US `div.col-md-5 > div.textwidget > p > a.read-more`
Introduction `main.main > div.row > div.col-md-7 > h3`
About Us `div.row > div.col-md-7 > p > a`
here `div.row > div.col-md-7 > p > a`
Frequently Asked Questions (FAQ) `div.row > div.col-md-7 > p > a`
Recent Activities `aside.sidebar > section.widget_text > div.textwidget > h3`
Head of Secretariat Addresses the Asian Export Control Seminar `aside.sidebar > section.widget_text > div.textwidget > a.video-link`
Enhanced Technical Briefing for WA Outreach Partners `aside.sidebar > section.widget_text > div.textwidget > a.video-link`
Introductory Video `aside.sidebar > section.widget_text > div.textwidget > a.video-link`
Contact `div.mobile-footer > section.widget > div.textwidget > h3`

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
section.widget_text > div.textwidget > a.video-link > img `section.widget_text > div.textwidget > a.video-link > img`
section.widget_text > div.textwidget > a.video-link > img `section.widget_text > div.textwidget > a.video-link > img`
section.widget_text > div.textwidget > a.video-link > img `section.widget_text > div.textwidget > a.video-link > img`
section.widget > div.textwidget > a.glyphicon > img `section.widget > div.textwidget > a.glyphicon > 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
div.mobile-footer > section.widget > div.textwidget > a.glyphicon `div.mobile-footer > section.widget > div.textwidget > a.glyphicon`
div.mobile-footer > section.widget > div.textwidget > a.glyphicon `div.mobile-footer > section.widget > div.textwidget > a.glyphicon`

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.

○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

●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

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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●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

○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

○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

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

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

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.wassenaar.org/wp/favicon.ico	`Failed to load resource: the server responded with a status of 404 ()`

●Uses HTTPS

●Avoids deprecated APIs

●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

●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

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.wassenaar.org/blog	READ MORE
/app/uploads/2019/12/WA-DOC-19-Public-Docs-Vol-I-Founding...	here

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
section.widget_text > div.textwidget > a.video-link > img `section.widget_text > div.textwidget > a.video-link > img`
section.widget_text > div.textwidget > a.video-link > img `section.widget_text > div.textwidget > a.video-link > img`
section.widget_text > div.textwidget > a.video-link > img `section.widget_text > div.textwidget > a.video-link > img`
section.widget > div.textwidget > a.glyphicon > img `section.widget > div.textwidget > a.glyphicon > img`

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

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #	Content	Error
33	`Disallow: ?wptheme=`	`Pattern should either be empty, start with "/" or "*"`

To appear in search results, crawlers need access to your app.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Page has successful HTTP status code

●Links are crawlable

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`