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
d2kfnvwohu0503.cloudfront.net/video/ip_landing_video_350kbps.mp4	0.0 ms	789.2 KiB
d2kfnvwohu0503.cloudfront.net/fonts/LyonDisplay-Regular-Web.ttf	0.0 ms	158.6 KiB
/js/vendor.min.js?v=92c177972ce291dec04ec903f691c3925c982...	0.0 ms	108.7 KiB
/js/main.min.js?v=a949851f0a8ee625a7893857b94481360a89b15...	0.0 ms	68.6 KiB
/img/landing_video_poster.png?v=65d08596d04226dd3612ba473...	0.0 ms	58.6 KiB
d2kfnvwohu0503.cloudfront.net/fonts/LyonText-Bold-Web.woff	0.0 ms	58.3 KiB
d2kfnvwohu0503.cloudfront.net/fonts/LyonText-Regular-Web.woff	0.0 ms	57.2 KiB
/css/main.min.css?v=0448d2b3a16473ecb2c6ab8786348384fd9a8...	0.0 ms	56.7 KiB
/img/landing_mobile_4.png?v=5e7599e46bd4c2089d37a3e114f7e...	0.0 ms	41.9 KiB
/js/landing.min.js?v=f6bbaa85bda0e2a6ab47a3609523561d2d19...	0.0 ms	33.7 KiB
/img/landing_mobile_2.png?v=6c40440adf166a2f23e2bd690113e...	0.0 ms	25.7 KiB
/img/landing_mobile_0.png?v=43b2fbfda039bbfb0c257824278bb...	0.0 ms	22.6 KiB
/img/landing_mobile_3.png?v=bf0159603cbc965accd184a337d7e...	0.0 ms	20.0 KiB
/img/landing_mobile_1.png?v=b3e955c41da1fc5767695a5a55835...	0.0 ms	17.8 KiB
/img/landing_video_fallback.png?v=4a909e13c460a0b0e266930...	0.0 ms	12.8 KiB
use.typekit.net/any5kzc.js	600.0 s	6.9 KiB
/css/landing.min.css?v=10f25f976b937ee395e6b38cd972bd6d2a...	0.0 ms	5.3 KiB
/img/landing_read_anywhere.png?v=858e349b49587cd54ae0b482...	0.0 ms	3.4 KiB
/img/landing_notes.png?v=ce19d10bcf9beb48f15ffa86a7f175f0...	0.0 ms	3.4 KiB
/img/landing_save_anything.png?v=3ca73e242e1aa194612923d0...	0.0 ms	3.0 KiB
d2kfnvwohu0503.cloudfront.net/img/logo@2x.png	0.0 ms	2.5 KiB
/js/jstz-1.0.4.min.js?v=ff08a13ff22ac21dc4474115a8e084194...	0.0 ms	2.1 KiB
www.gstatic.com/recaptcha/api2/logo_48.png	604800.0 s	2.3 KiB
/p.gif?s=1&k=any5kzc&ht=tk&h=instapaper.com&f=4455.5018.5...	604800.0 s	205 B

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
d2kfnvwohu0503.cloudfront.net/fonts/LyonDisplay-Regular-Web.woff	95 ms
use.typekit.net/af/f0ee97/00000000000000003b9adee9/27/l?subset_id=2&fvd=i4&v=3	35 ms
use.typekit.net/af/61961a/00000000000000000001707c/27/l?subset_id=1&fvd=n7&v=3	30 ms
use.typekit.net/af/d3823a/000000000000000000017087/27/l?subset_id=1&fvd=n4&v=3	25 ms
use.typekit.net/af/7b0f23/00000000000000003b9adeeb/27/l?subset_id=2&fvd=n4&v=3	20 ms
use.typekit.net/af/6a3278/000000000000000000017080/27/l?subset_id=1&fvd=i4&v=3	15 ms
use.typekit.net/af/683819/00000000000000003b9aded3/27/l?subset_id=2&fvd=n7&v=3	15 ms
use.typekit.net/af/731201/00000000000000003b9adee0/27/l?subset_id=2&fvd=n6&v=3	10 ms
d2kfnvwohu0503.cloudfront.net/fonts/LyonText-Regular-Web.woff	10 ms
d2kfnvwohu0503.cloudfront.net/fonts/LyonText-Bold-Web.woff	10 ms
d2kfnvwohu0503.cloudfront.net/fonts/LyonDisplay-Regular-Web.ttf	10 ms
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	10 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:37.76 source:map[column:30048 line:2 type:source-location url:https://d2kfnvwohu0503.cloudfront.net/js/vendor.min.js?v=92c177972ce291dec04ec903f691c3925c98292d443820a6cb3eb774e4c1363795dcae3fd7d416e9851999d33538c959de1fe2ebc0725d68104bd0b5b87a195c 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:34.057 source:map[column:31073 line:1 type:source-location url:https://d2kfnvwohu0503.cloudfront.net/js/vendor.min.js?v=92c177972ce291dec04ec903f691c3925c98292d443820a6cb3eb774e4c1363795dcae3fd7d416e9851999d33538c959de1fe2ebc0725d68104bd0b5b87a195c urlProvider:network]] map[reflowTime:3.703 source:map[column:55 line:1773 type:source-location url:https://d2kfnvwohu0503.cloudfront.net/js/vendor.min.js?v=92c177972ce291dec04ec903f691c3925c98292d443820a6cb3eb774e4c1363795dcae3fd7d416e9851999d33538c959de1fe2ebc0725d68104bd0b5b87a195c 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.

	URL	Resource Size	Est Savings
eReader `div.hero_viewport_center > div.landing_animation_wrapper > div.hero_image_no_autoplay > img#last_animated_device`	/img/landing_mobile_4.png?v=5e7599e46bd4c2089d37a3e114f7e...	41.5 KiB	13.1 KiB
Android `div.hero_viewport_center > div.landing_animation_wrapper > div.hero_image_no_autoplay > img.js_animated_device`	/img/landing_mobile_2.png?v=6c40440adf166a2f23e2bd690113e...	25.4 KiB	8.0 KiB
iPhone `div.hero_viewport_center > div.landing_animation_wrapper > div.hero_image_no_autoplay > img.js_animated_device`	/img/landing_mobile_0.png?v=43b2fbfda039bbfb0c257824278bb...	22.2 KiB	7.0 KiB
Desktop `div.hero_viewport_center > div.landing_animation_wrapper > div.hero_image_no_autoplay > img#second_to_last_animated_device`	/img/landing_mobile_3.png?v=bf0159603cbc965accd184a337d7e...	19.7 KiB	6.2 KiB
iPad `div.hero_viewport_center > div.landing_animation_wrapper > div.hero_image_no_autoplay > img.js_animated_device`	/img/landing_mobile_1.png?v=b3e955c41da1fc5767695a5a55835...	17.4 KiB	5.5 KiB

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-2-IMG

nodeLabel: iPhone

path: 1,HTML,1,BODY,1,MAIN,0,SECTION,0,DIV,0,DIV,0,DIV,1,DIV,0,IMG

selector: div.hero_viewport_center > div.landing_animation_wrapper > div.hero_image_no_autoplay > img.js_animated_device

snippet: <img class="js_animated_device animate" src="https://d2kfnvwohu0503.cloudfront.net/img/landing_mobile_0.png?v=43b2fbfda…" data-src="" alt="iPhone">

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

value: no origins were preconnected

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

title: Preconnect candidates

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
use.typekit.net/any5kzc.js	6.9 KiB	151 ms
/js/vendor.min.js?v=92c177972ce291dec04ec903f691c3925c982...	108.7 KiB	1.9 s
/js/main.min.js?v=a949851f0a8ee625a7893857b94481360a89b15...	68.6 KiB	1.1 s
/css/main.min.css?v=0448d2b3a16473ecb2c6ab8786348384fd9a8...	56.7 KiB	2.0 s
/css/landing.min.css?v=10f25f976b937ee395e6b38cd972bd6d2a...	5.3 KiB	150 ms

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.

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

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: 450 ms 83.1 KiB

URL	Transfer Size	Est Savings
/js/main.min.js?v=a949851f0a8ee625a7893857b94481360a89b15...	68.3 KiB	49.0 KiB
/js/landing.min.js?v=f6bbaa85bda0e2a6ab47a3609523561d2d19...	33.4 KiB	22.1 KiB
/js/vendor.min.js?v=92c177972ce291dec04ec903f691c3925c982...	108.4 KiB	12.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: 300 ms 53.8 KiB

URL	Transfer Size	Est Savings
/css/main.min.css?v=0448d2b3a16473ecb2c6ab8786348384fd9a8...	56.3 KiB	53.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: 3.0 s 349.8 KiB

URL	Transfer Size	Est Savings
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	361.8 KiB	176.7 KiB
/js/vendor.min.js?v=92c177972ce291dec04ec903f691c3925c982...	108.4 KiB	83.8 KiB
www.googletagmanager.com/gtag/js?id=G-YY0306L5MG	159.8 KiB	68.1 KiB
/js/main.min.js?v=a949851f0a8ee625a7893857b94481360a89b15...	68.3 KiB	21.2 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
Script Evaluation	1.4 s
Other	506 ms
Script Parsing & Compilation	286 ms
Style & Layout	256 ms
Parse HTML & CSS	63 ms
Rendering	25 ms
Garbage Collection	24 ms

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
d2kfnvwohu0503.cloudfront.net/video/ip_landing_video_350kbps.mp4	789.2 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	362.4 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	361.9 KiB
www.googletagmanager.com/gtag/js?id=G-YY0306L5MG	160.1 KiB
d2kfnvwohu0503.cloudfront.net/fonts/LyonDisplay-Regular-Web.ttf	158.6 KiB
/js/vendor.min.js?v=92c177972ce291dec04ec903f691c3925c982...	108.7 KiB
/js/main.min.js?v=a949851f0a8ee625a7893857b94481360a89b15...	68.6 KiB
use.typekit.net/af/61961a/00000000000000000001707c/27/l?subset_id=1&fvd=n7&v=3	66.2 KiB
use.typekit.net/af/d3823a/000000000000000000017087/27/l?subset_id=1&fvd=n4&v=3	65.9 KiB
use.typekit.net/af/6a3278/000000000000000000017080/27/l?subset_id=1&fvd=i4&v=3	64.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
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	1.0 s	855 ms	114 ms
Unattributable	365 ms	15 ms	0.0 ms
/js/vendor.min.js?v=92c177972ce291dec04ec903f691c3925c982...	343 ms	119 ms	44 ms
www.googletagmanager.com/gtag/js?id=G-YY0306L5MG	334 ms	268 ms	60 ms
instapaper.com/	263 ms	20 ms	2.7 ms
use.typekit.net/any5kzc.js	61 ms	43 ms	2.6 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
Read Anywhere `main.main > section > div.landing_constrained > img`	/img/landing_read_anywhere.png?v=858e349b49587cd54ae0b482...
Save Anything `main.main > section > div.landing_constrained > img`	/img/landing_save_anything.png?v=3ca73e242e1aa194612923d0...
Create Notes `main.main > section > div.landing_constrained > img`	/img/landing_notes.png?v=ce19d10bcf9beb48f15ffa86a7f175f0...

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

●Max Potential First Input Delay 120 ms

●Layout shift culprits

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●User Timing marks and measures 5 user timings

●Avoid long main-thread tasks 11 long tasks found

●Avoid non-composited animations 11 animated elements found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 60 ms

●Server Backend Latencies 60 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 120 ms

○INP breakdown

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

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.js `html.js`

These are opportunities to improve the interpretation of your content by users in different locales.

Contrast

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
iPhone `section > div.landing_constrained > p > a`
iPad `section > div.landing_constrained > p > a`
Android `section > div.landing_constrained > p > a`
Kindle `section > div.landing_constrained > p > a`
Kobo `section > div.landing_constrained > p > a`

These are opportunities to improve the legibility of your content.

Names and labels

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#control_bar > div.container-fluid > aside.logo > a `div#control_bar > div.container-fluid > aside.logo > a`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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

●Image elements have `[alt]` attributes

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

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●ARIA IDs are unique

○`[accesskey]` values are unique

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

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

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

○Deprecated ARIA roles were not used

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

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

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

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

○`[role]` values are valid

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

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

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

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

○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

○No form fields have multiple labels

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

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

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

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

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

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

○`[lang]` attributes have a valid value

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

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

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

Best Practices

General

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
instapaper.com/	`Access to font at 'https://d2kfnvwohu0503.cloudfront.net/fonts/LyonDisplay-Regular-Web.woff' from origin 'https://instapaper.com' has been blocked by CORS policy: The 'Access-Control-Allow-Origin' header has a value 'https://www.instapaper.com' that is not equal to the supplied origin.`
d2kfnvwohu0503.cloudfront.net/fonts/LyonDisplay-Regular-Web.woff	`Failed to load resource: net::ERR_FAILED`

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

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
`div#control_bar > div.container-fluid > nav.auth_nav > a.speed_endstate_ui`
div#sign_in_modal_group > form.modal_form > div.form_line_forgot_password > a.open_modal `div#sign_in_modal_group > form.modal_form > div.form_line_forgot_password > a.open_modal`

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

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`