Content groups tab
Override TurboCache settings for chosen URLs, the front page or post types, such as no delayed scripts on landing pages or no cache for a section.
TurboCache → Settings → Content groups lets one part of the site behave differently from the rest. Select Add group to create one.
How a group matches
- Enabled and a Group name (required).
- URIs / patterns — one per line; same pattern rules as exclusions. Use
@frontfor the front page. - Post types — any public post type.
- View — All, Desktop or Mobile.
The first enabled group whose URL, front-page flag or post type matches wins. A group with neither URIs nor post types matches nothing.
What a group can override
Each field defaults to Inherit (the global setting). On/off fields can be forced on or off; list fields are added to the global list.
- Functionality, Page cache, Lazy invalidation.
- CSS: optimize loading, critical mode, manual critical CSS, always critical (added), skip (added), combine.
- JS: defer, delay until interaction, delay timeout, critical (added), always delay (added), skip (added).
- Images: lazy load, keep first eager, WebP, lazy backgrounds.
- Video facades, HTML minify, HTML early paint.
Examples
- A “Landing pages” group for
/lp/*with manual critical CSS and JS: delay until interaction off, so a booking widget is ready immediately. - A “Shop” group for the Product post type with Lazy invalidation off, so price changes show at once.
- A group with Page cache off for a section that must never be cached. Matching pages report
BYPASS; reason=group-no-cache.
Did this answer the question? No — open a support request