Website audit scorecard for giulianaflores.com.br

HTTP 404 returned for sitemap_xml.

Failed: earned 0 of 12 points.

Priority: Priority 7: fix during launch polish.

Why it matters: A sitemap helps search engines discover the landing page and related public pages sooner.

Fix: Add /sitemap.xml with your public URLs and confirm it returns HTTP 200.

HTTP 404 returned for llms_txt.

Failed: earned 0 of 4 points.

Priority: Priority 24: lower-risk cleanup after urgent launch blockers.

Why it matters: A short LLM-readable file can help answer engines and AI tools summarize your product accurately.

Fix: Add /llms.txt or /.well-known/llms.txt with the product name, audience, value proposition, and key public links.

Detected 0 JSON-LD schema block(s).

Failed: earned 0 of 10 points.

Priority: Priority 12: fix during launch polish.

Why it matters: Structured data gives search and answer engines explicit facts about your product.

Fix: Add JSON-LD for SoftwareApplication, Product, Organization, or WebSite using only accurate public facts.

Detected 4 of 5 common public security headers. Present: strict-transport-security, content-security-policy, x-content-type-options, x-frame-options. Missing: referrer-policy.

Failed: earned 16 of 18 points from partial coverage.

Priority: Priority 5: fix before sharing the page publicly.

Why it matters: These headers reduce avoidable browser-side risk and show a baseline of care before launch.

Fix: Configure headers such as Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy.

A small allowlist probe returned a public success response.

Failed: earned 0 of 16 points.

Priority: Priority 1: fix before sharing the page publicly.

Why it matters: Publicly exposed config or backup files can leak implementation details or secrets.

Fix: Remove the exposed file, block public access to that path, and rotate any secrets that may have been exposed.

Detected labels or accessible names for 7 of 20 form control(s).

Failed: earned 0 of 14 points.

Priority: Priority 7: fix during launch polish.

Why it matters: Unlabeled inputs make email capture, demo requests, and signups harder for assistive technology users.

Fix: Connect each input to a visible label or an accurate aria-label/aria-labelledby value.

9 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.

Failed: earned 0 of 8 points.

Priority: Priority 20: lower-risk cleanup after urgent launch blockers.

Why it matters: Low contrast makes a launch page feel less polished and can exclude users with low vision.

Fix: Review key text, buttons, and links against a 4.5:1 contrast target for normal text.

axe found 6 violation rule(s), including 1 serious or critical rule(s). Top rules: image-alt (1), landmark-main-is-top-level (10), landmark-no-duplicate-main (1), landmark-unique (3), region (3).

Failed: earned 0 of 18 points.

Priority: Priority 5: fix before sharing the page publicly.

Why it matters: axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology.

Fix: Fix the top axe rule IDs first, especially critical and serious violations around names, roles, labels, headings, contrast, landmarks, and keyboard-accessible controls.

Detected 0 CTA candidate(s).

Failed: earned 0 of 14 points.

Priority: Priority 4: fix before sharing the page publicly.

Why it matters: Early visitors need a clear next step, such as trying the product, joining a waitlist, or booking a demo.

Fix: Add one prominent CTA above the fold with action-oriented text such as Start, Join, Try, Book, or Get started.

Detected about 4034 visible word(s).

Failed: earned 0 of 10 points.

Priority: Priority 21: lower-risk cleanup after urgent launch blockers.

Why it matters: Too little copy can leave visitors confused; too much copy can bury the value proposition.

Fix: Add concise sections for value, proof, how it works, and next steps, then remove repetitive copy.

Detected 0 trust-signal keyword occurrence(s).

Failed: earned 0 of 10 points.

Priority: Priority 16: lower-risk cleanup after urgent launch blockers.

Why it matters: Trust signals reduce hesitation when strangers see the product for the first time.

Fix: Add honest proof such as customer quotes, usage stats, founder credibility, security notes, or relevant logos.

Horizontal overflow: 0px. Small tap targets: 180.

Failed: earned 0 of 9 points.

Priority: Priority 13: fix during launch polish.

Why it matters: Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors.

Fix: Remove elements wider than the viewport, add responsive constraints, and make important links, buttons, inputs, and controls at least 40px tall and wide where possible.