View:

Progressive Web App 82 / 100

These audits validate the aspects of a Progressive Web App.

App can load on offline/flaky connections

Ensuring your web app can respond when the network connection is unavailable or flaky is critical to providing your users a good experience. This is achieved through use of a Service Worker.

  • Has a registered Service Worker
  • URL responds with a 200 when offline
  • Cache contains start_url from manifest (alpha)

Page load performance is fast

Users notice if sites and apps don't perform well. These top-level metrics capture the most important perceived performance concerns.

  • First meaningful paint (target: 1,600ms) (4351.0ms)  43
  • Speed Index (target: 1,250) (2249)  90
    First Visual Change: 1825ms
    Last Visual Change: 4370ms
  • Estimated Input Latency (target: 50ms) (36.5ms)  99
    90% probability of input latency at 36.5ms or shorter.
    (50%: 16.0ms, 75%: 16.0ms, 90%: 36.5ms, 99%: 211.3ms, 100%: 255.6ms)
  • Time To Interactive (alpha) (target: 1,700) (4351ms)  60
  • Content scrolls at 60fps (Coming soon) ¯\_(ツ)_/¯
  • Touch input gets a response in < 150ms (Coming soon) ¯\_(ツ)_/¯
  • App is interactive without jank after the first meaningful paint (Coming soon) ¯\_(ツ)_/¯

Site is progressively enhanced

Progressive enhancement means that everyone can access the basic content and functionality of a page in any browser, and those without certain browser features may receive a reduced but not unfunctioning experience.

  • Page contains some content when its scripts are not available

Network connection is secure

Security is an important part of the web for both developers and users. Moving forward, Transport Layer Security (TLS) support will be required for many APIs.

  • Site is on HTTPS
  • Site redirects HTTP traffic to HTTPS

User can be prompted to Add to Homescreen

While users can manually add your site to their homescreen in the browser menu, the prompt (aka app install banner) will proactively prompt the user to install the app if the below requirements are met and the user has visited your site at least twice (with at least five minutes between visits).

  • Has a registered Service Worker
  • Manifest exists
  • Manifest contains start_url
  • Manifest contains icons at least 144px
  • Manifest contains short_name

Installed web app will launch with custom splash screen

A default splash screen will be constructed, but meeting these requirements guarantee a high-quality and customizable splash screen the user sees between tapping the home screen icon and your app’s first paint.

  • Manifest exists
  • Manifest contains name
  • Manifest contains background_color
  • Manifest contains theme_color
  • Manifest contains icons at least 192px

Address bar matches brand colors

The browser address bar can be themed to match your site. A theme-color meta tag will upgrade the address bar when a user browses the site, and the manifest theme-color will apply the same theme site-wide once it's been added to homescreen.

  • Manifest exists
  • HTML has a theme-color <meta> (#5217a0) 
  • Manifest contains theme_color

Design is mobile-friendly

Users increasingly experience your app on mobile devices, so it's important to ensure that the experience can adapt to smaller screens.

  • HTML has a viewport <meta>
  • Content is sized correctly for the viewport

Best Practices

These audits do not affect your score but are worth a look.

  • Accessibility: Element aria-* roles are valid
  • Accessibility: Element aria-* attributes are valid ARIA attributes
  • Accessibility: Background and foreground colors have a sufficient contrast ratio
  • Accessibility: Every image element has an alt attribute
  • Accessibility: Every form element has a label
    Form elements must have labels
    • #app-root > .container.text-center > .city-select-container.false > .city-options-continer > .auto-complete-container > .input-city
  • Manifest: Manifest's short_name won't be truncated when displayed on homescreen
  • Manifest: Manifest's display property is set (standalone) 
  • UX: Service worker makes use of push notifications, if appropriate (Coming soon) ¯\_(ツ)_/¯
  • UX: Tap targets are appropriately sized for touch (Coming soon) ¯\_(ツ)_/¯
  • UX: Payment forms marked up with [autocomplete] attributes (Coming soon) ¯\_(ツ)_/¯
  • UX: Login forms marked up with [autocomplete] attributes (Coming soon) ¯\_(ツ)_/¯
  • UX: Input fields use appropriate [type] attributes for custom keyboards (Coming soon) ¯\_(ツ)_/¯

Performance Metrics

These encapsulate your app's performance.

  • Performance: Critical Request Chains 12
    Longest request chain (shorter is better): 3
    Longest chain duration (shorter is better): 3726.76ms
    Longest chain transfer size (smaller is better): 66.35KB
    Initial navigation
    / (housing.com)
    mobile/manifest.79b34388b9b089408d6c.js (assets-0.housingcdn.com) - 1944.72ms, 13.65KB
    images/mobile-banner-6f103fc18d00c5356d55c824f0515889.png (assets-0.housingcdn.com) - 2015.62ms, 14.43KB
    mobile/homeView.a829ff56268d9510eb12.js (assets-0.housingcdn.com) - 2152.36ms, 23.09KB
    images/city-sprite-1931d0fe6f27f4f5844af41729a024b9.png (assets-0.housingcdn.com) - 2323.81ms, 14.29KB
    mobile/app.8cd99c67d1c7ce54b71c.js (assets-0.housingcdn.com)
    mobile/lazyView.f5ad2ba36d680fac0d7e.css (assets-0.housingcdn.com) - 3189.63ms, 66.33KB
    mobile/homeView.a829ff56268d9510eb12.css (assets-0.housingcdn.com) - 3279.75ms, 64.87KB
    mobile/loginView.e50bbade1d561c4f915f.css (assets-0.housingcdn.com) - 3297.56ms, 63.29KB
    mobile/userProfileView.972a193001b01c0562ec.css (assets-0.housingcdn.com) - 3297.89ms, 62.99KB
    mobile/searchView.010aeecb1a4a2eef98d1.css (assets-0.housingcdn.com) - 3315.10ms, 65.11KB
    mobile/vendor.a1893c0e804e49bcdb7a.js (assets-0.housingcdn.com) - 2689.14ms, 78.18KB
    /favicon1.png (housing.com) - 3329.72ms, 0.75KB
    housing_mobile/icomoon-d10e5de610f0385805d449579fd486cb.woff2 (assets-1.housingcdn.com) - 3726.76ms, 3.70KB
  • Performance: User Timing marks and measures 0