# Long Animation Frames for ecommerce INP in 2026

Observe long-animation-frame entries in the field, map script URLs to slow PLP filters and cart taps, and fix INP on Shopify, WooCommerce and Magento.

- Date: 2026-11-21
- Category: Performance

## Table of contents

- Why Long Animation Frames for ecommerce INP beats guesswork
- What changed with LoAF and INP attribution in 2025 and 2026
- How Long Animation Frames for ecommerce INP are measured
- Production checklist for Long Animation Frames on storefronts
- What breaks Long Animation Frames for ecommerce INP programmes
- How to measure progress after LoAF fixes
- Related work on this site
- FAQ
  - What are Long Animation Frames for ecommerce INP in practice?
  - Do I need LoAF if I already run Lighthouse on product pages?
  - Where should Long Animation Frames for ecommerce INP fire on my site?
  - Can fixing LoAF issues hurt analytics or personalisation data?

Long Animation Frames for ecommerce INP is how I move from guessing which script killed a facet tap to naming the file, URL, and frame budget that blocked paint. I watch `long-animation-frame` entries in the field while shoppers use PLPs, quick views, and cart drawers on Shopify, WooCommerce, and Magento stacks. I am Alan Vo, a Gold Coast web developer with eighteen years of catalogue work. This note is for owners who already chase Interaction to Next Paint but still get mystery slow interactions on mobile.

The [Interaction to Next Paint (INP) guide on web.dev](https://web.dev/articles/inp) defines good responsiveness as 200 milliseconds or less at the 75th percentile in field data. INP cares about the full path from input through processing to the next paint. The [Long Animation Frames API on Chrome for Developers](https://developer.chrome.com/docs/web-platform/long-animation-frames) measures frames where rendering work runs longer than 50 milliseconds and attaches script attribution when the browser can provide it. Together they answer a question lab Lighthouse cannot: which bundle owned the main thread when a customer tried to filter suede boots on a train.

## Why Long Animation Frames for ecommerce INP beats guesswork

Long Animation Frames for ecommerce INP matter because catalogue UIs stack the worst patterns for main-thread congestion: AJAX filters, infinite scroll hydration, review stars, personalisation hooks, and sticky promos on the same PLP. [Core Web Vitals thresholds on web.dev](https://web.dev/articles/defining-core-web-vitals-thresholds) treat INP above 500 milliseconds as poor. A single 300 millisecond script block inside a long animation frame can push an interaction over that line even when median INP looks acceptable.

Classic long-task observers told me duration exceeded 50 milliseconds. They rarely said whether the delay sat in JavaScript, style and layout, or paint. LoAF separates those phases. The [Long animation frame timing page on MDN](https://developer.mozilla.org/en-US/docs/Web/API/Performance_API/Long_animation_frame_timing) documents `blockingDuration`, `renderStart`, `styleAndLayoutStart`, and a `scripts` array with `sourceURL` and `invoker` metadata when available. On a WooCommerce block theme I can see that a third-party filter reinjected a megabyte of minified code after consent fired, not that checkout itself was slow.

Store teams often blame hosting when INP fails. Field LoAF data frequently points at one marketing tag or a custom Alpine module on collection templates. That shifts the fix from upgrading PHP workers to deferring or splitting script. For adjacent tuning, see [how scheduler.yield() fixes ecommerce INP](https://alanvo.com/blog/scheduler-yield-ecommerce-inp/) and [Core Web Vitals and INP for online stores](https://alanvo.com/blog/core-web-vitals-online-stores/).

## What changed with LoAF and INP attribution in 2025 and 2026

What changed with LoAF is tighter integration with INP debugging workflows, not a new shopper-facing metric. Chrome documents LoAF as the successor mindset to raw long tasks for responsiveness work because frames map closer to what users perceive as jank or stalled taps. The [Find slow interactions in the field article on web.dev](https://web.dev/articles/find-slow-interactions-in-the-field) explains that the attribution build of the `web-vitals` library exposes `longAnimationFrameEntries` on slow interactions. That is the hook I use on production sites after baseline INP is already in CrUX or RUM.

![Long Animation Frames for ecommerce INP testing on a phone and laptop together](../../images/blog/long-animation-frames-ecommerce-inp-1.jpg)

Browser support is Chromium-first today. The API is designed so unsupported browsers ignore observers safely, which matches how I deploy observability without breaking Safari or Firefox shoppers. I still fix the scripts LoAF names because the same bundles usually hurt Total Blocking Time in lab runs as well. [Vitals measurement getting started on web.dev](https://web.dev/articles/vitals-measurement-getting-started) reminds teams that INP must be measured in the field; LoAF is field-only telemetry layered on top.

Magento Hyva and Shopware frontends that lean on Alpine or heavy Vue hydration saw more LoAF entries after Black Friday traffic doubled concurrent filter use. Shopify Online Store 2.0 themes with app embeds on every section show recurring frames tied to review widgets. None of that appears in a synthetic Lighthouse step because the lab never clicks facet chips three times in a row.

## How Long Animation Frames for ecommerce INP are measured

How Long Animation Frames for ecommerce INP are measured starts with a `PerformanceObserver` on `long-animation-frame`, optionally paired with INP attribution from `web-vitals`. A minimal diagnostic snippet I drop behind a feature flag looks like this:

```javascript
if (PerformanceObserver.supportedEntryTypes.includes('long-animation-frame')) {
  const observer = new PerformanceObserver((list) => {
    for (const entry of list.getEntries()) {
      if (entry.duration < 80) continue;
      const payload = {
        duration: entry.duration,
        blockingDuration: entry.blockingDuration,
        firstUIEventTimestamp: entry.firstUIEventTimestamp,
        scripts: entry.scripts?.map((s) => ({
          sourceURL: s.sourceURL,
          duration: s.duration,
          invoker: s.invoker,
        })),
        path: location.pathname,
      };
      navigator.sendBeacon('/telemetry/loaf', JSON.stringify(payload));
    }
  });
  observer.observe({ type: 'long-animation-frame', buffered: true });
}
```

Each LoAF entry covers work from the start of tasks that may trigger rendering through layout, with timestamps documented on MDN for `renderStart` and `styleAndLayoutStart`. When `renderStart` is zero, the frame was blocking without a paint requirement, which still matters for INP because input may queue behind that work.

The `web-vitals` attribution path ties specific LoAF rows to an interaction that breached your RUM threshold. I configure sampling at 5 to 10 percent on high-traffic PLPs so I do not drown storage. Always redact query strings that carry PII before logging `location`.

![Stopwatch and notebook during a speed pass](../../images/blog/long-animation-frames-ecommerce-inp-2.jpg)

On Shopify I avoid theme.liquid bloat by loading the observer from a deferred app pixel or a single custom asset registered in theme settings. On WordPress I enqueue the observer only on `is_shop()` and `is_product()` to keep admin clean. Magento requires discipline so the snippet does not run inside checkout where PCI scope and CSP already fight marketing tags.

## Production checklist for Long Animation Frames on storefronts

Production checklist for Long Animation Frames on storefronts is about signal quality, privacy, and turning logs into ticket-sized fixes.

1. **Confirm INP is already bad in the field on at least one money URL.** Use CrUX or your RUM vendor. LoAF without a responsiveness problem is noise.

2. **Enable LoAF only after consent where required.** Analytics scripts that run pre-consent should not send LoAF beacons. Align with [defer third-party tags without losing data](https://alanvo.com/blog/defer-third-party-tags/).

3. **Filter short frames in your pipeline.** Chrome marks LoAF at 50 milliseconds. I report frames from about 80 milliseconds upward on mobile catalogue templates to cut volume.

4. **Bucket by template and device class.** Split `product`, `product_list`, and `search` in Magento. Split collection and product in Shopify. WooCommerce product category archives behave differently from block checkout.

5. **Capture script URLs and invoker strings.** Invoker metadata often points at event listener registration sites even when source maps are missing.

6. **Correlate with marketing deploys.** When a new personalisation script ships, LoAF counts on PLPs should be in the release checklist beside INP.

7. **Pair with interaction replay sparingly.** Session replay can confirm a stuck filter UI; LoAF tells you which script to open in Sources.

8. **Set a weekly review owner.** Performance regressions on filters are merchandising incidents, not only engineering tickets.

9. **Document fixes in the theme or tag manager changelog.** Future agencies need to know why a script moved to interaction time.

10. **Re-measure INP p75 four weeks after each change.** LoAF is a scalpel, not a vanity metric.

## What breaks Long Animation Frames for ecommerce INP programmes

What breaks Long Animation Frames for ecommerce INP programmes is usually logging everything, everywhere. The Performance timeline caps buffered `long-animation-frame` entries at about 200 per navigation per MDN. Flooding your endpoint with sub-60 millisecond frames wastes money and hides the outliers that actually hurt INP.

Cross-origin scripts without attribution still produce LoAF rows but empty `scripts` arrays. That is normal for some tag containers. I use timing plus network dependency clues rather than expecting a filename for every frame.

![Compressed product photography on a light table](../../images/blog/long-animation-frames-ecommerce-inp-3.jpg)

Staging sites without real filters, reviews, or loyalty modules will not reproduce production LoAF signatures. Always validate on a canary theme or percentage rollout.

Checkout is a special case. INP on payment fields is sensitive. I do not send LoAF beacons from checkout routes that include cardholder data in the DOM. Measure browse and cart templates instead, and use [reduce JavaScript on checkout pages](https://alanvo.com/blog/reduce-javascript-checkout/) patterns where the slow frame is clearly checkout-specific.

Safari shoppers still benefit when you remove a 200 millisecond Hyva component even if they never emitted a LoAF row. Do not treat Chromium-only telemetry as an excuse to ignore other browsers.

## How to measure progress after LoAF fixes

How to measure progress after LoAF fixes combines INP p75 by URL, LoAF counts per session, and business sanity checks on filter use. Primary success metric remains INP at the 75th percentile for mobile on template types you changed. Secondary metrics include median `blockingDuration` per LoAF on those templates and the share of interactions with any LoAF over 100 milliseconds.

In Google Search Console Core Web Vitals, watch product and category URLs that ads and organic lean on. Compare week over week, not day over day, because ecommerce traffic mix swings with promotions.

In DevTools Performance, record a local filter interaction after deploying a fix. You should see fewer long frames and shorter style and layout slices. Lab Total Blocking Time should fall even though it is not a full INP substitute.

For image and LCP work that runs in the same frames as hydration, cross-check [content-visibility for ecommerce product grids](https://alanvo.com/blog/content-visibility-ecommerce-catalogues/) so layout thrash is not misread as pure JavaScript guilt.

Share a simple dashboard with merchandising: top five script URLs by total blocking milliseconds on PLPs. When they see a slider vendor owning 40 percent of frame time, prioritisation gets easier than arguing about abstract INP points.

## Related work on this site

Filter-heavy rebuilds like [Their Nibs](https://alanvo.com/work/their-nibs/), where published outcomes were 31 percent more conversions and 48 percent more orders, are where I would wire LoAF sampling on collection templates before adding another personalisation layer. [Skanvi](https://alanvo.com/work/skanvi/) is WooCommerce furniture with large PLPs and block editor components that can stack layout work inside the same frames as scripts. [Tamannaah Fine Jewellery](https://alanvo.com/work/tamannaah-fine-jewellery/) carries visual merchandising sliders that are classic LoAF candidates when autoplay and zoom share a thread with facet AJAX. None of these case studies imply you should skip field validation on your own theme.

![Checkout on a phone with a simple form](../../images/blog/long-animation-frames-ecommerce-inp-4.jpg)

## FAQ

### What are Long Animation Frames for ecommerce INP in practice?

Long Animation Frames for ecommerce INP in practice are browser-reported frames where rendering or blocking work took longer than 50 milliseconds on a shop page. They include script attribution when available. I use them to see which JavaScript or layout pass delayed the next paint after a tap on filters, size selectors, or cart icons.

### Do I need LoAF if I already run Lighthouse on product pages?

You need LoAF because Lighthouse does not score real INP on product pages where shoppers click facets and quick views. Lighthouse gives useful lab proxies like Total Blocking Time, but [INP on web.dev](https://web.dev/articles/inp) must be measured with real interactions. LoAF field data names offenders Lighthouse never triggers.

### Where should Long Animation Frames for ecommerce INP fire on my site?

Long Animation Frames for ecommerce INP should fire on high-traffic browse templates: category PLPs, search results, and product detail when upsell widgets hydrate. Avoid checkout and account pages unless legal and security teams sign off on telemetry. Sample a fraction of sessions so observability cost stays predictable.

### Can fixing LoAF issues hurt analytics or personalisation data?

Fixing LoAF issues can move scripts after first interaction or behind consent without deleting tags. Defer heavy work with patterns from [scheduler.yield()](https://alanvo.com/blog/scheduler-yield-ecommerce-inp/) and tag loading rules from [defer third-party tags without losing data](https://alanvo.com/blog/defer-third-party-tags/). Purchase and consent events should still fire; only the timing on browse templates changes.


![CDN and hosting notes next to a keyboard](../../images/blog/long-animation-frames-ecommerce-inp-5.jpg)


HTML version: https://alanvo.com/blog/long-animation-frames-ecommerce-inp/
