Web Performance Optimization & Lighthouse · Pelajaran

Memprioritaskan Konten demi Kecepatan

Terapkan teknik seperti `async`, `defer`, dan petunjuk sumber daya untuk memprioritaskan konten penting dan meningkatkan kinerja yang dirasakan pengguna.

Pelajaran 3 dari 411 langkah

Memprioritaskan Konten demi Kecepatan adalah pelajaran Web Performance Optimization & Lighthouse gratis di CoddyKit. Ini adalah pelajaran 3 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Web Performance Optimization & Lighthouse, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Web Performance Optimization & Lighthouse mencakup 4 pelajaran total.

Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.

Why Prioritize Content?

When a browser loads a webpage, it follows a sequence of steps to render content. This is often called the Critical Rendering Path (CRP).

Optimizing the CRP means delivering the most important content to the user as quickly as possible. This improves perceived performance – how fast a user *feels* the page is loading.

Blocking Scripts Slow Down

By default, when the browser encounters a <script> tag, it pauses parsing the HTML, fetches the script, executes it, and then resumes parsing. This is called a render-blocking script.

This can significantly delay how quickly users see content, especially if the script is large or on a slow network.

<html>
<head>
  <title>Blocking Script</title>
  <script>
    // This script blocks HTML parsing
    console.log("Blocking script started.");
    // Simulate a long task
    let start = performance.now();
    while (performance.now() - start < 700) { /* busy wait */ }
    console.log("Blocking script finished.");
  </script>
</head>
<body>
  <h1>Page Content</h1>
  <p>This content appears <b>after</b> the script finishes.</p>
</body>
</html>

Introducing `defer`

The defer attribute tells the browser to download the script in the background without blocking HTML parsing. Once the HTML is fully parsed, the deferred scripts execute in the order they appear in the document.

Non-blocking: HTML parsing continues.
Order preserved: Scripts execute in source order.
Execution time: After HTML parsing, before DOMContentLoaded.

`defer` in Action

Using defer is ideal for scripts that depend on the DOM being fully available, like analytics or UI initialization logic.

See how the 'Page Content' appears before the deferred script executes in the console.

<html>
<head>
  <title>Deferred Script Example</title>
  <script defer>
    console.log("Deferred script 1 started.");
  </script>
  <script defer>
    // This script will run after script 1
    console.log("Deferred script 2 started.");
  </script>
</head>
<body>
  <h1>Page Content</h1>
  <p>This content appears immediately while scripts are downloading.</p>
  <script>
    console.log("HTML parsing complete.");
  </script>
</body>
</html>

Introducing `async`

The async attribute also tells the browser to download the script in the background. However, async scripts execute as soon as they are downloaded, potentially before HTML parsing is complete.

Non-blocking: HTML parsing continues.
Order NOT preserved: Scripts execute as soon as they're ready.
Execution time: Asynchronously, as soon as possible.

`async` vs. `defer`

Choosing between async and defer depends on your script's needs:

Use async for independent scripts (e.g., third-party ads, tracking) where execution order doesn't matter.
Use defer for scripts that need the DOM or depend on other deferred scripts, ensuring order is maintained.

<html>
<head>
  <title>Async vs Defer</title>
  <script async>
    console.log("Async script executed!");
  </script>
  <script defer>
    console.log("Defer script executed!");
  </script>
  <script>
    console.log("HTML parsing continues, then inline script runs.");
  </script>
</head>
<body>
  <h1>Async & Defer Demo</h1>
  <p>Check the console to see the execution order.</p>
</body>
</html>

Resource Hint: `preconnect`

Resource hints give the browser clues about resources it will need soon, allowing it to start fetching them earlier.

<link rel="preconnect"> tells the browser to establish a connection to another domain early. This includes DNS lookup, TCP handshake, and TLS negotiation, saving precious milliseconds for critical third-party resources.

Resource Hint: `preload`

<link rel="preload"> tells the browser to fetch a resource that is critically important for the current navigation as soon as possible. This is useful for resources like fonts, critical CSS, or images that are discovered late by the parser.

<html>
<head>
  <title>Preload Example</title>
  <link rel="preload" href="data:text/css;base64,Ym9keSB7IGJhY2tncm91bmQtY29sb3I6IGxpZ2h0Ymx1ZTsgfQ==" as="style">
  <style>
    /* This is a simple inline style */
    body { margin: 20px; }
  </style>
  <style>
    /* The preloaded style will apply */
    @import url("data:text/css;base64,Ym9keSB7IGJhY2tncm91bmQtY29sb3I6IGxpZ2h0Ymx1ZTsgfQ==");
  </style>
</head>
<body>
  <h1>Preloaded Style</h1>
  <p>The CSS for the light blue background is preloaded, ensuring it's available early.</p>
</body>
</html>

Resource Hint: `prefetch`

<link rel="prefetch"> tells the browser to fetch a resource that might be needed for a future navigation. It's a lower priority hint than preload and is great for speeding up subsequent page loads.

For example, if you know a user is likely to click a specific link, you can prefetch the resources for that page.

Prioritization Quiz

Which of the following statements about script loading and resource hints are TRUE?

Jawab di pelajaran interaktif

Recap: Faster Page Loads

We've learned powerful techniques to prioritize content and speed up your web pages:

`defer` for non-blocking script loading, preserving execution order.
`async` for non-blocking, independent script execution.
`preconnect` to warm up connections to other domains.
`preload` to fetch critical resources early for the current page.
`prefetch` to fetch resources for future navigations.

By strategically using these, you can significantly improve your website's perceived performance and user experience!

Gratis untuk memulai

Belajar Web Performance Optimization & Lighthouse dengan tutor AI — gratis

Tulis dan jalankan kode asli di browser kamu, dapatkan bantuan instan dari tutor AI 24/7, dan lanjutkan di mana kamu tinggalkan di web atau aplikasi.

Kursus: 12
Pelajaran: 48

Mulai belajar gratis Lihat kursus lengkapnya

Pertanyaan yang Sering Diajukan

Apakah pelajaran “Memprioritaskan Konten demi Kecepatan” gratis?

Ya — teks lengkap “Memprioritaskan Konten demi Kecepatan” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Web Performance Optimization & Lighthouse, upgrade ke CoddyKit PRO. Kursus Web Performance Optimization & Lighthouse mencakup 4 pelajaran total.

Apa yang akan aku pelajari di “Memprioritaskan Konten demi Kecepatan”?

Terapkan teknik seperti `async`, `defer`, dan petunjuk sumber daya untuk memprioritaskan konten penting dan meningkatkan kinerja yang dirasakan pengguna. Kamu berlatih Web Performance Optimization & Lighthouse dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.

Apakah aku perlu pengalaman untuk memulai Web Performance Optimization & Lighthouse?

Tidak diperlukan pengalaman sebelumnya. Web Performance Optimization & Lighthouse di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 3 dari 4.

Berapa lama pelajaran “Memprioritaskan Konten demi Kecepatan” memakan waktu?

Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.

Bisakah aku menulis dan menjalankan kode dalam pelajaran Web Performance Optimization & Lighthouse ini?

Ya. Setiap pelajaran Web Performance Optimization & Lighthouse menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.

Semua pelajaran dalam kursus ini

← Kembali ke Web Performance Optimization & Lighthouse