Report loading
investors-lab.com
Preparing the full page inventory and screenshots.
Score
69
Issues
Analyzed
Report loading
Preparing the full page inventory and screenshots.
69 / 100
Fair
0 critical fixes · 3 quick wins
Priority verdict
69/100 - fair. Start with the fixes below before reading the full report.
The biggest issue is heavy third-party load (1.1 mb from 3 domain(s)). Start with the priority fixes, then use the evidence and technical details when a developer needs proof.
Fair
3 priority fixes identified
Score
69 / 100 — Fair
No major launch blockers found.
Biggest risk
Heavy third-party load (1.1 MB from 3 domain(s))
speed and loading experience
Fastest win
Heavy third-party load (1.1 MB from 3 domain(s))
A practical first fix for your builder or AI agent.
Estimated impact
Higher confidence and discoverability
Fix the priority items first, then re-scan to confirm the evidence.
Biggest area to improve: Security Headers, which mostly means visitor safety and trust.
Priority verdict
This site is technically inspectable, but the priority is making the next fix obvious.
Fix the highest-impact issue first, then use structured evidence and developer prompts so search engines, AI answer engines, and real visitors can understand the site more reliably.
What's working
What needs attention
What to do first
Investors Lab maintains a strong foundation for AI-driven discovery and brand authority, but significant accessibility and performance barriers currently degrade the user experience and search visibility. The site excels in technical SEO and AI readiness. The implementation of comprehensive Schema.org structured data, including Organization and FAQPage types, provides clear entity signals for answer engines. Furthermore, the site is well-prepared for machine-readable discovery, with a functional sitemap, active AI crawler accessibility, and robust email authentication protocols (SPF, DMARC, and DKIM) that protect brand reputation. A high-priority accessibility failure threatens both usability and compliance. Specifically, several interactive elements fail to meet minimum touch target size requirements, with some targets measuring as narrow as 2px. This is compounded by insufficient color contrast ratios that violate WCAG 2 AA standards. These issues create a fragmented experience for mobile users and those with visual impairments, potentially increasing bounce rates and limiting market reach. The most significant growth opportunity lies in optimizing the Largest Contentful Paint (LCP) and content depth. Current LCP speeds exceed 3.5 seconds, significantly trailing the 2.5-second "Good" threshold. By reducing heavy third-party loads and expanding commercial AI-search coverage—specifically adding pricing, product catalogs, and detailed comparison content—the site can capture high-intent traffic from generative search engines that prioritize comprehensive, fast-loading data. To stabilize the user experience and improve search rankings, the following actions are required in the next 30 days: - Resolve high-priority accessibility issues by increasing touch target sizes to at least 24px and correcting color contrast ratios.
Scan details
Checks performed: SEO, UX, accessibility, performance, security, AI search.
Fix workflow
Treat this report as a queue: send the ready fixes, accept any intentional risks, then re-scan the production URL after changes land.
32
Ready to send
87
Not started
0
Accepted risk
0
Re-scan queued
The full report has all the proof. This is the owner-friendly version of what to do first.
Plain-English reason
This affects speed and loading experience. PageLens marked it as important so you know where it belongs in the queue.
What to ask your builder or AI agent to do
Audit every third-party tag: drop ones you're no longer measuring, switch from <script> to async/defer, route analytics through a single tag manager, and self-host fonts as woff2 (most font CDNs add 50-150 KB per family).
Third-party scripts (analytics, embeds, ad pixels, font CDNs, chat widgets) are hosted outside your control and often render-block, INP-block, or both. Each adds DNS resolution + TLS overhead and can fail independently of your own infrastructure.
Plain-English reason
This affects whether everyone can use the site. PageLens marked it as important so you know where it belongs in the queue.
What to ask your builder or AI agent to do
Element matching `.space-y-4:nth-child(2) > .text-white\/40.tracking-\[0\.2em\]` has contrast ratio 3.75; WCAG AA requires 4.5:1. Increase the contrast between foreground and background colours (the Tailwind hint below proposes the next darker step in the same family if the offending class is a recognised palette utility). Reference: https://dequeuniversity.com/rules/axe/4.11/color-contrast?application=playwright
Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds. Fix any of the following: Element has insufficient color contrast of 3.75 (foreground color: #6a6b70, background color: #070810, font size: 9.0pt (12px), font weight: normal). Expected contrast ratio of 4.5:1
Plain-English reason
This affects whether everyone can use the site. PageLens marked it as important so you know where it belongs in the queue.
What to ask your builder or AI agent to do
Element matching `.sm\:flex-row.lg\:justify-start.pt-2 > a[href="/auth?mode=signup"]` is rendered at 246x2 px; touch targets must be >=24x24 px (WCAG 2.5.8). Add padding (e.g. `min-h-[24px] min-w-[24px]` in Tailwind, or `padding` so the bounding box reaches 24 px in both dimensions). Reference: https://dequeuniversity.com/rules/axe/4.11/target-size?application=playwright
Ensure touch targets have sufficient size and space. Fix any of the following: Target has insufficient size because it is partially obscured (smallest space is 246px by 2px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 2px instead of at least 24px.
A practical roadmap for turning the audit into progress.
Today
Audit every third-party tag: drop ones you're no longer measuring, switch from <script> to async/defer, route analytics through a single tag manager, and self-host fonts as woff2 (most font CDNs add 50-150 KB per family).
This week
Element matching `.space-y-4:nth-child(2) > .text-white\/40.tracking-\[0\.2em\]` has contrast ratio 3.75; WCAG AA requires 4.5:1. Increase the contrast between foreground and background colours (the Tailwind hint below proposes the next darker step in the same family if the offending class is a recognised palette utility). Reference: https://dequeuniversity.com/rules/axe/4.11/color-contrast?application=playwright
This month
Element matching `.sm\:flex-row.lg\:justify-start.pt-2 > a[href="/auth?mode=signup"]` is rendered at 246x2 px; touch targets must be >=24x24 px (WCAG 2.5.8). Add padding (e.g. `min-h-[24px] min-w-[24px]` in Tailwind, or `padding` so the bounding box reaches 24 px in both dimensions). Reference: https://dequeuniversity.com/rules/axe/4.11/target-size?application=playwright
Same data as the full report, grouped by what a non-technical owner should do with it.
High-impact fixes that should usually be tackled before anything else.
Important fixes that may need more development time or a design decision.
Nothing in this bucket.
Polish and lower-priority work. Useful, but not where to start.
Need the detail?
The full report still has every finding, evidence, rule ID, filters, screenshots, and technical panels.
