• Preact: drop in replacement for React and super tiny. Faster time to interactive too github.com/developit/preact #ChromeDevSummit

    • 3
    • 16
  • Webpack PoC from @addyosmani to put perf in your face when compiling. addyosmani/793126424253075456 #ChromeDevSummit

    • 0
    • 1
  • Code splitting in not panacea. Current tooling doesn’t put performance in your face. #WhatsInYourBundle #ChromeDevSummit

    • 1
    • 0
  • The PRPL pattern for improving time to interactive. #ChromeDevSummit

    • 1
    • 1
  • Less code, loaded better, helps everyone. #ChromeDevSummit

    • 0
    • 0
  • Test on real devices and real networks. No substitute. #ChromeDevSummit

    • 0
    • 0
  • Parse and compile time of 1MB (after gzip) of JS without download time #ChromeDevSummit

    • 0
    • 0
  • Ship minimal functional script to your users. #ChromeDevSummit

    • 0
    • 0
  • Average React app per from @addyosmani survey #ChromeDevSummit

    • 0
    • 1
  • Configuring Webpack #ChromeDevSummit

    • 0
    • 0
  • Time to interactive, <5s on 3G real device, <2s with service worker #ChromeDevSummit

    • 0
    • 0
  • Key points in loading a web application or site #ChromeDevSummit

    • 0
    • 0
  • Fast is not the default for most libraries and frameworks, but @addyosmani says: #ChromeDevSummit

    • 0
    • 1
  • Current saturation of loading on the web. 53% bounce after 3 seconds. All train of thought well lost after 10 #ChromeDevSummit

    • 0
    • 1
  • RT @slightlylate: Lyft, as a PWA, the future is here:

    • 0
    • 0
  • Average load time for @lyft PWA is faster than their native apps on modern device & shipped w/4x less engineers in 1 month #ChromeDevSummit

    • 1
    • 3
    • 2
    • 9
  • Performance impact on second load from service workers #ChromeDevSummit

    • 1
    • 2
  • First paint vs first meaningful paint #ChromeDevSummit

    • 1
    • 2
  • Impacts on server side rendering. Should we be surprised? #ChromeDevSummit

    • 1
    • 6
  • Housing Go’s metrics improvements moving to PWAs #ChromeDevSummit

    • 2
    • 5
  • Day 2 starts! #ChromeDevSummit

    • 0
    • 0
  • Test on real devices and networks, optimize network utilization, ship smallest amount of JS possible #ChromeDevSummit

    • 0
    • 2
  • V8 internals, like parse and complie time, available in Canary dev tools! #ChromeDevSummit

    • 0
    • 2