Overall AI readiness score
A combined result across all audit signals.
Average
AI readiness audit: 8/5/2026Public technical data
Overall AI readiness assessment
How ready spenger-echo.com is for AI systems
Spenger Echo (spenger-echo.com) received an AI-readiness score of 60/100 in an automated technical audit. llms.txt was accessible, llms-full.txt was not found, and ai.txt was not found. The robots.txt analysis found 0 explicitly allowed and 0 blocked AI crawlers, with 0 declared sitemaps. Homepage markup completeness was 10%; no Schema.org types were detected and 4 OpenGraph tags were detected. Results reflect the public site response observed on 2026-08-05T00:35:47.397Z.
Audit context
llms.txt is accessible and contains 285 tokens. No accessible llms-full.txt was detected, so deeper context still has to be assembled from regular pages. No separate ai.txt policy was detected; it is optional, but can clarify training, retrieval, and attribution preferences.
robots.txt is available. 11 of 11 tracked AI bots are not blocked. Declared sitemaps: 0. No Schema.org type was detected on the homepage. 4 OpenGraph tags were found and markup completeness is 10%, leaving more entity interpretation to crawlers.
The mobile Lighthouse profile adds Performance 71/100, Accessibility 95/100, Best Practices 100/100, SEO 92/100, and experimental Agentic Browsing 86/100. These signals have a limited weight: they complement rather than replace llms.txt, robots.txt, and structured-data checks.
Confirmed strengths
- Accessible llms.txt
Priority improvements
- 1Add llms-full.txt for richer first-party context.
- 2Declare the current sitemap.xml in robots.txt.
- 3Add JSON-LD for the organisation, website, and core entities.
- 4Complete OpenGraph and canonical homepage metadata.
llms.txt tokens285
llms-full.txt tokens—
ai.txt
sitemap.xml
Google Lighthouse technical profile
A mobile Lighthouse measurement. Google’s experimental Agentic Browsing category is explained separately and does not replace the broader llmsmap AI-readiness score.
71
Performance
95
Accessibility
100
Best Practices
92
Technical SEO
86
Agentic Browsing
What these results mean
Mobile performance is 71/100, with the largest visible content block appearing in 5.0 s and the browser main thread blocked for 0 ms. Layout shift was 0.219. The main thread is where the browser runs JavaScript, calculates layout, and paints the page; long work there delays both user input and browser-agent actions.
Accessibility scored 95/100, Best Practices 100/100, and technical SEO 92/100. The experimental Agentic Browsing category scored 86/100. It measures signals Google currently tests for software agents and is shown separately from the llmsmap AI-readiness score.
1
Free the main thread and accelerate the first view
Split long JavaScript tasks, defer non-critical scripts and styles, and shorten blocking request chains. This helps the primary content appear sooner and makes controls usable earlier.
2
Reduce code that loads without helping the page
Remove unused CSS and JavaScript, load heavy widgets on demand, and limit third-party scripts. Less code means less parsing and background work on the device.
3
Optimise images and their loading order
Serve correctly sized modern formats, prioritise the primary visual, and lazy-load content below the first viewport.
4
Reduce network delay
Improve server response time, remove unnecessary redirects and repeat downloads, and use compression, caching, and selective preconnect hints.
FCP1.4 s
First content
LCP5.0 s
Main content
CLS0.219
Layout stability
TBT0 ms
Blocking time
SI2.1 s
Visual speed
Metric glossary
- FCP · First content
- When the first text or image appeared on screen.
- LCP · Main content
- When the largest visible element in the first viewport rendered.
- CLS · Layout stability
- How much content shifted unexpectedly while loading; lower is better.
- TBT · Blocking time
- How long the browser main thread could not respond quickly to input.
- SI · Visual speed
- How quickly the visible viewport filled with content.
8/5/2026Lighthouse 13.4.1Mobile profile
AI readiness checks
Machine-readable files, crawler policy, discovery, and homepage markup.
llms-full.txt
Full version was not found
ai.txt
ai.txt file was not found
Sitemap in robots.txt
Sitemap is not declared in robots.txt
Schema.org (JSON-LD)
Schema.org markup was not found on the homepage
OpenGraph10%
4 OG tags found
AI bot access
Based on robots.txt analysis
GPTBotNot mentioned
OAI-SearchBotNot mentioned
ChatGPT-UserNot mentioned
Google-ExtendedNot mentioned
ClaudeBotNot mentioned
Claude-SearchBotNot mentioned
Claude-UserNot mentioned
BytespiderNot mentioned
CCBotNot mentioned
PerplexityBotNot mentioned
Perplexity-UserNot mentioned
OpenGraph tags
Social preview metadata found on the homepage.
# Spenger Echo > Das Spenger Echo ist die Online-Ausgabe eines monatlich erscheinenden Stadtmagazins für Spenge und die umliegenden Gemeinden. Es wird vom KV-Verlag Claudia Vogt betrieben und bietet aktuelle Informationen, Veranstaltungshinweise und Beiträge aus dem lokalen Leben. Das Spenger Echo vereint redaktionelle Inhalte, den offiziellen Veranstaltungskalender der Stadt Spenge sowie gewerbliche Anzeigen auf einer gemeinsamen Plattform. Neben aktuellen Artikeln finden Leser:innen hier auch die vollständigen PDF-Ausgaben der Printausgabe. Die Website richtet sich an Bürgerinnen und Bürger der Stadt Spenge sowie angrenzender Orte und möchte ein lebendiges Bild der Region vermitteln. ## Artikel in verschiedenen Übersichten - [Alle Beiträge chronologisch](https://spenger-echo.com/aktuelles) - [Beiträge nach Rubriken](https://spenger-echo.com/aktuelles/rubriken) - [Beiträge nach Orten](https://spenger-echo.com/aktuelles/orte) ## Veranstaltungskalender - [Veranstaltungskalender der Stadt Spenge](https://spenger-echo.com/kalender) ## Optional - [PDF-Ausgaben des Stadtmagazins](https://spenger-echo.com/printausgaben/)
Share or continue the analysis
Share this audit
Discuss with AI
Added 8/5/2026