Chrome Cut Android Scroll Jank 48%: What to Check on Your Site

A client scrolls a product page on Android and the page hitches. They blame the phone, the network, or "Chrome is slow." In July 2026 Chromium published how they cut the frequency of janky scrolls in Chrome on Android by about 48% between 2023 and 2026. That pipeline work is real. It still does not remove your scroll handlers, long tasks, or layout that shifts while the finger is moving.

Scroll jank is a missed frame during scroll: the screen shows a stale offset for about 16.7 ms on a 60 Hz display. Chrome owns input-to-frame delivery inside the browser. Your site owns the work that runs while Chrome is trying to produce the next frame. After a Chrome release note, only two buckets belong on the sprint board: main-thread and style work during scroll, and layout that moves mid-gesture.

What we put in the checklist for web teams:

• List every scroll / touchmove / wheel listener on priority templates (homepage, PDP, article, category feed).

• Mark each as passive observe, must preventDefault, or removable; drop handlers that force layout on every event.

• Move scroll-linked visuals to CSS sticky / transform where you can.

• Reserve space for lazy images, embeds, and infinite-scroll rows before they load.

• Audit third-party tags for long tasks during the first scroll after load; re-run mobile lab and watch INP and CLS field bands for the following weeks.

One green Lighthouse paste after a Chrome update is not proof the portfolio is smooth. Spot checks miss the template you did not open.

Read more: Chrome Android scroll jank: what to check on your site