WordPress CSS rendering hints and the Core Web Vitals
will-change (84.8%), aspect-ratio (67.4%), scroll-driven animations (34.7%), CSS containment (35.7%), and content-visibility (37.2%) across 51,385 sites.
84.8% of WordPress sites use will-change CSS rendering hints, and 100% of those sites have a good INP, against 100% of all WordPress sites.
INP pass rate
Sites with will-change CSS rendering hints have a good INP most often: 100%, against 100% of all WordPress sites. Sites with CSS containment CSS hints have it least often, at 99%.
CSS rendering hints usage
Will-change is the most used: 84.8% of WordPress sites.
CSS rendering hints per framework
Vue sets the CSS rendering hints to will-change on 97% of its sites, and 99% of Vue sites have a good INP, against 100% of all sites. Alpine sets the CSS rendering hints to aspect-ratio on 86% of its sites, and 99% of Alpine sites have a good INP.
CSS rendering hints or the framework
Does the framework explain the CSS rendering hints difference?
On jQuery, 100% of sites with will-change CSS rendering hints have a good INP, against 100% of jQuery sites with aspect-ratio. Within jQuery, sites with will-change and aspect-ratio have a good INP about equally often. On Vue, 100% of sites with will-change CSS rendering hints have a good INP, against 99% of Vue sites with aspect-ratio. Within Vue, sites with will-change and aspect-ratio 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, 84.8% use will-change (100% good INP), 67.4% use aspect-ratio (100% good INP), 34.7% use scroll-driven animations (100% good INP), 35.7% use contain (99% good INP), and 37.2% use content-visibility (100% 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 · 63,295 crawled WordPress sites (17,005 with desktop Chrome field data, 51,385 sites with CSS rendering hints, October 2026). How we measured.