David BlumeSince my old "New Tab" extension for Chrome was calling out to doubleclick.net, I decided to just use my own. Google's PageSpeed tools suggests that my new page is nearly 100% optimized (it could still eliminate render-blocking CSS).
I could blindly listen to the CSS complaint, or realize that it's 100% optimized for me. It's my desktop Chrome browser "New tab" page, so that's all that matters. No iOS Safari compatibility required.
It loads in 25ms. (Ha, ha. Yep, that's all cache. So you'd think it's a cheat, except that it's explicit. I set Cache-Control explicitly in my .htaccess.) About 99.9% of the time, it'll take less than 50ms to load in real-world use cases.
It uses .webp files, which compared favorably to .gif, .png, and .jpg.
It's optimized for my accessibility requirements. (Space, Tab, and Enter keys have to do what I expect, and the selected item needs to be called out.)
The HTML5 and CSS are as minimized as needed (which is not at all), the charset is specified in the HTTP header, not the document. And the document is compressed over HTTP.
It's co-located on the east coast and the west coast.
And it's easily maintained and updated by me, and I like the separation of CSS and HTML. So the trick to eliminate render-blocking CSS by inlining or deferred loading doesn't buy me a better overall experience.
It'll do. (Until I come back and tweak, which I just can't help. The inability to navigate via hjkl and arrow keys is the first thing killing me.)
I could blindly listen to the CSS complaint, or realize that it's 100% optimized for me. It's my desktop Chrome browser "New tab" page, so that's all that matters. No iOS Safari compatibility required.
It loads in 25ms. (Ha, ha. Yep, that's all cache. So you'd think it's a cheat, except that it's explicit. I set Cache-Control explicitly in my .htaccess.) About 99.9% of the time, it'll take less than 50ms to load in real-world use cases.
It uses .webp files, which compared favorably to .gif, .png, and .jpg.
It's optimized for my accessibility requirements. (Space, Tab, and Enter keys have to do what I expect, and the selected item needs to be called out.)
The HTML5 and CSS are as minimized as needed (which is not at all), the charset is specified in the HTTP header, not the document. And the document is compressed over HTTP.
It's co-located on the east coast and the west coast.
And it's easily maintained and updated by me, and I like the separation of CSS and HTML. So the trick to eliminate render-blocking CSS by inlining or deferred loading doesn't buy me a better overall experience.
It'll do. (Until I come back and tweak, which I just can't help. The inability to navigate via hjkl and arrow keys is the first thing killing me.)