Access whynotwednesday.com. Verizon: Wireless, Internet, TV and Phone Services

whynotwednesday.com

616 ms

pre_tumblelog.js

38 ms

css

71 ms

precrafted-social.css

84 ms

huge-styles.css

79 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Whynotwednesday.com, 11% (10 requests) were made to Static.tumblr.com and 10% (9 requests) were made to Secure.assets.tumblr.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source 49.media.tumblr.com.

Content Size

3.2 MB

After Optimization

2.0 MB

In fact, the total size of Whynotwednesday.com main page is 3.2 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 97.9 kB

Original 111.4 kB
After minification 87.3 kB
After compression 13.5 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 24.1 kB, which is 22% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 97.9 kB or 88% of the original size.

Image Optimization

-5%

Potential reduce by 77.4 kB

Original 1.6 MB
After minification 1.6 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Whynotwednesday images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 791.6 kB

Original 1.2 MB
After minification 1.2 MB
After compression 387.7 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 791.6 kB or 67% of the original size.

CSS Optimization

-76%

Potential reduce by 235.8 kB

Original 310.0 kB
After minification 299.4 kB
After compression 74.2 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Whynotwednesday.com needs all CSS files to be minified and compressed as it can save up to 235.8 kB or 76% of the original size.

Requests Now

After Optimization

The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whynotwednesday. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.