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

74

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.

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
section.max-w-6xl > div.grid > div.relative > div.absolute section.max-w-6xl > div.grid > div.relative > div.absolute
nymeriarosebooks.com/static/char-emma-age9.webp8.1 MiB7.3 MiB
section.max-w-6xl > div.grid > div.relative > div.absolute section.max-w-6xl > div.grid > div.relative > div.absolute
nymeriarosebooks.com/static/char-emma-age12.webp7.9 MiB7.0 MiB
Toby the Turtle™ div.relative > div > div.absolute > img.w-full
nymeriarosebooks.com/static/char-walter-whale.webp678.5 KiB588.5 KiB
Wendy the Weasel™ div.relative > div > div.absolute > img.w-full
nymeriarosebooks.com/static/char-riley-raccoon.webp496.1 KiB429.3 KiB
Toby the Turtle™ div.relative > div > div.absolute > img.w-full
nymeriarosebooks.com/static/char-oliver-otter.webp462.2 KiB400.0 KiB
Emma Louise div.relative > div > div.absolute > img.w-full
nymeriarosebooks.com/static/char-emma-age2.webp283.0 KiB244.9 KiB
Nymeria Rose, author of the Lake Stillwater Community™ div.float-right > div.relative > div.relative > img.w-full
nymeriarosebooks.com/static/author-nymeria-rose.jpg75.6 KiB54.0 KiB
div.flex-1 > main > section.relative > div.absolute div.flex-1 > main > section.relative > div.absolute
nymeriarosebooks.com/static/lake-stillwater-bg.webp302.1 KiB46.2 KiB
Lake Stillwater Books stone marker logo header.fixed > nav.max-w-6xl > a.flex > img.h-10
nymeriarosebooks.com/static/logo-stone-marker.webp31.2 KiB30.7 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
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
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.

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

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: 750 ms 126.5 KiB
URLTransfer SizeEst Savings
nymeriarosebooks.com/assets/index-BglyoBit.js231.1 KiB126.5 KiB

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

●Layout shift culprits
●Document request latency
●Optimize DOM size
●Font display
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Max Potential First Input Delay 20 ms
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●JavaScript execution time 0.3 s
●Minimizes main-thread work 2.0 s
●Avoid long main-thread tasks 6 long tasks found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 40 ms
●Server Backend Latencies 110 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 40 ms
○INP breakdown
○LCP request discovery
○User Timing marks and measures
○Avoid non-composited animations
○Avoid large layout shifts
84

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

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Home About All Books Emma's First Adventures™ (0–3) Walter's Lake Adventures™ (… header.fixed > nav.max-w-6xl > div.lg:hidden > div.absolute

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Home div.absolute > ul.p-2 > li > a.block
About div.absolute > ul.p-2 > li > a.block
All Books div.absolute > ul.p-2 > li > a.block
Emma's First Adventures™ (0–3) div.absolute > ul.p-2 > li > a.block
Walter's Lake Adventures™ (3–6) div.absolute > ul.p-2 > li > a.block
Lake Stillwater Early Learning™ (6–8) div.absolute > ul.p-2 > li > a.block
Emma & Walter's Shoreline Adventures™ (8–12) div.absolute > ul.p-2 > li > a.block
Growing Up Lake Stillwater™ (12–YA) div.absolute > ul.p-2 > li > a.block
The Lake Stillwater Chronicles™ (Adult) div.absolute > ul.p-2 > li > a.block
Characters div.absolute > ul.p-2 > li > a.block
Downloads div.absolute > ul.p-2 > li > a.block
Games div.absolute > ul.p-2 > li > a.block
Parents & Educators div.absolute > ul.p-2 > li > a.block
Contact div.absolute > ul.p-2 > li > a.block

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Explore the Books div.max-w-6xl > div.text-lake-100 > div.flex > a.px-7
ONE WORLD, EVERY READER main > section.max-w-6xl > div.text-center > p.font-sans
Learn more → div.relative > div.relative > div.flex > a.inline-block
Walter's books → div.relative > div.relative > div.flex > a.inline-block
Learn more → div.relative > div.relative > div.flex > a.inline-block
Learn more → div.relative > div.relative > div.flex > a.inline-block
Learn more → div.relative > div.relative > div.flex > a.inline-block
Adult fiction → div.relative > div.relative > div.flex > a.inline-block
Parents & Educators page → div.max-w-4xl > div.bg-white > div.flex-1 > a.inline-block
nymeriarosebooks@outlook.com div.max-w-6xl > div.grid > div > a.text-xs
EXPLORE div.max-w-6xl > div.grid > nav > p.font-sans
STAY IN THE LOOP div.max-w-6xl > div.grid > div > p.font-sans
Notify me div > form.mt-2 > div.flex > button.px-5
© 2026 Nymeria Rose. All rights reserved. footer.bg-lake-900 > div.max-w-6xl > div.mt-12 > p
Privacy Policy div.max-w-6xl > div.mt-12 > div.flex > a.hover:text-lake-200
Parents & Educators div.max-w-6xl > div.mt-12 > div.flex > a.hover:text-lake-200

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Home About All Books Emma's First Adventures™ (0–3) Walter's Lake Adventures™ (… nav.max-w-6xl > div.lg:hidden > div.absolute > ul.p-2

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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
Nymeria Rose div.min-h-screen > header.fixed > nav.max-w-6xl > a.flex
Oliver, the Otter™ Oliver, the Otter™ The Mischief Maker He didn’t mean to c… section.relative > div.relative > div.grid > div.relative
Emma Louise Emma Louise The Curious Explorer Six years old and asking questi… section.relative > div.relative > div.grid > div.relative
Riley the Raccoon™ Riley the Raccoon™ The Clever Collector If it’s shiny, Ri… section.relative > div.relative > div.grid > div.relative
○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.
●`button`, `link`, and `menuitem` elements have accessible names
●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 have a discernible name
●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
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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 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
○Links are distinguishable without relying on color.
○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.
100

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

●Uses HTTPS
●Avoids 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 clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
○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
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
○robots.txt is valid
○Document has a valid `rel=canonical`

Send Feedback