AI systems lack complete shipping and returns context

Shipping, returns, warranty, and support details are split across partial pages and are not summarized in AI-facing files.

Product answer copy is hidden from AI crawlers

Key sizing, material, and warranty answers are loaded inside client-side widgets instead of crawlable HTML.

Canonical rules conflict on filtered collection URLs

Twelve filtered collection pages still self-canonicalize instead of consolidating to their parent collection.

Homepage hero ships an oversized campaign image on mobile

The spring launch hero still delivers a 1.9 MB JPEG fallback to small screens before the optimized variant loads.

Cache-control behavior is inconsistent across blog and category routes

Product detail pages use stable edge-friendly directives, but blog and category responses still fall back to zero-max-age HTML.

Content-Security-Policy still allows broad script sources for checkout helpers

The latest CSP is tighter than last week, but script-src still permits a wider third-party surface than necessary.

Personalization script delays interactivity after hero render

The recommendation widget adds roughly 310 ms of main-thread work during initial hydration.

Primary brand font is not consistently preloaded on PDP templates

Collection templates preload Archivo, but product detail pages still rely on regular font discovery.

Product schema omits aggregate ratings on high-volume PDPs

Review counts are rendered visually, but the aggregateRating block is missing from the structured data on 18 top-selling SKUs.

llms-full.txt is not published yet

The storefront now exposes llms.txt, but does not yet provide a longer AI context file for product, policy, and support details.

DNSSEC is still not enabled for the apex zone

Nameserver delegation is healthy, but the zone is not yet signed.

Legacy jQuery widget still ships with the React storefront

A merchandising widget loads jQuery on collection pages even though the core storefront has already migrated to React.

Sitemap lastmod values lag behind merchandising updates

Category URLs were updated this week, but the sitemap still reports the previous merchandising timestamp.

Citation readiness signals are strong

Organization schema, contact paths, privacy, terms, and sitemap coverage support confident AI citation.

llms.txt is available for AI systems

A root-level llms.txt file summarizes the brand, categories, and important public pages.

Cloudflare edge protections appear active

The storefront is fronted by Cloudflare and response behavior matches managed edge protection policies.

Domain registration posture is stable

The domain has a multi-year registration window and protected registrar statuses.

Edge compression and request timing are strong

HTML and JavaScript are Brotli-compressed and median TTFB remains below 200 ms on the latest scan.

HSTS, TLS 1.3, and secure cookies are in place

Transport security is well-configured and the session cookie now ships as Secure, HttpOnly, and SameSite=Lax.

HTTP/2 delivery and CDN coverage are in place

The storefront is already taking advantage of multiplexed delivery through Cloudflare edge nodes.

Modern commerce stack is consistently detected

Next.js, Shopify, Stripe, and Algolia are all detected with high confidence across the current storefront.

MX, SPF, and DMARC records are present

Mail routing and authentication controls are configured and easy to audit.

Robots and sitemap endpoints are healthy

robots.txt and sitemap.xml both return 200 responses and surface the expected crawl directives.