Skip to content

Commit c86baf3

Browse files
committed
Add INP clarification to doc.write post
1 parent 7099dbb commit c86baf3

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

_posts/2023-01-10-why-not-document-write.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,12 @@ that `document.write()` guarantees that these negative behaviours will manifest
3636
themselves, whereas other synchronous scripts can make use of alternate
3737
optimisations to sidestep them.
3838

39+
<ins datetime="2025-06-01"><strong>N.B.</strong> Happily, nothing about
40+
<code>document.write()</code> specifically will impact Interaction to Next
41+
Paint. Only if the JavaScript itself is particularly problematic or expensive
42+
will you suffer poor INP scores. If you are struggling with INP, let’s organise
43+
a <a href="/workshops/">workshop</a>!</ins>
44+
3945
<small>**N.B.** This audit and, accordingly, this article, only deals with
4046
script injection using `document.write()`—not its usage in general. [The MDN
4147
entry for

0 commit comments

Comments
 (0)