Skip to content
https://oxfordlearnersdictionaries.com

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.

76

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.

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
Spread the Word div.responsive_row > div.row > div.box > img.placeholder
dtcfza6z1c8xn.cloudfront.net/OLD_WoTM_culture_war.png121.7 KiB113.2 KiB
div.responsive_container > div.row > div.box > img.box-image div.responsive_container > div.row > div.box > img.box-image
/external/images/home_2020/OxEngLearnEx.jpg?version=2.3.76120.3 KiB109.1 KiB
Learn & Practise Grammar div.responsive_row > div.row > div.box > img
dtcfza6z1c8xn.cloudfront.net/grammar-promo-square.png103.1 KiB94.6 KiB
a.secondaryButton > div.dictionnary_title > div.img > img.box-image
/external/images/home_2020/OLD_home_productsOLDAE.png?ver...77.2 KiB74.9 KiB
a.secondaryButton > div.dictionnary_title > div.img > img.box-image
/external/images/home_2020/OLD_home_productsDOS.png?versi...74.1 KiB71.7 KiB
Topic Dictionaries div.responsive_row > div.row > div.box > img
dtcfza6z1c8xn.cloudfront.net/OLD_home_newtopicsfeature.png65.8 KiB57.3 KiB
a.secondaryButton > div.dictionnary_title > div.img > img.box-image
/external/images/home_2020/OLD_home_productsPEU.png?versi...28.3 KiB27.0 KiB
Oxford Test of English Learner Corpora Research Competition div.responsive_row > div.row > div.box > img.placeholder
dtcfza6z1c8xn.cloudfront.net/2026_02_otelc-research-image.png26.1 KiB21.5 KiB
iSpeaker div.responsive_row > div.row > div.box > img
dtcfza6z1c8xn.cloudfront.net/OLD_home_Word_lists_panel5.png19.7 KiB18.8 KiB
a.secondaryButton > div.dictionnary_title > div.img > img.box-image
/external/images/home_2020/OLD_home_productsOALD.png?vers...17.1 KiB16.1 KiB
a.secondaryButton > div.dictionnary_title > div.img > img.box-image
/external/images/home_2020/OLD_home_productsCollocs.png?v...12.4 KiB11.6 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-8-IMG
nodeLabel: iSpeaker
path: 1,HTML,1,BODY,0,DIV,2,DIV,1,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,IMG
selector: div.responsive_row > div.row > div.box > img
snippet: <img src="https://dtcfza6z1c8xn.cloudfront.net/OLD_home_Word_lists_panel5.png" alt="iSpeaker">

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

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: 305 ms

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

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.

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.

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.

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 with cache-control:no-store header cannot enter back/forward cache.Actionable

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.

URL
iSpeaker div.responsive_row > div.row > div.box > img
dtcfza6z1c8xn.cloudfront.net/OLD_home_Word_lists_panel5.png
div.responsive_container > div.row > div.box > img.box-image div.responsive_container > div.row > div.box > img.box-image
/external/images/home_2020/OxEngLearnEx.jpg?version=2.3.76
Learn & Practise Grammar div.responsive_row > div.row > div.box > img
dtcfza6z1c8xn.cloudfront.net/grammar-promo-square.png
a.secondaryButton > div.dictionnary_title > div.img > img.box-image
/external/images/home_2020/OLD_home_productsDOS.png?versi...
a.secondaryButton > div.dictionnary_title > div.img > img.box-image
/external/images/home_2020/OLD_home_productsPEU.png?versi...
a.secondaryButton > div.dictionnary_title > div.img > img.box-image
/external/images/home_2020/OLD_home_productsOLDAE.png?ver...
Spread the Word div.responsive_row > div.row > div.box > img.placeholder
dtcfza6z1c8xn.cloudfront.net/OLD_WoTM_culture_war.png
Oxford Test of English Learner Corpora Research Competition div.responsive_row > div.row > div.box > img.placeholder
dtcfza6z1c8xn.cloudfront.net/2026_02_otelc-research-image.png
Topic Dictionaries div.responsive_row > div.row > div.box > img
dtcfza6z1c8xn.cloudfront.net/OLD_home_newtopicsfeature.png
a.secondaryButton > div.dictionnary_title > div.img > img.box-image
/external/images/home_2020/OLD_home_productsOALD.png?vers...
a.secondaryButton > div.dictionnary_title > div.img > img.box-image
/external/images/home_2020/OLD_home_productsCollocs.png?v...
div.responsive_container > div.row > div.box > img.box-image div.responsive_container > div.row > div.box > img.box-image
/external/images/home_2020/OLD_home_learning_with_oxford....
div.responsive_container > div.row > div.box > img.box-image div.responsive_container > div.row > div.box > img.box-image
/external/images/home_2020/OLD_home_teaching_with_OLW.svg...
Oxford University Press logo footer#ox-footer > div.footer-container > div.container > img.logo-footer
/external/images/footer/logo-oup.svg?version=2.3.76
Oxford Learners Dictionaries div#ox-container > div#ox-header > div#flex-menu > img.old-logo
www.oxfordlearnersdictionaries.com/external/images/OLD_logo.svg?version=2.3.76

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
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Max Potential First Input Delay 60 ms
●Minify JavaScript
●Avoids enormous network payloads Total size was 1,710 KiB
●JavaScript execution time 0.2 s
●Minimizes main-thread work 0.5 s
●Avoid long main-thread tasks 2 long tasks found
●Network Requests
●Network Round Trip Times 100 ms
●Server Backend Latencies 90 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 200 ms
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○User Timing marks and measures
○Avoid non-composited animations
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.

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
PLANTS AND TREES div.row > div.wotd-box > a.origin > div

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
a.secondaryButton > div.dictionnary_title > div.img > img.box-image
a.secondaryButton > div.dictionnary_title > div.img > img.box-image
a.secondaryButton > div.dictionnary_title > div.img > img.box-image
a.secondaryButton > div.dictionnary_title > div.img > img.box-image
a.secondaryButton > div.dictionnary_title > div.img > img.box-image

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.row > div.wotd-box > div.dayhead > a.rss-icon div.row > div.wotd-box > div.dayhead > a.rss-icon

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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.homepage html.homepage

These items highlight common accessibility best practices.

○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
●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.
●Select elements have associated label elements.
●ARIA attributes are used as specified for the element's role
●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
●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.
●Heading elements appear in a sequentially-descending order
●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`[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-hidden="true"]` elements do not contain focusable descendents
○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
○Buttons have an accessible name
○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
○`<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
○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.
77

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
Topics

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 403 ()
Failed to load resource: the server responded with a status of 403 ()
Uncaught TypeError: window.__tcfapi is not a function
●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 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
85

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

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
body > div#ox-container > div#ox-header > a.go-to-top body > div#ox-container > div#ox-header > a.go-to-top
English form#search-form > div#dictionarySelector > div.csm > a
American English form#search-form > div#dictionarySelector > div.csm > a

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

Content Best Practices

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
a.secondaryButton > div.dictionnary_title > div.img > img.box-image
a.secondaryButton > div.dictionnary_title > div.img > img.box-image
a.secondaryButton > div.dictionnary_title > div.img > img.box-image
a.secondaryButton > div.dictionnary_title > div.img > img.box-image
a.secondaryButton > div.dictionnary_title > div.img > img.box-image

Format your HTML in a way that enables crawlers to better understand your app’s content.

○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
●robots.txt is valid
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback