Refactoring HTML and CSS -


i know commonly refactor code back-end improve it's speed, security or make more readable next person takes on project, refactor html , css? since markup languages doesn't seem trivial, besides wiping off few bytes of code vs time input looking alternatives doesn't seem worth effort, if working on tight deadline.

there innumerable things can increase or decrease page performance. optimisation though, should start people seeing problems or slowdown.

on broader level, reducing payloads smallest possible size makes big difference. involves gzip, caching, , minification. can rewrite code thousand times won't end smaller if @ if use gzip , minify css — don't minify html it's prone rendering issues.

on finer level, specific css features such resizing large images , implementing lots of browser-generated gradients , shadows can bring performance down significantly. if you're noticing sluggishness when scrolling things need focus on. 1 image that's 640x480 or more being resized css can bring performance crashing down in browsers.

then of course there's latency. using content distribution networks or @ least highly optimised servers ensure html, css, javascript, , image files delivered users , shown possible.


Comments

Popular posts from this blog

java.util.scanner - How to read and add only numbers to array from a text file -

rewrite - Trouble with Wordpress multiple custom querystrings -