Independent technical audit

fault-project.com

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 fault-project.com is for AI systems

38/100

fault (fault-project.com) a obtenu 38/100 lors de l’audit technique automatisé de préparation à l’IA. llms.txt était introuvable, llms-full.txt avait aucun fichier accessible et ai.txt était introuvable. L’analyse de robots.txt a trouvé 0 robots IA explicitement autorisés, 0 bloqués et 0 sitemaps déclarés. La complétude du balisage de la page d’accueil atteint 0% ; aucun type Schema.org détecté. Balises OpenGraph détectées : 0. Les résultats correspondent aux réponses publiques observées le 2026-10-24T04:44:01.671Z.

Audit context

llms.txt was not available as a readable text file during the latest check. That removes the shortest first-party map of the site for an AI agent. No separate ai.txt policy was detected; it is optional, but can clarify training, retrieval, and attribution preferences.

robots.txt was not found, so explicit crawler policy could not be confirmed. 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 56/100, Accessibility 88/100, Best Practices 96/100, SEO 92/100, and experimental Agentic Browsing 100/100. These signals have a limited weight: they complement rather than replace llms.txt, robots.txt, and structured-data checks.

Confirmed strengths

Strong Google agentic signals

Priority improvements

1Restore a readable /llms.txt with canonical links and concise descriptions.
2Add llms-full.txt for richer first-party context.
3Publish robots.txt with explicit search and AI crawler rules.
4Declare the current sitemap.xml in robots.txt.

llms.txt tokens4,009

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.

Mobile · Lighthouse

Performance

Accessibility

Best Practices

Technical SEO

100

Agentic Browsing

What these results mean

Mobile performance is 56/100, with the largest visible content block appearing in 12.9 s and the browser main thread blocked for 0 ms. Layout shift was 0. 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 88/100, Best Practices 96/100, and technical SEO 92/100. The experimental Agentic Browsing category scored 100/100. It measures signals Google currently tests for software agents and is shown separately from the llmsmap AI-readiness score.

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.

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.

Optimise images and their loading order

Serve correctly sized modern formats, prioritise the primary visual, and lazy-load content below the first viewport.

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.

FCP8.8 s

First content

LCP12.9 s

Main content

CLS0

Layout stability

TBT0 ms

Blocking time

SI8.8 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.