Section 01
The site currently has a Performance score of 32, indicating significant issues with speed and resource management.
The LCP is recorded at 47.0 seconds, which is far outside the recommended range.
Why it matters
LCP marks the point in the page load timeline when the page's main content has likely loaded; a slow LCP creates a poor user experience.
The FCP is 3.8 seconds.
Why it matters
This measures the time from when the page starts loading to when any part of the page's content is rendered on the screen.
The TBT is 1,420 ms.
Why it matters
This quantifies how unresponsive a page is to user input, such as mouse clicks or screen taps, before it becomes fully interactive.
The index is 29.0 seconds.
Why it matters
This shows how quickly the contents of a page are visibly populated.
Images are not utilizing modern formats, leading to an estimated savings loss of 9,868 KiB. Several images, such as Cheetah-1.png, exceed 3.6 MB.
Why it matters
Large image files increase download times, directly delaying LCP and consuming user bandwidth.
Multiple scripts and stylesheets are blocking the page's initial render, causing a delay of 2,570 ms.
Why it matters
These resources must be fetched and processed before the browser can display the page content.
The audit identifies 634 KiB of unused JavaScript and 188 KiB of unused CSS.
Why it matters
Excess code increases network activity and requires more CPU time for the browser to parse and execute.
The server response time was observed at 2,099 ms.
Why it matters
A slow server response delays every other part of the page load.
The site uses HTTP/1.1 for several resources instead of modern protocols and contains legacy polyfills that are unnecessary for modern browsers.
Why it matters
Modern protocols like HTTP/2 or HTTP/3 offer benefits like multiplexing that speed up delivery.
Section 02
The site has a Best Practices score of 77, with several critical security and usability failures.
No CSP was found in enforcement mode.
Why it matters
A strong CSP significantly reduces the risk of Cross-Site Scripting (XSS) attacks.
The site lacks a Strict-Transport-Security (HSTS) policy.
Why it matters
This policy reduces the risk of connection downgrades and eavesdropping.
No Cross-Origin-Opener-Policy (COOP) header was found.
Why it matters
This header isolates the window from other documents to prevent certain cross-origin attacks.
No policy was found to mitigate clickjacking (X-Frame-Options or CSP frame-ancestors).
Why it matters
These headers control where a page can be embedded, preventing clickjacking attacks.
Several interactive elements, such as span.swiper-pagination-bullet, have insufficient size or spacing.
Why it matters
Small or crowded touch targets make it difficult for users to activate controls, especially on mobile devices.
The site uses deprecated APIs, specifically AttributionReporting within Facebook social scripts.
Why it matters
Deprecated APIs will eventually be removed from browsers, which could break site functionality.
Section 03
The site has an Accessibility score of 85, indicating several barriers for users of assistive technology.
Background and foreground colors do not meet required contrast ratios for multiple elements, including buttons and paragraph text.
Why it matters
Low-contrast text is difficult or impossible for users with low vision to read.
Several links, particularly those within swiper slides, do not have names that can be announced by screen readers.
Why it matters
Discernible link text allows users of screen readers to understand the purpose of a link before clicking it.
The document does not have a <main> landmark.
Why it matters
Landmarks help screen reader users navigate a web page more efficiently by jumping to major sections.
Some links with the same destination have different descriptions, or links with the same description go to different places.
Why it matters
Consistent link labeling helps users understand where a link will take them.
Section 04
The site has an SEO score of 85, with failures related to content clarity and crawler accessibility.
Multiple links use generic text such as "LEARN MORE" or "READ MORE".
Why it matters
Descriptive link text helps search engines understand the context of your content and improves accessibility.
Lighthouse was unable to download a robots.txt file.
Why it matters
If a robots.txt file is malformed or inaccessible, crawlers may not understand how the site should be indexed.