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

85

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:39.516 source:map[column:18520 line:1 type:source-location url:https://www.yourdictionary.com/_nuxt/vendors/app.f4d8d9f25d320d0e5f9f.js urlProvider:network]] map[reflowTime:0.147 source:map[column:114482 line:1 type:source-location url:https://www.yourdictionary.com/_nuxt/commons/app.0abf6ef5773581f60ac7.js urlProvider:network]] map[reflowTime:1.712 source:map[column:200233 line:1 type:source-location url:https://www.yourdictionary.com/_nuxt/vendors/app.f4d8d9f25d320d0e5f9f.js urlProvider:network]] map[reflowTime:0.248 source:map[column:109096 line:1 type:source-location url:https://www.yourdictionary.com/_nuxt/app.2ba3b02a996f825e8241.js urlProvider:network]]]

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

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.

RequestCache TTLTransfer Size
c.amazon-adsystem.com/aax2/apstag.js3600.0 s90.9 KiB
/lovetoknow-1r2kdxaraW/yourdictionary.com/prebid-wrapper.js3600.0 s88.1 KiB
cdn.id5-sync.com/api/1.0/id5-api.js3600.0 s34.4 KiB
secure.cdn.fastclick.net/js/pubcid/latest/pubcid.min.js900.0 s21.7 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
/lovetoknow-1r2kdxaraW/yourdictionary.com/prebid-load.js3600.0 s16.5 KiB
tagan.adlightning.com/lovetoknow/op.js3600.0 s15.4 KiB
raven-static.aditude.io/prod/1.19.14-y0ptsc/raven.js604800.0 s107.1 KiB
scripts.clarity.ms/0.8.60-beta/clarity.js86400.0 s25.0 KiB
js-sec.indexww.com/ht/p/185643-100517605785273.js14400.0 s11.0 KiB
eus.rubiconproject.com/usync.js19970.0 s11.5 KiB
code.ltkcdn.net/ltkrev.js0.0 ms7.1 KiB
htlbid.com/v3/yourdictionary.com/htlbid.js600.0 s7.0 KiB
tags.crwdcntrl.net/lt/c/16576/sync.min.js86400.0 s13.5 KiB
assets.bounceexchange.com/cache/4422/website-1e00c8aba9677dd7acf53c61b46ab419.js120.0 s5.0 KiB
tag.bounceexchange.com/4422/i.js60.0 s3.5 KiB
signal-beacon.s-onetag.com/beacon.min.js86400.0 s8.7 KiB
get.s-onetag.com/97e090f4-23bc-45b9-9e85-3ccae3218905/tag.min.js86400.0 s6.7 KiB
raven-edge.aditude.io/raven/lovetoknow-main-zfyc6/library.js300.0 s2.6 KiB
rules.quantcount.com/rules-p-p7MTDBqm32Fqn.js3600.0 s2.9 KiB
config.aps.amazon-adsystem.com/configs/16597f7a-8901-4808-aeac-5fae6e1418203600.0 s2.6 KiB
/components/htl-injector-component.6f9fd855080891057769.js86400.0 s5.1 KiB
/83f91531-6cd5-4b1e-b17f-c3632708d79b/launchpad-liveramp.js0.0 ms1.7 KiB
/components/creative-timed-refresh-component.a1a922b43837...86400.0 s4.1 KiB
/components/first-party-data-component.9031b6342187473708...86400.0 s2.9 KiB
/state/js?website_id=4422&device_id=8631380170478681290&v...0.0 ms978 B
/components/schain-config-component.ed1cd260619f0e580cd3.js86400.0 s2.4 KiB
config.aps.amazon-adsystem.com/configs/e5a6f2d1-7642-4cc5-a917-96dbe8c3ed8f3600.0 s852 B
/components/throttle-refresh-component.de8e70e8b17a42bbf0...86400.0 s1.6 KiB
/components/activity-refresh-component.059097ebda70e7a178...86400.0 s1.6 KiB
/components/refresh-all-ads-component.db7de998acab3aec35b...86400.0 s1.5 KiB
/prod/1.19.14-y0ptsc/prebid-analytics.980e6134af0dbb700d9...604800.0 s5.5 KiB
/components/htl-traffic-shaping-component.05bf9326dea218a...86400.0 s1.1 KiB
/components/taboola-auto-tagId-component.d35311409295ad80...86400.0 s1.1 KiB
sb.scorecardresearch.com/p?c1=2&c2=6036441&cv=3.6.0&cj=10.0 ms300 B
cdn.indexww.com/ht/htw-pixel.gif?086400.0 s247 B
/hadron.js?url=https%3A%2F%2Fwww.yourdictionary.com%2F&re...432000.0 s186 B
c.amazon-adsystem.com/aax2/apstag.js3600.0 s0 B

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.

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: 457 ms
URLTime Spent
yourdictionary.com/250 ms
www.yourdictionary.com/207 ms
www.yourdictionary.com/0.0 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

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.

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: 80 ms 929.0 KiB
URLTransfer SizeEst Savings
/pagead/managed/js/gpt/m202604200101/pubads_impl.js?cb=31...187.7 KiB140.6 KiB
/prebid/9.30.0.js?fork=1&v=bf6611fc0393cee6578a23c9bb5689...138.0 KiB104.5 KiB
accounts.google.com/gsi/client85.5 KiB72.3 KiB
www.googletagmanager.com/gtag/js?id=G-TM1GJBSHNN&cx=c&gtm=4e64k0155.6 KiB67.5 KiB
/assets/smart-tag/versioned/main-v2_9e4958801741d4d875ab9...116.1 KiB64.7 KiB
www.googletagmanager.com/gtag/js?id=G-Q6LE3EEZ1W&cx=c&gtm=4e64k0152.1 KiB64.2 KiB
raven-static.aditude.io/prod/1.19.14-y0ptsc/raven.js106.8 KiB63.3 KiB
www.googletagmanager.com/gtm.js?id=GTM-NJ2D3KV136.6 KiB62.6 KiB
c.amazon-adsystem.com/aax2/apstag.js90.4 KiB53.6 KiB
c.amazon-adsystem.com/aax2/apstag.js90.4 KiB51.0 KiB
/lovetoknow-1r2kdxaraW/yourdictionary.com/prebid-wrapper.js87.7 KiB46.4 KiB
www.yourdictionary.com/_nuxt/commons/app.0abf6ef5773581f60ac7.js105.1 KiB43.6 KiB
www.yourdictionary.com/_nuxt/vendors/app.f4d8d9f25d320d0e5f9f.js107.8 KiB32.4 KiB
/assets/smart-tag/versioned/ads-v2_b767962dfef6270095d208...42.1 KiB31.6 KiB
www.yourdictionary.com/_nuxt/app.2ba3b02a996f825e8241.js74.0 KiB30.6 KiB

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 8.1 KiB
URLTransfer SizeEst Savings
/*! tailwindcss v2.2.19 | MIT License | https://tailwindcss.com*/ /*! modern-normalize v1.1.0 | MI…37.8 KiB8.1 KiB

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: 0.0 ms 12.7 KiB
URLTransfer SizeEst Savings
launchpad.privacymanager.io/latest/launchpad.bundle.js40.2 KiB12.7 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 36.9 KiB
URLTransfer SizeEst Savings
/*! tailwindcss v2.2.19 | MIT License | https://tailwindcss.com*/ /*! modern-normalize v1.1.0 | MI…37.6 KiB26.8 KiB
10.1 KiB10.1 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
●Improve image delivery
●LCP breakdown
●Modern HTTP
●Render blocking requests
●Optimize viewport for mobile
●Avoids enormous network payloads Total size was 2,641 KiB
●User Timing marks and measures 22 user timings
●JavaScript execution time 0.8 s
●Minimizes main-thread work 1.8 s
●Avoid long main-thread tasks 5 long tasks found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 100 ms
●Server Backend Latencies 290 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 0 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○LCP request discovery
○Avoid non-composited animations
93

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
section.source-attribution-wrapper > div.source-attribution > div.source-attribution__carrousel > button.source-attribution__control section.source-attribution-wrapper > div.source-attribution > div.source-attribution__carrousel > button.source-attribution__control
section.source-attribution-wrapper > div.source-attribution > div.source-attribution__carrousel > button.source-attribution__control section.source-attribution-wrapper > div.source-attribution > div.source-attribution__carrousel > button.source-attribution__control

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.wf-opensans-n4-inactive html.wf-opensans-n4-inactive

These items highlight common accessibility best practices.

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
Dictionary div.search-box-wrapper > div.search-box-container > div.filter-dropdown-container > button.filter-dropdown-button
○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
●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
●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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●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 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.
○Image elements have `[alt]` attributes
○Input buttons have discernible text.
○`<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.
○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.
77

Best Practices

Trust and Safety

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Insecure URLRequest Resolution
www.yourdictionary.com/Allowed

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
api.rlcdn.com/api/identity?pid=2&rt=envelope
Failed to load resource: the server responded with a status of 451 ()
●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 clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
92

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
Dictionary div.search-box-container > div.filter-dropdown-container > div.filter-dropdown > a.filter-dropdown-link
Thesaurus div.search-box-container > div.filter-dropdown-container > div.filter-dropdown > a.filter-dropdown-link
Sentences div.search-box-container > div.filter-dropdown-container > div.filter-dropdown > a.filter-dropdown-link
Articles div.search-box-container > div.filter-dropdown-container > div.filter-dropdown > a.filter-dropdown-link
Word Finder div.search-box-container > div.filter-dropdown-container > div.filter-dropdown > a.filter-dropdown-link

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
●robots.txt is valid
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`
○Image elements have `[alt]` attributes

Send Feedback