Repair2Door — Site Extraction Dashboard

🔒 Fetch Tool Reported Blocked Access — Content Recovered via Direct HTTP Requests

Two automated fetch-tool attempts produced blocked-access markdown files (sources 8 & 9) and were excluded from analysis. As a fallback, direct HTTP GET requests to https://repair2door.base44.app/ succeeded, returning the full homepage HTML. Linked assets (JS bundle, CSS, manifest.json, asset_urls.json) were subsequently recovered and parsed. All extracted content therefore originates from 6 successfully accessed sources out of 9 inventoried. The uploaded-files directory was empty — no user-supplied reference documents contributed to the analysis.

📄

Content Records

100

Extracted across all page sections

8 distinct sections

✅

Sources Used

of 9 inventoried sources

67% utilisation rate

🚫

Excluded Sources

2 blocked fetch + 1 empty upload dir

33% not usable

🔗

Anchors Found

#coverage #filter #process #services #track #getrandomvalues-not-supported

From JS bundle

Coverage & Source Analysis

Source Inventory — Type & Access Outcome

All 9 inventoried sources plotted by type and access result. Green = used; blue = reachable but raw; amber = empty; red = blocked.

Content Records by Section

How the 100 extracted records distribute across the 8 identified homepage sections.

Content-Type Distribution

Breakdown of the 9 content-type labels assigned to the 100 records.

Confidence & Data Quality

Extraction Confidence Split

12 high-confidence metadata records vs 88 medium-confidence JS-inferred records.

Quality & Limitations

12 High-Confidence Records — These are structured metadata sourced directly from HTML tags: <title>, Open Graph meta fields, canonical URL, and manifest.json app properties. They are reliable ground truth requiring no inference.

88 Medium-Confidence Records — Extracted by parsing inline string literals from the compiled JS bundle. While the bundle contains genuine UI copy (service names, workflow steps, coverage claims), it also includes framework noise: React runtime error strings, Tailwind CSS class names embedded as template literals, UUID library warnings, and transport error messages. These records are directionally accurate but should not be treated as clean editorial copy.

Fetch Tool Blocked — Two fetch-tool attempts returned blocked-access markdown files. These were excluded entirely. The raw-HTTP workaround was successful for static asset recovery, but dynamic/server-rendered content and JS execution context are unavailable.

No Uploaded Files — The upload directory was empty. No cross-validation against internal documentation or product specs was possible.

Overall confidence is mixed. Metadata is reliable; JS-parsed copy is indicative but noisy. Treat service descriptions and workflow steps as structurally probable rather than verbatim editorial.

Findings — Product Positioning & Service Workflow

🌟 Brand Positioning

Brand name: Kinetic Repair Network

Core tagline: “An elite nationwide mobile surgical unit providing precision-engineered device restoration for all of Algeria.”

Hero copy: “Une Précision Chirurgicale” (A Surgical Precision)

Geography: Algeria-wide — all 58 Wilayas, from the Mediterranean coast to the Sahara. Geographic coverage is a primary differentiator (“58 Wilayas. Zéro Excuses.”).

Core value proposition: Door-to-door mobile phone repair — collect device from customer's home, repair with OEM parts, deliver back. No travel required.

Key guarantees extracted:

12-month warranty on all repairs (free repeat fix if fault recurs)
Original (OEM) parts only — no third-party components
Transparent pricing — no hidden fees
Data privacy — devices handled under strict protocols, data never accessed

Languages: Primarily French; at least one Arabic-language UI string detected (OLED/LCD restoration description), suggesting a bilingual interface.

🔎 Service Catalogue & Repair Workflow

Repair types offered (inferred from JS bundle):

Screen repair — OLED & LCD restoration, factory-quality screens, zero dead-pixel guarantee
Battery replacement — OEM lithium cells, full calibration included
Charging port — micro-soldering, USB-C / Lightning / legacy connectors
Camera module — front & rear replacement, lens glass & sensor repair
Water damage — ultrasonic board cleaning, corrosion removal, trace repair
Logic-board / micro-soldering — component-level IC replacement, data recovery

Six-step service pipeline (from process section):

Device & Damage Selection

Instant Transparent Quote

Collection Agent Dispatch

Microscopic Diagnosis

Precision Repair

Door Delivery + 12-Month Warranty

Real-time tracking: Customers enter a ticket number to see device status at every pipeline stage, from bench to door (“Suivre Votre Réparation”).

Source Inventory

Full Source Inventory (9 Sources)

All inventoried sources with type, access outcome, coverage classification, and notes.

#	Source / Path	Type	Access Status	Coverage	Notes
1	https://repair2door.base44.app/	URL	reachable via HTTP	Full	Live homepage — direct HTTP GET succeeded; used as primary source
2	homepage.html	HTML	used	Full	Raw HTML saved from HTTP response — source of all 12 high-confidence metadata records
3	manifest.json	JSON	used	Full	PWA manifest: app name, short name, icons, theme colour, start URL
4	index-CObJwx-8.js	JS Bundle	used	Full	Main React bundle — source of 88 medium-confidence records; contains UI copy and framework noise
5	index-kicYrbUR.css	CSS	used	Full	Tailwind CSS bundle — design tokens only; no content records extracted
6	asset_urls.json	JSON	used	Full	Asset URL index from build manifest; confirms asset list
7	/data/files/ (upload dir)	Upload Dir	empty — not used	Excluded	Directory present but contained no files; zero records contributed
8	fetch_repair2door…_171114.md	Fetch Markdown	excluded — fetch blocked	Excluded	Fetch tool attempt 1 — access denied; file excluded from all analysis
9	fetch_repair2door…_171909.md	Fetch Markdown	excluded — fetch blocked	Excluded	Fetch tool attempt 2 — access denied; file excluded from all analysis