Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

A 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:37.415 source:map[type:text value:[unattributed]]]]

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG

nodeLabel: The #1 choice for journaling for millions of people since 2008

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

selector: div.shrink-0 > div.flex > div.relative > img

snippet: <img alt="The #1 choice for journaling for millions of people since 2008" width="540" height="405" decoding="async" data-nimg="1" style="color:transparent" srcset="/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fhero-image-03.9070c3b3.jpg&w=…" src="/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fhero-image-03.9070c3b3.jpg&w=…">

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

title: Preconnected origins

value: no origins were preconnected

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

title: Preconnect candidates

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
Customize preview `div.max-w-3xl > div.transition-all > div.relative > img.mx-auto`	/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Ffeatures-hom...	74.0 KiB	60.2 KiB
The #1 choice for journaling for millions of people since 2008 `div.shrink-0 > div.flex > div.relative > img`	/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fhero-image-0...	21.2 KiB	13.2 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
penzu.com/_next/static/css/2ff163e3720bf447.css	15.1 KiB
penzu.com/_next/static/css/bee9e1170c7ea52e.css	2.7 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

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: 870 ms 220.3 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-SCST8L650K&cx=c&gtm=4e64h1	162.7 KiB	67.3 KiB
penzu.com/_next/static/chunks/c857e369-da905be1d23b2b43.js	90.6 KiB	66.9 KiB
www.googletagmanager.com/gtm.js?id=GTM-5NRNLRS	119.8 KiB	63.3 KiB
penzu.com/_next/static/chunks/5827-68d73673c4d10db3.js	25.1 KiB	22.8 KiB

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 reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

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

●Use efficient cache lifetimes

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 949 KiB

●User Timing marks and measures 5 user timings

●JavaScript execution time 1.0 s

●Minimizes main-thread work 1.7 s

●Avoid long main-thread tasks 6 long tasks found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 190 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

●Initial server response time was short Root document took 110 ms

○INP breakdown

○Avoid non-composited animations

○Avoid large layout shifts

Accessibility

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

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
Start your free journal now `div.text-center > div.max-w-xs > div > button.btn-xlg`
Organize `div.grid > button.text-center > div > div.md:text-lg`
Remember `div.grid > button.text-center > div > div.md:text-lg`
Encrypt `div.grid > button.text-center > div > div.md:text-lg`
Phone `div.mb-8 > button.flex > div > div.text-zinc-800`
When not near your computer, you can continue to write in and read your journal… `div.mb-8 > button.flex > div > div.text-slate-500`
Tablet `div.mb-8 > button.flex > div > div.text-zinc-800`
If you have an iPad or Android tablet you can enjoy the same familiar mobile ex… `div.mb-8 > button.flex > div > div.text-slate-500`
@anafricandiva `div.h-[370px] > div.w-full > hgroup.flex-grow-1 > p.font-merriweather`
Penzu `div.h-[370px] > section > p.text-lg > strong.text-blue-500`
@thisismeihere `div.h-[370px] > div.w-full > hgroup.flex-grow-1 > p.font-merriweather`
Headspace + Penzu `div.h-[370px] > section > p.text-lg > strong.text-blue-500`
@sunoppositemoon `div.h-[370px] > div.w-full > hgroup.flex-grow-1 > p.font-merriweather`
Penzu `div.h-[370px] > section > p.text-lg > strong.text-blue-500`
(-60%) `div > div.flex > div.text-sm > span.text-emerald-500`
Get started `div.max-w-sm > div.relative > div.p-3 > button.btn-lg`
Most Popular `div.max-w-sm > div.relative > div.absolute > div.inline-flex`
/ year `div.relative > div.mb-4 > div.inline-flex > span.font-medium`
Go Pro -> `div.max-w-sm > div.relative > div.p-3 > a.btn-lg`
/ year `div.relative > div.mb-4 > div.inline-flex > span.font-medium`
Go Pro+ -> `div.max-w-sm > div.relative > div.p-3 > a.btn-lg`
Start your free journal now! `div.relative > div.max-w-xs > button.btn-xlg > span`
Free signup `div.sm:col-span-6 > ul.text-sm > li > a.text-neutral-600`
Penzu PRO `div.sm:col-span-6 > ul.text-sm > li > a.text-neutral-600`
Login `div.sm:col-span-6 > ul.text-sm > li > a.text-neutral-600`
Support `div.sm:col-span-6 > ul.text-sm > li > a.text-neutral-600`
Terms & conditions `div.sm:col-span-6 > ul.text-sm > li > a.text-neutral-600`
Privacy policy `div.sm:col-span-6 > ul.text-sm > li > a.text-neutral-600`
Journal prompts `div.sm:col-span-6 > ul.text-sm > li > a.text-neutral-600`
What is a journal? `div.sm:col-span-6 > ul.text-sm > li > a.text-neutral-600`
Pregnancy journal `div.sm:col-span-6 > ul.text-sm > li > a.text-neutral-600`
Reflective journal `div.sm:col-span-6 > ul.text-sm > li > a.text-neutral-600`
Bible journal `div.sm:col-span-6 > ul.text-sm > li > a.text-neutral-600`
Dream journal `div.sm:col-span-6 > ul.text-sm > li > a.text-neutral-600`
Journal examples `div.sm:col-span-6 > ul.text-sm > li > a.text-neutral-600`
Five year journal `div.sm:col-span-6 > ul.text-sm > li > a.text-neutral-600`
Secret diary `div.sm:col-span-6 > ul.text-sm > li > a.text-neutral-600`
Electronic diary `div.sm:col-span-6 > ul.text-sm > li > a.text-neutral-600`
Diary templates `div.sm:col-span-6 > ul.text-sm > li > a.text-neutral-600`
Wedding diary `div.sm:col-span-6 > ul.text-sm > li > a.text-neutral-600`
School diary `div.sm:col-span-6 > ul.text-sm > li > a.text-neutral-600`
Health diary `div.sm:col-span-6 > ul.text-sm > li > a.text-neutral-600`
Food diary `div.sm:col-span-6 > ul.text-sm > li > a.text-neutral-600`
© 2026 Penzu Inc. All rights reserved. `footer.bg-red-50 > div.max-w-6xl > div.md:flex > div.text-sm`

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Sister Joy `div.h-[370px] > div.w-full > hgroup.flex-grow-1 > h5.font-bold`
Penzu `div.max-w-6xl > div.grid > div.sm:col-span-6 > h6.text-sm`

These are opportunities to improve keyboard navigation in your application.

○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

●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

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

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

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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

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

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

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

○`[lang]` attributes have a valid value

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

○Elements with visible text labels have matching accessible names.

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

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

100

Best Practices

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

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.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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