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 No
• URL responds with a 200 when offline No
• Cache contains start_url from manifest (alpha) No

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) (780.6ms)  100
• Speed Index (target: 1,250) (1009)  99
  First Visual Change: 824ms

  Last Visual Change: 1084ms
• Estimated Input Latency (target: 50ms) (81ms)  69
  90% probability of input latency at 81.0ms or shorter.

  (50%: 16.0ms, 75%: 16.0ms, 90%: 81.0ms, 99%: 184.3ms, 100%: 195.8ms)
• Time To Interactive (alpha) (target: 1,700) (1310.9ms)  99
• 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 Yes

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 Yes
• Site redirects HTTP traffic to HTTPS No

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 No
• Manifest exists No
• Manifest contains start_url No
• Manifest contains icons at least 144px No
• Manifest contains short_name No

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 No
• Manifest contains name No
• Manifest contains background_color No
• Manifest contains theme_color No
• Manifest contains icons at least 192px No

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 No
• HTML has a theme-color <meta> No
• Manifest contains theme_color No

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> Yes
• Content is sized correctly for the viewport Yes

• Accessibility: Element aria-* roles are valid Yes
• Accessibility: Element aria-* attributes are valid ARIA attributes Yes
• Accessibility: Background and foreground colors have a sufficient contrast ratio Yes
• Accessibility: Every image element has an alt attribute No
  Images must have alternate text

  • #react-mount > div > div:nth-of-type(1) > div > a > img
• Accessibility: Every form element has a label Yes
• Manifest: Manifest's short_name won't be truncated when displayed on homescreen No
• Manifest: Manifest's display property is set No
• 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: Critical Request Chains 8
  Longest request chain (shorter is better): 2

  Longest chain duration (shorter is better): 1159.53ms

  Longest chain transfer size (smaller is better): 63.79KB

  Initial navigation

  / (website--gatsbyjs.netlify.com)

  /path---index-6d06fec8966348fc5746.js (website--gatsbyjs.netlify.com) - 489.35ms, 3.72KB

  /page-component---pages-index-js-b9b5a8df7b9945bcfe85.js (website--gatsbyjs.netlify.com) - 494.53ms, 3.97KB

  /css (fonts.googleapis.com) - 588.99ms, 4.69KB

  static/gatsby-monogram.b4293b66.jpg (website--gatsbyjs.netlify.com) - 728.34ms, 17.47KB

  /app-aa3a298678530f932043.js (website--gatsbyjs.netlify.com) - 747.09ms, 21.57KB

  v10/UC3ZEjagJi85gF9qFaBgIN4KoCs5_BuQksQmhwRAS2Y.woff2 (fonts.gstatic.com) - 1009.58ms, 22.35KB

  static/ftn45-webfont.c2439033.woff2 (website--gatsbyjs.netlify.com) - 1028.84ms, 22.69KB

  /commons-780f71b3b274bd3484f3.js (website--gatsbyjs.netlify.com) - 1159.53ms, 67.29KB
• Performance: User Timing marks and measures 0