1. Is it Really Worth the Effort?
2. Aim for High Speed, Not Size
3. Go for Modular Code
4. Draw A Line Between Development and Production Level Code Bases
- the code's compression depends a great deal on the language you're using (go for Google’s htmlcompressor, for YUI Compressor for CSS, or any other method that suits you)
- the images' compression could just as well mean using Photoshop's "Save for the Web" tool. Keep diving into the "sea of tools and best practices for image formats, compression algorithms, quality monitoring and so on” available online.
5. Keep It Super Neat
- load stylesheets at the top and scripts at the bottom
- bundle up your images, nice and neat, so that it should be easier for your site to load them
6. Go From Poorly Written To Readable Code
- write identifiable, short CSS selectors: they will be far more speedy in doing "accomplishing their mission"
7. Optimize Your Fonts
- compress, compress, then compress your fonts some more (use FontLoading Api for instance)
- juggle with maximum 2 fonts
- go for font-face (whenever you need to access external font resources)
- select only the variants you need (no need to overload you website with all the available weights and styles)
- ease your site's job: go for WOFF2, WOFF, TTF, and EOF formats
- use CSS inlining
8. Do It For Google
9. "Tame" Your Third Party Scripts
10. Limit Your Dependency Requests
- use a CDN (especially if you're website's a large, heavy-content one)
- use SVG or sprites methods for handling images from your style sheets
We do Web development
Go to our Web development page!