| Metric | Value |
|---|---|
| Domain | argos-ci.com |
| Category | Visual Testing & Snapshot Testing |
| Pricing | SaaS Subscription |
| Pages Crawled | 40 |
| Crawl Date | 2026-08-14 |
Argos-CI Review: Strong AI-ready testing (77.7/100) — SiteList
Argos-CI earns a 77.7/100 for its exceptional AI search readiness and developer-centric documentation. However, critical technical health issues and mobile usability gaps on its app subdomain currently hinder its overall performance.
Reviewed by SiteList Engine · 34 dimensions · published Examined on August 14, 2026
Quick facts
- Pages Crawled
- 40
- Crawl Date
- 2026-08-14
Executive summary
Argos-CI exhibits a sophisticated content strategy and industry-pioneering AI search readiness, but its foundation is currently undermined by critical technical failures. A 'Poor' site health score (19) stems from a broken mobile experience on the app subdomain, significant homepage duplication, and performance anti-patterns like lazy-loading the primary hero image. While the site is strategically positioned to win in the 'AI Agent' testing niche, these P0 blockers must be resolved before growth investments will yield full ROI.
Key Themes
- Technical Foundation & Index Integrity: Structural duplication between the root and /homepage splits link equity and confuses crawlers.
- Mobile Parity & App Subdomain Health: The application layer is non-functional for mobile users due to missing viewport meta tags.
- LCP & Performance Anti-patterns: Homepage LCP is delayed by lazy-loading the hero image and a 3.8MB payload.
- Content Freshness & Strategic Gaps: Core commercial comparison pages have not been updated since 2024.
- AI Search & AEO Frontrunner: Argos is a top-tier example of AI readiness with its llms.txt and robots.txt configuration.
- Site Health Score
- 19/100
01 · First impressions & positioning — Strategic pivot to AI-agent readiness
Argos successfully differentiates itself from legacy visual testing tools by positioning its platform as the essential layer for the "age of AI." While competitors focus on human-driven workflows, Argos targets the high-volume code changes generated by AI agents. This specific framing creates immediate urgency for engineering teams scaling their automation. The site backs this positioning with a high-density logo wall featuring Meta and Redis, alongside a clear price-to-value comparison against incumbents like Percy.
- Primary Headline
- Review product changes in the age of AI
- Price Differentiation
- $100 vs $599 (Percy)
02 · Audience & messaging — High-transparency developer-first communication
The site demonstrates a deep understanding of the developer persona by addressing cost, trust, and stack compatibility within a single click of the homepage. Messaging is technically grounded, using industry-standard terms like "deterministic pixel diffing" and "CI pipeline" to signal expertise. Social proof is exceptionally strong, utilizing named testimonials from high-authority figures such as the CTO of GitBook. The inclusion of a pricing calculator and explicit comparison tables further reduces cognitive load for prospects.
- Trust Signals
- Named testimonials from GitBook and MUI
- Decision Support
- Integrated pricing calculator
03 · Usability — Frictionless conversion paths with minor contact hurdles
Argos provides a high-scent user experience where core tasks like evaluating pricing or starting a trial are completed in minimal steps. High-contrast purple CTAs are ubiquitous and lead directly to the application signup flow. The documentation, powered by GitBook, is robust and easily searchable, though this search functionality is currently isolated from the main marketing site. The primary usability friction point is the reliance on mailto: links for sales and support, which triggers local mail clients rather than providing an integrated contact form. Moving "Docs" to the top-level navigation would further improve accessibility for its primary developer audience.
- Navigation Efficiency
- 1-click path to pricing
- Contact Friction
- mailto: links on /contact page
04 · Accessibility — Strong ARIA foundation marred by structural omissions
Argos-CI utilizes accessible UI primitives like React Aria, ensuring interactive components are generally navigable for screen reader users. However, the site fails several standard WCAG 2.1 AA requirements. Most notably, there is no skip-to-content link on any audited page, forcing keyboard users to tab through the entire navigation menu repeatedly. Additionally, the documentation pages exhibit a broken heading hierarchy, often skipping directly to h5 tags. Visual accessibility is also compromised by low-contrast gray text in the hero sub-headers and a lack of support for prefers-reduced-motion in its CSS animations.
- Bypass Blocks
- hasSkipLink: false
- Heading Hierarchy
- Docs sequence starts at H5
05 · Design execution — Modern SaaS aesthetic with significant token drift
The site maintains a professional visual hierarchy and logical scan order, but technical debt is evident in its CSS implementation. Despite using a token system, the production build contains over 200 distinct colors and 39 border-radius variations, leading to a fuzzy interface where similar elements lack consistency. Mobile execution is a weakness; primary hero CTAs measure only 36px in height, failing the 44px ergonomic standard for touch targets. Furthermore, the presence of 47 distinct font families suggests a need for font-stack optimization to improve brand cohesion and load performance.
- Color Consistency
- 206 distinct color values
- Mobile Ergonomics
- 36px hero CTA height
07 · Performance — 3.8 MB payload and lazy-loaded hero delays
While hosted on a high-performance Next.js and Vercel stack, Argos suffers from avoidable client-side bottlenecks. The most critical error is the lazy-loading of the primary hero image, which delays the Largest Contentful Paint (LCP) as the browser waits for layout calculations before fetching the asset. The total page weight of 3.8 MB is heavy for a marketing site, driven largely by 128 requests and a 298 KB Google Tag Manager container. While server response times are excellent due to edge caching, these asset management choices result in a sluggish perceived experience for users on slower connections.
- Total Payload
- 3,844 KB
- LCP Anti-pattern
- loading="lazy" on hero image
09 · Writing quality — Technically authoritative copy with editorial hygiene gaps
Argos avoids generic marketing language by grounding its copy in concrete technical utility, such as citing specific costs per screenshot. The Problem-Solution-Proof structure is effective, particularly in the hero section's focus on the age of AI agents. However, editorial hygiene is inconsistent. The blog index suffers from extreme sentence density, with an average of 90 words per sentence in summaries. Furthermore, the site exhibits poor image metadata hygiene, with 18 missing alt tags on the homepage alone. A technical redundancy also exists where the root content is duplicated at the /homepage URL.
- Accessibility Hygiene
- 18 missing alt tags
- Sentence Density
- 90.3 avg_sentence_words on blog
10 · Vertical credibility — Tier-1 trust signals and high-fidelity product diffs
Argos excels at signaling institutional transparency and technical competence to engineering teams. The site leverages a logo cloud of recognizable brands like Meta and ClickHouse, supported by detailed case studies. Visual communication is a highlight; the use of actual product diffs effectively demonstrates the platform's value without relying on abstract illustrations. The inclusion of Organization schema with founder details further establishes credibility. To maximize this impact, the site should ensure all customer logos link directly to their respective case studies.
- Brand Authority
- Logo cloud including Meta and Redis
- Transparency
- Organization schema with founder details
11 · Competitive position — High-conviction challenger with educational gaps
Argos positions itself as a cost-effective, modern alternative to legacy tools like Percy and Applitools. It successfully captures commercial intent through pricing and integration pages but trails competitors in educational content. While category leaders maintain extensive learning centers, the Argos sitemap is focused primarily on documentation and changelogs. The site's AI-agent positioning provides a unique competitive edge, but this needs to be formalized into framework-specific landing pages (e.g., Playwright, Cypress) to capture high-intent integration traffic. Expanding the resources section to include top-of-funnel informational guides would help bridge the authority gap with entrenched incumbents.
- Content Volume
- 237 URLs in sitemap
- Competitive Intent
- Direct name-checks of Percy and Chromatic
12 · Decision-support surfaces — Exemplary pricing tools vs biased comparisons
Decision support on Argos is a study in contrasts. The pricing page features an exemplary usage calculator that allows teams to model costs dynamically, providing high transparency. Conversely, the competitor comparison pages fall into the hidden-recommendation trap. These grids are heavily biased, showing competitors failing on core features they actually possess, which risks alienating sophisticated buyers. Furthermore, these surfaces lack Last Updated timestamps or methodology disclosures, which are essential for maintaining trust. Adding objective "best-for" scenarios where a competitor might be preferred would significantly improve the integrity of these tools.
- Pricing Transparency
- Interactive usage sliders
- Comparison Bias
- 15/16 win ratio on comparison grids
13 · Review-content integrity — Marketing superlatives lacking evidentiary depth
The site's review-style content currently lacks the depth required for high-trust decision support. Claims of being the best alternative are presented as marketing copy rather than verified analysis, operating only at the level of manufacturer specifications. To improve integrity, Argos should transition toward evidence-based claims by citing third-party benchmarks or user sentiment from platforms like GitHub. The absence of a methodology block explaining how competitor data was verified further weakens the content's authority. Including product drawbacks or specific scenarios where Argos is not the ideal fit would demonstrate the objectivity necessary for high-integrity review content.
- Claim Verification
- Tier 1 evidence level
- Editorial Disclosure
- Missing methodology section
14 · Authority & link risk — Mature domain with internal equity leaks
Registered in 2016, the domain benefits from a decade of maturity and a clean outbound link profile. External links point to high-authority developer tools and customer sites, with no evidence of manipulative link schemes. However, internal equity distribution is inefficient. Several high-value technical guides are currently orphaned, receiving zero internal links and preventing equity from flowing to deep content. Additionally, minor social link rot was identified, such as a 404 error on the X.com link in the footer. Fixing these technical leaks and updating social references will strengthen the site's overall authority and link integrity.
- Domain Age
- Registered December 2016
- Internal Linking
- Orphaned wait-for-background-images page
15 · Off-page readiness — Founder-led entity with 2016 domain authority
Argos-CI possesses a mature off-page foundation, anchored by a 2016 domain registration and a comprehensive Organization schema. The presence of a named founder with a verified personal site provides the necessary E-E-A-T for high-tier outreach. While the site features tier-1 customer logos like Meta and GitBook, these lack direct links to verifiable case studies, limiting their impact as trust signals. The "Screenshot Testing Guide" serves as a primary linkable asset, though the site has yet to produce flagship industry reports to capture broader media attention. Outreach readiness remains high due to the site's professional design and clear value proposition in the DevOps niche.
- Domain Age
- 2016
- Entity Signals
- Organization schema includes founder and Paris address
16 · Rank readiness — High brand noise from retail sector competitors
The site is highly measurable with a clean URL structure, yet it faces significant brand ambiguity due to the "Argos" name shared with a major UK retailer. Rank tracking must be segmented into Brand Defensive (Argos CI) and Money Terms (visual testing) to filter out irrelevant noise. Currently, the /homepage and root URLs compete for the same keywords, creating internal cannibalization. Consolidating these surfaces is required to ensure the primary marketing page maintains its ranking position against specialized competitors like Percy and Chromatic. The site is well-positioned for technical terms, but brand-name noise remains a primary tracking hurdle.
- Keyword Conflict
- /homepage and / URLs compete
- Brand Risk
- Shared name with UK retailer
17 · Risk & stability — Proactive AI-agent hedging via llms.txt
Argos-CI maintains a stable technical environment with no catastrophic indexability failures or accidental blocks. The architectural separation between the marketing site and the application subdomain via noindex directives is correctly implemented. Because the platform operates in a technical niche, it faces high exposure to AI Overview displacement; however, the inclusion of a /llms.txt file is a sophisticated hedge that allows the site to influence LLM summaries. Internal link health is perfect, with 100% of sampled links returning 200 OK status codes during the crawl. The site passes all catastrophic failure checks, ensuring a reliable surface for search engines.
- Internal Link Health
- 100% 200 OK
- AI Readiness
- /llms.txt present
18 · Content briefs discipline — 40% snippet readiness with buried technical answers
Argos demonstrates high briefing discipline in its technical depth, though it frequently misses featured snippet opportunities by placing direct answers below the 60% scroll mark. The AI Agent page, while conceptually strong, buries its core technical implementation details. Internal linking relies on generic anchors like "Read more" and "Case study" (9 instances total), failing to pass descriptive keyword equity. To improve AI search optimization, the site needs to adopt answer-first paragraph structures and vary its heading stems to avoid repetitive patterns in the changelog and documentation. Snippet paragraphs currently only cover 40% of key informational queries.
- Snippet Readiness
- 40%
- Generic Anchors
- 9 instances of 'Read more'
19 · Editorial QA of content — 37 missing alt tags on core landing pages
A lack of final QA gates has resulted in significant accessibility gaps, including 37 images without alt text on the visual testing page. Editorial quality is high, with a technical voice that avoids AI-generated slop and throat-clearing patterns. The internal link graph is characterized by an anchor monoculture, with "argos" and "pricing" accounting for over 120 links. Furthermore, duplicate meta descriptions across the application subdomain's login and signup pages indicate a need for more granular editorial oversight of technical metadata. While the technical claims are well-supported, these hygiene gaps hinder the site's overall editorial authority.
- Missing Alt Text
- 37 images on /visual-testing
- Anchor Monoculture
- 129 links for 'argos' or 'pricing'
20 · Content program — High-authority pillars lacking lead-capture infrastructure
The content program is sophisticated, leveraging founder expertise to build authority in visual testing and AI-agent workflows. The "Screenshot Testing Guide" acts as a 1,993-word cornerstone asset with high E-E-A-T. Despite this technical excellence, the program fails to capture audience intent; the blog and high-traffic guides contain zero email subscription forms or lead-capture mechanisms. Additionally, valuable technical documentation on flaky tests remains orphaned with zero in-links, preventing the program from fully supporting the user's educational journey. The strategy successfully balances evergreen guides with timely product narratives but lacks a conversion funnel.
- Cornerstone Length
- 1,993 words
- Lead Capture
- 0 forms on /blog
21 · Distribution & reach — Fragmented social loops and missing RSS feeds
Argos maintains a steady publishing cadence but lacks the infrastructure for automated content distribution. The absence of a newsletter or RSS feed results in a reliance on manual social shares. While the GitHub and LinkedIn presence is strong, the X/Twitter integration is misconfigured, with footer links leading to 404 errors. To improve reach, the site must fix these social links and implement Related Posts modules to prevent articles from becoming dead-ends for developer traffic. The content is highly shareable and technically deep, but the distribution channels are currently fragmented.
- Social Link Status
- X.com link 404s
- Feed Availability
- No RSS/Atom detected
22 · Content freshness — 22% of the library exceeds 24 months without updates
The site follows a triaged-refresh pattern, prioritizing the changelog and blog while allowing commercial comparison pages to stagnate. Core comparison assets for Percy and Chromatic have not been substantially updated since April 2024, a significant gap in the fast-moving visual testing market. While the team published five posts in the last 14 days, the middle-of-funnel landing pages still feature 2024 screenshots and benchmarks. A quarterly audit is required to refresh these high-intent surfaces and maintain currency signals for both users and search engines. Currently, 22% of the library is in the stale bracket.
- Stale Content
- 22% > 24 months old
- Recent Cadence
- 5 posts in 14 days
23 · Docs & self-serve help — 94/100 for exceptional AI-agent and MCP support
Argos provides an industry-leading documentation ecosystem hosted on GitBook, covering all four Diátaxis content types. It is a first-mover in AI-readiness, offering an MCP (Model Context Protocol) server and a machine-readable API catalog to support AI agents. The documentation is visibly maintained, with updates recorded within the last 30 days. The primary improvement area is the fragmentation of help content; valuable troubleshooting information is currently locked in pricing page FAQs rather than being centralized within the main documentation sidebar. This high-usability interface serves as a significant sales and onboarding asset for technical users.
- Update Recency
- Last updated 24 days ago
- AI Support
- MCP server and llms.txt present
24 · Measurement readiness — Ad pixels firing without mandatory consent gates
The measurement stack uses a hybrid of GA4 and Plausible, providing a balance of deep attribution and privacy. However, a critical compliance risk exists as Google Ads pixels fire immediately on page load without a consent management platform (CMP). Furthermore, the transition from the marketing site to the app.argos-ci.com subdomain lacks visible cross-domain configuration. This gap likely results in broken attribution, where signups appear as Direct traffic rather than being credited to the original marketing campaigns or social referrals. Implementing a CMP and cross-domain linking is essential before scaling paid growth investments.
- Compliance Risk
- Ad pixels fire without consent
- Attribution Gap
- No cross-domain linking detected
25 · Technical SEO — 92/100 for SSR efficiency and AI-signal readiness
The technical foundation is excellent, utilizing Next.js for server-side rendering that ensures a 0% raw-vs-rendered content diff. The robots.txt includes modern Content-Signal directives, and the sitemap is cleanly structured. The most significant technical debt is the application subdomain's lack of a viewport meta tag, which causes horizontal overflow and poor mobile rendering. Additionally, the presence of 18 images on the homepage without alt text hinders image SEO. Consolidating the /homepage duplicate via a 301 redirect is the final step for index integrity. Crawlability and indexability remain near-perfect across the marketing surface.
- Render Diff
- 0%
- Mobile Health
- Missing viewport meta on app subdomain
26 · On-page SEO — Meta description truncation and homepage duplication
Argos features deep, intent-aligned content, but its on-page execution is hampered by structural duplication and unoptimized meta tags. The homepage meta description is 245 characters, far exceeding the 155-character truncation limit, while the pricing page title is too short to capture high-intent category keywords. The existence of a word-for-word duplicate at /homepage splits link equity and creates crawl waste. Correcting these requires a 301 redirect to the root and a rewrite of core titles to include Visual Testing and Snapshot Plans. These adjustments will improve click-through rates and consolidate authority on the primary domain.
- Meta Length
- 245 chars (Homepage)
- Content Duplication
- /homepage is a 100% duplicate
27 · Keyword targeting — 88 score driven by 'AI Agent' niche positioning
Argos-CI earns a strong 88 for keyword targeting by prioritizing high-intent comparison queries and a forward-looking pivot to AI agents. The strategy effectively captures users looking for alternatives to legacy tools like Percy, aligning content with migration intent. While the "AI Agents" positioning is a unique differentiator, the current page lacks the long-tail modifiers, such as "framework" or "best practices," needed to dominate broader developer searches. Expanding this section to include specific guidance on testing AI-generated UIs would solidify its authority in this emerging category.
- Comparison pages
- Target '[Competitor] alternative' queries
- AI Agents page
- 741 words lacking long-tail modifiers
28 · Content portfolio health — 1.0 MinHash similarity between root and /homepage
The content portfolio is substantive but suffers from structural duplication and back-catalog decay. While 70% of dateable pages were updated within the last 90 days, the high-value comparison cluster has remained stale for 27 months. A confirmed cannibalization issue exists between the root and the /homepage URL, which shares a 1.0 MinHash similarity and dilutes internal authority. Additionally, substantive technical guides, such as the 528-word article on flaky tests, are currently orphaned with zero internal links, preventing them from contributing to the site's topical authority.
- Comparison pages
- Last modified 2024-04-29
- MinHash similarity
- 1.0 between root and /homepage
- Orphaned content
- 528-word guide with 0 in-degree
29 · Content gaps — 0 dedicated landing pages for Playwright or Cypress
Argos captures users ready to switch from competitors but misses developers at the start of their journey. The site lacks dedicated product landing pages for Playwright and Cypress visual testing, despite these being core use cases. This absence forces high-intent traffic into generic documentation rather than optimized conversion paths. Furthermore, the informational funnel is thin, lacking foundational "what is" content or a glossary. Expanding the AI Agents page into a pillar with sub-sections for different architectures would bridge the current depth gap and capture early-stage research traffic.
- Framework landing pages
- 0 dedicated pages for Playwright/Cypress
- Content depth
- AI Agents page lacks H2/H3 depth on frameworks
30 · Keyword gaps — Category head terms dominated by Applitools and Percy
Argos successfully carves out a niche in the "alternative" market but loses high-volume category head terms to rivals like Applitools and Percy. The site lacks a dedicated page optimized for the "visual regression testing" string, which is a primary entry point for the sector. While the platform targets Storybook via its deployments page, competitors like Chromatic own this keyword with deeper, more specific content. To grow, Argos must contest these shared territories by creating specific pages that directly challenge competitor feature sets and optimizing existing assets for primary industry terminology.
- Keyword targeting
- Missing 'visual regression testing' head term page
- Competitive overlap
- Storybook keywords dominated by Chromatic
32 · AI search readiness — 45 Q&A pairs and explicit robots.txt invitation
Argos-CI is an exceptional example of AI search readiness, explicitly inviting crawlers via robots.txt and providing a curated llms.txt file. The site supports markdown content negotiation, making it a primary source for RAG-based AI agents. This technical transparency is supported by 45 Question/Answer pairs in the schema, which facilitates reliable extraction for AI Overviews. To maintain this lead, the platform should resolve the 404 error on its llms-full.txt file to provide a complete context corpus and surface "Last Updated" dates on technical guides to signal freshness to agents.
- Structured data
- 45 Q&A pairs and 27 Org entities
- AI accessibility
- robots.txt uses Content-Signal headers
- Missing asset
- llms-full.txt returned 404
33 · Fix-priority hygiene — 19 health score due to broken mobile app subdomain
Argos-CI currently suffers from a poor technical health score of 19, primarily due to critical P0 issues that compromise mobile usability and performance. The application subdomain is non-functional for mobile users because it lacks viewport meta tags, resulting in a 980px horizontal overflow on login pages. On the marketing site, the primary hero image is lazy-loaded, which delays the Largest Contentful Paint and degrades the user experience. Furthermore, over 100 images lack alt text, and the documentation template uses an unconventional heading hierarchy starting at H5. Immediate remediation should focus on adding the "priority" prop to hero images, implementing 301 redirects for the duplicate /homepage, and fixing the mobile viewport settings.
- App subdomain
- 0 viewport meta and 980px overflow
- Homepage payload
- 3.8MB with 298KB script bloat
- Image hygiene
- 100+ missing alt attributes
34 · SEO composite coherence — 34 score reflects technical P0 blockers
Argos-CI presents a paradox where sophisticated content strategy and AI readiness are undermined by foundational technical failures, resulting in a low composite score of 34. The site is strategically positioned to lead in the "AI Agent" testing niche, yet it currently fails basic health checks like mobile parity on its app subdomain and index integrity due to homepage duplication. While the blog maintains high velocity, core commercial assets have not been updated since 2024, risking relevance against competitors.
- Site health score
- 19/100
- Content age
- Comparison pages last updated April 2024
- Technical risk
- 100% duplication between root and /homepage
Verdict — 77.7/100: Sophisticated AI-ready platform
Argos-CI is a strong choice for engineering teams, offering a 77.7/100 experience that balances advanced AI readiness with significant but fixable technical debt. The platform's strongest assets are its developer-centric documentation and its forward-thinking approach to AI search engines, which ensures its content remains accessible to automated agents. However, the current technical state is a paradox; while it leads in AI readiness, it fails basic mobile usability and performance checks. Specifically, the lack of mobile support on the app subdomain and the duplication of the homepage are critical weaknesses that must be addressed. This product is best suited for software engineering teams and AI agent developers using Playwright or Storybook who require a high-density technical environment and can overlook temporary mobile management limitations.
- Overall Score
- 77.7/100
90-day roadmap
| Window | Action | Modules | Expected effect |
|---|---|---|---|
| Days 1-14 | Fix P0 Technical Blockers: Redirect /homepage, add viewport meta to app, and set hero image priority. | Site Health, Technical | Immediate recovery of mobile usability and index integrity. |
| Days 15-45 | Content Refresh & Hierarchy: Update 2024 comparison pages and fix documentation heading levels (H1-H2). | Content, Onpage | Improved rankings for high-intent 'alternative' queries and better crawl depth. |
| Days 46-90 | Strategic Expansion: Launch Playwright/Cypress landing pages and deploy llms-full.txt for AI agents. | Keyword, AEO | Capture category head terms and solidify its position in AI-driven search results. |
Methodology & data notes
This review is based on a 40-page crawl of argos-ci.com conducted on August 14, 2026, using SiteList's standard examination protocol. The analysis included simulated user walkthroughs for pricing, signup, and documentation modules. Dimensions 06 (Brand mark system) and 08 (Imagery & art direction) were excluded due to insufficient data, while 31 (Programmatic SEO) was deemed not applicable to the site's current shape. Enrichment is currently pending for Google Search Console access and full consent management layer compliance. For more details on our scoring framework, visit /methodology.
Questions buyers actually ask
Is Argos-CI suitable for mobile testing?
While Argos-CI is designed for visual testing of web applications, our crawl identified that the app subdomain currently lacks a viewport meta tag, making the management interface difficult to use on mobile devices.
How does Argos-CI handle AI search engines?
Argos-CI is a top-tier example of AI search readiness, featuring a curated llms.txt file and a robots.txt that explicitly welcomes AI crawlers, ensuring its documentation is easily consumable by LLMs.
What is the main technical issue with the Argos-CI website?
The primary technical concern is structural duplication between the root domain and the /homepage URL, which splits link equity and can confuse search engine crawlers.
Does Argos-CI support Playwright and Cypress?
Yes, Argos-CI supports these frameworks, though the marketing site currently lacks dedicated landing pages for them, which is a noted content gap in our review.