# does-site-use-lazy-loading

> does-site-use-lazy-loading is a paid API for AI agents from site.intel.rallylive.ca, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-18).

Detects whether a website uses native lazy loading by fingerprinting the homepage HTML and response headers, returning a yes/no answer with evidence snippet.

## Facts

- Endpoint: GET https://site.intel.rallylive.ca/site/uses/lazy-loading?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/does-site-use-lazy-loading-e009db2d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ha2JArT1vNsnRtSLx3u-Q

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 does-site-use-lazy-loading-e009db2d
```

Example prompt: Can you check if shopify.com uses native lazy loading on its homepage? I want to know if they've adopted it and see what the evidence looks like.

## When to prefer this

Use this endpoint when you need a fast, low-cost ($0.01) single-domain check for native lazy loading specifically. Prefer this over a bulk endpoint when checking just one domain, and over a full page audit tool when you only need technographic signal (yes/no + evidence) rather than a comprehensive performance report. Ideal for enriching CRM leads, validating competitor stacks, or automating pre-migration audits one domain at a time.

## Known failure modes

- Domain does not resolve or site is unreachable — returns error with no result
- Site blocks automated crawling (robots.txt, bot detection, 403/429 responses) — may return no evidence
- Homepage redirects or requires authentication — fingerprinting may be incomplete
- Dynamic/SPA sites that inject lazy loading via JavaScript after page load may be missed by HTML-only scanning
- Ambiguous or partial fingerprint matches may produce false negatives

## How this service works

Does a website use Native lazy loading? Fetches the page (homepage for a bare domain) and matches Native lazy loading's fingerprints in the HTML and response headers, returning yes/no with the evidence snippet and the category (performance). Technographics for sales, competitor research and migration planning, one technology per call. $0.01 per check.

## Output

Returns a yes/no boolean indicating whether the site uses native lazy loading, along with the matched evidence snippet from the HTML or response headers that triggered the fingerprint match, and the technology category ('performance').

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/does-site-use-lazy-loading-e009db2d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from site.intel.rallylive.ca](https://www.zero.xyz/host/site.intel.rallylive.ca/llms.txt)