Almacenamiento en caché del navegador y del servidor
Implemente estrategias eficaces de almacenamiento en caché mediante encabezados HTTP, service workers y mecanismos de caché del lado del servidor.
Almacenamiento en caché del navegador y del servidor es una lección gratuita de Web Performance Optimization & Lighthouse en CoddyKit. Esta es la lección 2 de 4. Puedes leer la lección completa abajo gratuitamente — luego la practicas en el navegador con un editor de código integrado y un tutor de IA 24/7. Forma parte de la ruta de aprendizaje de Web Performance Optimization & Lighthouse, y tu progreso se sincroniza en la web y la app de CoddyKit. El curso de Web Performance Optimization & Lighthouse incluye 4 lecciones en total.
Partes de esta lección aún no han sido traducidas y se muestran en inglés.
Caching: Speeding Up the Web
Imagine visiting a website. Every time, your browser has to download all the images, stylesheets, and scripts from scratch. That would be slow!
Caching solves this by storing copies of these resources closer to you, either in your browser or on an intermediate server. This means less data transfer and faster load times on subsequent visits.
Why Caching Matters
Efficient caching is crucial for web performance. It offers several key benefits:
- Faster Page Loads: Users get content quicker, improving their experience.
- Reduced Server Load: Your server doesn't have to send the same data repeatedly.
- Lower Bandwidth Costs: Less data transferred means lower costs for both users and providers.
- Offline Capabilities: Advanced caching can even allow users to browse content offline.
Two Types of Caching
Caching can happen in different places. We'll focus on two main types:
- Browser Caching (Client-Side): Resources are stored directly on the user's device. This is the fastest form of caching for returning visitors.
- Server-Side Caching: Resources are stored on the web server or a proxy server before they reach the user. This reduces the work the server has to do.
Browser Caching with HTTP Headers
How does a browser know what to cache and for how long? It relies on HTTP response headers sent by the web server. These headers act like instructions for the browser.
Key headers include Cache-Control, Expires, ETag, and Last-Modified. They dictate how long a resource is considered fresh and when it needs to be re-checked.
The Cache-Control Header
The Cache-Control header is the most powerful and flexible caching mechanism. It tells browsers and intermediate caches how to handle a resource.
Common directives include:
max-age=SECONDS: Cache for this many seconds.no-cache: Browser must revalidate with server before using cached copy.no-store: Never cache this resource.public/private: Can be cached by any cache or only by the user's browser, respectively.
Cache-Control Example
Here's an example of HTTP response headers for an image that can be cached publicly for one year (31,536,000 seconds). This tells the browser it's safe to use the local copy without checking the server for a long time.
HTTP/1.1 200 OK
Content-Type: image/jpeg
Cache-Control: public, max-age=31536000
Expires: Tue, 25 Nov 2025 10:00:00 GMT
ETag: "image-v123"Revalidation with ETag & Last-Modified
Even when a resource is cached, it might need to be revalidated. The ETag (entity tag) and Last-Modified headers help with this.
Last-Modified: The date and time the resource was last changed.ETag: A unique identifier (like a hash) for a specific version of a resource.
The browser sends these back to the server. If the resource hasn't changed, the server responds with a 304 Not Modified, saving bandwidth.
Service Workers: Advanced Caching
Beyond HTTP headers, Service Workers offer powerful, programmatic control over caching. A Service Worker is a JavaScript file that acts as a proxy between your browser and the network.
They can intercept network requests, cache responses using the Cache API, and serve content even when offline. This enables truly robust offline experiences and custom caching strategies.
Registering a Service Worker
To use a Service Worker, you first need to register it in your main JavaScript file. This code checks for Service Worker support and registers your sw.js file.
Once registered, the Service Worker can then define its own caching logic, like caching specific assets or entire pages.
// This code would be in your main.js file
if ('serviceWorker' in navigator) {
window.addEventListener('load', () => {
navigator.serviceWorker.register('/sw.js')
.then(registration => {
console.log('SW registered with scope:', registration.scope);
})
.catch(error => {
console.log('SW registration failed:', error);
});
});
}Server-Side Caching Overview
Caching isn't just for browsers. Servers also use caching to reduce the load on databases and speed up response times. This can involve storing:
- Database Query Results: Avoid re-running complex queries.
- Rendered HTML Fragments: Serve parts of a page that don't change often.
- API Responses: Cache data fetched from other services.
Server-side caching is managed by your web server or application framework, often using tools like Redis or Memcached.
Caching Strategy Check
You've learned about various caching mechanisms. Let's test your understanding of HTTP caching headers.
Recap: Caching for Performance
We've covered how caching significantly boosts web performance. You learned about:
- Browser Caching: Using HTTP headers like
Cache-Control,ETag, andLast-Modified. - Service Workers: Providing powerful, programmatic control over client-side caching, enabling offline capabilities.
- Server-Side Caching: Reducing server load and speeding up dynamic content delivery.
Implementing effective caching strategies is a fundamental step towards building fast and resilient web applications.
Aprende Web Performance Optimization & Lighthouse con un tutor de IA — gratis
Escribe y ejecuta código real en tu navegador, obtén ayuda instantánea de un tutor de IA disponible 24/7 y continúa donde lo dejaste en la web o en la aplicación.
- Cursos
- 12
- Lecciones
- 48
Preguntas frecuentes
¿La lección «Almacenamiento en caché del navegador y del servidor» es gratis?
Sí — el texto completo de «Almacenamiento en caché del navegador y del servidor» es gratis para leer aquí en la web. Para practicarla de forma interactiva (editor de código integrado y tutor de IA 24/7) y desbloquear el resto del curso de Web Performance Optimization & Lighthouse, actualiza a CoddyKit PRO. El curso de Web Performance Optimization & Lighthouse incluye 4 lecciones en total.
¿Qué aprenderé en «Almacenamiento en caché del navegador y del servidor»?
Implemente estrategias eficaces de almacenamiento en caché mediante encabezados HTTP, service workers y mecanismos de caché del lado del servidor. Practicas Web Performance Optimization & Lighthouse con código real que ejecutas directamente en el navegador, y un tutor de IA 24/7 responde tus preguntas mientras trabajas en la lección.
¿Necesito experiencia previa para empezar Web Performance Optimization & Lighthouse?
No se requiere experiencia previa. Web Performance Optimization & Lighthouse en CoddyKit está estructurado para principiantes hasta estudiantes avanzados, así que puedes empezar aquí o desde el inicio y avanzar a tu ritmo. Esta es la lección 2 de 4.
¿Cuánto tiempo toma la lección «Almacenamiento en caché del navegador y del servidor»?
La mayoría de las lecciones de CoddyKit toman alrededor de 5–10 minutos. Cada una es compacta e interactiva, así que avanzas constantemente y retomas exactamente por donde dejaste en la web y la app.
¿Puedo escribir y ejecutar código en esta lección de Web Performance Optimization & Lighthouse?
Sí. Cada lección de Web Performance Optimization & Lighthouse incluye un editor de código integrado, así que escribes y ejecutas código real directamente en tu navegador y obtienes retroalimentación instantánea de IA — sin configuración local necesaria.
Todas las lecciones de este curso
- Fundamentos de HTTP/2 y HTTP/3
- Almacenamiento en caché del navegador y del servidor
- Redes de distribución de contenido (CDN)
- Compresión y codificación de transferencia