date: 2019-09-19, reading time 3 min
On speed matters in Internet world . Nobody doubts that. Believe that no one is fast enough. Waving your hand and saying it is not important is not the right approach. The page load time relates to many factors. First one is your server or hosting you have. This is the first basic factor. Not only what server and hosting, but also who your IP address is shared with.
The second major factor is the design of the page itself, the more requests on the page, the slower page is. It's logical. Let me give you an example of this - if you have a sheet of paper and just tear it, it's faster than tearing a sheet of paper into more smaller pieces and much faster than cutting paper into precise shapes with scissors. In the end, you have torn paper. Learn the basics How do I create a new website?.
Check out the Google homepage. You'll load a white home page with the Google logo, search bar, Google login option, and that's it. Fast load and all what the user needs. The fact that other processes run in the background does not interest the user. You enter a search query and other processes run in the background as you type. When typing the user gets an offer of what query most people search for, etc. All of these tasks run very fast.
Take the same approach and display what you want to display only. And let the other requests upload in the background later. For example as connecting to another server / resource, loading images, or resources for other pages. The user will give you a few seconds to complete these requests, while read the displayed page. It is similar to the way you put a signpost on the main page. Take a look at CNN or BBC websites, for example. Notice how they load and how many articles on the main page they can display. Their main pages are classic signposts with photos and text, or a link to a video. The user selects the news what he wants to read. What article wants to open. And this article will then load quickly. Imagine how fast and how frequently must news sites update the content. This is another point. Not only fast website, but also easy and fast maintaining.
Take advantage of saving resources to the user's device - cache expiration period. Website needs the resources to render when the user visits the page again. And when browsing through next pages on your website as well. Formats, links, pictures. As an example, I will mention the logo. A small image that is associated with each page. But do you want the user's device loads logo separately for each page, over and over again? You certainly don't want to.
Another point that may not directly relate to speed is https format. But there is the relation. Depending on user's browser settings, insecure connections may be automatically blocked. This means the page will not load to the user, but a warning will appear. This is the worst variant of speed - malfunction.
The sequence and website speed of rendering a web page depends on the order in which you write the requests in the webpage source file. Browsers read and process these requests according to defined rules. The basic ones are, reading from top to bottom and from left to right. Example if you have a sidebar request at the top of the source file. The sidebar element requests for additional external resources. This sequence slows down rendering because the browser has to find the external source address, connect to, download data and after can continue render. It is better to render first html content or at least start rendering ....... if you would experiment a little, you find the best way to render your page fast. Think about the correct order of commands and requested resources. What the browser needs and does not need to render - for example, include a social sharing bar with external requests after the main content. Pass to the browser the basic and most important information first, and then the other data. Reduce the number of requests and files. Here you can read the right procedure Prioritize main content.
By changing the order of html, js, php, and css, minimizing the number of resources, and timing them correctly, you can ensure that your website is fast enough. Or at least you win the impression that the page is fast. Check the rendering sequence - waterfall, the free tool is GtMetrix. Example - only by changing the sequence of commands and resources you can achieve a significant increase in ranking on the Google page speed test. For no less than 20 percent. Because you speed up the rendering of the page. Just a few seconds of work and you win a lot. This is just one of the factors. Why not have a website as fast as possible. Read a few articles to get a good overview and basic guidance on how to organize your content rendering.
Don't look at page coding, like writing an article in a magazine. This is different type of writing.
Back up and perform a functional test after any modification!
About & Contact Follow:
Copyright © 2019 SeoTools.la, Los Angeles, California