10 of the Weirdest Web Performance Tips: Set image width and height attributes; Compression can result in slower responses; File concatenation can make a site slower; Multiple domains may not improve performance; Use font repositories effectively; Avoid base64 encoding; Load ES6 code in the HTML <head>; Check the efficiency of ES5 transpilation; Caching CDN assets can be dangerous!; Is analytics harming site performance?
The average web page takes seven seconds to load on a desktop device and 20 seconds on mobile. It makes 70 HTTP requests and downloads more than 2MB of data including:
Source: httparchive.org Slow sites are bad for:
Users Downloading a single page on a mobile phone costs $0.29 in Canada, $0.19 in Japan, and $0.13 in the US. Those browsing in Vanuatu, Mauritania, or Madagascar pay more than 1% of their daily income.
Business Slow sites rank lower in search engines, incur higher hosting costs, are more difficult to maintain, and reduce conversion rates.
There is a simple solution to web performance: transmit less data and do less processing. The practicalities are more challenging. The following tips may be unconventional, controversial, counter-intuitive, or reverse previous advice. As always, the best result will depend on what you’re trying to achieve. Testing is imperative so tools such as Lighthouse and Asayer.io can help evaluate the impact of your changes.
Want to develop a website or re-design using CSS Development? We build a website and we implemented CSS successfully if you are planning to **[Hire CSS Developer](https://hourlydeveloper.io/hire-dedicated-css-developer/ "Hire CSS Developer")**...