Skip to content
https://youradchoices.ca

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

29

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.

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.

URLEst Savings
use.typekit.net/af/da506f/00000000000000007735f990/31/l?subset_id=2&fvd=n3&v=350 ms
use.typekit.net/af/4fa2f6/00000000000000007753c3b6/31/l?subset_id=2&fvd=n6&v=345 ms
use.typekit.net/af/2ff9be/00000000000000007735f999/31/l?subset_id=2&fvd=n7&v=345 ms
use.typekit.net/af/1fbf9b/00000000000000007735f98d/31/l?subset_id=2&fvd=n4&v=340 ms
use.typekit.net/af/742085/00000000000000007735f992/31/l?subset_id=2&fvd=n5&v=340 ms
use.typekit.net/af/e7e7b3/00000000000000007735f99a/31/l?subset_id=2&fvd=n6&v=340 ms
use.typekit.net/af/ef2702/00000000000000007753c3b7/31/l?subset_id=2&fvd=n9&v=335 ms
use.typekit.net/af/299e31/00000000000000007753c3bb/31/l?subset_id=2&fvd=i6&v=335 ms
use.typekit.net/af/a7ae71/00000000000000007753c3b2/31/l?subset_id=2&fvd=i7&v=335 ms
use.typekit.net/af/9f5daf/00000000000000007753c3bf/31/l?subset_id=2&fvd=n7&v=330 ms
use.typekit.net/af/0789c1/00000000000000007753c3ad/31/l?subset_id=2&fvd=n8&v=330 ms
use.typekit.net/af/947e89/00000000000000007735b901/31/l?subset_id=2&fvd=i7&v=325 ms
use.typekit.net/af/780d3f/00000000000000007753c3b3/31/l?subset_id=2&fvd=i9&v=325 ms
use.typekit.net/af/1b7608/00000000000000007753c3b0/31/l?subset_id=2&fvd=n5&v=325 ms
use.typekit.net/af/0b8052/00000000000000007758cf90/31/l?subset_id=2&fvd=i3&v=320 ms
use.typekit.net/af/38ea3a/00000000000000007758cf7d/31/l?subset_id=2&fvd=i7&v=320 ms
use.typekit.net/af/fd6e19/00000000000000007735b8f8/31/l?subset_id=2&fvd=i4&v=320 ms
use.typekit.net/af/d7ff92/00000000000000007735e609/31/l?subset_id=2&fvd=n4&v=315 ms
use.typekit.net/af/26f7ec/00000000000000007735e605/31/l?subset_id=2&fvd=n5&v=315 ms
use.typekit.net/af/5be242/00000000000000007735e603/31/l?subset_id=2&fvd=n7&v=315 ms
/static/5c055f98620b858a898bfcae/t/5c12aa9188251b557b445f...10 ms
/static/5c055f98620b858a898bfcae/t/5c12a94689858332629db9...10 ms
use.typekit.net/af/3888dc/00000000000000007735e606/31/l?subset_id=2&fvd=n3&v=310 ms
use.typekit.net/af/fdfc76/00000000000000007735b8f6/31/l?subset_id=2&fvd=n4&v=35.0 ms
use.typekit.net/af/507990/00000000000000007735b8ff/31/l?subset_id=2&fvd=n7&v=35.0 ms
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff25.0 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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:9.692 source:map[column:5104 line:1 type:source-location url:https://static1.squarespace.com/static/ta/55f0a9b0e4b0f3eb70352f6d/359/scripts/site-bundle.js urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:43.658 source:map[column:26071 line:3 type:source-location url:https://static1.squarespace.com/static/ta/55f0a9b0e4b0f3eb70352f6d/359/scripts/site-bundle.js urlProvider:network]] map[reflowTime:18.399 source:map[column:87469 line:74 type:source-location url:https://assets.squarespace.com/universal/scripts-compressed/common-685e8299b71caa80-min.en-US.js urlProvider:network]] map[reflowTime:2.217 source:map[column:31201 line:1 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js urlProvider:network]] map[reflowTime:0.084 source:map[column:31266 line:3 type:source-location url:https://static1.squarespace.com/static/ta/55f0a9b0e4b0f3eb70352f6d/359/scripts/site-bundle.js urlProvider:network]] map[reflowTime:2.805 source:map[column:213 line:4 type:source-location url:https://static1.squarespace.com/static/ta/55f0a9b0e4b0f3eb70352f6d/359/scripts/site-bundle.js urlProvider:network]] map[reflowTime:0.329 source:map[column:249 line:4 type:source-location url:https://static1.squarespace.com/static/ta/55f0a9b0e4b0f3eb70352f6d/359/scripts/site-bundle.js urlProvider:network]] map[reflowTime:4.721 source:map[column:30266 line:2 type:source-location url:https://static1.squarespace.com/static/ta/55f0a9b0e4b0f3eb70352f6d/359/scripts/site-bundle.js urlProvider:network]] map[reflowTime:0.356 source:map[column:6216 line:4 type:source-location url:https://static1.squarespace.com/static/ta/55f0a9b0e4b0f3eb70352f6d/359/scripts/site-bundle.js urlProvider:network]] map[reflowTime:1.397 source:map[column:3771 line:4 type:source-location url:https://static1.squarespace.com/static/ta/55f0a9b0e4b0f3eb70352f6d/359/scripts/site-bundle.js urlProvider:network]]]

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.

URLResource SizeEst Savings
YourAdChoices-CYCLE-REDslower.gif figure#yui_3_17_2_1_1776805156864_129 > div#yui_3_17_2_1_1776805156864_128 > div#yui_3_17_2_1_1776805156864_127 > img.loaded
/content/v1/5c055f98620b858a898bfcae/1549389806485-ICGOX3...2.1 MiB1.8 MiB
DAAC-WALKCYCLE-BLUEslower.gif figure#yui_3_17_2_1_1776805156864_100 > div#yui_3_17_2_1_1776805156864_99 > div#yui_3_17_2_1_1776805156864_98 > img.loaded
/content/v1/5c055f98620b858a898bfcae/1549062533683-83B820...863.3 KiB681.1 KiB
DAAC---QA-YELLOW-Web5.gif figure#yui_3_17_2_1_1776805156864_141 > div#yui_3_17_2_1_1776805156864_140 > div#yui_3_17_2_1_1776805156864_139 > img.loaded
/content/v1/5c055f98620b858a898bfcae/1548979696650-MPTF2N...175.1 KiB111.8 KiB
div.intrinsic > div.intrinsic-inner > div#yui_3_17_2_1_1776805156864_408 > img.loaded div.intrinsic > div.intrinsic-inner > div#yui_3_17_2_1_1776805156864_408 > img.loaded
/content/v1/5c055f98620b858a898bfcae/1548184031021-36NM8P...32.8 KiB8.0 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:22.626999755859377 label:Time to first byte subpart:timeToFirstByte] map[duration:1283.6590002441405 label:Resource load delay subpart:resourceLoadDelay] map[duration:63.168 label:Resource load duration subpart:resourceLoadDuration] map[duration:1417.703 label:Element render delay subpart:elementRenderDelay]]
lhId: page-1-IMG
nodeLabel: DAAC-WALKCYCLE-BLUEslower.gif
path: 1,HTML,2,BODY,3,DIV,2,DIV,1,DIV,0,MAIN,0,SECTION,1,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,FIGURE,0,DIV,0,DIV,0,IMG
selector: figure#yui_3_17_2_1_1776805156864_100 > div#yui_3_17_2_1_1776805156864_99 > div#yui_3_17_2_1_1776805156864_98 > img.loaded
snippet: <img data-stretch="false" data-src="https://images.squarespace-cdn.com/content/v1/5c055f98620b858a898bfcae/154…" data-image="https://images.squarespace-cdn.com/content/v1/5c055f98620b858a898bfcae/154…" data-image-dimensions="1200x1170" data-image-focal-point="0.5,0.5" alt="DAAC-WALKCYCLE-BLUEslower.gif" data-load="false" elementtiming="system-image-block" src="https://images.squarespace-cdn.com/content/v1/5c055f98620b858a898bfcae/154…" width="1200" height="1170" sizes="(max-width: 640px) 100vw, (max-width: 767px) 50vw, 50vw" style="display: block; object-fit: cover; width: 100%; height: 100%;" …>

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-1-IMG
nodeLabel: DAAC-WALKCYCLE-BLUEslower.gif
path: 1,HTML,2,BODY,3,DIV,2,DIV,1,DIV,0,MAIN,0,SECTION,1,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,FIGURE,0,DIV,0,DIV,0,IMG
selector: figure#yui_3_17_2_1_1776805156864_100 > div#yui_3_17_2_1_1776805156864_99 > div#yui_3_17_2_1_1776805156864_98 > img.loaded
snippet: <img data-stretch="false" data-src="https://images.squarespace-cdn.com/content/v1/5c055f98620b858a898bfcae/154…" data-image="https://images.squarespace-cdn.com/content/v1/5c055f98620b858a898bfcae/154…" data-image-dimensions="1200x1170" data-image-focal-point="0.5,0.5" alt="DAAC-WALKCYCLE-BLUEslower.gif" data-load="false" elementtiming="system-image-block" src="https://images.squarespace-cdn.com/content/v1/5c055f98620b858a898bfcae/154…" width="1200" height="1170" sizes="(max-width: 640px) 100vw, (max-width: 767px) 50vw, 50vw" style="display: block; object-fit: cover; width: 100%; height: 100%;" …>

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer SizeDuration
/universal/scripts-compressed/common-685e8299b71caa80-min...276.0 KiB2.3 s
/universal/scripts-compressed/commerce-ad9e32fad34293d6-m...189.2 KiB1.1 s
/universal/scripts-compressed/common-vendors-88286999a7ee...167.8 KiB2.9 s
/universal/scripts-compressed/common-vendors-stable-b8d71...80.2 KiB1.8 s
/universal/scripts-compressed/user-account-core-502565b71...32.4 KiB151 ms
/universal/scripts-compressed/extract-css-moment-js-vendo...44.2 KiB1.1 s
/static/ta/55f0a9b0e4b0f3eb70352f6d/359/scripts/site-bund...46.2 KiB1.1 s
ajax.googleapis.com/ajax/libs/jquery/2.2.0/jquery.min.js29.5 KiB1.1 s
ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js33.3 KiB1.7 s
assets.squarespace.com/@sqs/polyfiller/1.6/modern.js41.8 KiB1.4 s
/static/sitecss/5c055f98620b858a898bfcae/556/55f0aac0e4b0...82.3 KiB3.3 s
/universal/scripts-compressed/cldr-resource-pack-22c6db79...14.8 KiB453 ms
/website-component-definition/static-assets/website.compo...1.1 KiB
/website-component-definition/static-assets/website.compo...755 B
/website-component-definition/static-assets/website.compo...3.8 KiB159 ms
/universal/scripts-compressed/extract-css-runtime-a192575...16.8 KiB604 ms
fonts.googleapis.com/css2?family=Alice:ital,wght@0,400930 B785 ms
/static/custom-css/5c055f98620b858a898bfcae/5c0842654d7a9...3.3 KiB151 ms
/website-component-definition/static-assets/website.compo...525 B
/website-component-definition/static-assets/website.compo...332 B159 ms
/website-component-definition/static-assets/website.compo...2.9 KiB778 ms
/universal/styles-compressed/user-account-core-f82c59bd53...915 B151 ms
/universal/styles-compressed/commerce-d50e5960dc9fd059-mi...2.1 KiB755 ms
cdnjs.cloudflare.com/ajax/libs/flag-icon-css/2.6.0/css/flag-icon.css2.2 KiB782 ms

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.

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: 450 ms 78.0 KiB
URLTransfer SizeEst Savings
/static/sitecss/5c055f98620b858a898bfcae/556/55f0aac0e4b0...82.2 KiB78.0 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.

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.

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.

CategoryTime Spent
Script Evaluation3.5 s
Other1.0 s
Script Parsing & Compilation961 ms
Style & Layout424 ms
Garbage Collection133 ms
Parse HTML & CSS129 ms
Rendering49 ms

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
AdChoices in Canada div.Mobile-bar > div > a.Mobile-bar-branding > img.Mobile-bar-branding-logo
/content/v1/5c055f98620b858a898bfcae/1573239822493-7FTI37...

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

●Layout shift culprits
●Document request latency
●Optimize DOM size
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●User Timing marks and measures 47 user timings
●Avoid long main-thread tasks 20 long tasks found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 10 ms
●Server Backend Latencies 70 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 10 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○Avoid non-composited animations
91

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

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
div.intrinsic > div.intrinsic-inner > div#yui_3_17_2_1_1776805156864_408 > img.loaded div.intrinsic > div.intrinsic-inner > div#yui_3_17_2_1_1776805156864_408 > img.loaded

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
Association of Canadian Advertisers div.sqs-block-content > div.sqs-html-content > p > a
Canadian Marketing Association div.sqs-block-content > div.sqs-html-content > p > a
Institute of Canadian Agencies div.sqs-block-content > div.sqs-html-content > p > a
Association canadienne des annonceurs div.sqs-block-content > div.sqs-html-content > p > a
Association canadienne du marketing div.sqs-block-content > div.sqs-html-content > p > a
Canadian Media Directors' Council div.sqs-block-content > div.sqs-html-content > p > 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>`
●`[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
●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 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
●Links are distinguishable without relying on color.
●Links have a discernible name
●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
○`[accesskey]` values are unique
○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
○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
○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.
○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.
96

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.

SourceDescription
youradchoices.ca/ line 133, col 0
SyntaxError: Invalid or unexpected token
●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 clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
85

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.

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
div.intrinsic > div.intrinsic-inner > div#yui_3_17_2_1_1776805156864_408 > img.loaded div.intrinsic > div.intrinsic-inner > div#yui_3_17_2_1_1776805156864_408 > img.loaded

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

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Document has a meta description
●Page has successful HTTP status code
●Links are crawlable
●robots.txt is valid
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback