Use HTTP/2 server push selectively

HTTP/2 server push can place a critical resource on the connection before the browser requests it, but an unnecessary push consumes bandwidth and may duplicate an object already held in cache.

Select stable critical assets

Begin with a small stylesheet or script required by the initial response and verify that it would otherwise be discovered late. Avoid pushing page-specific media and large libraries speculatively.

Observe cache interaction

Test repeat visits and intermediaries. The server does not automatically know the complete browser cache state, and implementations differ in how pushed responses are accepted, cancelled or stored.

Compare against simpler hints

Measure push beside preload headers, early discovery and ordinary caching. Retain it only where the waterfall and user timing show a consistent improvement under realistic connection conditions.