Measure widget performance and privacy on your own pages.
An async script is not a complete performance result. Inspect its requests, when work happens, and what the visitor can control.
By the ComplyWCAG team · Updated 13 October 2026
Use the same page for a fair comparison
Create a staging page without the widget and an otherwise identical version with it. Record the page revision, loader/runtime release, browser version, viewport, device/CPU/network settings, and cache state. Run each condition repeatedly and compare medians rather than selecting the best run.
Measure initial page load, first panel activation, and a representative preference change separately. Capture transferred bytes, requests, layout shifts, long tasks, and time to usable content. A local lab run is not field Core Web Vitals; production experience needs real-user data over time.
Local lab · 13 October 2026
One fixture, three conditions.
Three fresh runs per condition on a static localhost fixture, at 390 × 844 pixels, with 4× CPU slowdown, 150ms latency, 200KB/s download, and browser cache disabled. The tested fixture loaded runtime 1.2.0. These are lab observations, not production Core Web Vitals or a competitor comparison.
| Condition | LCP | Layout shift | Long tasks |
|---|---|---|---|
| Without widget | 232 ms | 0.000 | 0 ms |
| Launcher ready | 236 ms | 0.000 | 0 ms |
| Panel activated | 244 ms | 0.000 | 198 ms |
Panel activation took about 1.48 seconds, including the test click, lazy resource loading, and dialog detection. This exposes an activation cost to investigate on realistic sites. No preference transformation or field interaction-latency result is included.
Download raw samples and environmentCheck the privacy behavior directly
Before activation
Open a fresh session and inspect network requests and browser storage. Identify configuration, runtime, and third-party calls. Repeat with optional consent declined.
After activation
Open the panel and change a preference. Record what is stored, which requests occur, and whether host-page form contents or full URLs are transmitted.
After reset and withdrawal
Reset the preference and withdraw optional analytics consent. Verify future optional requests stop and inspect the actual storage state.
After removal
Delete the install snippet, clear caches, and reload in a fresh session. Confirm the page works and the widget makes no further requests.
Report evidence with its limits
ComplyWCAG's marketing site gates optional analytics and marketing scripts through cookie preferences. That behavior is separate from the widget host's own consent integration. Read the privacy policy, installation documentation, and exact release behavior rather than assuming one consent banner covers every integration.
This guide does not claim a measured advantage over another vendor. Reproducible measurements should publish their environment, samples, and release identities; fixture or localhost results must not be presented as production guarantees. The site's lab verification record is maintained in the repository with the SEO action plan.
Your next step