Skip to content
https://hospitalbagchecklist.online

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.

67

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
/beacon.min.js/vce701823e78c4301a35b7e07294d8730179208881...86400.0 s10.2 KiB

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.122998] map[node:map[boundingRect:map[bottom:13670 height:12996 left:0 right:412 top:674 width:412] lhId:page-1-SECTION nodeLabel:0 of 35 packed0% ● Saved on this device · Clearing browser data may remove you… path:1,HTML,1,BODY,4,DIV,1,MAIN,1,SECTION selector:body.size-full > div.flex > main.flex-1 > section#checklist snippet:<section id="checklist" aria-label="Your checklist" class="scroll-mt-20"> type:node] score:0.122998 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://hospitalbagchecklist.online/_next/static/media/dc6d2a64e9dbf3bc-s.p.4b9eb7a1.woff2]]] type:subitems]]]

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

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.

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

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
0 of 35 packed0% ● Saved on this device · Clearing browser data may remove you… body.size-full > div.flex > main.flex-1 > section#checklist
0.123

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.

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

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.

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.

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 Evaluation1.4 s
Other740 ms
Style & Layout704 ms
Script Parsing & Compilation222 ms
Rendering180 ms
Parse HTML & CSS121 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
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.

●Document request latency
●Optimize DOM size
●Font display
●Forced reflow
●Improve image delivery
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Avoids enormous network payloads Total size was 583 KiB
●Avoid long main-thread tasks 10 long tasks found
●Image elements have explicit `width` and `height`
●Network Requests
●Network Round Trip Times 10 ms
●Server Backend Latencies 30 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 140 ms
○INP breakdown
○LCP request discovery
○User Timing marks and measures
○Avoid non-composited animations
97

Accessibility

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

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
0% div.min-w-[200px] > div.flex > p.text-[15px] > span.ml-1.5
· Clearing browser data may remove your checklist. div.flex > span.text-[13px] > div.hbc-noprint > span.text-foreground/55
44 div.sticky > div#hbc-list > button.min-h-9 > span.ml-1.5
35 div.sticky > div#hbc-list > button.min-h-9 > span.ml-1.5
Need to get 35 · Pack last 6 · Tasks 0/7 div.mx-auto > div.grid > div.min-w-0 > p.mt-2
16 left div.mt-5 > section > h2#sec-mom > span.text-[13px]
Check-in at the front desk usually asks for these. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
Speeds up admission if you pre-registered. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
Cover up for walking the halls and visitors. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
Something comfortable of your own to sleep in after birth. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
For bleeding after birth — check with your hospital what it supplies. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
A loose outfit for the ride home. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
Your own toothbrush and wash things feel familiar. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
Hospital air is dry; lips chap quickly. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
Keeps hair out of the way during labor. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
So you can see without fiddling with contacts. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
Your regular medicines — ask your care team what to bring. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
For after birth — ask what you may eat during labor. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
10 left div.mt-5 > section > h2#sec-baby > span.text-[13px]
Needed for the baby’s ride home; install it before the due date. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
Newborns lose heat through their heads. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
Tuck over the harness in the car seat, never under it. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
Check with your hospital — many provide some during the stay. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
Diaper changes and quick clean-ups. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
If you plan to formula feed — check with your hospital what it supplies. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
Skipped div.flex > div.min-w-0 > span.mt-1.5 > span.hbc-chip
Baby bag div.flex > div.min-w-0 > span.mt-1.5 > span.hbc-chip-sm
6 left div.mt-5 > section > h2#sec-partner > span.text-[13px]
A fresh change for a long stay. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
Toothbrush and deodorant for the support person. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
The support person’s own regular medicines. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
Food and change for long hours and vending machines. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
Makes a chair or couch bed more bearable. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
Lets your partner support you in the shower or tub. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
Skipped div.flex > div.min-w-0 > span.mt-1.5 > span.hbc-chip
Partner bag div.flex > div.min-w-0 > span.mt-1.5 > span.hbc-chip-sm
5 left div.mt-5 > section > h2#sec-shared > span.text-[13px]
Calls, photos and updates for family. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
Outlets are often far from the bed — a long cable reaches. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
Backup power when you can’t reach an outlet. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
Easy to forget in the rush out the door. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
Keeps used clothes apart from clean ones. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
7 left div.mt-5 > section > h2#sec-leaving > span.text-[13px]
Find out what is supplied so you don’t overpack. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
Know the way, where to park and which entrance to use. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
So anyone can grab the bags if you can’t. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
Installing early avoids a scramble at discharge. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
Someone ready to step in, day or night. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
One less stop when it’s time to go. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
Numbers ready in every phone that might make the call. li.hbc-row > div.flex > div.min-w-0 > span.hbc-row-purpose
· By the door ul.mt-2 > li.flex > span > span.text-foreground/55
18 section.rounded-2xl > ul.mt-2 > li.flex > span.tabular-nums
· By the door ul.mt-2 > li.flex > span > span.text-foreground/55
· Closet ul.mt-2 > li.flex > span > span.text-foreground/55
· Car ul.mt-2 > li.flex > span > span.text-foreground/55
· Entry table ul.mt-2 > li.flex > span > span.text-foreground/55
These are illustrative examples of how the checklist works, not reviews from re… div.flex > main.flex-1 > section.mx-auto > p.mt-3
This site is a planning aid, not medical advice. If you’re unsure whether to go… body.size-full > div.flex > main.flex-1 > p.mx-auto
© 2026 hospitalbagchecklist.online · Free forever · No ads · No affiliate links div.flex > footer.hbc-noprint > div.border-t > p.mx-auto

These are opportunities to improve the legibility of your content.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Hospital Bag Checklist div.flex > header.hbc-noprint > div.mx-auto > a.flex
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
More li.hbc-row > div.flex > div.hbc-row-actions > button.hbc-mini
English div.lg:col-span-2 > div.mt-4 > details.hbc-lang > summary.flex
○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
●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
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●`[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
●ARIA `progressbar` elements have accessible names
●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
●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
○`[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
○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.
○Image elements have `[alt]` attributes
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[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.
○Identical links have the same purpose.
○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.
96

Best Practices

General

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
ReferenceError: e is not defined at https://hospitalbagchecklist.online/:1:5953 at https://hospitalbagchecklist.online/:1:6122
●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 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
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Detected JavaScript libraries
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
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`
○Image elements have `[alt]` attributes

Send Feedback