PWA category refactor tracking issue

New groupings:

Fast and Reliable

• Page load is fast enough on mobile networks (TTI < 10s)
• Current URL responds with a 200 when offline
  • rename: “Current page responds with a 200 when offline” #6494
• start_url responds with 200 when offline - #6397

Installable

• Uses HTTPS (either localhost or has valid certificate)
• Registers a service worker
  • check that test page URL is in SW scope #6609
  • check that start_url is in SW scope #6678
• Manifest requirements (starturl, name, display, icons) #6630

PWA Optimized

• rename group #6494
• Redirects HTTP traffic to HTTPS
  • ~should be in a different group?~ (deferring question for now)
• Is not configured for a custom splash screen
• Address bar does not match brand colors
  • needs a rename #6494
• Has a <meta name="viewport"> tag with width or initial-scale
• Content is sized correctly for the viewport
• Contains some content when JavaScript is not available

Manual

• Page transitions don’t feel like they block on the network
• Site works cross-browser
• Each page has a URL

Next:

• add groups to default-config - #6396
• Badging!
  • Add grayscale group badges #6486, #6686
  • Change to filled-in badges when group is passing - #6504,
  • Replace score gauge with badged gauge - #6526, #6670
• Add adequate vertical spacing between audit groups (see comment) - #6688
• Score gauge tooltip (see comment) - #6689
• No more passed audit hiding
  • Refactor of current category-renderer to support new use cases #6460, #6482, #6594
  • Add pwa-category-renderer, don’t hide passed audits #6486

Lighthouse v5

• ⁅ ⁆ Figure out LHR/scoring story

[hwikyounglee]

And we landed on “PWA Optimized” cc: @kusler @paulirish 💅

[brendankenny]

💥 💥 💥 💥