You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: apply webperf-docs-reviewer rules to Find-render-blocking-resources
- Remove ### Overview section, intro paragraph goes directly under title
- Replace 9 bold-as-headers with ### headings in sentence case
- Fix 4 headings from title case to sentence case
- Refactor JS snippet: calculate lastBlockingEnd, totalSizeBytes, byType
once before if/else to eliminate duplicate computation
Copy file name to clipboardExpand all lines: pages/Loading/Find-render-blocking-resources.mdx
+14-16Lines changed: 14 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,30 +3,28 @@ import { Snippet } from '../../components/Snippet'
3
3
4
4
# Find render-blocking resources
5
5
6
-
### Overview
7
-
8
6
Identifies resources that block the browser from rendering the page. These resources must be fully downloaded and processed before the browser can display any content, directly impacting First Contentful Paint (FCP) and Largest Contentful Paint (LCP).
9
7
10
-
**Why this matters:**
8
+
### Why this matters
11
9
12
10
Render-blocking resources are the primary cause of slow initial page renders. Users see a blank white screen while CSS and JavaScript files download and parse. On slow connections or mobile networks, this can add several seconds to your load time. Eliminating or deferring render-blocking resources is one of the highest-impact optimizations you can make.
13
11
14
-
**What are render-blocking resources?**
12
+
### What are render-blocking resources?
15
13
16
14
| Resource Type | When it blocks rendering |
17
15
|---------------|-------------------------|
18
16
|**CSS**| All `<link rel="stylesheet">` in `<head>` block rendering by default |
19
17
|**JavaScript**| Scripts without `async` or `defer` in `<head>` block parsing and rendering |
20
18
|**Fonts**|`@font-face` fonts block text rendering until loaded |
21
19
22
-
**Impact on performance:**
20
+
### Impact on performance
23
21
24
22
- Delays First Contentful Paint (FCP)
25
23
- Can delay Largest Contentful Paint (LCP)
26
24
- Users see a blank page while resources load
27
25
- Particularly harmful on slow connections
28
26
29
-
**Render-Blocking Timeline:**
27
+
### Render-blocking timeline
30
28
31
29
```mermaid
32
30
sequenceDiagram
@@ -59,15 +57,15 @@ sequenceDiagram
59
57
Note over Browser,Render: User sees content
60
58
```
61
59
62
-
> **Browser Support:** The `renderBlockingStatus` property is currently Chromium-only (Chrome 107+, Edge 107+, Opera 93+). Firefox and Safari don't support this API yet.
60
+
> **Browser support:** The `renderBlockingStatus` property is currently Chromium-only (Chrome 107+, Edge 107+, Opera 93+). Firefox and Safari don't support this API yet.
63
61
64
62
### Snippet
65
63
66
64
<Snippetcode={snippet} />
67
65
68
-
### Understanding the Results
66
+
### Understanding the results
69
67
70
-
**Summary Metrics:**
68
+
### Summary metrics
71
69
72
70
| Metric | Description |
73
71
|--------|-------------|
@@ -76,7 +74,7 @@ sequenceDiagram
76
74
|**Total size**| Combined transfer size of all blocking resources |
77
75
|**By type**| Breakdown by resource type (script, link/css, font) |
78
76
79
-
**Timeline Visualization:**
77
+
### Timeline visualization
80
78
81
79
Shows each resource with:
82
80
- Resource type
@@ -86,7 +84,7 @@ Shows each resource with:
86
84
87
85
Resources are sorted by completion time (latest first), so you can see which resource is the last to complete and thus determines when rendering can start.
0 commit comments