Back
https://llmadvisor.ai/
Thu, 16 Apr 2026 02:36:02 GMT
Site Audited
llmadvisor.ai
https://llmadvisor.ai/
Completed
Thu, 16 Apr 2026 02:36:02 GMT
Duration
335ms
Overall
100 · A+
100
A+
A score
llmadvisor.ai
Audit completed
Strong technical setup overall. No major failures were detected in this audit.
Main issue: No major failures were detected in this audit.
↺ Run again ⬇ Export Excel View fixes 🏅 View Leaderboard
Edge/network/header analysis · bot simulation · crawlability evidence
Alert
No urgent crawler access problem was found in this audit.
Advise
Your most important bots appear to be reaching the site normally, so the main opportunities are lower-priority hardening and polish.
Action Step
Keep monitoring crawler access and focus next on response headers, caching, and small technical improvements.
Key Findingswhat failed first
Passed
✓
HTTPS is enabled.
✓
HSTS is valid.
✓
robots.txt is present.
Fix Priorityrecommended next steps
1Review tracking flags and confirm only intended analytics scripts are loaded.
2Review the detailed sections below for lower-priority hardening opportunities.
3Review the detailed sections below for lower-priority hardening opportunities.
4Review the detailed sections below for lower-priority hardening opportunities.
Speed
100
Excellent response path
Security
100
core protections are present
SEO
100
crawl assets are discoverable
Bot Access
100
bot responses are aligned
Result Integrity98% measurement confidence · 1 conflict
Speed Confidence
100%
Security Confidence
94%
SEO Confidence
100%
Bot Confidence
100%
LOWCSP contains 'unsafe-inline' — inline script execution is permitted, which is the most common CSP bypass vector
Replace 'unsafe-inline' with nonce-based or hash-based script allowlisting. This single change has more XSS-protection impact than any other CSP improvement.
Main fetch: ok
Security: ok
SEO: ok
20/20 bot probes succeeded
Bot Importance Hierarchy all ranked bots stable
Ranks crawlers by practical impact so users can tell whether a failure is mission-critical, growth-related, or lower-priority.
Tier 1
Mission Critical
Search and AI discovery bots that most directly affect visibility and retrieval.
stable tier
Google
Stable
9ms / no crawler override
OAI Search
Stable
18ms / no crawler override
GPTBot
Stable
9ms / no crawler override
Vertex AI
Stable
19ms / no crawler override
ChatGPT
Stable
18ms / no crawler override
Perplexity
Stable
10ms / no crawler override
Claude
Stable
9ms / no crawler override
Tier 2
Growth & Distribution
Bots that influence secondary reach, ecosystem visibility, and social preview distribution.
stable tier
Bing
Stable
9ms / no crawler override
Meta AI
Stable
20ms / no crawler override
Amazon
Stable
15ms / no crawler override
Mistral
Stable
18ms / no crawler override
Apple
Stable
8ms / no crawler override
Facebook
Stable
12ms / no crawler override
Twitter
Stable
12ms / no crawler override
LinkedIn
Stable
13ms / no crawler override
Tier 3
Reference & Baseline
Supportive or baseline agents useful for comparison and lower-priority monitoring.
stable tier
ByteDance
Stable
16ms / no crawler override
CommonCrawl
Stable
16ms / no crawler override
DuckDuck
Stable
6ms / no crawler override
Chrome
Stable
13ms / no crawler override
BotWatcher
Stable
13ms / no crawler override
consistent access caution anomaly / blocked
Anomaly Detection peak low drift
Asset Discovery 7/8 public assets visible
HTTPS
TLS active
Cloudflare
MISS
Compression
br
robots.txt
crawl rules live
Sitemap
3 URLs
llms.txt
AI crawler guide
Structured Data
5 schema blocks
Analytics
none detected
Map routes are derived from bot simulation responses and compliance checks. This board is audit-driven, not global telemetry.
Bot Access & Consistency100▾
✓
Bot Access & Consistency 100
Major tested bots were treated consistently in this audit.
ℹ
Why this matters
AI search visibility, social previews, and crawler trust can drop when some agents receive different responses or are blocked.
✓
Different bots received different responses
No response divergence detected
✓
Status codes stayed consistent
All tested agents received the same response class
✓
AI crawler guidance
llms.txt present
Bot Status Strip
Google
Bing
DuckDuck
Apple
GPTBot
Claude
Perplexity
Facebook
Twitter
LinkedIn
Chrome
BotWatcher
amazonbot
bytespider
ccbot
chatgptuser
oaisearchbot
mistralaiuser
googlevertexbot
metaexternalagent
BotResultHTTProbots.txtNotes
Googlebot 2.1Accessible200allowed9ms
Bingbot 2.0Accessible200allowed9ms
DuckDuckBotAccessible200unspecified6ms
ApplebotAccessible200unspecified8ms
GPTBot (OpenAI)Accessible200allowed9ms
ClaudeBot (Anthropic)Accessible200allowed9ms
PerplexityBotAccessible200unspecified10ms
Facebook External HitAccessible200unspecified12ms
TwitterbotAccessible200unspecified12ms
LinkedInBotAccessible200unspecified13ms
Chrome (baseline)Accessible200unspecified13ms
BotWatcherAudit/1.0Accessible200unspecified13ms
amazonbotAccessible200unspecified15ms
bytespiderAccessible200unspecified16ms
ccbotAccessible200unspecified16ms
chatgptuserAccessible200unspecified18ms
oaisearchbotAccessible200unspecified18ms
mistralaiuserAccessible200unspecified18ms
googlevertexbotAccessible200unspecified19ms
metaexternalagentAccessible200unspecified20ms
Performance100▾
TTFB
183ms
Total Time
183ms
Body Size
84.0 KB
Status
200
Compression
br
CF Cache
MISS
✓
HTTPS
Secure TLS
✓
TTFB: 183ms
Excellent
✓
HTTP 200
OK
✓
Compression
Encoding: br
✓
Cache-Control
public, max-age=3600, must-revalidate
✓
ETag
Present
✓
Redirects: 0
No redirects
✓
Cloudflare CDN
CF-Cache-Status: MISS
Security Headers100▾
✓
HTTPS / TLS
Secure
✓
HSTS
max-age=31536000; includeSubDomains; preload
✓
Content-Security-Policy
default-src 'self' https:; script-src 'self' https://cdn.jsdelivr.net https://cd…
✓
X-Content-Type-Options
nosniff
✓
Clickjacking protection
Via CSP frame-ancestors
✓
Referrer-Policy
strict-origin-when-cross-origin
✓
Permissions-Policy
camera=(), microphone=(), geolocation=()
✓
Cross-Origin-Opener-Policy
same-origin
✓
Cross-Origin-Embedder-Policy
credentialless
SEO & Crawlability100▾
✓
Meta title
LLM Advisor — AI Model Comparison, API Reference & Project Hub | llmad…
✓
Meta description
llmadvisor.ai is a developer's AI hub: compare GPT-5.4, Claude Sonnet 4.6, and Gemini 3.1 side by si…
✓
Canonical URL
https://llmadvisor.ai/
✓
Viewport meta
width=device-width, initial-scale=1.0, viewport-fit=cover
✓
robots.txt
1 sitemap(s)
✓
Googlebot access
Allowed
✓
Sitemap.xml
3 URL(s)
✓
Open Graph
og:title = "llmadvisor.ai — AI Model Comparison & Developer Pr…"
✓
JSON-LD Structured Data
WebSite, Person, Organization, WebApplication, FAQPage
✓
llms.txt (AI compliance)
Present - AI-era ready
Third-Party & Privacy▾

Analyzes raw HTML source for third-party domains, consent tooling, render-blocking scripts, and tracking pixels. Tools injected at the edge (Cloudflare Zaraz, CF Web Analytics) or loaded dynamically via JS after page load will not appear here — use your browser's Network tab for a complete runtime picture. Results are informational and do not affect your score.

3 third-party domains · 0 render-blocking scripts · ✗ No consent tool
No analytics detected — you may be flying blind on traffic data
Third-Party Domains in Source
cdn.jsdelivr.net
docs.google.com
llmadvisor.ai
Platforms Detected in Source
○ Google Analytics 4○ Universal Analytics (UA)○ Google Tag Manager○ Cloudflare Web Analytics○ Cloudflare Zaraz○ Plausible○ Fathom○ Matomo / Piwik○ Hotjar○ Microsoft Clarity○ Segment○ Mixpanel○ Heap○ Amplitude○ HubSpot○ Intercom○ Adobe Analytics○ Meta (Facebook) Pixel○ TikTok Pixel○ Crisp Chat
Domain Surface▾

Probes common subdomains and non-standard HTTP/HTTPS ports to map the visible attack surface of this domain. Results are based on network-layer responses only. Informational — does not affect your score.

!
Wildcard DNS detected — subdomain results are not meaningful
A probe of a guaranteed-nonexistent subdomain (wildcardtestconfirmationbotwatcherai.llmadvisor.ai) returned HTTP 530, definitively confirming a wildcard DNS record (*.llmadvisor.ai) is active and answering all subdomain requests. Individual subdomain scan results are unreliable when wildcard DNS is present and have been suppressed.
Non-standard Ports
PortStatusHTTPTTFB
http:8080Responded30173ms
https:8443Responded20085ms
http:3000Responded30176ms
http:8000Responded30178ms