Independent technical audit

tempmail.pw

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 tempmail.pw is for AI systems

39/100

Temp Mail PW - AI Discoverable Privacy & Productivity Platform (tempmail.pw) erreichte im automatisierten technischen Audit 39/100 Punkte bei der KI-Bereitschaft. llms.txt war nicht auffindbar, llms-full.txt hatte keine erreichbare Datei und ai.txt war nicht auffindbar. Die robots.txt-Analyse ergab 11 ausdrücklich erlaubte und 0 blockierte KI-Crawler sowie 1 deklarierte Sitemap. Die Vollständigkeit des Homepage-Markups lag bei 0%; es wurden keine Schema.org-Typen erkannt. Erkannte OpenGraph-Tags: 0. Die Ergebnisse entsprechen den öffentlich erreichbaren Antworten der Website zum Prüfzeitpunkt 2026-10-25T08:53:57.055Z.

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 is available. 11 of 11 tracked AI bots are not blocked. Declared sitemaps: 1. 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 43/100, Accessibility 83/100, Best Practices 96/100, SEO 92/100, and experimental Agentic Browsing 19/100. These signals have a limited weight: they complement rather than replace llms.txt, robots.txt, and structured-data checks.

Confirmed strengths

1 sitemap declaration

Priority improvements

1Restore a readable /llms.txt with canonical links and concise descriptions.
2Add llms-full.txt for richer first-party context.
3Add JSON-LD for the organisation, website, and core entities.
4Complete OpenGraph and canonical homepage metadata.

llms.txt tokens1,552

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

Agentic Browsing

What these results mean

Mobile performance is 43/100, with the largest visible content block appearing in 13.2 s and the browser main thread blocked for 180 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 83/100, Best Practices 96/100, and technical SEO 92/100. The experimental Agentic Browsing category scored 19/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.4 s

First content

LCP13.2 s

Main content

CLS0.219

Layout stability

TBT180 ms

Blocking time

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