4.1 sec in total
247 ms
3 sec
799 ms
Click here to check amazing When Release content for United States. Otherwise, check out these important facts you probably never knew about when-release.com
Great Encyclopedia of dates. Our site covers release date releases and events. Join us!
Visit when-release.comWe analyzed When-release.com page load time and found that the first response time was 247 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
when-release.com performance score
247 ms
66 ms
60 ms
61 ms
118 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 38% of them (28 requests) were addressed to the original When-release.com, 23% (17 requests) were made to Fonts.gstatic.com and 14% (10 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Google.com.
Page size can be reduced by 631.3 kB (30%)
2.1 MB
1.5 MB
In fact, the total size of When-release.com main page is 2.1 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 25.7 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 25.7 kB or 78% of the original size.
Potential reduce by 24.4 kB
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. When Release images are well optimized though.
Potential reduce by 257.0 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 257.0 kB or 65% of the original size.
Potential reduce by 324.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. When-release.com needs all CSS files to be minified and compressed as it can save up to 324.2 kB or 83% of the original size.
Number of requests can be reduced by 25 (45%)
55
30
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of When Release. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
when-release.com
247 ms
bootstrap.min.css
66 ms
bootstrap-theme.min.css
60 ms
user.css
61 ms
jquery-1.11.0.min.js
118 ms
jquery.ui.touch-punch.min.js
78 ms
bootstrap.min.js
77 ms
platform.js
79 ms
css
60 ms
css
74 ms
analytics.js
153 ms
pattern.png
153 ms
cse.js
151 ms
ZIM1HydF9UA
191 ms
post-rate2.png
78 ms
1456434582.jpg
112 ms
post-rate.png
76 ms
post-see.png
76 ms
1456434358.jpg
111 ms
1456433768.jpg
228 ms
1456433531.jpg
322 ms
1456340813.jpg
279 ms
1433856664.jpg
278 ms
1440150480.jpg
323 ms
1450650171.jpg
324 ms
1435223322.jpg
326 ms
1434282092.jpg
524 ms
1438328556.jpg
523 ms
1450824506.jpg
570 ms
1440060657.jpg
527 ms
1437389924.jpg
547 ms
1450208157.jpg
525 ms
1448184933.jpg
572 ms
1452248858.jpg
572 ms
cb=gapi.loaded_0
66 ms
cb=gapi.loaded_1
105 ms
page
309 ms
B85vmdvDILX92ray16e-1g.ttf
102 ms
oHi30kwQWvpCWqAhzHcCSKCWcynf_cDxXwCLxiixG1c.ttf
149 ms
Fl4y0QdOxyyTHEGMXX8kcaCWcynf_cDxXwCLxiixG1c.ttf
211 ms
rB9EtQHnJI9-9iLCzVr5P_esZW2xOQ-xsNqO47m55DA.ttf
231 ms
isZ-wbCXNKAbnjo6_TwHTqCWcynf_cDxXwCLxiixG1c.ttf
231 ms
3Y_xCyt7TNunMGg0Et2pnqCWcynf_cDxXwCLxiixG1c.ttf
259 ms
Zd2E9abXLFGSr9G3YK2MsNbQxvdFQproHqwx84HIuqM.ttf
230 ms
b9QBgL0iMZfDSpmcXcE8nH2Kqn9Vte1TGXY0ojLIJME.ttf
230 ms
b9QBgL0iMZfDSpmcXcE8nOXJWfeCXjwsU1ch6Jnjz-M.ttf
261 ms
BP5K8ZAJv9qEbmuFp8RpJehHuOLqwNoF1nbrW56GUTo.ttf
305 ms
mg0cGfGRUERshzBlvqxeAFFckvC8hXgXsmQzHuFCZy4.ttf
304 ms
mg0cGfGRUERshzBlvqxeAIEk51q8QmfgWAq2uDf2a4w.ttf
292 ms
collect
35 ms
collect
259 ms
jsapi
2416 ms
www-embed-player-vflQrT_sR.css
431 ms
www-embed-player.js
495 ms
base.js
579 ms
postmessageRelay
202 ms
rs=AGLTcCPQvKMaxZ_UZrje0vYo2o8gAds_NA
18 ms
rs=AGLTcCMjQOKLzmHw4jAL4LZH64_0PwYekw
42 ms
rs=AGLTcCMnARcWhtqGuymQqcrJHs7QMmwU7g
136 ms
photo.jpg
275 ms
logo.png
312 ms
api.js
224 ms
core:rpc:shindig.random:shindig.sha1.js
303 ms
2536007149-postmessagerelay.js
226 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
172 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
170 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
172 ms
rs=AGLTcCMnARcWhtqGuymQqcrJHs7QMmwU7g
62 ms
rs=AGLTcCMnARcWhtqGuymQqcrJHs7QMmwU7g
29 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
36 ms
ad_status.js
39 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
8 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
7 ms
when-release.com SEO score
RU
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise When-release.com can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it does not match the claimed English language. Our system also found out that When-release.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
when-release.com
Open Graph description is not detected on the main page of When Release. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: