HTTP Cache, CDN & Compression Performance Auditor

HTTP Delivery Performance and Cache Regression Monitor preserving the original audit while adding cache policy classification, CDN signals, drift and deployment gating. Returns structured, machine-readable results for repeatable research, monitoring, automation, Apify Tasks, API.

Quick start

Start with this working example and replace the target values with your own:

{
  "urls": [
    "https://example.com",
    "https://www.python.org"
  ]
}

The Actor writes structured results to the default Apify Dataset and can be used from the Store, API, schedules, Tasks, automations and MCP-compatible AI workflows.

Input

• urls — URLs: Up to 100 public HTTP(S) URLs to audit.
• previous_results — Previous delivery snapshots: Optional map keyed by URL. Enables cache/CDN/compression drift and deployment regression gating.

All integration and advanced analysis fields are optional. The default example is intentionally runnable without configuring MCP or a previous-run baseline.

Output

The Dataset exposes predictable machine-readable output. Representative fields include dataset.

Pricing

This Actor uses Pay Per Event. The current factory base price is $0.001000 per result event. The Apify Store remains the source of truth for the price and plan/tier details shown to the buyer.

Use cases

• Run the buyer-ready workflows exposed as Apify Tasks without preparing a custom integration first.
• Use the Actor from API or schedules for recurring collection, comparison or monitoring.
• Feed the structured Dataset output into spreadsheets, databases, automations or AI agents.
• Compare repeat runs when the product supports snapshots or previous-run inputs.

Automation and AI

Use the same Actor through Apify API, schedules, public Tasks and the Apify MCP server. Outputs are structured for downstream workflows and AI agents rather than requiring manual copy/paste.

Limitations

• Public websites and upstream APIs can change markup, access rules, rate limits or field availability without notice.
• Fields that are not publicly available are returned as unavailable or omitted rather than fabricated.
• Analytical outputs depend on the quality and coverage of the supplied or collected source data.
• Treat marketplace, reputation, workforce, safety or commercial signals as decision support and validate material decisions against the underlying source evidence.

Detailed documentation

Detailed documentation

Audit public URL delivery for cache policy, validators, compression, CDN signals, delivery drift and deployment regressions. Each run returns structured evidence plus deterministic remediation actions, so the result can feed CI, monitoring, agents and MCP-connected workflows without a browser or third-party API key.

What it does

For every URL, the Actor follows safe public redirects and returns the final URL, status code, Cache-Control, ETag, Last-Modified, Vary, Content-Encoding, Content-Type and Content-Length. It also calculates a simple 0-100 delivery-hygiene score and emits explicit issue flags.

Use cases

• Check cache and compression configuration after a website release.
• Audit agency or multi-site inventories on a schedule.
• Detect missing cache validators such as ETag or Last-Modified.
• Flag text, JSON, JavaScript, XML or SVG responses that appear uncompressed.
• Feed deterministic HTTP delivery checks into CI, monitoring, QA or technical SEO pipelines.

Input

Provide urls, an array of up to 100 public HTTP(S) URLs. URLs without a scheme are normalized to HTTPS.

Output

Each input produces one dataset row including status, score, cacheControl, etag, lastModified, vary, contentEncoding, contentType, hasCacheControl, hasValidator, hasVary, usesCompression, httpsFinal, and issues.

Example

Input: {"urls":["https://example.com"]}. The output reports whether caching metadata, validators, Vary and compression are present, whether the final page uses HTTPS, and any issue flags detected.

Pricing

Pay per result: $0.001 USD per URL result. This keeps recurring bulk audits inexpensive while preserving a clear result-based charging model.

Key features

• One structured cache and compression decision record per URL.
• Explicit issue flags rather than an opaque performance score alone.
• SSRF-aware validation of public targets and redirect destinations.
• No browser, external performance API, login, or paid AI dependency.

Why use this Actor

It sits between a raw curl -I check and a heavyweight browser performance suite. It is useful when you want fast, structured HTTP delivery evidence that can be scheduled, compared, stored, or used as a pipeline gate.

Why this Actor

1. It combines caching, validators, compression, Vary and HTTPS checks in one result.
2. It reports the underlying response metadata alongside the score so findings are auditable.
3. It flags likely uncompressed compressible content in machine-readable form.
4. It is designed for low-cost batch automation and requires no external API credentials.

Limitations

This Actor inspects response metadata only. It does not measure Core Web Vitals, JavaScript rendering, real-user performance, CDN internals, or authenticated sessions. Cache choices can be intentional and should be interpreted in the context of the resource. Some sites may block automated requests.

Responsible use

Audit only public URLs you are authorized to access. Keep batch sizes reasonable and respect website terms, rate limits, and applicable law.

Input reliability update — 24 October 2026

Target arrays accept non-empty strings. Identical targets are processed once per run to avoid duplicate requests and result charges. Whitespace around targets is removed. Baseline maps must be JSON objects. Existing result fields, pricing and target limits are preserved.