agentic checks passed 50% readiness - how well this site can be read, trusted and transacted with by AI agents
Last checked
javsex.cfd is live and passes 11 of 30 agentic-readiness checks (50%). It runs on wordpress on cloudflare over HTTPS.
For AI agents, javsex.cfd's strongest signals are tidy, crawlable markup, fully indexable pages, a visually stable layout, and a clear canonical URL. Approximately 1450 DOM nodes - consider simplifying.
Its main gaps are text that is hard for agents to extract, no structured tables or lists, few clear definitions, and no self-contained answer passages. The weakest area is Trust & transparency; addressing it first would raise this score the most.
Agent interaction
~Semantic HTML5 & AccessibilityMissing lang attribute on <html> tag
✓Clean, Crawlable HTMLPage has title and meta description
✗Extraction Friction ScoreFew pages have voice-friendly lead paragraphs
✓Indexability & Snippet EligibilityPages are indexable and snippet-eligible - the precondition for Google AI features is met
✓Layout Stability & Responsiveness48/48 images lack explicit width/height - the most common cause of layout shift (CLS)
✓Canonical URL StrategySingle canonical tag present (no duplicates)
✓Page Speed: Page SizeApproximately 1450 DOM nodes - consider simplifying
✗Table & List ExtractabilityNo HTML tables found across homepage
~Sentence AtomicityAverage 39% atomic sentences across 1 pages (target 40%+)
✓Entity DensityAverage entity density 73.5% across 1 pages (target >15%)
✗Definition PatternsOnly 1 definition pattern(s) found
✗Answer Capsule Pattern0/4 H2 sections have 15-30 word self-contained capsules (0%)
Structured data
✓Schema.org Structured DataOrganization or LocalBusiness schema found on homepage
✓Schema Coverage & Depth@id linking found - schema types are connected in a graph
✗Speakable SchemaNo SpeakableSpecification schema found across homepage
AI discovery
✗llms.txt FileNo llms.txt file found at https://javsex.cfd/llms.txt (connection failed)
~robots.txt for AI CrawlersNo explicit AI crawler rules in robots.txt
✓Sitemap CompletenessSitemap index found, indicating organized sitemap structure
✗RSS/Atom FeedRSS/Atom feed link tag found in homepage <head>
✗Internationalization SignalsNo hreflang alternate links found
✗Content Licensing & AI PermissionsNo ai.txt file found
Trust & transparency
~Entity Authority & E-E-A-TNo phone number found on homepage
✗Creator TransparencyCreator visibility is weak on content-like pages
✗Methodology TransparencyLittle content-production or review transparency is visible
~AI Assistance DisclosureNo AI-assistance disclosure found on sampled pages (neutral - the engine cannot tell whether AI was used)
~Visible Date Signal46 visible <time> element(s) with datetime attribute found across homepage
✓Title & Meta QualityTitles are present, unique, and well-sized, and pages carry meta descriptions
~Content Freshness SignalsNo JSON-LD date properties (datePublished/dateModified) found across homepage
✗Author & Expert SchemaNo Person schema found across homepage
Every check is a verifiable fact about javsex.cfd's live pages. Scoring follows Google Lighthouse agentic-browsing: a fraction of concrete checks, not an invented 0-100.
How to improve for AI agents
The highest-impact changes to make javsex.cfd more agent-ready, in priority order.
1 Add structured tables and lists critical impactmedium effort
Present javsex.cfd's comparison and spec data as real HTML tables and lists agents can extract.
2 Add content freshness signals high impactlow effort
Refresh and re-date javsex.cfd's key pages so agents see it as maintained.
