为速度优化内容优先级
使用 `async`、`defer` 和资源提示等技术,为关键内容设置优先级并改善感知性能。
为速度优化内容优先级 是 CoddyKit 上的免费 Web Performance Optimization & Lighthouse 课时。 这是第 3 节课,共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Web Performance Optimization & Lighthouse 学习路径的一部分,你的进度在网页和 CoddyKit 应用中同步。 Web Performance Optimization & Lighthouse 课程共包含 4 节课。
本课时的部分内容尚未翻译,以英文显示。
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
asyncfor independent scripts (e.g., third-party ads, tracking) where execution order doesn't matter. - Use
deferfor 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?
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!
常见问题解答
「为速度优化内容优先级」课时是免费的吗?
是的 — 「为速度优化内容优先级」的完整文本可在网页上免费阅读。要进行交互式练习(内置代码编辑器和全天候 AI 导师)并解锁 Web Performance Optimization & Lighthouse 课程的其余内容,请升级到 CoddyKit PRO。 Web Performance Optimization & Lighthouse 课程共包含 4 节课。
「为速度优化内容优先级」这节课中我会学到什么?
使用 `async`、`defer` 和资源提示等技术,为关键内容设置优先级并改善感知性能。 你通过在浏览器中直接运行的动手代码来练习 Web Performance Optimization & Lighthouse,全天候 AI 导师会在你学习这节课的过程中回答你的问题。
学习 Web Performance Optimization & Lighthouse 需要有经验吗?
无需任何先前经验。CoddyKit 上的 Web Performance Optimization & Lighthouse 课程适合初学者到高级学习者,你可以从这里开始或从头开始,按照自己的节奏学习。 这是第 3 节课,共 4 节。
「为速度优化内容优先级」课时需要多长时间?
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动,所以你能稳步进步,并在网页和应用中从离开的地方继续。
我能在这节 Web Performance Optimization & Lighthouse 课中编写并运行代码吗?
能。每节 Web Performance Optimization & Lighthouse 课都包含内置代码编辑器,你可以在浏览器中直接编写并运行真实代码,并获得即时 AI 反馈 — 无需本地设置。