What is gzipWTF?
gzipWTF is the easiest f***ing way to check for gzip and more. Well, that's our slogan, but seriously, that's pretty much what we do.
So seriously, what is gzipWTF?
gzipWTF allows you to check any site for several statistics, one of them being HTTP compression. Gzip is the most common type of HTTP compression on the web, although despite our name, gzipWTF also checks for other types of compression that may still be used (deflate,sdhc). Aside from compression, gzipWTF checks several other useful statistics about the resources (javascript and css files) on your site, and conveniently displays them in a sortable table. So, aside from checking for compression, you can use gzipWTF to check for slow resource files and 404 (page not found) errors.
What's our mission?
To make more sites blazing fast. The web is only getting more complex, and it is imperative that we keep things managable. We also want our site to be accessible to people from all around the world. To accomplish this, we've tried to make use of icons as much as possible. If you don't see your country's language, please contact us and help us translate!
Why should I bother?
Ensuring all your site's resource files are gzipped can make a huge impact on your site's performance. Consider a javascript file that is 200kb – gzipped it can be as low as 40kb. Now imagine you have several javascript files being served on your site, and you can start to understand the benefits of gzip. gzipWTF checks for gzip on all sorts of files (not just javascript files), although javascript files tend to be the largest in size, and thus have the most potential in terms of compression. Also note that Google now accounts for a site's performance (its load speed) as a factor for search ranking.
How does gzipWTF work?
gzipWTF works by first requesting the URL you enter. It then parses the HTML response, and finds all referenced resources, proceeding to request each resource in parallel. Our engine works very fast & efficiently, so most requests should only take a few seconds to complete. In the results you'll see three sections. The first overviews the initial request to your URL. Second is a series of pie charts that summarize the requests to individual resources. Last is a table of all the individual resources. For the most detailed view of the last table, make sure to check "details" before you make your request.
What's different about gzipWTF?
Aside from the fact that we haven't seen a service quite like ours, we aim to do so with a clean, minimal interface that "just works." We give you detailed information about your site's performance, but not so much that it's overwhelming. We want to make it easy for you to take action using gzipWTF's results.
Does gzipWTF gzip files for me?
No, that's silly.

Is gzipWTF free?
Yes, the beta is completely free – even no signup is required! We plan on offering a paid plan in the near future, for users who want unlimited access to gzipWTF.
What are the limitations of beta?
You must enter a CAPTCHA for every request. Also, you must wait 60 seconds between requests. We put in these limits to prevent spam and overload on our servers. Furthermore, every request is supplemented with a quote from George Washington's Rules of Civility. To remove all limitations, Upgrade to a paid plan (coming soon!).
Will you offer a paid service?
We hope! Right now we're just in beta to see if people around the world find our service useful. If so, we will build a very affordable paid version that will unlock any limitations of the beta, as well as provide some new features that we're working on, such as exporting results to .CSV, and the ability to save results.

I'm getting error messages "too many requests in a 24 hour period" but I haven't even used the service in the last 24 hours. WTF!?
Our limiting system isn't perfect because it is based by IP address. Although unlikely, it is possible that another person with the same IP address has used gzipWTF too many times in the last 24 hours. This can happen if you are using gzipWTF at a place with shared internet (and thus usually a single, shared IP address) such as an internet cafe or an office.
I don't think gzipWTF is finding all my site's resources?
gzipWTF can only read files referenced directly. If you have resources that are loaded dynamically (e.g. an external script that is loaded into the body dynamically), gzipWTF will not be able to read them. In any case, it is unlikely that this will affect your results, because dynamically loaded scripts are usually tracking pixels. If you are having trouble with tracking pixels, you should investigate further with a browser.
My requests are taking too long?
Some sites are faster to respond to requests than others. Please allow up to 30 seconds for the request to complete. If our server still cannot connect to the requested site after 30 seconds, you'll see a "Timeout occurred!" error. Most gzipWTF requests, however, should complete in under 10 seconds.
The twitter "news" feed on the homepage is empty?
Twitter limits feeds to 150 requests per hour per IP address. If you are on a shared IP address with many other people using gzipWTF, your IP may have used up its 150 allowed requests for the hour, and the news feed will show empty. Please check back in the next hour and it will be available again. For future releases of gzipWTF, we're looking for a better alternative.
I'm getting an 'Internal Error' every time I do a request?
Internal Errors indicate a problem with our system. Please contact bugs@gzipwtf.com and we'll do our best to resolve the issue ASAP.

How should I interpret the results of a request?
To get the most useful information, make sure you have selected "details" before making your request. There are certain things to look for in the detailed results that will help you diagnose poor performance (room for significant improvement), namely: 404s – First, you want to make sure none of your resource files are throwing 404 errors. You can check this in the "HTTP Code" column.gzip – Second, check if all your resources are gzipped – if not, a wise first step would be to make sure those resources are served with gzip. If the resource is being served from an external site, you don't have control over it, but otherwise you can enable gzip on any resources being served from your web server. For details on how to enable gzip, see "". speed – Third, check for resources with unusually high transfer times (you can sort the total time column to see this conveniently). Slow transfer speeds are normal if the resource file size is very small, so it's best to gauge slowness by the total time column – anything over one second should be double checked.
Why do you require entering CAPTCHA for each request? Why?
Nobody likes entering CAPTCHA, but it in the end it is preventing spam and helping digitize books. Upgrade to a paid plan (coming soon!) and never type in a CAPTCHA again!

Does gzipWTF store any of my information?
We absolutely don't store any of your information. Search settings are saved in localstorage on YOUR computer. Note that settings saved in localstorage are on a per-browser basis – if you save your settings in Chrome but then open gzipWTF in Firefox, you'll notice your settings are reverted to the defaults.