Web Page Performance Analysis Tool

Web Page Performance Analysis Tool

Web Page Performance Analysis Tool

Why is my website slow? How do I diagnose my web site? Now you can use our free Online Web Page Performance Analysis Tool to analyze your website and get suggestions to improve website performance based on a set of rules for high performance web pages.

Bookmark:

Web Page Performance Analysis Tool

Online Web Page Performance Analysis Tool provide suggestions to Improve web site performance. This tool analyze given web page using these rules: Minimize HTTP Requests, Use a Content Delivery Network, Add an Expires or a Cache-Control Header, Gzip Components, Put StyleSheets at the Top, Put Scripts at the Bottom, Avoid CSS Expressions, Make JavaScript and CSS External, Reduce DNS Lookups, Minify JavaScript and CSS, Avoid Redirects, Remove Duplicate Scripts, Configure ETags, Make AJAX Cacheable, Use GET for AJAX Requests, Reduce the Number of DOM Elements, No 404s, Reduce Cookie Size, Use Cookie-Free Domains for Components, Avoid Filters, Do Not Scale Images in HTML, Make favicon.ico Small and Cacheable

 Web Page Performance Analysis 

Web Performance Optimization Tips

Minimize HTTP Requests
Most of web sites take 80% of the loading time in downloading components of the Front-End. Most of this time is tied up in downloading all the components in the page: images, stylesheets, scripts, Flash, etc. Reducing the number of components in turn reduces the number of HTTP requests required to render the page. This is the key to faster pages. Some techniques for reducing the number of HTTP requests: Combined files, CSS Sprites, Image maps and Inline images. read more ...

Use a Content Delivery Network
Content Delivery Network (CDN) is an excellent way to speed up your Website, Using CDN will definitely increase website speed which will gives a best performance to the end users and also Search engine bots. CDN will parallelize the downloads across the host names, it means whenever a request for a web page there are multiple Sub requests will generate for the Images, scripts, CSS etc. So it takes longer, if you host all the Images, scripts and CSS in one domain. Because after processing the first request only, another request will processed. So it will slow down the page load time. read more ...

Add an Expires or a Cache-Control Header
A first-time visitor to your page may have to make several HTTP requests, but by using the Expires header you make those components cacheable. This avoids unnecessary HTTP requests on subsequent page views. Expires headers are most often used with images, but they should be used on all components including scripts, stylesheets, and Flash components. read more ...

Gzip Components
Gzip is the most popular and effective compression method currently available and generally reduces the response size by about 70%. CSS Stylesheet,JavaScript files occupy significant size in overall webpage size. It is hence advisable to compress these files before sending them to client. This significantly improve the performance of a webpage. read more ...

Put Stylesheets at the Top
Moving CSS stylesheets to the document HEAD makes pages appear to be loading faster. This is because putting stylesheets in the HEAD allows the page to render progressively. read more ...

Put CSS Stylesheets at the Top
Moving CSS stylesheets to the document HEAD makes pages appear to be loading faster. This is because putting stylesheets in the HEAD allows the page to render progressively. read more ...

Put Scripts at the Bottom
The problem caused by scripts is that they block parallel downloads. Browsers download no more than two components in parallel per hostname. If you serve your images from multiple hostnames, you can get more than two downloads to occur in parallel. While a script is downloading, however, the browser won't start any other downloads, even on different hostnames. read more ...

Avoid CSS Expressions
While JavaScript expressions in CSS have their upsides, they are very resource intensive. That will affect the speed of the website because the expressions are frequently evaluated by the browser, causing the site to be sluggish. Not only are they evaluated when the page is rendered and resized, but also when the page is scrolled and even when the user moves the mouse over the page. Adding a counter to the CSS expression allows us to keep track of when and how often a CSS expression is evaluated. read more ...

Make JavaScript and CSS External
Using external files generally produces faster pages because the JavaScript and CSS files are cached by the browser. If users on your site have multiple page views per session and many of your pages re-use the same scripts and stylesheets, there is a greater potential benefit from cached external files. read more ...

Reduce DNS Lookups
The Domain Name System (DNS) maps hostnames to IP addresses. DNS has a cost. It typically takes 20-120 milliseconds for DNS to lookup the IP address for a given hostname. read more ...

Minify JavaScript and CSS
Minification is the practice of removing unnecessary characters from code to reduce its size thereby improving load times. The goal of JavaScript and CSS minification is always to preserve the operational qualities of the code while reducing its overall byte footprint. read more ...

Avoid Redirects
Minimizing HTTP redirects from one URL to another cuts out additional Minimize round-trip times (RTTs) and wait time for users. Redirects slow down the user experience. Inserting a redirect between the user and the HTML document delays everything in the page since nothing in the page can be rendered and no components can start being downloaded until the HTML document has arrived. read more ...

Configure ETags
Entity tags (ETags) are a mechanism that web servers and browsers use to determine whether the component in the browser's cache matches the one on the origin server. ETags were added to provide a mechanism for validating entities that is more flexible than the last-modified date. The problem with ETags is that they are constructed to be unique to a specific resource on a specific server. For busy sites with multiple servers, ETags can cause identical resources to not be cached, degrading performance. However, most of the websites that we tested don't bother configuring their ETags, so a simpler solution is to turn off ETags entirely and rely on Expires or Cache-Control headers to enable efficient caching of resources. read more ...

Make Ajax Cacheable
To improve performance, it's important to optimize these Ajax responses. The most important way to improve the performance of Ajax is to make the responses cacheable. Some of the other rules also apply to Ajax: Gzip Components, Reduce DNS Lookups, Minify JavaScript, Avoid Redirects, Configure ETags. read more ...

Reduce the Number of DOM Elements
A complex page means more bytes to download and it also means slower DOM access in JavaScript. A high number of DOM elements can be a symptom that there's something that should be improved with the markup of the page without necessarily removing content. read more ...

Avoid HTTP 404 (Not Found) error
HTTP requests are expensive so making an HTTP request and getting a useless response (i.e. 404 Not Found) is totally unnecessary and will slow down the user experience without any benefit.

Reduce Cookie Size
HTTP cookies are used for a variety of reasons such as authentication and personalization. Information about cookies is exchanged in the HTTP headers between web servers and browsers. It's important to keep the size of cookies as low as possible to minimize the impact on the user's response time. read more ...

Use Cookie-free Domains for Components
When the browser makes a request for a static image and sends cookies together with the request, the server doesn't have any use for those cookies. You should make sure static components are requested with cookie-free requests. Create a subdomain and host all your static components there. read more ...

Avoid AlphaImageLoader filter
The problem with this filter is that it blocks rendering and freezes the browser while the image is being downloaded. It also increases memory consumption and is applied per element, not per image. read more ...

Avoid AlphaImageLoader filter
The problem with this filter is that it blocks rendering and freezes the browser while the image is being downloaded. It also increases memory consumption and is applied per element, not per image. read more ...

Don't Scale Images in HTML
Don't use a bigger image than you need just because you can set the width and height in HTML. read more ...

Make favicon.ico Small and Cacheable
Make favicon.ico preferably under 1K. Set the Expires header a few months in the future. You can check the last modified date of your current favicon.ico to make an informed decision. read more ...

Online Web Page Performance Analysis Tool Information:

  • Purpose of this Tool: Web Page Optimization, Provide Suggestions to Improve Web Site Performance
  • Intended Audience: Webmasters, Web Developers, Programmers, System Administrators, Network Administrators

Credit:

External Resources: