![Sam Dutton](https://web.dev/images/authors/samdutton.jpg) Sam Dutton [X](https://twitter.com/sw12) [GitHub](https://github.com/samdutton) [Mastodon](https://techhub.social/@samdutton) [Bluesky](https://bsky.app/profile/samdutton.bsky.social) [Homepage](https://samdutton.com)

<br />

You won't be able to build a PWA without HTTPS.

Serving your site over HTTPS is fundamental for security, and many APIs won't work without it. If
you need to justify implementation costs, find out [why HTTPS matters](https://web.dev/web/fundamentals/security/encrypt-in-transit/why-https).

If a site uses HTTP for any assets, users will be warned in the URL bar. Chrome displays a warning
like the following.
![Chrome 'not secure' warning](https://web.dev/static/articles/performance-audit-security/image/chrome-secure-warning-b50f01f199ca5.png) *From Chrome 68, the address bar warns if not all assets use HTTPS*

HTTPS should be implemented everywhere --- not just, for example, on login or checkout pages. Any
insecure page or asset can be a vector for attack, making your site a liability for your users and
your business.

Site security is easy to check with [Chrome DevTools Security panel](https://web.dev/web/tools/chrome-devtools/security). Keep a record of any
problems.

The site in the following example is not secure, since some assets are served over HTTP.
![Chrome DevTools Security panel](https://web.dev/static/articles/performance-audit-security/image/chrome-devtools-security-bedb6731dad0c.png) *Chrome DevTools Security panel*