8 ms·
You Don't Get AMP
- colept 10y agoCleverly leaves out the part where Google siphons your traffic. AMP is the trojan horse and I don't "get" those welcoming it into the gates.
- quarterto 10y agoIf you use Cloudflare as your CDN, is Cloudflare "siphoning your traffic"?
- soared 10y agoDoes cloudflare take users to a webpage that isn't yours with a header with a button that doesn't lead to your site?
- quarterto 10y agoThe page is still yours. You have absolute control over the branding, the analytics, the monetisation. Just because it happens not to be served from your domain doesn't mean it's not yours. Let's also not forget that AMP is actively encouraging alternative caches: Cloudflare Ampersand[1] was announced literally an hour after my post. It's a whitelabelled AMP cache aimed at solving this exact problem. [1]: https://www.cloudflare.com/website-optimization/ampersand/ https://www.cloudflare.com/website-optimization/ampersand/
- soared 10y agoYes you still control most of it. My argument is that the traffic /would/ be going to your actual site (where you aren't limited at all) but now it is going to a google AMP page with strict limitations. Which isn't great, but the big deal is that bar on top that doesn't link to your site. That is so bad for your site and massively increases the bounce rate.
- quarterto 10y agoThat is a sticking point for me. Alternative AMP caches (with alternative UX, e.g. Ampersand generally keeps users on your site when they bounce) go some way towards solving this, but they're not (yet?) first-class ecosystem citizens: > But these are just guidelines, and Google can’t guarantee they’re behaving well, so they’re not first-class citizens. > I’d love for this to be something you could statically verify, just like AMP HTML, so that anybody could add a Cache to the ecosystem and get a lightning bolt on Google search results and Cloudflare links and Twitter Moments™, but I’m pretty sure this reduces to the Halting Problem.
- owebmaster 10y ago> Just because it happens not to be served from your domain doesn't mean it's not yours. This is exactly what means not be yours. It's Google and they lease it to you.
- goodplay 10y agoFor now. AMP is a PROXY/MITM service, with all the perks that come from being such a service. There is nothing stopping google ,or whatever company owns them after they become a Yahoo!, from changing their "policy" to better be aligned with their interests.
- quarterto 10y agoAs soon as Google stops providing value to publishers, they lose their power in the industry. For now, we work with what we have.
- colept 10y ago> As soon as Google stops providing value to publishers, they lose their power in the industry As soon as Google stops providing value to publishers, they are the industry.
- flukus 10y ago> Tap a Top Stories card, and bam, you’re in the article. Takes maybe 100 milliseconds, just at the edge of perception. You can’t do that with a full page load: not on a 3G network, not on a mobile CPU. Yes you can, quite comfortably. Pre rendering is just patching the bloated web, not fixing it. If you want to make the web better focus on less javascript, with noscript on I get AMP like speeds almost everywhere.
- quarterto 10y agoBut that's the point: AMP allows far richer pages than just totally cutting out Javascript. Like it or not, the web is an application platform.
- CaptSpify 10y agoWhat does amp give me that a non-js page can't? Also, applications aren't the target for amp.
- quarterto 10y agoCan you write a carousel without JS? A live blog? Lazy loading images and ads? A stateful e-commerce product page? Have a look through the list of AMP components, you'll be surprised what's possible. https://www.ampproject.org/docs/reference/components https://www.ampproject.org/docs/reference/components
- CaptSpify 10y agoGood examples, but none of that is anything that I want. I'd much prefer small, simple, static pages to any of that. Additionally, they will load faster, and be easier to read. Those things are just trimming pages down to what Google wants, not users.
- quarterto 10y agoAs somebody who has implemented AMP for a major newspaper, these are in fact things that publishers want.
- CaptSpify 10y agoOh, I get AMP just fine. I get that it's a power play by Google. The problem AMP is trying to solve is very real. But instead of trying to fix the problem, Google is using it to take an even greater chunk of the web. No thanks
- quarterto 10y ago> Google gonna Google. They’ve been dangling carrots in front of publishers for twenty-one years.
- CaptSpify 10y agoI don't buy it. If that's true, how come all of the top results I get are slow, heavy bloated sites, yet small, simple, fast sites are ~10 pages deep?
- quarterto 10y agoSure, speed should be a ranking factor, but I'd much rather have a slow site that's relevant than a fast one that isn't.
- CaptSpify 10y agoHow about a relevant page that is fast. We can have the best of both worlds.
- quarterto 10y agoWouldn't that be nice. But Google don't control how relevant or fast something is, they can only decide how to rank them.
- CaptSpify 10y ago... thats my point. This is a problem that Google created. If they would prioritize small, simple, fast sites, and rank them higher, people would make more sites like that. Google is the one pushing slow, bloated sites to the top of the list. Now they are coming in to "fix" the problem that they made.
- owebmaster 10y agoOP: You don't get HTML
- RichardHeart 10y agoIf you let GOOGLE control the browser, OS, search engine, keyboard, maps, and user created video content, what could possibly go wrong?
- webartisan 10y agoAs someone who has developed for mobile web, it can be surprisingly hard to push back on bloat from marketing / seo / analytics teams. I hope this becomes a W3C standard so us developers can show them the finger the next time they want to bring mobile web to a crawl.
- CaptSpify 10y agoDoes Google not have any guidelines that say to keep pages small and fast? Seems like they should have a list of things to keep in mind when looking at search-rankings
- webartisan 10y agoIt does, although only can only assume the effect of performance on search rankings. It's non-tangible metric as far as revenue is concerned.
- CaptSpify 10y agoThen what would be the difference between showing them the AMP standards, and just pointing them to those documents?
- webartisan 10y agoAs someone who has developed for mobile web, it can be surprisingly hard to push back on bloat from marketing / seo / analytics teams. I hope this becomes a W3C standard so us developers can show them the finger the next time they want to bring mobile web to a crawl.
- webartisan 10y agoAs someone who has developed for mobile web, it can be surprisingly hard to push back on bloat from marketing / seo / analytics teams. I hope this becomes a W3C standard so us developers can show them the finger the next time they want to bring mobile web to a crawl.