Overall AI readiness score
A combined result across all audit signals.
Excellent
AI readiness audit: 7/21/2026Public technical data
Overall AI readiness assessment
How ready appzung.com is for AI systems
AppZung was independently audited by llmsmap. appzung.com currently scores 89/100 for AI readiness. The result combines AI-specific files, crawler policy, sitemap discovery, structured homepage data, and—when available—the mobile Google Lighthouse technical profile.
Audit context
llms.txt is accessible and contains 344 tokens. An expanded llms-full.txt is also available with — tokens, giving agents more direct context. A separate ai.txt policy is published.
robots.txt is available. 11 of 11 tracked AI bots are not blocked. Declared sitemaps: 1. The homepage exposes Schema.org types OnlineBusiness; 6 OpenGraph tags were found and markup completeness is 60%.
The mobile Lighthouse profile adds Performance 92/100, Accessibility 93/100, Best Practices 100/100, SEO 100/100, and experimental Agentic Browsing 67/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
- Expanded llms-full.txt
- Published AI policy
- 1 sitemap declaration
- Schema.org: OnlineBusiness
Priority improvements
- 1Complete OpenGraph and canonical homepage metadata.
llms.txt tokens344
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.
92
Performance
93
Accessibility
100
Best Practices
100
Technical SEO
67
Agentic Browsing
What these results mean
The mobile page renders efficiently; its largest visible content block appeared in 2.7 s.
Accessibility scored 93/100, Best Practices 100/100, and technical SEO 100/100. The experimental Agentic Browsing category scored 67/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
Optimise images and their loading order
Serve correctly sized modern formats, prioritise the primary visual, and lazy-load content below the first viewport.
3
Reduce network delay
Improve server response time, remove unnecessary redirects and repeat downloads, and use compression, caching, and selective preconnect hints.
4
Make controls unambiguous
Give buttons and links accessible names, associate labels with fields, and use ordered headings and semantic regions. The same structure helps screen readers and software agents understand actions.
FCP2.7 s
First content
LCP2.7 s
Main content
CLS0.025
Layout stability
TBT0 ms
Blocking time
SI2.7 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.
7/21/2026Lighthouse 13.4.0Mobile profile
AI readiness checks
Machine-readable files, crawler policy, discovery, and homepage markup.
Sitemap in robots.txt1
1 sitemap found
Schema.org (JSON-LD)
Types: OnlineBusiness
OpenGraph60%
6 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
Sitemaps
Declared discovery routes for crawlers and agents.
OpenGraph tags
Social preview metadata found on the homepage.
og:titleAppZung CodePush - The modern CodePush platform for mobile developersog:typewebsiteog:imagehttps://appzung.com/banner.pngog:urlhttps://appzung.com/og:image:urlhttps://appzung.com/banner.pngog:image:altAppZung logoSchema.org markup
Structured entities and properties exposed on the homepage.
OnlineBusiness
nameAppZungurlhttps://appzung.comdescriptionAppZung provides a modern CodePush platform for mobile developers, offering seamless app updates without going through app stores.logohttps://appzung.com/favicon.svgsameAshttps://github.com/appzung, https://twitter.com/appzungemailhello@appzung.com# AppZung > AppZung provides CodePush services for mobile app developers. The platform allows deploying updates to mobile apps instantly without going through app store reviews. Key features: - React Native and Expo support - Community support for other frameworks (Cordova) - Migration tools from AppCenter - Code signing - EU-based infrastructure - Automatic rollbacks - Staged deployments - Analytics and security controls - Great customer support ## Docs ### Core - [What is CodePush?](https://appzung.com/what-is-codepush): Core concepts and use cases - [Frequently asked questions](https://appzung.com/faq): Questions about features, migration from AppCenter, security, pricing, and technical specifications ### CodePush React Native SDK - [README](https://raw.githubusercontent.com/AppZung/react-native-code-push/refs/heads/main/README.md) - [Code signing](https://raw.githubusercontent.com/AppZung/react-native-code-push/refs/heads/main/docs/code-signing.md) ### CodePush Expo config plugin - [README](https://raw.githubusercontent.com/AppZung/expo-config-code-push/refs/heads/main/README.md) ### CLI - [README](https://unpkg.com/@appzung/cli/README.md) - [CHANGELOG](https://unpkg.com/@appzung/cli/CHANGELOG.md) ## Optional - [Developer console](https://console.appzung.com) - [Support](mailto:support@appzung.com) - [GitHub](https://github.com/appzung)
Share or continue the analysis
Share this audit
Discuss with AI
Added 7/19/2026