
Key takeaways
- Rakuten 24 ran a month-long 50/50 A/B test and measured 53.37% more revenue per visitor and 33.13% higher conversion on the optimized version.
- Vodafone's optimized page improved Largest Contentful Paint by 31% and measured 8% more total sales, plus gains in lead-to-visit and cart-to-visit rate.
- Vodafone's named changes were server-side rendering a widget and critical HTML, plus resizing the hero image and holding back images not yet in the viewport.
- Both tests split real production traffic 50/50 rather than comparing before-and-after periods, controlling for seasonality and traffic-mix shifts.
- Google selected and published both cases as examples of the pattern it wants publicised, so neither figure is a guaranteed or average effect size for every site.
Google runs a small library of named, dated case studies at web.dev/case-studies, each attached to a real company and a real test. Two of them isolate Core Web Vitals specifically: Rakuten 24, a Japanese e-commerce retailer, and Vodafone. Unlike Deloitte’s 37-site correlation study or Shopify’s aggregate LCP data covered on this site’s page speed and conversion rate piece, these two are single-company A/B tests that Google itself ran or reviewed and published under its own byline. Here is what each one actually tested, in Google’s own words.
Rakuten 24: a month-long test
The setup. Rakuten’s team picked a landing page with “significant traffic and conversion” so the test could produce a meaningful sample, then split traffic 50/50 for a month: half of visitors saw the original page (version B), half saw a performance-optimized version (version A) that was otherwise unchanged. The write-up, credited to four named Rakuten and Google engineers and last updated 24 August 2022, reports the optimized version’s results relative to the original.
The business numbers. Version A delivered a 53.37% increase in revenue per visitor and a 33.13% increase in conversion rate, alongside a 15.20% increase in average order value, a 35.12% reduction in exit rate, and a 9.99% increase in time on page.
The performance numbers behind it. The same optimized version cut Cumulative Layout Shift by 92.72%, improved First Input Delay by 7.95%, First Contentful Paint by 8.45%, and Time to First Byte by 18.03%, relative to the unoptimized version. Separately, Rakuten also ran a field-data correlation analysis (not the A/B test) across its real user population and found good LCP associated with up to 61.13% higher conversion and 26.09% higher revenue per visitor, a wider, noisier number that supports the same direction without being the headline A/B result.
Vodafone: 8% more sales
The setup. Vodafone’s optimized and original pages ran as a 50/50 A/B split too, each getting roughly 100,000 clicks and 34,000 visits a day from paid display, search, social and app traffic, “visually and functionally identical” apart from the performance changes. Google published this one on 17 March 2021.
What actually changed. Google names three changes, not a general “made it faster” claim: moving the rendering logic for one widget from client-side to server-side, server-side rendering the critical HTML, and image work (resizing the hero image, SVG and PNG optimization, and media queries to avoid loading images not yet visible in the viewport).
The result. The optimized version improved Largest Contentful Paint by 31% and produced 8% more total sales, plus a 15% uplift in lead-to-visit rate and an 11% uplift in cart-to-visit rate. One honest wrinkle Google’s own page reports: DOMContentLoaded actually increased 15% on the optimized version even as LCP improved, a reminder that one metric moving well does not mean every metric moves the same way.
Why we care
These are Google’s own selected success stories, not a random sample. Google chose to publish Rakuten 24 and Vodafone specifically because the numbers were good enough to make the point Google wants to make: Core Web Vitals work pays off in revenue, not just rankings. That is a legitimate reason to take Core Web Vitals seriously, and a bad reason to promise a client 53% more revenue from a similar change; Rakuten’s own field data on the same site showed a much wider range of outcomes than its single A/B test headline.
An A/B test beats a before/after comparison, which is why these numbers travel further than Deloitte’s or Shopify’s. Splitting live traffic 50/50 for the same weeks controls for seasonality, marketing pushes and traffic-mix shifts that a simple before-and-after read cannot; that is a stronger methodology than the correlational studies in our companion piece on page speed and conversion rate, even though the two named cases here cover only two companies rather than dozens.
Cite the company and the exact change, not just the percentage. “31% faster, 8% more sales” is Vodafone’s number for three named technical changes on one page in 2021. “53% more revenue per visitor” is Rakuten 24’s number for one landing page over one month. Neither is a general Core Web Vitals multiplier; both are useful, specific, sourced evidence that the work matters.
The evidence
- Subject
- Google's own Core Web Vitals business-impact case studies
- Timeframe
- Vodafone 2021; Rakuten 24, 2022
- Verified
- Yes, against first-party data
| Metric | Before | After |
|---|---|---|
| Rakuten 24 - revenue per visitor, optimized vs. original page | 0% | 53.37% |
| Rakuten 24 - conversion rate, optimized vs. original page | 0% | 33.13% |
| Vodafone - Largest Contentful Paint improvement | 0% | 31% |
| Vodafone - total sales, optimized vs. original page | 0% | 8% |
Sources
- 1.Rakuten 24 case study - Google web.dev, August 24, 2022Primary
- 2.Vodafone case study - Google web.dev, March 17, 2021Primary
Common questions
Were these controlled tests or just before-and-after comparisons?
Both were A/B tests. Rakuten 24 split traffic 50/50 between an optimized landing page and the original for one month. Vodafone also ran a 50/50 split, serving roughly 100,000 clicks and 34,000 visits a day to each version, with the two pages "visually and functionally identical" apart from the performance work.
What exactly did Vodafone change to cut LCP by 31%?
Per Google's write-up, three changes, moving the rendering logic for one widget from client-side to server-side, server-side rendering the critical HTML, and image work - resizing the hero image, optimizing SVGs, optimizing PNGs and avoiding loading images that were not yet visible in the viewport.
Do these figures apply to any site that improves Core Web Vitals?
No. Google chose these two cases to publish as success stories; it does not claim they represent a typical or average effect size. Rakuten 24's own field-data analysis (separate from its A/B test) found good LCP correlated with up to 61.13% higher conversion on some segments and lower gains on others, which is itself a sign the multiplier varies by site and traffic mix.
About the author

Founder, UpgradIQ FZC LLC
Adam Hafez works on technical SEO and search measurement: how pages get crawled, indexed, ranked and now quoted by answer engines. He founded UpgradIQ, which reads Google Search Console and GA4 to tie ranking movement back to the changes that caused it. He publishes what the data supports and states the limits of it.
- Technical SEO
- Search Console and GA4
- Answer engine optimization
- Structured data
The briefing
Only what actually changed in search, delivered in full by RSS, Atom or JSON feed.
FollowRelated reading
Median home page weight 2025: 2.86 MB desktop, 2.56 MB mobile
The 2025 Web Almanac puts the median home page at 2.86 MB on desktop and 2.56 MB on mobile, with images and JavaScript the two largest parts.
Image lazy loading and width/height checker
Image lazy loading checker: paste HTML to test every img tag for width and height, lazy loading on the likely LCP image. Free, runs in your browser.
Page weight and rankings: what the Backlinko study actually found
Backlinko and Ahrefs analyzed 11.8 million search results and found no correlation between page HTML size and Google rankings.
INP in 2025: 77% of mobile sites pass, but the top 1,000 lag at 63%
The 2025 Web Almanac's INP data: 77% of mobile sites have good INP, popular sites trail at 63%, and mobile home pages beat inner pages 80% to 69%.



