Report loading
iwatched.app
Preparing the full page inventory and screenshots.
Score
78
Issues
Analyzed
Report loading
Preparing the full page inventory and screenshots.
Good
Health Score
Here's the simple version
78/100 - good. Good enough to understand, not good enough to ignore. The _iWatched_ digital presence maintains excellent Core Web Vitals and a clear value proposition, but significant technical debt in third-party dependencies and accessibility compliance threatens long-term scalability and user retention. The site demonstrates high-tier performance metrics, specifically achieving "Good" ratings across all Core Web Vitals, including an impressive LCP of 716ms. The visual hierarchy is well-defined, utilizing a strong hero section and semantic HTML structure that effectively communicates the core utility to users and search engines alike. Furthermore, the presence of a privacy policy and secure header configurations like HSTS provides a solid foundation for user trust and regulatory compliance. A high-priority performance issue stems from a heavy third-party load, with 1.2 MB of scripts and assets being pulled from eight external domains. This dependency introduces significant DNS and TLS overhead that can jeopardize the current performance advantages as the feature set expands. Additionally, the site faces serious accessibility and SEO gaps, specifically regarding missing alt text for movie and series posters and a lack of responsive image implementation, which impacts both inclusive design and mobile bandwidth efficiency. There is a significant opportunity to optimize the site for the emerging AI-driven search landscape. While the current robots.txt policy is clear, the site lacks specialized discovery files like `llms.txt` and comprehensive structured data (Schema.org) for products and FAQs. Implementing these would allow answer engines to more accurately cite _iWatched_ as a primary source for entertainment tracking queries, capturing high-intent traffic from AI assistants. **First 30 Days** - Audit and consolidate third-party scripts to reduce the 1.2 MB external payload. - Implement missing alt text for all movie and series poster images to meet WCAG standards. - Deploy a `sitemap.xml` to improve search engine crawlability and indexation.
Good
Health score
Launch blockers
No major launch blockers found.
The rest of the report is a fix queue, not a reason to panic.
Fix first
Start with the top 3.
These are the items most likely to improve trust, speed, or conversion.
Best next step
Hand the fix list to your builder or AI agent.
The technical detail is still here when they need evidence.
Biggest area to improve: Performance, which mostly means speed and loading experience.
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
Populate the `alt` attribute of each movie image with the title of the movie. For example: `<img ... alt='The Punisher: One Last Kill'>`.
The movie poster images in the grid (e.g., `<img class='img-fluid image-box-hover' ... alt=''>`) have empty alt attributes. While they are links, screen reader users will not know which movie the link represents without the text content being properly associated.
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
Update the `<img>` tags within the series grid to include the title of the show in the `alt` attribute. For example: `<img alt='The Boys' ...>`.
Several series poster images (e.g., 'The Boys', 'FROM') have empty `alt=""` attributes. While decorative images can have empty alt text, these are primary content elements that convey the identity of the show to screen reader users.
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.
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.
