2 ms·
Amp is not about making your site fast but about making sure that sites aggregated in e.g. Google News are all predictably fast by constraining what they can do
by jillesvangurp 8y ago
Amp is not about making your site fast but about making sure that sites aggregated in e.g. Google News are all predictably fast by constraining what they can do. It's not about making the individual sites fast but making sure that none of them are needlessly slow by imposing constraints.
Similarly PWA is also not about performance but about adding metadata that phones and browsers can use to treat the site like an app by e.g. giving it an icon in an app folder. You couldn't do this before, now you can. Before people were doing silly things like packaging up websites as apps and putting them in the app store just so they could their own cute little icon in somebody's app folder. Now they don't have to do that and the install/discovery is a bit smoother as well (easier discovery, less steps, less users lost).
- blablabla123 8y agoNo idea how Amp actually works, I always thought that one component about it was acting like a CDN for common frameworks. PWAs are much easier to tune for global performance though if you have a tight budget. The app doesn't have to talk much to a Backend server and (down)loading can be tuned by using a CDN.
- jjulius 8y ago>... but making sure that none of them are needlessly slow by imposing constraints. Anecdotally, AMP sites always load a bit slower for me. The page will sit blank for a few seconds before finally dumping all of the content at once, as opposed to loading text immediately while it takes a moment to load the rest of the content that has a higher file-size. Without AMP, I can start reading a page before it's done loading. With AMP, especially on a desktop, I'm often stuck staring at a white screen for 15-20 seconds before anything shows up. I often find myself trying to cut the "amp" bit out of the URL to see if I can get to the original page. It's frustrating, and it is a big part of why I'm considering dumping Google as a search engine. That's just my experience, though - YMMV.
- ayoisaiah 8y agoAMP on the desktop? Don't think I've seen that before. I've only seen AMP links on mobile and I don't think it's returned in desktop search results
- jjulius 8y agoYou're correct - Google search results don't return AMP links on desktops, but that doesn't stop me from stumbling upon them. If you come across an article you want to share from your mobile device, and it's an AMP link, it's the AMP URL that gets shared if you post it on sites like HN, FB or Reddit. If I'm browsing those pages from my desktop, clicking that link almost never redirects me to the "original" page, but loads the AMP page in the desktop browser. Sometimes getting around that is as easy as cutting out "/amp/" from the URL, other times it's a totally different URL and I'm stuck staring at a blank page for 30 seconds before it either loads, I just give up or I Google the headline/title and try to find the original page. Forced AMP results on mobile devices also make it difficult to get to certain pages when I want them. Take Eater's 38 lists[1] that they put together. If I'm on my phone and want to find a restaurant from that list in a particular location (say if I'm out of the house and want restaurants near me), then the AMP result returns a page that doesn't include the map, only a list, which isn't very helpful. In order to get to the map, I either need to go to Eater.com and manually find it, or use something like Bing to search for it. I know that the purpose of AMP is to not load the map in an effort to increase speed, but in that instance the map is exactly what I want and AMP makes it harder to get to. I'm not saying AMP doesn't have its benefits, but its inconveniences have outweighed them, in my experience. [1]https://sf.eater.com/maps/best-restaurants-san-francisco-38 https://sf.eater.com/maps/best-restaurants-san-francisco-38
- bitpush 8y agoSounds like you have a rogue extension blocking render