PWA stands for Progressive Web App: a website built with modern web tech so it behaves more like a native app. Users can often install it to their home screen, open it in its own window, and get faster repeat visits via cache and a service worker. Lazy loading can defer what you have not cached yet. A PWA is one kind of web app.
PWAs run in the browser, so one codebase can cover mobile and desktop without a full app store or Google Play release. They shine for catalogs, booking tools, and light e-commerce experiences — especially when responsive design and solid hosting are already in place. They don’t replace every native app, and they are not cross-platform store apps: those ship from a shared codebase. Deep hardware access or heavy offline games may still need a native build.
A real-life example of a PWA
A local shop’s site loads fast on a phone, offers “Add to Home Screen,” and still shows yesterday’s catalog on a flaky subway connection. That “almost an app” feel is a PWA. A push notification and an offline cart are optional extras, not the definition.
Start with performance and a reliable install experience before chasing every PWA feature. Speed work that helps PWAs also helps Core Web Vitals — see Improve Site Performance.