|
| 1 | +--- |
| 2 | +layout: page |
| 3 | +title: Core Web Vitals on iOS |
| 4 | +page-class: page--services page--workshops |
| 5 | +meta: "Join the one-day workshop and get hands-on with Core Web Vitals in Safari" |
| 6 | +permalink: /workshops/core-web-vitals-on-ios/ |
| 7 | +--- |
| 8 | + |
| 9 | +**Safari’s getting Core Web Vitals in 2025. Are you ready?** |
| 10 | + |
| 11 | +<a href="/contact/" class="btn btn--primary">Get Prepared</a> |
| 12 | + |
| 13 | +When [Google announced Core Web Vitals were coming to Chrome in |
| 14 | +2020](https://web.dev/articles/vitals#core-web-vitals), the web performance |
| 15 | +industry was a frenzy! Everyone wanted to get their sites in shape, and it was |
| 16 | +a great time for web performance. |
| 17 | + |
| 18 | +Five years on, Core Web Vitals have worked! The web as an ecosystem has gotten |
| 19 | +steadily faster across the board: |
| 20 | + |
| 21 | +<figure> |
| 22 | +<img src="/img/content/core-web-vitals-ios/origins-with-good-scores.png" alt="Chart showing an increasing trend in the number of origins passing all three Core Web Vitals" width="1200" height="1200"> |
| 23 | +<figcaption>From the <a href="https://httparchive.org/reports/techreport/tech?tech=ALL#good-cwvs">HTTP Archive Technology Report</a></figcaption> |
| 24 | +</figure> |
| 25 | + |
| 26 | +**Or has it?** |
| 27 | + |
| 28 | +<a href="/contact/" class="btn btn--primary">Get Ahead of the Curve</a> |
| 29 | + |
| 30 | +## Core Web Vitals on (Mobile) Safari |
| 31 | + |
| 32 | +It’s important to view Core Web Vitals through two distinct lenses: |
| 33 | + |
| 34 | +<img src="/img/content/core-web-vitals-ios/firefox-logo.png" alt="Firefox logo" width="128" height="128" |
| 35 | + style="float: right; |
| 36 | + margin-left: 24px; |
| 37 | + shape-outside: url(/img/content/core-web-vitals-ios/firefox-logo.png);" /> |
| 38 | + |
| 39 | +1. **[Core Web Vitals, the metrics](https://web.dev/articles/vitals):** Largest |
| 40 | + Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift. |
| 41 | + These metrics are platform agnostic and defined in a spec that any other |
| 42 | + browser is free to implement. [Firefox already |
| 43 | + has!](https://bugzilla.mozilla.org/show_bug.cgi?id=1722322) |
| 44 | +2. **[The Chrome User eXperience Report |
| 45 | + (CrUX)](https://developer.chrome.com/docs/crux):** The public dataset used by |
| 46 | + Google as a ranking signal for SEO. This is specific only to Chrome, so any |
| 47 | + other browser—including Chrome on iOS!—is a blind spot. |
| 48 | + |
| 49 | +These two points yield two corresponding problems… |
| 50 | + |
| 51 | +1. Apple haven’t implemented any of the Core Web Vitals in their own browser, |
| 52 | + Safari, and; |
| 53 | +2. Apple, until [iOS |
| 54 | + 17.4](https://developer.apple.com/support/alternative-browser-engines/), |
| 55 | + hasn’t allowed any non-WebKit browser engine on the iOS platform. |
| 56 | + |
| 57 | +This means that we’ve had zero visibility of the Core Web Vitals metrics on iOS |
| 58 | +or any flavour of Safari at all. If you’re based in [North |
| 59 | +America](https://gs.statcounter.com/browser-market-share/mobile/united-states-of-america) |
| 60 | +or northwestern Europe, that may mean **the majority of your audience is |
| 61 | +completely unaccounted for**. |
| 62 | + |
| 63 | +However, things are about to change. |
| 64 | + |
| 65 | +<a href="/contact/" class="btn btn--primary">Beat the Competition</a> |
| 66 | + |
| 67 | +<img src="/img/content/core-web-vitals-ios/safari-logo.png" alt="Safari logo" width="128" height="128" |
| 68 | + style="float: left; |
| 69 | + margin-right: 24px; |
| 70 | + shape-outside: url(/img/content/core-web-vitals-ios/safari-logo.png);" /> |
| 71 | + |
| 72 | +## Core Web Vitals Come to Safari |
| 73 | + |
| 74 | +Apple announced that Largest Contentful Paint and Interaction to Next Paint |
| 75 | +would be coming to Safari as part of [the Interop 2025 |
| 76 | +project](https://webkit.org/blog/16458/announcing-interop-2025/)! This means |
| 77 | +that we can begin tracking and instrumenting two of the three Core Web Vitals |
| 78 | +before the end of the year! |
| 79 | + |
| 80 | +## Are You Prepared? |
| 81 | + |
| 82 | +If you’ve been focusing on Core Web Vitals for your Chrome visitors already, |
| 83 | +you’re well poised. But are you prepared for what it might mean for the |
| 84 | +business? Are your developers prepared for the different rendering engine? Do |
| 85 | +you know how to track site-speed in Safari if the data doesn’t go into CrUX? |
| 86 | + |
| 87 | +## Get the Workshop |
| 88 | + |
| 89 | +To help prepare clients—both new and old—I’ve designed a one-day workshop |
| 90 | +covering, but not limited to: |
| 91 | + |
| 92 | +* **Apple, Safari, and Core Web Vitals** |
| 93 | + * Why can’t we get Core Web Vitals on iPhones? |
| 94 | + * Why can’t we get Core Web Vitals in Safari? |
| 95 | + * What even is Chrome on iOS? |
| 96 | +* **Key events** |
| 97 | + * LCP is coming to Safari in 2025! |
| 98 | + * Blink can run on iOS as of 17.4 (but it still doesn’t) |
| 99 | +* **What does Safari mean to you?** |
| 100 | + * Based on your own audience, how much does it matter to you? |
| 101 | + * Can we infer anything from existing Core Web Vitals data? |
| 102 | +* **How does Safari differ from Chrome?** |
| 103 | + * WebKit vs. Blink |
| 104 | + * JavaScriptCore vs. V8 |
| 105 | + * Performance API availability |
| 106 | + * Interop 2025 |
| 107 | +* **How do we measure Safari in the wild?** |
| 108 | + * If it’s not in CrUX, where is it? |
| 109 | + * Real user monitoring |
| 110 | + * Which metrics can we capture |
| 111 | +* **Safari on localhost** |
| 112 | + * Safari-specific devtools |
| 113 | + * Tips, tricks, and workflows |
| 114 | + * Testing real devices |
| 115 | + |
| 116 | +The goal is to leave the team aware of the upcoming changes, arm them with tools |
| 117 | +and knowledge to optimise for the different engines, and ensure that your Safari |
| 118 | +users aren’t being overlooked. |
| 119 | + |
| 120 | +### Remote or In-Person |
| 121 | + |
| 122 | +I much, much prefer in person workshops—it means we can hang out and probably |
| 123 | +head for drinks after! But as it’s only a single day, running the workshop |
| 124 | +remotely works pretty naturally. Remote workshops will be recorded for you to |
| 125 | +keep. |
| 126 | + |
| 127 | +Ready? [Let’s get it booked in!](/contact/) |
| 128 | + |
| 129 | +<a href="/contact/" class="btn btn--primary">Arrange the Workshop</a> |
0 commit comments