Brazil · Sao Paulo Completed: Apr 21, 2026 22:58 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 79 / 100
Based on 8 categories, 0 sections
Fast site — your users get a smooth experience.
Good foundation, but a few gaps could be exploited.
Several issues make your site difficult for assistive technology users.
Well-optimized for search — your content is discoverable.
Good server performance with room for optimization.
Mostly compliant — a few items need attention.
Good content signals with minor gaps.
Lean and efficient — low environmental impact per visit.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
1 button(s) with no accessible text
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
2 control(s) without accessible label
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
No <main> landmark found
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
No H1 heading found
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
8 third-party resources (78% of weight)
Performance issues directly impact user engagement and conversion rates.
High impact, low effort — start here.
Nothing in this quadrant — good news.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/ddfed7ea-7714-4d82-a49d-c2f8406c3312)<a href="https://beavercheck.com/results/ddfed7ea-7714-4d82-a49d-c2f8406c3312"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwordreference.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fwordreference.comThis badge auto-updates with your latest scan result.
Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your server takes 661ms to respond — every other performance metric inherits that delay. Addressing the critical issues below would have the most immediate impact on your audience reach.
6 barrier(s) likely increasing bounce by ~15%.
No HSTS header
+1% bounceReturning visitors are briefly exposed to downgrade attacks on first request
Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains
No Content-Security-Policy header
+1% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
2 form field(s) without a label
+4% bounceScreen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes
Fix: Associate every input with a visible <label for="…">; add autocomplete attributes
Viewport disables user zoom
+2% bounceVisitors with low vision can't read the page — and some jurisdictions treat this as a legal risk
Fix: Remove user-scalable=no; drop maximum-scale if it's below 2
No Open Graph tags
+2% bounceLinks shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop
Fix: Add og:title, og:description, og:image, og:url to the page head
No skip-to-content link
+1% bounceKeyboard and screen-reader users must tab through the entire header on every page
Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
€720 investment → €0.05/month returns + EUR 120,500,000 risk avoided
€720
8h · 5 findings
€0.05 /mo
~€0.65 / year
EUR 120,500,000
if kept compliant
Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.
8.0 developer hours at €90/hr
Based on Germany rates (€90/hr)
€10,041,667 / month at risk
~€120,500,001 / year if left unfixed
€120,500,000
+7 more
€0.05 /mo
729.4 MB/mo × 0.074 EUR/GB
Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 4 critical issues to capture this value
Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.
Your site's LCP: → estimated after fixes.
These are estimates based on industry research — actual results vary
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
Key metrics that affect user experience.
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
1.11 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.11 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
190 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.85 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
3.28 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| wordreference.com/css/homepagebundle.min.css | 6.4 KiB | 355 ms |
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| wordreference.com/js/homepagebundle.min.js | 86400.0 s | 22.0 KiB |
| wordreference.com/css/homepagebundle.min.css | 86400.0 s | 6.4 KiB |
| www.wordreference.com/home/HomepageIP2CC | 0.0 ms | 554 B |
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.
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.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.googletagmanager.com/gtag/js?id=G-WV46ZWEMKW | 170.5 KiB | 66.9 KiB |
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
.com body > div#container > div#content > span.dotcom |
Español div#container > div#content > div.links > a |
Français div#container > div#content > div.links > a |
Italiano div#container > div#content > div.links > a |
Português div#container > div#content > div.links > a |
Català div#container > div#content > div.links > a |
Deutsch div#container > div#content > div.links > a |
Svenska div#container > div#content > div.links > a |
Nederlands div#container > div#content > div.links > a |
Русский div#container > div#content > div.links > a |
Polski div#container > div#content > div.links > a |
Română div#container > div#content > div.links > a |
Čeština div#container > div#content > div.links > a |
Ελληνικά div#container > div#content > div.links > a |
Türkçe div#container > div#content > div.links > a |
英汉词典 div#container > div#content > div.links > a |
英和辞書 div#container > div#content > div.links > a |
영-한 사전 div#container > div#content > div.links > a |
قاموس إنجليزي - عربي div#container > div#content > div.links > a |
Virtual dictionaries for non-English language pairs div#container > div#content > div.links > a |
These are opportunities to improve the legibility of your content.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div#container > div#content > form#text_form > input.submit-button div#container > div#content > form#text_form > input.submit-button |
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
English-Spanish
Spanish-English
Spanish-French
Spanish-Portuguese
Spanish-Itali… div#content > form#text_form > label.custom-select > select#fSelect |
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.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
head > meta head > meta |
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These items highlight common accessibility best practices.
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.
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
Performance issues directly impact user engagement and conversion rates.
| Uncrawlable Link |
|---|
Light body > div#container > div.footer-theme-button > a.toggle-button |
To appear in search results, crawlers need access to your app.
Industry-standard audits powered by Google Lighthouse. — Desktop
Key metrics that affect user experience. — Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
447 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
447 ms
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
0 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
770 ms
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
447 ms
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| wordreference.com/css/homepagebundle.min.css | 6.4 KiB | 244 ms |
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| wordreference.com/js/homepagebundle.min.js | 86400.0 s | 22.0 KiB |
| wordreference.com/css/homepagebundle.min.css | 86400.0 s | 6.4 KiB |
| www.wordreference.com/home/HomepageIP2CC | 0.0 ms | 554 B |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.googletagmanager.com/gtag/js?id=G-WV46ZWEMKW | 170.5 KiB | 66.9 KiB |
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
.com body > div#container > div#content > span.dotcom |
Español div#container > div#content > div.links > a |
Français div#container > div#content > div.links > a |
Italiano div#container > div#content > div.links > a |
Português div#container > div#content > div.links > a |
Català div#container > div#content > div.links > a |
Deutsch div#container > div#content > div.links > a |
Svenska div#container > div#content > div.links > a |
Nederlands div#container > div#content > div.links > a |
Русский div#container > div#content > div.links > a |
Polski div#container > div#content > div.links > a |
Română div#container > div#content > div.links > a |
Čeština div#container > div#content > div.links > a |
Ελληνικά div#container > div#content > div.links > a |
Türkçe div#container > div#content > div.links > a |
英汉词典 div#container > div#content > div.links > a |
英和辞書 div#container > div#content > div.links > a |
영-한 사전 div#container > div#content > div.links > a |
قاموس إنجليزي - عربي div#container > div#content > div.links > a |
Virtual dictionaries for non-English language pairs div#container > div#content > div.links > a |
There are two free Spanish-English dictionaries: our own dictionary and one fro… div#content > div.info > div#infoone > p |
WordReference has two of its own dictionaries plus those of Collins. The French… div#content > div.info > div#infotwo > p |
The WordReference language forum is the largest repository of knowledge and adv… div#content > div.info > div#infothree > p |
These are opportunities to improve the legibility of your content.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div#container > div#content > form#text_form > input.submit-button div#container > div#content > form#text_form > input.submit-button |
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
English-Spanish
Spanish-English
Spanish-French
Spanish-Portuguese
Spanish-Itali… div#content > form#text_form > label.custom-select > select#fSelect |
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.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
head > meta head > meta |
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These items highlight common accessibility best practices.
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.
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
Performance issues directly impact user engagement and conversion rates.
| Uncrawlable Link |
|---|
Light body > div#container > div.footer-theme-button > a.toggle-button |
To appear in search results, crawlers need access to your app.
Send Feedback