Skip to content
https://www.readingrockets.org

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.

44

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:142.396 source:map[column:156 line:8 type:source-location url:https://www.readingrockets.org/sites/default/files/js/js_NV6AhuKEGPT5fCuOs8ub6sybUcptyCfgOBuWS8vcvpQ.js?scope=footer&delta=1&language=en&theme=readingrockets_d9&include=eJxlj9sOwiAMQH-IyLOPfgnpRtN1louFqfj1Ml7c4stJOIc2KaVEgq4CWeowdH5fYIX3WQYj8Gl2h1FPbmOHggFjLXYGTVtBGeGFFSxJmkDcWn4qgwIp5MVliPtfBM-RNM13rMX563Hory3doBpV57lkgWbXx4ba3JxChsoTC9e297KAoh28RQ69pXjwlfvOYJ6Mr2IHx7FfvNRqgw urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:123.012 source:map[column:45355 line:1 type:source-location url:https://www.readingrockets.org/core/assets/vendor/jquery/jquery.min.js?v=4.0.0 urlProvider:network]] map[reflowTime:0.671 source:map[column:46159 line:1 type:source-location url:https://www.readingrockets.org/core/assets/vendor/jquery/jquery.min.js?v=4.0.0 urlProvider:network]] map[reflowTime:0.961 source:map[column:45377 line:1 type:source-location url:https://www.readingrockets.org/core/assets/vendor/jquery/jquery.min.js?v=4.0.0 urlProvider:network]] map[reflowTime:17.752 source:map[column:76400 line:1 type:source-location url:https://www.readingrockets.org/core/assets/vendor/jquery/jquery.min.js?v=4.0.0 urlProvider:network]]]

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-DIV
nodeLabel: Reading Rockets offers a rich library of evidence-based classroom strategies to…
path: 1,HTML,1,BODY,2,DIV,0,DIV,3,DIV,0,MAIN,1,DIV,0,DIV,0,DIV,0,ARTICLE,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV
selector: div.field-content > div.paragraph-panel > div.content-container > div.panel-intro
snippet: <div class="panel-intro">

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.

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
elementary teachers talking with two students at their desks div.image-carousel-image > div.field > picture > img
/sites/default/files/styles/carousel_poster_image_mobile_...119.1 KiB108.7 KiB
Two young girls looking at picture books at the library div.image-carousel-image > div.field > picture > img
/sites/default/files/styles/carousel_poster_image_mobile_...110.8 KiB100.5 KiB
two kids lay on floor looking at an open picture book div.image-carousel-image > div.field > picture > img
/sites/default/files/styles/carousel_poster_image_mobile_...64.0 KiB53.7 KiB
closeup of young boy holding a book div.image-carousel-image > div.field > picture > img
/sites/default/files/styles/carousel_poster_image_mobile_...60.5 KiB50.1 KiB
girl looks up from her writing notebook while leaning against tree outdoors div.image-carousel-image > div.field > picture > img
/sites/default/files/styles/carousel_poster_image_mobile_...31.1 KiB25.4 KiB
Diverse group of elementary students working on writing project div.image-card-image > div.field > picture > img
/sites/default/files/styles/card_image_mobile_2x/public/2...34.0 KiB24.5 KiB
Multicultural group of smiling elementary students div.image-carousel-image > div.field > picture > img
/sites/default/files/styles/carousel_poster_image_mobile_...29.9 KiB24.4 KiB
elementary teacher talking with students during lesson div.image-card-image > div.field > picture > img
/sites/default/files/styles/card_image_mobile_2x/public/2...31.4 KiB22.7 KiB
Young boy looking up at butterflies div.image-carousel-image > div.field > picture > img
/sites/default/files/styles/carousel_poster_image_mobile_...24.8 KiB20.2 KiB
Reading tutor working with a first grade student at a desk div.image-card-image > div.field > picture > img
/sites/default/files/styles/card_image_mobile_2x/public/2...25.5 KiB18.4 KiB
girl looks up with finger on temple, deep in thought div.image-carousel-image > div.field > picture > img
/sites/default/files/styles/carousel_poster_image_mobile_...21.5 KiB17.5 KiB
Elementary teacher working with student during reading instruction div.image-card-image > div.field > picture > img
/sites/default/files/styles/card_image_mobile_2x/public/2...20.5 KiB14.8 KiB
Illustration of two fish looking at an open book article.media > div.field > picture > img
/sites/default/files/styles/sticker_2x/public/stickers/rr...18.0 KiB14.5 KiB
Looking at Writing div.image-card-image > div.field > picture > img
/sites/default/files/styles/card_image_mobile_2x/public/l...18.0 KiB12.9 KiB

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

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.

Estimated savings: 1.4 s 178.0 KiB

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.1 s
Other1.0 s
Style & Layout1.0 s
Parse HTML & CSS216 ms
Script Parsing & Compilation175 ms
Rendering66 ms

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 1,561 KiB
●JavaScript execution time 1.2 s
●Avoid long main-thread tasks 12 long tasks found
●Avoid non-composited animations 10 animated elements found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 20 ms
●Server Backend Latencies 90 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 90 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○User Timing marks and measures
100

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.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●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
○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 type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○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.
○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.
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
Failed to load resource: the server responded with a status of 404 ()
●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 DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
100

SEO

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

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

Send Feedback