Skip to content
https://astronomy.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.

37

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.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLEst Savings
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff245 ms
/s/opensans/v40/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu...45 ms
fonts.gstatic.com/s/firasans/v18/va9E4kDNxMZdWfMOD5Vvl4jLazX3dA.woff235 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:0.411 source:map[column:2245 line:1 type:source-location url:https://www.astronomy.com/wp-content/plugins/cdp-tracker/assets/js/tracker.min.js?ver=1.0.7 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:88.359 source:map[type:text value:[unattributed]]] map[reflowTime:17.544 source:map[column:25478 line:0 type:source-location url:https://cdn-cookieyes.com/client_data/8b2b503ea77987f25f16a19b/banner.js urlProvider:network]] map[reflowTime:3.402 source:map[column:26372 line:0 type:source-location url:https://cdn-cookieyes.com/client_data/8b2b503ea77987f25f16a19b/banner.js urlProvider:network]] map[reflowTime:0.411 source:map[column:8739 line:0 type:source-location url:https://www.astronomy.com/wp-content/plugins/cdp-tracker/assets/js/tracker.min.js?ver=1.0.7 urlProvider:network]] map[reflowTime:26.182 source:map[column:449 line:19 type:source-location url:/_/mss/boq-content-ads-contributor/_/js/k=boq-content-ads-contributor.ContributorServingResponseClientJs.en_US.pSJko196IH0.es5.O/d=1/exm=kernel_loader,loader_js_executable/ed=1/rs=AJlcJMwW9cECbTFkq4PRqOWQ0smSYbz1fw/m=web_iab_tcf_v2_wall_executable 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
div.wp-block-kb-pic-of-the-day > div.wp-block-kb-pic-of-the-day__img > a > img.attachment-large div.wp-block-kb-pic-of-the-day > div.wp-block-kb-pic-of-the-day__img > a > img.attachment-large
www.astronomy.com/wp-content/uploads/2026/04/Team-FACT-Sh-2-115.jpg9.4 MiB9.4 MiB
div.wp-block-kb-post-content-selector__grid > article#post-170281 > a.card-image > img.attachment-medium_large div.wp-block-kb-post-content-selector__grid > article#post-170281 > a.card-image > img.attachment-medium_large
www.astronomy.com/wp-content/uploads/2024/04/042323AuroraB.jpg1.3 MiB1.3 MiB
Astronomy Magazine div.footer-magazine > div.default-max-width > div.footer-magazine-inner > img.footer-magazine-image
www.astronomy.com/wp-content/uploads/2023/01/3-Issue-Image@2x.png624.3 KiB615.1 KiB
Radiant of the Lyrid meteor shower, April 22, 2026, 3 AM, looking east div.wp-block-kb-post-content-selector__grid > article#post-170178 > a.card-image > img.attachment-medium_large
www.astronomy.com/wp-content/uploads/2026/03/ASY-SM0426_05-768x747.png274.9 KiB253.0 KiB
div.wp-block-kb-post-content-selector__grid > article#post-116908 > a.card-image > img.attachment-medium_large div.wp-block-kb-post-content-selector__grid > article#post-116908 > a.card-image > img.attachment-medium_large
www.astronomy.com/wp-content/uploads/2023/03/ASYEP0621_09.jpg121.5 KiB106.5 KiB
div.wp-block-kb-post-content-selector__grid > article#post-170245 > a.card-image > img.attachment-medium_large div.wp-block-kb-post-content-selector__grid > article#post-170245 > a.card-image > img.attachment-medium_large
www.astronomy.com/wp-content/uploads/2026/04/ASY-GR1125_01-768x512.jpg80.0 KiB64.9 KiB
div.wp-block-kb-post-content-selector__grid > article#post-169974 > a.card-image > img.attachment-medium_large div.wp-block-kb-post-content-selector__grid > article#post-169974 > a.card-image > img.attachment-medium_large
/wp-content/uploads/2026/04/canadarm2-iss065e045231-768x5...41.5 KiB33.7 KiB
div.wp-block-kb-post-content-selector__grid > article#post-159858 > a.card-image > img.attachment-medium_large div.wp-block-kb-post-content-selector__grid > article#post-159858 > a.card-image > img.attachment-medium_large
www.astronomy.com/wp-content/uploads/2025/03/ASY-TF0425_19-768x511.jpg40.1 KiB30.7 KiB
div.wp-block-kb-post-content-selector__grid > article#post-170063 > a.card-image > img.attachment-medium_large div.wp-block-kb-post-content-selector__grid > article#post-170063 > a.card-image > img.attachment-medium_large
www.astronomy.com/wp-content/uploads/2026/04/nhq202604100018-768x563.webp20.0 KiB16.2 KiB

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.

URLTransfer SizeDuration
/css?family=Fira+Sans%3Aital%2Cwght%400%2C400%3B0%2C500%3...1.4 KiB843 ms
olytics.omeda.com/olytics/css/v3/p/olytics.css3.3 KiB755 ms
www.astronomy.com/wp-content/themes/astronomy/dist/style-frontend.css?ver=1.0.411.5 KiB302 ms
www.astronomy.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.130.9 KiB453 ms
/wp-content/plugins/gravityforms/assets/css/dist/theme-co...79 B
/wp-content/plugins/gravityforms/assets/css/dist/basic.mi...7.4 KiB151 ms
www.astronomy.com/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.15.0 KiB151 ms
/wp-content/plugins/gravityforms/assets/css/dist/theme.mi...7.0 KiB
/wp-content/themes/seedlet/assets/css/style-navigation.cs...2.2 KiB
www.astronomy.com/wp-content/themes/seedlet/style.css?ver=1.0.018.8 KiB
/wp-content/plugins/astronomy-core/dist/lib/css/glide.cor...379 B
www.astronomy.com/wp-content/plugins/fc-top-banner/style.css?ver=1.1.5857 B
/wp-content/plugins/sheknows-infuse/public/css/style.css?...299 B
/wp-content/plugins/astronomy-core/dist/blocks/post-conte...1.3 KiB
/wp-content/plugins/astronomy-core/dist/blocks/pic-of-the...314 B

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
ads.blogherads.com/static/chunks/5273.eec6f62e6c9beefc4be4.js14400.0 s132.2 KiB
olytics.omeda.com/olytics/js/v3/p/olytics.min.js21600.0 s70.9 KiB
ads.blogherads.com/static/chunks/3622.7d0e84ccad5146cd86e6.js14400.0 s50.4 KiB
ads.blogherads.com/static/chunks/831.b113b40433677910de75.js14400.0 s43.3 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
s.dpmsrv.com/dpm_1784f0e37c1fdd6200c1e8b28e8caae5402e74e0.min.js0.0 ms13.7 KiB
ads.blogherads.com/static/chunks/2030.b94af747cd5b3350d333.js14400.0 s19.8 KiB
static.chartbeat.com/js/chartbeat.js7200.0 s15.9 KiB
scripts.clarity.ms/0.8.59/clarity.js86400.0 s26.2 KiB
/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/...14400.0 s12.3 KiB
ads.blogherads.com/static/chunks/982.31e834f3c5c91bf8b371.js14400.0 s11.4 KiB
static.chartbeat.com/js/chartbeat_mab.js7200.0 s10.1 KiB
ads.blogherads.com/static/chunks/4857.910c4b46763f23e61854.js14400.0 s8.0 KiB
d81mfvml8p5ml.cloudfront.net/rftykj48.js600.0 s4.8 KiB
ads.blogherads.com/static/chunks/6559.074815d12fef9b41149e.js14400.0 s6.2 KiB
ads.blogherads.com/static/chunks/6317.7fde3be0f22be218a9d5.js14400.0 s4.8 KiB
ads.blogherads.com/static/blogherads.js14400.0 s4.4 KiB
olytics.omeda.com/olytics/css/v3/p/olytics.css21600.0 s3.3 KiB
ads.blogherads.com/sk/12/124/1242172/31478/header.js14400.0 s2.8 KiB
s.dpmsrv.com/blank.png0.0 ms1.0 KiB
cdn-cookieyes.com/assets/images/poweredbtcky.svg36000.0 s1.5 KiB
d1mkq4fbm7j30i.cloudfront.net/21/oHS-21.js0.0 ms843 B
cdn-cookieyes.com/assets/images/revisit.svg36000.0 s1.2 KiB
cdn-cookieyes.com/assets/images/close.svg36000.0 s796 B
dn1i8v75r669j.cloudfront.net/v/?w=rftykj48300.0 s446 B
www.gstatic.com/recaptcha/api2/logo_48.png604800.0 s2.3 KiB
insight.adsrvr.org/track/pxl/?adv=f6ba480&ct=0:s161583&fmt=30.0 ms149 B
insight.adsrvr.org/track/pxl/?adv=f6ba480&ct=0:0qwxs84&fmt=30.0 ms148 B

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: 927 ms
URLTime Spent
astronomy.com/927 ms
www.astronomy.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 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: 150 ms 588.5 KiB
URLTransfer SizeEst Savings
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js361.8 KiB177.0 KiB
ads.blogherads.com/static/chunks/5273.eec6f62e6c9beefc4be4.js132.0 KiB103.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-WHWV7HZ143.8 KiB69.1 KiB
www.googletagmanager.com/gtag/js?id=G-2R82D8QZG9&cx=c&gtm=4e64k1154.7 KiB63.2 KiB
olytics.omeda.com/olytics/js/v3/p/olytics.min.js70.4 KiB46.2 KiB
ads.blogherads.com/static/chunks/3622.7d0e84ccad5146cd86e6.js50.1 KiB41.2 KiB
ads.blogherads.com/static/chunks/831.b113b40433677910de75.js43.0 KiB34.9 KiB
fundingchoicesmessages.google.com/i/pub-9489621755605348?ers=168.7 KiB33.1 KiB
www.astronomy.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.130.8 KiB20.4 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.astronomy.com/1.3 s132 ms18 ms
Unattributable1.0 s30 ms0.0 ms
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js826 ms695 ms79 ms
/f/AGSKWxWBrsUvPaeJKYDYj87YqkmJqw6QeseMOLQIlLAEx3dHba--Mq...456 ms225 ms60 ms
s.dpmsrv.com/dpm_1784f0e37c1fdd6200c1e8b28e8caae5402e74e0.min.js331 ms195 ms4.8 ms
www.astronomy.com/cdn-cgi/challenge-platform/scripts/jsd/main.js306 ms282 ms3.0 ms
cdn-cookieyes.com/client_data/8b2b503ea77987f25f16a19b/banner.js295 ms191 ms2.4 ms
ads.blogherads.com/static/chunks/5273.eec6f62e6c9beefc4be4.js284 ms256 ms22 ms
fundingchoicesmessages.google.com/i/pub-9489621755605348?ers=1280 ms252 ms24 ms
scripts.clarity.ms/0.8.59/clarity.js204 ms186 ms7.3 ms
www.googletagmanager.com/gtm.js?id=GTM-WHWV7HZ204 ms168 ms30 ms
olytics.omeda.com/olytics/js/v3/p/olytics.min.js191 ms143 ms32 ms
www.googletagmanager.com/gtag/js?id=G-2R82D8QZG9&cx=c&gtm=4e64k1183 ms142 ms40 ms
www.astronomy.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1124 ms76 ms10 ms
www.google-analytics.com/analytics.js116 ms105 ms5.7 ms
dkpklk99llpj0.cloudfront.net/rftykj48_1696962623165.js104 ms91 ms8.1 ms
static.chartbeat.com/js/chartbeat.js90 ms83 ms2.8 ms
www.astronomy.com/wp-content/themes/astronomy/dist/frontend.js?ver=1.0.481 ms38 ms1.1 ms
static.chartbeat.com/js/chartbeat_mab.js51 ms44 ms2.8 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.3 s
Other1.2 s
Style & Layout1.1 s
Script Parsing & Compilation448 ms
Parse HTML & CSS235 ms
Garbage Collection166 ms
Rendering106 ms

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 6.1 KiB
URLTransfer SizeEst Savings
/* ============================================================ Astronomy.com Additional CSS — v5…11.7 KiB3.3 KiB
www.astronomy.com/wp-content/themes/seedlet/style.css?ver=1.0.018.8 KiB2.8 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: 0.0 ms 28.6 KiB
URLTransfer SizeEst Savings
www.astronomy.com/wp-content/themes/seedlet/style.css?ver=1.0.018.7 KiB14.7 KiB
.fc-consent-root .fc-dialog-container.fc-fullscreen { height: 100% !important; … } …16.2 KiB14.0 KiB

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.

URLTransfer Size
www.astronomy.com/wp-content/uploads/2026/04/Team-FACT-Sh-2-115.jpg9.4 MiB
www.astronomy.com/wp-content/uploads/2024/04/042323AuroraB.jpg1.3 MiB
www.astronomy.com/wp-content/uploads/2023/01/3-Issue-Image@2x.png624.8 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js362.4 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js361.9 KiB
www.astronomy.com/wp-content/uploads/2026/03/ASY-SM0426_05-768x747.png275.2 KiB
www.googletagmanager.com/gtag/js?id=G-2R82D8QZG9&cx=c&gtm=4e64k1154.8 KiB
www.googletagmanager.com/gtm.js?id=GTM-WHWV7HZ144.2 KiB
ads.blogherads.com/static/chunks/5273.eec6f62e6c9beefc4be4.js132.2 KiB
www.astronomy.com/wp-content/uploads/2023/03/ASYEP0621_09.jpg121.8 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
Publisher logo div.default-max-width > div.subfooter-inner > div.publisher-info > img
www.astronomy.com/wp-content/uploads/2023/01/cropped-Logo-white@2x.png

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
●LCP request discovery
●Modern HTTP
●Optimize viewport for mobile
●Minify JavaScript
●User Timing marks and measures 7 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 170 ms
●Server Backend Latencies 470 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 210 ms
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○Avoid non-composited animations
94

Accessibility

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

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Learn more div.fc-dialog-content > div.fc-dialog-scrollable-content > button.fc-faq-header > span.fc-faq-label
List of partners. div.fc-dialog-scrollable-content > div.fc-footer > p > a.fc-vendors-list-dialog
Manage options div.fc-dialog > div.fc-footer-buttons-container > button.fc-button > p.fc-manage-options-third-button-label

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.wp-block-group > div.wp-block-kb-pic-of-the-day > div.wp-block-kb-pic-of-the-day__img > a div.wp-block-group > div.wp-block-kb-pic-of-the-day > div.wp-block-kb-pic-of-the-day__img > a
ul.glide__slides > li.wp-block-post-carousel__slide > article.agency-ui-card > a.card-image ul.glide__slides > li.wp-block-post-carousel__slide > article.agency-ui-card > a.card-image
li.wp-block-post-carousel__slide > article.agency-ui-card > h3.card-title > a li.wp-block-post-carousel__slide > article.agency-ui-card > h3.card-title > 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.

○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.
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●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.
●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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●Uses ARIA roles only on compatible elements
●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
○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 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>`.
○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
www.astronomy.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
www.astronomy.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge
www.astronomy.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
Topics
ads.blogherads.com/static/chunks/3622.7d0e84ccad5146cd86e6.js line 1, col 55741

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
/rftykj48/campaigns/?k=27mgga7&d=9e1oymyegt&url=https%3A%...
Failed to load resource: the server responded with a status of 401 ()
●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
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
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