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
Imagine my delight when ISO got in touch. I love a spec, I love a standard, so
20
+
working with _the_[International Organization for
21
+
Standardization](https://www.iso.org/) is a bit of a dream come true! As a Brit,
22
+
[ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) and [ISO
23
+
3103:2019](https://www.iso.org/standard/73224.html) are particularly close to my
24
+
heart, so to work with the folk that write them…? It’s a yes from me.
25
+
26
+
Conversations stared in October 2024 with a view to kicking off the project in
27
+
early 2025. This gave us ample time to [design the perfect
28
+
engagement](/services/) and be very well prepared into the run-up. The brief was
29
+
simple: improve the user experience. The focus wasn’t on
30
+
[SEO](/2023/07/core-web-vitals-for-search-engine-optimisation/) or revenue, but
31
+
simply on improving the user experience. After all, improve UX, and all else
32
+
follows. It’s a wise move!
33
+
34
+
We decided to benchmark on [Core Web Vitals](/workshops/core-web-vitals-on-ios/)
35
+
as they’re arguably the most sensible place to start for a fledgling project.
36
+
Their biggest sticking points were Largest Contentful Paint and Cumulative
37
+
Layout Shift. Interaction to Next Paint wasn’t much of a concern for them as
38
+
they’d made smart decisions in the past and not gone all-in on JavaScript.
39
+
40
+
The project was to be incredibly tactical—a quick-fire round of specific
41
+
improvements built out into a backlog that the team could pick up as and when
42
+
they were ready. What was nice about this approach, and not running a big
43
+
reveal-style project, is that we were able to realise performance improvements
44
+
while the project was in flight. Not only was this highly motivating, it
45
+
demonstrated immediate value in the project. It was the right thing to do!
46
+
47
+
And how did it go? It went very well:
48
+
49
+
<figure>
50
+
<imgsrc="/img/content/case-studies/iso-org/crux.png"alt="Graphs showing significant and sustained improvements in all three Core Web Vitals since the project started"width="1500"height="348"loading="lazy">
51
+
<figcaption>I think the numbers speak for themselves…</figcaption>
52
+
</figure>
53
+
54
+
As is customary, I handed over a full Trello backlog (half of which were already
55
+
live), and an Executive Summary document for the non-technical stakeholders and
56
+
sponsors.
57
+
58
+
It was about as targeted as a [web performance audit](/performance-audits/) can
59
+
get: in and out, job done.
60
+
61
+
If you need some of the same, [get in touch](/contact/).
0 commit comments