Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Metrics
First Contentful Paint
1.0 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric.
Largest Contentful Paint
1.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Total Blocking Time
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric.
Cumulative Layout Shift
0
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
1.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
Show audits relevant to:
Diagnostics
Minify JavaScript Potential savings of 102 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.FCPLCP
URL | Transfer Size | Potential Savings |
|---|---|---|
chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/vendor/@eyeo/webext-ad-filtering-solution/content.js | 104.8 KiB | 86.4 KiB |
chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/polyfill.js | 14.0 KiB | 8.9 KiB |
chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/adblock-picreplacement.js | 9.0 KiB | 3.7 KiB |
chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/adblock-functions.js | 6.8 KiB | 3.1 KiB |
Initial server response time was short Root document took 240 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.FCPLCP
URL | Time Spent |
|---|---|
jwvbremen.nl 1st party | 240 ms |
240 ms |
JavaScript execution time 0.0 s
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.TBT
URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
jwvbremen.nl 1st party | 174 ms | 16 ms | 21 ms |
174 ms | 16 ms | 21 ms |
Minimizes main-thread work 0.3 s
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 workTBT
Category | Time Spent |
|---|---|
Style & Layout | 106 ms |
Script Evaluation | 86 ms |
Other | 70 ms |
Script Parsing & Compilation | 31 ms |
Parse HTML & CSS | 10 ms |
Rendering | 5 ms |
Avoid long main-thread tasks 2 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasksTBT
URL | Start Time | Duration |
|---|---|---|
jwvbremen.nl 1st party | 111 ms | |
910 ms | 56 ms | |
…chunks/framework-5429a50ba5373c56.js (everyorigin.jwvbremen.nl) | 1,915 ms | 55 ms |
User Timing marks and measures 4 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more about User Timing marks.
![Next.js](data:image/svg+xml,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 207 124"><path fill="%23000" d="M48.942 32.632h38.96v3.082h-35.39v23.193H85.79v3.082H52.513v25.464h35.794v3.081H48.942V32.632Zm42.45 0h4.139l18.343 25.464 18.749-25.464L158.124.287l-41.896 60.485 21.59 29.762h-4.302l-19.642-27.086L94.15 90.534h-4.22l21.751-29.762-20.29-28.14Zm47.967 3.082v-3.082h44.397v3.082h-20.453v54.82h-3.571v-54.82h-20.373ZM.203 32.632h4.464l61.557 91.671-25.439-33.769L3.936 37.011l-.162 53.523H.203zm183.194 53.891c.738 0 1.276-.563 1.276-1.29 0-.727-.538-1.29-1.276-1.29-.73 0-1.277.563-1.277 1.29 0 .727.547 1.29 1.277 1.29Zm3.509-3.393c0 2.146 1.555 3.549 3.822 3.549 2.414 0 3.874-1.446 3.874-3.956v-8.837h-1.946v8.828c0 1.394-.704 2.138-1.946 2.138-1.112 0-1.867-.692-1.893-1.722h-1.911Zm10.24-.113c.14 2.233 2.007 3.662 4.787 3.662 2.97 0 4.83-1.498 4.83-3.887 0-1.878-1.06-2.917-3.632-3.514l-1.38-.338c-1.634-.38-2.294-.891-2.294-1.783 0-1.125 1.025-1.86 2.563-1.86 1.459 0 2.466.718 2.649 1.869h1.893c-.113-2.103-1.971-3.583-4.516-3.583-2.737 0-4.56 1.48-4.56 3.704 0 1.835 1.033 2.926 3.3 3.454l1.616.39c1.659.389 2.388.96 2.388 1.912 0 1.108-1.146 1.913-2.71 1.913-1.676 0-2.84-.753-3.005-1.939h-1.928Z"/></svg>)
Consider using Next.js Analytics to measure your app's real-world performance. Learn more.Name | Type | Start Time | Duration |
|---|---|---|---|
Next.js-before-hydration | Measure | 0.00 ms | 493.12 ms |
Next.js-hydration | Measure | 493.12 ms | 4.18 ms |
beforeRender | Mark | 493.12 ms | |
afterHydrate | Mark | 497.30 ms |
Avoids enormous network payloads Total size was 194 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.LCP
URL | Transfer Size |
|---|---|
jwvbremen.nl 1st party | 192.8 KiB |
…media/c9a5bc6a7c948fb0-s.p.woff2 (everyorigin.jwvbremen.nl) | 45.6 KiB |
…chunks/framework-5429a50ba5373c56.js (everyorigin.jwvbremen.nl) | 42.7 KiB |
…chunks/814-0e2ccaa2935c3925.js (everyorigin.jwvbremen.nl) | 40.1 KiB |
…chunks/main-fdf56fc4602be5bb.js (everyorigin.jwvbremen.nl) | 29.7 KiB |
/favicon.ico (everyorigin.jwvbremen.nl) | 25.5 KiB |
…css/8a5a8eeb687913db.css (everyorigin.jwvbremen.nl) | 3.0 KiB |
…pages/index-9a564…d674d.js (everyorigin.jwvbremen.nl) | 2.3 KiB |
1.9 KiB | |
…css/ebf630b125565c5c.css (everyorigin.jwvbremen.nl) | 1.2 KiB |
…chunks/webpack-8fa1640cc84ba8fe.js (everyorigin.jwvbremen.nl) | 0.8 KiB |
Avoids an excessive DOM size 24 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.TBT
Statistic | Element | Value |
|---|---|---|
Total DOM Elements | 24 | |
Maximum DOM Depth | Jan-Willem van Bremen <a href="https://jwvbremen.nl" rel=" noopener noreferrer" target="_blank"> | 6 |
Maximum Child Elements | Authored by: Jan-Willem van Bremen
EveryOrigin
The free CORS proxy
EveryOrigi… <main class="flex min-h-screen flex-col items-center justify-between gap-8 p-4 pt-12 te…"> | 5 |
Largest Contentful Paint element 1,820 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element |
|---|
EveryOrigin is a free CORS proxy that allows you to access any website from any… <p> |
Phase | % of LCP | Timing |
|---|---|---|
TTFB | 39% | 720 ms |
Load Delay | 0% | 0 ms |
Load Time | 0% | 0 ms |
Render Delay | 61% | 1,110 ms |
Passed audits (30) Show Hide
Passed audits (30)
Show Hide
Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.FCPLCP
Use the next/script component to defer loading of non-critical third-party scripts. Learn more. Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Use the next/image component to set the appropriate sizes. Learn more. Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.
Use the next/image component instead of <img> to automatically lazy-load images. Learn more. Minify CSS
Reduce unused CSS
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.FCPLCP
Consider setting up PurgeCSS in Next.js configuration to remove unused rules from stylesheets. Learn more. Reduce unused JavaScript
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.LCP
Use Webpack Bundle Analyzer to detect unused JavaScript code. Learn more Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Use the next/image component instead of <img> to adjust image quality. Learn more. Serve images in next-gen formats
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.
Use the next/image component instead of <img> to automatically optimize image format. Learn more. Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.FCPLCP
Enable compression on your Next.js server. Learn more. Preconnect to required origins
Consider adding
preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.FCPLCP Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.FCPLCP
Preload key requests
Consider using
<link rel=preload> to prioritize fetching resources that are currently requested later in page load. Learn how to preload key requests.FCPLCP Use HTTP/2
HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing. Learn more about HTTP/2.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formatsLCP
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. TBT
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScriptTBT
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.LCP
Use the next/image component and set "priority" to true to preload LCP image. Learn more. Uses efficient cache policy on static assets 0 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Configure caching for immutable assets and Server-side Rendered (SSR) pages. Learn more. Avoid chaining critical requests
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn how to avoid chaining critical requests.FCPLCP
Maximum critical path latency: 286.955 ms
Initial Navigation
- 286.955 ms, 1.94 KiB
All text remains visible during webfont loads
Leverage the
font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display.FCPLCP Minimize third-party usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.TBT
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.TBT
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.LCP
Avoid large layout shifts
These DOM elements contribute most to the CLS of the page. Learn how to improve CLSCLS
Uses passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as
passive to improve your page's scroll performance. Learn more about adopting passive event listeners. Avoids document.write()
document.write() For users on slow connections, external scripts dynamically injected via
document.write() can delay page load by tens of seconds. Learn how to avoid document.write(). Avoid non-composited animations
Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animationsCLS
Image elements have explicit width and height
width and height Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensionsCLS
Use the next/image component to make sure images are always sized appropriately. Learn more. Has a <meta name="viewport"> tag with width or initial-scale
<meta name="viewport"> tag with width or initial-scale A
<meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.TBT Page didn't prevent back/forward cache restoration
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
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.
Additional items to manually check (10) Show Hide
Additional items to manually check (10)
Show Hide
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn how to decorate interactive elements with affordance hints.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new content.
HTML5 landmark elements are used to improve navigation
Landmark elements (
<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more about landmark elements. Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.
Passed audits (16) Show Hide
Passed audits (16)
Show Hide
[aria-*] attributes match their roles
[aria-*] attributes match their roles 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. [aria-hidden="true"] is not present on the document <body>
[aria-hidden="true"] is not present on the document <body> Assistive technologies, like screen readers, work inconsistently when
aria-hidden="true" is set on the document <body>. Learn how aria-hidden affects the document body. [role]s have all required [aria-*] attributes
[role]s have all required [aria-*] attributes Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.
[aria-*] attributes have valid values
[aria-*] attributes have valid values Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
[aria-*] attributes are valid and not misspelled
[aria-*] attributes are valid and not misspelled Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
Buttons have an accessible name
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.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5. Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
[role] values are valid
[role] values are valid ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
Background and foreground colors have a sufficient contrast ratio
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Document has a <title> element
<title> element The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
<html> element has a [lang] attribute
<html> element has a [lang] attribute If a page doesn't specify a
lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute. <html> element has a valid value for its [lang] attribute
<html> element has a valid value for its [lang] attribute Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the
lang attribute. Links are distinguishable without relying on color.
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
Links have a discernible name
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.
Heading elements appear in a sequentially-descending order
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.
Values assigned to role="" are valid ARIA roles.
role="" are valid ARIA roles. ARIA
roles enable assistive technologies to know the role of each element on the web page. If the role values are misspelled, not existing ARIA role values, or abstract roles, then the purpose of the element will not be communicated to users of assistive technologies. Learn more about ARIA roles. Not applicable (45) Show Hide
Not applicable (45)
Show Hide
[accesskey] values are unique
[accesskey] values are unique Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more about access keys.
button, link, and menuitem elements have accessible names
button, link, and menuitem elements have accessible names When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
Elements with role="dialog" or role="alertdialog" have accessible names.
role="dialog" or role="alertdialog" have accessible names. ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
[aria-hidden="true"] elements do not contain focusable descendents
[aria-hidden="true"] elements do not contain focusable descendents Focusable descendents within an
[aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements. ARIA input fields have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
ARIA meter elements have accessible names
meter elements have accessible names When a meter element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name
meter elements. ARIA progressbar elements have accessible names
progressbar elements have accessible names When a
progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label progressbar elements. Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
[role] that require children to contain a specific [role] have all required children. Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
[role]s are contained by their required parent element
[role]s are contained by their required parent element Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.
Elements with the role=text attribute do not have focusable descendents.
role=text attribute do not have focusable descendents. Adding
role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's focusable descendents will not be announced. Learn more about the role=text attribute. ARIA toggle fields have accessible names
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.
ARIA tooltip elements have accessible names
tooltip elements have accessible names When a tooltip element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name
tooltip elements. ARIA treeitem elements have accessible names
treeitem elements have accessible names When a
treeitem element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about labeling treeitem elements. The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more about bypass blocks.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements. When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.
Definition list items are wrapped in <dl> elements
<dl> elements Definition list items (
<dt> and <dd>) must be wrapped in a parent <dl> element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly. [id] attributes on active, focusable elements are unique
[id] attributes on active, focusable elements are unique All focusable elements must have a unique
id to ensure that they're visible to assistive technologies. Learn how to fix duplicate ids. ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn how to use form labels.
<frame> or <iframe> elements have a title
<frame> or <iframe> elements have a title Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute. If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the
lang attribute. Image elements have [alt] attributes
[alt] attributes Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the
alt attribute. Image elements do not have [alt] attributes that are redundant text.
[alt] attributes that are redundant text. Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the
alt attribute. Input buttons have discernible text.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
<input type="image"> elements have [alt] text
<input type="image"> elements have [alt] text When an image is being used as an
<input> button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text. Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Lists contain only <li> elements and script supporting elements (<script> and <template>).
<li> elements and script supporting elements (<script> and <template>). Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements
<li>) are contained within <ul>, <ol> or <menu> parent elements 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. The document does not use <meta http-equiv="refresh">
<meta http-equiv="refresh"> Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
<object> elements have alternate text
<object> elements have alternate text Screen readers cannot translate non-text content. Adding alternate text to
<object> elements helps screen readers convey meaning to users. Learn more about alt text for object elements. Select elements have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the
select element. Skip links are focusable.
Including a skip link can help users skip to the main content to save time. Learn more about skip links.
No element has a [tabindex] value greater than 0
[tabindex] value greater than 0 A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the
tabindex attribute. Tables have different content in the summary attribute and <caption>.
<caption>. The summary attribute should describe the table structure, while
<caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption. Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
<table> element that use the [headers] attribute refer to table cells within the same table. Screen readers have features to make navigating tables easier. Ensuring
<td> cells using the [headers] attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more about the headers attribute. <th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe. Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more about table headers.
[lang] attributes have a valid value
[lang] attributes have a valid value Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how to use the
lang attribute. <video> elements contain a <track> element with [kind="captions"]
<video> elements contain a <track> element with [kind="captions"] When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more about video captions.
All heading elements contain content.
A heading with no content or inaccessible text prevent screen reader users from accessing information on the page's structure. Learn more about headings.
Identical links have the same purpose.
Links with the same destination should have the same description, to help users understand the link's purpose and decide whether to follow it. Learn more about identical links.
Document has a main landmark.
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Touch targets have sufficient size and spacing.
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.
Elements with visible text labels have matching accessible names.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
Tables use <caption> instead of cells with the [colspan] attribute to indicate a caption.
<caption> instead of cells with the [colspan] attribute to indicate a caption. Screen readers have features to make navigating tables easier. Ensuring that tables use the actual caption element instead of cells with the
[colspan] attribute may improve the experience for screen reader users. Learn more about captions. <td> elements in a large <table> have one or more table headers.
<td> elements in a large <table> have one or more table headers. Screen readers have features to make navigating tables easier. Ensuring that
<td> elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.Trust and Safety
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
Description | Directive | Severity |
|---|---|---|
No CSP found in enforcement mode | High |
General
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Name | Version |
|---|---|
Next.js | 14.0.4 |
Passed audits (13) Show Hide
Passed audits (13)
Show Hide
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Avoids deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Allows users to paste into input fields
Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more about the geolocation permission.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Properly defines charset
A character encoding declaration is required. It can be done with a
<meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding. Avoids unload event listeners
unload event listeners The
unload event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use pagehide or visibilitychange events instead. Learn more about unload event listeners No browser errors logged to the console
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
No issues in the Issues panel in Chrome Devtools
Issues panel in Chrome Devtools Issues logged to the
Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue. Page has valid source maps
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 | Map URL |
|---|---|
chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/vendor/@eyeo/webext-ad-filtering-solution/content.js |
Not applicable (1) Show Hide
Not applicable (1)
Show Hide
Fonts with font-display: optional are preloaded
font-display: optional are preloaded Preload
optional fonts so first-time visitors may use them. Learn more about preloading fontsThese 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.
Additional items to manually check (1) Show Hide
Additional items to manually check (1)
Show Hide
Structured data is valid
Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more about Structured Data.
Passed audits (11) Show Hide
Passed audits (11)
Show Hide
Has a <meta name="viewport"> tag with width or initial-scale
<meta name="viewport"> tag with width or initial-scale A
<meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.TBT Document has a <title> element
<title> element The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
Links have descriptive text
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Links are crawlable
Search engines may use
href attributes on links to crawl websites. Ensure that the href attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.
Document has a valid hreflang
hreflang hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about
hreflang. Document uses legible font sizes 100% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
Source | Selector | % of Page Text | Font Size |
|---|---|---|---|
Legible text | 100.00% | ≥ 12px |
Document avoids plugins
Search engines can't index plugin content, and many devices restrict plugins or don't support them. Learn more about avoiding plugins.
Tap targets are sized appropriately 100% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), or have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more about tap targets.
Not applicable (3) Show Hide
Not applicable (3)
Show Hide
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Image elements have [alt] attributes
[alt] attributes Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the
alt attribute. Document has a valid rel=canonical
rel=canonical Canonical links suggest which URL to show in search results. Learn more about canonical links.
These checks validate the aspects of a Progressive Web App. Learn what makes a good Progressive Web App.
Installable
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more about manifest installability requirements.
Failure reason |
|---|
Page has no manifest <link> URL |
PWA Optimized
Is not configured for a custom splash screenFailures: No manifest was fetched.
Failures: No manifest was fetched.
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more about splash screens.
Does not set a theme color for the address bar.Failures: No manifest was fetched,
No `<meta name="theme-color">` tag found.
Failures: No manifest was fetched,
No `<meta name="theme-color">` tag found.
The browser address bar can be themed to match your site. Learn more about theming the address bar.
Content is sized correctly for the viewport
If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Learn how to size content for the viewport.
Has a <meta name="viewport"> tag with width or initial-scale
<meta name="viewport"> tag with width or initial-scale A
<meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.TBT Manifest doesn't have a maskable iconNo manifest was fetched
No manifest was fetched
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn about maskable manifest icons.
Additional items to manually check (3) Show Hide
Additional items to manually check (3)
Show Hide
Site works cross-browser
To reach the most number of users, sites should work across every major browser. Learn about cross-browser compatibility.
Page transitions don't feel like they block on the network
Transitions should feel snappy as you tap around, even on a slow network. This experience is key to a user's perception of performance. Learn more about page transitions.
Each page has a URL
Ensure individual pages are deep linkable via URL and that URLs are unique for the purpose of shareability on social media. Learn more about providing deep links.