Comprehensive
Technical Analysis
Diagnosing Crawl Health and Infrastructure for senz.sa.
Overall Site Health
Solid Foundation with Systemic Gaps
Solid Base
Clean crawl, healthy response codes, no true orphan pages.
Security Gaps
Almost complete absence of server-level security headers.
Diagnostic Dashboard: 8 Criteria
| Crawlability & Bot Accessibility | 9.5/10 (Excellent) |
| Internal Response Codes Health | 7.5/10 (Very Good) |
| Internal Linking & Discovery | 6.0/10 (Acceptable) |
| Basic Meta Elements Quality | 5.5/10 (Acceptable) |
| Content & Image Optimization | 5.5/10 (Acceptable) |
| Issue Severity Distribution | 5.0/10 (Acceptable) |
| Indexing & Canonical Integrity | 4.5/10 (Poor) |
| Site-wide Security Headers | 3.0/10 (Critical) |
Absence of Server-Level Protection
While HTTPS is perfectly implemented, crucial security headers protecting the user and the store are missing.
100% HTTPS
Zero mixed content. Encryption is fully active.
Referrer-Policy
Controls how much referrer info is passed.
X-Frame-Options
Leaves site vulnerable to Clickjacking attacks.
CSP Header
Content-Security-Policy absent against XSS.
Consultant Insight
These gaps don't represent a direct SEO penalty, but rather a severe security and trust risk for an e-commerce platform processing user data. Fixing requires a single server-level or Cloudflare configuration, not page-by-page edits.
Redirects & Routing Health
Diagnostic Monitoring of Link Equity and Flow.
Anatomy of Redirects: Diagnostic Monitoring System
Overall Redirect Volume
Score: 7.0/10Single hop (Optimal Behavior). The vast majority of links work perfectly.
Two-hop chains. The challenge is isolated to 74 unique URLs causing these repeated chain instances.
The 43-Case Illusion
Score: 8.0/10301
302
Unified Root Cause
Updating just one single link in the shared global footer template will instantly resolve all 43 instances of redirect chains across the entire website. There are zero internal redirect chains.
Internal vs External
8.5/1093.6% resolve successfully (200). Full team control.
High volume is purely an artifact of repeated social media icons (WhatsApp, Facebook).
Code Integrity: 301 vs 302
9.5/10100% Technical Accuracy: The 302s are justified (Payment sessions & Cloudflare). No permanent moves are using the wrong code.
Final Destination (Code 0)
9.0/10These are WhatsApp app-links and dynamic Payment Sessions. Do not fix these. The behavior is correct and protects user sessions from bot manipulation.
The Bottleneck: Legacy Links
Score: 5.0/10Of old URLs are still being used directly within internal navigation elements instead of their modern counterparts.
Culprit Identified
Bundles & Packages Pages: These specific templates are pulling legacy sub-product links, forcing browsers into unnecessary redirect hops.
Technical Debt Map: The 43 Legacy Link Types
1. Old Numeric Barcode
55 CasesExample: /...6287053630048
22% suffer from double-encoding.
2. Old Arabic Slug
17 CasesExample: /ar/[Arabic-Text]/
3. Old Short Slug
10 CasesExample: /c/- or /p/-
4. Old Prefix
8 CasesExample: /p/
The page "ultimate-care-bundle" alone contains 18 instances of these outdated links.
Page-Level Redirect Check
Score: 10.0 / 10Pages Passed Successfully
Zero pages contain redirects in their primary loading path. Browsers do not need to process extra hops before requested pages begin rendering. Perfect PageSpeed impact.
Routing Action Plan (Near/Medium Term)
Immediate (High Impact)
- Update the Facebook icon link in the global footer to `senz.care` (Instantly solves 43 chain errors).
- Document the intentional "Code 0" exception for WhatsApp and Payment links to prevent mistaken future developer edits.
Medium Term
- Update the 43 legacy internal links directly in the CMS content, prioritizing numeric barcodes, then Arabic slugs.
- Investigate the source of double-encoding (25%) affecting 5 links inside the "Related Products" widget template.
Hreflang & Language Targeting
Diagnostics of Internationalization Tags.
Technical Anatomy: How Hreflang Should Work
Source Page
The starting point for every targeting relationship.
Code embedded in the HTML header declaring an alternate version exists.
Destination
The live URL (HTTP 200) representing the alternate version.
The Scope of the Problem
1/5th of the site carries broken Arabic tags:
- 19.74% of total internal pages (15 unique pages out of 76).
- 17 total instances (includes duplicates due to tracking parameter `_svs=embed-card`).
- 100% of cases use the `ar` value exclusively.
There is no random pattern here. The scope of the problem is strictly limited and closed to a single language value (`ar`). The remaining pages (80.26%) are completely unaffected, making a bulk fix highly realistic and quick to execute.
Hidden Symptoms: Silent Directives
These tags confuse search engines while remaining invisible to users.
Bot View
...
User View
100% of cases are unlinked. There is no broken language switcher button. Real visitors will never encounter these links.
100% of the cases are hidden in Rendered HTML and return a Permanent Redirect (301). Zero 404 or 500 errors.
The Root Cause: Self-Referencing Loops
Remnants of a previous linguistic structure.
- 15 out of 15 unique cases refer back to the exact title of the source page verbatim.
- Zero (0) cases lead to an actual separate Arabic page.
The site currently has a single-language structure, but the code still declares a bilingual hierarchy. This technical residue traps the search engine crawler in a closed loop, returning it to the starting point.
One Strategic Decision, One Unified Fix
Is there an actual plan to launch a separate regional/language version?
Immediate Fix
Completely remove the Hreflang tag from the Product Template. (Saves maintenance effort).
Structural Fix
Update the destination inside the tag to point to the actual separate Arabic URLs.
Coordinated with the task of cleaning up legacy links in Chapter 2, executing this fix during the same optimization sprint will immediately raise the score of this chapter to approximately 8.5/10 without requiring any isolated programming effort.
The Annoying Illusion:
812 Errors or Just One?
At first glance, 812 Schema errors across 50 pages looks catastrophic (Score: 4.9/10). However, deep analysis reveals a domino effect. Commercial features (like Price and Ratings in search results) have a 96% failure rate due to a single, localized formatting issue.
The Root Cause (71.4% of all errors)
580 cases are caused by a localization function outputting Arabic/Hindi numerals instead of standard Latin numerals in the JSON-LD payload. Fixing this one function will instantly resolve over 90% of the merchant listing issues.
Core Web Vitals: A Tale of Two Metrics
Section Score: 4.9 / 10
LCP (Largest Contentful Paint)
Critical Status • Score: 2.0 / 10
Failure Rate
9.17s Average
The Prime Suspect
A single, massive icon font file (sallaicons.woff - 269KB) consumes up to 64% of the critical rendering path. It causes a render-blocking delay, freezing the main content.
CLS (Cumulative Layout Shift)
Near Perfect • Score: 9.0 / 10
Success Rate
0.018 Average
The platform handles space reservation for images and elements professionally. Zero annoying visual jumps during load time across almost all pages.
The Main Thread Traffic Jam
Average Main Thread processing time is an alarming 13.6 seconds per page. The issue isn't just one file, but a scattered responsibility across multiple parties.
CPU Time Distribution Sources
Surprisingly high overhead for security scripts.
Chapter Score
Critical Burden
Execution Roadmap: JS & Processing
Split app.css file and eliminate the duplicate Orion page and articles.
Salla Tech Support + SEO Team
Audit the overlap of security tools (Sift/Cloudflare) and clean up GTM container.
Tech Management + Marketing
Migrate towards Conversions APIs (Meta/TikTok) to eliminate heavy tracking pixels.
Digital Marketing Team
Chapter Score
TTFB Response
100% Failure Rate
Security Headers
99.7% Missing (X-Frame)
Internal Cache
99.9% Perfect Performance
Third Parties
26 Entities Consuming CPU
Network & Third Parties
The Tamara Anomaly
A single SVG logo for the payment gateway (Tamara) is sized at an absurd 741 KB. An SVG logo should typically be under 5KB.
Image Sizing Waste
96.4% of image waste is due to loading massive images (e.g., 2000x2000px) into tiny containers (240x240px) without using responsive `srcset` or an Image CDN. Total waste: 3.55 MB.
Container
Loaded Image
(Elite Fresh)
The browser is forced to download the massive file only to shrink it visually, wasting bandwidth and CPU time.
Cookie Security - A Point of Strength
Sensitive security cookies (like XSRF-TOKEN and _said_) are correctly configured with HttpOnly and Secure flags. Excellent security awareness.
Preconnect Opportunities
9 external domains are prime candidates for preconnect (DNS + TLS).
Potential early savings range between 300ms and 1,489ms per domain simply by adding a basic `` directive in the ``.
Architectural Shift: From Chaos to Sustainable Order
Current State
Slow loading / Wasted resources
Future Architecture (Long-term)
Image CDN
Structural Solution: Implement a responsive Image CDN to process image sizes automatically upon upload, eliminating 96% of size waste permanently.
Server-Side APIs
Structural Solution: Transition from heavy browser tracking pixels to Server-Side APIs (Conversions API), radically reducing JavaScript execution overhead and tracking burdens.
Urgent Recovery & Network Coordination Plan
Escalate TTFB
Top priority. Open an urgent ticket with Salla to resolve the 1.4-second initial server delay, which bottlenecks the entire site.
Global Security Shield
Activate X-Frame-Options and the missing security headers centrally via Cloudflare configuration.
The Free Win
Remove the duplicate Orion page to instantly wipe out 100% of the massive network payload warnings with a single click.
Marketing Sync
Audit external tools. Assess the CPU and caching burden of Facebook/Snapchat pixels to evaluate their ongoing ROI.
Platform Sync
Submit a unified request to Salla to address render-blocking resources and fix Google Fonts loading protocols.
Internal Tasks
Implement Preconnect directives for the 9 identified external domains, and secure the remaining 16 first-party cookies.
DOM Structure & Accessibility
Two sides of the same coin: Code structure vs Human experience.
Chapter Scorecard
Architectural Whitepaper: Core Concepts
| Term | Definition | Impact |
|---|---|---|
| DOM Tree | The internal structural representation of all HTML elements. | Excessive depth slows layout rendering and complicates maintenance. |
| ARIA Landmark | Tags defining major page regions (e.g., Main, Header, Footer). | Allows screen reader users to skip navigation and jump straight to content. |
| Contrast Ratio | The mathematical variance between text color and its background. | Weak contrast makes text unreadable for visually impaired or mobile users in sunlight. |
| Touch Target | The actual clickable physical area of an interactive element. | Tiny targets make accurate finger-tapping difficult, especially for the elderly. |
DOM Structure
The internal structural complexity of the page and how browsers/search engines read it. Every element consumes processing power and memory.
Accessibility
The actual user experience, especially for users with disabilities, screen readers, and touch browsing. Good accessibility practices are inherently good SEO practices. The crawler understands the site exactly as a screen reader does.
Catastrophic Exception (Orion Page)
Warning Threshold: 800 elements.
Duplicated Orion Page: 2,661 excessive elements!
The result: Unquestionably the heaviest page, carrying twice the volume of the next largest page (1,371 elements), and over 4x the site average (618).
The Biggest Structural Gap: Missing
Structural Data
- 98.68% of pages (75 of 76) completely lack a
landmark. - 76.32% of pages have content not contained within any structural landmark.
- 23.68% of pages have no H1 heading or Title tag.
User Impact
Without a tag, a screen reader user is forced to sequentially listen to every item in the header and menus every time a new page loads, unable to skip directly to the content.
Quick Win
A single code fix adding the tag to the base template instantly resolves the most critical violation across the entire site.
Clarity & Context: Reading and Interaction Challenges
Descriptive Texts & ARIA - Understanding
aria-label="Search"
Clear Context (ARIA)
- 17.11% of pages contain links without any text.
- 15.79% use non-allowed ARIA attributes (Critical).
Color Contrast - Visibility
75% of pages fall below the minimum contrast limit (AA).
The Touch Navigation Bottleneck (8x8px)
Actual Observed Size: 8x8 pixels (Only 12% of the required area).
Recommended Minimum (WCAG 2.2 AA): 24x24 pixels.
Source of Flaw: One specific element (Slider pagination dots span.swiper-pagination-bullet) accounts for 100% of these violations.
Quick Win
A local CSS Override to expand the click area to 24x24px completely resolves this metric across all pages permanently (click area can be expanded without changing visual size).
Data Cleansing: Tracking Link Ghosts
The Anomaly
19.74% (15 pages) were reported missing the HTML Lang attribute.
The Reality
These are not real content pages. Perfect match with the confirmed GTM noise (links to securemetric/GTM).
The Cascade Effect: The Orion Page Ghost
The duplicated version of orion-intimate-care-wash appeared as the worst technical anomaly across six different chapters of this comprehensive report. Removing this single duplicate yields the highest cumulative value across the entire architecture.
Page
Action Plan & Developer Taskforce
Add tag around the main content area in the template.
Modify CSS to enlarge slider touch targets to 24x24 pixels.
Review site color palette to meet (AA) contrast standards via design variables.
Correct ARIA properties and add aria-label to silent links.
Implement an Accessibility Checklist for any newly developed component.
Apply GTM crawl exclusion permanently to prevent data pollution.
Return on Effort: Rapid Performance Jump
(Solves 98.68% pages)
(Solves 100% targets)
Radical improvement in accessibility compliance with minimal programmatic intervention.
Conclusion of Comprehensive Technical Analysis
The eight chapters conclude with a clear technical truth: Structural Quality (Code) and Accessibility (Human) require the exact same foundations.
Remove Orion Duplicate
The highest cumulative impact across the entire site architecture.
Fix Font Files & Icons Sizes
Address the massive sallaicons.woff and bloated Tamara SVG logo.
Correct Structured Data (JSON-LD)
Fix the JSON-LD numeral format to unlock rich merchant listings.
Insert
Instant accessibility wins with the highest ROI on developer time.
Comprehensive
Technical Analysis
Diagnosing Crawl Health and Infrastructure for senz.sa.
Overall Site Health
Solid Foundation with Systemic Gaps
Solid Base
Clean crawl, healthy response codes, no true orphan pages.
Security Gaps
Almost complete absence of server-level security headers.
Diagnostic Dashboard: 8 Criteria
| Crawlability & Bot Accessibility | 9.5/10 (Excellent) |
| Internal Response Codes Health | 7.5/10 (Very Good) |
| Internal Linking & Discovery | 6.0/10 (Acceptable) |
| Basic Meta Elements Quality | 5.5/10 (Acceptable) |
| Content & Image Optimization | 5.5/10 (Acceptable) |
| Issue Severity Distribution | 5.0/10 (Acceptable) |
| Indexing & Canonical Integrity | 4.5/10 (Poor) |
| Site-wide Security Headers | 3.0/10 (Critical) |
Absence of Server-Level Protection
While HTTPS is perfectly implemented, crucial security headers protecting the user and the store are missing.
100% HTTPS
Zero mixed content. Encryption is fully active.
Referrer-Policy
Controls how much referrer info is passed.
X-Frame-Options
Leaves site vulnerable to Clickjacking attacks.
CSP Header
Content-Security-Policy absent against XSS.
Consultant Insight
These gaps don't represent a direct SEO penalty, but rather a severe security and trust risk for an e-commerce platform processing user data. Fixing requires a single server-level or Cloudflare configuration, not page-by-page edits.
Redirects & Routing Health
Diagnostic Monitoring of Link Equity and Flow.
Anatomy of Redirects: Diagnostic Monitoring System
Overall Redirect Volume
Score: 7.0/10Single hop (Optimal Behavior). The vast majority of links work perfectly.
Two-hop chains. The challenge is isolated to 74 unique URLs causing these repeated chain instances.
The 43-Case Illusion
Score: 8.0/10301
302
Unified Root Cause
Updating just one single link in the shared global footer template will instantly resolve all 43 instances of redirect chains across the entire website. There are zero internal redirect chains.
Internal vs External
8.5/1093.6% resolve successfully (200). Full team control.
High volume is purely an artifact of repeated social media icons (WhatsApp, Facebook).
Code Integrity: 301 vs 302
9.5/10100% Technical Accuracy: The 302s are justified (Payment sessions & Cloudflare). No permanent moves are using the wrong code.
Final Destination (Code 0)
9.0/10These are WhatsApp app-links and dynamic Payment Sessions. Do not fix these. The behavior is correct and protects user sessions from bot manipulation.
The Bottleneck: Legacy Links
Score: 5.0/10Of old URLs are still being used directly within internal navigation elements instead of their modern counterparts.
Culprit Identified
Bundles & Packages Pages: These specific templates are pulling legacy sub-product links, forcing browsers into unnecessary redirect hops.
Technical Debt Map: The 43 Legacy Link Types
1. Old Numeric Barcode
55 CasesExample: /...6287053630048
22% suffer from double-encoding.
2. Old Arabic Slug
17 CasesExample: /ar/[Arabic-Text]/
3. Old Short Slug
10 CasesExample: /c/- or /p/-
4. Old Prefix
8 CasesExample: /p/
The page "ultimate-care-bundle" alone contains 18 instances of these outdated links.
Page-Level Redirect Check
Score: 10.0 / 10Pages Passed Successfully
Zero pages contain redirects in their primary loading path. Browsers do not need to process extra hops before requested pages begin rendering. Perfect PageSpeed impact.
Routing Action Plan (Near/Medium Term)
Immediate (High Impact)
- Update the Facebook icon link in the global footer to `senz.care` (Instantly solves 43 chain errors).
- Document the intentional "Code 0" exception for WhatsApp and Payment links to prevent mistaken future developer edits.
Medium Term
- Update the 43 legacy internal links directly in the CMS content, prioritizing numeric barcodes, then Arabic slugs.
- Investigate the source of double-encoding (25%) affecting 5 links inside the "Related Products" widget template.
Hreflang & Language Targeting
Diagnostics of Internationalization Tags.
Technical Anatomy: How Hreflang Should Work
Source Page
The starting point for every targeting relationship.
<link rel="alternate" hreflang="ar" href="..." />
Code embedded in the HTML header declaring an alternate version exists.
Destination
The live URL (HTTP 200) representing the alternate version.
The Scope of the Problem
1/5th of the site carries broken Arabic tags:
- 19.74% of total internal pages (15 unique pages out of 76).
- 17 total instances (includes duplicates due to tracking parameter `_svs=embed-card`).
- 100% of cases use the `ar` value exclusively.
There is no random pattern here. The scope of the problem is strictly limited and closed to a single language value (`ar`). The remaining pages (80.26%) are completely unaffected, making a bulk fix highly realistic and quick to execute.
Hidden Symptoms: Silent Directives
These tags confuse search engines while remaining invisible to users.
Bot View
<html>
<head>
<meta charset="utf-8">
<link rel="alternate" hreflang="ar" href="..."/>
...
User View
100% of cases are unlinked. There is no broken language switcher button. Real visitors will never encounter these links.
100% of the cases are hidden in Rendered HTML and return a Permanent Redirect (301). Zero 404 or 500 errors.
The Root Cause: Self-Referencing Loops
Remnants of a previous linguistic structure.
- 15 out of 15 unique cases refer back to the exact title of the source page verbatim.
- Zero (0) cases lead to an actual separate Arabic page.
The site currently has a single-language structure, but the code still declares a bilingual hierarchy. This technical residue traps the search engine crawler in a closed loop, returning it to the starting point.
One Strategic Decision, One Unified Fix
Is there an actual plan to launch a separate regional/language version?
Immediate Fix
Completely remove the Hreflang tag from the Product Template. (Saves maintenance effort).
Structural Fix
Update the destination inside the tag to point to the actual separate Arabic URLs.
Coordinated with the task of cleaning up legacy links in Chapter 2, executing this fix during the same optimization sprint will immediately raise the score of this chapter to approximately 8.5/10 without requiring any isolated programming effort.
The Annoying Illusion:
812 Errors or Just One?
At first glance, 812 Schema errors across 50 pages looks catastrophic (Score: 4.9/10). However, deep analysis reveals a domino effect. Commercial features (like Price and Ratings in search results) have a 96% failure rate due to a single, localized formatting issue.
The Root Cause (71.4% of all errors)
580 cases are caused by a localization function outputting Arabic/Hindi numerals instead of standard Latin numerals in the JSON-LD payload. Fixing this one function will instantly resolve over 90% of the merchant listing issues.
Core Web Vitals: A Tale of Two Metrics
Section Score: 4.9 / 10
LCP (Largest Contentful Paint)
Critical Status • Score: 2.0 / 10
Failure Rate
9.17s Average
The Prime Suspect
A single, massive icon font file (sallaicons.woff - 269KB) consumes up to 64% of the critical rendering path. It causes a render-blocking delay, freezing the main content.
CLS (Cumulative Layout Shift)
Near Perfect • Score: 9.0 / 10
Success Rate
0.018 Average
The platform handles space reservation for images and elements professionally. Zero annoying visual jumps during load time across almost all pages.
The Main Thread Traffic Jam
Average Main Thread processing time is an alarming 13.6 seconds per page. The issue isn't just one file, but a scattered responsibility across multiple parties.
CPU Time Distribution Sources
Surprisingly high overhead for security scripts.
Chapter Score
Critical Burden
Execution Roadmap: JS & Processing
Split app.css file and eliminate the duplicate Orion page and articles.
Salla Tech Support + SEO Team
Audit the overlap of security tools (Sift/Cloudflare) and clean up GTM container.
Tech Management + Marketing
Migrate towards Conversions APIs (Meta/TikTok) to eliminate heavy tracking pixels.
Digital Marketing Team
Chapter Score
TTFB Response
100% Failure Rate
Security Headers
99.7% Missing (X-Frame)
Internal Cache
99.9% Perfect Performance
Third Parties
26 Entities Consuming CPU
Network & Third Parties
The Tamara Anomaly
A single SVG logo for the payment gateway (Tamara) is sized at an absurd 741 KB. An SVG logo should typically be under 5KB.
Image Sizing Waste
96.4% of image waste is due to loading massive images (e.g., 2000x2000px) into tiny containers (240x240px) without using responsive `srcset` or an Image CDN. Total waste: 3.55 MB.
Container
Loaded Image
(Elite Fresh)
The browser is forced to download the massive file only to shrink it visually, wasting bandwidth and CPU time.
Cookie Security - A Point of Strength
Sensitive security cookies (like XSRF-TOKEN and _said_) are correctly configured with HttpOnly and Secure flags. Excellent security awareness.
Preconnect Opportunities
9 external domains are prime candidates for preconnect (DNS + TLS).
Potential early savings range between 300ms and 1,489ms per domain simply by adding a basic `` directive in the ``.
Architectural Shift: From Chaos to Sustainable Order
Current State
Slow loading / Wasted resources
Future Architecture (Long-term)
Image CDN
Structural Solution: Implement a responsive Image CDN to process image sizes automatically upon upload, eliminating 96% of size waste permanently.
Server-Side APIs
Structural Solution: Transition from heavy browser tracking pixels to Server-Side APIs (Conversions API), radically reducing JavaScript execution overhead and tracking burdens.
Urgent Recovery & Network Coordination Plan
Escalate TTFB
Top priority. Open an urgent ticket with Salla to resolve the 1.4-second initial server delay, which bottlenecks the entire site.
Global Security Shield
Activate X-Frame-Options and the missing security headers centrally via Cloudflare configuration.
The Free Win
Remove the duplicate Orion page to instantly wipe out 100% of the massive network payload warnings with a single click.
Marketing Sync
Audit external tools. Assess the CPU and caching burden of Facebook/Snapchat pixels to evaluate their ongoing ROI.
Platform Sync
Submit a unified request to Salla to address render-blocking resources and fix Google Fonts loading protocols.
Internal Tasks
Implement Preconnect directives for the 9 identified external domains, and secure the remaining 16 first-party cookies.
DOM Structure & Accessibility
Two sides of the same coin: Code structure vs Human experience.
Chapter Scorecard
Architectural Whitepaper: Core Concepts
| Term | Definition | Impact |
|---|---|---|
| DOM Tree | The internal structural representation of all HTML elements. | Excessive depth slows layout rendering and complicates maintenance. |
| ARIA Landmark | Tags defining major page regions (e.g., Main, Header, Footer). | Allows screen reader users to skip navigation and jump straight to content. |
| Contrast Ratio | The mathematical variance between text color and its background. | Weak contrast makes text unreadable for visually impaired or mobile users in sunlight. |
| Touch Target | The actual clickable physical area of an interactive element. | Tiny targets make accurate finger-tapping difficult, especially for the elderly. |
DOM Structure
The internal structural complexity of the page and how browsers/search engines read it. Every element consumes processing power and memory.
Accessibility
The actual user experience, especially for users with disabilities, screen readers, and touch browsing. Good accessibility practices are inherently good SEO practices. The crawler understands the site exactly as a screen reader does.
Catastrophic Exception (Orion Page)
Warning Threshold: 800 elements.
Duplicated Orion Page: 2,661 excessive elements!
The result: Unquestionably the heaviest page, carrying twice the volume of the next largest page (1,371 elements), and over 4x the site average (618).
The Biggest Structural Gap: Missing <main> Landmark
Structural Data
- 98.68% of pages (75 of 76) completely lack a
<main>landmark. - 76.32% of pages have content not contained within any structural landmark.
- 23.68% of pages have no H1 heading or Title tag.
User Impact
Without a <main> tag, a screen reader user is forced to sequentially listen to every item in the header and menus every time a new page loads, unable to skip directly to the content.
Quick Win
A single code fix adding the <main> tag to the base template instantly resolves the most critical violation across the entire site.
Clarity & Context: Reading and Interaction Challenges
Descriptive Texts & ARIA - Understanding
<button class="icon-search"></button>
Silent (No Context)
aria-label="Search"
Clear Context (ARIA)
- 17.11% of pages contain links without any text.
- 15.79% use non-allowed ARIA attributes (Critical).
Color Contrast - Visibility
75% of pages fall below the minimum contrast limit (AA).
The Touch Navigation Bottleneck (8x8px)
Actual Observed Size: 8x8 pixels (Only 12% of the required area).
Recommended Minimum (WCAG 2.2 AA): 24x24 pixels.
Source of Flaw: One specific element (Slider pagination dots span.swiper-pagination-bullet) accounts for 100% of these violations.
Quick Win
A local CSS Override to expand the click area to 24x24px completely resolves this metric across all pages permanently (click area can be expanded without changing visual size).
Data Cleansing: Tracking Link Ghosts
The Anomaly
19.74% (15 pages) were reported missing the HTML Lang attribute.
The Reality
These are not real content pages. Perfect match with the confirmed GTM noise (links to securemetric/GTM).
The Cascade Effect: The Orion Page Ghost
The duplicated version of orion-intimate-care-wash appeared as the worst technical anomaly across six different chapters of this comprehensive report. Removing this single duplicate yields the highest cumulative value across the entire architecture.
Page
Action Plan & Developer Taskforce
Add <main> tag around the main content area in the template.
Modify CSS to enlarge slider touch targets to 24x24 pixels.
Review site color palette to meet (AA) contrast standards via design variables.
Correct ARIA properties and add aria-label to silent links.
Implement an Accessibility Checklist for any newly developed component.
Apply GTM crawl exclusion permanently to prevent data pollution.
Return on Effort: Rapid Performance Jump
<main> tag(Solves 98.68% pages)
(Solves 100% targets)
Radical improvement in accessibility compliance with minimal programmatic intervention.
Conclusion of Comprehensive Technical Analysis
The eight chapters conclude with a clear technical truth: Structural Quality (Code) and Accessibility (Human) require the exact same foundations.
Remove Orion Duplicate
The highest cumulative impact across the entire site architecture.
Fix Font Files & Icons Sizes
Address the massive sallaicons.woff and bloated Tamara SVG logo.
Correct Structured Data (JSON-LD)
Fix the JSON-LD numeral format to unlock rich merchant listings.
Insert <main> & Expand Touch Targets
Instant accessibility wins with the highest ROI on developer time.