# CSS-only carousel solutions improve performance - Scope: Block carousel implementation without JavaScript ## Source - [WordPress 6.9 Dev Notes, WordCamp Canada Talks, Interactivity API - Weekend Edition #349 - Gutenberg Times](<../Readwise/Articles/WordPress 6.9 Dev Notes, WordCamp Canada Talks, Interactivity API - Weekend Edition %23349 - Gutenberg Times.md>) ## Links - [[3. Resources/Permanent Notes/Zet · Server-side development reduces JavaScript complexity]] — because extends: the same trade in a different layer. A CSS-only carousel and server-rendered output both buy performance by removing client JavaScript rather than by optimizing it. - [[3. Resources/Permanent Notes/Zet · Technical constraints shape feature implementation paths]] — because applies-in: what the platform makes cheap in CSS determines whether a block ships without JavaScript at all. - [[3. Resources/Permanent Notes/Platform-Level Defaults Beat Site-Level Optimization for the Same Audiences]] — because extends: a carousel that is performant by default in core beats every site fixing its own, which is the stronger version of this note's claim. - [[3. Resources/Permanent Notes/Accessibility Enforced at Authoring Time Beats Post-Hoc Auditing]] — because contrasts: carousels are a persistent accessibility problem, and removing JavaScript does nothing for keyboard operability or motion control. Performance and accessibility are separate axes here. - [[WordPress Hosting Security Stack MOC]] — because applies-in: performance and delivery defaults sit alongside the security stack as platform-level properties a site owner does not choose individually. ## Needs human eyes Thin — a scope line and a source, no evidence block and no atomicity marker. Migrated `draft` → `seedling` and connected rather than expanded, because the underlying source (Gutenberg Times Weekend Edition #349) would need re-reading to write a real claim. Candidate for either expansion or deletion.