WebPerf Google brings non-news AMP links to its mobile search results

TechCrunch reports that Google is introducing non-news AMP links to mobile search results Google brings non-news AMP links to its mobile search results | TechCrunch

---

@Sunka @RoldanLT @deltahf @Matt might be interested in this. Centmin Mod community forums already rolled out AMP page thread support a while back

i.e. this thread's amp html meta tag

HTML:

<link rel="amphtml" href="https://community.centminmod.com/threads/google-brings-non-news-amp-links-to-its-mobile-search-results.8807/?amp=1">

 

webpagetets.org test run in dulles, VA for cable 1 for this thread in amp html vs non-amp html normal mode

 

interesting Google May Be Stealing Your Mobile Traffic

 

yeah interesting times ahead.. my sites only have <10% mobile traffic right now so probably won't feel it. But some sites are now with major portions of mobile traffic !

 

looks like Cloudflare is taking care of AMP generated pages now too Introducing Accelerated Mobile Links: Making the Mobile Web App-Quick !

 

Yeah that's the main one for me. I hope it does motivate web designers to come up with more AMP like html frameworks that are more focused on page load performance

I like purecss Pure. Centmin Mod 123.09beta01's new index.html design for new nginx vhosts is purecss based https://community.centminmod.com/posts/36843/

 

Looks like AMP is growing Google’s AMP now powers 2B+ mobile pages and 900K domains, loads 2x faster

 

Very indeed

 

interested testing amped pages for this forum for a thread with webpagetest and while amp'd version is smaller is size and overall page load is faster but the initial perceived render time was slower (speedindex) by ~0.26s

• non-amped https://community.centminmod.com/threads/letsencrypt-downtime.11737/
• amped https://community.centminmod.com/threads/letsencrypt-downtime.11737/?amp=1

so perceived page loading speed vs actual page loading speed !

first contentful & meaningful paint metrics and speedindex are the real important factors for perceived page load speed by end users









First Meaningful Paint

 

Anti-Amp Kill Google AMP before it KILLS the web

haha

 

Indeed it is especially for publishers end whether or not the publisher implements AMP or not. If publishers don't implement AMP, then mobile search rankings may end up favouring AMP'd publishers so search ranking wise wouldn't be ideal anyway.

For established existing publishers, would it eventually be a choice between whether to implement AMP and less visitors hit your own site or not implement AMP and have still less visitors hit your own site (due to lower mobile search rankings). For new site publishers starting out in a mobile first world, they would only have an option to use AMP for mobile search rankings and visitor growth and they don't have an established visitor traffic base to build off of. So would need to rely on other non-Google sourced traffic i.e. social medium etc and word of mouth/news.

 

hmm wonder what happens if you setup a server to force a 301 or 302 redirect from Amp'd copy of page to non-Amp ? Guess Google won't consider it an Amp page ?

Also I touched on First Meaningful Paint in comparison page load tests at

here's it explained

 

re-visited amp vs non-amp forum thread comparison from https://community.centminmod.com/th...to-its-mobile-search-results.8807/#post-50034 but this time using Webpagetest Moto G4 Chrome with Emerging Markets 3G 400ms RTT speed profile and same again, perceived visual render time, speedindex and first meaningful paint times are faster on non-amp'd page.

• non-amped https://community.centminmod.com/threads/letsencrypt-downtime.11737/
• amped https://community.centminmod.com/threads/letsencrypt-downtime.11737/?amp=1

Filmstrip view clearly shows faster visual render time for non-amped page