Path: SpeedyGo → Settings → Caching & Preloading
4.1 Overview #
Browser caching instructs the visitor’s browser to store static resources locally for a defined period. Instead of downloading the same files again on every visit, the browser loads them directly from local storage.
SpeedyGo automatically adds Expires and Cache-Control headers via .htaccess (or server configuration).
This applies to:
- CSS files
- JavaScript files
- Images
- Fonts
Benefits:
- Faster repeat visits
- Reduced server requests
- Lower bandwidth consumption
How It Works Internally #
- Adds
Expiresheaders to define resource lifetime - Sets
Cache-Control: public, max-age=values - Applies rules to common static file extensions (CSS, JS, JPG, PNG, WebP, SVG, WOFF, etc.)
- Improves performance for returning visitors
4.2 Settings #
Enable Browser Caching #
- Toggle Browser Caching → ON
Cache Duration #
- Set Cache Duration (in hours)
Example:
720hours = 30 days
This defines how long static assets remain stored in the visitor’s browser before revalidation.
4.3 Best Practice Recommendation #
- Use longer durations (30–90 days) for stable assets
- Clear cache after major design or CSS/JS changes
- Combine with Full-Page Caching for maximum performance gains
Browser Caching significantly improves performance for returning users and reduces overall server load.