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

How fast is AMP really?

timkadlec.com

Post reply on HN
Print view View original

81–90 of 167 posts

Re: How fast is AMP really?

#81

Post by JoshMnem »

seanwilson wrote: post #56
JoshMnem wrote: post #46

Earlier quoted context omitted.

> I think I understand what it's trying to do. It's appifying the WWW on Google's domain and allowing them to dictate how sites are monetized. On the most basic level, it isn't motivated by speed.

> On the most basic level, it isn't motivated by speed. So you think Google has no interest in making search results load faster and this factor is just a ploy?

There are employees there who probably buy the idea that it's motivated by speed, but the project wasn't created primarily for speed, just like Chrome wasn't primarily motivated by the need to make a better browser. (Both are about advertising.)

Re: How fast is AMP really?

#82

Post by JoshMnem »

fastball wrote: post #61
JoshMnem wrote: post #46

Earlier quoted context omitted.

> I think I understand what it's trying to do. It's appifying the WWW on Google's domain and allowing them to dictate how sites are monetized. On the most basic level, it isn't motivated by speed.

Fast page loads means a better UX on the web. Better UX on the wide web means people enjoy using Google more. If I'm using Google, it means I want to find something. If Google has encouraged the entire web to be faster, I will find what I'm looking for faster. People using Google and enjoying it is good for Google.

> Fast page loads means a better UX on the web.

Not necessarily. AMP has terrible usability. For people who block 3rd party JS from loading, AMP pages take 8 seconds to load.

AMP will hurt publishers in the long run:

- giant back button to take users back to Google Search instead of deeper into your site

- broken referrers

- bad inbound links (that point to google.com)

- someone else dictates your monetization strategy

- someone else limits how you publish online

- not faster than DIY optimization

- etc. https://www.google.com/search?num=100&q=amp+sucks

Re: How fast is AMP really?

#83

Post by seanwilson »

JoshMnem wrote: post #81
seanwilson wrote: post #56

Earlier quoted context omitted.

> On the most basic level, it isn't motivated by speed. So you think Google has no interest in making search results load faster and this factor is just a ploy?

There are employees there who probably buy the idea that it's motivated by speed, but the project wasn't created primarily for speed, just like Chrome wasn't primarily motivated by the need to make a better browser. (Both are about advertising.)

> There are employees there who probably buy the idea that it's motivated by speed, but the project wasn't created primarily for speed, just like Chrome wasn't primarily motivated by the need to make a better browser

You have evidence of these two claims or you're speculating?

Re: How fast is AMP really?

#84

Post by Sylos »

cptskippy wrote: post #45
Waterluvian wrote: post #40

Earlier quoted context omitted.

Holy crap. The internet on a phone can feel like this?!

It didn't seem that fast to me compared to other sites, then I realized I'm running Firefox with uBlock while the rest of you are probably on Chrome.

This seems to rather be a case where it just happens to be crazy-fast on Chrome, whereas it does not happen to be on Firefox.

Might be Chrome pre-loading content that's behind links, which Firefox doesn't do for security, privacy, battery and not-eating-all-your-RAM-ery reasons.

I tried enabling preloading in about:config, which didn't seem to make a difference, but I'm not sure, if I did that right or if that feature is even functional at the moment. It's an experimental about:config flag after all, not a production feature.

Then again, this very much seems to be the exception on Chrome, too, so it's not exactly a reason to stop enjoying the internet without ads.

Re: How fast is AMP really?

#87

Post by Too »

So nowadays 61 requests per page load is considered an "accelerated" page? Might not be so bad with http2 but still wow. Maybe publishers should start working on that number if they want actually faster web pages.

Re: How fast is AMP really?

#88

Post by yxhuvud »

seanmcdirmid wrote: post #32
user5994461 wrote: post #20

Earlier quoted context omitted.

You must be American then because that's the American format. Different countries and languages have different format of numbers. That's one of the most common issue in internationalization. If you send a bill for a 5,000 dollars service, expect your international customers to send you back five dollars. The comma is broadly interpreted as the decimal separator.

Not just America uses dot as the decimal separator, see: https://en.m.wikipedia.org/wiki/File:DecimalSeparator.svg Blue uses the dot, green uses the comma. By population dot wins (since India and China use the American style).

What that map show is that space wins because otherwise someone is bound to be confused.

Re: How fast is AMP really?

#89

Post by Kalium »

geuis wrote: post #33
lern_too_spel wrote: post #11

A very low quality article. The whole point of AMP is to define a restricted subset of HTML that is safe to prerender and still provide working analytics to the publisher. When you prerender, the advantage of AMP is substantial as it is impossible to beat a user experience of instant, which is why users prefer it and why publishers go through the trouble of implementing two web versions of their web pages (in additio…

AMP is a cancer on search results. The purpose of a search engine is to provide the best links it can to content related to a user’s search. The search engine should not be providing the content of the search result as a primary link. Having a backup cache of the link is fine in case it changes or disappears. It’s the responsibility of the original site to be able to serve its visitors.

You're right! Users are looking for something very specific when they search. Generally, they are looking for a particular bit of information. Sometimes the best way to get that is to click through to someone's site and read an essay.

At other times, well, it's possible that it might be the best experience for the user to have information presented to them immediately. It's definitely negative for people whose entire business model depended on those clicks, though. I understand their pain, fear, and anger.

Re: How fast is AMP really?

#90

Post by colordrops »

colordrops wrote: post #64
Waterluvian wrote: post #54

Earlier quoted context omitted.

On a phone? Last time I tried adblocking on a phone I was super irritated by it. Some proxy setup that never quite worked and felt like it slowed everything down.

Try Brave browser. It's a modified version of Chromium with seemless ad blocking by the co-founder of Mozilla.

Can't edit my post since it's been 3 hours, but I'm very curious why I was downvoted. Was there some negative news around Brave that I missed?
Post reply on HN