47 ms·
The complete forking of HTML for primarily google search traffic will do more harm than good. HTML is already fast. Google could've used search rankings to fac
by manigandham 10y ago
The complete forking of HTML for primarily google search traffic will do more harm than good.
HTML is already fast. Google could've used search rankings to factor in site speed and forced many sites to become much faster in a few months, instead of now requiring more resources to maintain an alternative version just for them. Also 90% of the ads on the web are served by Google's own Doubleclick for Publishers, one of the slowest ad servers available.
- andy_ppp 10y agoYes! Ban slow ads you say? But we make money from that and it means we can extend the web for our purposes! Brilliant!
- lostboys67 10y agoyes good luck with that if you have had to work with any site on the internet it can be a Sisyphean task to get trivial changes made on many sites.
- manigandham 10y agoSearch rankings and the resulting traffic are a priority, changes would be made quickly. AMP pages were rolled out within weeks as well, but all that time and effort could've been spent on making the universal HTML page much better.
- lostboys67 10y agoLol you haven't worked with may real sites in the wild around 80% of the ones I have worked with need the CTO to tell the developers to pull their socks up or your all on a PIP
- manigandham 10y agoWhat? What are "real sites"? I'm in the adtech industry and know execs and devs at all the top publishers. Revenue/traffic issues are at the top of the list. They don't sit around doing nothing all day. Regardless, resources are always constrained and working on AMP means not working on the standard (mobile) HTML version.