google amp feb 24, 2016

http://mediagazer.com/160224/p4#a160224p4

http://mediagazer.com/160223/p28#a160223p28

Publishers are dumb. Publishers create terrible websites. Publishers need Facebook and Google to save them.

A lot of moronic rhetoric will exist about this topic.

http://www.wsj.com/articles/google-starts-including-amp-content-in-mobile-search-results-1456326159

q.
“The feedback from publishers so far has been very enthusiastic. *Everyone is excited to make the Web faster,”* said Dave Besbris, Google’s vice president of engineering. 
q..

The Web or the web is not slow. Browsers on desktops, laptops, tablets, and phones are not the problem.

*Bloated, poorly designed websites are the problem.* And publishers create them.  These stunningly huge article pages bog down old computers and cause slow downloads.

The solution is to create simpler websites. My test site that's using my new formatting app to create static html pages loads fast and works fine on desktop and phone. http://article.soupmode.com/static

My other sites, such as http://maketoledo.com and http://crochet.soupmode.com/, also load fast because the Nginx web server pulls the homepages and the article pages from Memcached. And if the article page was not cached, then my code is accessed, which pulls the content from the MySQL or CouchDB database, and then the content is cached before or after it's sent to the user. A refresh retrieves the newly cached page. But when I create or update an article, that page is cached.

Make the web faster? No. Make your websites leaner. Make your websites reader-friendly instead of reader-hostile.