PhotoCashFlow
Log in

Historical record · 2016–2020 · Every figure sourced

The browser worker at work: 30 companies, real money.

≈ 37 min

The service worker — the small script that lives inside the customer's browser, keeps the shop's stock on the shelf (cache), and lets the shop open with no internet — is not a theory. Between 2016 and 2020, thirty named companies published what it did to their numbers: conversions, revenue, sales, subscriptions, ad income, and acquisition cost. Every case below carries its figures exactly as its source states them, the capability the source credits, and a link to that source. Where a famous figure does not hold up, it is flagged — not repeated.

What the worker actually does

It sits between the page and the network. For each request it decides: serve from the shelf (instant, zero network), go to the network, or network first, shelf as backup. It also receives push notifications and makes the site installable — an icon on the home screen, no app store, no 30% commission.

How to read the money

Almost none of these companies published dollars. They published the levers that become dollars: conversion rate, revenue per visit, clickouts, subscriptions, ad revenue, data cost, and customer-acquisition cost. Each card says plainly when a case has no financial figure at all — reach only. Of the 30, 28 carry a measured metric; Uber (№ 23) and Tinder (№ 25) published reach and behaviour signals only, and their cards say exactly that.

30
named companies, each verified against a published source
5
financial levers — conversion, push, reach, ads & subscriptions, cost avoidance
2016–18
when almost all results were published — the PWA showcase era
0
independent audits in the set — read the honesty box at the end

Capability key — which part of the worker earned it

aCache = speed. Stock on the shelf loads instantly.
bOffline / bad network. The shop stays open when the street goes dark.
cPush re-engagement. The worker receives the tap on the shoulder.
dInstall, no store. Home-screen icon, zero app-store friction.
eTiny size. Kilobytes where a native app takes megabytes.
pkgWhole package. The source credits the PWA as a whole, not one capability.

Showing 30 of 30 companies.

No company matches that search. Clear the search or pick “All 30”.
LEVER 1

Conversion & revenue gains

The direct money lever: the same visitors, more of them buying. Fifteen retailers, marketplaces, travel and property companies — the wins come mostly from speed (a) and the home-screen icon (d).

№ 012016

Alibaba.com

B2B e-commerce marketplace

+76% conversions
across browsers — a conversion = a visit resulting in direct contact with a supplier
  • 14% more monthly active users on iOS; 30% more on Android
  • 4× higher interaction rate from Add to Home Screen
  • Push notifications at the same open rate as the native app
d · installc · pushpkg · whole PWA

Source: Google Developers showcase 2016, as summarised in PWA Stats / Elogic — elogic.co

№ 022016

AliExpress

Consumer e-commerce · Alibaba Group

+104% conversion
for new users, across all browsers
  • 82% increase in iOS conversion rate
  • 2× more pages visited per session, per user
  • 74% increase in time spent per session
pkg · whole PWAb · offlinec · push

Source: web.dev case study — web.dev/case-studies/aliexpress (verified live)

№ 032016

Flipkart Lite

E-commerce · India

+70% conversion
among shoppers arriving via Add to Home Screen
  • 3× more time on site — 3.5 minutes vs 70 seconds
  • 40% higher re-engagement rate; 3× lower data usage
  • 63% of Flipkart Lite users reached the site via 2G
  • 60% of all visits came from the home-screen icon; service workers let shoppers browse categories, searches and product pages offline
d · installb · offlinec · push

Source: web.dev case study — web.developers.google.cn/case-studies/flipkart

№ 042017

Lancôme

Luxury beauty e-commerce · L'Oréal · launched Oct 2016

+17% conversions
with an 84% decrease in time until the page is interactive
  • 51% increase in mobile sessions overall; 53% on iOS
  • 15% decrease in bounce rates
  • Push notifications: 18% open rate; over 18,000 shoppers signed up for alerts

Carry the caveats: the recovered-cart push figure conflicts between sources — PWA Stats states a “12% increase in recovered carts” and “8% of people responding to a notification make a purchase”; Retail Dive (24 May 2017) states push “has driven an 8% rise in conversion rates on recovered carts”. Also: most of Lancôme's 2017 PWA users were on iPhones, which did not then support service workers — so the 17% lift is largely a fast-mobile-site-rebuild effect.

a · speedc · push

Sources: web.dev / Google Developers case study 2017 via pwastats.com; Retail Dive, 24 May 2017

№ 052017

BookMyShow

Entertainment ticketing · India

+80% conversions
“80+% increase in conversion rates, which means more users purchasing tickets”
  • PWA 54× smaller than the Android app and 180× smaller than the iOS app — about 440 KB
  • Subsequent loads in less than 2.94 seconds; checkout within 30 seconds
  • Service workers “to deliver reliable performance on slow or unreliable networks”
a · speede · tiny sizeb · offline

Source: web.dev case study — web.dev/case-studies/bookmyshow (verified live)

№ 062017

MakeMyTrip

Online travel · India

3× conversion rate
and first-time shoppers three times more likely to convert than first-time visitors to the native app
  • 38% improvement in page load times; 160% increase in shopper sessions
  • Bounce rate lowered by 20% vs the previous mobile site
  • Reached users in 24% more cities; works offline from cached data; no install required
a · speedb · offlined · install

Source: web.dev case study — web.dev/case-studies/make-my-trip

№ 072016

Housing.com

Online real estate · India · “Housing Go”

+38% conversions
with a 40% lower bounce rate
  • 10% longer average session
  • Page-load performance “increased by over 30 percent”
  • Built on Service Workers, IndexedDB, Add to Home Screen and Push Notifications; users can review previous searches while offline
pkg · whole PWAb · offlinea · speed

Source: Google Developers showcase, reported by InfoTechLead — infotechlead.com

№ 08c. 2020

Rakuten 24

E-commerce — grocery / everyday goods · Japan · results over a 1-month timeframe

+150% sales per customer
and a 200% increase in conversion rate
  • 450% jump in visitor retention vs the previous mobile web flow
  • Visit frequency per user up 310% compared to the rest of their web users
  • Credited driver: installability. Workbox service worker (cache-first CSS/JS, stale-while-revalidate images) for offline / bad network is secondary
  • Results achieved “without spending significant time and money building platform-specific apps for iOS and Android”

Read carefully: the 310% compares people who installed against “the rest of their web users” — a self-selected installed cohort, which inflates the apparent effect.

d · installb · offline

Source: web.dev case study — web.dev/case-studies/rakuten-24 (verified live)

№ 092018

George (ASDA)

Clothing retail · UK · George.com

+31% mobile conversions
with a 3.8× faster average page load time
  • 2× lower bounce rate; 20% more page views per visit
  • 28% longer average time on site for visits from the Home screen
  • Also used push notifications and offline page access
a · speedd · installpkg · whole PWA

Source: Google case study, via Dockyard — dockyard.com

№ 102017

Debenhams

Department-store retail · UK · PWA built in 4 months on Mobify

+40% mobile revenue
and a 20% increase in conversion
  • User journey from browsing to purchase 2× to 4× faster than the previous mobile site
  • During peak trading 2017, mobile revenue overtook desktop revenue
a · speed

Sources: Econsultancy — econsultancy.com; figures also on PWA Stats

№ 112017–18

West Elm

Home-furnishings retail · Williams-Sonoma · US · beta test

+9% revenue per visit
a 9% lift in revenue per visit, in a PWA beta
  • 15% increase in average time spent on site
  • Trade-press telling: a “9 percent” mobile conversion boost “driven largely by revenue-per-visitor gains” — i.e. the 9% is revenue/conversion, not two separate 9% gains
a · speedpkg · whole PWA

Sources: PWA Stats; A List Apart, excerpt of Jason Grigsby, Progressive Web Apps — alistapart.com

№ 122017

Petlove

Pet-supplies e-commerce · Brazil

2.8× conversion
and a 2.8× increase in time spent on site
  • 2× more users go to checkout already signed in (simplified signup / auto sign-back-in)
  • Not attributed to a single capability in the source — PWA plus credential / auto-sign-in

Small conflict: contemporaneous Chrome Dev Summit notes put time spent at 2.7×, not 2.8×. Conversion is 2.8× in both tellings.

pkg · whole PWA

Sources: PWA Stats; Chrome Dev Summit notes — lukew.com

№ 132018

Treebo

Budget hotels · India · PWA 2017, results published Feb 2018

4× conversion rate
year-over-year
  • Conversion rates for repeat users: 3× increase
  • Median interactive time on mobile dropped to 1.5 s
a · speed

Source: Treebo engineering team (Feb 2018), via PWA Stats

№ 142017–18

BMW

Automotive · BMW.com

4× clicks to a sales site
people clicking from the homepage to a BMW sales site — one summary: from 8% to 30%
  • 50% growth in mobile users; 49% more site visits vs the old site
  • Page load 4× faster than the old site

Do not credit the PWA alone: the project was AMP + PWA combined (AMP content pages feeding a PWA). Quote the 4× as an AMP+PWA result.

a · speedAMP + PWA

Source: Think with Google case, via Aureate Labs summary — aureatelabs.com

№ 152016

5miles

Local buy/sell marketplace · US

+30% conversion
for users who arrived via Add to Home Screen — from web.dev's Results list
  • 50% decrease in bounce rates
  • 30% increase in time spent on site
  • Push notifications also added for Android mobile-web users

Flagged headline: web.dev's own Summary headline says the PWA “increases conversions by 60%” — but its Results list contains no 60% figure. The two do not reconcile; this card quotes the Results list, not the headline.

d · installc · push

Source: web.dev case study — web.dev/case-studies/5miles (verified live)

BONUS—

Garbarino

Electronics / home retail · Argentina · sourced but not counted in the 30 — aggregator-only

+27% conversion rate
motivation reported: unreliable network coverage in Argentina
  • Returning visitors +13%; pageviews +35%; bounce rate −9%
b · offline

Source: PWA Stats — e-commerce tag

LEVER 2

Push-notification re-engagement

The service worker is what receives a web push when the page is closed. Three companies published what that tap on the shoulder was worth — including one where push beat email as the best retention channel.

№ 162017

OLX

Online classifieds · India · launched Nov 2016

+250% re-engagement
“Altogether, these two updates increased engagement by 250%” — push + Add to Home Screen
  • 146% higher CTR on Ads; 80% lower bounce rates
  • 23% less time until page is interactive
  • Over 600,000 users signed up for notifications since the site launched in November 2016
  • Speed drove the ad-CTR / bounce gains — “ads loading faster, the clickthrough rate (CTR) rising 146%”
c · pushd · installa · speed

Source: web.dev case study — web.dev/case-studies/olx (verified live)

№ 172016

United eXtra Electronics

Consumer-electronics retail · Saudi Arabia

+100% sales via web push
100% more sales from users arriving via web push, at a 12% click-through rate
  • 4× increase in re-engagement
  • Opted-in users returned 4× more often and spent twice as much time on the site (within six weeks)
  • Web push came to exceed email as eXtra.com's best-performing retention-marketing channel

Scope note: this is a web-push implementation on the mobile site (via Mobify), published by Google alongside the PWA showcases — not a full PWA rebuild story. The credited capability is web push only.

c · push only

Source: web.dev case study — web.dev/case-studies/extra (verified live)

№ 182017

Trivago

Hotel search / travel metasearch · PWA in 33 languages / 55 countries

+97% clickouts to hotel offers
clickouts are Trivago's revenue event — paid referrals to booking sites
  • Engagement +150% for people who add the PWA to the home screen
  • Repeat visits rose to an average of 2 vs 0.8 on the previous mobile site
  • More than 500,000 people added the icon
  • 67% of users who go offline “continue to browse the site when they come back online”
d · installc · pushb · offline

Sources: Think with Google case study, via PWA Stats feed page carrying the Trivago entry and AppYourself summary

Push also drives part of the Lancôme (№ 04), Alibaba (№ 01), Flipkart (№ 03) and Weather Channel (№ 29) results — Lancôme's cart-recovery push and OLX's buyer/seller message alerts are the clearest push-to-purchase attributions in the set.

LEVER 3

Emerging-market reach — small size, offline, bad networks

Where data is expensive, phones are low-end and networks drop, a 200 KB web app reaches customers a 100 MB native app never will. Seven cases — two of them honestly carry no revenue figure at all.

№ 192017

Twitter Lite

Social media · became the default mobile-web experience globally Apr 2017

+75% Tweets sent
with 65% more pages per session and a 20% decrease in bounce rate
  • Takes up less than 1 MB on device; launches up to 30% faster
  • Data Saver “can reduce your data usage by up to 70 percent” (Twitter's own launch post)
  • Secondary summaries of the web.dev case add: 250,000 daily unique users launching from the home screen an average of 4 times a day, and 10 million push notifications sent daily
pkg · whole PWAa · speedb · offlinec · pushd · installe · tiny size

Sources: web.dev / Google case study May 2017, results table via MobiLoud; Twitter launch details via Adweek

№ 202017

Ola

Ride-hailing · India

200 KB — 300× smaller
than downloading the Android app; more than 500× smaller than the iOS app
  • 68% increase in mobile traffic in Tier 2 and 3 cities
  • In Tier 3 cities, conversion rates are 30% higher with the PWA (Tier 2: same as native app)
  • Native sizes for scale: Android app 60 MB, iOS app 100 MB
  • 20% of users who book in the PWA had previously uninstalled the app
  • Repeat visits use as little as 10 KB; 3.4-second first visit and under a second for repeat visits on 2G/3G
e · tiny sizeb · offline / intermittentd · install

Source: web.dev case study — web.dev/case-studies/ola (verified live)

№ 212016

Konga

E-commerce · Nigeria

−92% data, first load
vs the native app — the framing matters; see all four figures
  • 92% less data for initial load, vs native app
  • 82% less data to complete first transaction, vs native app
  • 63% less data for initial load, vs previous mobile web experience
  • 84% less data to complete first transaction, vs previous mobile web experience

Framing note: the often-quoted “−92% data usage” is only correct in the vs-native-app, initial-load framing. Google's own PWA explainer credits service workers directly: “Service workers enabled Konga to send 63% less data for initial page loads, and 84% less data to complete the first transaction!”

a · speed / datae · tiny size

Source: web.dev case study — web.developers.google.cn/case-studies/konga

№ 222017

Jumia Travel

Travel / hotel booking · Africa · Jumia Group · case study released 13 Jun 2017

12× more users than native
versus native apps (Android & iOS), with a 33% higher conversion rate
  • 50% lower bounce rate
  • 5× less data used; 25× less device storage required
  • PWA uses 80% less data than the native app to complete the first transaction
  • Release also credits increased conversions through push notifications
e · data / storagepkg · whole PWAc · push

Sources: Jumia/Google case-study press release, 13 Jun 2017 — wazomoja.com; figures corroborated by PWA Stats

№ 232017

Uber — m.uber

Ride-hailing · global · Uber Engineering, Jun 2017

50 KB core, <3 s on 2G
“The core app is only 50k gzipped and takes less than 3 seconds to load on 2G networks”
  • Designed so anyone can request a ride on any device / network

No financial figure exists: no revenue, conversion or booking figure was published for m.uber. This is a reach / enablement case only — do not attach a financial % to it.

e · tiny sizea · speed

Source: Uber Engineering via PWA Stats

№ 242017–18

Starbucks

Coffee / food ordering · PWA ordering launched 2017; builder case study 2018

99.84% smaller than the app
approximately 233 KB, vs the 148 MB size of the original iOS mobile app
  • Daily active users doubled (builder's account — see flag)
  • Desktop users ordering at about the same rate as mobile app users
  • Offline-first ordering: browse the menu, customise orders and add items to cart without a connection, with a service worker keeping core JavaScript/CSS available offline

Flag: the builder-side account is most often retold as daily active users doubling; other retellings phrase it as Starbucks doubling “the number of web users who place orders each day”. No Google/web.dev Starbucks case-study page with a results table was located — this case rests on builder (Formidable) and press accounts, unlike most entries here.

b · offline-firste · tiny size

Sources: Formidable (the builder) Starbucks project account, via Nearform/Formidable summaries in search results; service-worker detail via Designveloper round-up

№ 252017

Tinder Online

Dating / social

11.91 s → 4.69 s load
and the PWA is 90% smaller than Tinder's native Android app
  • Core experience delivered at 10% of the data-investment costs for a user in a data-costly market (2.8 MB)
  • Business signals in the primary study are qualitative: users “swipe more”, “message more”, “purchase on par with native apps”, longer sessions vs native
  • Service workers “for network resilience”; push notifications for chat engagement; long-term asset caching via service worker / Workbox

No % revenue figure exists in the primary study — and a vendor page's “+137% engagement” claim for Tinder Online is not in it. Do not repeat it.

a · speedb · resiliencec · push

Source: Tinder PWA performance case study (Addy Osmani), PerfPlanet, Dec 2017 — calendar.perfplanet.com

LEVER 4

Speed-driven ad & subscription gains

For media, speed is money twice: more pages seen means more ads viewed, and a fast reading experience converts readers into subscribers. Four publishers — keep the two Pinterest measurement periods separate; they are not one result.

№ 262017 · 2018

Pinterest

Social / visual discovery · two different measurement periods — do not merge

+44% ad revenue
user-generated ad revenue up 44% in the 2017 case study
  • 2017 case: time spent +40% vs the old mobile web experience; core engagements +60%; time-to-interactive fell from 23 seconds to 5.6 seconds on average Android hardware over slow 3G
  • 2018 one-year retrospective: weekly active users on mobile web +103% year-over-year (Brazil 156%, India 312%)
  • Session length +296%; Pins seen +401%; logins +370%; new signups +843% year-over-year
  • 800,000 weekly home-screen users in under 6 months
  • Service workers “for network resilience” alongside the speed work
a · speedb · resiliencepkg · full rewrite

Sources: Addy Osmani, “A Pinterest Progressive Web App Performance Case Study”, Nov 2017 — readmedium.com; Zack Argyle, Pinterest Engineering, “A one year PWA retrospective”, Jul 2018 — go.mobileatscale.com

№ 272018

Nikkei

News / financial media · Japan · PWA launched Nov 2017

+58% conversions
conversions = subscriptions
  • 2.3× organic traffic; 49% more daily active users
  • 2× page views per session; 2× better Speed Index
  • 14 seconds faster time-to-interactive; 75% faster loading with prefetch; Lighthouse score 23 → 82
  • Credited directly: “By adding a service worker… top articles are always available and loaded almost immediately because they're stored using Cache Storage” — cache-first also gives offline / flaky-network reliability; installable via manifest
a · service-worker cacheb · offlined · install

Source: web.dev case study — web.dev/case-studies/nikkei (verified live)

№ 282017

Forbes

Business media · US

+43% sessions per user
with ad viewability up 20% and 100% more engagement
  • Secondary tellings also credit push notifications and Add to Home Screen

Weakest sourcing in this list: aggregator only. The same aggregator also carries a different Forbes set — “2x increase in average user session length, 6x completion rate, and 20% more impressions. Loads in 0.8s down from 3 to 12s” and “Forbes' PWA loads in 2.5 seconds… Impressions per visit are up 10%”. The aggregator does not separate their provenance; the figures may come from different Forbes tests/talks.

a · speedpkg · whole PWA

Source: PWA Stats — page 4 (aggregator only)

№ 292016–17

The Weather Channel

Weather media · weather.com · global · push test 2016; international PWA rollout reported 2017

~1 million push opt-ins
within three months — 52 percent coming from mobile
  • 80% improvement in load time
  • PWA “now available in 62 languages and 178 countries”
  • Push = severe-weather alerts: “they used a technology called service workers to provide offline processing and deliver messages quickly”
  • One code base supporting 60+ languages is also a cost / reach point — see Lever 5
c · pusha · speed

Source: web.dev case study — web.dev/case-studies/weather-channel (verified live)

LEVER 5

Cost avoidance vs native apps

Money not spent is money earned — but this is the thinnest lever in the record. Only one case in the verified set puts a figure on it, and no case anywhere in the set publishes an audited development-cost saving in currency.

№ 302016

Selio

Buy / sell / chat marketplace app

10× cheaper acquisition
“Selio's average customer acquisition cost for Progressive Web Apps is 10× less than for native apps”
  • Conference-talk notes put figures on it: CPA €3–5 for native apps, and €0.30–0.40 for PWA users
  • Users spent an average of 6+ minutes in the app
  • The saving is acquisition cost (link-based, no app-store friction) — not a measured dev-cost saving
d · no store friction

Sources: PWA Stats — page 4; talk write-up, “State of the gap”, Jun 2016 — multipop.org

ALSO—

Cost avoidance, stated without a figure

Inside three cases above — honest about what is and is not measured

  • Rakuten 24 (№ 08) “was able to drive these results without spending significant time and money building platform-specific apps for iOS and Android” — it had judged itself “not in a position to invest the time and cost in developing a platform-specific app”
  • MakeMyTrip (№ 06) — operating on any OS is “non-trivial in terms of development time and expense” saved
  • The Weather Channel (№ 29) — 62 languages / 178 countries served by enabling languages “using one code base”

Open point, stated plainly: no case in the verified set publishes an audited development-cost saving in currency. Treat any specific “$ saved by building a PWA instead of native” figure circulating in blog posts as unsourced — see the Alibaba flag below.

d · one code base

Sources: the case studies at № 08, № 06 and № 29 above.

The honesty box — read this before quoting any number

Famous figures that did not survive checking

These circulate widely in PWA articles. The research checked each against its source; they are listed here so they are never repeated without the flag — two famous names were excluded from the 30 entirely.

  1. Washington Post — NOT a PWA case in its own source. Excluded from the 30. web.dev's page is titled/summarised “AMP helps the Washington Post increase returning users from mobile search by 23%”, with results “23% increase in mobile search users who return within 7 days” and “88% improvement in load time for AMP content versus traditional mobile web” (1,000+ AMP articles/day). Those are Accelerated Mobile Pages figures, with no service worker/PWA attribution on the page. — web.dev/case-studies/wapo (verified live)
  2. Wego — excluded for the same conflation. The amp.dev success story (11 May 2017) credits AMP landing pages plus a follow-on PWA, and its headline numbers — “95% Increase in partner conversion rates”, “49% Increase in search-to-conversion rates”, “3X Increase in ad CTRs”, “10X Increase in page speed” — are presented for the combined AMP+PWA programme, with the speed gain explicitly delivered by AMP (“Pageload speeds decreased from more than 11 seconds to less than one second with AMP”). PWA Stats retells them as PWA results. — amp.dev/success-stories/wego
  3. Cdiscount — no case study found. Excluded. Searches returned no Google/web.dev case study and no company or trade-press figures. If a Cdiscount figure is quoted elsewhere, it was not sourceable in this research.
  4. “Truly” — no case study found. Excluded. No identifiable company/PWA case study under that name was found; the nearest documented travel case is Trivago (№ 18), which may be the source of the confusion.
  5. Alibaba “$15 million annual saving” — unsourced. A secondary statistics page claims Alibaba's PWA strategy “helped them achieve cost savings of around $15 million annually”. No such figure appears in the Google case-study figures for Alibaba (76% / 14% / 30% / 4×). Do not repeat it.
  6. Twitter Lite “68% lower bounce rate” — misstated secondary. A vendor page (InstantPWA) claims “Twitter Lite cut bounces by 68%”. The Google case-study figure is a 20% decrease in bounce rate. The 68% figure appears to be a transplant (cf. Ola's unrelated 68% mobile-traffic increase).
  7. Tinder “+137% engagement” — not in the primary study. The primary Tinder case study (PerfPlanet, Dec 2017) gives load-time/size figures and qualitative “purchase on par with native apps” signals only — no 137% figure. See № 25.
  8. AliExpress iOS figure is 82%, not 84%. At least one secondary slide deck retells it as an “84% surge in iOS conversion rate”. web.dev states 82% (and, confusingly, 84% is Lancôme's time-to-interactive figure — a likely cross-contamination).
  9. 5miles “60%” and BMW's 4× are flagged on their own cards (№ 15 and № 14): the first is internally inconsistent in its primary source; the second is an AMP+PWA result, not PWA-only.

Put your comment here