@@ -197,7 +197,7 @@ absurd! INP is measured in **hundreds of milliseconds**, LCP is measured in
197197inordinate weighting to INP.
198198
199199<figure >
200- <img src =" /wp-content/uploads/2024/11/new-metric-01.png " alt =" " width =" 1500 " height =" 194 " loading =" lazy " >
200+ <img src =" {{ site.cloudinary }} /wp-content/uploads/2024/11/new-metric-01.png" alt =" " width =" 1500 " height =" 194 " loading =" lazy " >
201201<figcaption >A naive summing approach awards the lowest score to our highest
202202performer and the highest score to our middlemost. This is completely
203203useless.</figcaption >
@@ -214,7 +214,7 @@ why don’t we try normalising them?
214214Let’s convert our INP into seconds:
215215
216216<figure >
217- <img src =" /wp-content/uploads/2024/11/new-metric-02.png " alt =" " width =" 1500 " height =" 194 " loading =" lazy " >
217+ <img src =" {{ site.cloudinary }} /wp-content/uploads/2024/11/new-metric-02.png" alt =" " width =" 1500 " height =" 194 " loading =" lazy " >
218218<figcaption >This is marginally better—we’re now attributing the best to the
219219best, but we’re now awarding the worst to the middle.</figcaption >
220220</figure >
@@ -255,7 +255,7 @@ Once we’ve done this, we end up with a new normalised column that places each
255255the metrics proportionately (not equally) on a 0–1 scale:
256256
257257<figure >
258- <img src =" /wp-content/uploads/2024/11/new-metric-rescaled.png " alt =" " width =" 1500 " height =" 210 " loading =" lazy " >
258+ <img src =" {{ site.cloudinary }} /wp-content/uploads/2024/11/new-metric-rescaled.png" alt =" " width =" 1500 " height =" 210 " loading =" lazy " >
259259<figcaption >Now we can compare disparate metrics like-for-like.</figcaption >
260260</figure >
261261
@@ -284,7 +284,7 @@ Once we averaged out the normalised Core Web Vitals scores, we were onto
284284something much more trustworthy!
285285
286286<figure >
287- <img src =" /wp-content/uploads/2024/11/new-metric-03.png " alt =" " width =" 1500 " height =" 194 " loading =" lazy " >
287+ <img src =" {{ site.cloudinary }} /wp-content/uploads/2024/11/new-metric-03.png" alt =" " width =" 1500 " height =" 194 " loading =" lazy " >
288288<figcaption >Now the new metric aligns with our ordinal score. That’s great
289289news!</figcaption >
290290</figure >
@@ -310,7 +310,7 @@ numbers. As the scale is 0–1, we just need to subtract the derived score from
310310` = 1 - (AVERAGE(E2:G2)) ` :
311311
312312<figure >
313- <img src =" /wp-content/uploads/2024/11/new-metric-inverted.png " alt =" " width =" 1500 " height =" 194 " loading =" lazy " >
313+ <img src =" {{ site.cloudinary }} /wp-content/uploads/2024/11/new-metric-inverted.png" alt =" " width =" 1500 " height =" 194 " loading =" lazy " >
314314<figcaption >Now we have a higher-is-better paradigm which is much more familiar
315315as a measure of success.</figcaption >
316316</figure >
@@ -321,15 +321,15 @@ worst. I decided that a Lighthouse-like score out of 100 might be more intuitive
321321still: ` = 100 - (AVERAGE(E2:G2) * 100) ` :
322322
323323<figure >
324- <img src =" /wp-content/uploads/2024/11/new-metric-100.png " alt =" " width =" 1500 " height =" 194 " loading =" lazy " >
324+ <img src =" {{ site.cloudinary }} /wp-content/uploads/2024/11/new-metric-100.png" alt =" " width =" 1500 " height =" 194 " loading =" lazy " >
325325<figcaption >Now we have a higher-is-better paradigm which is much more familiar
326326as a measure of success.</figcaption >
327327</figure >
328328
329329Finally, let’s round the numbers to the nearest integer:
330330
331331<figure >
332- <img src =" /wp-content/uploads/2024/11/new-metric-rounded.png " alt =" " width =" 1500 " height =" 194 " loading =" lazy " >
332+ <img src =" {{ site.cloudinary }} /wp-content/uploads/2024/11/new-metric-rounded.png" alt =" " width =" 1500 " height =" 194 " loading =" lazy " >
333333<figcaption >Oh, that doesn’t seem too fair…</figcaption >
334334</figure >
335335
@@ -348,7 +348,7 @@ dataset, gave much more encouraging results, I still wanted to build in more
348348resilience:
349349
350350<figure >
351- <img src =" /wp-content/uploads/2024/11/new-metric-real-data.png " alt =" " width =" 1500 " height =" 192 " loading =" lazy " >
351+ <img src =" {{ site.cloudinary }} /wp-content/uploads/2024/11/new-metric-real-data.png" alt =" " width =" 1500 " height =" 192 " loading =" lazy " >
352352<figcaption >Nice! I worked with RIMOWA for about 18 months on getting them to
353353this place.</figcaption >
354354</figure >
@@ -366,7 +366,7 @@ and a score out of 100 obscures this fact.
366366The 100-based score was short lived, and I soon removed it:
367367
368368<figure >
369- <img src =" /wp-content/uploads/2024/11/new-metric-indexed.png " alt =" " width =" 1500 " height =" 192 " loading =" lazy " >
369+ <img src =" {{ site.cloudinary }} /wp-content/uploads/2024/11/new-metric-indexed.png" alt =" " width =" 1500 " height =" 192 " loading =" lazy " >
370370<figcaption >0–1 is a better scale for indexing.</figcaption >
371371</figure >
372372
@@ -396,7 +396,7 @@ Now, instead of immediately aggregating the normalised values, I weight the
396396normalised values around passingness and then aggregate them.
397397
398398<figure >
399- <img src =" /wp-content/uploads/2024/11/new-metric-weighted.png " alt =" " width =" 1500 " height =" 328 " loading =" lazy " >
399+ <img src =" {{ site.cloudinary }} /wp-content/uploads/2024/11/new-metric-weighted.png" alt =" " width =" 1500 " height =" 328 " loading =" lazy " >
400400<figcaption >It looks like everyone got a little bump… is that fair?</figcaption >
401401</figure >
402402
@@ -418,7 +418,7 @@ based entirely on data, and no weighting is applied with influence or bias. It
418418all facts all the way down.
419419
420420<figure >
421- <img src =" /wp-content/uploads/2024/11/new-metric-crrrux.png " alt =" " width =" 1500 " height =" 278 " loading =" lazy " >
421+ <img src =" {{ site.cloudinary }} /wp-content/uploads/2024/11/new-metric-crrrux.png" alt =" " width =" 1500 " height =" 278 " loading =" lazy " >
422422<figcaption >The Weighted Score further weighted by Ordinal Score gave good
423423outcomes.</figcaption >
424424</figure >
@@ -439,7 +439,7 @@ a list of origins with the click of a button. Here is an abridged top-100
439439origins from the HTTP Archive:
440440
441441<figure >
442- <img src =" /wp-content/uploads/2024/11/new-metric-top-100.png " alt =" " width =" 1500 " height =" 588 " loading =" lazy " >
442+ <img src =" {{ site.cloudinary }} /wp-content/uploads/2024/11/new-metric-top-100.png" alt =" " width =" 1500 " height =" 588 " loading =" lazy " >
443443<figcaption >I had to blur the origins—there’s a lot of NSFW stuff in here.</figcaption >
444444</figure >
445445
@@ -451,7 +451,7 @@ In 2021, [Jake Archibald](https://jakearchibald.com/) ran a series determining
451451Plugging the current roster into CrRRUX:
452452
453453<figure >
454- <img src =" /wp-content/uploads/2024/11/new-metric-f1.png " alt =" " width =" 1500 " height =" 379 " loading =" lazy " >
454+ <img src =" {{ site.cloudinary }} /wp-content/uploads/2024/11/new-metric-f1.png" alt =" " width =" 1500 " height =" 379 " loading =" lazy " >
455455<figcaption >Again, I am happy with the clustering and respect for ordinality.</figcaption >
456456</figure >
457457
0 commit comments