Report loading
calledit.joelrubio.app
Preparing the full page inventory and screenshots.
Score
77
Issues
Analyzed
Report loading
Preparing the full page inventory and screenshots.
77 / 100
Good
0 critical fixes · 4 quick wins
Priority verdict
77/100 - good. Good enough to understand, not good enough to ignore.
The biggest issue is missing <html lang> attribute. Start with the priority fixes, then use the evidence and technical details when a developer needs proof.
Good
3 priority fixes identified
Score
77 / 100 — Good
No major launch blockers found.
Biggest risk
Missing <html lang> attribute
whether everyone can use the site
Fastest win
Missing <html lang> attribute
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: Accessibility, which mostly means whether everyone can use the site.
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
The Called It! digital experience currently operates in a state of total search engine invisibility due to restrictive indexing directives. The platform demonstrates exceptional technical performance and brand cohesion. On both DESKTOP and MOBILE, Largest Contentful Paint (LCP) scores are well within the "Good" threshold, ensuring a fast, responsive user experience. The visual identity is strong, utilizing a custom SVG wordmark and a clear primary call-to-action that provides an immediate path for user engagement. Furthermore, the site maintains a professional compliance posture with a visible privacy policy and robust security headers like HSTS. However, the site faces high-priority accessibility and visibility hurdles that undermine its professional utility. On DESKTOP, the root HTML element lacks a language attribute, which prevents screen readers from applying correct pronunciation profiles. More critically, the site currently employs noindex meta tags on the homepage and sign-in pages, effectively barring the product from organic search results. This is compounded by a robots.txt configuration that blocks major AI retrieval crawlers, such as OAI-SearchBot, which significantly limits the product's discoverability in modern AI-driven search interfaces. There is a significant opportunity to transition Called It! from a private application to a high-growth consumer product by optimizing for the "answer engine" era. By removing restrictive indexing directives and implementing JSON-LD structured data, the site can move from being invisible to being a primary source for AI-driven sports predictions and search queries. To establish a foundation for growth, the following must be addressed in the first 30 days: - Remove noindex directives from the homepage and core landing pages to allow search engine indexing.
lang attribute to resolve high-priority accessibility gaps.robots.txt to permit essential AI retrieval bots to ensure visibility in ChatGPT and similar search surfaces.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.
23
Ready to send
48
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 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
Set the document language: <html lang="en"> (or your appropriate BCP 47 tag).
The root <html> element has no lang attribute. Screen readers cannot pick the correct pronunciation profile, and Google can't reliably language-target the page (WCAG 2.2 SC 3.1.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 `.landing-eyebrow` has contrast ratio 3.37; 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.37 (foreground color: #8a7f68, background color: #f3eddd, font size: 9.0pt (12px), font weight: normal). Expected contrast ratio of 4.5:1
Plain-English reason
This affects how AI search tools understand the site. PageLens marked it as worth fixing so you know where it belongs in the queue.
What to ask your builder or AI agent to do
Allow retrieval crawlers such as OAI-SearchBot and PerplexityBot for public marketing, product, help, and documentation pages while keeping private app/account routes blocked.
robots.txt appears to block at least one retrieval-oriented AI crawler used for answer/search experiences. This can reduce eligibility for AI search surfaces, though it does not measure live ranking.
A practical roadmap for turning the audit into progress.
Today
Set the document language: <html lang="en"> (or your appropriate BCP 47 tag).
This week
Set the document language: <html lang="en"> (or your appropriate BCP 47 tag).
This month
Element matching `.landing-eyebrow` has contrast ratio 3.37; 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
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.