Sam Richard
@Snugug
BBQ lead, ChromeOS DevRel. Mostly food, sometimes design and development, especially for the web. 7008px tall. He/him.
An archive of my Twitter timeline up until I moved to Mastodon. You can find me there at @[email protected]
If I can’t interact with your app, beyond scrolling, in under 1s, you’ve failed. #ChromeDevSummit
istlsfastyet.com by @igrigorik #ChromeDevSummit
The mobile web is no longer a subset of the web. It is the web. @samccone #ChromeDevSummit
The average load time on mobile sites is 19s #ChromeDevSummit
The critical rendering path: what it takes to paint (not interactive) #ChromeDevSummit
Use rel=preload to hint to browsers that link tags should be grabbed as they’ll be needed #ChromeDevSummit
Lazy loading makes for last discovery documents, which increases download times. preload helps minimize this #ChromeDevSummit
HTTP/2 push plus service workers gives benefits of first load push w/o most downfalls of cache #ChromeDevSummit
Network takeaways for increasing performance #ChromeDevSummit
All of this is the L, load, of Rail. Getting to interactive is hard, slow. #ChromeDevSummit
JS parse time, after load, to get to interactive for your users. #ChromeDevSummit
V8 internals, like parse and complie time, available in Canary dev tools! #ChromeDevSummit
Test on real devices and networks, optimize network utilization, ship smallest amount of JS possible #ChromeDevSummit
Favorite talks from Day 1 #ChromeDevSummit m.youtube.com/watch?v=4bZvq3nodf4 m.youtube.com/watch?v=HF1luRD4Qmk m.youtube.com/watch?feature=youtu.be&v=3tb-1MWg44Y m.youtube.com/watch?v=X8EQSy-ajo4
Housing Go’s metrics improvements moving to PWAs #ChromeDevSummit
Impacts on server side rendering. Should we be surprised? #ChromeDevSummit
First paint vs first meaningful paint #ChromeDevSummit
Performance impact on second load from service workers #ChromeDevSummit
Housing’s perf monitoring in their PR comments medium.com/engineering-housing/continuous-integration-using-webpagetest-and-webpack-1f4465d95405#.mppytr7gc #ChromeDevSummit
Average load time for @lyft PWA is faster than their native apps on modern device & shipped w/4x less engineers in 1 month #ChromeDevSummit
Current saturation of loading on the web. 53% bounce after 3 seconds. All train of thought well lost after 10 #ChromeDevSummit
Fast is not the default for most libraries and frameworks, but @addyosmani says: #ChromeDevSummit
Key points in loading a web application or site #ChromeDevSummit
Time to interactive, <5s on 3G real device, <2s with service worker #ChromeDevSummit
Configuring Webpack #ChromeDevSummit
Average React app per from @addyosmani survey #ChromeDevSummit
Ship minimal functional script to your users. #ChromeDevSummit
Parse and compile time of 1MB (after gzip) of JS without download time #ChromeDevSummit
Test on real devices and real networks. No substitute. #ChromeDevSummit
Less code, loaded better, helps everyone. #ChromeDevSummit
The PRPL pattern for improving time to interactive. #ChromeDevSummit
Code splitting in not panacea. Current tooling doesn’t put performance in your face. #WhatsInYourBundle #ChromeDevSummit
Webpack PoC from @addyosmani to put perf in your face when compiling. addyosmani/793126424253075456 #ChromeDevSummit
Preact: drop in replacement for React and super tiny. Faster time to interactive too github.com/developit/preact #ChromeDevSummit
Network as an enhancement with service workers #ChromeDevSummit
Target everyone. Progressive enhancement enables you to do so. #ChromeDevSummit
Uncanny valley on the web: users can see content and scroll around, but can’t interact because all JS hasn’t loaded #ChromeDevSummit
PRPL in practice: waterfalls before and after #ChromeDevSummit
Business impact for @Flipkart from adopting PWAs #ChromeDevSummit
All of the awesome code @NASA is working on! code.nasa.gov #ChromeDevSummit
Best practices should be automated. #ChromeDevSummit
code.nada.gov is a PWA built with Polymer App Toolbox. And OSS! polymer-project.org/1.0/toolbox github.com/nasa/code-nasa-gov #ChromeDevSummit
Let’s Perf The Web Forward #ChromeDevSummit
github.com/GoogleChrome/sw-toolbox and github.com/GoogleChrome/sw-precache to help simplify writing and maintaining service workers #ChromeDevSummit
@IBMFrontend at #ChromeDevSummit
Client storage is the largest loading perf win in all browsers #ChromeDevSummit
Cost of actually using the network docs.google.com/a/snug.ug/document/d/1f2tcvW72A9haFkCNsVhKgi1iteNrCRHYA7Y_uIautl4/mobilebasic #ChromeDevSummit
Sad so many examples are being given via framework code. 3 lines of framework code doesn’t mean anything to complexity #ChromeDevSummit
Browser storage quotas per domain #ChromeDevSummit
Reasoning about browser storage and when domains get evicted #ChromeDevSummit
V8 mission statement #ChromeDevSummit
History of measuring performance #ChromeDevSummit
Real web page runtime breakdowns in V8 #ChromeDevSummit
Status of Service Workers today #ChromeDevSummit
Server render vs single page app. Missing here is that the critical rendering path is at end of render (green) #ChromeDevSummit
Server render provides gradual render, single page apps break that. When streams land, that will minimized #ChromeDevSummit
Server rendered pages can often be faster than single page apps. SPAs need everything before they render, slowing them #ChromeDevSummit
Progressive Web App does not mean Single Page App #ChromeDevSummit
You don’t need to wait to add PWA functionality to your site. Leverage progressive enhancement and you can start today! #ChromeDevSummit
Automatically generate a web manifest from your rendered HTML webmanife.st #ChromeDevSummit
A bunch of preprocessor available as web workers. Very cool. github.com/patrickkettner/WebWorkerPreProcessor #ChromeDevSummit
Link to all the goodies @jaffathecake talked about jaffathecake/797235127835246592 #ChromeDevSummit jaffathecake/797235023673892864
The CSS Houdini slides from the #ChromeDevSummit breakout. Lots of great coming here. DasSurma/797250746034991104
SLICE the web.
Secure Linkable Indexable Composable Ephemeral
#ChromeDevSummit
Or its the web SAD NUCLEAR MICE #ChromeDevSummit
Day 2 starts! #ChromeDevSummit
