4 ms·
> The open solution to a faster mobile web would have been so easy: Just penalize large and slow web pages without defining a dedicated mobile specification It
by usernam 10y ago
> The open solution to a faster mobile web would have been so easy: Just penalize large and slow web pages without defining a dedicated mobile specification
It's obvious they have a different view on this. You can see this first-hand on their pagespeed tool. Pagespeed ranks your pages mostly according to random features, irregardless of size and performance. Actual test you can perform: 1kb web page with no compression ranks lower than 1mb web page after compression: "because you should enable server-side compression".
Their mobile assessment tool is similarly a joke.
The sad thing is that I'm likely getting a lower ranking on my website with has 5kb vanilla uncompressed js (gasp, not even async!) compared to the glittered rating of a 5mb homepage which loads 5mb+ more excluding webfonts from external CDNs.
You can taste that this has spread into google monoculture by the performance of their own web services.
- freehunter 10y ago>You can taste that this has spread into google monoculture by the performance of their own web services. I gave up on Google Maps a long time ago. On my desktop or laptop, it loads in chunks. Like, the map loads, then the search bar loads, then the navigation (zoom tools, etc) loads. When I click and drag, many times I end up selecting the page instead of moving the map because it hasn't finished loading. I use Bing Maps on desktop and Apple Maps on mobile, only using Google Maps when I need to verify an address is the right place or find a company's hours, since their data is better than their competitors. But man their performance is worse. Way worse.
- nebabyte 10y agoregardless