Warp Performance Analyzer inspects website performance locally when you open its toolbar popup or DevTools panel. It has no analytics, backend connection, remote code, or automatic browsing-history upload. We do not receive, sell, share, or use your inspection data for advertising. No developer or third party receives access to this local data through the extension.

Page inspections

Opening the toolbar popup reads the active page's origin, a bounded title, navigation and resource timing, retained LCP and layout-shift entries, limited element descriptions (tag names and constrained IDs/classes), and public technology markers such as generator metadata and sanitized script paths. Resource URLs have credentials, query strings, and fragments removed before entering the extension. Paths, titles, and element identifiers can still contain sensitive information. The snapshot stays in popup memory and is discarded when the popup closes, except for measurements and paths you explicitly save through an experiment.

A bounded probe in the page's JavaScript context checks up to 500 DOM nodes for React-owned property names and whether two named library globals exist. Only recognized marker names are returned, never property values, page objects, or script contents.

Opening the popup also arms a local interaction observer in the tab's isolated extension context. It records event timing and constrained target descriptions for at most 200 interaction IDs for up to 15 minutes or until the document is discarded. This observer may continue while the popup is closed. Reopening or refreshing the popup reads the sample; it does not record typed text, key values, mouse coordinates, or form values. This is a bounded responsiveness sample, not a final visit-wide INP measurement.

Advertising and analytics tag inspection

The optional Inspect tag IDs button examines recognized script and resource URLs on the current page. It extracts only allowlisted public configuration IDs for supported providers (for example Google tags, Meta Pixel, AdSense, Clarity, Hotjar, and TikTok). Unrelated query values, visitor IDs, cookies, form data, and page text are not returned. Results stay in popup memory. The presence of a tag is not proof that events were sent.

DevTools inspection

The optional Warp Analyzer DevTools panel observes completed requests after an observed navigation while the panel is open. It retains at most 2,000 request summaries: sanitized resource paths, origin, type, response status, duration, response body byte count when available, protocol, and these response headers only: cache-control, age, cf-cache-status, cf-ray, x-cache, x-litespeed-cache, etag, last-modified, and content-encoding. Header values are limited to 200 characters. It does not read request headers, cookies, authentication tokens, request or response bodies, or form values. No HAR file is stored or exported. Captures are discarded on the next observed navigation or when DevTools closes.

Experiments and local storage

Clicking Block & retest temporarily blocks one sanitized resource path, including requests with query variants, for the selected resource type in the selected tab and site scope. This may break the page. It does not change the website's server or configuration. The TEST badge and restore button indicate an active test. The rule stays active until restored, the tab closes, or the browser session ends. Navigating away does not by itself guarantee removal; returning to the tested site in that tab can still apply the rule until restored.

chrome.storage.local holds active experiment records and up to 30 completed tests. Each record contains the site hostname, sanitized resource URL, tab and rule IDs, resource type, timestamps, and before/after numeric performance measurements. This data stays on this device and is not synced by the extension. Completed records remain until cleared or replaced by newer records. Clear local history removes completed records; restore an active test to stop its rule. Uninstalling the extension removes its extension storage and rules. Browser session rules are reconciled with local records when the background worker starts.

The Warp favicon and logo are packaged locally. Opening Explore Warp is a user action that visits warpperformance.com under that website's own privacy practices. Inspection data is not attached to that link. For privacy or support questions, use the contact options at https://warpperformance.com.

Limited Use

Warp Performance Analyzer's use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Data is used only for the disclosed website performance inspection and local testing features.

 

Questions about billing?

Send us your account email and order details and we’ll help.

Contact support