Skip to content
https://masslive.com

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.

30

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
s.ntv.io/serve/load.js3600.0 s251.1 KiB
cdn.tinypass.com/api/tinypass.min.js14400.0 s132.6 KiB
c.amazon-adsystem.com/aax2/apstag.js3600.0 s90.8 KiB
news.google.com/swg/js/v1/swg.js3000.0 s71.5 KiB
/pagead/managed/js/activeview/current/ufs_web_display.js3600.0 s73.1 KiB
sdk.mrf.io/statics/marfeel-sdk.js?id=65301800.0 s58.9 KiB
privacy.advancelocal.com/fides.js?3600.0 s51.3 KiB
cdn.sophi.io/assets/demeter/1/stable/766914176.js?isConsented=true900.0 s37.8 KiB
js.matheranalytics.com/static/ltm/ma63527/all/20/ml.br.js3600.0 s41.4 KiB
js.datadome.co/tags.js3600.0 s39.4 KiB
cdn.cxense.com/cx.js3600.0 s38.1 KiB
cdn.id5-sync.com/api/1.0/id5-api.js3600.0 s34.5 KiB
sdk.mrf.io/statics/47bd3e88b6bda15c34ce.js3600.0 s24.4 KiB
secure.cdn.fastclick.net/js/pubcid/latest/pubcid.min.js900.0 s21.7 KiB
d-code.liadm.com/did-00ab.min.js86400.0 s45.9 KiB
tags.crwdcntrl.net/lt/c/962/lt.min.js86400.0 s19.9 KiB
s.go-mpulse.net/boomerang/S69BL-NPKS2-VLL9S-WR9DU-DJ4K7604800.0 s56.9 KiB
cdn.cxense.com/cx.cce.js3600.0 s6.8 KiB
tags.crwdcntrl.net/lt/c/16576/sync.min.js86400.0 s13.4 KiB
news.google.com/swg/js/v1/swg-button.css3000.0 s5.2 KiB
sdk.mrf.io/statics/compass-multimedia-sdk.js?version=22623600.0 s4.3 KiB
sb.scorecardresearch.com/internal-cs/default/beacon-and.js86400.0 s7.8 KiB
analytics.ahrefs.com/analytics.js14400.0 s3.0 KiB
config.aps.amazon-adsystem.com/configs/31783600.0 s2.1 KiB
pagead2.googlesyndication.com/pagead/js/r20260421/r20110914/abg_lite_fy2021.js1209600.0 s8.4 KiB
ead.masslive.com/baker?dtstmp=17768918504470.0 ms540 B
experience.tinypass.com/xbuilder/experience/load?aid=C8WJ5qarpu1800.0 s602 B
/i?e=pv&page=Massachusetts%20Local%20News%2C%20Breaking%2...0.0 ms245 B
/track/usersync?us_privacy=&gdpr=0&gdpr_consent=undefined...0.0 ms149 B
/pagead/js/r20260421/r20110914/client/window_focus_fy2021.js1209600.0 s1.2 KiB
cdn.indexww.com/ht/htw-pixel.gif?086400.0 s223 B
/tr?id=120978121945017&ev=ViewContent&cd[article_content_...0.0 ms19 B
/tr?id=158988308834612&ev=ViewContent&cd[article_content_...0.0 ms16 B
/tr?id=120978121945017&ev=PageView&dl=https%3A%2F%2Fwww.m...0.0 ms16 B
/tr?id=158988308834612&ev=PageView&dl=https%3A%2F%2Fwww.m...0.0 ms16 B
/pagead/managed/js/activeview/current/ufs_web_display.js3600.0 s0 B
pagead2.googlesyndication.com/pagead/js/r20260421/r20110914/abg_lite_fy2021.js1209600.0 s0 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:36.712 source:map[type:text value:[unattributed]]]]

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
body.jar > div#google_image_div > a#aw0 > img.img_ad body.jar > div#google_image_div > a#aw0 > img.img_ad
tpc.googlesyndication.com/simgad/1586366564614468888052.3 KiB40.1 KiB
WMass ‘mid-century glass octagon’ among 'most wishlisted’ Airbnb listings a > div.article-picture--inner > div.article__picture > img.article__picture--img
/resizer/v2/6D6NDAD5PFFLHIGHQVWRF62OAE.jpeg?auth=4c723572...59.3 KiB15.4 KiB
Sabres coach suggests a big move is possible for Game 3 vs. Bruins a > div.article-picture--inner > div.article__picture > img.article__picture--img
/resizer/v2/I3CZERT2URGPBGRV5NS2RIVNPE.jpg?auth=52a78c3d6...54.3 KiB10.4 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: 781 ms
URLTime Spent
masslive.com/781 ms
www.masslive.com/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.

Estimated savings: 450 ms 89.0 KiB
URLTransfer SizeEst Savings
/pf/dist/components/combinations/default.css?d=1788&mxId=...92.4 KiB89.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.

Estimated savings: 4.1 s 1.7 MiB
URLTransfer SizeEst Savings
www.masslive.com/pf/dist/components/combinations/default.js?d=1788&mxId=00000000899.1 KiB736.5 KiB
s.ntv.io/serve/load.js250.4 KiB190.4 KiB
/pagead/managed/js/gpt/m202604170101/pubads_impl.js?cb=31...187.4 KiB96.2 KiB
cdn.tinypass.com/api/tinypass.min.js132.1 KiB82.5 KiB
www.googletagmanager.com/gtm.js?id=GTM-MZKDL44188.4 KiB68.7 KiB
www.googletagmanager.com/gtag/js?id=G-E42D2H0KT5&cx=c&gtm=4e64k0153.6 KiB63.7 KiB
news.google.com/swg/js/v1/swg.js68.9 KiB48.4 KiB
micro.rubiconproject.com/prebid/dynamic/10071.js173.6 KiB47.0 KiB
news.google.com/swg/js/v1/swg.js68.9 KiB46.5 KiB
c541.masslive.com/plugin/library/ec59bd4f95fa151d37d3a5458cf0564769.2 KiB43.6 KiB
c.amazon-adsystem.com/aax2/apstag.js90.4 KiB38.0 KiB
s.go-mpulse.net/boomerang/S69BL-NPKS2-VLL9S-WR9DU-DJ4K756.7 KiB37.1 KiB
www.masslive.com/pf/dist/engine/react.js?d=1788&mxId=00000000130.1 KiB36.8 KiB
/pagead/managed/js/activeview/current/ufs_web_display.js73.1 KiB31.7 KiB
/pagead/managed/js/activeview/current/ufs_web_display.js73.1 KiB30.9 KiB
/pf/dist/components/combinations/98.chunk.js?d=1788&mxId=...40.5 KiB25.8 KiB
sdk.mrf.io/statics/marfeel-sdk.js?id=653058.6 KiB24.7 KiB
cdn.cxense.com/cx.js37.5 KiB23.7 KiB
/ats-modules/f4105e35-d596-4694-b9a4-ed81ae9873a1/ats.js38.6 KiB23.3 KiB
privacy.advancelocal.com/fides.js?50.9 KiB22.4 KiB
sdk.mrf.io/statics/47bd3e88b6bda15c34ce.js23.9 KiB22.1 KiB
plugins.blueconic.net/static/scripts/jquery/jquery-3.7.1-BC-v2.min.js29.7 KiB22.1 KiB
acustomizedgift.com/public/ritg0nizf_gfl.index.js36.3 KiB20.1 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.

URLTotal CPU TimeScript EvaluationScript Parse
www.masslive.com/pf/dist/components/combinations/default.js?d=1788&mxId=000000001.9 s751 ms365 ms
www.masslive.com/pf/dist/engine/react.js?d=1788&mxId=000000001.5 s1.2 s44 ms
Unattributable1.4 s412 ms0.0 ms
/pagead/managed/js/gpt/m202604170101/pubads_impl.js?cb=31...988 ms835 ms106 ms
www.masslive.com/885 ms67 ms66 ms
www.googletagmanager.com/gtm.js?id=GTM-MZKDL44821 ms730 ms74 ms
c541.masslive.com/script.js745 ms667 ms20 ms
/pf/dist/components/combinations/99.chunk.js?d=1788&mxId=...708 ms667 ms11 ms
privacy.advancelocal.com/fides.js?525 ms454 ms20 ms
js.datadome.co/tags.js490 ms454 ms10.0 ms
sdk.mrf.io/statics/marfeel-sdk.js?id=6530401 ms379 ms1.2 ms
micro.rubiconproject.com/prebid/dynamic/10071.js369 ms325 ms40 ms
s.ntv.io/serve/load.js362 ms271 ms83 ms
/pagead/managed/js/activeview/current/ufs_web_display.js291 ms266 ms18 ms
cdn.tinypass.com/api/tinypass.min.js290 ms208 ms49 ms
www.googletagmanager.com/gtag/js?id=G-E42D2H0KT5&cx=c&gtm=4e64k0259 ms214 ms43 ms
c.amazon-adsystem.com/aax2/apstag.js178 ms136 ms34 ms
cdn.sophi.io/assets/demeter/1/stable/766914176.js?isConsented=true161 ms144 ms17 ms
js.matheranalytics.com/s/ma63527/484602604/all/ml.js?cb=1714129 ms114 ms12 ms
d-code.liadm.com/did-00ab.min.js122 ms99 ms14 ms
news.google.com/swg/js/v1/swg.js108 ms43 ms63 ms
cdn.cxense.com/cx.js96 ms81 ms13 ms
cdn.parsely.com/keys/masslive.com/p.js89 ms79 ms4.7 ms
advancelocal.blueconic.net/DG/DEFAULT/cs?&callback=bc_json86285 ms55 ms0.2 ms
/t?ntv_mvi=&ntv_url=https%253A%252F%252Fwww.masslive.com%...77 ms72 ms1.3 ms
securepubads.g.doubleclick.net/tag/js/gpt.js75 ms62 ms13 ms
acustomizedgift.com/public/ritg0nizf_gfl.index.js71 ms59 ms10 ms
s.go-mpulse.net/boomerang/S69BL-NPKS2-VLL9S-WR9DU-DJ4K768 ms43 ms21 ms
/ats-modules/f4105e35-d596-4694-b9a4-ed81ae9873a1/ats.js63 ms48 ms14 ms
secure.cdn.fastclick.net/js/pubcid/latest/pubcid.min.js59 ms53 ms5.2 ms
cdn.id5-sync.com/api/1.0/id5-api.js54 ms34 ms12 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 Evaluation9.3 s
Other2.0 s
Script Parsing & Compilation1.3 s
Style & Layout697 ms
Rendering209 ms
Garbage Collection153 ms
Parse HTML & CSS131 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
The page has an unload handler in the main frame.Actionable

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

Layout shift culprits
Optimize DOM size
Font display
LCP breakdown
LCP request discovery
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 14 user timings
Avoid long main-thread tasks 20 long tasks found
Image elements have explicit `width` and `height`
Network Requests
Network Round Trip Times 100 ms
Server Backend Latencies 780 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 590 ms
Avoid large layout shifts 4 layout shifts found
INP breakdown
Avoid non-composited animations
97

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
Advertisement div.page-type__home-beta > div#footer > div.revenue__full-break-2--no-small-view > div#InFeed_Center_Wide_Adhesion_1

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.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<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
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
`[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.
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
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
ARIA IDs are unique
No form fields have multiple labels
`<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
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.
`<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
Unload event listeners are deprecated and will be removed.
Topics
js.datadome.co/tags.js line 1, col 32233

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
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 451 ()
NotFoundError: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node. at Rl (https://www.masslive.com/pf/dist/engine/react.js?d=1788&mxId=00000000:2:156430) at Ul (https://www.masslive.com/pf/dist/engine/react.js?d=1788&mxId=00000000:2:157958) at Jl (https://www.masslive.com/pf/dist/engine/react.js?d=1788&mxId=00000000:2:158206) at Ul (https://www.masslive.com/pf/dist/engine/react.js?d=1788&mxId=00000000:2:158084) at Jl (https://www.masslive.com/pf/dist/engine/react.js?d=1788&mxId=00000000:2:158282) at Ul (https://www.masslive.com/pf/dist/engine/react.js?d=1788&mxId=00000000:2:158084) at Jl (https://www.masslive.com/pf/dist/engine/react.js?d=1788&mxId=00000000:2:161018) at Ul (https://www.masslive.com/pf/dist/engine/react.js?d=1788&mxId=00000000:2:158084) at Jl (https://www.masslive.com/pf/dist/engine/react.js?d=1788&mxId=00000000:2:161018) at Ul (https://www.masslive.com/pf/dist/engine/react.js?d=1788&mxId=00000000:2:158084)
NotFoundError: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node. at Rl (https://www.masslive.com/pf/dist/engine/react.js?d=1788&mxId=00000000:2:156430) at Ul (https://www.masslive.com/pf/dist/engine/react.js?d=1788&mxId=00000000:2:157958) at Jl (https://www.masslive.com/pf/dist/engine/react.js?d=1788&mxId=00000000:2:158206) at Ul (https://www.masslive.com/pf/dist/engine/react.js?d=1788&mxId=00000000:2:158084) at Jl (https://www.masslive.com/pf/dist/engine/react.js?d=1788&mxId=00000000:2:158282) at Ul (https://www.masslive.com/pf/dist/engine/react.js?d=1788&mxId=00000000:2:158084) at Jl (https://www.masslive.com/pf/dist/engine/react.js?d=1788&mxId=00000000:2:161018) at Ul (https://www.masslive.com/pf/dist/engine/react.js?d=1788&mxId=00000000:2:158084) at Jl (https://www.masslive.com/pf/dist/engine/react.js?d=1788&mxId=00000000:2:161018) at Ul (https://www.masslive.com/pf/dist/engine/react.js?d=1788&mxId=00000000:2:158084) [object Object]
SyntaxError: Unexpected token 'a', "adv-OFMQS5"... is not valid JSON
Uncaught (in promise) No config could be discovered in the page

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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 clickjacking with XFO or CSP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Redirects HTTP traffic to HTTPS
92

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.module > div.empty-module > div.article__details-headline > a.article__details-headline-text div.module > div.empty-module > div.article__details-headline > a.article__details-headline-text
div.module > div.empty-module > div.article__details-headline > a.article__details-headline-text div.module > div.empty-module > div.article__details-headline > a.article__details-headline-text

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`

Send Feedback