This overhead should be avoided for certain file formats (e.g. JPEG graphics), since these formats are already packed and there is hardly any saving in the amount of data transferred (keyword: “apache deflate” ) . Reduce rendering time After all data has been transferred to the browser, it still has to be displayed. Here you can grab the browser a little under the arms. Depending on whether you have Firefox, Internet Explorer, Chrome or Opera "in front of the gun", this brings a little more or less. Validate HTML code The browser asks itself exactly two questions... What should I show of the data.
How should I view the data? So it can be quite time-consuming for the browser and take a long time until it has "interpreted" what it should do (rendering time). In one project we experienced that a gross blunder required almost 30% of the page speed after (!) the last byte had been transferred. So always remember to make the HTML code W3C-compliant (validate) as far as possible, so as not to force the browser to "guess". Images with width and height Israel phone number list Totally simple, but often forgotten or underestimated: Specify width and height for images. This allows the browser to just leave space and continue rendering without the image having to be loaded.
Dealing with JavaScript and CSS Javascript files block the rendering when loading because they could theoretically change the object tree in the HTML. They therefore belong at the end of the page if possible. CSS files, on the other hand, are loaded in parallel and belong in the head of the page. Conclusion Practice shows that consistent optimization of the loading time has a significant impact on SEO. The motto is often: "Small cause, big effect". not necessarily have to be complicated and involve extensive programming work. For the test winner blog, we were able to reduce the page speed from an average of 8-14 seconds to a constant 3 seconds with the rather simple options.