is the easiest f***ing way to check for gzip and more. The purpose of this site is to aide web designers & developers in speeding up sites by pinpointing which resources are not being gzipped by the server, which resources are slow and which resources are causing 404s. Our mission is to increase awareness of site speed as an important part of the web's future. George Washington approves. Read more...
| Timestamp | Effective URL | DNS lookup time | Total Time (s) | Redirect Count | Redirect Time (s) | Size (KB) | Speed (KB/s) |
|---|
| Resource URI | HTTP Code | Speed (KB/s) | Size (KB) | Total Time (s) | Type | Compression |
|---|
The time (E.S.T.) that the user initiated a request.
The "final" URL that the request is made on. For example, one may enter "example.com" for a URL. Internally, our system will go through a series of forwards and/or redirects, and may end up with "http://www.example.com" as the effective URL.
The time it takes our server to lookup the IP address of the entered site.
The total time it took for our server to load the entered site.
The total # of redirects that occurred before landing on the effective URL.
The total time it took to perform all the redirects.
The total size (in KB) of the requested URL. Note that this is the size of the initial page, and not the total size of all resources on the site. Resource statistics are seen in a separate table.
The average download speed (in KB/s).
The URL of an individual resource. These are links directly to resources of the site (for example, CSS + javascript files).
The HTTP code returned by the remote server when requesting a resource file. You should see "200" (success) for all your resource files. It is particularly unwanted if you see "404" (page not found) for any resources, and these should be among the first things you fix on your site. For a full explanation of what HTTP codes mean, see List of HTTP status codes
The type of resource file being requested. Mostly these will be "js" (javascript) or "css" (cascading style sheet), however it is possible to see other types. If our server doesn't know the type, it will show a best guess.
The type of compression the resource is being returned with. If there is "none" here, there is a potential for improvement, as there is almost no reason not to compress your resource files. On compressed files, overwhelmingly you will see "gzip", although other types of compression may be seen.
Gzip is a type of HTTP compressions. Any modern browser will support receiving gzip compressed resources. The server sending the resources must be configured to send resources with gzip, which may or may not be enabled by default, depending on the web server.