13 ms·
Centralized info for web page optimization. I wonder at the efforts spent on page speed improvements, versus letting tech improve and publishing tools handle mu
by messel 17y ago
Centralized info for web page optimization. I wonder at the efforts spent on page speed improvements, versus letting tech improve and publishing tools handle much of the implementation details.
I think web masters, sites and developers should focus all their efforts on content quality,and check a box that the page loads fast enough now.
To the contrary of this, I consciously admire optimized page loads, that flicker into existence. But this is secondary to the "knowledge payload" of the site.
- patio11 17y agoThe most critical components of page load optimization are simple tick-the-box items when setting up your application that need to be automatic for every web engineer, but aren't. They are mostly not a matter of having the tech improve. They are mostly not involved with "publishing tools" at all, insofar as by the time your CMS is in the picture it is way too late. Partial checklist: It takes something like four lines in your web server config to turn on gzip. Did you turn on gzip? It takes perhaps ten lines of code to splat all your Javascript and CSS files into one file at deployment. If you were running Rails, this would be about fifteen keystrokes or so. Did you do it? You should be loading your static assets from 2-3 hosts to maximize how many can be loaded in parallel. This is, again, two minutes of work and doesn't even require you to actually possess multiple hosts since you can just create multiple DNS entries pointing to the same one. Did you do it?