Website audit scorecard for easyinvoicepdf.com

FreeScan.app reached the public page with HTTP 200. robots.txt blocks Googlebot, Bingbot, DuckDuckBot, and 9 more for this page path.

Failed: earned 0 of 14 points.

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

Why it matters: If crawlers cannot access the page, search engines and answer engines may not discover, index, or summarize the launch page correctly.

Fix: Review robots.txt, Cloudflare/WAF bot rules, rate limits, and security challenges. Allow legitimate search and AI crawler access to public launch pages while keeping private, admin, and authenticated paths protected.

Detected 0 H1 heading(s) and 0 total headings.

Failed: earned 0 of 8 points.

Priority: Priority 9: fix during launch polish.

Why it matters: Clear headings help visitors, search engines, and assistive technology understand the page quickly.

Fix: Keep one H1 for the main promise, then use H2 and H3 headings in order for sections below it.

Detected 0 internal link(s).

Failed: earned 0 of 6 points.

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

Why it matters: Internal links help visitors find pricing, docs, contact, legal, or product details without getting stuck.

Fix: Add clear public links such as pricing, docs, contact, privacy, terms, or product detail pages where appropriate.

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

Failed: earned 4 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.

Heading levels found: none.

Failed: earned 0 of 11 points.

Priority: Priority 13: fix during launch polish.

Why it matters: A clean heading outline helps visitors scan the page and helps assistive technology navigate it.

Fix: Use headings in order: one H1, then H2 for major sections, then H3 for subsections.

Detected 0 landmark element(s) or roles.

Failed: earned 0 of 10 points.

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

Why it matters: Landmarks make the page easier to navigate for assistive technology and keyboard users.

Fix: Use semantic elements such as header, nav, main, and footer around the appropriate page areas.

axe found 5 violation rule(s), including 0 serious or critical rule(s). Top rules: heading-order (1), landmark-one-main (1), landmark-unique (1), meta-viewport (1), region (34).

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 0 H1 heading(s) and 147 meta-description characters.

Failed: earned 0 of 13 points.

Priority: Priority 6: fix during launch polish.

Why it matters: Visitors decide quickly whether the product is relevant; a vague hero weakens every acquisition channel.

Fix: Use one clear H1 plus supporting copy that names the audience, problem, and outcome.

Detected about 8 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.

Detected 0 spacing class/style signal(s).

Failed: earned 0 of 7 points.

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

Why it matters: Consistent spacing helps the page feel deliberate and easier to scan.

Fix: Use consistent section padding, gaps, and margins across repeated content blocks.

Detected 0 hierarchy signal(s) from headings, CTA, and emphasized text.

Failed: earned 0 of 9 points.

Priority: Priority 12: fix during launch polish.

Why it matters: Hierarchy tells visitors what to read first and what action to take next.

Fix: Create a clear H1, supportive section headings, emphasized proof, and one visually prominent primary CTA.

DOMContentLoaded: 1041ms. Load complete: 1520ms. First contentful paint: 740ms. Resources: 40. Scripts: 25. Images: 1. Third-party origins: 11. Transfer: not available.

Failed: earned 0 of 10 points.

Priority: Priority 14: fix during launch polish.

Why it matters: Slow pages lose impatient visitors and make every SEO, social, and paid-traffic visit work harder.

Fix: Reduce render-blocking scripts/styles, compress and size images, defer non-critical JavaScript, reduce third-party tags, and keep above-the-fold content quick to paint.

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

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.