The homepage renders zero <h1> elements. This is the single most impactful on-page SEO element. Google relies heavily on H1 to determine the primary topic of a page. Without it, the homepage cannot rank for core keywords like "premium perfume India" or "long-lasting perfume."

maximum-scale=1.0, user-scalable=no prevents mobile users from zooming in. This violates WCAG 2.1 Success Criterion 1.4.4. Google's mobile-first index now factors accessibility in rankings. It also directly hurts mobile conversion rates for users who need to inspect product details or ingredients.

Current title is "Bla Bli Blu Perfume" — 18 chars. Google allows up to 60 chars. The title misses high-intent keywords like "long-lasting," "premium," "India," "online," or "buy." Competitors are ranking for these modifier terms.

Disallow: /search blocks Google from crawling internal search result pages. While this is common practice, it also means Googlebot cannot discover all product URLs through search navigation. Internal link equity is not being fully utilised.

meta-og:image uses http://blabliblulife.com/cdn/... while the secure version is correctly listed in og:image:secure_url. Mixed content warnings can suppress social previews on secure platforms.

GPTBot (ChatGPT), ClaudeBot (Anthropic), PerplexityBot, and Google-Extended are absent from robots.txt. Without explicit allowance, these crawlers may default to not indexing the site for AI answers. AI search already drives 15–20% of premium product discovery globally.

The /llms.txt URL returns HTTP 200 but the content is not structured in the AI-readable format (markdown with brand description, product categories, key facts). This is a missed GEO opportunity — AI models use llms.txt to understand what a site is about before citing it.

AI models cite sources that have clear, factual, quotable statements. The homepage has no paragraph-length copy explaining: what Bla Bli Blu is, why its perfumes last 10–12 hours, what "25% oil concentration" means vs. EDPs/EDTs, or why the trial pack model is unique in India.

AI search excels at answering "vs." queries. "Bla Bli Blu vs. imported perfumes", "affordable perfume vs. luxury" — Bla Bli Blu is missing out on comparison-driven traffic that AI answers synthesize from brand pages.

The homepage has a well-structured FAQ section with 9 relevant questions (shipping, longevity, refunds, support). But zero FAQPage JSON-LD schema exists. Without it, Google cannot display these as rich results (FAQ drop-downs in SERPs), nor can voice assistants use them for spoken answers.

Google's Speakable schema marks which sections are most relevant for voice assistant reading. With smart speaker adoption growing in India (Google Home, Alexa), "Hey Google, find a good Indian perfume under ₹1000" queries are rising. No speakable markup means zero voice answer eligibility.

Current FAQ answers vary in length and don't follow the 40–60 word direct-answer format that Google prefers for featured snippets. For example, "Are your perfumes long-lasting?" answers with 2 sentences but doesn't lead with the direct time claim (10–12 hours).

AI models prioritise pages with verifiable, specific factual claims. Bla Bli Blu has no statements like "founded in [year]," "X fragrance SKUs," "serving X customers," "shipped to X cities." Even the banner copy ("Fragrance Brand of The Year") lacks attribution or context.

The site has /blogs/perfume but it's buried in the footer. Active, topically relevant blog content dramatically increases AI citability by providing informational content that AI models can reference. Currently contributing near-zero to GEO.

The homepage is entirely product cards, hero banners, and a marquee ticker. There is no paragraph text explaining the brand, the perfume philosophy, what makes Bla Bli Blu different, or why customers should choose them over Skinn, Bella Vita, or imported brands. Google needs indexable text to rank the page.

The marquee ticker leads with "Fragrance Brand of The Year" — a strong claim but without attribution (who gave the award, which year). Unattributed claims can hurt trust signals that both users and AI models evaluate.

Product card titles are being cut off ("Vetiver Oud -...", "Love Drunk - ...") in the homepage listing. While this may be a CSS truncation, it signals that product names aren't optimised as full keyword phrases in the listing view.

The homepage HTML alone is 862 KB before JS/CSS/image assets are counted. This is typical of Shopify themes with many apps, but indicates render-blocking scripts, unused CSS, and full carousel images being loaded on initial paint. On India's 4G average (8 Mbps), this adds ~0.9s to LCP.

The homepage hero has 6 slides, each with both a mobile (841×1161px) and desktop (2400×1020px) image. All appear to be loaded simultaneously. The LCP image (first slide) competes with 10+ other large images for bandwidth.

The site connects to Shopify CDN, Google Fonts, Google Tag Manager, and potentially other third-party services. Without <link rel="preconnect"> hints, the browser wastes time establishing connections during render.

The homepage shows review counts per product (1,187 for Vetiver Oud, 1,126 for By the Beach, etc.) — this is powerful social proof. But no AggregateRating JSON-LD exists to surface these as star ratings in Google SERPs. Rich snippet stars for top products would dramatically improve click-through rates.

Collection and product pages likely lack BreadcrumbList schema. Google shows breadcrumb trails in search results for e-commerce sites — this replaces the URL in the snippet with a human-readable path like "Home > Men > Old Money - 100ml."

The scam warning in the footer (about fraudulent calls/WhatsApp) signals active brand impersonation risk. While good for user trust, it could benefit from structured Organization schema with verified contact details to signal authenticity to search engines.

Current HSTS header: max-age=7889238 (~91 days). Google's best practice recommendation and HSTS preload requirement is 1 year (31,536,000 seconds). A lower value reduces protection window and signals lower security maturity to browsers and search crawlers.

No Permissions-Policy header is set. This header controls browser feature access (camera, microphone, geolocation). Its absence doesn't cause ranking drops but is increasingly flagged in security audits and browser trust indicators.

The CSP header block-all-mixed-content; frame-ancestors 'none' is basic but functional. It doesn't define script-src, style-src, or img-src policies, which means malicious injected scripts aren't blocked.