The loading time of a website is an important part of webdesign. With ever-faster Internet access, digital cameras with dozens of megapixels and feature-packed content management systems, the advantage of a brisk internet connection is quickly put into perspective again. Long loading times annoy and ensure a high bounce rate.
Badly or not at all optimized websites can become unusable with a slow line (for example) with spent data volume even with infinite patience, because the components of the website simply can not be loaded in time and the webserver will eventually acknowledge the request with a timeout. Since the announcement by Google, the Pagespeed to be a Rankingfactor to take into account, it is advisable to examine the loading time of websites in more detail and to optimize carefully. It is advisable to always measure the current website load time before any change in order to make the impact of each change comprehensible.
Prerequisites for a short load time summarized right at the beginning:
- professional hosting
- low latencies
- Minify script
- minify CSS
- optimize images
- Prevent spaghetti code
- GZIP compression
- Leverage Chaching
An important approach to page-speed optimization is the measurement of time-to-first bytes (TTFB). Especially with cheap hosting and many users per server, the value for the time-to-first byte is usually very high, which is expressed by a long commemoration break when calling a website. Remedy for a short TTFB and low latencies creates only professional hosting.
In particular, reducing HTTP requests can reduce latency.
A good way to reduce requests is to reduce the number of icons by using CSS sprites. Several icons are summarized in a file and then the corresponding areas are retrieved via CSS. In addition to the CSS sprites, images can also be retrieved via data: uri. This reduces the number of requests by one request per image, but the image encoded via data: uri is no longer usable “image” from an SEO point of view and does not have any structured data such as old tags. Such an image will no longer appear in Google’s image search and can not be cached separately. Another method of reducing HTTP requests is to use inline code. In addition to data: uri, script and CSS style sheets can also be entered inline directly in the HTML code in order to save one request at a time. With effectively configured leverage caching this is counterproductive. On the one hand, you reduce by one more request, but the content can no longer be loaded in parallel. Modern browsers are able to process several requests in parallel. In conjunction with leverage caching, certain elements can be specified that are stored locally on the user’s computer and do not have to be downloaded again.
The required bandwidth and thus also the required charging time can be reduced by using GZIP compression. GZIP can be used to compress specific types of files. It should be noted that media content such as images or sound are often already compressed so much that GZIP compression does not create an advantage in terms of size, but the server has to make CPU resources available. Read here how to compress images.
Another way to conserve bandwidth and reduce load time is to use minify. Minify removes unnecessary spaces in stylesheet CSS files, reducing the overall size of these files. Minify is already present in many CMS and works automatically. But there are also online providers that compress uploaded CSS files on-the-fly. The extent to which a specific measure has a concrete effect must be considered on a case-by-case basis.
For a website with many visitors, using CDN may be useful. These are external servers that provide specific content. From its own server, only the basic building blocks are loaded, with other such. Google fonts, bootstrap stylesheets, pictures, videos et cetera are available on other servers and added. Internet sites with a particularly large number of visitors and many elements benefit particularly from the use of CDN.
Webdesign-aus-Braunschweig supports you with the page-optimized optimization of your homepage. Simply make a non-binding request for an individual offer.