Archimedes Trajano

Another approach I can think of is to NOT do anything automatically to determine what should be pushed. Instead let the theme or blog developer do it themselves by having...

Not anymore, I found that it didn't work too well in Chrome. It was actually causing double downloads.

The main problem is Chrome will only "link" the content if it was built from a script rather than the HTML. So `` will double download but setting `.src` via...

I still `preload` a few things on my main portfolio https://trajano.net/ however, since they're all remote resources (i.e. google fonts etc) it won't be server push. Only those that are...

Many issues... it may not be fixed though unless the spec has made it explicit that it should also be for non-scripted resources. So far only script injected resources will...

I think it is more that it is dismissed already regardless I found that we shouldn't try to do guess what needs to be sent automatically and instead rely on...

You cannot push jquery unless you defer loading jquery. It may impact the page speed more if you defer such a critical component. However the interim of doing the link...

Best is to write a small HTML file and see what happens. Basically if you use chrome it will show if it downloads twice in the logs. I am not...

I just created a Gist, the warnings does appear in Chrome 57 http://rawgit.com/trajano/a61654502d4aa6191d742766f87dc5fe/raw/4aaa942f8457513d60fd1a26d953fd847b2aaea2/preload-double-download.html

Be careful with deferring jquery. We may get flash of unstyled content. Which can be prevented by display none and unhiding when document is loaded. At the expense of slower...