v2.0 adds a latency badge to every captured fire. It's the simplest way to spot a tag that's slow enough to delay your conversion.
How it's measured
At the moment of capture, Pixel Auditor stamps the fire with performance.now(). The result is the wall-clock time of the fire relative to the navigation start, in milliseconds.
The pills
| Color | Range | Interpretation |
|---|---|---|
| 142ms | < 500 ms | Healthy. Tag is firing close to navigation start, before the user notices. |
| 812ms | 500–2000 ms | Slow. Likely waiting on a CMP, a slow tag library, or a deferred load. |
| 2.4s | > 2000 ms | Problem. The tag is firing well after the page is interactive — high risk of being missed for short sessions. |
Common reasons for high latency
- CMP-gated load. The tag library doesn't load until consent is granted. If your CMP banner takes 1.5 s to render, your tags fire 1.5 s+ after navigation.
- Deferred or async script with a big bundle. Tag libraries 100 KB+ on slow connections take noticeable time.
- Network-blocked tag. Vendor's edge is slow or geographically distant.
- SPA route change with a hand-rolled trigger. The trigger fires after every render rather than on the route event itself.
How to investigate
- Click the slow row to open the drawer.
- Note the method (fetch / XHR / Image / sendBeacon).
- Open Chrome DevTools Network tab and filter by the same vendor host.
- Compare timings — Pixel Auditor's latency includes the JS interception path; DevTools shows the actual network timing.
why
Slow conversion tags directly correlate with reported revenue loss. A 2 s latency on a purchase tag means every user who navigates away within 2 seconds of completing the purchase is missing from your analytics.