Article Description: for page load optimization tools, it's best to have a variety of options (better yet, a variety of free options). But you can use these tools to generate a list of Web site performance enhancements that can be manipulated. If you have some tools that I haven't noticed, feel free to let us know in the comments. |
Over the past few months, Google has been telling the world that the speed of web pages is increasingly becoming an important aspect of the site. Google Speed website, has a commendable goal, is to browse the Internet as fast as the book. In their webmaster blogs, several blog posts and a wide variety of free tools, including their own and others, have been introduced and have achieved great results.
So, as a website owner, if you suspect that you have a problem with web loading, what's the first step? Where to get the overall understanding of your site's performance? Do you want to open every page on the site with a stopwatch?
Many of our first places to go are our Google Webmaster tool account, login, click "Lab", then "site performance". There you can see the performance data from the Web site feedback from their crawler.
On this page, you can also see an example of the loading time of 10 pages. Unfortunately, it will not show much deeper. But at least you can see two or three bad performance pages in order to use other tools for further investigation.
YSlow and Google page speed tools (both require installing Firebug plug-ins on Firefox) all seem to show the same message. So the reason I choose YSlow instead of the page speed tool is simple. YSlow provides the level of each page that has been checked and the level of each element, and the page speed tool returns only a green, yellow, or red warning sign with a full score of 100 points. You may like the page Speed tool, but because there is not much difference between them, we will use YSlow.
When using YSlow, click on the text after each element level, it will show the details detected on that page, regardless of the JS file configuration, content compression, or the current page HTTP request times.
But this is not all, you can check out the page component statistics (such as JS files, CSS files, flash files, etc.), to see which files directly affect the load speed.
The AOL page Test tool has more visual representation on the page, showing the load time for each element of the page with a waterfall chart. Each element you can see DNS lookup time, the connection time, the first byte time, and the real content download time, which alerts you to a single element (that is, if the JS file on other domains takes too long to load, it should be placed directly on your own domain name). A green vertical line indicates when the page starts to render, and a blue vertical line indicates that the page rendering process is complete (although some page elements will not be fully rendered after a few seconds, you can check them out on the chart).
In the configuration settings for this tool, you can set the test two times per page, so it can also display the effect of the cached content loading time after the first visit.
For page load optimization tools, it's best to have a variety of options (better yet, a variety of free options). But you can use these tools to generate a list of Web site performance enhancements that can be manipulated. If you have some tools that I haven't noticed, feel free to let us know in the comments.
Source: http://www.jxln.info/wangzhan-zhizuo/3-optimizing-page-speed-tools.html
Original source: http://searchenginewatch.com/3636580