Progressive web app (PWA) case studies report measurable gains in mobile reach, speed, engagement, and conversion. The results span media, commerce, transportation, food delivery, real estate, and weather services, with measurements taken in different years and markets.
Contents
- Audience scale and mobile reach
- Speed, loading, and data usage
- Engagement and session behavior
- Conversion and revenue outcomes
- PWA and app size comparisons
- Sector examples beyond publishing
Audience scale and mobile reach
The businesses in these case studies already operated at substantial scale, making their PWA results relevant to publishers and other high-traffic digital services. Mynet serves more than 34 million visitors each month, according to the Mynet web.dev case study. Housing.com was on track for 50 million visits in the year reported by its Housing.com web.dev case study. BookMyShow has more than 50 million monthly visitors, according to its BookMyShow web.dev case study.
Infobae reported 38 million monthly active unique users. Its audience was strongly mobile-led: 71% of traffic came from mobile devices, and 84% of that mobile traffic came from Android phones. These figures come from the Infobae web.dev case study and describe the traffic mix during the period covered there.
The PWA examples also show reach outside the largest urban or highest-connectivity audiences. Ola serves more than 100 Indian cities and has a network of about 600,000 driver-partners. It completes more than 1 million daily rides, while the Ola web.dev case study cites an estimated 300 million daily taxi trips in India as market backdrop. After its PWA launch, Ola reported a 68% increase in mobile traffic in Tier 2 and Tier 3 cities.
Ele.me operates in more than 200 cities in China and serves 260 million registered users. It has more than 1.3 million restaurant listings, and 99% of its users order food on mobile, according to the Ele.me web.dev case study. The figures indicate why mobile delivery performance can matter even when the service already has a large established user base.
Speed, loading, and data usage
Speed is one of the most consistently quantified themes in the case studies. Mynet recorded a 4X faster average page-load speed after launching its AMP-based PWA, according to the Mynet web.dev case study. Housing.com reported a 30% improvement in page-load speed after building Housing Go as a PWA.
Network conditions were explicit in the Ola results. Its first visit took 3.4 seconds on 2G and 3G networks, while repeat visits loaded in less than 1 second on those networks. Ola’s app shell was 200KB. The company said that this was 300 times smaller than its Android app download and more than 500 times smaller than its iOS app download. Repeat visits consumed only 10KB of data.
Ele.me reported an 11.6% reduction in loading time across all pre-cached pages and a 6.35% average reduction across all pages. Its time-to-consistently-interactive for a first load fell to 4.93 seconds on a 3G network. These are separate measurements: the pre-cached-page result does not represent the same page set as the all-pages average.
BookMyShow’s PWA was 54 times smaller than its Android app and 180 times smaller than its iOS app, according to the BookMyShow web.dev case study. These comparisons describe download size, not a claim that every aspect of the applications had identical functionality.
Engagement and session behavior
Several case studies connect a faster or more accessible mobile experience with deeper use. Mynet increased average time on site by 43% on mobile after its PWA rollout. It also gained 34% more page views per session and cut bounce rates by 24%. The same Mynet case study reported 25% higher revenue per article pageview, discussed further below.
Infobae’s mobile sessions were 230% longer than on its previous mobile site. Users viewed three times more pages per session, and the bounce rate fell to 5% from 51% on the previous mobile site. The before-and-after comparison is specific to Infobae’s prior mobile experience and the period documented in its web.dev case study.
Flipkart reported that Flipkart Lite raised time on site to 3.5 minutes, compared with 70 seconds on the previous mobile experience. That is a time-on-site comparison between the PWA experience and the earlier mobile site, rather than a general benchmark for all PWAs.
Housing.com increased average session length by 10% and cut bounce rate by 40% with its new PWA. These changes were reported alongside a 38% increase in conversions. Taken together, the Housing.com measurements cover both behavioral indicators and a business outcome, but they should not be treated as a universal causal model for every implementation.
Conversion and revenue outcomes
The strongest commercial results in the supplied case studies are concentrated in mobile conversion. Flipkart’s PWA increased conversions by 70%, while BookMyShow’s PWA increased conversions by more than 80%. Orange reported a 52% increase in mobile conversions after launching its new PWA.
Housing.com saw 38% more conversions after building Housing Go as a PWA. Lancôme reported a 17% increase in conversions after rebuilding its mobile site as a PWA. In Tier 3 cities, Ola’s PWA produced conversion rates 30% higher than the native app, according to the Ola web.dev case study. That comparison is geographically specific and should not be generalized to Ola’s entire user base.
Mynet’s reported commercial measure was different: revenue per article pageview was 25% higher after its AMP-based PWA launch. For a media publisher, revenue per article pageview can capture monetization efficiency even when the underlying metric is not the same as an order conversion rate.
Lancôme also reported an 8% increase in conversion rates on recovered carts via push notifications. The figure applies to recovered carts reached through push notifications, not to all mobile visitors. The same case study reported that desktop shopping-cart-to-order rate was 38%, while the mobile web conversion rate was 15% during the cited period. Mobile traffic first eclipsed desktop traffic for Lancôme in 2016.
The conversion figures are compactly compared below. Each result retains the scope described by its source.
| Organization | Reported PWA result | Scope of measurement |
|---|---|---|
| Flipkart | 70% increase in conversions | Flipkart Lite PWA |
| BookMyShow | More than 80% increase in conversions | PWA experience |
| Orange | 52% increase in mobile conversions | New PWA |
| Housing.com | 38% more conversions | Housing Go PWA |
| Lancôme | 17% increase in conversions | Rebuilt mobile site |
| Ola | 30% higher conversion rates | Tier 3 cities versus native app |
PWA and app size comparisons
The case studies treat small downloads as a practical access metric, particularly for users on slower networks, limited data plans, or devices with constrained storage. Ola’s app shell was 200KB. Ola said that this was 300 times smaller than the Android app download and more than 500 times smaller than the iOS app download. Its repeat visits consumed only 10KB of data, giving the case study a separate measure for returning users.
BookMyShow reported that its PWA was 54 times smaller than the Android app and 180 times smaller than the iOS app. The two ratios are not interchangeable: they compare the PWA with different platform downloads. They also describe relative size, not loading speed, conversion, or total data consumed during a complete session.
These examples put the performance results in a wider context. A PWA can be evaluated not only by whether a page becomes interactive sooner, but also by how much a first-time visitor must download and how much data a returning visitor uses. The Ola case study is the clearest example of both measurements, with a 3.4-second first visit on 2G and 3G and repeat visits below 1 second.
Sector examples beyond publishing
The results extend well beyond media sites. Ola’s 68% increase in mobile traffic in Tier 2 and Tier 3 cities shows a reach outcome in transportation. Its 1 million-plus daily rides and roughly 600,000 driver-partner network provide the operating context for that result, while the 30% higher Tier 3 conversion rate supplies a separate outcome.
Ele.me’s mobile ordering share was 99% among users. Its PWA work was associated with an 11.6% loading-time reduction across pre-cached pages, a 6.35% average reduction across all pages, and a 4.93-second first-load time-to-consistently-interactive on 3G. The company’s more than 200-city footprint and more than 1.3 million restaurant listings show the scale at which these measurements were reported.
Lancôme’s case study connects mobile commerce with both audience behavior and re-engagement. Mobile traffic had first eclipsed desktop traffic in 2016. After the PWA rebuild, mobile sessions on iOS increased by 53%, overall conversions increased by 17%, and recovered-cart conversion rates increased by 8% through push notifications. Its cited desktop and mobile shopping measures remained distinct: 38% for desktop shopping-cart-to-order rate and 15% for mobile web conversion rate.
The Weather Company serves an average of 40 billion forecast requests every day, according to The Weather Channel web.dev case study. That figure describes request volume and does not itself quantify a PWA lift, but it illustrates the very large service scale represented in the case-study set.
Across these examples, the reported outcomes fall into four measurable groups: audience reach, technical performance, user engagement, and commercial conversion. Mynet, Infobae, and Flipkart provide especially clear publishing and retail engagement comparisons; Ola and Ele.me document network and mobile-access conditions; Housing.com, Lancôme, Orange, and BookMyShow report conversion changes. The measurements come from the named web.dev case studies and cover the periods those case studies cited, so legacy results should be read as historical case-study findings rather than newly verified benchmarks.