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
2.2 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
2.2 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
2.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
- Captured at Mar 9, 2025, 6:00 PM UTC
- Emulated Moto G Power with Lighthouse 12.4.0Unthrottled CPU/Memory Power: 453 CPU throttling: 1.2x slowdown (Simulated) Screen emulation: 412x823, DPR 1.75 Axe version: 4.10.2
- Single page sessionThis data is taken from a single page session, as opposed to field data summarizing many sessions.
- Initial page load
- Slow 4G throttlingNetwork throttling: 150 ms TCP RTT, 1,638.4 kb/s throughput (Simulated) Browser location: North America
- Using HeadlessChromium 133.0.6943.141 with lrUser agent (network): "Mozilla/5.0 (Linux; Android 11; moto g power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Mobile Safari/537.36"
Show audits relevant to:
Diagnostics
Eliminate render-blocking resources Potential savings of 680 ms
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.LCPFCP
URL | Transfer Size | Potential Savings |
|---|---|---|
Unpkg cdn | 0.6 KiB | 800 ms |
…dist/index.global.js (unpkg.com) | 0.6 KiB | 800 ms |
Serve static assets with an efficient cache policy 1 resource found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
URL | Cache TTL | Transfer Size |
|---|---|---|
Cloudflare utility | 7 KiB | |
/beacon.min.js/vcd15cbe… (static.cloudflareinsights.com) | 1d | 7 KiB |
Reduce unused JavaScript Potential savings of 27 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.LCPFCP
URL | Transfer Size | Potential Savings |
|---|---|---|
Unpkg cdn | 69.9 KiB | 26.9 KiB |
/@tailwindcss/browser@4 (unpkg.com) | 69.9 KiB | 26.9 KiB |
User Timing marks and measures 37 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.
Name | Type | Start Time | Duration |
|---|---|---|---|
Build #1 (full) | Measure | 282.99 ms | 60.83 ms |
Create compiler | Measure | 283.30 ms | 50.39 ms |
Reading Stylesheets | Measure | 283.33 ms | 0.19 ms |
Compile CSS | Measure | 283.72 ms | 49.79 ms |
Build | Measure | 333.75 ms | 9.99 ms |
Collect classes | Measure | 333.93 ms | 0.08 ms |
Build utilities | Measure | 334.11 ms | 9.15 ms |
Build #2 (incremental) | Measure | 345.45 ms | 21.61 ms |
Build | Measure | 345.52 ms | 21.46 ms |
Collect classes | Measure | 345.66 ms | 0.25 ms |
Build utilities | Measure | 346.05 ms | 20.57 ms |
Build #1 (full) (start) | Mark | 282.99 ms | |
Create compiler (start) | Mark | 283.30 ms | |
Reading Stylesheets (start) | Mark | 283.33 ms | |
Reading Stylesheets (end) | Mark | 283.52 ms | |
Compile CSS (start) | Mark | 283.72 ms | |
Loaded stylesheet | Mark | 286.85 ms | |
Loaded stylesheet | Mark | 288.11 ms | |
Loaded stylesheet | Mark | 288.38 ms | |
Loaded stylesheet | Mark | 288.55 ms | |
Compile CSS (end) | Mark | 333.51 ms | |
Create compiler (end) | Mark | 333.69 ms | |
Build (start) | Mark | 333.75 ms | |
Collect classes (start) | Mark | 333.93 ms | |
Collect classes (end) | Mark | 334.02 ms | |
Build utilities (start) | Mark | 334.11 ms | |
Build utilities (end) | Mark | 343.26 ms | |
Build (end) | Mark | 343.74 ms | |
Build #1 (full) (end) | Mark | 343.82 ms | |
Build #2 (incremental) (start) | Mark | 345.45 ms | |
Build (start) | Mark | 345.52 ms | |
Collect classes (start) | Mark | 345.66 ms | |
Collect classes (end) | Mark | 345.91 ms | |
Build utilities (start) | Mark | 346.05 ms | |
Build utilities (end) | Mark | 366.62 ms | |
Build (end) | Mark | 366.98 ms | |
Build #2 (incremental) (end) | Mark | 367.06 ms |
Avoid chaining critical requests 1 chain found
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.
Maximum critical path latency: 259.213 ms
Initial Navigation
/@tailwindcss/browser@4
(unpkg.com)
/@tailwindcss/browser@4.0.12
(unpkg.com)
…dist/index.global.js
- 89.412 ms, 70.53 KiB (unpkg.com)
Minimize third-party usage Third-party code blocked the main thread for 30 ms
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
Third-Party | Transfer Size | Main-Thread Blocking Time |
|---|---|---|
Unpkg cdn | 72 KiB | 33 ms |
/@tailwindcss/browser@4 (unpkg.com) | 1 KiB | 33 ms |
…dist/index.global.js (unpkg.com) | 71 KiB | 0 ms |
/@tailwindcss/browser@4.0.12 (unpkg.com) | 1 KiB | 0 ms |
Cloudflare utility | 7 KiB | 0 ms |
/beacon.min.js/vcd15cbe… (static.cloudflareinsights.com) | 7 KiB | 0 ms |
Largest Contentful Paint element 2,220 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element |
|---|
CASA International en CASA Logistics hebben op 5 maart 2025 het faillissement a… <p class="mb-8"> |
Phase | % of LCP | Timing |
|---|---|---|
TTFB | 27% | 600 ms |
Load Delay | 0% | 0 ms |
Load Time | 0% | 0 ms |
Render Delay | 73% | 1,620 ms |
Avoid long main-thread tasks 1 long task 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 |
|---|---|---|
Unpkg cdn | 83 ms | |
/@tailwindcss/browser@4 (unpkg.com) | 1,550 ms | 83 ms |
Passed audits (28) Show Hide
Passed audits (28)
Show Hide
Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.LCPFCP
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.LCPFCP
Minify CSS
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.LCPFCP
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.LCPFCP
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.LCPFCP
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.LCPFCP
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.LCPFCP
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.LCPFCP Initial server response time was short Root document took 70 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.LCPFCP
URL | Time Spent |
|---|---|
casashops.com 1st party | 70 ms |
70 ms |
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.LCPFCP
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 formatsLCPFCP
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. LCPFCP
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 serve modern JavaScriptLCPFCP
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
Avoids enormous network payloads Total size was 85 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
URL | Transfer Size |
|---|---|
Unpkg cdn | 71.7 KiB |
…dist/index.global.js (unpkg.com) | 70.5 KiB |
/@tailwindcss/browser@4.0.12 (unpkg.com) | 0.6 KiB |
/@tailwindcss/browser@4 (unpkg.com) | 0.6 KiB |
Cloudflare utility | 7.1 KiB |
/beacon.min.js/vcd15cbe… (static.cloudflareinsights.com) | 7.1 KiB |
casashops.com 1st party | 6.7 KiB |
3.3 KiB | |
2.9 KiB | |
/cdn-cgi/rum (be.casashops.com) | 0.4 KiB |
Avoids an excessive DOM size 6 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 | 6 | |
Maximum DOM Depth | CASA International en CASA Logistics hebben op 5 maart 2025 het faillissement a… <p class="mb-8"> | 4 |
Maximum Child Elements | CASA International en CASA Logistics hebben op 5 maart 2025 het faillissement a… <div class="w-full px-4 md:px-6 text-xl text-gray-800 leading-normal" style="font-family:Georgia,serif;"> | 3 |
JavaScript execution time 0.1 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 |
|---|---|---|---|
Unpkg cdn | 83 ms | 77 ms | 6 ms |
/@tailwindcss/browser@4 (unpkg.com) | 83 ms | 77 ms | 6 ms |
casashops.com 1st party | 56 ms | 29 ms | 0 ms |
56 ms | 29 ms | 0 ms |
Minimizes main-thread work 0.2 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 |
|---|---|
Script Evaluation | 125 ms |
Other | 40 ms |
Style & Layout | 22 ms |
Script Parsing & Compilation | 6 ms |
Parse HTML & CSS | 2 ms |
Rendering | 1 ms |
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. 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 are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. 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
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.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 (6) Show Hide
Passed audits (6)
Show Hide
[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. [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.
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. Not applicable (51) Show Hide
Not applicable (51)
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.
[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. Uses ARIA roles only on compatible elements
Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page. Learn more about ARIA roles.
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.
ARIA attributes are used as specified for the element's role
Some ARIA attributes are only allowed on an element under certain conditions. Learn more about conditional ARIA attributes.
Deprecated ARIA roles were not used
Deprecated ARIA roles may not be processed correctly by assistive technology. Learn more about deprecated ARIA roles.
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 use only permitted ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
[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.
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.
[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.
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. [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.
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. 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.
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.
<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.
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.
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. 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.
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.
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 |
Use a strong HSTS policy
Deployment of the HSTS header significantly reduces the risk of downgrading HTTP connections and eavesdropping attacks. A rollout in stages, starting with a low max-age is recommended. Learn more about using a strong HSTS policy.
Description | Directive | Severity |
|---|---|---|
No HSTS header found | High |
Ensure proper origin isolation with COOP
The Cross-Origin-Opener-Policy (COOP) can be used to isolate the top-level window from other documents such as pop-ups. Learn more about deploying the COOP header.
Description | Directive | Severity |
|---|---|---|
No COOP header found | High |
Mitigate clickjacking with XFO or CSP
The
X-Frame-Options (XFO) header or the frame-ancestors directive in the Content-Security-Policy (CSP) header control where a page can be embedded. These can mitigate clickjacking attacks by blocking some or all sites from embedding the page. Learn more about mitigating clickjacking.Description | Severity |
|---|---|
No frame control policy found | High |
Passed audits (15) Show Hide
Passed audits (15)
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.
Avoids third-party cookies
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. Learn more about third-party cookies.
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.
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. 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 |
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. 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.
Not applicable (2) Show Hide
Not applicable (2)
Show Hide
Redirects HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
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
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Crawling and Indexing
robots.txt is not valid 56 errors found
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.
Line # | Content | Error |
|---|---|---|
1 | <!DOCTYPE html> | Syntax not understood |
2 | <html lang="en"> | Syntax not understood |
3 | <head> | Syntax not understood |
4 | <meta charset="UTF-8"> | Syntax not understood |
5 | <meta name="viewport" content="width=device-width, initial-scale=1.0"> | Syntax not understood |
6 | <title>CASA: Trendy woonproducten voor in en rond het huis | CASA</title> | Unknown directive |
7 | <script src="https://unpkg.com/@tailwindcss/browser@4"></script> | Unknown directive |
8 | </head> | Syntax not understood |
9 | <body class="bg-gray-100 font-sans leading-normal tracking-normal"> | Syntax not understood |
12 | <!--Container--> | Syntax not understood |
13 | <div class="container w-full md:max-w-3xl mx-auto pt-20"> | Unknown directive |
15 | <div class="w-full px-4 md:px-6 text-xl text-gray-800 leading-normal" style="font-family:Georgia,serif;"> | Unknown directive |
17 | <!--Title--> | Syntax not understood |
18 | <!-- <div class="font-sans"> | Syntax not understood |
19 | <h1 class="font-bold font-sans break-normal text-gray-900 pt-6 pb-2 text-3xl md:text-4xl">Welcome to Minimal Blog</h1> | Unknown directive |
20 | <p class="text-sm md:text-base font-normal text-gray-600">Published 19 February 2019</p> | Unknown directive |
21 | </div> --> | Syntax not understood |
24 | <!--Post Content--> | Syntax not understood |
27 | <!--Lead Para--> | Syntax not understood |
28 | <!-- <p class="py-6"> | Syntax not understood |
29 | 👋 Welcome fellow <a class="text-green-500 no-underline hover:underline" href="https://www.tailwindcss.com">Tailwind CSS</a> and miminal monochrome blog fan. This starter template provides a starting point to create your own minimal monochrome blog using Tailwind CSS and vanilla Javascript. | Unknown directive |
30 | </p> --> | Syntax not understood |
32 | <!-- <p class="py-6">The basic blog page layout is available and all using the default Tailwind CSS classes (although there are a few hardcoded style tags). If you are going to use this in your project, you will want to convert the classes into components.</p> | Syntax not understood |
35 | <h1 class="py-2 font-sans">Heading 1</h1> | Syntax not understood |
36 | <h2 class="py-2 font-sans">Heading 2</h2> | Syntax not understood |
37 | <h3 class="py-2 font-sans">Heading 3</h3> | Syntax not understood |
38 | <h4 class="py-2 font-sans">Heading 4</h4> | Syntax not understood |
39 | <h5 class="py-2 font-sans">Heading 5</h5> | Syntax not understood |
40 | <h6 class="py-2 font-sans">Heading 6</h6> --> | Syntax not understood |
43 | <p class="mb-8">CASA International en CASA Logistics hebben op 5 maart 2025 het faillissement aangevraagd. | Syntax not understood |
44 | Hierdoor zijn alle activiteiten on hold gezet en sluiten wij (tijdelijk) onze webshop en de Belgische winkels. In de winkels in de andere landen bent u nog steeds welkom. | Syntax not understood |
45 | De curator die aangesteld wordt, zal de komende weken beslissen of de winkel/webshop al dan niet nog terug opengaat in kader van het faillissementsdossier en wat er met uw reeds betaalde bestellingen zal gebeuren. | Syntax not understood |
46 | In afwachting van deze informatie danken wij u voor uw jarenlange steun en vertrouwen en waarderen uw begrip in deze situatie. | Syntax not understood |
47 | </p> | Syntax not understood |
49 | <p class="mb-8">Dear customer, | Syntax not understood |
50 | CASA International and CASA Logistics filed for bankruptcy on March 5, 2025. | Syntax not understood |
51 | As a result, all activities have been put on hold and we are (temporarily) closing our webshop and Belgian stores. Stores in other countries will continue to operate as usual. | Syntax not understood |
52 | The trustee that will be appointed, will decide in the coming weeks whether or not the webshop/stores will reopen and what will happen with your paid order, as part of the bankruptcy proceedings. | Syntax not understood |
53 | Pending this information, we thank you for your many years of support and trust and appreciate your understanding in this situation. | Syntax not understood |
54 | </p> | Syntax not understood |
56 | <p>Cher client, | Syntax not understood |
57 | CASA International et CASA Logistics ont déposé leur bilan le 5 mars 2025. | Syntax not understood |
58 | Par conséquent, toutes les activités ont été suspendues et nous fermons (temporairement) notre webshop et shops en Belgique. | Syntax not understood |
59 | Le curateur qui sera désigné, décidera dans les prochaines semaines de la réouverture ou non du magasin/webshop ainsi que le traitement des commandes déja payé dans le cadre de la procédure de faillite. | Syntax not understood |
60 | Dans l'attente de ces informations, nous vous remercions de votre soutien et de votre confiance depuis de nombreuses années et apprécions votre compréhension dans cette situation. | Syntax not understood |
61 | </p> | Syntax not understood |
62 | <!-- <ol> | Syntax not understood |
63 | <li class="py-3">Maecenas accumsan lacus sit amet elementum porta. Aliquam eu libero lectus. Fusce vehicula dictum mi. In non dolor at sem ullamcorper venenatis ut sed dui. Ut ut est quam. Suspendisse quam quam, commodo sit amet placerat in, interdum a ipsum. Morbi sit amet tellus scelerisque tortor semper posuere.</li> | Syntax not understood |
64 | <li class="py-3">Morbi varius posuere blandit. Praesent gravida bibendum neque eget commodo. Duis auctor ornare mauris, eu accumsan odio viverra in. Proin sagittis maximus pharetra. Nullam lorem mauris, faucibus ut odio tempus, ultrices aliquet ex. Nam id quam eget ipsum luctus hendrerit. Ut eros magna, eleifend ac ornare vulputate, pretium nec felis.</li> | Syntax not understood |
65 | <li class="py-3">Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia Curae; Nunc vitae pretium elit. Cras leo mauris, tristique in risus ac, tristique rutrum velit. Mauris accumsan tempor felis vitae gravida. Cras egestas convallis malesuada. Etiam ac ante id tortor vulputate pretium. Maecenas vel sapien suscipit, elementum odio et, consequat tellus.</li> | Syntax not understood |
66 | </ol> --> | Syntax not understood |
70 | </div> | Syntax not understood |
76 | </div> | Syntax not understood |
77 | <!--/container--> | Syntax not understood |
80 | </body> | Syntax not understood |
82 | </html> | Syntax not understood |
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 (6) Show Hide
Passed audits (6)
Show Hide
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 <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.
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 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. Not applicable (2) Show Hide
Not applicable (2)
Show Hide
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.
