How long should I cache static assets in the browser?

For truly static assets like fonts, logos, and versioned CSS/JS files, a cache duration of one year (max-age=31536000) is recommended. For assets that change occasionally, shorter durations of one week to one month work well, combined with cache-busting techniques like file versioning or query strings.

Browser Cache vs Server Cache: Effective Caching Strategies for Speed

Q: What is the difference between browser cache and server cache?

Browser cache stores assets (images, CSS, JS) locally on the user's device to speed up repeat visits. Server cache stores pre-generated pages or data on the server side (using tools like Redis, Varnish, or built-in CMS caching) so the server doesn't have to rebuild content for every request. Both reduce load times but operate at different layers of the delivery chain.

Why Caching Is the Fastest Win for Web Performance

If your website takes more than 3 seconds to load, you’re losing nearly 53% of mobile visitors (Google data). The good news? Caching is one of the simplest and most impactful ways to fix that.

Caching works by storing copies of your content so it doesn’t need to be rebuilt or re-downloaded every time someone visits. But not all caches are equal. Understanding the difference between browser cache and server cache — and using both strategically — is the key to a truly fast website.

Browser Cache: Speed on the Client Side

How It Works

When a user visits your site, their browser downloads assets like images, stylesheets, JavaScript files, and fonts. Browser caching tells the browser to store these files locally so that on subsequent visits, it doesn’t need to download them again.

This is controlled through HTTP headers, primarily:

Cache-Control — defines how long a resource should be cached (e.g., max-age=86400 for 24 hours)
ETag — a fingerprint that lets the browser check if a file has changed
Expires — an older directive specifying an absolute expiration date

Real-World Impact

A well-configured browser cache can reduce repeat page load times by 60-80%. For an e-commerce site with 50 product images per page, that means going from 4.5 seconds down to under 1 second on return visits.

Best Practices

Set max-age=31536000 (1 year) for versioned static assets
Use no-cache for HTML documents so users always get fresh content
Implement file versioning (e.g., style.v3.css) to bust cache when updates are needed

Server Cache: Speed at the Source

How It Works

Server-side caching stores pre-built responses so the server doesn’t have to process the same request repeatedly. Instead of querying the database, executing PHP, and rendering HTML for every visitor, the server delivers a ready-made copy.

Common server caching layers include:

Opcode cache (OPcache) — caches compiled PHP bytecode
Object cache (Redis, Memcached) — stores database query results in memory
Full-page cache (Varnish, Nginx FastCGI) — serves entire HTML pages without touching the application
CDN edge cache (CloudFront, Cloudflare) — distributes cached content across global servers

Real-World Impact

A WordPress site without server caching might handle 50-100 requests per second. Add Redis object caching and Varnish full-page caching, and that same server can handle 2,000-5,000 requests per second — a 40x improvement.

For Prestashop stores, enabling built-in caching combined with a reverse proxy can cut Time to First Byte (TTFB) from 800ms to under 100ms.

Best Practices

Enable OPcache on every PHP-based site — it’s free performance
Use Redis for dynamic sites with heavy database queries
Implement Varnish or a CDN for high-traffic pages
Always set proper cache invalidation rules to avoid serving stale content

The Layered Approach: Combining Both for Maximum Speed

The most effective strategy isn’t choosing one over the other — it’s stacking them intentionally:

Layer	What It Caches	Benefit
CDN / Edge Cache	Static + full pages	Reduces latency globally
Reverse Proxy (Varnish)	Full HTML pages	Offloads application server
Object Cache (Redis)	Database queries	Speeds up dynamic content
OPcache	PHP bytecode	Eliminates recompilation
Browser Cache	CSS, JS, images, fonts	Eliminates re-downloads

At Lueur Externe, our team — certified AWS Solutions Architects and Prestashop experts since 2003 — implements this exact layered caching approach for clients. We’ve seen sites go from a 6-second load time to under 1.2 seconds simply by configuring the right caching stack.

Common Caching Mistakes to Avoid

Caching logged-in user pages — this can expose private data to other users
No cache invalidation plan — updates won’t appear until the cache expires
Over-caching dynamic content — shopping carts and checkout pages should never be cached
Ignoring mobile — ensure your CDN and cache respect Vary headers for device-specific content

Conclusion: Don’t Leave Performance on the Table

Caching isn’t optional in 2025 — it’s foundational. A proper caching strategy reduces hosting costs, improves Core Web Vitals, boosts SEO rankings, and most importantly, keeps your visitors happy.

Whether you run a WordPress blog or a high-traffic Prestashop store, the right combination of browser and server caching can transform your site’s speed. If you’re unsure where to start or want a professional audit, Lueur Externe can help you design and implement a caching strategy tailored to your infrastructure.

Get in touch with our performance experts →