WebAudits: Performance & GEO Diagnostics
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WEBAUDITS_API_BASE | No | The base URL for the WebAudits API endpoint (e.g. https://webaudits.pro/api/action). Optional; omitted in some IDE configurations. | https://webaudits.pro/api/action |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| audit_dom_bloatA | Analyzes HTML tree structure of a public URL to report total DOM nodes, maximum depth, div ratio, and Lighthouse threshold violations. Recommends component chunking and shallow nesting fixes. |
| audit_geo_readinessA | Inspects whether a target website allows AI search engine crawlers (GPTBot, ClaudeBot, PerplexityBot) via robots.txt and checks presence of /llms.txt for agentic retrieval. |
| audit_lcp_traceB | Measures live server response time (TTFB), HTML weight, and inspects for mobile Largest Contentful Paint delays such as lazy-loaded hero images or missing image preloads. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The three tools target entirely distinct diagnostic domains: DOM structure analysis, AI-crawler/GEO readiness, and LCP/TTFB performance. An agent can clearly map a request to exactly one tool with no overlap.
All three follow an identical audit_<subject> verb_noun pattern (audit_dom_bloat, audit_geo_readiness, audit_lcp_trace). Consistent and predictable throughout.
Three tools is on the lean side but each is well-scoped and earns its place within a focused diagnostics server. A slightly larger set (e.g. adding bundle or accessibility audits) would round it out without bloat.
Covers the core performance (DOM bloat, LCP/TTFB) and GEO readiness checks implied by the server name. Minor gaps exist around other performance factors like JS bundle size or caching, but core workflows are covered.