Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

WordPress Sites Now Support Google’s AMP to Make Mobile Pages Load Faster

techcrunch.com

Post reply on HN
Print view View original

31–40 of 52 posts

Re: WordPress Sites Now Support Google’s AMP to Make Mobile Pages Load Faster

#31

Post by troyvit »

I'm curious what long term ad click rates are going to be for publishers that use AMP. The user experience is very reader-centric. When you do a search and click on an AMP-enabled page (at the top of the search results) you can then swipe left and scroll to the next AMP-enabled page. It's a strong incentive to just read the headline of an article then swipe away. This is great for readers but bad for publishers since they'll get fewer clicks and less time spent on the site from users who come from google. For those of us who just skim the headlines we'll never even see an ad.

google search will funnel users to amp-enabled pages, so anybody /not/ on the amp train will suffer. In that way it is a walled garden. It's google's version of becoming a portal.

How does google make money off of this?

Re: WordPress Sites Now Support Google’s AMP to Make Mobile Pages Load Faster

#32

Post by josefresco »

currysausage wrote: post #21
krapp wrote: post #11

Earlier quoted context omitted.

I would say in that case, the administrator who didn't properly configure their theme and plugins is "schizophrenic."

Most administrators are lazy. If you write software for thousands or millions of users, sane defaults are a must. I find it useful to keep Saint-Exupéry in mind: "It seems that perfection is attained not when there is nothing more to add, but when there is nothing more to remove." Let's look at the first lines of WordPress's default template: Why bother with xmlns if it's not well-formed XML anyway? Why dir and lang…

First 3 lines of Twenty Sixteen are:

I checked back to Twenty Fourteen and didn't see the lines you referenced. Regardless, it's a silly argument, the default themes are "reference" themes, meant to show off all the features WordPress offers and of course don't represent all WP themes.

Re: WordPress Sites Now Support Google’s AMP to Make Mobile Pages Load Faster

#34

Post by busterarm »

donohoe wrote: post #6

No, your WP site supports AMP if you haven't bothered to do anything custom and don't care about anything other than standard design.... in which case you have work ahead of you.

Pretty much.

I develop for a dozen or more totally custom Wordpress sites for my job and the effect this will have on us is precisely zero.

More importantly, this is a band-aid fix for the problem.

Re: WordPress Sites Now Support Google’s AMP to Make Mobile Pages Load Faster

#35

Post by currysausage »

nissehulth wrote: post #28
currysausage wrote: post #21

Earlier quoted context omitted.

Most administrators are lazy. If you write software for thousands or millions of users, sane defaults are a must. I find it useful to keep Saint-Exupéry in mind: "It seems that perfection is attained not when there is nothing more to add, but when there is nothing more to remove." Let's look at the first lines of WordPress's default template: Why bother with xmlns if it's not well-formed XML anyway? Why dir and lang…

What "default template" would that be? As for the "lang" attribute, it is set to the language chosen when WordPress was installed.

Oops, sorry, I was looking at the HTML of the theme previewer instead of the theme itself. With regard to WordPress, only my "XHTML friends network" point remains valid. Concerning web development in general, I have seen way too much cargo cult boilerplate, too many hardcoded lang attributes, etc.

Re: WordPress Sites Now Support Google’s AMP to Make Mobile Pages Load Faster

#36

Post by wanda »

troyvit wrote: post #31

I'm curious what long term ad click rates are going to be for publishers that use AMP. The user experience is very reader-centric. When you do a search and click on an AMP-enabled page (at the top of the search results) you can then swipe left and scroll to the next AMP-enabled page. It's a strong incentive to just read the headline of an article then swipe away. This is great for readers but bad for publishers since…

> How does Google profit from this?

Isn't AMP intended to compete with the likes of Facebook Instant Pages?

At the same time, Google thrives by returning high quality search results. It also depends heavily on web over native. For the web to stay relevant on mobile, it needs to meet some minimum expectations met by native experiences.

I frequently find fault with the websites I arrive at through Google because of shitty performance and irritatingly obtrusive advertising. There's more to mobile friendliness than a responsive CSS grid system and publishers need to realise that.

Re: WordPress Sites Now Support Google’s AMP to Make Mobile Pages Load Faster

#37

Post by Zikes »

callahad wrote: post #25
Zikes wrote: post #17

Earlier quoted context omitted.

The project is open source and open to contributions from anyone. Every single time this comes up the project contributors have said that they will gladly modify to support any network they can. They're also constantly developing new components to fill in the gaps for other embeddable services. You want ? Submit a PR! Open an issue! It's open source! And please, please tell me what's wrong with using e.g. ? It's just…

> The project is open source and open to contributions from anyone. The project is exclusively governed by three Google employees, listed at https://github.com/ampproject/amphtml/blob/master/GOVERNANCE... , all contributions are at their discretion. All contributors must sign a legally binding licensing agreement with Google which includes a patent grant, per https://github.com/ampproject/amphtml/blob/master/CONTRIBU…

I don't see what makes it different from any other open source project. Of course it's going to have technical leads and core committers, it's not like you can go force a PR merge on jQuery trunk any time you please. I'm aghast that you would even suggest such a thing.

And CLA's aren't fun, but they're hardly new, either.[1]

If you don't like that it's Google, that's fine, but at least be honest with yourself about it. But unless you've submitted a PR or can cite a PR (on any Google OSS repo at all) that they've rejected purely on the basis that Google is somehow doing wrong by the developers, then what are we even talking about?

[1] https://en.wikipedia.org/wiki/Contributor_License_Agreement#...

Re: WordPress Sites Now Support Google’s AMP to Make Mobile Pages Load Faster

#38

Post by Zikes »

fareesh wrote: post #30
Zikes wrote: post #12

Earlier quoted context omitted.

Can you elaborate? From what I can tell, AMP makes use of on-demand resource loading, which HTTP/2 prefers over bundled resources thanks to multiplexing.

From what I understood, there are a few contradictions like splitting up assets (preferable in HTTP/2) as opposed to concatenating/merging them (preferable in AMP). Perhaps I misunderstood

AMP encourages you to keep your assets separated, so you only load the bits you need. If a page is going to use you'll have to include the appropriate script tag for that component in the page, for example.

Re: WordPress Sites Now Support Google’s AMP to Make Mobile Pages Load Faster

#39

Post by CM30 »

ck2 wrote: post #7

WordPress is schizophrenic Oh hey let's load up your webpages with all this cr*p by default, tons of javascript, css, external files, fonts, headers, footers useless markup. Oh hey, let's use this plugin to strip all that out. How about not putting it in there in the first place.

A large portion of said code comes from themes and plugins. Especially the latter, which seem to use (abuse) wp_enqueue_script and wp_enqueue_style like it's going out of fashion.

A significant amount of WordPress related overhead would disappear if developers would keep resources to a minimum and provide a way to turn them off without writing additional code. Or if there was some built in system that tried to bundle together the CSS and JS files.

Re: WordPress Sites Now Support Google’s AMP to Make Mobile Pages Load Faster

#40

Post by rezashirazian »

troyvit wrote: post #31

I'm curious what long term ad click rates are going to be for publishers that use AMP. The user experience is very reader-centric. When you do a search and click on an AMP-enabled page (at the top of the search results) you can then swipe left and scroll to the next AMP-enabled page. It's a strong incentive to just read the headline of an article then swipe away. This is great for readers but bad for publishers since…

Don't users already get to see the article's headlines in Google search results before clicking into the site?
Post reply on HN