The only reason AMP matters is because Google was heavily pushing it and for awhile restricted the top search result carousel to AMP pages. This goal could far more easily have been satisfied by a policy which set limits for time-to-render and total transfer rather than dictating usage of a proprietary framework which often makes performance worse (you need a 100KB of JavaScript to finish running before an AMP page isn't blank).
What actually made Google try it is that it gives them control over the advertising system. Performance was the pretext they used to protect their main source of revenue.
* It's clearly driven by a biased entity (Google)
* It doesn't actually directly prioritize page speed
* It breaks websites
You probably meant it the other way round?
I'm really torn on AMP to be honest. I'm morally and technically opposed to it, but... the experience is often dramatically better than what I would have gotten without it.
TFA is just stating that you don't need handcuffs to behave well. You can optimise your site without AMP.
Now, I don't know whether that's true, but supposing that it's, the post you're responding to raises an important point. If AMP doesn't inherently limit bloat, maybe it's only a matter of time before AMP pages are all bloated crap.
Or don't, and you'd never have the problem in the first place. The problem with bloat IMO is that clients at all support it. Thankfully there are a lot of browser extensions for generous content blocking that can make the user experience passable.
Exactly. Nothing stops you from following them in the regular Web
That's why you can't have a fast news site without it - because new site owners won't follow the rules needed to make their site fast unless they get something in return other than speed. Only AMP gives that.
If Google based is lightning bolt etc. on measured page speed instead then yes you might not need AMP. But they don't.
But they do?
https://searchengineland.com/google-speed-update-page-speed-...
When I load this AMP page [1] with an empty cache, Dev Tools show that 3.3 Mb of files are loaded [2]. Also, the page contains lots of errors [3]. This page contains ads, analytics and even a video that you have mentioned in your comment.
After loading, every 10 seconds a HTTP2 request to cloudapi.imrworldwide.com is sent even if the page is in the background.
AMP looks more like an internal Google standard for integrating websites into search results. The spec contains a lot of restrictions like these: you MUST include a 12 000-line JS script from Google ( https://cdn.ampproject.org/v0.js ) into every AMP page, you MAY use only components made by Google and even custom JS template engine made by Google. If you are an ad network then you have to make negiotiations with Google, your competitor, to be included into the whitelist. There are lot of whitelists: list of sites that can provide fonts, list of sites that can add widgets to AMP pages.
Here is one example of such conditions [4]:
> In order to qualify for inclusion, an extended component that integrates a third-party service must generally meet the notability requirements of the English Wikipedia, and is in common use in Internet publishing. As a rough rule of thumb, it should be used or requested by 5% of the top 10,000 websites as noted on builtwith.com, or already integrated into oEmbed.
If you are a small business, you are not welcome.
[1] https://amp.theguardian.com/us-news/commentisfree/2016/feb/1...
[4] https://github.com/ampproject/amphtml/blob/master/3p/README....
Part of the third-party bloatware problem on the web is us, users who aren't willing to pay for content
> The truth probably is that most websites would fail if users had to pay for them.
I agree with you here, but the implication of this is that if the user isn't willing to pay for it, and ads aren't enough to sustain the business, maybe they should not be in that particular business.
Or, they could try to rise to the challenge and build a brand people are willing to pay for. The Guardian in the UK recently hit a million paying digital subscribers, so it's certainly not impossible. Most sites do not need a million subscribers to make payroll.
Try a random article page like https://edition.cnn.com/2018/12/07/tech/australia-encryption...
I refreshed a few times, scrolling to the bottom of the page each time. According to Chrome dev tools even without a video playing between 6 MB and 21 MB was transferred just for me to scroll to the bottom of the page.
That's why I view other initiatives by Google such as https://web.dev [1] laughable at best.
[1] Is a rehash of what has been in their docs for ages: https://developers.google.com/web/fundamentals/performance/w...
Literally nothing has ever achieved that, and it likely never will, it's also no AMP's job, AMP's job is to be a workaround for that systemic issue.
Oh. And ads. It's always about the ads.
They don't even attempt to hide it, really. Right there on AMP's page (emphasis mine):
--- quote ---
The project enables the creation of websites and ads that are...
What AMP Provides
Higher Performance and Engagement
....
Flexibility and Results
Publishers and advertisers can decide how to present their content and what technology vendors to use, all while maintaining and improving key performance indicators.
...
More than 1.5B AMP pages have been published to date and 100+ leading analytics, ad tech and CMS providers support the AMP format.
--- end quote ---
https://www.ampproject.org/ (desktop version is AMP-ified too).
PLEASE go browse a bunch of non-AMP media sites with adblocker off. 500kb is TINY by comparison to what is out there outside of AMP.
By the time you've loaded CNN's AMP page, you'll have loaded at least 4 MB: ~2 MB of AMP prefetching done on Google's search results page and another ~2.2 MB on the AMP page itself.
If Google adhered to its own page performance standards, as outlined here: https://developers.google.com/web/fundamentals/performance/w..., CNN's AMP page would be demoted in search results. However, since its AMP, it gets put front and center in search carousel.
Same goes for every single other AMP page.
Disagree.
The most important feature of AMP is that it makes it impossible to add the kind of bloated crap that causes poor performance on something like a large media company website.
Something like a news website likely has 2-4+ analytics integrations, and a similar number of ad provider integrations.
Your staff want to use google analytics so that goes in. Your display ad provider (ads appearing in the page around articles) uses some other analytics provider so they have to go in. You want video ads so another ad provider who requires a video specific analytics provider goes in. Site rankings produced by someone or other are important to get direct ad sales so their required analytics integration goes in. Then someone in sales signs some deal to add a third party widget to your homepage so that goes in.
All of this happens over the protestations of the developers. People may literally quit over these integrations but their replacement will implement it.
Turn off your ad blocker, go to a news site, watch the network tab and despair.
AMP makes that crap near enough to impossible that the developers can convince the sales team and management that it simply cannot be done.