C — https://www.neon.tech | BeaverCheck Audit

Site Health

Score: 76 / 100

Based on 8 categories, 0 sections

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.

Top Priorities (5)

Content-Security-Policy header is missing

Security › Security Headers

No Content-Security-Policy header found

Security › Content Security Policy

2 image-only link(s) without alt text

Accessibility › Link & Button Quality

Cross-Origin-Embedder-Policy header is missing

Security › Security Headers

Cross-Origin-Opener-Policy header is missing

Security › Security Headers

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.neon.tech)](https://beavercheck.com/results/67e0f367-6a73-7f85-c619-1e86f0ee9085)

HTML

<a href="https://beavercheck.com/results/67e0f367-6a73-7f85-c619-1e86f0ee9085"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.neon.tech" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fwww.neon.tech

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

Best Practices

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.

2.90 s

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

6.07 s

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

1.50 s

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

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

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

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

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.

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:65.518 source:map[column:7484 line:1 type:source-location url:https://neon.com/_next/static/chunks/14pofykpskj6v.js?dpl=dpl_5cMpj5nAJ9JL9mMRdmLL7VSEmj46 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:65.518 source:map[column:24744 line:0 type:source-location url:https://neon.com/_next/static/chunks/0g91v89uj-570.js?dpl=dpl_5cMpj5nAJ9JL9mMRdmLL7VSEmj46 urlProvider:network]] map[reflowTime:20.139 source:map[column:88031 line:8 type:source-location url:https://neon.com/_next/static/chunks/15lxb7jjl82fj.js?dpl=dpl_5cMpj5nAJ9JL9mMRdmLL7VSEmj46 urlProvider:network]]]

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

lhId: page-0-IMG

nodeLabel: main.flex > section.hero > div.pointer-events-none > img.relative

path: 1,HTML,1,BODY,3,DIV,3,MAIN,0,SECTION,1,DIV,1,IMG

selector: main.flex > section.hero > div.pointer-events-none > img.relative

snippet: <img alt="" width="752" height="326" decoding="async" data-nimg="1" class="relative left-[40%] hidden w-[752px] max-w-none -translate-x-1/2 sm:block" style="color:transparent" srcset="/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fbg-illustration.0v57pgq90-qg1…" src="/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fbg-illustration.0v57pgq90-qg1…">

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.

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.

Request	Cache TTL	Transfer Size
/2.js?z=JTdCJTIyZXhlY3V0ZWQlMjIlM0ElNUIlNUQlMkMlMjJjJTIyJ...	0.0 ms	7.0 KiB
neonapi.io/cb.js	0.0 ms	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

	URL	Resource Size	Est Savings
div.min-w-0 > div.relative > div.hidden > img.h-0 `div.min-w-0 > div.relative > div.hidden > img.h-0`	/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Favoid-illust...	140.8 KiB	71.8 KiB
Neon in IDE `div.mx-auto > div.min-w-0 > div.relative > img.hidden`	/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fide-mobile.0...	58.3 KiB	14.4 KiB

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.

URL	Transfer Size	Duration
/_next/static/chunks/0g~lkn047k.tl.css?dpl=dpl_5cMpj5nAJ9...	64.4 KiB	602 ms
/_next/static/chunks/00pd.iv8bj1ox.css?dpl=dpl_5cMpj5nAJ9...	1.5 KiB

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.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Estimated savings: 771 ms

URL	Time Spent
www.neon.tech/	771 ms
neon.com/	0.0 ms

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

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.

Estimated savings: 300 ms 729.7 KiB

URL	Transfer Size	Est Savings
/_next/static/chunks/0fo60y7ohavwr.js?dpl=dpl_5cMpj5nAJ9J...	239.1 KiB	239.0 KiB
/_next/static/chunks/18capnr.er6lu.js?dpl=dpl_5cMpj5nAJ9J...	238.4 KiB	238.3 KiB
/_next/static/chunks/0vih00lfusn-f.js?dpl=dpl_5cMpj5nAJ9J...	35.5 KiB	35.0 KiB
/_next/static/chunks/12z.16dpsg_42.js?dpl=dpl_5cMpj5nAJ9J...	35.4 KiB	34.9 KiB
/_next/static/chunks/0l7tg8r6xuc29.js?dpl=dpl_5cMpj5nAJ9J...	29.4 KiB	29.3 KiB
/_next/static/chunks/0vvlj5zzpjfyu.js?dpl=dpl_5cMpj5nAJ9J...	29.4 KiB	29.3 KiB
/_next/static/chunks/12ctv16-prg-8.js?dpl=dpl_5cMpj5nAJ9J...	29.2 KiB	29.1 KiB
/_next/static/chunks/08rokcdozfqe8.js?dpl=dpl_5cMpj5nAJ9J...	27.1 KiB	26.9 KiB
/_next/static/chunks/0-65m4coapv97.js?dpl=dpl_5cMpj5nAJ9J...	23.2 KiB	23.2 KiB
/_next/static/chunks/14pofykpskj6v.js?dpl=dpl_5cMpj5nAJ9J...	70.4 KiB	22.9 KiB
/_next/static/chunks/0r7171-o75t26.js?dpl=dpl_5cMpj5nAJ9J...	21.8 KiB	21.8 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.

URL	Total CPU Time	Script Evaluation	Script Parse
/_next/static/chunks/14pofykpskj6v.js?dpl=dpl_5cMpj5nAJ9J...	2.7 s	2.1 s	17 ms
neon.com/	2.4 s	143 ms	45 ms
/_next/static/chunks/15lxb7jjl82fj.js?dpl=dpl_5cMpj5nAJ9J...	1.2 s	166 ms	6.5 ms
Unattributable	659 ms	168 ms	0.0 ms
/_next/static/chunks/0g~lkn047k.tl.css?dpl=dpl_5cMpj5nAJ9...	143 ms	0.0 ms	0.0 ms
/_next/static/chunks/0yfh7_u68d5.q.js?dpl=dpl_5cMpj5nAJ9J...	133 ms	94 ms	8.5 ms
/_next/static/chunks/0-wyrs755k4-p.js?dpl=dpl_5cMpj5nAJ9J...	131 ms	117 ms	10 ms
/_next/static/chunks/18capnr.er6lu.js?dpl=dpl_5cMpj5nAJ9J...	80 ms	1.1 ms	78 ms
/_next/static/chunks/0fi9lix4fz.yg.js?dpl=dpl_5cMpj5nAJ9J...	80 ms	76 ms	3.0 ms
/_next/static/chunks/0fo60y7ohavwr.js?dpl=dpl_5cMpj5nAJ9J...	53 ms	0.7 ms	52 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

Category	Time Spent
Script Evaluation	2.9 s
Other	2.0 s
Style & Layout	1.6 s
Rendering	621 ms
Script Parsing & Compilation	346 ms
Parse HTML & CSS	250 ms
Garbage Collection	78 ms

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

URL	Transfer Size
cdn.rive.app/runtime/flutter/inter.ttf	787.3 KiB
cdn.jsdelivr.net/npm/@rive-app/canvas@2.32.0/rive_fallback.wasm	513.8 KiB
/_next/static/chunks/0fo60y7ohavwr.js?dpl=dpl_5cMpj5nAJ9J...	239.6 KiB
/_next/static/chunks/18capnr.er6lu.js?dpl=dpl_5cMpj5nAJ9J...	238.9 KiB
/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Favoid-illust...	141.1 KiB
neon.com/animations/pages/home/speed-scale-ide.riv?2025121142	86.9 KiB
neon.com/	78.3 KiB
/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fsave-costs-m...	74.2 KiB
/_next/static/chunks/14pofykpskj6v.js?dpl=dpl_5cMpj5nAJ9J...	70.6 KiB
neon.com/fonts/geist-mono/GeistMono-Regular.ttf	66.7 KiB

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

●Layout shift culprits

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoid long main-thread tasks 17 long tasks found

●Avoid non-composited animations 178 animated elements found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 180 ms

●Server Backend Latencies 40 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 20 ms

○INP breakdown

○User Timing marks and measures

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

Contrast

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

Failing Elements
02 `li > div.relative > span.absolute > span.absolute`
Test and deploy >> `ol.flex > li > div.relative > h4.mb-6`

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.

Failing Elements
Privacy Notice `div.flex > div.flex > p.flex > a.hover:text-gray-new-20`
California Privacy `div.flex > div.flex > p.flex > a.hover:text-gray-new-20`

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

●Document has a `<title>` element

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

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

●Links are distinguishable without relying on color.

●Links have a discernible name

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

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

●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

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

○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

○Form elements have associated labels

○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

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

Source	Description
neon.com/	`Access to fetch at 'https://unpkg.com/@rive-app/canvas@2.13.4/rive.wasm' from origin 'https://neon.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.`
unpkg.com/@rive-app/canvas@2.13.4/rive.wasm	`Failed to load resource: net::ERR_FAILED`

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.

URL
/_next/static/chunks/18capnr.er6lu.js?dpl=dpl_5cMpj5nAJ9J...
/_next/static/chunks/0fo60y7ohavwr.js?dpl=dpl_5cMpj5nAJ9J...

●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

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.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Link destination	Link Text
/unify?a=2873d867-3be6-45c3-83d9-85ef59831f1b&n=docs/guid...	Learn more
/unify?a=2873d867-3be6-45c3-83d9-85ef59831f1b&n=docs/refe...	Learn more

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

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

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

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.

970 ms

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

1.43 s

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

230 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.19 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.04 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.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

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:54.278 source:map[column:22223 line:1 type:source-location url:https://neon.com/_next/static/chunks/0vih00lfusn-f.js?dpl=dpl_5cMpj5nAJ9JL9mMRdmLL7VSEmj46 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:54.278 source:map[column:96749 line:0 type:source-location url:https://neon.com/_next/static/chunks/0vih00lfusn-f.js?dpl=dpl_5cMpj5nAJ9JL9mMRdmLL7VSEmj46 urlProvider:network]]]

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

lhId: page-0-IMG

nodeLabel: section.hero > div.pointer-events-none > div.overflow-hidden > img.relative

path: 1,HTML,1,BODY,3,DIV,3,MAIN,0,SECTION,1,DIV,0,DIV,0,IMG

selector: section.hero > div.pointer-events-none > div.overflow-hidden > img.relative

snippet: <img alt="" loading="lazy" width="1920" height="832" decoding="async" data-nimg="1" class="relative" style="color:transparent" sizes="100%" srcset="/_next/image?url=https%3A%2F%2Fcdn.neonapi.io%2Fpublic%2Fpages%2Fhome%2Fhe…" src="https://neon.com/_next/image?url=https%3A%2F%2Fcdn.neonapi.io%2Fpublic%2Fp…">

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.

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.

Request	Cache TTL	Transfer Size
cdn.neonapi.io/public/pages/home/hero/hero-av1.mp4	14400.0 s	1.2 MiB
/2.js?z=JTdCJTIyZXhlY3V0ZWQlMjIlM0ElNUIlNUQlMkMlMjJjJTIyJ...	0.0 ms	7.0 KiB
neonapi.io/cb.js	0.0 ms	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

	URL	Resource Size	Est Savings
div.min-w-0 > div.relative > div.pointer-events-none > img.relative `div.min-w-0 > div.relative > div.pointer-events-none > img.relative`	/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fbg.0zus6c-7j...	119.4 KiB	56.6 KiB
body > a.group > img.pointer-events-none `body > a.group > img.pointer-events-none`	/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fleft-pattern...	23.6 KiB	21.6 KiB
body > a.group > img.pointer-events-none `body > a.group > img.pointer-events-none`	/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fright-patter...	20.5 KiB	18.9 KiB

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.

URL	Transfer Size	Duration
/_next/static/chunks/0g~lkn047k.tl.css?dpl=dpl_5cMpj5nAJ9...	64.5 KiB	81 ms
/_next/static/chunks/00pd.iv8bj1ox.css?dpl=dpl_5cMpj5nAJ9...	1.4 KiB

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Estimated savings: 356 ms

URL	Time Spent
www.neon.tech/	356 ms
neon.com/	0.0 ms

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.

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.

Estimated savings: 40 ms 759.2 KiB

URL	Transfer Size	Est Savings
/_next/static/chunks/0fo60y7ohavwr.js?dpl=dpl_5cMpj5nAJ9J...	239.1 KiB	239.0 KiB
/_next/static/chunks/18capnr.er6lu.js?dpl=dpl_5cMpj5nAJ9J...	238.4 KiB	238.3 KiB
/_next/static/chunks/15lxb7jjl82fj.js?dpl=dpl_5cMpj5nAJ9J...	35.6 KiB	35.1 KiB
/_next/static/chunks/12z.16dpsg_42.js?dpl=dpl_5cMpj5nAJ9J...	35.4 KiB	34.9 KiB
/_next/static/chunks/0f_0xrh~5__7j.js?dpl=dpl_5cMpj5nAJ9J...	29.4 KiB	29.3 KiB
/_next/static/chunks/0vvlj5zzpjfyu.js?dpl=dpl_5cMpj5nAJ9J...	29.4 KiB	29.3 KiB
/_next/static/chunks/0brdxb_tnyuiz.js?dpl=dpl_5cMpj5nAJ9J...	29.3 KiB	29.2 KiB
/_next/static/chunks/12ctv16-prg-8.js?dpl=dpl_5cMpj5nAJ9J...	29.2 KiB	29.1 KiB
/_next/static/chunks/08rokcdozfqe8.js?dpl=dpl_5cMpj5nAJ9J...	27.1 KiB	26.9 KiB
/_next/static/chunks/0-65m4coapv97.js?dpl=dpl_5cMpj5nAJ9J...	23.2 KiB	23.2 KiB
/_next/static/chunks/14pofykpskj6v.js?dpl=dpl_5cMpj5nAJ9J...	70.4 KiB	23.0 KiB
/_next/static/chunks/0r7171-o75t26.js?dpl=dpl_5cMpj5nAJ9J...	21.8 KiB	21.8 KiB

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Failure reason	Failure type
Navigation was cancelled before the page could be restored from back/forward cache.	Not actionable

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

URL	Transfer Size
cdn.neonapi.io/public/pages/home/hero/hero-av1.mp4	1.2 MiB
cdn.rive.app/runtime/flutter/inter.ttf	787.3 KiB
cdn.jsdelivr.net/npm/@rive-app/canvas@2.32.0/rive_fallback.wasm	513.8 KiB
neon.com/images/pages/home/speed-scale/noise.png	245.5 KiB
/_next/static/chunks/0fo60y7ohavwr.js?dpl=dpl_5cMpj5nAJ9J...	239.6 KiB
/_next/static/chunks/18capnr.er6lu.js?dpl=dpl_5cMpj5nAJ9J...	238.9 KiB
/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fbg.0zus6c-7j...	119.7 KiB
neon.com/animations/pages/home/speed-scale-ide.riv?2025121142	86.9 KiB
neon.com/	78.3 KiB
/_next/static/chunks/14pofykpskj6v.js?dpl=dpl_5cMpj5nAJ9J...	70.5 KiB

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

●Time to Interactive 2.0 s

●Layout shift culprits

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●JavaScript execution time 0.7 s

●Minimizes main-thread work 1.7 s

●Avoid long main-thread tasks 4 long tasks found

●Avoid non-composited animations 177 animated elements found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 170 ms

●Server Backend Latencies 40 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 20 ms

○INP breakdown

○User Timing marks and measures

○Avoid large layout shifts

Accessibility

Contrast

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

Failing Elements
02 `li > div.relative > span.absolute > span.absolute`
Test and deploy >> `ol.flex > li > div.relative > h4.mb-6`
Compliant `ul.flex > li.-my-px > a.group/link > span.ml-1.5`
Compliant `ul.flex > li.-my-px > a.group/link > span.ml-1.5`
Certified `ul.flex > li.-my-px > a.group/link > span.ml-1.5`
Certified `ul.flex > li.-my-px > a.group/link > span.ml-1.5`
Certified `ul.flex > li.-my-px > a.group/link > span.ml-1.5`
Compliant `ul.flex > li.-my-px > a.group/link > span.ml-1.5`

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.

Failing Elements
Privacy Notice `div.flex > div.flex > p.flex > a.hover:text-gray-new-20`
California Privacy `div.flex > div.flex > p.flex > a.hover:text-gray-new-20`

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

●Document has a `<title>` element

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

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

●Links are distinguishable without relying on color.

●Links have a discernible name

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

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

●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

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

○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

○Form elements have associated labels

○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

○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

Source	Description
neon.com/	`Access to fetch at 'https://unpkg.com/@rive-app/canvas@2.13.4/rive.wasm' from origin 'https://neon.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.`
unpkg.com/@rive-app/canvas@2.13.4/rive.wasm	`Failed to load resource: net::ERR_FAILED`

URL
/_next/static/chunks/18capnr.er6lu.js?dpl=dpl_5cMpj5nAJ9J...
/_next/static/chunks/0fo60y7ohavwr.js?dpl=dpl_5cMpj5nAJ9J...

●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

SEO

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Link destination	Link Text
/unify?a=f3b83097-f751-4f46-bd3e-c0774517d9dd&n=docs/guid...	Learn more
/unify?a=f3b83097-f751-4f46-bd3e-c0774517d9dd&n=docs/refe...	Learn more

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

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Browse & Analyze

Learn

Results for https://www.neon.tech

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Best practices

Best Practices

General

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Best practices

Best Practices

General

SEO

Content Best Practices

Keyboard Shortcuts