Web Performance Optimization & Lighthouse · レッスン

ブラウザーとサーバーのキャッシュ

HTTPヘッダー、サービスワーカー、サーバー側のキャッシュ機構を使って、効果的なキャッシュ戦略を実装します。

レッスン 2/412 ステップ

「ブラウザーとサーバーのキャッシュ」はCoddyKit上の無料Web Performance Optimization & Lighthouseレッスンです。これはレッスン2/4です。下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応のAIチューターでハンズオン演習できます。これはWeb Performance Optimization & Lighthouse学習パスの一部であり、ウェブとCoddyKitアプリ全体で進捗が同期されます。 Web Performance Optimization & Lighthouseコースには全4レッスンが含まれています。

このレッスンの一部はまだ翻訳されておらず、英語で表示されています。

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, and Last-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.

無料で開始

AI チューターと学ぶ Web Performance Optimization & Lighthouse — 無料

ブラウザでリアルコードを書いて実行し、24/7 の AI チューターから瞬時にサポートを受け、ウェブまたはアプリで続きから学習できます。

コース: 12
レッスン: 48

無料で学習を始めるコース全体を表示

よくある質問

「ブラウザーとサーバーのキャッシュ」レッスンは無料ですか？

はい。「ブラウザーとサーバーのキャッシュ」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し（組み込みコードエディタと24時間対応のAIチューター）、Web Performance Optimization & Lighthouseコースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 Web Performance Optimization & Lighthouseコースには全4レッスンが含まれています。

「ブラウザーとサーバーのキャッシュ」で何を学びますか？

HTTPヘッダー、サービスワーカー、サーバー側のキャッシュ機構を使って、効果的なキャッシュ戦略を実装します。ブラウザで直接実行するハンズオンコードでWeb Performance Optimization & Lighthouseを演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。

Web Performance Optimization & Lighthouseを始めるのに経験は必要ですか？

事前経験は必要ありません。CoddyKitのWeb Performance Optimization & Lighthouseは初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。これはレッスン2/4です。

「ブラウザーとサーバーのキャッシュ」レッスンにはどのくらい時間がかかりますか？

ほとんどのCoddyKitレッスンは約5～10分かかります。各レッスンはコンパクトでインタラクティブなので、着実に進歩し、ウェブとアプリ全体で正確に前回の場所から再開できます。

このWeb Performance Optimization & Lighthouseレッスンでコードを書いて実行できますか？

はい。すべてのWeb Performance Optimization & Lighthouseレッスンに組み込みコードエディタが含まれているため、ブラウザでリアルコードを書いて実行し、即座のAIフィードバックを取得できます。ローカル設定は不要です。

このコースのすべてのレッスン

← Web Performance Optimization & Lighthouseに戻る