[meta] Lighthouse 6.0 Burndown

[brendankenny]

Channeling our ancestors, we introduce the new abbreviated major release burndown list.

6.0 final scope

• (see all: https://github.com/GoogleChrome/lighthouse/labels/6.0)
• T&S added as a group to BP [@Beytoven] (PR report: add Trust & Safety group under Best Practices #10623)
• add "mixed content" wording into "https" (PR core(is-on-https): add Mixed Content verbiage to description #10712) [@Beytoven]
• new metrics actionability
• • LCP core: surface LCP element in a diagnostic audit #10517
• • CLS core: surface top CLS elements in a diagnostic audit #10702
• • long tasks new_audit: add long-tasks diagnostic audit for surfacing top long tasks #10736
• window.location for finalUrl [@paulirish, @patrickhulce] (PR core(driver): use last frameNavigated event to determine finalUrl #10339)
• add desktop scoring curves to LCP/TBT [@brendankenny] (PR core: add desktop score curves for TBT and LCP #10756)
• roll 1.0.0 of adspeed plugin [@paulirish]

Punting to 6.1

• fold experimental config into default? [@connorjclark]

6.0-beta.0 scope

(need to triage a bit )

New audits

• Total Blocking Time
  • land it (PRs new_audit: add TTI Companion Metric to JSON #8975, core(tbt): Clean up total blocking time code #9409)
  • Update score curve from HTTPArchive distributions [@brendankenny]
  • web.dev docs (content: Lighthouse doc for Total Blocking Time web.dev#1627)
• Largest Contentful Paint
  • Land observed impl (PR core(largest-contentful-paint): add new metric #9706)
  • Land lantern impl/audit [@connorjclark]
  • web.dev docs (Add Largest Contentful Paint documentation for Lighthouse web.dev#1639)
• New axe audits evaluate new axe audits for inclusion #7127
  • land new audits (PR new_audit: add new accessibility audits #9798) [@brendankenny]
  • web.dev docs (content: New a11y audit docs for Lighthouse 6.0 web.dev#1629)
• Cumulative Layout Shift
  • land it (PR new_audit: add cumulative layout shift metric #9037) [@paulirish]
  • make decisions about it :)

Lantern

• "Fixed RTT" calculation [@paulirish]
• Keep first paint events (FCP may impact by the loadEvent fire or not in simulator throttling. #9627) [@connorjclark]
• Remove min task duration core(lantern): Remove min task duration from lantern graphs #9910 [@warrengm]
• data URI server response time (lantern: data uris include server response time #9833) [@patrickhulce]

Scoring

• check latest HTTPArchive distributions for major drift from current metric score curves [@brendankenny]
• apply new LH 6.0 score weightings [@paulirish]
  • deprecate any existing metrics [@paulirish]
• desktop curves Make desktop perf metric score curves identical everywhere #9436 [@connorjclark ]
• revise scoring documentation (content: Add historical scoring info and deprecations for Lighthouse 6.0 web.dev#1630) [@kaycebasques]
  • take another pass on this and merge in work from here and probably here [@paulirish]
  • these docs need to be updated https://github.com/GoogleChrome/lighthouse/blob/d2ec9ffbb21de9ad1a0f86ed24575eda32c796f0/docs/scoring.md#how-are-the-scores-weighted
• Move PWA fastenough check to use TBT instead? Punting for now and keeping it dependent on TTI. Moving to TBT doesn't appear to be a clear win.

New gatherers

• main-document-content Add a html-only gatherer #9756 (PR core(gather): add new MainDocumentContent public artifact #9781) [@brendankenny]

Core misc

• iframe page dependency fix (PR core(lantern): link layout nodes to root frame request #9727) [@patrickhulce]
• redirect/first vs last navstart cleanups Improve handling of redirects, navStart #8984 [@brendankenny] core(driver): use last frameNavigated event to determine finalUrl #10339 handled the part we wanted for 6.0
• nexus 5x -> moto g4 labeling change [@connorjclark]
• i18n plugin things

Lighthouse CI [@patrickhulce]

• MVP burndown list: MVP Burndown lighthouse-ci#9

Extension

• retire the full-LH extension (PR clients: retire extension; replace with PSI launcher #9193) [@connorjclark]

DevTools [@connorjclark]

• Add device emulation flag core: add settings.internalDisableDeviceScreenEmulation #9377
• New design / Throttling removal / logo
• OOPIFs in DevTools Audits panel are not analyzed
• Write throttling Learn More doc [cjamcl, paulirish]

PSI

• New field data thresholds [@paulirish]
• reanalyze prompt. redirect & amp [@exterkamp]
• Make comms for v6.0.0 PSI scoring changes [@egsweeny]

Plugins

• QoL improvements Unclear model for installing/using a plugin alongside LH #9052 [@paulirish]
• Write Plugins learn more doc [@egsweeny]
• "Community plugins beta" in DevTools [@connorjclark]
  • build step [@brendankenny]

Budgets

• Add timing budgets [Lightwallet] Support timings in budgets UI #8917 [@khempenius]

Stack Packs

• Pick and merge new packs from lighthouse-stack-packs (PR core(stack-packs): add angular, react, amp, and magento packs #9797) [@exterkamp]
• i18n strings [@exterkamp]

Puntable

Core breaking changes (#9180)

• Remove path support for --extra-headers (and possibly budget-path?) as now users can use cli-flags-path
• (possibly) remove maxWaitForFcp timeout and look directly for the early load-failure cases (DNS, bad cert, etc) - core(constants): increase default maxWaitForFcp #9509 (comment)
• outstanding i18n tasks? Internationalization of Lighthouse (Phase 2) #7238 [@exterkamp] none for 6.0
• (possibly) refactor i18n section in proto to use Map<string, string> instead of RendererFormattedStrings

Report

• mobile or desktop run indicator at the top of the report Report needs visible indicator of mobile or desktop run  #9379

[addyosmani]

Thanks for putting together the 6.0 burndown list, @brendankenny! Are we planning to create issues for tracking the rest of the items here? (e.g scoring seems light :))

[brendankenny]

Thanks for putting together the 6.0 burndown list, @brendankenny! Are we planning to create issues for tracking the rest of the items here? (e.g scoring seems light :))

yes, any and all of these can be expanded in here based on how the work can be split up and in separate issues if they need more discussion. We can definitely do JIT expansion based on where discussion is needed...for many of these PR review is sufficient, for others (like scoring) there are other discussions going on that may end up finding a home in a new issue.

But please do open issues and expand bullet points as you see fit.

[rockeynebhwani]

@paulirish / @addyosmani - Is there a timeline for LightHouse 6.0 to be released?

[natusvince]

@paulirish / @addyosmani - Is there a timeline for LightHouse 6.0 to be released?

+1

[connorjclark]

6.0 is LIVE.