C — https://aeon.co | BeaverCheck Audit

Site Health

Score: 74 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Rich content metadata — your pages look great everywhere.

Reasonable footprint with room for optimization.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Amazon Route 53 · 970 peers

You 74

Avg 72

At average

0 50 100

Better than 64% of Amazon Route 53 sites See full Amazon Route 53 benchmark →

Bulma · 343 peers

You 74

Avg 74

At average

0 50 100

Better than 48% of Bulma sites See full Bulma benchmark →

Top Priorities (5)

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

HSTS header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy

1 link(s) with no accessible text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality

14 third-party resources (44% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Faeon.co)](https://beavercheck.com/results/98048be4-fc89-4230-8bc3-f7d385a3e806)

HTML

<a href="https://beavercheck.com/results/98048be4-fc89-4230-8bc3-f7d385a3e806"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Faeon.co" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Faeon.co

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 9.3s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.

1 accessibility issue excludes users who rely on assistive technology.

Your LCP is 9.3s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.

Conversion Barriers

3 critical 4 warning

7 barrier(s) likely increasing bounce by ~30%.

Speed (2)

Page takes 9.3s to load

+12% bounce

Users abandon at ~3s — you're 6.8s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Page feels frozen for 984ms

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (2)

No HSTS header

+1% bounce

Returning 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% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Content (1)

Content is hard to read

+2% bounce

Graduate-level reading difficulty — limits the addressable audience for product or blog pages

Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60

Navigation (2)

No skip-to-content link

+1% bounce

Keyboard 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

76 broken link(s) on the page

+5% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

$500 investment → $6,341/month returns + USD 157,500 risk avoided

Payback period: < 1 month First-year ROI: +15118%

Investment

$500

5h · 5 findings

Monthly returns

$6,341 /mo

~$76,088 / year

Conversions recovered $6,340
Bandwidth savings $0.54

Regulatory risk avoided

USD 157,500

if kept compliant

ADA Title III USD 150,000
CCPA/CPRA USD 7,500

Payback period

0 12mo 24mo

$150 — in quick wins — start here for the fastest payback

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.

Full methodology & sources

Estimated Remediation Cost

$500

5.0 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins

$150 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$13,126 / month at risk

~$157,506 / year if left unfixed

Compliance Risk

$157,500

ADA Title IIICCPA/CPRA

No privacy policy link detected
CCPA/CPRA: USD 2,500 – USD 7,500
Trackers detected but no cookie policy found
CCPA/CPRA: USD 2,500 – USD 7,500
Trackers detected but no privacy policy found
CCPA/CPRA: USD 2,500 – USD 7,500

+2 more

Bandwidth Waste

$0.54 /mo

6753.9 MB/mo × 0.080 USD/GB

Optimize transfer: save ~675 KB per page load
Saves $0.54/mo

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.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue

Current bounce (est.)

After fixes (est.)

Estimated bounce reduction

Fix 4 critical issues to capture this value

How this is calculated

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

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

Best Practices

100

SEO

Core Web Vitals

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.24 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

9.27 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

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

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

13.47 s

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

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.

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

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
Coloured microscopic image of mitochondria in a cell with red structures and bl… `a > div.group/card > div.relative > img.object-cover`	/images/52781036-d695-4c84-b620-0b1c4ef9ed74/essay-c06266...	148.3 KiB	97.0 KiB
Photo of a Gothic cathedral interior with colourful stained glass windows and o… `a > div.group/card > div.relative > img.object-cover`	/images/5612be05-ab10-41e7-bfe8-ea974c72f6f5/the-engineer...	103.9 KiB	52.6 KiB
Aerial photo of a desert village with round huts, winding paths and sparse gree… `a > div.group/card > div.relative > img.object-cover`	/images/a52748cf-7e1e-40af-bc92-3ff558b1647d/essay-panos_...	101.7 KiB	50.4 KiB
Abstract painting of a man’s face with collage elements, flowers and mathematic… `a > div.group/card > div.relative > img.object-cover`	/images/f3c246ed-c17b-4e4a-b1b3-5fa460429731/tweak-essay-...	93.0 KiB	41.7 KiB
Street photo of people walking past shopfronts with signs, one partially obscur… `a > div.group/card > div.relative > img.object-cover`	/images/3b1f56af-c076-451b-9446-995a44341a19/essay-nyc827...	61.1 KiB	9.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.

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

value: no origins were preconnected

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

value: No additional origins are good candidates for preconnecting

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
aeon.co/_next/static/chunks/0983gr2k_kuan.css	23.0 KiB	150 ms
aeon.co/_next/static/chunks/0nny2nqybhu93.css	600 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.

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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

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

Estimated savings: 300 ms 220.3 KiB

URL	Transfer Size	Est Savings
aeon.co/_next/static/chunks/0_v8f1g7.92mg.js	169.6 KiB	68.5 KiB
/gtag/js?id=G-R4TJTKRVYG&cx=c&gtm=4e64k0&sign=e3781219faf...	171.9 KiB	68.3 KiB
analytics.aeon.co/gtm.js?id=GTM-MHVZTPR	130.2 KiB	61.7 KiB
aeon.co/_next/static/chunks/10_t3scxt3gpu.js	24.8 KiB	21.9 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
aeon.co/_next/static/chunks/0_v8f1g7.92mg.js	2.4 s	2.1 s	75 ms
Unattributable	801 ms	92 ms	0.0 ms
aeon.co/	652 ms	19 ms	15 ms
/gtag/js?id=G-R4TJTKRVYG&cx=c&gtm=4e64k0&sign=e3781219faf...	475 ms	409 ms	55 ms
analytics.aeon.co/gtm.js?id=GTM-MHVZTPR	266 ms	219 ms	40 ms
aeon.co/_next/static/chunks/133qnazah~2eg.js	223 ms	144 ms	15 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	3.0 s
Other	886 ms
Style & Layout	551 ms
Script Parsing & Compilation	324 ms
Rendering	78 ms
Parse HTML & CSS	72 ms
Garbage Collection	34 ms

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

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 2,199 KiB

●User Timing marks and measures 6 user timings

●Avoid long main-thread tasks 12 long tasks found

●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 40 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 0 ms

○INP breakdown

○Avoid non-composited animations

○Avoid large layout shifts

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.mx-auto > div.flex > div.flex > button.hover:opacity-70 `div.mx-auto > div.flex > div.flex > button.hover:opacity-70`

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.space-y-1 > label.flex > label.flex > input#_r_3_ `div.space-y-1 > label.flex > label.flex > input#_r_3_`
div.space-y-1 > label.flex > label.flex > input#_r_4_ `div.space-y-1 > label.flex > label.flex > input#_r_4_`

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

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`

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

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

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

●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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●No form fields have multiple labels

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○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

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

○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

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

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

Best Practices

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.

Source Description

Source	Description
aeon.co/_next/static/chunks/0_v8f1g7.92mg.js line 20, col 92746	Error: Minified React error #418; visit https://react.dev/errors/418?args[]=HTML&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at rX (https://aeon.co/_next/static/chunks/0_v8f1g7.92mg.js:21:92747) at lu (https://aeon.co/_next/static/chunks/0_v8f1g7.92mg.js:21:143788) at uf (https://aeon.co/_next/static/chunks/0_v8f1g7.92mg.js:21:184478) at https://aeon.co/_next/static/chunks/0_v8f1g7.92mg.js:21:179364 at ue (https://aeon.co/_next/static/chunks/0_v8f1g7.92mg.js:21:179465) at uW (https://aeon.co/_next/static/chunks/0_v8f1g7.92mg.js:21:206029) at MessagePort.N (https://aeon.co/_next/static/chunks/0_v8f1g7.92mg.js:21:54187)

aeon.co/_next/static/chunks/0_v8f1g7.92mg.js line 20, col 92746

Error: Minified React error #418; visit https://react.dev/errors/418?args[]=HTML&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at rX (https://aeon.co/_next/static/chunks/0_v8f1g7.92mg.js:21:92747)
    at lu (https://aeon.co/_next/static/chunks/0_v8f1g7.92mg.js:21:143788)
    at uf (https://aeon.co/_next/static/chunks/0_v8f1g7.92mg.js:21:184478)
    at https://aeon.co/_next/static/chunks/0_v8f1g7.92mg.js:21:179364
    at ue (https://aeon.co/_next/static/chunks/0_v8f1g7.92mg.js:21:179465)
    at uW (https://aeon.co/_next/static/chunks/0_v8f1g7.92mg.js:21:206029)
    at MessagePort.N (https://aeon.co/_next/static/chunks/0_v8f1g7.92mg.js:21:54187)

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
/gtag/js?id=G-R4TJTKRVYG&cx=c&gtm=4e64k0&sign=e3781219faf...
aeon.co/_next/static/chunks/0_v8f1g7.92mg.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 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

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`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

Best Practices

100

SEO

Core Web Vitals

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.

351 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

2.38 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

167 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.33 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.27 s

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.

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:29.792 source:map[column:53948 line:21 type:source-location url:https://aeon.co/_next/static/chunks/0_v8f1g7.92mg.js urlProvider:network]]]

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:59.947 source:map[type:text value:[unattributed]]] map[reflowTime:29.792 source:map[column:9586 line:1 type:source-location url:https://aeon.co/_next/static/chunks/12xvhgcjdi.20.js urlProvider:network]] map[reflowTime:0.763 source:map[column:53687 line:19 type:source-location url:https://aeon.co/_next/static/chunks/0_v8f1g7.92mg.js urlProvider:network]]]

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
Aerial photo of a desert village with round huts, winding paths and sparse gree… `div.relative > div.relative > div.relative > img`	/featuredimages/5c208ccc-4723-41dd-ac08-4ad43c75ee55/home...	358.8 KiB	240.2 KiB
Coloured microscopic image of mitochondria in a cell with red structures and bl… `a > div.group/card > div.relative > img.object-cover`	/images/52781036-d695-4c84-b620-0b1c4ef9ed74/essay-c06266...	110.6 KiB	93.0 KiB
A modern house built over a waterfall surrounded by lush green forest, with sto… `a > div.group/card > div.relative > img.object-cover`	/images/38ec910f-8938-4496-8861-3bbaf9420bd1/essay-master...	86.3 KiB	68.7 KiB
Photo of a Gothic cathedral interior with colourful stained glass windows and o… `a > div.group/card > div.relative > img.object-cover`	/images/5612be05-ab10-41e7-bfe8-ea974c72f6f5/the-engineer...	75.6 KiB	60.8 KiB
Abstract painting of a man’s face with collage elements, flowers and mathematic… `a > div.group/card > div.relative > img.object-cover`	/images/f3c246ed-c17b-4e4a-b1b3-5fa460429731/tweak-essay-...	69.3 KiB	51.7 KiB
A bustling chemist shop in Kolkata, India, with customers and shelves stocked w… `a > div.group/card > div.relative > img.object-cover`	/images/38b746ba-acd6-491d-a703-e5ef462fa082/panos_002467...	57.0 KiB	39.5 KiB
3D model of an historic city map with detailed buildings, rivers and greenery. `a > div.group/card > div.relative > img.object-cover`	/images/26fb7e41-d6b7-4cd6-8858-6fe968314f1d/evolution-of...	54.1 KiB	39.3 KiB
Street photo of people walking past shopfronts with signs, one partially obscur… `a > div.group/card > div.relative > img.object-cover`	/images/3b1f56af-c076-451b-9446-995a44341a19/essay-nyc827...	45.3 KiB	28.8 KiB
Children interacting with a giraffe from a car window and skylight in a park se… `a > div.group/card > div.relative > img.object-cover`	/images/aaa3e45d-40b6-4dee-a51c-3956d13b481b/essay-lon486...	41.3 KiB	23.7 KiB
Three paintings of a young musician with a lute sheet music and a violin. `a > div.group/card > div.relative > img.object-cover`	/images/d655235b-0cce-49cc-aa13-8628f4b97717/essay-peters...	36.9 KiB	19.5 KiB
Painting of swimmers on starting blocks at a pool, crowd in background, vibrant… `a > div.group/card > div.relative > img.object-cover`	/images/42bf9a4b-d0d7-4eac-b18e-4e3e360c98d9/butterfly-pa...	29.8 KiB	18.0 KiB
Photo of a town with houses and buildings, surrounded by mountains under a clou… `a > div.group/card > div.relative > img.object-cover`	/images/fd8c5f87-b2da-4dd1-98af-d109b8c932f2/your-opinion...	29.1 KiB	17.6 KiB
Illustration of a hand using shears to prune a tree with vibrant green branches… `a > div.group/card > div.relative > img.object-cover`	/images/17da9ab8-7dd6-4f2f-b2b0-c49899fdce9c/v2-essay-str...	32.4 KiB	17.2 KiB
A young boy in a car’s front seat with adults in the other seats on a dusty roa… `a > div.group/card > div.relative > img.object-cover`	/images/f2d8fe96-4646-4174-aeb5-eec1b2e53666/essay-panos_...	31.3 KiB	16.6 KiB
Illustration of figures in kimonos with colourful patterns and red sashes on a … `a > div.group/card > div.relative > img.object-cover`	/images/5834a208-4335-4ce2-926e-078aed2f9130/impromptu-la...	25.2 KiB	15.2 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.

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.

title: Preconnected origins

value: no origins were preconnected

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

value: No additional origins are good candidates for preconnecting

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
aeon.co/_next/static/chunks/0983gr2k_kuan.css	23.1 KiB
aeon.co/_next/static/chunks/0nny2nqybhu93.css	625 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.

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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

Source: Google web.dev / Lighthouse

Estimated savings: 40 ms 239.8 KiB

URL	Transfer Size	Est Savings
aeon.co/_next/static/chunks/0_v8f1g7.92mg.js	169.6 KiB	68.5 KiB
/gtag/js?id=G-R4TJTKRVYG&cx=c&gtm=4e64k0&sign=cd22cc3cbf1...	171.9 KiB	67.2 KiB
analytics.aeon.co/gtm.js?id=GTM-MHVZTPR	130.2 KiB	60.2 KiB
aeon.co/_next/static/chunks/0tei0hr6ltgqv.js	22.2 KiB	22.1 KiB
aeon.co/_next/static/chunks/10_t3scxt3gpu.js	24.8 KiB	21.9 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
/featuredimages/5c208ccc-4723-41dd-ac08-4ad43c75ee55/home...	359.3 KiB
/gtag/js?id=G-R4TJTKRVYG&cx=c&gtm=4e64k0&sign=cd22cc3cbf1...	172.0 KiB
aeon.co/_next/static/chunks/0_v8f1g7.92mg.js	169.8 KiB
analytics.aeon.co/gtm.js?id=GTM-MHVZTPR	130.3 KiB
/images/52781036-d695-4c84-b620-0b1c4ef9ed74/essay-c06266...	111.0 KiB
/images/38ec910f-8938-4496-8861-3bbaf9420bd1/essay-master...	86.7 KiB
/images/5612be05-ab10-41e7-bfe8-ea974c72f6f5/the-engineer...	76.0 KiB
/images/f3c246ed-c17b-4e4a-b1b3-5fa460429731/tweak-essay-...	69.7 KiB
assets.aeonmedia.co/dynamic_image/f3b0ff06-f819-48d8-9775-2df7a8f671bc/240.mp4	59.2 KiB
/images/38b746ba-acd6-491d-a703-e5ef462fa082/panos_002467...	57.4 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

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●User Timing marks and measures 8 user timings

●JavaScript execution time 1.0 s

●Minimizes main-thread work 1.5 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 20 ms

●Server Backend Latencies 30 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 10 ms

○INP breakdown

○Avoid non-composited animations

○Avoid large layout shifts

Accessibility

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.space-y-1 > label.flex > label.flex > input#_r_3_ `div.space-y-1 > label.flex > label.flex > input#_r_3_`
div.space-y-1 > label.flex > label.flex > input#_r_4_ `div.space-y-1 > label.flex > label.flex > input#_r_4_`

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
body.flex > main.flex-1 > div.relative > a.absolute `body.flex > main.flex-1 > div.relative > a.absolute`

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

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`
Save `div.group/card > div.relative > div.flex > button.group`

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

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

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

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

●Buttons have an accessible name

●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

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●No form fields have multiple labels

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○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

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

○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

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

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

Best Practices

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.

Source Description

Source	Description
aeon.co/_next/static/chunks/0_v8f1g7.92mg.js line 20, col 92746	Error: Minified React error #418; visit https://react.dev/errors/418?args[]=HTML&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at rX (https://aeon.co/_next/static/chunks/0_v8f1g7.92mg.js:21:92747) at lu (https://aeon.co/_next/static/chunks/0_v8f1g7.92mg.js:21:143788) at uf (https://aeon.co/_next/static/chunks/0_v8f1g7.92mg.js:21:184478) at https://aeon.co/_next/static/chunks/0_v8f1g7.92mg.js:21:179364 at ue (https://aeon.co/_next/static/chunks/0_v8f1g7.92mg.js:21:179465) at uW (https://aeon.co/_next/static/chunks/0_v8f1g7.92mg.js:21:206029) at MessagePort.N (https://aeon.co/_next/static/chunks/0_v8f1g7.92mg.js:21:54187)

aeon.co/_next/static/chunks/0_v8f1g7.92mg.js line 20, col 92746

Error: Minified React error #418; visit https://react.dev/errors/418?args[]=HTML&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at rX (https://aeon.co/_next/static/chunks/0_v8f1g7.92mg.js:21:92747)
    at lu (https://aeon.co/_next/static/chunks/0_v8f1g7.92mg.js:21:143788)
    at uf (https://aeon.co/_next/static/chunks/0_v8f1g7.92mg.js:21:184478)
    at https://aeon.co/_next/static/chunks/0_v8f1g7.92mg.js:21:179364
    at ue (https://aeon.co/_next/static/chunks/0_v8f1g7.92mg.js:21:179465)
    at uW (https://aeon.co/_next/static/chunks/0_v8f1g7.92mg.js:21:206029)
    at MessagePort.N (https://aeon.co/_next/static/chunks/0_v8f1g7.92mg.js:21:54187)

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
/gtag/js?id=G-R4TJTKRVYG&cx=c&gtm=4e64k0&sign=cd22cc3cbf1...
aeon.co/_next/static/chunks/0_v8f1g7.92mg.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 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

100

SEO

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

Results for https://aeon.co

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Speed (2)

Trust (2)

Content (1)

Navigation (2)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Payback period

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Names and labels

Best practices

Best Practices

General

SEO

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Names and labels

Best practices

Best Practices

General

SEO

Keyboard Shortcuts