Skip to content
https://edutopia.org

Lighthouse Desktop

· 0 checks — Desktop 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.

81

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.

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

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

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.
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

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.

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.

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
Building Empathy Through Mixed-Media Art div.css-lpv8ee > a > picture > img.css-e3lg9r
i.ytimg.com/vi/RNZwzHtAnxQ/maxresdefault.jpg133.3 KiB117.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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 213 ms
URLTime Spent
edutopia.org/213 ms
www.edutopia.org/0.0 ms

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.

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 6.1 KiB

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.

Estimated savings: 0.0 ms 58.8 KiB

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

●Layout shift culprits
●Optimize DOM size
●Font display
●LCP breakdown
●LCP request discovery
●Modern HTTP
●Optimize viewport for mobile
●Minify JavaScript
●Avoids enormous network payloads Total size was 2,023 KiB
●User Timing marks and measures 7 user timings
●JavaScript execution time 0.7 s
●Minimizes main-thread work 1.2 s
●Avoid long main-thread tasks 4 long tasks found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 120 ms
●Server Backend Latencies 120 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 10 ms
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○Avoid non-composited animations
87

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.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite
div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite div.css-15k3j3w > div.css-b06ysn > div.lite > button.lite

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
TOPICS nav.css-1dhnxoy > ul.css-5mz8rd > li.css-xjkdwq > button#topics-menu-trigger
VIDEOS nav.css-1dhnxoy > ul.css-5mz8rd > li.css-xjkdwq > a.css-1ksxkkd
ASK & ANSWER nav.css-1dhnxoy > ul.css-5mz8rd > li.css-xjkdwq > a.css-1ksxkkd
INTEGRATED STUDIES div.css-124ae9w > div.hero-card-bottom-wrap-bottom > div.css-1seknyz > div.eyebrow
Bill Manchester div.hero-card-bottom-wrap-bottom > div.css-1seknyz > div.css-rs4cum > a.css-1s343gm
CRITICAL THINKING div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow
Maurice J. Elias div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm
FORMATIVE ASSESSMENT div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow
Katie R. Medill div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm
Hear from peers! div.css-pfq62c > div.skeleton-container > div > a.css-1tz00mm
SOCIAL & EMOTIONAL LEARNING (SEL) div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow
ADMINISTRATION & LEADERSHIP div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow
Andrew Miller div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm
CLASSROOM MANAGEMENT div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow
Wendy Turner div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm
LITERACY div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow
Andrew Paull div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm
STUDENT ENGAGEMENT div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow
Kathryn Lemerich div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm
Jessica Holloway div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm
RESEARCH div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow
Andrea Tamayo div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm
CURRICULUM PLANNING div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow
Miriam Plotinsky div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm
POPULAR div.css-1f07lbu > div.css-jxc7g8 > div.css-q1v2j2 > span.css-1td86i2
COMMUNICATION SKILLS div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow
Christina Grassi div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm
Meghan Lowe div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm
TECHNOLOGY INTEGRATION div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow
BRAIN-BASED LEARNING div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow
STUDENT ENGAGEMENT div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow
Cathleen Beachboard div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm
TEACHING STRATEGIES div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow
SOCIAL & EMOTIONAL LEARNING (SEL) div.css-jxc7g8 > div.css-q1v2j2 > span.css-1td86i2 > a
TEACHING STRATEGIES div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow
SOCIAL & EMOTIONAL LEARNING (SEL) div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow
Connie Morris div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm
SOCIAL & EMOTIONAL LEARNING (SEL) div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow
Donna Paul div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm
SOCIAL & EMOTIONAL LEARNING (SEL) div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow
Cara Zelas div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm
SOCIAL & EMOTIONAL LEARNING (SEL) div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow
Matthew James Friday div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm
CLASSROOM MANAGEMENT div.css-jxc7g8 > div.css-q1v2j2 > span.css-1td86i2 > a
CLASSROOM MANAGEMENT div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow
Rachel Lawton div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm
TEACHING STRATEGIES div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow
CLASSROOM MANAGEMENT div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow
Crystal Frommert div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm
CLASSROOM MANAGEMENT div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow
Corrie Littlejohn-Pope div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm
CLASSROOM MANAGEMENT div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow
Todd Finley div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm
STUDENT WELLNESS div.css-jxc7g8 > div.css-q1v2j2 > span.css-1td86i2 > a
STUDENT WELLNESS div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow
Amy Brownlee div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm
STUDENT WELLNESS div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow
Amy Brownlee div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm
ADMINISTRATION & LEADERSHIP div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow
Jerald McNair div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm
STUDENT WELLNESS div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow
Sheila Garth div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm
STUDENT WELLNESS div.css-o76eps > div.view > div.css-wi0ozw > div.eyebrow
Ella Miesner div.view > div.css-wi0ozw > div.css-rs4cum > a.css-1s343gm
Privacy Policy section > ul.css-p2bolw > li.css-11rkab1 > a.css-14vv2hs
Terms of Use section > ul.css-p2bolw > li.css-11rkab1 > a.css-14vv2hs

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
POPULAR TOPICS section.topic-links > nav.css-13gb0g9 > div.css-1swx3yj > h5.css-13tn2mc

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>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●`[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 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.
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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
○`[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
○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
○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.
○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.
○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.
81

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
AttributionReporting

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 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
●Detected JavaScript libraries
○Redirects HTTP traffic to HTTPS
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