Lighthouse Desktop

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

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
Elevate ESL Lessons `div.max-w-6xl > a.flex > div.w-10 > img.w-full`	esl-go.com/logo.png	265.6 KiB	265.5 KiB
Idioms & Real Expressions `div.mb-10 > div.grid > div.group > img.absolute`	/photo-1517486808906-6ca8b3f04846?w=800&auto=format&fit=c...	71.9 KiB	60.4 KiB
Everyday Dialogues `div.mb-10 > div.grid > div.group > img.absolute`	/photo-1522202176988-66273c2fd55f?w=800&auto=format&fit=c...	43.7 KiB	33.2 KiB
Phrasal Verbs in Action `div.mb-10 > div.grid > div.group > img.absolute`	/photo-1529156069898-49953e39b3ac?w=800&auto=format&fit=c...	38.3 KiB	23.2 KiB
Grammar Structures `div.mb-10 > div.grid > div.group > img.absolute`	/photo-1456513080510-7bf3a84b82f8?w=800&auto=format&fit=c...	25.2 KiB	21.0 KiB
Past Simple Listening Practice: Weekend Stories & Memorable Events `div.grid > article.bg-white > div.relative > img.w-full`	/photo-1505740420928-5e560c06d30e?w=800&auto=format&fit=c...	15.9 KiB	12.7 KiB

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-4-IMG

nodeLabel: Grammar Structures

path: 1,HTML,1,BODY,0,DIV,0,DIV,1,MAIN,0,DIV,1,DIV,0,DIV,1,DIV,0,DIV,0,IMG

selector: div.mb-10 > div.grid > div.group > img.absolute

snippet: <img alt="Grammar Structures" referrerpolicy="no-referrer" class="absolute inset-0 w-full h-full object-cover transition-transform duration-…" src="https://images.unsplash.com/photo-1456513080510-7bf3a84b82f8?w=800&auto=fo…">

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

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.

URL	Transfer Size	Duration
/css2?family=Inter:wght@400;500;600;700;800&family=Plus+J...	1.4 KiB	256 ms
esl-go.com/assets/index-wDnpTs0m.css	8.9 KiB	69 ms

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

Diagnostics

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 60 ms 29.2 KiB

URL	Transfer Size	Est Savings
esl-go.com/assets/index-DfSHavb5.js	165.7 KiB	29.2 KiB

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: 120 ms 90.7 KiB

URL	Transfer Size	Est Savings
esl-go.com/assets/index-DfSHavb5.js	165.6 KiB	90.7 KiB

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

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Time to Interactive 1.3 s

●Max Potential First Input Delay 20 ms

●Minify CSS

●Reduce unused CSS

●Avoids enormous network payloads Total size was 668 KiB

●JavaScript execution time 0.1 s

●Minimizes main-thread work 0.2 s

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 170 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 20 ms

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○User Timing marks and measures

○Avoid long main-thread tasks

○Avoid non-composited animations

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
Choose a specific language focus to view corresponding listening practice tests. `div.mb-10 > div.flex > div > p.text-xs`
Phrasal Verbs (Soon) `div.bg-white > div.flex > span.px-3 > span`
Idioms (Soon) `div.bg-white > div.flex > span.px-3 > span`
Everyday Dialogues (Soon) `div.bg-white > div.flex > span.px-3 > span`
Click on any test to open the self-contained listening audio and interactive qu… `div.max-w-6xl > div.flex > div > p.text-xs`
Showing 2 tests `div > div.max-w-6xl > div.flex > span.text-xs`
Start test `div.p-5 > div.pt-3 > span.inline-flex > span`
Start test `div.p-5 > div.pt-3 > span.inline-flex > span`
Visit Elevate Store on TPT `div.max-w-6xl > section.bg-gradient-to-r > a.inline-flex > span`
01 `div.max-w-6xl > div.grid > div.bg-white > span.text-amber-600`
02 `div.max-w-6xl > div.grid > div.bg-white > span.text-amber-600`
03 `div.max-w-6xl > div.grid > div.bg-white > span.text-amber-600`
Listening Lessons `div.flex > div.flex > div.font-extrabold > span.text-amber-600`
TPT Store `div.max-w-6xl > div.flex > a.text-[#00897b] > span`
© 2026 Elevate Listening Lessons. All rights reserved. Free audio practice, gra… `div.min-h-screen > footer.border-t > div.border-t > p`

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
Authentic Audio Dialogues `div.max-w-6xl > div.grid > div.bg-white > h4.font-bold`

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-hidden="true"]` is not present on the document `<body>`

●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-hidden="true"]` elements do not contain focusable descendents

●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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA attributes are used as specified for the element's role

○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

○Elements use only permitted ARIA attributes

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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

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

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

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

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.

URL
esl-go.com/assets/index-DfSHavb5.js

●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

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.

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #	Content	Error
1	`<!doctype html>`	`Syntax not understood`
2	`<html lang="en">`	`Syntax not understood`
3	`<head>`	`Syntax not understood`
4	`<meta charset="UTF-8" />`	`Syntax not understood`
5	`<meta name="viewport" content="width=device-width, initial-scale=1.0" />`	`Syntax not understood`
6	`<title>Elevate Listening Lessons — English Listening Tests & Grammar Practice</title>`	`Syntax not understood`
7	`<meta name="description" content="Free grammar-based English listening lessons and interactive tests by Elevate ESL Lessons. Practice with authentic audio dialogues and instant scoring." />`	`Syntax not understood`
8	`<meta property="og:title" content="Elevate Listening Lessons — English Listening Tests & Grammar Practice" />`	`Unknown directive`
9	`<meta property="og:description" content="Free grammar-based English listening lessons and interactive tests by Elevate ESL Lessons. Practice with authentic audio dialogues and instant scoring." />`	`Unknown directive`
10	`<meta property="og:type" content="website" />`	`Unknown directive`
11	`<meta property="og:image" content="/logo.png" />`	`Unknown directive`
12	`<meta name="twitter:card" content="summary_large_image" />`	`Unknown directive`
13	`<link rel="canonical" href="https://esl-go.com" />`	`Unknown directive`
14	`<link rel="icon" type="image/png" href="/logo.png" />`	`Syntax not understood`
15	`<link rel="preconnect" href="https://fonts.googleapis.com" />`	`Unknown directive`
16	`<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />`	`Unknown directive`
17	`<link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700;800&family=Plus+Jakarta+Sans:wght@500;600;700;800&display=swap" rel="stylesheet" />`	`Unknown directive`
18	`<script type="module" crossorigin src="/assets/index-DfSHavb5.js"></script>`	`Syntax not understood`
19	`<link rel="stylesheet" crossorigin href="/assets/index-wDnpTs0m.css">`	`Syntax not understood`
20	`</head>`	`Syntax not understood`
21	`<body class="bg-[#f1f5f9] text-[#1e293b] font-sans antialiased selection:bg-[#fbbf24] selection:text-[#1e293b]">`	`Syntax not understood`
22	`<div id="root"></div>`	`Syntax not understood`
23	`</body>`	`Syntax not understood`
24	`</html>`	`Syntax not understood`

To appear in search results, crawlers need access to your app.

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

●Document has a valid `rel=canonical`