Definitely true. What you need is less js and more content. My site loads so fast that it even works in a forest where there is only EDGE available.
Neither PWA nor AMP are needed to make a website load fast
151–160 of 225 posts
Re: Neither PWA nor AMP are needed to make a website load fast
#152Earlier quoted context omitted.
> AMP, or something even better, needs to be the default way to build websites. No. We don't need AMP or something else. The existing tools are more than enough. What we need are actual, trained engineers/developers on the platform. The real problem with web performance is that any random guy with questionable or non-existent knowledge thinks he can whip up a website by mixing any library he comes across. That is fin…
This isn't about engineers. This is about businesses. Up until now there apparently hasn't been a business case for fast websites. Fast website costs a lot of money in development time. If a website loads fast enough , nobody wants to invest X amount of dollars to make it somewhat faster. Since AMP sites are prioritized on mobile, there is now a very clear business case for supporting AMP.
Fast sites are significantly cheaper to develop, it's just a case of _not_ adding things, but that's an impossible choice to make when the website for a new channel is entirely not what the company is for.
Re: Neither PWA nor AMP are needed to make a website load fast
#153Earlier quoted context omitted.
Well, fast initial page loads would improve the experience a user gets when they're using a search engine to find an answer, especially if they have to visit multiple websites. For a site like Hackernews though where you probably visit many pages each visit, downloading the same e.g. 50KB of CSS every page is wasteful.
Hackernews has 7KB of css - 2KB with compression. The html for this document is 200kb - 30kb with compression.
I meant hypothetically; sites where most users visits many pages.
Re: Neither PWA nor AMP are needed to make a website load fast
#154I’ve seen many cases where AMP version of an article was slower to load than the regular web version.
Re: Neither PWA nor AMP are needed to make a website load fast
#155Earlier quoted context omitted.
This isn't about engineers. This is about businesses. Up until now there apparently hasn't been a business case for fast websites. Fast website costs a lot of money in development time. If a website loads fast enough , nobody wants to invest X amount of dollars to make it somewhat faster. Since AMP sites are prioritized on mobile, there is now a very clear business case for supporting AMP.
Most people do not work in an Dilbertesque organization filled with pointy haired bosses. And this is a very bad excuse for all sorts of startups that are generally behind these atrocious websites. And as a startup your whole damn company is filled with engineering people. If your management that is filled with engineering people fails to understand the importance of fast websites then the I am afraid the problem is…
[deleted]
Re: Neither PWA nor AMP are needed to make a website load fast
#156Earlier quoted context omitted.
The AMP Project site itself is ~500kb. https://www.ampproject.org/ (desktop version is AMP-ified too).
For me it was over a megabyte, could not scroll smoothly, and had a broken header once I started scrolling.
Do people not use the web, particularly media sites.
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.
Re: Neither PWA nor AMP are needed to make a website load fast
#157Though we can find a lot of obvious overengineering cases, Tonsky should have known better that reference-style website a la Wiki and feature rich application like Airbnb impose very different trade offs between initial/overall loading times and functionality. An interesting case when someone who is firmly saying "BS" three times in every paragraph is BS too.
How is Airbnb a "feature rich application" compared to Wikipedia? They're both Search+CRUD sites as far as I can see.
Wikipedia user experience is basically a tree, Airbnb is a pretty complex graph
Re: Neither PWA nor AMP are needed to make a website load fast
#158Earlier quoted context omitted.
Except it does so in a rather poor way: * It's clearly driven by a biased entity (Google) * It doesn't actually directly prioritize page speed * It breaks websites
The web development community had plenty of time to fix these problems in better ways and it instead just spent time building bigger and bigger JS frameworks and background videos.
What problems exactly? The web works pretty well and the source of most problems is non-technical. AMP is cache + handcuffs. No, thanks. I am no web-developer, but pretty sure I wouldn't want to touch that. Is performance really an issue these days? It probably always is but there are worse ones. One specifically being closed web technologies administered by large companies like Google.
Re: Neither PWA nor AMP are needed to make a website load fast
#159Earlier quoted context omitted.
For me it was over a megabyte, could not scroll smoothly, and had a broken header once I started scrolling.
Do people not use the web, particularly media sites. 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.
Oh, that was with an adblocker on. But aside from that, many of the websites I go to don't have AMP and load quickly. Hacker News is a pretty good example; I try to keep my own website relatively lightweight as well, just like many other personal blog sites.
Re: Neither PWA nor AMP are needed to make a website load fast
#160I too struggle to like AMP. The rhetoric seems a little absent imagination in regard to offline. Are you really saying your handheld computer can't be useful without a worldwide network connection?