Skip to content
Audit Complete

Results for https://www.substack.com

Visit site
Spain Spain · Madrid Completed: Apr 7, 2026 20:20 UTC
Share card preview
Share on X Share on LinkedIn Share on Reddit Share on Hacker News Share via Email Download share image
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C72

Site Health

Score: 72 / 100

Based on 8 categories, 0 sections

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

Top Priorities (5)

1

Content-Security-Policy header is missing

Security › Security Headers
2

Cookie 'AWSALBTG' is missing the Secure flag

Security › Cookie Security
3

No Content-Security-Policy header found

Security › Content Security Policy
4

Page weighs 10.1 MB (4.5 MB transferred)

Performance › Page Weight Budget
5

1 button(s) with no accessible text

Accessibility › Link & Button Quality
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.substack.com)](https://beavercheck.com/results/f4e59440-a3d6-34e1-9919-03864b5f5e9f)
<a href="https://beavercheck.com/results/f4e59440-a3d6-34e1-9919-03864b5f5e9f"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.substack.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwww.substack.com

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

55
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
70
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
77
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

14.14 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

25.33 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

48 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

14.14 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

25.37 s

Detailed Report

Audit breakdown by category with detailed findings.

55

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

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

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

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

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.

URLEst Savings
substackcdn.com/fonts/Cahuenga-SemiBold.woff2185 ms

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

URLResource SizeEst Savings
The app for independent voices Get the app Learn more div.pencraft > div.pencraft > div.pencraft > div.pencraft
substackcdn.com/img/growth_page/footer.jpeg1.7 MiB183.1 KiB
a.pencraft > div.pencraft > picture > img.img-OACg1c a.pencraft > div.pencraft > picture > img.img-OACg1c
/image/fetch/$s_!Cez8!,w_1040,h_545,c_fill,f_webp,q_auto:...95.6 KiB86.2 KiB
div.pencraft > div.pencraft > picture > img.img-OACg1c div.pencraft > div.pencraft > picture > img.img-OACg1c
/image/fetch/$s_!fgyZ!,w_630,c_limit,f_webp,q_auto:good,f...78.6 KiB58.0 KiB
div.pencraft > div.pencraft > picture > img.img-OACg1c div.pencraft > div.pencraft > picture > img.img-OACg1c
/image/fetch/$s_!uaD6!,w_630,c_limit,f_webp,q_auto:good,f...54.0 KiB39.8 KiB
div.pencraft > div.pencraft > picture > img.img-OACg1c div.pencraft > div.pencraft > picture > img.img-OACg1c
/image/fetch/$s_!iJMe!,w_396,c_limit,f_webp,q_auto:good,f...34.8 KiB33.1 KiB

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

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:308.69 label:Time to first byte subpart:timeToFirstByte] map[duration:2174.831 label:Resource load delay subpart:resourceLoadDelay] map[duration:44.185 label:Resource load duration subpart:resourceLoadDuration] map[duration:38.726 label:Element render delay subpart:elementRenderDelay]]
lhId: page-3-IMG
nodeLabel: div.pencraft > div.pencraft > picture > img.img-OACg1c
path: 1,HTML,1,BODY,1,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,2,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,1,DIV,0,DIV,0,PICTURE,1,IMG
selector: div.pencraft > div.pencraft > picture > img.img-OACg1c
snippet: <img src="https://substackcdn.com/image/fetch/$s_!uaD6!,w_630,c_limit,f_webp,q_auto:…" sizes="315px" alt="" srcset="https://substackcdn.com/image/fetch/$s_!uaD6!,w_315,c_limit,f_auto,q_auto:…" width="315" height="auto" loading="lazy" draggable="false" class="img-OACg1c pencraft pc-reset">

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

lhId: page-3-IMG
nodeLabel: div.pencraft > div.pencraft > picture > img.img-OACg1c
path: 1,HTML,1,BODY,1,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,2,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,1,DIV,0,DIV,0,PICTURE,1,IMG
selector: div.pencraft > div.pencraft > picture > img.img-OACg1c
snippet: <img src="https://substackcdn.com/image/fetch/$s_!uaD6!,w_630,c_limit,f_webp,q_auto:…" sizes="315px" alt="" srcset="https://substackcdn.com/image/fetch/$s_!uaD6!,w_315,c_limit,f_auto,q_auto:…" width="315" height="auto" loading="lazy" draggable="false" class="img-OACg1c pencraft pc-reset">

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.

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

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

RequestCache TTLTransfer Size
substack.com/cdn-cgi/challenge-platform/h/b/scripts/jsd/625261456364/main.js?14400.0 s12.6 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.

TTI

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Estimated savings: 896 ms
URLTime Spent
www.substack.com/896 ms
substack.com/0.0 ms

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.

Estimated savings: 540 ms 57.5 KiB
URLTransfer SizeEst Savings
substackcdn.com/bundle/static/css/77496.13fa4a14.css32.8 KiB32.8 KiB
substackcdn.com/bundle/static/css/reader2.0991e6aa.css25.2 KiB24.7 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.

Estimated savings: 5.1 s 982.0 KiB
URLTransfer SizeEst Savings
substackcdn.com/bundle/static/js/reader2.dd4aee9b.js619.2 KiB348.5 KiB
substackcdn.com/bundle/static/js/51606.9e5d2f4f.js301.3 KiB236.2 KiB
substackcdn.com/bundle/static/js/async/50551.9f31dfda.js95.0 KiB81.7 KiB
substackcdn.com/bundle/static/js/77496.a030b7b6.js81.4 KiB60.9 KiB
substackcdn.com/bundle/static/js/96869.cf1a6316.js37.7 KiB37.6 KiB
substackcdn.com/bundle/static/js/30440.3a078123.js44.3 KiB35.4 KiB
substackcdn.com/bundle/static/js/96924.6b3177b3.js43.7 KiB32.8 KiB
substackcdn.com/bundle/static/js/97993.36609a05.js27.7 KiB27.5 KiB
substackcdn.com/bundle/static/js/62744.d65af920.js35.0 KiB27.0 KiB
substackcdn.com/bundle/static/js/lib-router.faae56b7.js25.4 KiB24.3 KiB
substackcdn.com/bundle/static/js/28407.85861033.js27.0 KiB23.9 KiB
substackcdn.com/bundle/static/js/61861.fd526f64.js34.2 KiB23.5 KiB
substackcdn.com/bundle/static/js/45337.6965623b.js28.2 KiB22.9 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.

URLTotal CPU TimeScript EvaluationScript Parse
substackcdn.com/bundle/static/js/77496.a030b7b6.js2.1 s2.0 s1.0 ms
Unattributable1.2 s31 ms0.0 ms
substack.com/cdn-cgi/challenge-platform/scripts/jsd/main.js257 ms247 ms2.3 ms
substack.com/254 ms39 ms6.1 ms
substackcdn.com/bundle/static/js/async/50551.9f31dfda.js221 ms109 ms30 ms
substackcdn.com/bundle/static/js/reader2.dd4aee9b.js75 ms3.8 ms5.7 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

CategoryTime Spent
Script Evaluation2.5 s
Other1.3 s
Style & Layout272 ms
Script Parsing & Compilation93 ms
Parse HTML & CSS73 ms
Garbage Collection67 ms
Rendering34 ms

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

URLTransfer Size
substackcdn.com/img/growth_page/footer.jpeg1.7 MiB
substackcdn.com/bundle/static/js/reader2.dd4aee9b.js621.0 KiB
substackcdn.com/bundle/static/js/51606.9e5d2f4f.js306.2 KiB
/image/fetch/$s_!Cez8!,w_1040,h_545,c_fill,f_webp,q_auto:...96.1 KiB
substackcdn.com/bundle/static/js/async/50551.9f31dfda.js95.4 KiB
substackcdn.com/bundle/static/js/77496.a030b7b6.js81.9 KiB
/image/fetch/$s_!fgyZ!,w_630,c_limit,f_webp,q_auto:good,f...79.1 KiB
substackcdn.com/fonts/Cahuenga-SemiBold.woff269.5 KiB
substackcdn.com/bundle/static/js/92520.bf6ac17b.js59.4 KiB
/image/fetch/$s_!uaD6!,w_630,c_limit,f_webp,q_auto:good,f...54.4 KiB

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

URL
div.pencraft > div.pencraft > picture > img.img-OACg1c div.pencraft > div.pencraft > picture > img.img-OACg1c
/image/fetch/$s_!iJMe!,w_396,c_limit,f_webp,q_auto:good,f...
div.pencraft > div.pencraft > picture > img.img-OACg1c div.pencraft > div.pencraft > picture > img.img-OACg1c
/image/fetch/$s_!DzDi!,w_244,c_limit,f_webp,q_auto:good,f...

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

●Max Potential First Input Delay 90 ms
●Layout shift culprits
●Optimize DOM size
●Forced reflow
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoid long main-thread tasks 8 long tasks found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 30 ms
●Server Backend Latencies 170 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 140 ms
○INP breakdown
○User Timing marks and measures
○Avoid non-composited animations
○Avoid large layout shifts
70

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

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Failing Elements
div.reader-nav-root > div.pencraft > div.pencraft > a.pencraft div.reader-nav-root > div.pencraft > div.pencraft > a.pencraft
div.reader-nav-root > div.pencraft > div.pencraft > a.pencraft div.reader-nav-root > div.pencraft > div.pencraft > a.pencraft
div.reader-nav-root > div.pencraft > div.pencraft > a.pencraft div.reader-nav-root > div.pencraft > div.pencraft > a.pencraft

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Failing Elements
div#entry > div.reader-nav-root > div.app-banner > button.reader2-button-reset div#entry > div.reader-nav-root > div.app-banner > button.reader2-button-reset

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.

Failing Elements
div.pencraft > div.pencraft > div.pencraft > a.pencraft div.pencraft > div.pencraft > div.pencraft > a.pencraft

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.

Contrast

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

Failing Elements
Get the app div.pencraft > div.pencraft > div.pencraft > button.pencraft
Get the app div.pencraft > div.pencraft > div.pencraft > button.pencraft
For you div.pencraft > div.pencraft > div.pencraft > button.pencraft
Mar 27 div.pencraft > span.pencraft > a.pencraft > span.pencraft
Subscribe div.pencraft > div.pencraft > div.pencraft > button.pencraft
Mar 29 div.pencraft > span.pencraft > a.pencraft > span.pencraft
Subscribe div.pencraft > div.pencraft > div.pencraft > button.pencraft
4h div.pencraft > span.pencraft > a.pencraft > span.pencraft
Subscribe div.pencraft > div.pencraft > div.pencraft > button.pencraft
You always own your intellectual property, mailing list, and subscriber payment… div.pencraft > div.pencraft > div.pencraft > p.pencraft
Get started div.pencraft > div.pencraft > div.pencraft > button.pencraft
3h div.pencraft > span.pencraft > a.pencraft > span.pencraft
Subscribe div.pencraft > div.pencraft > div.pencraft > button.pencraft
3h div.pencraft > span.pencraft > a.pencraft > span.pencraft
Subscribe div.pencraft > div.pencraft > div.pencraft > button.pencraft
bookshop.org/p/books/dr… div.pencraft > div.ProseMirror > p > a.pencraft
Mar 12 span.pencraft > span.pencraft > a.pencraft > span.pencraft
Join the most interesting and insightful discussions. div.pencraft > div.pencraft > div.pencraft > p.pencraft
Get started div.pencraft > div.pencraft > div.pencraft > button.pencraft
1h div.pencraft > span.pencraft > a.pencraft > span.pencraft
Subscribe div.pencraft > div.pencraft > div.pencraft > button.pencraft
5calls.org div.pencraft > a.pencraft > div.pencraft > p.pencraft
Spend 5 minutes. Make 5 calls. Make your voice heard. div.pencraft > a.pencraft > div.pencraft > p.pencraft
Get app div.reader-nav-root > div.app-banner > a.app-banner-cta > div.pencraft
privacy policy div.pencraft > div.pencraft > div.pencraft > a.pencraft

These are opportunities to improve the legibility of your content.

Navigation

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.

Failing Elements
The app for independent voices div.pencraft > div.pencraft > div.pencraft > h4.pencraft

These are opportunities to improve keyboard navigation in your application.

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.

Failing Elements
head > meta head > meta

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.

Failing Elements
Hayley DeRoche's avatar div.pencraft > a.pencraft > div.pencraft > a.pencraft
Hayley DeRoche div.pencraft > span > span.pencraft > a.pencraft
Mar 12 div.pencraft > span.pencraft > span.pencraft > a.pencraft

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Failing Elements
html html

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Failing Elements
22.2K div.pencraft > div.pencraft > div.pencraft > button.pencraft
1.2K div.pencraft > div.pencraft > div.pencraft > button.pencraft
565 div.pencraft > div.pencraft > div.pencraft > button.pencraft
6.5K div.pencraft > div.pencraft > div.pencraft > button.pencraft
59 div.pencraft > div.pencraft > div.pencraft > button.pencraft
1K div.pencraft > div.pencraft > div.pencraft > button.pencraft
129 div.pencraft > div.pencraft > div.pencraft > button.pencraft
6 div.pencraft > div.pencraft > div.pencraft > button.pencraft
1.3K div.pencraft > div.pencraft > div.pencraft > button.pencraft
156 div.pencraft > div.pencraft > div.pencraft > button.pencraft
341 div.pencraft > div.pencraft > div.pencraft > button.pencraft
20 div.pencraft > div.pencraft > div.pencraft > button.pencraft
1 div.pencraft > div.pencraft > div.pencraft > button.pencraft
27 div.pencraft > div.pencraft > div.pencraft > button.pencraft
3 div.pencraft > div.pencraft > div.pencraft > button.pencraft
7 div.pencraft > div.pencraft > div.pencraft > button.pencraft
○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
●Image elements have `[alt]` attributes
●ARIA attributes are used as specified for the element's role
●Elements use only permitted ARIA attributes
●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>`).
●No element has a `[tabindex]` value greater than 0
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○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.

Deprecation / WarningSource
SharedStorage
substack.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
substack.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge
substack.com/cdn-cgi/challenge-platform/scripts/jsd/main.js

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

SourceDescription
substack.com/api/v1/messages/unread-count
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
●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
○Use a strong HSTS policy
○Mitigate clickjacking with XFO or CSP
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

Uncrawlable Link
3h div.pencraft > div.pencraft > span.pencraft > a.pencraft

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`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

47
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
75
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
77
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
85
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.59 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

5.32 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

477 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

2.04 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

5.32 s

Detailed Report

Audit breakdown by category with detailed findings.

47

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

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

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

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

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.

URLEst Savings
substackcdn.com/fonts/Cahuenga-SemiBold.woff2315 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.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:31.298 source:map[type:text value:[unattributed]]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

URLResource SizeEst Savings
The app for independent voices Get started Learn more div.pencraft > div.pencraft > div.pencraft > div.pencraft
substackcdn.com/img/growth_page/footer.jpeg1.7 MiB183.1 KiB
div.pencraft > div.pencraft > picture > img.img-OACg1c div.pencraft > div.pencraft > picture > img.img-OACg1c
/image/fetch/$s_!u9e1!,w_300,c_limit,f_webp,q_auto:good,f...34.0 KiB30.6 KiB
div.pencraft > div.pencraft > picture > img.img-OACg1c div.pencraft > div.pencraft > picture > img.img-OACg1c
/image/fetch/$s_!fgyZ!,w_315,c_limit,f_webp,q_auto:good,f...27.2 KiB5.6 KiB
a.pencraft > div.pencraft > picture > img.img-OACg1c a.pencraft > div.pencraft > picture > img.img-OACg1c
/image/fetch/$s_!Cez8!,w_520,h_272,c_fill,f_webp,q_auto:g...27.5 KiB4.5 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

lhId: page-4-IMG
nodeLabel: div.pencraft > div.pencraft > picture > img.img-OACg1c
path: 1,HTML,1,BODY,1,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,2,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,1,DIV,0,DIV,0,PICTURE,1,IMG
selector: div.pencraft > div.pencraft > picture > img.img-OACg1c
snippet: <img src="https://substackcdn.com/image/fetch/$s_!uaD6!,w_315,c_limit,f_webp,q_auto:…" sizes="315px" alt="" srcset="https://substackcdn.com/image/fetch/$s_!uaD6!,w_315,c_limit,f_auto,q_auto:…" width="315" height="420" loading="lazy" draggable="false" class="img-OACg1c pencraft pc-reset">

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.

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

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

RequestCache TTLTransfer Size
substack.com/cdn-cgi/challenge-platform/h/b/scripts/jsd/625261456364/main.js?14400.0 s12.7 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Estimated savings: 364 ms
URLTime Spent
www.substack.com/364 ms
substack.com/0.0 ms

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.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

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.

Estimated savings: 40 ms 51.8 KiB
URLTransfer SizeEst Savings
substackcdn.com/bundle/static/css/77496.13fa4a14.css32.8 KiB27.3 KiB
substackcdn.com/bundle/static/css/reader2.0991e6aa.css25.2 KiB24.6 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.

Estimated savings: 790 ms 974.7 KiB
URLTransfer SizeEst Savings
substackcdn.com/bundle/static/js/reader2.dd4aee9b.js619.3 KiB344.4 KiB
substackcdn.com/bundle/static/js/51606.9e5d2f4f.js301.3 KiB236.2 KiB
substackcdn.com/bundle/static/js/async/50551.9f31dfda.js95.0 KiB81.7 KiB
substackcdn.com/bundle/static/js/77496.a030b7b6.js81.4 KiB60.8 KiB
substackcdn.com/bundle/static/js/96869.cf1a6316.js37.7 KiB37.6 KiB
substackcdn.com/bundle/static/js/30440.3a078123.js44.3 KiB35.5 KiB
substackcdn.com/bundle/static/js/96924.6b3177b3.js43.7 KiB31.5 KiB
substackcdn.com/bundle/static/js/97993.36609a05.js27.7 KiB27.5 KiB
substackcdn.com/bundle/static/js/62744.d65af920.js35.0 KiB27.0 KiB
substackcdn.com/bundle/static/js/lib-router.faae56b7.js25.4 KiB24.3 KiB
substackcdn.com/bundle/static/js/28407.85861033.js27.0 KiB23.9 KiB
substackcdn.com/bundle/static/js/61861.fd526f64.js34.2 KiB22.4 KiB
substackcdn.com/bundle/static/js/45337.6965623b.js28.2 KiB22.1 KiB

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

URL
div.pencraft > div.pencraft > picture > img.img-OACg1c div.pencraft > div.pencraft > picture > img.img-OACg1c
/image/fetch/$s_!u9e1!,w_300,c_limit,f_webp,q_auto:good,f...
div.pencraft > div.pencraft > picture > img.img-OACg1c div.pencraft > div.pencraft > picture > img.img-OACg1c
/image/fetch/$s_!DzDi!,w_176,c_limit,f_webp,q_auto:good,f...

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
●JavaScript execution time 1.0 s
●Minimizes main-thread work 1.9 s
●Avoid long main-thread tasks 6 long tasks found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 20 ms
●Server Backend Latencies 260 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 160 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○User Timing marks and measures
○Avoid non-composited animations
75

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Failing Elements
Home Subscriptions Chat Activity Explore Profile Create div#entry > div.reader-nav-root > div.pencraft > div.pencraft

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.

Failing Elements
Subscriptions div.pencraft > div.pencraft > a.pencraft > div.pencraft
Chat div.pencraft > div.pencraft > a.pencraft > div.pencraft
Activity div.pencraft > div.pencraft > a.pencraft > div.pencraft
Explore div.pencraft > div.pencraft > a.pencraft > div.pencraft
Profile div.pencraft > div.pencraft > a.pencraft > div.pencraft
Create div.pencraft > div.pencraft > div.pencraft > button.pencraft
Get started div.pencraft > div.pencraft > div.pencraft > button.pencraft
For you div.pencraft > div.pencraft > div.pencraft > button#radix-P0-6
Mar 27 div.pencraft > span.pencraft > a.pencraft > span.pencraft
Subscribe div.pencraft > div.pencraft > div.pencraft > button.pencraft
22.2K div.pencraft > div.pencraft > button.pencraft > div.pencraft
1.2K div.pencraft > div.pencraft > button.pencraft > div.pencraft
565 div.pencraft > div.pencraft > button.pencraft > div.pencraft
Mar 29 div.pencraft > span.pencraft > a.pencraft > span.pencraft
Subscribe div.pencraft > div.pencraft > div.pencraft > button.pencraft
6.5K div.pencraft > div.pencraft > button.pencraft > div.pencraft
59 div.pencraft > div.pencraft > button.pencraft > div.pencraft
1K div.pencraft > div.pencraft > button.pencraft > div.pencraft
4h div.pencraft > span.pencraft > a.pencraft > span.pencraft
Subscribe div.pencraft > div.pencraft > div.pencraft > button.pencraft
129 div.pencraft > div.pencraft > button.pencraft > div.pencraft
You always own your intellectual property, mailing list, and subscriber payment… div.pencraft > div.pencraft > div.pencraft > p.pencraft
Get started div.pencraft > div.pencraft > div.pencraft > button.pencraft
3h div.pencraft > span.pencraft > a.pencraft > span.pencraft
Subscribe div.pencraft > div.pencraft > div.pencraft > button.pencraft
1.3K div.pencraft > div.pencraft > button.pencraft > div.pencraft
156 div.pencraft > div.pencraft > button.pencraft > div.pencraft
341 div.pencraft > div.pencraft > button.pencraft > div.pencraft
3h div.pencraft > span.pencraft > a.pencraft > span.pencraft
Subscribe div.pencraft > div.pencraft > div.pencraft > button.pencraft
bookshop.org/p/books/dr… div.pencraft > div.ProseMirror > p > a.pencraft
Mar 12 span.pencraft > span.pencraft > a.pencraft > span.pencraft
20 div.pencraft > div.pencraft > button.pencraft > div.pencraft
Join the most interesting and insightful discussions. div.pencraft > div.pencraft > div.pencraft > p.pencraft
Get started div.pencraft > div.pencraft > div.pencraft > button.pencraft
1h div.pencraft > span.pencraft > a.pencraft > span.pencraft
Subscribe div.pencraft > div.pencraft > div.pencraft > button.pencraft
5calls.org div.pencraft > a.pencraft > div.pencraft > p.pencraft
Spend 5 minutes. Make 5 calls. Make your voice heard. div.pencraft > a.pencraft > div.pencraft > p.pencraft
27 div.pencraft > div.pencraft > button.pencraft > div.pencraft
Get the app div.pencraft > div.pencraft > div.pencraft > button.pencraft
Juno News span > div.pencraft > span.pencraft > a.link-LIBpto
5m read div.pencraft > div.pencraft > span.pencraft > span.pencraft
∙ 4 likes div.pencraft > div.pencraft > span.pencraft > span.pencraft
∙ 3 comments div.pencraft > div.pencraft > span.pencraft > span.pencraft
Malone News span > div.pencraft > span.pencraft > a.link-LIBpto
18m read div.pencraft > div.pencraft > span.pencraft > span.pencraft
∙ 327 likes div.pencraft > div.pencraft > span.pencraft > span.pencraft
∙ 71 comments div.pencraft > div.pencraft > span.pencraft > span.pencraft
The Bulwark span > div.pencraft > span.pencraft > a.link-LIBpto
6m read div.pencraft > div.pencraft > span.pencraft > span.pencraft
∙ 421 likes div.pencraft > div.pencraft > span.pencraft > span.pencraft
privacy policy div.pencraft > div.pencraft > div.pencraft > a.pencraft

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Failing Elements
div.pencraft > div.pencraft > picture.pencraft > img.pencraft div.pencraft > div.pencraft > picture.pencraft > img.pencraft
div.pencraft > div.pencraft > picture.pencraft > img.pencraft div.pencraft > div.pencraft > picture.pencraft > img.pencraft
div.pencraft > div.pencraft > picture.pencraft > img.pencraft div.pencraft > div.pencraft > picture.pencraft > img.pencraft
div.pencraft > div.pencraft > picture.pencraft > img.pencraft div.pencraft > div.pencraft > picture.pencraft > img.pencraft
div.pencraft > div.pencraft > picture.pencraft > img.pencraft div.pencraft > div.pencraft > picture.pencraft > img.pencraft
div.pencraft > div.pencraft > picture.pencraft > img.pencraft div.pencraft > div.pencraft > picture.pencraft > img.pencraft

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.

Failing Elements
head > meta head > meta

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.

Failing Elements
Hayley DeRoche's avatar div.pencraft > a.pencraft > div.pencraft > a.pencraft
Hayley DeRoche div.pencraft > span > span.pencraft > a.pencraft
Mar 12 div.pencraft > span.pencraft > span.pencraft > a.pencraft
Juno News span > div.pencraft > span.pencraft > a.link-LIBpto
Malone News span > div.pencraft > span.pencraft > a.link-LIBpto
The Bulwark span > div.pencraft > span.pencraft > a.link-LIBpto

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Failing Elements
html html

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Failing Elements
22.2K div.pencraft > div.pencraft > div.pencraft > button.pencraft
1.2K div.pencraft > div.pencraft > div.pencraft > button.pencraft
565 div.pencraft > div.pencraft > div.pencraft > button.pencraft
6.5K div.pencraft > div.pencraft > div.pencraft > button.pencraft
59 div.pencraft > div.pencraft > div.pencraft > button.pencraft
1K div.pencraft > div.pencraft > div.pencraft > button.pencraft
129 div.pencraft > div.pencraft > div.pencraft > button.pencraft
6 div.pencraft > div.pencraft > div.pencraft > button.pencraft
1.3K div.pencraft > div.pencraft > div.pencraft > button.pencraft
156 div.pencraft > div.pencraft > div.pencraft > button.pencraft
341 div.pencraft > div.pencraft > div.pencraft > button.pencraft
20 div.pencraft > div.pencraft > div.pencraft > button.pencraft
1 div.pencraft > div.pencraft > div.pencraft > button.pencraft
27 div.pencraft > div.pencraft > div.pencraft > button.pencraft
3 div.pencraft > div.pencraft > div.pencraft > button.pencraft
7 div.pencraft > div.pencraft > div.pencraft > button.pencraft
○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>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Form elements have associated labels
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○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.

Deprecation / WarningSource
SharedStorage
substack.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
substack.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge
substack.com/cdn-cgi/challenge-platform/scripts/jsd/main.js

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

SourceDescription
substack.com/api/v1/messages/unread-count
Failed to load resource: the server responded with a status of 401 ()
substack.com/api/v1/search-modules
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
●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
○Use a strong HSTS policy
○Mitigate clickjacking with XFO or CSP
85

SEO

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

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

Uncrawlable Link
Subscriptions div.pencraft > div.pencraft > div.pencraft > a.pencraft
Chat div.pencraft > div.pencraft > div.pencraft > a.pencraft
Activity div.pencraft > div.pencraft > div.pencraft > a.pencraft
Profile div.pencraft > div.pencraft > div.pencraft > a.pencraft
3h div.pencraft > div.pencraft > span.pencraft > a.pencraft

To appear in search results, crawlers need access to your app.

Content Best Practices

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Failing Elements
div.pencraft > div.pencraft > picture.pencraft > img.pencraft div.pencraft > div.pencraft > picture.pencraft > img.pencraft
div.pencraft > div.pencraft > picture.pencraft > img.pencraft div.pencraft > div.pencraft > picture.pencraft > img.pencraft
div.pencraft > div.pencraft > picture.pencraft > img.pencraft div.pencraft > div.pencraft > picture.pencraft > img.pencraft
div.pencraft > div.pencraft > picture.pencraft > img.pencraft div.pencraft > div.pencraft > picture.pencraft > img.pencraft
div.pencraft > div.pencraft > picture.pencraft > img.pencraft div.pencraft > div.pencraft > picture.pencraft > img.pencraft
div.pencraft > div.pencraft > picture.pencraft > img.pencraft div.pencraft > div.pencraft > picture.pencraft > img.pencraft

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

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

Send Feedback