C — https://hackernoon.com | BeaverCheck Audit

Site Health

Score: 76 / 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

Facebook sites average 72

At average

Better than 81% of Facebook sites See full Facebook benchmark →

Goober sites average 71

At average

Better than 83% of Goober sites See full Goober benchmark →

Top Priorities (5)

Content-Security-Policy 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

27 link(s) with no accessible text

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

Accessibility › Link & Button Quality

7 button(s) with no accessible text

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

Accessibility › Link & Button Quality

No H1 heading found

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

Accessibility › Heading Hierarchy

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%2Fhackernoon.com)](https://beavercheck.com/results/89d79504-91da-4826-adbc-88a873f0313a)

HTML

<a href="https://beavercheck.com/results/89d79504-91da-4826-adbc-88a873f0313a"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fhackernoon.com" alt="BeaverCheck Score"></a>

Image URL

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

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. Addressing the critical issues below would have the most immediate impact on your user trust.

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

3 accessibility issues exclude users who rely on assistive technology.

Could reach Estimate based on resolving critical issues

Return on Investment

€468 investment → €1,762/month returns + EUR 120,500,000 risk avoided

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

Investment

€468

6h · 5 findings

Monthly returns

€1,762 /mo

~€21,142 / year

Conversions recovered €1,761
Bandwidth savings €0.61

Regulatory risk avoided

EUR 120,500,000

if kept compliant

ePrivacy Directive EUR 100,000,000
GDPR EUR 20,000,000
EAA EUR 500,000

Payback period

0 12mo 24mo

€85 — 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

€468

5.5 developer hours at €85/hr

Based on European Union rates (€85/hr)

Quick wins

€85 2 fixes in ~60 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

€10,041,667 / month at risk

~€120,500,007 / year if left unfixed

Compliance Risk

€120,500,000

ePrivacy DirectiveGDPREAA

No privacy policy link detected
GDPR: EUR 10,000 – EUR 20,000,000
Trackers detected but no cookie policy found
GDPR: EUR 5,000 – EUR 10,000,000
Trackers detected but no cookie policy found
GDPR: EUR 10,000 – EUR 20,000,000

+4 more

Bandwidth Waste

€0.61 /mo

8291.0 MB/mo × 0.074 EUR/GB

Optimize transfer: save ~829 KB per page load
Saves €0.61/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 5 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.49 s

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

12.97 s

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

1000 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.002

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

4.95 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.89 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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:10.973 source:map[column:3910 line:1 type:source-location url:https://hackernoon.com/_next/static/chunks/3082-aee0a240f1adbc5a.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:34.254 source:map[column:4083 line:0 type:source-location url:https://hackernoon.com/_next/static/chunks/3082-aee0a240f1adbc5a.js urlProvider:network]] map[reflowTime:17.961 source:map[column:3454 line:0 type:source-location url:https://hackernoon.com/_next/static/chunks/pages/index-0c7e6dbc5623fed3.js urlProvider:network]]]

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-ARTICLE

nodeLabel: AI Memory Systems: The Approaches You Need to Know by Tom Bedor Apr 15, 2026 …

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

selector: div.bg-dark > div.carousel > div.carousel-item > article.group

snippet: <article class="group relative w-full h-[300px] sm:h-[400px] overflow-hidden bg-cover bg-c…" style="background-image: url("https://hackernoon.imgix.net/images/ai-memory-abstr…");">

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

value: No additional origins are good candidates for preconnecting

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.

Request	Cache TTL	Transfer Size
cdn2.hackernoon.com/HackerNoonV2-Regular.woff2	14400.0 s	11.0 KiB
cs.iubenda.com/cookie-solution/confs/js/18778700.js	3600.0 s	1.6 KiB

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
hackernoon.com/_next/static/media/iconfont.8480cc91.woff2	20 ms

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
caveman newsletter `div.max-w-[1400px] > div.flex > div.flex > img`	hackernoon.com/images/caveman.gif	146.0 KiB	143.2 KiB
/how-deepgram-and-modulate-benchmark-against-real-world-audio feature image `div.flex > a.flex > span > img.h-full`	/images/RefDnRaKIEfhPjE5HUK7SNjGEZg1-u103bj0.jpeg?auto=fo...	62.3 KiB	49.3 KiB
AI Coding Tip 015 - Force the AI to Obey You by Maxi Contieri Apr 14, 2026 · … `div.bg-dark > div.carousel > div.carousel-item > article.group`	hackernoon.imgix.net/images/RIiBoPtpMiRsMKX3dnzl5gb1Urj1-wj838tc.png	108.6 KiB	15.5 KiB

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

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 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: 500 ms 52.7 KiB

URL	Transfer Size	Est Savings
hackernoon.com/_next/static/css/21f88a768b9f42d6.css	49.0 KiB	42.6 KiB
	11.6 KiB	10.1 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

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: 4.3 s 1.6 MiB

URL	Transfer Size	Est Savings
hackernoon.com/_next/static/chunks/3197-5551de4d59578971.js	1.1 MiB	602.2 KiB
hackernoon.com/_next/static/chunks/3392295e-d6a14435d0e6cc1f.js	105.5 KiB	96.1 KiB
hackernoon.com/_next/static/chunks/1606726a-a5554f21a86069ef.js	83.3 KiB	75.7 KiB
accounts.google.com/gsi/client	95.4 KiB	71.8 KiB
www.googletagmanager.com/gtag/js?id=G-ECJJ2Q2SJQ	173.0 KiB	65.5 KiB
hackernoon.com/_next/static/chunks/e4405247-b92cad2245dc32a9.js	105.8 KiB	60.3 KiB
hackernoon.com/_next/static/chunks/484bcb1e-a74d55912652d457.js	66.2 KiB	58.6 KiB
hackernoon.com/_next/static/chunks/pages/c/%5Bcategory%5D-688600f31a5fb52c.js	66.2 KiB	58.4 KiB
cdn.iubenda.com/cookie_solution/iubenda_cs/1.98.0/core-en.js	110.1 KiB	54.9 KiB
hackernoon.com/_next/static/chunks/ee759108-51af8ccea7c8c9cb.js	77.5 KiB	54.6 KiB
hackernoon.com/_next/static/chunks/29107295-4a69275373f23f88.js	70.0 KiB	50.4 KiB
hackernoon.com/_next/static/chunks/4804-0be234a5b629b212.js	49.1 KiB	43.6 KiB
hackernoon.com/_next/static/chunks/8840-a83404e2e4af8c4a.js	46.3 KiB	42.5 KiB
hackernoon.com/_next/static/chunks/b3e8167d-b2aa66c4b942030a.js	48.1 KiB	39.9 KiB
hackernoon.com/_next/static/chunks/52066749-b7c60fb5a3cb081d.js	56.2 KiB	37.9 KiB
hackernoon.com/_next/static/chunks/pages/_app-715058edf9331717.js	64.7 KiB	35.3 KiB
hackernoon.com/_next/static/chunks/3785-309c253d4be151fd.js	183.9 KiB	35.2 KiB
hackernoon.com/_next/static/chunks/9802-c314c25e99adc644.js	55.1 KiB	35.1 KiB
hackernoon.com/_next/static/chunks/431-44e3001b0878358b.js	35.5 KiB	32.9 KiB
hackernoon.com/_next/static/chunks/969-887dd8f5ec269b49.js	37.7 KiB	28.5 KiB
hackernoon.com/_next/static/chunks/807-3cf1f14373e3bbf3.js	28.3 KiB	20.4 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
hackernoon.com/	800 ms	26 ms	2.4 ms
hackernoon.com/_next/static/chunks/pages/index-0c7e6dbc5623fed3.js	688 ms	466 ms	2.5 ms
Unattributable	553 ms	83 ms	0.0 ms
hackernoon.com/_next/static/chunks/3197-5551de4d59578971.js	371 ms	259 ms	111 ms
www.googletagmanager.com/gtag/js?id=G-ECJJ2Q2SJQ	305 ms	256 ms	46 ms
cdn.iubenda.com/cookie_solution/iubenda_cs/1.98.0/core-en.js	276 ms	172 ms	55 ms
hackernoon.com/_next/static/chunks/52066749-b7c60fb5a3cb081d.js	245 ms	221 ms	16 ms
hackernoon.com/_next/static/chunks/framework-79bce4a3a540b080.js	244 ms	100 ms	9.1 ms
hackernoon.com/_next/static/chunks/3768.af7c75292f9a548f.js	219 ms	143 ms	1.0 ms
hackernoon.com/_next/static/chunks/1274-8082537aae8a025b.js	210 ms	106 ms	7.8 ms
hackernoon.com/_next/static/chunks/pages/_app-715058edf9331717.js	165 ms	135 ms	19 ms
hackernoon.com/_next/static/q8NSk-fxsCneHvN_q8tML/_buildManifest.js	122 ms	119 ms	2.2 ms
hackernoon.com/_next/static/chunks/main-87ffee5d2ac3498b.js	103 ms	82 ms	8.5 ms
hackernoon.com/_next/static/chunks/8848.0408c1f2b4f7e7af.js	83 ms	74 ms	1.2 ms
/_next/static/chunks/pages/p/[pageSlug]/[subPageSlug]-979...	78 ms	77 ms	0.5 ms
hackernoon.com/_next/static/chunks/webpack-022ff6fd855ac40e.js	67 ms	63 ms	0.7 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	2.5 s
Other	901 ms
Style & Layout	804 ms
Script Parsing & Compilation	594 ms
Rendering	123 ms
Parse HTML & CSS	65 ms
Garbage Collection	34 ms

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
hackernoon.com/_next/static/chunks/3197-5551de4d59578971.js	284.6 KiB
www.googletagmanager.com/gtag/js?id=G-ECJJ2Q2SJQ	173.3 KiB
hackernoon.com/images/caveman.gif	146.8 KiB
cdn.iubenda.com/cookie_solution/iubenda_cs/1.98.0/core-en.js	110.7 KiB
hackernoon.imgix.net/images/RIiBoPtpMiRsMKX3dnzl5gb1Urj1-wj838tc.png	108.9 KiB
accounts.google.com/gsi/client	96.2 KiB
hackernoon.imgix.net/images/ai-memory-abstract-c2nxjpcqrda57ev09thk3azu.png	72.0 KiB
hackernoon.com/_next/static/chunks/484bcb1e-a74d55912652d457.js	66.7 KiB
hackernoon.com/_next/static/chunks/pages/_app-715058edf9331717.js	65.1 KiB
/images/RefDnRaKIEfhPjE5HUK7SNjGEZg1-u103bj0.jpeg?auto=fo...	62.6 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
caveman newsletter `div.max-w-[1400px] > div.flex > div.flex > img`	hackernoon.com/images/caveman.gif

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Layout shift culprits

●Document request latency

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 16 user timings

●Avoid long main-thread tasks 19 long tasks found

●Avoid non-composited animations 12 animated elements found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 40 ms

●Server Backend Latencies 120 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 40 ms

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

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
header.font-[ibm-plex-sans] > div.flex > div.navbar-end > button.btn `header.font-[ibm-plex-sans] > div.flex > div.navbar-end > button.btn`
header.font-[ibm-plex-sans] > div.flex > div.navbar-end > button.flex `header.font-[ibm-plex-sans] > div.flex > div.navbar-end > button.flex`
div.transition-all > div.z-20 > div.lg:hidden > button.bg-dark `div.transition-all > div.z-20 > div.lg:hidden > button.bg-dark`
div > div#trending > div.:hidden > button.hover:text-lightAccent `div > div#trending > div.:hidden > button.hover:text-lightAccent`
div > div#trending > div.:hidden > button.hover:text-lightAccent `div > div#trending > div.:hidden > button.hover:text-lightAccent`
section#about > div > div.grid > button.px-2 `section#about > div > div.grid > button.px-2`
section#about > div > div.grid > button.px-2 `section#about > div > div.grid > button.px-2`
section#about > div > div.grid > button.px-2 `section#about > div > div.grid > button.px-2`

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`

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
Go to slide 1 `div.lg:hidden > div.bg-dark > div.flex > button.w-3`
Go to slide 2 `div.lg:hidden > div.bg-dark > div.flex > button.w-3`
Go to slide 3 `div.lg:hidden > div.bg-dark > div.flex > button.w-3`
Go to slide 4 `div.lg:hidden > div.bg-dark > div.flex > button.w-3`
Go to slide 5 `div.lg:hidden > div.bg-dark > div.flex > button.w-3`

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

●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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

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

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

●No element has a `[tabindex]` value greater than 0

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

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

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

○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

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
Maxi Contieri `div.flex > div.flex > span > img.rounded-full`	/images/RIiBoPtpMiRsMKX3dnzl5gb1Urj1-w68367c.jpeg?auto=fo...	35 x 35 (1.00)	96 x 64 (1.50)

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
hackernoon.com/	`Not signed in with the identity provider.`

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
hackernoon.com/_next/static/chunks/3197-5551de4d59578971.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

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

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.

583 ms

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

1.49 s

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

8 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.018

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

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

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

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
hackernoon.com/_next/static/media/iconfont.8480cc91.woff2	25 ms

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

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG

nodeLabel: AI Memory Systems: The Approaches You Need to Know

path: 1,HTML,1,BODY,0,DIV,0,DIV,0,MAIN,1,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,ARTICLE,0,DIV,0,A,0,SPAN,1,IMG

selector: div.relative > a > span > img.w-full

snippet: <img alt="AI Memory Systems: The Approaches You Need to Know" sizes="(max-width: 768px) 100vw, 400px" srcset="https://hackernoon.imgix.net/images/ai-memory-abstract-c2nxjpcqrda57ev09th…" src="https://hackernoon.imgix.net/images/ai-memory-abstract-c2nxjpcqrda57ev09th…" decoding="async" data-nimg="responsive" class="w-full h-full object-cover transition-transform duration-200 hover:scale-1…" style="position: absolute; inset: 0px; box-sizing: border-box; padding: 0px;">

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

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.

Request	Cache TTL	Transfer Size
cdn2.hackernoon.com/HackerNoonV2-Regular.woff2	14400.0 s	11.0 KiB
cs.iubenda.com/cookie-solution/confs/js/18778700.js	3600.0 s	1.6 KiB

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
caveman newsletter `div.max-w-[1400px] > div.flex > div.flex > img`	hackernoon.com/images/caveman.gif	146.0 KiB	142.9 KiB
AI Coding Tip 015 - Force the AI to Obey You `div.relative > a > span > img.w-full`	/images/RIiBoPtpMiRsMKX3dnzl5gb1Urj1-wj838tc.png?auto=for...	42.4 KiB	26.7 KiB

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

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: 220 ms 423.4 KiB

URL	Transfer Size	Est Savings
hackernoon.com/_next/static/chunks/2297-2b1836f7e743c4dd.js	86.2 KiB	77.0 KiB
accounts.google.com/gsi/client	95.4 KiB	71.8 KiB
www.googletagmanager.com/gtag/js?id=G-ECJJ2Q2SJQ	173.0 KiB	65.5 KiB
hackernoon.com/_next/static/chunks/484bcb1e-a74d55912652d457.js	66.2 KiB	58.6 KiB
cdn.iubenda.com/cookie_solution/iubenda_cs/1.98.0/core-en.js	110.1 KiB	54.8 KiB
hackernoon.com/_next/static/chunks/52066749-b7c60fb5a3cb081d.js	56.2 KiB	37.9 KiB
hackernoon.com/_next/static/chunks/pages/_app-715058edf9331717.js	64.7 KiB	35.3 KiB
hackernoon.com/_next/static/chunks/4423-7ebecf7eae66949a.js	24.9 KiB	22.5 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 67.5 KiB

URL	Transfer Size	Est Savings
hackernoon.com/_next/static/css/21f88a768b9f42d6.css	49.0 KiB	42.0 KiB
@font-face{font-family:'IBM Plex Mono';font-style:normal;font-weight:400;font-display:swap; … } …	15.4 KiB	15.4 KiB
	11.6 KiB	10.1 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
caveman newsletter `div.max-w-[1400px] > div.flex > div.flex > img`	hackernoon.com/images/caveman.gif

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Time to Interactive 2.1 s

●Max Potential First Input Delay 70 ms

●Layout shift culprits

●Document request latency

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●User Timing marks and measures 16 user timings

●JavaScript execution time 0.4 s

●Minimizes main-thread work 1.0 s

●Avoid long main-thread tasks 1 long task found

●Avoid non-composited animations 10 animated elements found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 40 ms

●Server Backend Latencies 150 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 50 ms

●Avoid large layout shifts 3 layout shifts found

○INP breakdown

Accessibility

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
header.font-[ibm-plex-sans] > div.flex > div.navbar-end > button.lg:flex `header.font-[ibm-plex-sans] > div.flex > div.navbar-end > button.lg:flex`
header.font-[ibm-plex-sans] > div.flex > div.navbar-end > button.flex `header.font-[ibm-plex-sans] > div.flex > div.navbar-end > button.flex`

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`
div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2 `div.max-w-[1400px] > div.border-t > div.flex-1 > a.m-2`

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
READ `nav.bg-secondary > div.flex > div.relative > a.cursor-pointer`
TOP BLOGS `nav.bg-secondary > div.flex > div.relative > a.cursor-pointer`
WRITE NOW `nav.bg-secondary > div.flex > div.relative > a.cursor-pointer`
BUSINESS BLOGGING `nav.bg-secondary > div.flex > div.relative > a.py-4`
HACKATHONS `nav.bg-secondary > div.flex > div.relative > a.cursor-pointer`
ABOUT `nav.bg-secondary > div.flex > div.relative > a.cursor-pointer`
MORE `div.z-20 > nav.bg-secondary > div.flex > button.py-4`

These are opportunities to improve the legibility of your content.

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
#ARTIFICIAL-INTELLIGENCE `article.relative > div.relative > div.absolute > a.text-sm`
#HEALTHCARE-CYBERSECURITY `article.relative > div.relative > div.absolute > a.text-sm`
#GAMING `article.relative > div.relative > div.absolute > a.text-sm`
#SYMFONY `article.relative > div.relative > div.absolute > a.text-sm`
#AI-CODING `article.relative > div.relative > div.absolute > a.text-sm`

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

●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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

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

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

●No element has a `[tabindex]` value greater than 0

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

○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

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
Hackernoon logo `a.relative > div.w-[35px] > span > img`	hackernoon.imgix.net/hn-icon.png?auto=format&fit=max&w=64	42 x 42 (1.00)	64 x 69 (0.93)
Maxi Contieri `div.sm:hidden > div.sc-b25c0d3d-0 > span > img.rounded-full`	/images/RIiBoPtpMiRsMKX3dnzl5gb1Urj1-w68367c.jpeg?auto=fo...	40 x 40 (1.00)	48 x 32 (1.50)

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
hackernoon.com/	`Not signed in with the identity provider.`

●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

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

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://hackernoon.com

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

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

User Experience

General

SEO

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Names and labels

Contrast

Best practices

Best Practices

User Experience

General

SEO

Keyboard Shortcuts