[kinkrtyavimoodh]

Despite understanding and largely agreeing with the concerns against AMP Cache that get discussed any time an AMP article gets posted on HN, I cannot stress enough on how relieved I feel to see the lightning icon next to a mobile search result, especially on my now aging phone.

Most content websites have become such a massive crapfest of ad-bloat, bad UX, huge page sizes and general usability hell that it's nigh impossible that I'd be able to reach the actual content of a non AMP site in the first 5-10 seconds of clicking on its link. (On my phone that's an additional 1-2 seconds for registering the tap, and 1-2 seconds for navigating to the browser)

My click-throughs to non AMP websites have reduced considerably.

So say what you may, AMP (or FB Instant or its ilk) will prosper until the mobile web experience stops being so crappy.

(Edit: About a decade ago, when mobile browsers were in their infancy and data plans were slow and limited, I distinctly remember using Opera Mini for mobile browsing because it used to pre-render pages on the server and send a very light payload to the phone. This saved you both data costs and made mobile browsing even realistically possible)

[dividuum]

Personally I don't think the idea behind AMP is bad. But the implementation is dangerous as it artificially fragments the web. I guess fewer would oppose AMP if google made some machine verifiable guidelines for "light" webpages that would earn them this "icon". Linked from the "fat" page by some "link" meta tag.

[godot]

>if google made some machine verifiable guidelines for "light" webpages that would earn them this "icon". Linked from the "fat" page by some "link" meta tag.

That is exactly what AMP is; with the exception (a huge one, I know) that Google also then caches the page on their server and serves it from a google.com host.

[avaer]

For Google, the hijack is the prime feature; AMP is the PR vehicle that makes it swallow.

AMP could have been done without the huge exception, but then Google couldn't profit from it.

[claudiulodro]

The fast, non-blocking content loading is the main feature. I took a radical path when developing my site and made it AMP-first. Instead of having an AMP version of each page, every page is its own AMP version because it's an AMP page.

Even served from my cheapo shared web host and not Google's AMP cache, I have pretty-much instant loading of all pages: http://multithreaded.link/2017/08/lyft-customer-acquisition-...

It's a good framework for building super fast pages. I will admit it's a little riskier to build a site on top of technology a large company owns, but this is a risk that you also have when you use React or other frameworks.

[smt88]

> this is a risk that you also have when you use React or other frameworks

React isn't a good analogy. When you use React, you can get 100% of the value of the library, even if Facebook disappears overnight.

By contrast, much of the benefit of AMP is the caching aspect, which relies on Google.

[stephenr]

> The fast, non-blocking content loading is the main feature.

You don't need requires-js-to-render markup or a cache operated by a privacy whoring ad company to make a page load quickly.

Edit: also, comparing to react or whatever js framework is like saying "look at my new cast iron shoes, they're so much lighter than those old lead ones".

[kmoe]

Your "About", "Contact", and "Privacy Policy" footer links don't work (they go to "#").

[claudiulodro]

Yeah sorry about that! I just launched it recently so I'm still getting everything going. :)

[an27]

Nice, on FF I get a white page because Google domains lurk in my hosts file. I suppose I'm not your target audience.

[leeoniya]

> For Google, the hijack is the prime feature; AMP is the PR vehicle that makes it swallow.

this is 100% true. yet somehow there are still those who swear this isnt the case. i've ranted about it previously [1].

[1] https://news.ycombinator.com/item?id=14695268

[cobookman]

I think it's also about prefetching amp pages from Google search. You can't do that without the cdn.

Sure google could modify chrome to allow this and not block it. but you'd be asking for even more technical blockers. And you'd have something that only works for a small portion of the web.

[avaer]

Sounds like the perfect use case for a nice standard CORSy web prefetch API that all browsers could implement.

And this would work for at least as much of the web as is currently putting effort into AMP.

[cramforce]

We are thinking about this. The problem is privacy. AMP can pre-render a page from publisher X without publisher X learning that this happened.

This is important for avoiding that you e.g. would suddenly see re-marketing ads for pages that you have never clicked.

[baddox]

Regardless of profit, if Google just made the AMP spec and didn't incentivize publishers to use it, well, no one would use it.

[avaer]

Not saying that's true, but if it is, wouldn't that mean AMP is not a desired product?

I fully support a "faster page spec" that search engines incentivize, just like I support a ranking boost for using HTTPS.

But AMP isn't that; AMP is incentivizing the payment of tribute data to Google under the veneer of a faster page spec, to steer the rhetoric more favorably for the company.

[nine_k]

It's desired by the (non-paying) users, but not necessarily by web publishers. Here the desires of said users and Google align: they both want to see a search result quickly.

[baddox]

> wouldn't that mean AMP is not a desired product?

Well, kind of, in the same way that common-sense lightweight HTML/CSS/JS pages aren't a desired product for the people who make those decisions on publisher websites.

[brianwawok]

I want it as a consumer.

If AMP went away tomorrow I would just browsing on my phone. Ad blockers are not good enough, and I refuse to fight popups and scroll blockers and blah blah blah in 2017.

[notatoad]

>For Google, the hijack is the prime feature

what does google get out of it? The experience is better for users who like fast, lightweight pages, but as far as i can tell there's no tangible direct benefit to google when you load an AMP page. The only benefit to google is if their users like the experience and continue to use Google search so they can access AMP-cached pages. If users don't like AMP, google gets no benefit.

or am i missing something?

[avaer]

Google's entire business model is tracking users as they use the internet in order to target ads.

Every AMPed page is contributing work towards improving the effectiveness and appeal of Google's product (selling ads), by adding data to the targeting algorithms.

If every piece of content on the internet is tracked -- through full UX hijack on Google's infrastructure -- that might be a trillion dollar holy grail.

[tyingq]

The ux hijack will progress over time as well. Google knows how to boil users slowly so they never notice the heat.

AMP carousel pages have some subtle capture features that regular AMP pages don't. They will add more, then slowly move them to the regular AMP pages over time.

[notatoad]

you think google doesn't already track the links you click on the SERP? they aren't learning anything new by putting a tracking code on the page that link takes you to.

[fastball]

I don't understand why this matters though?

Google is tracking you. If you don't want to be data-mined, you shouldn't be using Google. If you are using Google, it means you don't mind being tracked. It means you are placing the convenience that Google provides above your concerns about what a faceless corporation can do with your data. If you don't mind being tracked, AMP is not a problem.

I understand how you could dislike Google. I don't understand how you could dislike AMP specifically, but not necessarily google.

[shimon_e]

Fact is, Google would already have a complete profile on you for advertising purposes even without AMP. They offer more than enough services that track you that they don't really need AMP for tracking purposes.

[notyourwork]

How does google profit from serving these pages opposed to original content creator?

[the8472]

> That is exactly what AMP is

Except that there is mandatory 3rd-party javascript that needs to be loaded just to get it to render. That doesn't make sense if it really just were about lean pages

[ninkendo]

That's an extremely disingenuous statement. It's not just "a [huge] exception", it's the entire basis for google's strategy. AMP isn't just a standard for how to construct a website, it's a way for external entities like Google to host your site directly inside their site, so that they have ever-increasing access to your browsing behavior. Now Google doesn't just know what results you clicked on, but what links you're following inside those results, how long you stay on the pages, etc.

Facebook, twitter, reddit, etc already utilize similar techniques on their mobile apps to make it so "web links" you click just keep you in the app.

But the web (as in, not bespoke mobile apps, but what you get in a general-purpose web browser) is supposed to be decentralized and resistant to any one entity owning the end-to-end experience.

I'm aware that any other entity (like Bing for instance) could do the same thing that Google does, and that the AMP standard isn't what's at fault here, but there should be no doubt as to Google's motives.

[grey-area]

So, that's not what AMP is. There's a reason google don't drop the incredibly unpopular hijacking of content, and it's not to do with edge caching, but control.

[kuschku]

And modifies the pages UI.

And forces you to load content from Google’s CDN.

And so on.

[stephenr]

You don't need new js-required-to-render markup to make a page lightweight

[rhizome]

With Google I can never relax to think that something new will be a good thing for me, a user, but their "make mobile viewable" (or whatever the message is) reformatter for sites that still have 10 year old CSS could certainly result in some sort of signal displayed in search results. A mobile-viewability indicator, perhaps. I dunno, it sounds kinda hokey when I write it out like that, but I have to think they're going to productize it at some point.

[stephenr]

It's pretty easy to detect the number of external scripts, media objects, fonts and images a page attempts to load.

But that wouldn't give google control and importantly, a sure-fire run around same-origin privacy protections.

[mikeytown2]

>if google made some machine verifiable guidelines for "light" webpages that would earn them this "icon".

If you get a score above 95 or (X) on google page speed insights that might be a metric that everyone can agree on.

[BoorishBears]

I can't for the life of me understand why the icon couldn't just be a link to the AMP version (or be located near the current cached link is), and the link would link to the normal page

[dimal]

The crazy thing is that content websites insist they need dozens of ad and analytics libraries on every page because otherwise, how would they monetize their site? So, they create a crappy experience, realize it's crappy, then switch to AMP, getting rid of all the libraries they supposedly "needed". They could just remove the cruft themselves and cut out the middleman.

[lllr_finger]

In reality, they get scared of losing traffic by not adapting AMP, decide to implement it, and then flip out over how restrictive it is without understanding how they caused this situation.

It's all driven by money, and unfortunately AMP and bloated pages make money - fast, sexy pages without AMP do not.

[hdhzy]

> Most content websites have become such a massive crapfest of ad-bloat, bad UX, huge page sizes and general usability hell that it's nigh impossible that I'd be able to reach the actual content of a non AMP site in the first 5-10 seconds of clicking on its link.

Or just use Firefox for Android with uBlock extension and Reader Mode. No, it's not perfect but doesn't require parallel internet (Google's) to function.

I hope AMP meets the same fate as other Google's "works best in chrome" techniques such as PNaCl. Maybe we'll get something standardized out of it like PNaCl was replaced with WebAssembly?

[sbov]

There's ways Google could fix this without AMP, such as factoring in total page weight when ranking mobile search results.

[rolodato]

It's not as simple as total page weight - latency and server throughput are also important. AMP pages are likely served from a fast global cache with low latency from all over the world.

[colordrops]

Are you saying that global latency is not measurable?

[nallerooth]

As mentioned by others, page weight is a bit tricky. However, Google has this thing called "Google Page Speed" and that would actually be a pretty good indication on the performance part.

Then again - any site with good performance can be made unusable by crazy marketing people who wants [insert tracking tool here] on every page or similar.

[dazc]

Absolutely this.

[anon1385]

I think that the fact AMP sites are faster than the average site is exactly what makes it so dangerous. Obviously there are plenty of sites out there that aren't bloated up with javascript and ads, but Google doesn't offer any way to identify that in the search results. The only reliable indicator of site speed is the Google AMP Cache logo. So naturally users will consciously or otherwise favour clicking results with the Google AMP logo. That drives more traffic to those sites, improves their search ranking etc. A non-GoogleAMPCache site could be incredibly lean and fast but it will still lose out to the Google AMP Cache hosted sites in terms of traffic and ranking. The only way to compete is to use Google's proprietary markup standard and cede hosting of your site to Google.

[andy_ppp]

AMP isn’t that much faster, it’s still html, css and gobloads ofv js. The real speed increase is Google SERP sucking up your data plan and prerenders a whole loads of stuff without asking.

[vanadium]

Well, here's an interesting data point to dig through insofar as AMP performance is concerned: http://www.webpagetest.org/result/170816_7R_b596415003dabf34...

Average Guardian article.

[sdoering]

So 80% is js bloat? How does that optimizes for my experience?

[vanadium]

But it's _their_ bloat.

[owenversteeg]

I completely agree. As a programmer, I don't like it. As a user, I love it. I'm often on a crappy data connection or on an older device, and waiting for non-AMP pages to load is ridiculous. I'd usually choose the 10th search result over the 1st if the 10th is the first AMP one. (Provided that it looks suitable for whatever I was Googling.) It's that significant of an effect.

[PaulHoule]

It would go a long way to the reform of the mobile web if they got rid of all the "pop-in" windows that are hard (and sometimes impossible) to dismiss.

Pop-ins are annoying on the desktop, but close to catastrophic on mobile.

[JetSpiegel]

The same AMP experience can be had with Firefox and uBlock Origin on old Android phones.

[colordrops]

You aren't addressing the issue people have with AMP though. There's no reason Google couldn't boost site rankings and provide the little logo to compliant sitea and still allow the sites to host under their own domain.

[deftturtle]

I just use a content blocker to prevent JS, CSS, fonts, and images on all websites by default. Then if I care about the site, I can change permissions.

Medium.com now loads so fast, as well as other bloated publishers and newspapers. It's amazing how many tabs I can open, and I use so little bandwidth.

I end using my phone's screen reader usually, so I don't care about appearance. Just need good stories in the <html> :)

[techmagus]

Same here. I can load sites with AMP (or its competitors) faster on my low-end to mid-range phones fine, and on a metered Internet connection.

As much as I don't like it on a webmaster / blogger perspective, it does help a lot in getting a wider audience than by only offering a "responsive theme".

[executesorder66]

Why not use Firefox with uBlock Origin addon for your phone?