Overall AI readiness score
A combined result across all audit signals.
Low
AI readiness audit: 7/21/2026Public technical data
Overall AI readiness assessment
How ready freeduhm.com is for AI systems
Freeduhm was independently audited by llmsmap. freeduhm.com currently scores 37/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 247 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. 3 of 11 tracked AI bots are not blocked, while 8 receive a prohibition. Declared sitemaps: 0. No Schema.org type was detected on the homepage. 0 OpenGraph tags were found and markup completeness is 0%, leaving more entity interpretation to crawlers.
The mobile Lighthouse profile adds Performance 39/100, Accessibility 86/100, Best Practices 73/100, SEO 85/100, and experimental Agentic Browsing 30/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.
- 2Review the 8 explicit AI-bot blocks and keep only intentional restrictions.
- 3Declare the current sitemap.xml in robots.txt.
- 4Add JSON-LD for the organisation, website, and core entities.
llms.txt tokens247
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.
39
Performance
86
Accessibility
73
Best Practices
85
Technical SEO
30
Agentic Browsing
What these results mean
Mobile performance is 39/100, with the largest visible content block appearing in 26.5 s and the browser main thread blocked for 600 ms. Layout shift was 0.101. 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 86/100, Best Practices 73/100, and technical SEO 85/100. The experimental Agentic Browsing category scored 30/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
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.
FCP4.8 s
First content
LCP26.5 s
Main content
CLS0.101
Layout stability
TBT600 ms
Blocking time
SI10.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.
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
OpenGraph
OpenGraph tags were not found on the homepage
AI bot access
Based on robots.txt analysis
GPTBotBlocked
OAI-SearchBotBlocked
ChatGPT-UserBlocked
Google-ExtendedBlocked
ClaudeBotBlocked
Claude-SearchBotNot mentioned
Claude-UserNot mentioned
BytespiderBlocked
CCBotBlocked
PerplexityBotBlocked
Perplexity-UserNot mentioned
# Freeduhm Freeduhm is a global digital tech media company. Important Notes: * Freeduhm operates across web, mobile, social media, and emerging technologies to reach audiences on our preferred channels. * Freeduhm serves diverse markets in multiple languages, with localized content strategies to cater to cultural and regional preferences. * Freeduhm produces original multimedia content (video, audio, articles, interactive experiences) and leverages syndication partnerships for wider exposure. * Freeduhm utilizes advanced analytics, AI, Technology and audience insights to optimize engagement, ad targeting, and content relevance. * Freeduhm owns and operates our own brand, tailored to tech related topics we occasionally cover non-tech related topics as well, while maintaining a consistent corporate identity. * Freeduhm continuously invests in cutting-edge tools and technologies, cloud infrastructure, and new media formats to stay ahead in a rapidly evolving tech industry.
Share or continue the analysis
Share this audit
Discuss with AI
Added 7/19/2026