Is there a way to block AMP and load the real page instead?
no
Google AMP Cache, AMP Lite, and the Need for Speed
171–180 of 247 posts
Re: Google AMP Cache, AMP Lite, and the Need for Speed
#172Earlier quoted context omitted.
Would you rather see a fast site with rubbish content, or a slow site with good content? My guess is that some altruistic folks at Google see AMP as a way of offering the best of both worlds. But most of us know that in big business, every good idea gets abused for short term profits.
Why is there any relation to the quality of the content?
The OP said Google aren't doing enough to promote fast sites. My point was that quality is more important than speed.
Re: Google AMP Cache, AMP Lite, and the Need for Speed
#173I hate AMP. Not even kind of, I mean so much I've started using Bing (DuckDuckGo hasn't been so useful for me). Beyond the distasteful navigation hijacking, and often broken or buggy page loading... I think Google throwing its weight around to force publishers to use it is an abusive use of power. I also think it's an unnecessary standard since it's nothing more than simple well wittten HTML and CSS. Yes, we should m…
Conversely, I love AMP.
I find it works well, I don't think there's any abuse of power, and I think it's an entirely necessary standard.
Re: Google AMP Cache, AMP Lite, and the Need for Speed
#174Earlier quoted context omitted.
> 5 different JavaScript frameworks This is not the problem. You can easily use i.e. React and some related libs on mobile without slowing down the experience at all. Everything will be fast and responsive, loading times and the mobile site itself (if done right). The problem Google tries to address (and this is a real problem) are the cascaded ad networks on webpages which load hundreds of JS libs once a page is loa…
>> "This is not the problem. You can easily use i.e. React and some related libs on mobile without slowing down the experience at all." Hasn't Facebook proven this to be incorrect. Facebook mobile app was originally just HTML5 & JavaScript. The experience was so slow, they ditched it and instead built a native iOS & Android app. [1] [1] https://techcrunch.com/2012/12/13/facebook-android-faster/
Two more reasons why this comparison is not on point:
- On iOS, the FB App had to make do with a really slow JS engine at the time. IIRC Safari's JS performance was x5 compared to JS performance in apps' web views? This has more to do with how iOS treats apps, rather than how fast web pages in Safari are or were.
- The FB apps were okayish at the time, given that they were web based. If you manage to get your web app to that level, your site is ok. Now add to that the performance gains and browser optimizations of the last 4 years and you get a system that flies. Native apps are still faster and respond quicker to touch, but you cannot hold that against JS web apps.
Re: Google AMP Cache, AMP Lite, and the Need for Speed
#175I hate AMP. Not even kind of, I mean so much I've started using Bing (DuckDuckGo hasn't been so useful for me). Beyond the distasteful navigation hijacking, and often broken or buggy page loading... I think Google throwing its weight around to force publishers to use it is an abusive use of power. I also think it's an unnecessary standard since it's nothing more than simple well wittten HTML and CSS. Yes, we should m…
I switched my default search engine on my phone from Google to DuckDuckGo because I got sick of the growing number AMP links, which I also don't like for all the same reasons you listed. They are a bad reminder of the early days of the mobile internet when lots of websites would automatically redirect you to a terrible 'mobile version'. I certainly want better mobile sites, but not in the form of these AMP pages.
Actually it's even worse nowadays. Mobile-first design by unskilled designers has resulted in an avalanche of websites that are terrible with mobile browsers and even worse with desktop browsers due to extremely low information density. Mobile-first websites usually require much more clicking and scrolling through almost content free pages to browse through content. Lately I've been stunned by the amount of crappy mobile-first websites that display hardly any actual content at all above the fold.
Re: Google AMP Cache, AMP Lite, and the Need for Speed
#176Earlier quoted context omitted.
I switched my default search engine on my phone from Google to DuckDuckGo because I got sick of the growing number AMP links, which I also don't like for all the same reasons you listed. They are a bad reminder of the early days of the mobile internet when lots of websites would automatically redirect you to a terrible 'mobile version'. I certainly want better mobile sites, but not in the form of these AMP pages.
AMP annoys my too, but it hadn't occurred to me to switch to DuckDuckGo. Good idea, just made the change.
It sure would be awesome if Chrome on Android had it available as an option. But, it's Google.
Re: Google AMP Cache, AMP Lite, and the Need for Speed
#177Earlier quoted context omitted.
AMP annoys my too, but it hadn't occurred to me to switch to DuckDuckGo. Good idea, just made the change.
It sure would be awesome if Chrome on Android had it available as an option. But, it's Google.
If you trust APKs from random strangers on the internet, here's my custom Chromium for Android build with DDG support: https://sr.ht/dIQO.apk
Here's the patch that adds it to the list of search providers: https://sr.ht/h4bZ.patch
Re: Google AMP Cache, AMP Lite, and the Need for Speed
#178Re: Google AMP Cache, AMP Lite, and the Need for Speed
#179Earlier quoted context omitted.
Under no circumstances should web browsers be hard-coding special favors to paper over deficiencies in the user experience of Google's news product. The entire idea is insane. Google is just another company on the internet, and should be treated like any other.
SVG was Adobe's open implementation of the ideas of behind Macromedia Flash. It solved a real pain (the lack of vector support on the Web) and has been implemented by all the browsers. Does this upset you? Most of the progress of the web platform is sponsored by companies like Adobe and Google. AMP is a curated subset of web functionality designed to load quickly and be safely cacheable. Like SVG, it's an open attemp…
SVGs are displayed whether or not they're hosted on Adobe's servers.
What other servers are serving AMP pages, (edit: and would benefit from this "cached from " URL bar display logic) other than Google's news product?
Re: Google AMP Cache, AMP Lite, and the Need for Speed
#180Earlier quoted context omitted.
SVG was Adobe's open implementation of the ideas of behind Macromedia Flash. It solved a real pain (the lack of vector support on the Web) and has been implemented by all the browsers. Does this upset you? Most of the progress of the web platform is sponsored by companies like Adobe and Google. AMP is a curated subset of web functionality designed to load quickly and be safely cacheable. Like SVG, it's an open attemp…
SVGs are displayed whether or not they're hosted on Adobe's servers. What other servers are serving AMP pages, (edit: and would benefit from this "cached from " URL bar display logic) other than Google's news product?
All the publishers Google copies the AMP from? Google could just redirect mobile users to that if they wanted, as can every other site linking to a page. If they then also got rid of the requirement of loading the AMP JS from a CDN Google runs, they'd actually have something resembling an open standard...