One solution is to simply delay loading images. Images can play a major role in the difference between “document complete” and “fully rendered site” loading times, especially for mobile sites. Reducing the Image File Size Using the Lossy and Lossless Compression Techniques So, for instance, having a “document complete” time which is faster than the “fully rendered time” could help.Ģ. Even though it is difficult to pinpoint specifically and with certainty which aspect of speed directly helps your rankings, working on your site loading speed, in general, is bound, at the very least, to enhance your users’ experience. The latter means that everything is clearly visible on the page, even background stuff like ads and images. The former means that while not all the elements on a page are showing, you can start clicking and navigating. What is and how exactly does Google measure “site speed?”įor instance, the difference between “document complete” and “fully rendered” time when loading a page was mentioned. Some questions and concerns remain though, the most important being:
In fact, chances are smaller sites have the upper hand here in terms of flexibility and adjusting. The slew of freely available tools is certainly meant to wear off some of the concerns that only big sites can benefit from this change. There is the PageSpeed module in the Google Developers section and a Page Speed Insights for making a speed audit for every website.Įven Yahoo has a developer module for page speed improvement, called Yslow. Google thinks the same, as indicated by the very fact that it provides us with tools to check up on our site speed and suggests solutions for sluggish pages. Users get an enhanced experience, site owners are more likely to get reduced operation costs and… well, more users, who stay on the website longer. Site speed, according to Google, “reflects how quickly a website responds to web requests” and for all intents and purposes serves both the user and the site owner.
0 kommentar(er)
