Re:Google AMP case study: leads dropped by 59%
by TeMPOraL on Sunday December 16, 2018 @04:20PM
(#18695309)
And none of the things you mention will amount to anything if the site is still pulling dozens of trackers and ad scripts.
The average JS dev (like average anything dev) may not write performant code, but the functional parts of the website are not where the main problem lies.
Re:Google AMP case study: leads dropped by 59%
by sureaboutthis on Sunday December 16, 2018 @08:56PM
(#18696420)
That is a business and design problem not a programming problem. And if one thinks the functional part of a web site cannot be tuned to substantially increase the speed of a web site then one is part of that jQuery plugin crowd who does not know or understand the pipeline from browser to network to server and back.
Re:Google AMP case study: leads dropped by 59%
by TeMPOraL on Monday December 17, 2018 @01:10AM
(#18697216)
Website performance will be limited by the parts you're not allowed to improve, i.e. ad & tracking junk. It's basically Amdahl's law. I'd thought understanding that would be even more important.
There are a multitude of issues that can be tweaked to speed things up more so than javascript elimination. You can switch to HTTP/2, implement server push, image compression, header compression, compressing HTML/CSS/Javascript downloads, preloading, above-the-fold downloads, and much more. A jQuery plugin user might not know half those things and I only mentioned maybe half the things one should know.