Skip to content
https://ewg.org

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.

28

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.

RequestCache TTLTransfer Size
/client_16f9efd0362a4/c6ea966df8231d554ff79bea842474ea.jpg0.0 ms680.7 KiB
/client_16f9efd0362a4/ff79c4a17b889acfb020cbb5f74d9805.jpg0.0 ms660.3 KiB
/client_16f9efd0362a4/e2eb552d5cbf5710464d7ba1cd26b882.jpg0.0 ms278.8 KiB
d3rse9xjbp8270.cloudfront.net/at.js900.0 s269.6 KiB
static.everyaction.com/ea-actiontag/at.js900.0 s269.6 KiB
connect.facebook.net/en_US/fbevents.js1200.0 s96.6 KiB
cdn.popt.in/pixel.js?id=16f9efd0362a41800.0 s80.9 KiB
cdn.fundraiseup.com/widget/AKWZXHJB0.0 ms65.0 KiB
/client_16f9efd0362a4/6cfcb8e447026a61da147020e9264272.png0.0 ms54.5 KiB
/679d2170c60630c1ec95c6eb/679d21c66f9dbbe0733ca426.js0.0 ms43.9 KiB
js.verygoodvault.com/vgs-collect/2.18.4/vgs-collect.js60.0 s43.8 KiB
/custom/16f9efd0362a4/FreightText Pro Book/FreightText Pr...0.0 ms43.0 KiB
/signals/config/431673573640385?v=2.9.303&r=stable&domain...1200.0 s44.6 KiB
/custom/16f9efd0362a4/Niveau Grotesk Regular/Niveau Grote...0.0 ms38.7 KiB
/custom/16f9efd0362a4/Niveau Grotesk Bold/Niveau Grotesk ...0.0 ms38.1 KiB
cdn.branch.io/branch-latest.min.js300.0 s23.5 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
/signals/config/367774270429261?v=2.9.303&r=stable&domain...1200.0 s16.1 KiB
d3rse9xjbp8270.cloudfront.net/extra.min.css900.0 s14.3 KiB
d3rse9xjbp8270.cloudfront.net/at.min.css900.0 s12.2 KiB
scripts.clarity.ms/0.8.59/clarity.js86400.0 s26.2 KiB
www.ewg.org/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/main.js?14400.0 s13.4 KiB
cdn.popt.in/css/poptin-style-en.css?ver=101800.0 s9.8 KiB
d362h7pxdteoyk.cloudfront.net/fonts/poppins/pxiEyp8kv8JHgFVrJJfecg.woff20.0 ms8.1 KiB
cdn.popt.in/css/brands.min.css1800.0 s5.4 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...86400.0 s10.7 KiB
cdn.fundraiseup.com/embed-data/elements-global/AKWZXHJB.js0.0 ms3.1 KiB
cdn.popt.in/css/poptin-animations.css?ver=101800.0 s2.8 KiB
/?family=Poppins&display=swap0.0 ms1.3 KiB
cdn.popt.in/validation/email/email-autofill.js1800.0 s1.5 KiB
/_r?sdk=web2.87.1&branch_key=key_live_eCxj0JQSbzzPNBW8cEF...0.0 ms667 B
/p.css?s=1&k=wyp4ngq&ht=tk&f=13464.13465.13472.13473.2707...604800.0 s172 B
/tr/?id=431673573640385&ev=PageView&dl=https%3A%2F%2Fwww....0.0 ms16 B
/tr/?id=367774270429261&ev=PageView&dl=https%3A%2F%2Fwww....0.0 ms16 B

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.

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:32.254 source:map[column:149513 line:2 type:source-location url:https://cdn.fundraiseup.com/widget/AKWZXHJB urlProvider:network]] map[reflowTime:0.128 source:map[column:120656 line:1 type:source-location url:https://static.fundraiseup.com/elementsApi.c0fc24ed4d35f527.js urlProvider:network]] map[reflowTime:16.862 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-ARTICLE
nodeLabel: EARTH DAY MATCH Double your impact today All gifts matched dollar-for-dollar un…
path: 1,HTML,1,BODY,3,DIV,0,DIV,0,DIV,1,MAIN,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,SPAN,0,ARTICLE
selector: div.views-row > div.views-field > span.field-content > article.gradient-blue
snippet: <article class="gradient-blue node node--type-landing-page node--view-mode-hero has-featur…">

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.
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.

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.

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
Ken Cook Is Having Another Episode div.field__items > div.field__item > a.linked-image > img.image-style-standard-xl
/sites/default/files/styles/standard_xl/public/2024-03/EW...65.6 KiB53.3 KiB
See which produce has the highest and lowest pesticide residues. By submitting… body.page-node--6657 > div#liteboxFormat22 > div#poptinDraggableContainer
/client_16f9efd0362a4/e2eb552d5cbf5710464d7ba1cd26b882.jpg278.1 KiB51.9 KiB
Solar panel installation div.field__items > div.field__item > a.linked-image > img.image-style-standard-sm
/sites/default/files/styles/standard_sm/public/2021-04/EW...44.7 KiB16.2 KiB
Mother applying sunscreen to child div.field__items > div.field__item > a.linked-image > img.image-style-standard-sm
/sites/default/files/styles/standard_sm/public/2023-05/Su...41.6 KiB15.1 KiB
Child holding blueberries div.field__items > div.field__item > a.linked-image > img.image-style-standard-sm
/sites/default/files/styles/standard_sm/public/2023-02/20...38.4 KiB13.9 KiB
Water with lemon div.field__items > div.field__item > a.linked-image > img.image-style-standard-sm
/sites/default/files/styles/standard_sm/public/2021-02/ch...36.4 KiB13.2 KiB
div.field__items > div.field__item > a.linked-image > img.image-style-standard-sm div.field__items > div.field__item > a.linked-image > img.image-style-standard-sm
/sites/default/files/styles/standard_sm/public/blog/Clean...36.1 KiB13.1 KiB
Woman putting on face cream div.field__items > div.field__item > a.linked-image > img.image-style-standard-sm
/sites/default/files/styles/standard_sm/public/2021-02/St...29.7 KiB10.8 KiB

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

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: 996 ms
URLTime Spent
ewg.org/996 ms
www.ewg.org/0.0 ms

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.

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.

URLTotal CPU TimeScript EvaluationScript Parse
cdnjs.cloudflare.com/ajax/libs/jquery/3.7.1/jquery.min.js1.9 s917 ms7.5 ms
Unattributable713 ms27 ms0.0 ms
www.ewg.org/632 ms32 ms5.0 ms
d3rse9xjbp8270.cloudfront.net/at.js498 ms400 ms78 ms
static.fundraiseup.com/checkout.9e2624d0be733d7f.js427 ms231 ms186 ms
cdn.fundraiseup.com/widget/AKWZXHJB351 ms194 ms22 ms
www.googletagmanager.com/gtag/js?id=G-C93205YZVJ&cx=c&gtm=4e64h1337 ms244 ms45 ms
www.googletagmanager.com/gtm.js?id=GTM-PPNMZJ324 ms274 ms42 ms
www.googletagmanager.com/gtag/js?id=G-CS21GC49KT&cx=c&gtm=4e64h1296 ms253 ms40 ms
www.googletagmanager.com/gtag/js?id=G-DQS34PDF9K&cx=c&gtm=4e64h1258 ms208 ms48 ms
www.ewg.org/cdn-cgi/challenge-platform/scripts/jsd/main.js240 ms228 ms2.2 ms
static.everyaction.com/ea-actiontag/at.js236 ms148 ms85 ms
scripts.clarity.ms/0.8.59/clarity.js223 ms197 ms6.4 ms
www.googletagmanager.com/gtag/destination?id=AW-1071783566&cx=c&gtm=4e64h1182 ms149 ms32 ms
www.googletagmanager.com/gtag/js?id=UA-296149-22178 ms141 ms35 ms
/sites/default/files/js/js_6Dk5y3dOlPZo2KLdCSjiYW-7-iEM4J...177 ms106 ms11 ms
static.fundraiseup.com/9483.5049a274cd651063.js170 ms154 ms0.8 ms
www.googletagmanager.com/gtag/destination?id=AW-698108002&cx=c&gtm=4e64h1162 ms128 ms33 ms
connect.facebook.net/en_US/fbevents.js123 ms89 ms33 ms
/signals/config/431673573640385?v=2.9.303&r=stable&domain...112 ms91 ms20 ms
static.fundraiseup.com/elements-langs-vendors.86315bee0669542d.js70 ms0.8 ms69 ms
cdn.popt.in/pixel.js?id=16f9efd0362a465 ms37 ms28 ms
/signals/config/367774270429261?v=2.9.303&r=stable&domain...60 ms48 ms9.7 ms
js.verygoodvault.com/vgs-collect/2.18.4/vgs-collect.js59 ms45 ms14 ms
www.google-analytics.com/analytics.js58 ms53 ms4.3 ms
static.fundraiseup.com/elementsApi.c0fc24ed4d35f527.js53 ms42 ms10 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.

CategoryTime Spent
Script Evaluation4.6 s
Script Parsing & Compilation990 ms
Other948 ms
Parse HTML & CSS817 ms
Style & Layout669 ms
Garbage Collection175 ms
Rendering150 ms

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

Layout shift culprits
Optimize DOM size
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 20 user timings
Avoid long main-thread tasks 20 long tasks found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 170 ms
Server Backend Latencies 220 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 430 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
Avoid non-composited animations
82

Accessibility

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

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Dialog popup start body.page-node--6657 > div#liteboxFormat22 > span.poptin-tabindex-start
Dialog popup end body.page-node--6657 > div#liteboxFormat22 > span.poptin-tabindex-end

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
APRIL 13, 2026 div.field > div.field__items > div.field__item > time.datetime
MARCH 24, 2026 div.field > div.field__items > div.field__item > time.datetime
MARCH 20, 2026 div.field > div.field__items > div.field__item > time.datetime
MARCH 19, 2026 div.field > div.field__items > div.field__item > time.datetime
GET MY FREE GUIDE div.froala-editor-button > p > span > span

These are opportunities to improve the legibility of your content.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
See which produce has the highest and lowest pesticide residues. div#liteboxFormat22 > div#poptinDraggableContainer > form#poptinFormSubmita709016f30cc6 > div.draggable
By submitting, you'll receive updates from EWG.  Unsubscribe any time or refer … div#liteboxFormat22 > div#poptinDraggableContainer > form#poptinFormSubmita709016f30cc6 > div.draggable
Continue to site div#liteboxFormat22 > div#poptinDraggableContainer > form#poptinFormSubmita709016f30cc6 > div#poptinFormCloseText
GET MY FREE GUIDE div#poptinDraggableContainer > form#poptinFormSubmita709016f30cc6 > div#poptinFormSubmitText > input#poptinFormSubmitButton
JUST RELEASED div#liteboxFormat22 > div#poptinDraggableContainer > form#poptinFormSubmita709016f30cc6 > div.draggable
2026 Dirty Dozen™  & Clean Fifteen™ div#liteboxFormat22 > div#poptinDraggableContainer > form#poptinFormSubmita709016f30cc6 > div.draggable
EMAIL* div.inputs-container > div.froala-editor-input > div#poptinDesignInputTextFieldEmail > input#poptinDesignInputTextFieldEmail
ZIP CODE* div.inputs-container > div.froala-editor-input > div#poptinDesignInputCustomField-CUSTOM_ZIPCODE > input#poptinDesignInputCustomField-CUSTOM_ZIPCODE
CELL (OPTIONAL) div.inputs-container > div.froala-editor-input > div#poptinDesignInputTextFieldPhone > input#poptinDesignInputTextFieldPhone
Dialog popup start body.page-node--6657 > div#liteboxFormat22 > span.poptin-tabindex-start
Dialog popup end body.page-node--6657 > div#liteboxFormat22 > span.poptin-tabindex-end

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Tap Water Database div#tns1-item0 > article.node > div.node__content > h3.node-title

These are opportunities to improve keyboard navigation in your application.

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.field__items > div.field__item > p > a.search-toggle div.field__items > div.field__item > p > a.search-toggle

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
Privacy Policy nav#block-system-menu-block-footer-utility-menu > ul.menu > li.menu-item > a
Legal Disclaimer nav#block-system-menu-block-footer-utility-menu > ul.menu > li.menu-item > a
Reprint Permission Information nav#block-system-menu-block-footer-utility-menu > ul.menu > li.menu-item > 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
Image elements have `[alt]` attributes
Input buttons have discernible text.
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
`[aria-hidden="true"]` elements do not contain focusable descendents
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
Document has a main landmark.
Deprecated ARIA roles were not used
ARIA IDs are unique
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
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 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
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 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.
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.
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.
77

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 / WarningSource
SharedStorage
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
Fledge
AttributionReporting

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
www.ewg.org/ line 1773, col 0
Access to XMLHttpRequest at 'https://secure.everyaction.com/v1/Forms/_jKOzsF3OE-CRm7cJ3j3Tw2' from origin 'https://www.ewg.org' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
www.ewg.org/ line 1775, col 0
Access to XMLHttpRequest at 'https://secure.everyaction.com/v1/Forms/_jKOzsF3OE-CRm7cJ3j3Tw2' from origin 'https://www.ewg.org' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
fetching error [object Object]
Uncaught NVTag was already initialized. The NVTag JS is likely included more than once on this page.
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 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
100

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Links have descriptive text
Links are crawlable
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback