# Immedia (immedia.ch): agent-readiness 55/100, grade D > Rank 551 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-27T15:20:17.447Z. Page: https://qomvia.com/site/immedia-ch JSON: https://qomvia.com/api/score/immedia-ch ## Summary { "known": false, "confidence": "low", "summary": "I do not have specific pre-existing knowledge about immedia.ch in my training data. Therefore, I cannot provide a summary of what this site is or what it does from my own knowledge.", "offerings": [], "audience": null, "geography": null, "strengths": [], "unknowns": [ "Specific business model and services provided", "Target audience and market segments", "Geographical operational focus", "Competitive landscape and market positioning", "Client reputation and operational scale" ], "alternatives": [], "business": "I cannot confidently describe what this company does, for whom, or where, based on my existing knowledge.", "competitors": [] } ## Score by group - Machine access: 21/24 - Content legibility: 21/26 - Discovery surface: 6/20 - Identity & policy: 3/12 - Agent-facing performance: 3/8 - Agent protocols: 1/10 Failing checks: - [blocker] No llms.txt - [blocker] Server responds too slowly for agents - [blocker] No heading hierarchy - [blocker] No MCP endpoint to call - [improvement] No stated policy for automated access ## FAQ Q: Is Immedia readable by AI agents? A: Immedia (immedia.ch) scores 55 out of 100 for agent readiness, grade D, measured 3 days ago, on 27.09.2026. 0 of 3 agent classes we test can use the site, and 4 checks currently block agents outright. Q: What stops agents from using immedia.ch? A: The heaviest problems are: No llms.txt; Server responds too slowly for agents; No heading hierarchy; No MCP endpoint to call; No stated policy for automated access. Each one is scored from a public HTTP response, and the fix for each is listed in the signed-in report. Q: How is the Immedia agent-readiness score calculated? A: Qomvia fetches public pages of immedia.ch as an AI agent would and runs the core checks every site gets across 6 groups: Machine access, Content legibility, Discovery surface, Identity & policy, Agent-facing performance, Agent protocols. Checks are weighted by how much an agent loses when they fail, and the score is expressed out of 100. Q: How often is this score updated? A: Public scores are re-checked when the site is re-scanned; tracked domains are re-scanned weekly and their owners are alerted when a check regresses. This page shows the scan from 3 days ago, on 27.09.2026. ## Related - Leaderboard: https://qomvia.com/leaderboard - Score another site: https://qomvia.com/