Report loading
cierga.com
Preparing the full page inventory and screenshots.
Report loading
Preparing the full page inventory and screenshots.
Fair
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 CIERGA digital experience currently suffers from critical technical debt that undermines its premium brand positioning and search visibility. While the site achieves "Good" Core Web Vitals and utilizes sophisticated typography to establish a high-end aesthetic, these strengths are neutralized by severe performance inefficiencies and incomplete metadata.
The platform demonstrates technical excellence in its Core Web Vitals, specifically maintaining a stable layout with a 0.000 CLS and rapid LCP. The implementation of optimized font loading and lazy-loading for below-the-fold images ensures a smooth perceived user experience. Furthermore, the site maintains a clean heading hierarchy and includes essential Schema.org structured data, providing a solid foundation for search engine understanding.
However, the site is crippled by excessive technical bloat and poor SEO configuration. A massive 3.3 MB page weight and an excessive count of 335 HTTP requests—driven largely by 1.7 MB of heavy third-party scripts—threaten long-term scalability and mobile performance. More critically, the absence of meta descriptions and the use of undersized, non-descriptive page titles prevent CIERGA from capturing meaningful organic search traffic. This lack of descriptive metadata, combined with missing Open Graph images, ensures that any social sharing or search appearance remains unoptimized and uncompelling.
The most significant opportunity lies in transitioning from a heavy, script-dependent architecture to a streamlined, SEO-optimized storefront. By aggressively pruning third-party dependencies and implementing a comprehensive metadata strategy, the brand can align its technical performance with its premium visual identity.
First 30 Days Recommendation:
<title> tags and <meta name="description"> across all primary collection and product pages.5 highest-impact findings, ranked.
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 /
Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds. Fix any of the following: Element has insufficient color contrast of 1.06 (foreground color: #626262, background color: #666666, font size: 10.5pt (14px), font weight: normal). Expected contrast ratio of 4.5:1
How to fix: Element matching `#app-embed-container-894941 #label-first_name` has contrast ratio 1.06; WCAG AA requires 4.5:1. Increase the contrast between foreground and background colours (the Tailwind hint below proposes the next darker step in the same family if the offending class is a recognised palette utility). Reference: https://dequeuniversity.com/rules/axe/4.11/color-contrast?application=playwright
On /
Google typically displays 50–60 characters of the title in search results. A title under 30 chars usually fails to set context.
How to fix: Expand the title to 30–60 characters with the page topic and a brand suffix, e.g. <title>Page topic — Brand</title>.
No <meta name="description"> on this page. Google may auto-generate snippet text from page content, which is usually less compelling than a hand-written description.
How to fix: Add: <meta name="description" content="Compelling 120-160 char summary of this page."> — front-load the value proposition.
The JSON-LD Organization schema contains several empty strings in the `sameAs` array. While not a technical error, it provides no value to search engines and should be cleaned up to maintain high data quality.
How to fix: Remove the empty strings from the `sameAs` array in the `<script type="application/ld+json">` block. If no social profiles exist, remove the key entirely: `"sameAs": []`.