Cross-link perf.mark-type articles

Author: csswizardry

_posts/2022-08-24-measure-what-you-impact-not-what-you-influence.md

@@ -2,6 +2,7 @@
 layout: post
 title: "Measure What You Impact, Not What You Influence"
 date: 2022-08-24 12:41:16
+last_modified_at: 2025-08-22
 categories: Web Development
 main: "https://res.cloudinary.com/csswizardry/image/fetch/f_auto,q_auto/https://csswizardry.com/wp-content/uploads/2022/08/user-timing-chrome.png"
 meta: "When implementing performance fixes, it’s imperative that you measure the right thing—but what is ‘right’?"
@@ -13,6 +14,12 @@ lead to incorrect conclusions about the effectiveness of that work. This can go
 either way: under- or overestimating the efficacy of those changes. Naturally,
 neither is great.
 
+<p class="c-highlight">You can now make your measurements even more meaningful
+by using the <a href="/2025/07/the-extensibility-api/"><i>Performance
+Extensibility API</i></a>: add rich metadata to your <i>User Timing</i>
+<code>performance.mark()</code>s and <code>performance.measure()</code>s, and
+filter and group them in DevTools’ <i>Performance</i> panel.</p>
+
 ## Problems When Measuring Performance
 
 As I see it, there are two main issues when it comes to measuring performance

_posts/2025-07-25-the-extensibility-api.md

@@ -2,6 +2,7 @@
 layout: post
 title: "Making Sense of the Performance Extensibility API"
 date: 2025-07-25 15:15:11
+last_modified_at: 2025-08-22
 categories: Web Development
 main: "/wp-content/uploads/2025/07/extensibility-10.png"
 meta: "Making sense—and use!—of the new Performance Extensibility API in Chrome DevTools."
@@ -14,6 +15,12 @@ documentation is somewhat dry and doesn’t really state the benefits or outcome
 very clearly, so I spent a couple of hours looking into it and here are the key
 takeaways.
 
+<p class="c-highlight">Not sure how to use the Performance Extensibility API?
+Read up on the <a
+href="/2022/08/measure-what-you-impact-not-what-you-influence/"><i>User Timing
+API</i>’s <code>performance.mark()</code> and
+<code>performance.measure()</code></a> first.</p>
+
 If you:
 
 * are interested in closely profiling specific, atomic parts of your