# HubVibe Performance Audit

> HubVibe Performance Audit is a paid API for AI agents from hubvibe-io.com, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-15).

Measures DOM node count, transferred bytes, and HTTP request count from a single real page load without running a full Lighthouse audit.

## Facts

- Endpoint: POST https://hubvibe-io.com/audit/performance
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/hubvibe-performance-audit-22046ac5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vpvydEm5jmUY0UbRibhhG

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability hubvibe-performance-audit-22046ac5 -d '<json body>'
```

Example prompt: Can you check how many DOM nodes, total bytes transferred, and HTTP requests my homepage at https://example.com makes on a real page load?

## When to prefer this

Choose this endpoint when you need fast, lightweight page load stats (DOM nodes, bytes, request count) without the overhead and cost of a full Lighthouse audit. It is ideal for regression checks, CI pipelines, or quick comparisons where you only care about raw payload and complexity metrics rather than scored performance categories.

## Known failure modes

- URL is unreachable or returns a non-200 status — audit cannot complete
- Page takes too long to load and the session times out
- JavaScript-heavy SPA fails to fully render before metrics are captured
- Malformed or missing URL in the request body returns a validation error
- Network restrictions or bot-blocking on the target page prevent a real load

## How this service works

Page speed and page weight audit of a web page from one real browser load: total bytes transferred, HTTP request count and DOM node count, measured rather than estimated, with findings when the page is heavy. Page-weight signals, not Core Web Vitals.

## Output

Returns three lightweight page load metrics from a real browser session: the total DOM node count, the number of bytes transferred over the network, and the total HTTP request count. No Lighthouse scores or full audit report is included.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "format": "uri",
   "examples": [
    "https://example.com"
   ],
   "description": "Live, fetchable http(s) URL to audit."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/hubvibe-performance-audit-22046ac5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from hubvibe-io.com](https://www.zero.xyz/host/hubvibe-io.com/llms.txt)