Web Quality Audit: Indinoor (indinoor.in)

Website: https://indinoor.in | Date: 2026-08-24 | Platform: Shopify (theme 158459429080, OS 2.0) | Industry: Fashion / imitation & 925-silver jewellery (D2C)

Business context (from business-analysis.md): Indinoor is a 15-month-old celebrity-co-created D2C jewellery brand (Shanaya Kapoor × House of Isharya / Reliable Fashions India Pvt. Ltd.). 2,183 SKUs, median ₹2,390, ~90 active Meta ads, and a 92–97% mobile audience — so mobile performance, accessibility and trust are the commercial battleground, not nice-to-haves. A mid-2026 mobile Core Web Vitals regression was already flagged in the business analysis; this audit verifies it with live field + lab data.

---

Executive Summary

Indinoor is a well-built Shopify store with solid SEO basics (92/100), a sound security posture (HSTS, CSP, X-Frame-Options all present), and clean product schema — but it is held back by three things: (1) a severe mobile performance problem that spiked and is only partially recovering, (2) an accessibility layer that is failing automated checks (no H1 on the homepage, redundant/empty alt text, unnamed buttons, contrast failures), and (3) missing trust + structured-data depth that matters enormously for a low-consideration imitation-jewellery purchase (no reviews on PDPs, no BreadcrumbList, empty sameAs, no social links on-site).

The single most important story: mobile Core Web Vitals collapsed in mid-2026 and are only now clawing back. CrUX phone LCP went from ~2.0–2.5 s (Good, Oct 2025–May 2026) to 5,834 ms (Poor) in the 2026-07-05→08-01 window, then recovered to 2,914 ms (Needs Improvement) in the latest 2026-07-26→08-22 window. INP followed the same arc (peaked ~422 ms Poor, now 223 ms Needs Improvement). The site is not currently in a "Failed" state on the latest data — but it sits one bad deploy away from Poor, and the Lighthouse lab test still shows a catastrophic 25.2 s mobile LCP under throttling, meaning real-world recovery is real but fragile.

Category	Mobile Score	Desktop Score	Grade
Performance	28	42	🔴
Accessibility	78	78	🟡
Best Practices	50	50	🟡
SEO	92	92	🟢
Overall (weighted, quality lens)	~48	~55	🟡

Mobile-vs-desktop gap: Performance 28 vs 42 (~1.5×). The mobile LCP lab figure (25.2 s) is 9.3× the good threshold (2.5 s) — the dominant risk. Desktop is merely "slow" (LCP 3.4 s), mobile is "broken under throttle."

Highest-ROI fixes: (P0) restore a real homepage <h1> and fix alt text; (P0) ship BreadcrumbList + AggregateRating/Review schema and turn on Loox/Kla review display on PDPs; (P0) repair the Organization sameAs array (9 empty strings); (P1) image delivery optimization (2,421 KiB savings identified) and reduce render-blocking JS/CSS; (P1) add og:image to the homepage and switch og:image to https://.

---

1. Performance Audit

1.1 CrUX Real-World Field Data

Core Web Vitals Assessment (phone): Needs Improvement on the latest 28-day window (2026-07-26 → 2026-08-22). LCP and INP are both "Needs Improvement"; CLS is "Good." This is a recovery from a "Poor" spell in June–July 2026.

Note on platform coverage: CrUX Vis exposes the phone time series for this origin (phone = 92 % of traffic). Desktop (8 %) and tablet (0 %) are below the per-form-factor sampling threshold, so desktop/tablet field CWV are not assessed here. Because the audience is 92 % mobile, phone data is the right lens anyway.

Phone CWV trend (from CrUX Vis graphics-symbol aria-labels, origin https://indinoor.in):

4-week window	LCP	INP	CLS	LCP rating
2025-10-26 → 11-22	2,179 ms	147 ms	0.02	Good
2026-05-03 → 05-30	2,382 ms	164 ms	0.00	Good
2026-05-31 → 06-27	2,390 ms	176 ms	0.07	Good
2026-06-07 → 07-04	3,980 ms	264 ms	0.08	Needs Improvement
2026-06-14 → 07-11	4,722 ms	310 ms	0.09	Needs Improvement
2026-06-21 → 07-18	5,419 ms	382 ms	0.06	Poor
2026-06-28 → 07-25	5,810 ms	422 ms	0.02	Poor
2026-07-05 → 08-01	5,834 ms	419 ms	0.01	Poor (peak)
2026-07-12 → 08-08	5,679 ms	412 ms	0.00	Poor
2026-07-19 → 08-15	4,791 ms	328 ms	0.00	Needs Improvement
2026-07-26 → 08-22	2,914 ms	223 ms	0.00	Needs Improvement (recovering)

Interpretation: A clear, sharp regression began around 2026-06-07 (LCP +1.6 s over one window) and bottomed out at 5,834 ms / INP 419 ms in early July — squarely "Poor" on two of three metrics. The latest window shows a dramatic rebound to 2,914 ms / 223 ms. Two takeaways:

• The latest state is "Needs Improvement," not "Good" — LCP is still 414 ms over the 2.5 s good threshold, and INP is 23 ms over the 200 ms good threshold. A single heavy deploy re-breaks it.
• The swing itself is the finding: something shipped in early June 2026 (heavier hero media, an app injection, or a theme change) degraded mobile LCP by ~3.4 s and INP by ~260 ms. Even though it has been partly rolled back/fixed, the cause should be identified and guarded so festive-season (Diwali/Navratri) traffic — when 90 Meta ads are driving mobile shoppers — doesn't hit a Poor window.

1.2 Core Web Vitals (Lighthouse Lab Data)

Source: PageSpeed Insights, report captured 2026-08-24 11:32 UTC. Lighthouse 13.4.1. Mobile = emulated Moto G Power, Slow 4G. Desktop = unthrottled.

Metric	Mobile (lab)	Mobile rating	Desktop (lab)	Desktop rating	Good threshold
FCP	5.0 s	Poor	0.7 s	Good	≤ 1.8 s
LCP	25.2 s	Poor	3.4 s	Needs Improvement	≤ 2.5 s
TBT	2,660 ms	Poor	2,830 ms	Poor	≤ 200 ms
CLS	0	Good	0	Good	≤ 0.10
SI	11.7 s	Poor	3.8 s	Needs Improvement	≤ 3.4 s
TTFB	1.5 s	Needs Improvement	0.3 s	Good	≤ 0.8 s (exp.)

Reading: The lab mobile LCP of 25.2 s is alarmingly high and is the reason the mobile Performance score is 28/100. Desktop (42/100) is "slow but functional." The large gap between field LCP (2.9 s) and lab LCP (25.2 s) on mobile is itself diagnostic: under throttling the page is catastrophically render-blocked, even though real 4G users (faster than the emulated Slow-4G + Moto G) experience ~2.9 s. The lever is the same regardless: cut the critical-path JS/CSS and image weight.

1.3 LCP Phase Breakdown (Mobile)

PageSpeed Insights surfaces these as "LCP breakdown / request discovery / network dependency tree" insights. Direct phase values weren't exported, but the insight set tells the story:

• Improve image delivery — est. savings 2,421 KiB. The LCP element (homepage slideshow image, alt="Slideshow Image 1") is almost certainly oversized/unoptimized. This is the #1 mobile LCP driver.
• Render-blocking requests — est. savings 170 ms. CSS/JS on the critical path (theme.css, font-settings.css, the smind-app-319 extension CSS are all <link rel="preload">-injected in the HTTP headers).
• Forced reflow and LCP request discovery insights present → JS is deferring discovery of the LCP element.
• Preconnect warning: "More than 4 preconnect connections were found" — the response preconnects to cdn.shopify.com (×2) + fonts.googleapis.com + the smind extension; excess preconnects dilute priority and can hurt LCP.

1.4 Performance Issues by Impact

Critical (> 1 s estimated savings)

Issue	Evidence	Est. savings	Recommendation
Image delivery not optimized	PSI insight "Improve image delivery," 2,421 KiB; homepage slideshow alt="Slideshow Image 1"	2,421 KiB	Serve AVIF/WebP, responsive srcset, right-size the hero; don't lazy-load the LCP image
Render-blocking CSS/JS on critical path	"Render-blocking requests" 170 ms; 14 stylesheets + 115 scripts in homepage DOM	170 ms + pre-resource delay	Inline critical CSS, defer non-critical, use defer on app scripts
Enormous network payload	PSI "Avoid enormous network payloads — Total size was 9,595 KiB" (desktop)	—	Trim third-party app JS (GoKwik, Cooee, Return Prime, Shiprocket, smind) on the homepage

High (200 ms–1 s)

Issue	Evidence	Recommendation
Total Blocking Time 2,660 ms (mobile) / 2,830 ms (desktop)	"Minimize main-thread work 13.0 s," "20 long tasks"	Code-split / defer app scripts; lazy-init below-fold widgets (Cooee personalization, Return Prime)
Reduce unused JavaScript	"Est. savings of 1,672 KiB"	Remove dead app bundles; load personalization/returns only where needed
Legacy JavaScript	"Est. savings of 13 KiB" + "Uses deprecated APIs (2 warnings)"	Update polyfilled libs
Efficient cache lifetimes	"Est. savings of 1,086 KiB"	Bump Cache-Control max-age on static CDN assets

Medium / Low

• Minify CSS (3 KiB) / JS (21 KiB) — trivial.
• Reduce unused CSS (98 KiB) — Shopify theme ships section CSS not used on the homepage.
• DOM size "Optimize DOM size" — homepage 2,944 elements (acceptable but watch on collection PDPs).
• Preconnect reduction to 2–3 origins (drop the duplicate cdn.shopify.com and extension preconnect unless critical).

1.5 Resource Transfer Summary

Category	Finding	Note
Images	Dominant payload; 2,421 KiB savings identified	Hero slideshow + product grid images not next-gen
JS	115 <script> on homepage; 1,672 KiB unused	GoKwik/Cooee/Return Prime/Shiprocket + smind extension
CSS	14 stylesheets; 98 KiB unused	theme.css + extension CSS
3rd-party	"3rd parties" insight present; main-thread work 13.0 s	Personalization (Cooee) and checkout (GoKwik) heaviest

---

2. Accessibility Audit

2.1 Critical Issues

1. No <h1> on the homepage. The rendered homepage DOM has 0 <h1> elements — heading structure begins at <h2> ("BESTSELLERS ON SALE," "SHOP BY MOTIF," "NEW LAUNCH"). This is a WCAG A failure and a lost SEO/wayfinding signal: screen-reader users and Google get no single page-level topic. (PDPs do have an H1 — the product title — so this is a homepage template bug, not a global one.)
2. Images missing alt entirely — homepage: 1 <img> with no alt; PDP: 4 with no alt. WCAG A.
3. Redundant/empty alt text. Homepage: 41 of 83 images have alt="" (several are decorative LineExtensions_* lines — acceptable — but combined with the no-alt count it's inconsistent). PDP: 72 of 103 <img> have alt="". PSI flags "Image elements do not have [alt] attributes that are redundant text" — decorative images must be alt="" (fine) but content/product images need descriptive alt. The pattern suggests product imagery is being marked decorative.

2.2 High Priority Issues

• Buttons without accessible names (PSI). Example in DOM: the wishlist "Add to wishlist" buttons wrap only an <img> with no alt + no aria-label; the slideshow "View slide N" buttons render as \"\" (empty) text. Screen-reader users hear nothing.
• <iframe> elements without a title (PSI) — the Cooee/GoKwik/YouTube widgets.
• Links without a discernible name (PSI) — icon-only links (Wishlist, Search, Cart) lack aria-label.
• Contrast failures (PSI: "Background and foreground colors do not have a sufficient contrast ratio"). Common on festive-palette sale badges / light-on-colored CTAs.
• [aria-hidden="true"] elements contain focusable descendants (PSI) — a focus-order bug; keyboard users can land on hidden controls.
• Touch targets insufficient size/spacing (PSI Best Practices) — common on mobile nav icon buttons.

2.3 Positive Findings

• <html lang="en"> present; <meta name="viewport"> present and correct (width=device-width, initial-scale=1).
• "Skip to content" link present (first focusable element) — good.
• PDPs have a proper <h1> and visible product title.
• 22 accessibility audits passed; 10 manual checks flagged for human review (color contrast in context, heading order, focus management).

---

3. SEO Audit

3.1 Technical SEO

Check	Status	Evidence
HTTPS enforced	✅	strict-transport-security: max-age=7889238; upgrade-insecure-requests in CSP
robots.txt	✅	Allows crawl; disallows cart/checkout/account; references Sitemap; clean
XML Sitemap	✅	Index + 3 product sitemaps (2,179 URLs), 247 collections, 56 blogs, 12 pages, agentic-discovery
Canonical URLs	✅	Self-referencing on homepage + PDP + collection (verified)
Indexation / noindex	✅	No noindex on key templates observed
URL structure	✅	Clean lowercase hyphenated handles (/products/zia-everyday-silver-studs)
Mobile-friendly	✅	Viewport + responsive OS 2.0 theme
Mixed content	⚠️	PDP og:image is http://indinoor.in/... (301→https; not broken, but violates CSP block-all-mixed-content correctness and can fail some crawlers/social scrapers)
Hreflang	❌	No hreflang anywhere (single-locale en-IN; acceptable only because there's no second locale — no i18n gap today)

3.2 On-Page SEO Issues

Page type	Title	Meta desc	OG image	Notes
Homepage	✅ "Fashion Jewellery Online & Ethnic Jewellery Collection - Indinoor" (65 char)	✅ present	❌ missing og:image	Title/desc good; no share preview image
PDP	✅ product name + brand	✅ auto from description	⚠️ http:// scheme	Good; fix scheme
Collection (/collections/rakhi-ready)	✅ "Rakhi-Ready – Indinoor"	❌ no meta description	❌ no og:image	Collections are the festive discovery surface — missing meta desc + OG image across 247 collections is a real CTR/SEO gap

• Homepage has no H1 (see §2.1) — also an on-page SEO issue (no keyword-bearing H1).
• No og:image on the homepage is the headline OG gap: shared links to indinoor.in render without a preview image on WhatsApp/Instagram/FB — damaging for a brand whose entire acquisition is social/Meta (90 ads).

3.3 Schema Markup

Type	Homepage	PDP	Collection	Notes
Organization	✅	✅	—	sameAs = 9 empty strings ❌ — should list Instagram/FB or be omitted
WebSite + SearchAction	✅	—	—	Good (enables sitelinks search box)
Product	—	✅	—	name, brand, offer, sku, availability present
Offer	—	✅	—	price/currency/availability present
Brand	—	✅	—	matches Organization name ("Indinoor") ✅
BreadcrumbList	❌	❌	❌	Missing everywhere — no SERP breadcrumbs
AggregateRating / Review	❌	❌ (app JS only)	❌	No rich-result reviews despite Loox/Kla installed
LocalBusiness / JewelryStore	❌	❌	❌	Brand has a real Mumbai address — missed local/entity signal
ItemList (collections)	—	—	❌	Collection pages don't list products as ItemList

Key schema problems:

1. Organization sameAs is an array of 9 empty strings — this is broken structured data; Google may ignore or distrust the entity graph. Fix: populate with the real Instagram/Facebook URLs (both exist) or remove empty entries.
2. No AggregateRating/Review JSON-LD on PDPs even though review apps (Loox, Kla) are installed — confirms the business-analysis finding that on-site reviews are not surfaced for SEO/crawlers (they render client-side only). This forfeits star-rich-results in SERPs — a major miss for a trust-sensitive jewellery category.
3. No BreadcrumbList anywhere — both an SEO and UX gap (no breadcrumb nav observed in DOM either).

3.4 Image SEO

• Filenames: product images use SKU-style names (IN-E790-17-SG-127_1_zoom.jpg) — acceptable but not keyword-rich.
• Alt text: inconsistent (see §2.1) — decorative vs content not cleanly separated.
• No AI-generated image filenames detected (Gemini/ChatGPT/Picsart/ai0_ patterns) — product photography appears genuine, which is good for a "House of Isharya craft heritage" brand.

3.5 Internal Linking & Keyword Targeting

• Homepage links to festive/everyday/925-silver hubs and category strips (Necklace Sets, Earrings, Wristwear, Rings, Accessories) — good top-level IA.
• 228 links on homepage; 0 internal social links (see §3.6).
• Keyword targeting: title carries "Fashion Jewellery / Ethnic Jewellery" — reasonable; collection pages need unique meta descriptions to avoid thin-indexation.

3.6 E-E-A-T / Trust Signals

• Phone, email, address all present in footer/contact (support@indinoor.in, +91 8433550190, Mumbai HQ) ✅.
• Return + shipping policies linked on PDP ✅; 7-day return + 1-year plating warranty stated ✅.
• GST/CIN (Reliable Fashions India Pvt. Ltd., CIN U51398MH2008PTC186733) referenced ✅ — strong trust signal for an Indian D2C.
• Social links absent from the rendered site — 0 instagram/facebook/youtube hrefs in the homepage DOM, despite a real 94K-follower Instagram and active Meta presence. This is a missed trust, SEO and cross-channel signal (and contradicts the Organization sameAs, which should carry these).

---

4. International SEO

Not applicable. The store is single-locale (en-IN, content-language: en-IN), no hreflang, no /fr/ etc. No i18n gap to report. If Indinoor later expands to NRIs/US (parent Isharya historically served US), revisit with hreflang + x-default.

---

5. Best Practices & Security

5.1 Security Headers (from curl -sI https://indinoor.in/)

Header	Value	Verdict
HSTS	max-age=7889238 (~91 days)	⚠️ Short. Recommend max-age=31536000; includeSubDomains; preload
X-Frame-Options	DENY	✅
X-Content-Type-Options	nosniff	✅
CSP	block-all-mixed-content; frame-ancestors 'none'; upgrade-insecure-requests;	⚠️ No script-src directive → PSI flags "Ensure CSP is effective against XSS attacks"; no Trusted Types
X-XSS-Protection	1; mode=block	✅ (legacy, harmless)
COOP	absent	⚠️ "Ensure proper origin isolation with COOP" (PSI)
Referrer-Policy	absent	Minor

Other: X-Download-Options: noopen, X-Permitted-Cross-Domain-Policies: none ✅. Cloudflare + Shopify edge. Verdict: solid baseline, missing the modern hardeners (script-src CSP, COOP, preload HSTS).

5.2 Modern Standards

• Valid HTML5, UTF-8 ✅. No document.write observed.
• Third-party cookies: PSI "Uses third-party cookies (3 cookies found)" + "Browser errors logged to console" — the _shopify_* cookies are first-party; the flag is likely GoKwik/checkout cookies (expected for Shopify). Low risk.
• Deprecated APIs: 2 warnings (PSI) — update libs.
• Low-resolution images served (PSI) — some CDN images delivered below display resolution (likely the srcset/thumbnail mismatch on grid cards).
• Lighthouse Best Practices score: 50/100 (dragged down by CSP/COOP/HSTS + low-res images).

---

6. Content Quality Assessment

6.1 Image Quality & Authenticity

• No AI-generated images detected (checked PDP + homepage image filenames against Gemini/ChatGPT/Picsart/ai0_/unnamed_1 patterns) — product photography is real, on-brand for "House of Isharya craft heritage." ✅ No brand-authenticity mismatch.
• Image delivery is the quality problem, not fakeness: oversized hero + grid images (2,421 KiB savings) and low-res served images hurt perceived polish on mobile.

6.2 Trust Signals

• Strong on paper (phone/email/address, GST/CIN, return + warranty, policies) but under-leveraged on-site: no social links, no reviews surfaced, no local-business entity markup. For an imitation-jewellery buyer (high risk-perception, low ticket), the missing reviews + social proof is the conversion leak.

6.3 Breadcrumb Navigation

• Absent visually and in schema on homepage, PDP and collections. Wayfinding + SERP breadcrumbs both missing.

6.4 Review / Social Proof

• Review apps Loox and Kla are installed (found in PDP HTML) but no review markup or visible aggregate rating is server-rendered — reviews are client-side only, invisible to crawlers and absent from rich results. The business analysis noted "limited visible star ratings" — confirmed.

---

7. Priority Recommendations

🔴 Immediate (This Week)

#	Issue	Impact	Effort
1	Add a real <h1> to the homepage template (keyword-bearing, visible)	Accessibility A + on-page SEO + wayfinding	Low (theme edit)
2	Fix Organization sameAs — populate Instagram/Facebook URLs or remove 9 empty entries	Entity graph trust / rich results	Low
3	Add og:image to homepage + switch all og:image to https://	Social share previews (90 Meta ads depend on this)	Low
4	Turn on Loox/Kla server-side review rendering + AggregateRating/Review JSON-LD on PDPs	Star rich-results, trust, CRO	Medium (app config)
5	Add BreadcrumbList schema + visual breadcrumbs to PDP/collections	SERP nav + UX	Medium

🟡 Short-Term (This Month)

#	Issue	Impact	Effort
6	Optimize hero + grid images (AVIF/WebP, srcset, right-size, don't lazy-load LCP)	Mobile LCP ~25 s → target < 4 s; +2,421 KiB	Medium
7	Defer non-critical JS (Cooee/Return Prime/Shiprocket), inline critical CSS	TBT 2,660 ms → < 600 ms	High
8	Reduce preconnect to 2–3 origins; remove duplicate cdn.shopify.com	LCP priority	Low
9	Add unique meta descriptions + OG tags to all 247 collections	Festive discovery CTR/SEO	Medium (bulk)
10	Add LocalBusiness/JewelryStore schema (Mumbai address, tel, geo)	Local + entity signal	Medium
11	Fix empty/redundant alt text on product imagery; name wishlist/search/cart buttons	Accessibility A/AA	Medium

🟢 Long-Term (This Quarter)

#	Issue	Impact	Effort
12	Harden CSP (script-src), add COOP, extend HSTS to preload	Security best practices 50 → 90+	Low–Med
13	Root-cause the June 2026 mobile regression; add a Lighthouse CI guard	Prevent future Poor windows during festive peak	Medium
14	Link social channels in footer (Instagram 94K, Facebook)	Trust + cross-channel + sameAs consistency	Low
15	Add ItemList schema to collection pages	Collection rich results	Med
16	Contrast + touch-target fixes from PSI	Accessibility 78 → 90+	Med

---

Summary Score Card

Category	Score	Grade	Basis
Performance (Mobile)	28/100	🔴	LCP 25.2 s (lab), field LCP recovering to 2.9 s (Needs Improvement)
Performance (Desktop)	42/100	🔴	LCP 3.4 s, TBT 2,830 ms
Accessibility	78/100	🟡	No homepage H1, alt/button/iframe/contrast fails
Best Practices	50/100	🟡	Weak CSP/COOP/HSTS, low-res images, deprecated APIs
SEO	92/100	🟢	Clean crawl/index/canonical; gaps in OG/meta-desc/collections
Content Quality	65/100	🟡	Genuine images, but no reviews/social/breadcrumbs surfaced
UX (trust/nav)	60/100	🟡	Strong policy/contact info, weak social proof + breadcrumbs
Security	75/100	🟡	HSTS/XFO/nosniff present; CSP/COOP incomplete
Overall	~55/100	🟡	Solid foundations; mobile perf + a11y + trust depth are the gaps

---

Sources & Citations

All data captured 2026-08-24. Every figure above is from a live fetch:

• HTTP headers / security: curl -sI https://indinoor.in/ — HSTS max-age=7889238, X-Frame-Options DENY, X-Content-Type-Options nosniff, CSP block-all-mixed-content; frame-ancestors 'none'; upgrade-insecure-requests;, server Cloudflare + Shopify, content-language: en-IN.
• robots.txt / sitemap: curl https://indinoor.in/robots.txt and sitemap.xml (+ child sitemaps) — 2,179 product URLs (3 files), 247 collections, 56 blogs, 12 pages; Sitemap directive present.
• CrUX field CWV (phone): https://cruxvis.withgoogle.com/#/ origin https://indinoor.in — graphics-symbol aria-labels, windows 2025-10-26 → 2026-08-22; peak Poor LCP 5,834 ms (2026-07-05→08-01), latest 2,914 ms (2026-07-26→08-22). Desktop/tablet below sampling threshold (audience 92 % phone per business-analysis.md §5a).
• Lighthouse lab data: https://pagespeed.web.dev/ — report 2026-08-24 11:32 UTC, Lighthouse 13.4.1. Mobile (Moto G Power, Slow 4G): Performance 28, Accessibility 78, Best Practices 50, SEO 92; FCP 5.0 s, LCP 25.2 s, TBT 2,660 ms, CLS 0, SI 11.7 s. Desktop: Performance 42; FCP 0.7 s, LCP 3.4 s, TBT 2,830 ms, SI 3.8 s. Insights: image delivery 2,421 KiB, render-blocking 170 ms, payload 9,595 KiB, main-thread 13.0 s, 20 long tasks, unused JS 1,672 KiB.
• JS-rendered DOM (homepage): browser_console on https://indinoor.in/ — 0 <h1>, 8 <h2>, <title> 65 char, lang="en", viewport present, canonical self-ref, meta description present, og:tags (site_name/url/title/type/description) no og:image, twitter:card summary_large_image, JSON-LD = Organization + WebSite, Organization sameAs = 9 empty strings, 83 imgs (1 no-alt, 41 empty-alt), 115 scripts, 14 stylesheets, 2,944 elements, 0 social hrefs.
• PDP: curl https://indinoor.in/products/zia-everyday-silver-studs (559 KB) — title "925 Sterling Silver Pearl Stud Earrings – Indinoor", meta description present, og:image http://…, canonical self-ref, JSON-LD Product + Offer + Brand + Organization, no BreadcrumbList/AggregateRating/Review/ItemList/LocalBusiness, 103 <img> (4 no-alt, 72 empty-alt), Loox + Kla review-app signatures present (client-side only).
• Collection: curl https://indinoor.in/collections/rakhi-ready (1.07 MB) — title "Rakhi-Ready – Indinoor", no meta description, no og:image, canonical self-ref, JSON-LD = Organization only (no BreadcrumbList/ItemList), 72 product links, 0 ?variant= pollution.
• Business context: /root/cro-reports/indinoor/20260824-164637/business-analysis.md (§5a device split, §16 performance flag, §17 social, §15 reviews gap).