Website audit scorecard for trendgap.io
The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
https://trendgap.io/
Final URL
https://trendgap.io
Created
Jul 6, 2026, 4:17 PM
Safe fetch
1035 ms
87
out of 100
100
out of 100
92/92 rule points
100
out of 100
76/76 rule points
72
out of 100
68/94 rule points
76
out of 100
84/110 rule points
Category point breakdown
Biggest score-losing checks
axe found 1 violation rule(s), including 0 serious or critical rule(s). Top rules: region (5).
DOMContentLoaded: 1591ms. Load complete: 2025ms. First contentful paint: 1552ms. Resources: 46. Scripts: 2. Images: 3. Third-party origins: 12. Transfer: not available.
Horizontal overflow: 0px. Small tap targets: 24.
7 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.
Fix rendered axe accessibility violations
-18 rule ptsWhat failed
The rendered page has accessibility rule violations detected by axe-core.
Evidence
axe found 1 violation rule(s), including 0 serious or critical rule(s). Top rules: region (5).
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.
How to fix it
Fix the top axe rule IDs first, especially critical and serious violations around names, roles, labels, headings, contrast, landmarks, and keyboard-accessible controls.
Fix rendered layout ergonomics
-9 rule ptsWhat failed
The browser-rendered page has layout or tap-target issues.
Evidence
Horizontal overflow: 0px. Small tap targets: 24.
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.
How to fix it
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.
Improve rendered speed signals
-10 rule ptsWhat failed
The browser-rendered page shows slow or heavy speed signals.
Evidence
DOMContentLoaded: 1591ms. Load complete: 2025ms. First contentful paint: 1552ms. Resources: 46. Scripts: 2. Images: 3. Third-party origins: 12. Transfer: not available.
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.
How to fix it
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.
Improve detectable color contrast
-8 rule ptsWhat failed
The scanner found text/background color pairs that may be hard to read, or could not verify contrast.
Evidence
7 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.
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.
How to fix it
Review key text, buttons, and links against a 4.5:1 contrast target for normal text.
Fix runtime browser errors
-7 rule ptsWhat failed
The rendered page produced console or uncaught JavaScript errors.
Evidence
Detected 6 console error(s) and 1 uncaught page error(s) during render.
Priority
Priority 15: fix during launch polish.
Why it matters
Runtime errors can break forms, CTAs, animations, tracking, or responsive behavior even when the static HTML looks fine.
How to fix it
Open the page in a browser, reproduce the console errors, and fix missing assets, hydration problems, client-side exceptions, or failing third-party scripts.
SEO / AEO
Severity mix: 0 critical, 6 high, 3 medium, 2 low.
No failed checks in this category.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
No failed checks in this category.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
Rendered axe accessibility violations
-18 rule ptsaxe found 1 violation rule(s), including 0 serious or critical rule(s). Top rules: region (5).
Basic contrast
-8 rule pts7 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
Rendered speed signals
-10 rule ptsDOMContentLoaded: 1591ms. Load complete: 2025ms. First contentful paint: 1552ms. Resources: 46. Scripts: 2. Images: 3. Third-party origins: 12. Transfer: not available.
Rendered layout ergonomics
-9 rule ptsHorizontal overflow: 0px. Small tap targets: 24.
Runtime console health
-7 rule ptsDetected 6 console error(s) and 1 uncaught page error(s) during render.
Showing failed checks.
Failed checks
These checks need attention.
Basic contrast
0/87 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.
Rendered axe accessibility violations
0/18axe found 1 violation rule(s), including 0 serious or critical rule(s). Top rules: region (5).
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.
Rendered speed signals
0/10DOMContentLoaded: 1591ms. Load complete: 2025ms. First contentful paint: 1552ms. Resources: 46. Scripts: 2. Images: 3. Third-party origins: 12. 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.
Runtime console health
0/7Detected 6 console error(s) and 1 uncaught page error(s) during render.
Failed: earned 0 of 7 points.
Priority: Priority 15: fix during launch polish.
Why it matters: Runtime errors can break forms, CTAs, animations, tracking, or responsive behavior even when the static HTML looks fine.
Fix: Open the page in a browser, reproduce the console errors, and fix missing assets, hydration problems, client-side exceptions, or failing third-party scripts.
Rendered layout ergonomics
0/9Horizontal overflow: 0px. Small tap targets: 24.
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.
Share preview
trendgap.io website audit report
Close to ready: 87/100 overall, with prioritized fixes for SEO, security, accessibility, and design.
Public reports expose the scanned public URL, safe scores, sanitized public evidence, and fix guidance. They do not include credentials, cookies, hidden form values, or sensitive response bodies.