Report loading
parfaifragrance.com
Preparing the full page inventory and screenshots.
Report loading
Preparing the full page inventory and screenshots.
Poor
Health Score
Score by category
The headline health score combines page-level quality and site-wide repeat patterns, then stays anchored to the weakest visible category so it never looks worse than every category beneath it.
Section 01
The site's 9.4 MB page weight and heavy third-party dependencies represent a critical threat to user retention and mobile performance.
Parfai establishes a sophisticated, luxury brand identity through an elegant typography scale and well-structured SEO metadata. The core user journey is supported by highly prominent primary calls-to-action and excellent initial render speeds, with Largest Contentful Paint (LCP) metrics consistently falling within Google's "Good" band across both desktop and mobile viewports.
However, extreme page bloat—driven by over 8 MB of third-party scripts and unoptimized assets—severely compromises the experience for mobile users on constrained networks. This technical debt is compounded by critical security gaps, including a missing Content-Security-Policy and an SSL certificate set to expire within 30 days. Furthermore, visual noise from excessive background decorative elements distracts from primary content, while the search input lacks a clear reset affordance on desktop and sufficient visual depth on mobile.
There is a significant opportunity to reclaim performance and brand clarity by aggressively auditing third-party dependencies and streamlining the DOM. Reducing the total page weight below the 2 MB threshold will drastically improve interaction stability and lower data costs for users. Refining the Schema.org implementation with more granular properties like featureList also strengthens search engine visibility and product discoverability.
First 30 days:
5 highest-impact findings, ranked.
No HSTS header. Users are vulnerable to protocol downgrade attacks.
How to fix: Add: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
On /
The search input field has no visual way to reset the query once text is entered. This can lead to frustration for users trying to refine their searches.
How to fix: Add a clear button (an 'X' icon) inside the right side of the `<input type='text'>` element that appears when the value is non-empty.
On /
While the site uses Tailwind's `focus-visible` utility, many interactive elements like the 'Accept All' cookie button and navigation links do not show a highly visible high-contrast ring when focused via keyboard. This can make it impossible for keyboard users to track their location.
How to fix: Ensure all interactive elements have a robust, high-contrast focus indicator. For the cookie banner buttons, add `focus-visible:ring-2 focus-visible:ring-offset-2 focus-visible:ring-black` to the button classes.
On /about
While the page uses `WebApplication` schema, it is missing critical properties like `featureList`, `applicationCategory`, and `operatingSystem` (though some are present) to fully describe the application's functionality to search engines.
On /home
Third-party scripts (analytics, embeds, ad pixels, font CDNs, chat widgets) are hosted outside your control and often render-block, INP-block, or both. Each adds DNS resolution + TLS overhead and can fail independently of your own infrastructure.
How to fix: Audit every third-party tag: drop ones you're no longer measuring, switch from <script> to async/defer, route analytics through a single tag manager, and self-host fonts as woff2 (most font CDNs add 50-150 KB per family).
On /home
