CSS rendering hints on React sites
will-change (71.3%), aspect-ratio (53.5%), scroll-driven animations (77.2%), CSS containment (27.6%), and content-visibility (21.8%) across 9,068 sites.
77.2% of React sites use scroll-driven animation CSS rendering hints, and 99% of those sites have a good INP, against 99% of all React sites.
INP pass rate
Sites with scroll-driven animation CSS rendering hints have a good INP most often: 99%, against 99% of all React sites. Sites with CSS containment CSS hints have it least often, at 99%.
CSS rendering hints usage
Scroll-driven animation is the most used: 77.2% of React sites.
CSS rendering hints per platform
Wix sets the CSS rendering hints to scroll-driven animation on 100% of its sites, and 100% of Wix sites have a good INP, against 99% of all sites. WordPress sets the CSS rendering hints to will-change on 85% of its sites, and 100% of WordPress sites have a good INP.
CSS rendering hints or the platform
Does the platform explain the CSS rendering hints difference?
On Wix, 100% of sites with scroll-driven animation CSS rendering hints have a good INP, against 100% of Wix sites with will-change. Within Wix, sites with scroll-driven animation and will-change have a good INP about equally often. On WordPress, 100% of sites with scroll-driven animation CSS rendering hints have a good INP, against 99% of WordPress sites with will-change. Within WordPress, sites with scroll-driven animation and will-change have a good INP about equally often.
How CSS rendering hints isolate layout and compositor work
CSS hints instruct the rendering engine how to allocate compositor layers and skip offscreen layout work. Among hint-using sites, 71.3% use will-change (99% good INP), 53.5% use aspect-ratio (99% good INP), 77.2% use scroll-driven animations (99% good INP), 27.6% use contain (99% good INP), and 21.8% use content-visibility (99% good INP).
Understanding CSS rendering hints
Use aspect-ratio to reserve responsive media boxes, scroll-driven animations to move scroll effects off the main thread, and content-visibility: auto with contain-intrinsic-size on long below-the-fold sections. Avoid applying will-change across large numbers of elements, which exhausts GPU memory.
By Arjen Karel · 9,570 crawled React sites (1,979 with desktop Chrome field data, 9,068 sites with CSS rendering hints, October 2026). How we measured.