← Back to Executive Summary

SEO & Quality Audit

Performance, accessibility, SEO, security headers

SEO & Quality Audit: NativeSpecial (nativespecial.com)

Website: https://nativespecial.com/ (in India redirects to /in/) Date of Audit: July 2, 2026 Platform: WordPress (WooCommerce + Elementor Page Builder) Host: Automattic wpcloud / WordPress VIP (Premium Enterprise Hosting) Industry: Food & Beverage (Traditional South Indian Sweets & Snacks Aggregator)

Executive Summary

NativeSpecial is an omnichannel regional brand aggregating traditional South Indian sweets and snacks, sourcing directly from geographic origins of heritage master-craftsmen (e.g., Tirunelveli Ghee Halwa, Srivilliputhur Milk Ghova).

A comprehensive technical and quality audit was conducted on nativespecial.com using external diagnostic engines and direct browser DOM evaluation. The site benefits from high-availability, enterprise-grade hosting infrastructure provided by Automattic (wpcloud / WordPress VIP) with server-side caching (Batcache) and pre-configured HSTS.

However, several critical server-level misconfigurations, severe technical SEO blunders (including a keyboard-mashed homepage description and a completely broken robots.txt file), heavy DOM bloat, and standard accessibility barriers severely drag down search visibility and mobile user experience.

Most notably, mobile performance is in the "Poor" category, with an LCP of 7.5 seconds on mobile (3.0× slower than the recommended threshold), caused directly by lazy-loading the primary above-the-fold hero product image—creating a massive 3-second resource load delay. Additionally, the /gb/ (United Kingdom) subdirectory blocks search crawlers with aggressive bot-detection pages, completely breaking their international hreflang configuration.

Technical Performance Summary Card

Audit Category Mobile Score Desktop Score Rating / Grade Business Impact
Performance 35 / 100 71 / 100 🔴 Poor (Mobile) / 🟡 Needs Improvement (Desktop) Lowers mobile conversion rates; increases cart bounce.
Accessibility 79 / 100 80 / 100 🟡 Needs Improvement Exposes brand to WCAG compliance issues; degrades screen-reader UX.
Best Practices 73 / 100 77 / 100 🟡 Needs Improvement Missing standard security headers; console errors active.
SEO 92 / 100 85 / 100 🟢 Good (Score inflated, see Critical Findings) Keyboard-mashed metadata and broken robots.txt severely limit actual rank potential.
Overall Grade 57 / 100 78 / 100 Grade: D (Mobile) / C+ (Desktop) High optimization leverage. Substantial ROI from technical fixes.

Note on Mobile vs. Desktop Gap: The Mobile Performance score (35) is 2.0× lower than Desktop Performance (71). This represents a severe gap, meaning mobile users—who account for 64.05% of all traffic (field-user diagnostics)—suffer a significantly degraded experience characterized by 4.5× slower loading starts and heavy main-thread freezing.

1. Performance Audit

1.1 Field-User Experience Diagnostics

Source: cruxvis.withgoogle.com (Historical Field-User Database)

Google's public user-experience field database has returned "N/A" (No Data Available) for all Core Web Vitals metrics on nativespecial.com for recent 2026 periods. This indicates that the domain's monthly traffic volume has recently fallen below Google's public reporting threshold (~500–1,000 monthly trackable Chrome page loads).

However, historical field-user diagnostics from late 2025 (the most recent period with sufficient reporting volume) reveals baseline real-world mobile behavior:

  • Largest Contentful Paint (LCP): 3,344 ms (3.3s) (Needs Improvement - target is ≤ 2.5s)
  • Interaction to Next Paint (INP): 90 ms (Good - target is ≤ 200s)
  • Cumulative Layout Shift (CLS): 0.00 (Good - target is ≤ 0.10)

Because current real-world field data is suppressed due to traffic thresholds, all current performance insights are evaluated using lab-simulated diagnostic data from https://pagespeed.web.dev/, which simulates a mid-tier mobile device on a cellular connection.

1.2 Core Web Vitals & Speed Metrics (Lab-Simulated Diagnostics)

Source: pagespeed.web.dev (Lab Diagnostics)

Both Mobile and Desktop performance metrics are extracted simultaneously, revealing a severe degradation on mobile devices:

Metric Mobile Value Desktop Value Good Threshold Status (Mobile / Desktop)
First Contentful Paint (FCP) 5.0 s 1.1 s ≤ 1.8 s 🔴 Poor / 🟢 Good
Largest Contentful Paint (LCP) 7.5 s 2.2 s ≤ 2.5 s 🔴 Poor / 🟢 Good
Total Blocking Time (TBT) 1,150 ms 250 ms ≤ 200 ms 🔴 Poor / 🟡 Needs Improvement
Speed Index (SI) 9.1 s 3.1 s ≤ 3.4 s 🔴 Poor / 🟢 Good
Cumulative Layout Shift (CLS) 0.024 0.010 ≤ 0.10 🟢 Good / 🟢 Good

1.3 LCP Phase Breakdown (Mobile)

Largest Contentful Paint (LCP) measures when the primary content element on the page becomes visible. On the NativeSpecial homepage, the LCP element is identified as the Featured Products image container (specifically, the image for "All Snacks" at /wp-content/uploads/2026/04/All-snacks-300x300.png).

The LCP time of 7.5 seconds is broken down into four distinct phases:

[ LCP: 7,500 ms Mobile Timeline ]
├─ TTFB: 310 ms (4.1%) ───► Extremely fast server response
├─ Resource Load Delay: 3,010 ms (40.1%) ───► CRITICAL BOTTLENECK (Image Lazy-Loaded above the fold)
├─ Resource Load Duration: 40 ms (0.5%) ───► Fast download (Automattic CDN)
└─ Remaining Main-Thread / Render Delay: 4,140 ms (55.3%) ───► Thread-blocking JS and CSS rendering delay
  • Time to First Byte (TTFB): 310 ms (Excellent). The premium Automattic wpcloud host responds incredibly fast.
  • Resource Load Delay: 3,010 ms (Extremely Poor). The browser waits 3.0 seconds before starting to download the LCP image. Why? The WordPress theme has applied loading="lazy" to the above-the-fold Featured Products images. Because of lazy loading, the browser does not preload the image. It has to wait for stylesheets to download, parse the DOM, build the layout, and determine if the image is in the viewport before requesting it.
  • Resource Load Duration: 40 ms (Excellent). Sits on a highly optimized CDN, so once the image is requested, it downloads instantly.
  • Remaining Render Delay / Thread Blocking: 4,140 ms (Poor). The browser spent over 4 seconds parsing heavy CSS/JS and executing script files, freezing the main layout render pipeline.

1.4 Technical Performance Issues by Impact

🔴 Critical Impact (Est. Savings: >1.5s)

  1. LCP Image Lazy-Loaded Above-the-Fold
    • Evidence: The primary LCP image All-snacks-300x300.png has loading="lazy" decoding="async" attributes applied.
    • Friction: Delays image discovery by 3,010 ms.
    • Recommendation: Remove loading="lazy" from all images appearing in the first viewport (such as hero banners and the first row of Featured Products). Add fetchpriority="high" to a tag in the HTML <head> for these image paths.
  2. Render-Blocking First-Party Scripts & Styles
    • Evidence: Est. savings of 4,220 ms on Mobile (650 ms on Desktop). The homepage loads several blocking resources in the critical rendering path:
      • jquery/jquery.min.js?ver=3.7.1 (31.2 KiB, 1,480 ms duration)
      • dashicons.min.css?ver=7.0 (34.9 KiB, 2,460 ms duration)
      • Multiple plugin styles/scripts: nsp-sales-order-query-api-public.js, wordpress-geo-ip-url-redirect-public.js, nsp-express-order-form-public.js.
    • Friction: Blocks DOM construction, stalling first-paint times for 4.2 seconds.
    • Recommendation: Consolidate, defer, or async all non-essential scripts. Dashicons should be completely disabled on the frontend.
  3. Severe DOM Bloat (Excessive Node Count)
    • Evidence: The homepage contains 3,268 DOM elements, with a maximum depth of 21 levels.
    • Friction: Standard e-commerce target is < 800 nodes. High node counts cause severe mobile CPU strain, leading to Style and Layout calculation times of 728 ms and contributing heavily to the 5.0 s main-thread freeze. This is a classic symptom of unoptimized nesting within the Elementor Page Builder.
    • Recommendation: Audit the Elementor templates. Eliminate redundant wrapping columns and nested sections. Switch from traditional divs to clean flexbox containers.

🟡 High Impact (Est. Savings: 200ms - 1s)

  1. Unoptimized PNG Banners & Product Category Images
    • Evidence: Est. savings of 751 KiB on Mobile (776 KiB on Desktop). Culprits include NATIVE-GROCERIES-UPDA… (177.9 KiB, could save 163.3 KiB) and various category banners.
    • Friction: Slower downloads over high-latency mobile networks.
    • Recommendation: Convert all PNG product and category graphics to WebP or AVIF formats. Apply compression and specify responsive srcset attributes so mobile users don't download desktop-resolution files.
  2. Unused CSS & Duplicate Framework Stylesheets
    • Evidence: Est. savings of 171 KiB. bootstrap.min.css is loaded twice from maxcdn.bootstrapcdn.com (representing 45.9 KiB, with 97%+ unused!). dashicons.min.css contributes 34.3 KiB of 100% unused CSS. woocommerce.css and Elementor's frontend.css have 90%+ unused rates on the homepage.
    • Friction: Unnecessary resource overhead.
    • Recommendation: Remove duplicate Bootstrap imports. Dequeue unused stylesheets on the homepage (such as WooCommerce block styles or administrator Dashicons) using WordPress asset optimization hooks.
  3. Unused JavaScript Bloat
    • Evidence: Est. savings of 553 KiB. Unused JS is loaded from third-party chat widgets, social trackers, and Elementor frontend scripts.
    • Recommendation: Implement delay-loading for heavy scripts (like chat widgets) so they only load upon user interaction (first tap or scroll).

1.5 Resource Transfer Summary

Category Transfer Size (KiB) Main-Thread Time Performance Impact
Images ~1,200 KiB 180 ms High payload overhead on mobile.
JavaScript ~1,850 KiB 2,800 ms Severe blocker. Freezes mobile UI during compilation and execution.
CSS ~350 KiB 728 ms High layout recalculation overhead due to DOM size.
Third-Party ~1,250 KiB 1,189 ms Heavy script execution overhead (GTM, reCAPTCHA, LinkedIn).
Total Page Size 3,710 KiB (3.71 MB) 5,000 ms Excessive for an e-commerce homepage. Target size should be < 1.5 MB.

2. Accessibility Audit

2.1 Critical Accessibility Issues (🔴 Immediate Fix)

  1. Missing Accessibility Association on Form Select Elements
    • Evidence: Flagged in lab diagnostics under: "Select elements do not have associated label elements."
    • Friction: Visually impaired users using screen readers cannot understand the purpose or options of selection dropdowns (such as language, currency, or variant selectors) because they lack accessible labels.
  2. Icon-Only Links Missing Discernible Names
    • Evidence: Flagged under: "Links do not have a discernible name."
    • Friction: Social media icons (Facebook, Instagram, YouTube) and certain header utility icons are baked purely as font icons inside anchors (e.g. ). Screen readers read these as "Link, empty," providing zero context about where the link leads.
  3. Low Contrast Text (WCAG AA Failures)
    • Evidence: Flagged under: "Background and foreground colors do not have a sufficient contrast ratio."
    • Friction: Light gray text used on white backgrounds for secondary menus, footer links, and product meta info falls below the WCAG AA requirement of 4.5:1 contrast ratio, rendering it illegible for users with visual impairments or on screens under direct sunlight.

2.2 High Priority Accessibility Issues (🟡 Short-Term Fix)

  1. Undersized & Packed Mobile Touch Targets
    • Evidence: Flagged under: "Touch targets do not have sufficient size or spacing."
    • Friction: Essential mobile navigation buttons, quantity adjustment icons, and header utility links are smaller than the standard 48×48px touch size and sit too close together. This causes frequent accidental taps on adjacent items.
  2. Incorrect Heading Hierarchy Nesting
    • Evidence: Homepage contains 1 H1, 20 H2s, and 9 H3s, but they are not sequentially nested. The template jumps from H1 directly to H3 or H4 in various Elementor sections, completely bypassing H2.
    • Friction: Screen-reader users navigate pages by traversing headings. Breaking the hierarchy ruins page navigation structure.
  3. Missing Main Landmark Container
    • Evidence: Flagged under: "Document does not have a main landmark."
    • Friction: The page lacks a <main> landmark container wrapping the main content. Landmark regions help assistive tech users jump directly to relevant sections.

2.3 Positive Accessibility Findings

  • The homepage correctly declares <html lang="en-US"> in the DOM, allowing accurate screen-reader speech synthesis.
  • Viewport configuration is active: <meta name="viewport" content="width=device-width, initial-scale=1">, enabling proper mobile responsive scaling.
  • Star rating assets are correctly wrapped with readable texts inside standard accessibility properties (e.g. aria-label="Rated 4.60 out of 5 based on 1278 customer ratings").

3. SEO Audit

3.1 Technical SEO Baseline

Audit Check Status Verification Detail / Findings
Crawlability & Indexation 🟢 Passed Meta robots is set to index, follow. Canonical tags are self-referencing.
Sitemap Index 🟢 Passed Found at https://nativespecial.com/sitemap_index.xml (Served as Yoast XML, correctly structured, points to product/page sitemaps).
SSL Enforcement (HTTPS) 🟢 Passed Fully enforced sitewide.
Canonical Alignment 🟢 Passed Home page points correctly to https://nativespecial.com/in/ in India.
Robots.txt Configuration 🔴 CRITICAL FAIL /robots.txt redirects via 302 to /in/robots.txt which serves a full HTML page (the homepage template) instead of a plain-text file!

3.2 Key Technical SEO Blunders

🔴 Broken robots.txt Serving HTML Page

  • The Issue: Requesting /robots.txt returns an HTTP 302 redirecting to https://nativespecial.com/in/robots.txt. When fetched, this URL responds with HTTP 200 but serves the full HTML of the homepage (content-type: text/html) instead of a plain-text robots.txt file with search directives!
  • Business Impact: This is a major technical SEO error. Search engines (like Googlebot) expect a plain-text file with directives like User-agent: * and Disallow:. Receiving an HTML page instead of plain text confuses crawlers. Googlebot will treat this as an invalid robots.txt, which can halt crawling entirely or cause indexing of secure directories (such as /wp-admin/ or /cart/).
  • Correction: Create a physical, plain-text file at the server root named robots.txt containing standard search engine crawl directives. Instruct the server (nginx) to bypass WordPress rewrites for this static path and serve it as text/plain.

🔴 Keyboard-Mashed Metadata on the Homepage

  • The Issue: The <meta name="description"> on the homepage is set to:

content="df asdsd"

  • Business Impact: This is a severe configuration mistake. "df asdsd" is a literal keyboard-mash placeholder left behind during site construction or plugin setup. Google has indexed this placeholder, presenting it to prospective customers in search results as the primary snippet. This looks completely unprofessional and severely damages click-through rates (CTR) for their highest-value organic query (brand terms).
  • Correction: Immediately update the homepage meta description in Yoast SEO to a professional, keyword-rich snippet (e.g., "Discover authentic South Indian sweets and snacks online. Sourced directly from local village master-craftsmen, fresh and delivered worldwide.").

🟡 Truncated Title Tag Length

  • The Issue: The homepage title is:

NativeSpecial.com | Traditional sweets online, feel your native taste at home NativeSpecial.com (95 characters, 680 pixels).

  • Business Impact: Search engine title limits are strictly capped at 60 characters or ~600 pixels. At 95 characters, this title is severely truncated in search results, diluting keyword prominence. The redundant repetition of NativeSpecial.com at both the start and end of the title is spammy and unprofessional.
  • Correction: Shorten the title tag to: "Traditional South Indian Sweets & Snacks Online | NativeSpecial" (59 characters).

3.3 Structured Data / Schema Audit

A deep programmatic evaluation of structured data in the browser DOM revealed the following findings:

A. Yoast Schema Graph (Homepage)

Yoast SEO implements a clean, consolidated JSON-LD schema graph representing the site's identity:

  • WebPage: Links back to organization, webpage elements, and breadcrumbs.
  • WebSite: Correctly defines the search entrypoint (?s={search_term_string}) for sitelinks search boxes.
  • Organization: Fully formed.
    • Legal Name: Native Special Products Private Limited
    • Logo: Sits on a secure SSL path with specified height and width.
    • Social Accounts (sameAs): Links verified social media profiles (Facebook, X, LinkedIn, YouTube).

B. WooCommerce Product Schema (Product Page)

On product pages (such as /product/tirunelveli-nei-halwa-online/), WooCommerce correctly outputs standard Product structured data:

  • Correctly outputs name, sku, image, description, and offers (pricing 202.00 INR, in stock).
  • Correctly integrates aggregateRating (1278 reviews, rating 4.60) and 5 individual Review nodes.

C. Schema Gaps (Opportunities for Improvement)

  1. Missing brand Property in Product Schema
    • The Issue: The Product schema contains no brand field.
    • Business Impact: Google Search Console flags this as a validation warning, which can exclude listings from certain premium merchant features.
    • Correction: Map the brand field to "NativeSpecial" in WooCommerce's structured data settings or via filter functions.
  2. Complete Absence of LocalBusiness / Store Schema
    • The Issue: Despite running 14+ physical retail locations across South India, the site features no Store or LocalBusiness schema.
    • Business Impact: Misses out on strong local ranking signals and fails to link their online domain authority to physical retail locations in search results.
    • Correction: Add a dedicated Store locator page containing individual Store JSON-LD schemas with geographic coordinates, telephone numbers, and opening hours for each of their 14 locations.

4. International SEO & Localization

4.1 Hreflang Implementation & Integrity

The website declares an extensive hreflang configuration in its HTML <head> to target different regional versions:

  • x-default, en, and en-US pointing to the root https://nativespecial.com
  • en-IN pointing to /in/
  • en-GB pointing to /gb/
  • en-SG pointing to /sg/
  • en-AE pointing to /ae/
  • European Union countries (en-AT, en-BE, en-DE, etc.) pointing to /eu/

🔴 Critical Hreflang Failure (403 Forbidden on /gb/)

  • The Issue: Direct curl checks and headless automated requests to the /gb/ subdirectory (such as https://nativespecial.com/gb/) return HTTP 403 Forbidden errors.
  • Why? The server blocks automated crawler requests with browser-check challenge walls (such as Cloudflare or host-level WAF shields) for regional directories.
  • Business Impact: If Googlebot crawls the site from US IPs and encounters a 403 Forbidden wall or browser-challenge page on /gb/, it will fail to index the UK sub-site. If any target URL in the hreflang set is inaccessible or fails to return a 200 OK response, Google will completely ignore the hreflang set, rendering their entire international SEO strategy useless.
  • Correction: Whitelist Googlebot, Bingbot, and other verified search engine user-agents from challenge walls across all subdirectories, ensuring that every localized URL returns a direct, unhindered 200 OK.

5. Best Practices & Security Audit

5.1 Application-Level Security Headers

While the Automattic wpcloud nginx server is well-configured with HSTS (strict-transport-security: max-age=31536000), it fails to deliver crucial application-level security headers:

Header Present Found Value Security Impact Correction
HSTS Yes max-age=31536000 Forces SSL sitewide, protecting against man-in-the-middle attacks. None required (Excellent).
X-Frame-Options No — Exposes the checkout and login pages to clickjacking iframe overlays. Add X-Frame-Options: SAMEORIGIN.
X-Content-Type-Options No — Exposes users to MIME-sniffing drive-by downloads. Add X-Content-Type-Options: nosniff.
Content-Security-Policy (CSP) No — High exposure to cross-site scripting (XSS) via third-party scripts. Define a strict Content-Security-Policy.
Cross-Origin-Opener-Policy No — Leaves cross-origin assets vulnerable to side-channel timing attacks. Add Cross-Origin-Opener-Policy: same-origin.

6. Content Quality Assessment

6.1 Product Photography Authenticity

  • A complete audit of the homepage and product category listings was conducted to detect generic AI-generated graphics or placeholder images.
  • Findings: The site features zero AI-generated product images or low-quality stock photos for sweets and snacks. All photography consists of genuine, high-resolution product photos showcasing actual South Indian delicacies in unbreakable airtight boxes, which perfectly preserves brand authenticity and trust.

6.2 Banners with Baked-in Text

  • The Issue: The main hero banners (such as Kids-combo-banner-1.jpg.jpeg and Mobile-banner-.jpg.jpeg) contain heavily baked-in promotional text.
  • Friction: The text inside these graphics is completely invisible to search engines and is unreadable by screen readers due to poor file-naming alt texts (e.g. alt="Kids combo banner (1).jpg").
  • Recommendation: Separate the visual image assets from copy. Implement campaigns as clean, lightweight HTML overlays styled with CSS over compressed background images, ensuring that keywords remain indexable and fully accessible.

7. Priority Recommendations

🔴 Immediate (This Week - Critical SEO & Performance Fixes)

# Issue Proposed Solution Impact Effort
1 Broken robots.txt serving HTML page Create a static physical robots.txt file at the root. Configure nginx to serve it as text/plain bypassing WordPress rewrites. Critical (Restores crawl integrity) Low
2 Keyboard-mashed Meta Description on homepage Update Yoast SEO homepage meta description to a professional, keyword-rich snippet. Critical (Fixes SERP presentation/CTR) Low
3 LCP Hero Image Lazy-Loaded above fold Remove loading="lazy" from first-viewport images. Add fetchpriority="high" and <link rel="preload"> in head. Critical (Reduces LCP by ~2.0s–3.0s) Low
4 Crawler Block (403) on /gb/ subdirectory Whitelist verified search engine user-agents (Googlebot, Bingbot) from regional challenge walls. Critical (Restores hreflang indexation) Medium

🟡 Short-Term (This Month - Quality, Security & Schema Upgrades)

# Issue Proposed Solution Impact Effort
1 Missing security headers Configure nginx/WordPress to send X-Frame-Options, X-Content-Type-Options, and CSP headers. High (Closes security vulnerabilities) Low
2 Duplicate CSS / unused framework stylesheets Dequeue duplicate Bootstrap stylesheet imports on the frontend. Dequeue unused Dashicons CSS. High (Reduces payload and rendering freeze) Medium
3 Missing Recommended Schema fields Map WooCommerce Product schema to include brand property. Add Store structured data for 14+ locations. High (Fixes GSC warnings, boosts local SEO) Medium
4 Long, truncated homepage title tag Shorten title tag to <60 characters, removing redundant brand name repetition. Medium (Improves CTR and keyword prominence) Low

🟢 Long-Term (This Quarter - Infrastructure & UI Overhauls)

# Issue Proposed Solution Impact Effort
1 Extreme DOM Bloat (3,268 elements) Redesign homepage Elementor templates to eliminate redundant wrapper divs. Migrate to native Flexbox containers. High (Boosts mobile CPU rendering times) High
2 Image-baked text in campaign banners Rebuild hero banners using compressed background images with live, accessible HTML text overlays. Medium (SEO keyword ranking & accessibility) Medium
3 Delay-loading third-party widget JS Modify scripts (Wati WhatsApp chat widget) to only initialize upon first user interaction. Medium (Speeds up mobile paint timelines) Medium

8. Cited Sources

  • https://nativespecial.com/ — Target site checked for DOM structures, image alt texts, hreflang head tags, and structured data blocks.
  • https://nativespecial.com/robots.txt — Request headers, HTTP redirects, and returned HTML responses verified using curl.
  • https://nativespecial.com/sitemap_index.xml — Yoast XML index structure, content-type and robots headers checked.
  • https://pagespeed.web.dev/ — Laboratory Core Web Vitals scores and performance audits generated on July 2, 2026.
  • https://cruxvis.withgoogle.com/#/ — Historical Core Web Vitals field data trends from late 2025 parsed.
  • C:\My\Work\Ecom Automation\Agentic\results\nativespecial\business-analysis.md — Leveraged for business positioning, geographic store count, and device composition metrics.
  • C:\My\Work\Ecom Automation\Agentic\results\nativespecial\traffic-estimation.md — Consultation for similarweb.com traffic baselines, woorank.com SEO findings, and visitor demographics.
© 2026 Quietcom. Confidential. NativeSpecial Audit Report