• JS parse time, after load, to get to interactive for your users. #ChromeDevSummit

    • 0
    • 1
  • All of this is the L, load, of Rail. Getting to interactive is hard, slow. #ChromeDevSummit

    • 0
    • 0
  • Network takeaways for increasing performance #ChromeDevSummit

    • 0
    • 0
  • HTTP/2 push plus service workers gives benefits of first load push w/o most downfalls of cache #ChromeDevSummit

    • 1
    • 4
  • Lazy loading makes for last discovery documents, which increases download times. preload helps minimize this #ChromeDevSummit

    • 0
    • 0
  • Use rel=preload to hint to browsers that link tags should be grabbed as they’ll be needed #ChromeDevSummit

    • 1
    • 1
  • The critical rendering path: what it takes to paint (not interactive) #ChromeDevSummit

    • 0
    • 0
  • The average load time on mobile sites is 19s #ChromeDevSummit

    • 0
    • 0
  • The mobile web is no longer a subset of the web. It is the web. @samccone #ChromeDevSummit

    • 0
    • 1
  • istlsfastyet.com by @igrigorik #ChromeDevSummit

    • 0
    • 3
  • If I can’t interact with your app, beyond scrolling, in under 1s, you’ve failed. #ChromeDevSummit

    • 0
    • 0
  • “If you are using today’s framework with naive implementations, you are failing by default” - @slightlylate #ChromeDevSummit

    • 0
    • 0
  • Tools and techniques brought over from desktop era are hurting us. #ChromeDevSummit

    • 0
    • 0
  • “A 4G user isn’t a 4G user most of the time” - @igrigorik #ChromeDevSummit

    • 0
    • 0
  • Mobile networks are actually getting slower! #ChromeDevSummit

    • 1
    • 2
  • Mobile networks hate you. Mobile networks basically operate the opposite of how TCP was designed #ChromeDevSummit

    • 0
    • 1
  • Turns out flash isn’t always flash. Chip consolidation and low parallelism make for slow perf. Think spinning disks #ChromeDevSummit

    • 0
    • 0
  • The web is not optimized to work how mobile devices are optimized to run. #ChromeDevSummit

    • 0
    • 0
  • Thanks to power and thermal constraints, a large amount of the silicon in our phone is unused #ChromeDevSummit

    • 0
    • 0
  • Mobile phones don’t run a fast as desktops despite similar advertised speeds because they can’t burn your hand. #ChromeDevSummit

    • 0
    • 0
  • Optimize the motion mark benchmark on your phone by adding an ice pack! #ChromeDevSummit

    • 0
    • 1
  • The $700 iPhone in your pocket isn’t what the next billion people are going to buy when they come online #ChromeDevSummit

    • 0
    • 0
  • “The truth is in the (real device) trace” - @slightlylate #ChromeDevSummit

    • 0
    • 1
  • “Traces from real mobile devices are a harsh master” - @slightlylate #ChromeDevSummit

    • 0
    • 0
  • Why are our tools slow by default? Why don’t we fully get the constrains of the mobile web? #ChromeDevSummit

    • 0
    • 0