Spain · Madrid Completed: Apr 7, 2026 20:21 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 77 / 100
Based on 8 categories, 0 sections
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
'unsafe-eval' found in script source
'unsafe-inline' found in script source
1 link(s) with no accessible text
Cross-Origin-Embedder-Policy header is missing
Cross-Origin-Opener-Policy header is missing
[](https://beavercheck.com/results/e6131471-40fd-bf6b-e4c9-b9107af3f4cd)<a href="https://beavercheck.com/results/e6131471-40fd-bf6b-e4c9-b9107af3f4cd"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.prisma.io" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fwww.prisma.ioThis badge auto-updates with your latest scan result.
Thanks for your feedback!
Industry-standard audits powered by Google Lighthouse.
Key metrics that affect user experience.
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
6.15 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
11.14 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
898 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.
8.69 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.
11.57 s
Audit breakdown by category with detailed findings.
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.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| proxyhog.prisma-data.net/static/posthog-recorder.js?v=1.364.4 | 14400.0 s | 77.0 KiB |
| proxyhog.prisma-data.net/static/surveys.js?v=1.364.4 | 14400.0 s | 29.5 KiB |
| kit.fontawesome.com/ad485975d2.js | 60.0 s | 5.7 KiB |
| kit.fontawesome.com/c1448b716e.js | 60.0 s | 5.7 KiB |
| /array/phc_cmc85avbWyuJ2JyKdGPdv7dxXli8xLdWDBPbvIXWJfs/co... | 14400.0 s | 4.8 KiB |
| cdn-cookieyes.com/assets/images/close.svg | 36000.0 s | 868 B |
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.
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.
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 |
|---|---|---|
| /site-static/_next/static/chunks/ce7d09c07ef18cd7.css?dpl... | 40.3 KiB | 450 ms |
| /site-static/_next/static/chunks/665dc3aa4aa2d85c.css?dpl... | 4.1 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.
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.
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /site-static/_next/static/chunks/23e9b289b6d26136.js?dpl=... | 151.0 KiB | 120.9 KiB |
| /site-static/_next/static/chunks/2724685019ebc7c1.js?dpl=... | 65.0 KiB | 47.5 KiB |
| proxyhog.prisma-data.net/static/posthog-recorder.js?v=1.364.4 | 76.9 KiB | 45.8 KiB |
| /site-static/_next/static/chunks/156abb6c90a0c7cc.js?dpl=... | 57.2 KiB | 26.7 KiB |
| /site-static/_next/static/chunks/55ab220829433019.js?dpl=... | 69.8 KiB | 25.0 KiB |
| /site-static/_next/static/chunks/8566c171816e342a.js?dpl=... | 26.1 KiB | 23.3 KiB |
| proxyhog.prisma-data.net/static/surveys.js?v=1.364.4 | 29.4 KiB | 22.3 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 |
|---|---|---|---|
| www.prisma.io/ | 3.8 s | 28 ms | 25 ms |
| /site-static/_next/static/chunks/0b67ccd61ccae070.js?dpl=... | 2.7 s | 1.3 s | 4.3 ms |
| /site-static/_next/static/chunks/156abb6c90a0c7cc.js?dpl=... | 1.4 s | 819 ms | 50 ms |
| proxyhog.prisma-data.net/static/posthog-recorder.js?v=1.364.4 | 1.2 s | 1.2 s | 25 ms |
| Unattributable | 1.2 s | 60 ms | 0.0 ms |
| /site-static/_next/static/chunks/55ab220829433019.js?dpl=... | 1.2 s | 858 ms | 20 ms |
| kit.fontawesome.com/c1448b716e.js | 137 ms | 134 ms | 2.3 ms |
| cdn-cookieyes.com/client_data/96980f76df67ad5235fc3f0d/banner.js | 107 ms | 56 ms | 2.2 ms |
| /site-static/_next/static/chunks/fed6255c55e7e67f.js?dpl=... | 61 ms | 35 ms | 14 ms |
| /site-static/_next/static/chunks/23e9b289b6d26136.js?dpl=... | 53 ms | 2.7 ms | 50 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 | 4.5 s |
| Style & Layout | 4.4 s |
| Other | 2.0 s |
| Rendering | 550 ms |
| Script Parsing & Compilation | 296 ms |
| Parse HTML & CSS | 160 ms |
| Garbage Collection | 128 ms |
More information about the performance of your application. These numbers don't directly affect the Performance score.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.
| Failing Elements |
|---|
body.flex > nav.z-10 > div.max-w-7xl > ul.gap-4 body.flex > nav.z-10 > div.max-w-7xl > ul.gap-4 |
45.7K body.flex > nav.z-10 > div.max-w-7xl > ul.gap-4 |
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
| Failing Elements |
|---|
Create database div.content > div.flex > a.flex > span |
npx prisma init div.content > div.flex > button.flex > span.text-foreground-neutral-weak |
Explore Pricing div.web-cta > div.content > a.flex > span |
500k div.px-4 > div.max-w-[1240px] > h5.[&>b]:text-background-ppg-reverse-strong > b |
Create your first Database div.mx-auto > div.flex > a.flex > span |
All Systems Operational div.gap-6 > a.flex > span > p.underline |
These are opportunities to improve the legibility of your content.
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
| Failing Elements |
|---|
TRUSTED BY MORE THAN 500k MONTHLY ACTIVE DEVELOPERS GLOBALLY section.my-12 > div.px-4 > div.max-w-[1240px] > h5.[&>b]:text-background-ppg-reverse-strong |
Free to get started, no credit card needed. div.mx-auto > div.p-4 > div.mx-auto > h6.mb-0! |
These are opportunities to improve keyboard navigation in your application.
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.
| Failing Elements |
|---|
div.max-w-7xl > ul.gap-4 > li.relative > a.focus-visible:ring-ring/50 div.max-w-7xl > ul.gap-4 > li.relative > a.focus-visible:ring-ring/50 |
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.
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
| Failing Elements |
|---|
45.7K body.flex > nav.z-10 > div.max-w-7xl > ul.gap-4 |
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
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.
Industry-standard audits powered by Google Lighthouse. — Desktop
Key metrics that affect user experience. — Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
582 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.21 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
86 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.007
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.80 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.23 s
Audit breakdown by category with detailed findings.
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.
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.
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.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| proxyhog.prisma-data.net/static/posthog-recorder.js?v=1.364.4 | 14400.0 s | 77.0 KiB |
| proxyhog.prisma-data.net/static/surveys.js?v=1.364.4 | 14400.0 s | 29.6 KiB |
| kit.fontawesome.com/ad485975d2.js | 60.0 s | 5.7 KiB |
| kit.fontawesome.com/c1448b716e.js | 60.0 s | 5.7 KiB |
| /array/phc_cmc85avbWyuJ2JyKdGPdv7dxXli8xLdWDBPbvIXWJfs/co... | 14400.0 s | 4.8 KiB |
| cdn-cookieyes.com/assets/images/close.svg | 36000.0 s | 845 B |
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 | |
|---|---|---|---|
Profile photo of Nicolás Torres div.text-foreground-neutral > div.flex > div.bg-background-neutral-reverse > img.w-full | www.prisma.io/photos/people/nicolas-torres.png | 187.7 KiB | 187.6 KiB |
Profile photo of Elie Steinbock div.text-foreground-neutral > div.flex > div.bg-background-neutral-reverse > img.w-full | www.prisma.io/photos/people/elie-steinbock.png | 125.0 KiB | 124.9 KiB |
Profile photo of Jim Hendriks div.text-foreground-neutral > div.flex > div.bg-background-neutral-reverse > img.w-full | www.prisma.io/photos/people/jim-hendriks.webp | 79.0 KiB | 79.0 KiB |
Profile photo of Yuval Hazaz div.text-foreground-neutral > div.flex > div.bg-background-neutral-reverse > img.w-full | www.prisma.io/photos/people/yuval-hazaz.jpeg | 37.1 KiB | 37.0 KiB |
Profile photo of Zai Chi div.text-foreground-neutral > div.flex > div.bg-background-neutral-reverse > img.w-full | www.prisma.io/photos/people/zai-chi.jpg | 36.7 KiB | 36.6 KiB |
Profile photo of Harshdeep Singh Hura div.text-foreground-neutral > div.flex > div.bg-background-neutral-reverse > img.w-full | www.prisma.io/photos/people/harshdeep-singh-hura.jpg | 26.2 KiB | 26.1 KiB |
Profile photo of Cody Bontecou div.text-foreground-neutral > div.flex > div.bg-background-neutral-reverse > img.w-full | www.prisma.io/photos/people/cody-bontecou.jpg | 24.5 KiB | 24.4 KiB |
Profile photo of Matti Nannt div.text-foreground-neutral > div.flex > div.bg-background-neutral-reverse > img.w-full | www.prisma.io/photos/people/matti-nannt.jpeg | 23.0 KiB | 22.9 KiB |
Profile photo of Steven Tey div.text-foreground-neutral > div.flex > div.bg-background-neutral-reverse > img.w-full | www.prisma.io/photos/people/steven-tey.jpeg | 19.0 KiB | 18.9 KiB |
Profile photo of Dries Augustyns div.text-foreground-neutral > div.flex > div.bg-background-neutral-reverse > img.w-full | www.prisma.io/photos/people/dries-augustyns.jpg | 17.1 KiB | 17.1 KiB |
Profile photo of Jonathan Wilke div.text-foreground-neutral > div.flex > div.bg-background-neutral-reverse > img.w-full | www.prisma.io/photos/people/jonathan-wilke.jpeg | 16.8 KiB | 16.7 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 |
|---|---|
| /site-static/_next/static/chunks/ce7d09c07ef18cd7.css?dpl... | 40.2 KiB |
| /site-static/_next/static/chunks/665dc3aa4aa2d85c.css?dpl... | 4.0 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.
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /site-static/_next/static/chunks/23e9b289b6d26136.js?dpl=... | 151.0 KiB | 120.9 KiB |
| /site-static/_next/static/chunks/2724685019ebc7c1.js?dpl=... | 65.0 KiB | 47.5 KiB |
| proxyhog.prisma-data.net/static/posthog-recorder.js?v=1.364.4 | 76.9 KiB | 45.9 KiB |
| /site-static/_next/static/chunks/156abb6c90a0c7cc.js?dpl=... | 57.2 KiB | 26.7 KiB |
| /site-static/_next/static/chunks/55ab220829433019.js?dpl=... | 69.8 KiB | 25.3 KiB |
| /site-static/_next/static/chunks/8566c171816e342a.js?dpl=... | 26.1 KiB | 23.3 KiB |
| proxyhog.prisma-data.net/static/surveys.js?v=1.364.4 | 29.4 KiB | 22.3 KiB |
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 |
|---|---|
| Style & Layout | 1.2 s |
| Script Evaluation | 1.2 s |
| Other | 623 ms |
| Rendering | 214 ms |
| Script Parsing & Compilation | 62 ms |
| Garbage Collection | 48 ms |
| Parse HTML & CSS | 32 ms |
More information about the performance of your application. These numbers don't directly affect the Performance score.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.
| Failing Elements |
|---|
Products
Pricing
Resources
Docs
Blog body.flex > nav.z-10 > div.max-w-7xl > ul.gap-4 |
45.7K
Login
Get started body.flex > nav.z-10 > div.max-w-7xl > ul.gap-4 |
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
| Failing Elements |
|---|
Get started ul.gap-4 > div.contents > li.relative > a.flex |
Create database div.content > div.flex > a.flex > span |
npx prisma init div.content > div.flex > button.flex > span.text-foreground-neutral-weak |
Explore Pricing div.web-cta > div.content > a.flex > span |
Create your first Database div.mx-auto > div.flex > a.flex > span |
All Systems Operational div.gap-6 > a.flex > span > p.underline |
These are opportunities to improve the legibility of your content.
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
| Failing Elements |
|---|
TRUSTED BY MORE THAN 500k MONTHLY ACTIVE DEVELOPERS GLOBALLY section.my-12 > div.px-4 > div.max-w-[1240px] > h5.[&>b]:text-background-ppg-reverse-strong |
Free to get started, no credit card needed. div.mx-auto > div.p-4 > div.mx-auto > h6.mb-0! |
These are opportunities to improve keyboard navigation in your application.
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.
| Failing Elements |
|---|
div.max-w-7xl > ul.gap-4 > li.relative > a.focus-visible:ring-ring/50 div.max-w-7xl > ul.gap-4 > li.relative > a.focus-visible:ring-ring/50 |
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.
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
| Failing Elements |
|---|
Products
Pricing
Resources
Docs
Blog body.flex > nav.z-10 > div.max-w-7xl > ul.gap-4 |
45.7K
Login
Get started body.flex > nav.z-10 > div.max-w-7xl > ul.gap-4 |
Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.
| Failing Elements |
|---|
Products div.max-w-7xl > ul.gap-4 > div.hidden > li.relative |
Pricing div.max-w-7xl > ul.gap-4 > div.hidden > li.relative |
Resources div.max-w-7xl > ul.gap-4 > div.hidden > li.relative |
Docs div.max-w-7xl > ul.gap-4 > div.hidden > li.relative |
Blog div.max-w-7xl > ul.gap-4 > div.hidden > li.relative |
45.7K ul.gap-4 > div.contents > div.gap-4 > li.relative |
Discord ul.gap-4 > div.contents > div.gap-4 > li.relative |
Login div.max-w-7xl > ul.gap-4 > div.contents > li.relative |
Get started div.max-w-7xl > ul.gap-4 > div.contents > li.relative |
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
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.
Send Feedback