13.9 sec in total
331 ms
11.4 sec
2.2 sec
Visit when-release.ru now to see the best up-to-date When Release content for Russia and also check out these interesting facts you probably never knew about when-release.ru
Большая энциклопедия дат. Наш сайт освещает даты выхода релизов и событий. Присоединяйтесь к нам!
Visit when-release.ruWe analyzed When-release.ru page load time and found that the first response time was 331 ms and then it took 13.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
when-release.ru performance score
name
value
score
weighting
Value4.6 s
13/100
10%
Value18.7 s
0/100
25%
Value11.6 s
4/100
10%
Value2,990 ms
3/100
30%
Value0.006
100/100
15%
Value26.5 s
0/100
10%
331 ms
363 ms
77 ms
178 ms
180 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 32% of them (35 requests) were addressed to the original When-release.ru, 11% (12 requests) were made to Vk.com and 9% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (6.5 sec) belongs to the original domain When-release.ru.
Page size can be reduced by 614.8 kB (24%)
2.6 MB
1.9 MB
In fact, the total size of When-release.ru main page is 2.6 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. 55% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 162.8 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 162.8 kB or 84% of the original size.
Potential reduce by 31.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 266.4 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 266.4 kB or 58% of the original size.
Potential reduce by 154.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.ru needs all CSS files to be minified and compressed as it can save up to 154.2 kB or 83% of the original size.
Number of requests can be reduced by 49 (46%)
107
58
The browser has sent 107 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 33 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
when-release.ru
331 ms
when-release.ru
363 ms
bootstrap.min.css
77 ms
bootstrap-theme.min.css
178 ms
user.css
180 ms
jquery-1.11.0.min.js
265 ms
jquery.ui.touch-punch.min.js
175 ms
bootstrap.min.js
173 ms
forgetmenot.min.js
105 ms
openapi.js
1855 ms
adsbygoogle.js
100 ms
top100.jcn
734 ms
css
204 ms
css
247 ms
analytics.js
191 ms
watch.js
71 ms
pattern.png
104 ms
logo.png
92 ms
search1.png
92 ms
post-rate2.png
91 ms
1459977112.jpg
228 ms
1459976773.jpg
221 ms
1459976269.jpg
266 ms
1459976064.jpg
285 ms
1459975889.jpg
382 ms
1417442127.jpg
460 ms
1414762419.jpg
337 ms
1419434803.jpg
945 ms
1415171548.jpg
602 ms
1435067765.jpg
516 ms
post-rate.png
663 ms
post-see.png
415 ms
383c3668e9cddccde2984a98921ce273.jpg
1249 ms
1425756895.jpg
573 ms
fc8381dd34fad9e0791d407783b56f0e.jpg
987 ms
1414755364.jpg
1404 ms
1425058097.jpg
972 ms
1427182365.jpg
1435 ms
1425412155.jpg
1278 ms
1414564722.jpg
1107 ms
collect
42 ms
collect
1034 ms
upload.gif
232 ms
widgets.js
540 ms
widget_community.php
430 ms
sdk.js
921 ms
ca-pub-2116068764546941.js
47 ms
zrt_lookup.html
559 ms
show_ads_impl.js
249 ms
BC_utynUcSw
394 ms
context.js
781 ms
ads
627 ms
osd.js
53 ms
www-embed-player-vfl5foy2V.css
1948 ms
www-embed-player.js
2481 ms
loader_nav19239_3.js
240 ms
lite.css
395 ms
lite.js
1134 ms
lang3_0.js
561 ms
widget_community.css
711 ms
xdm.js
744 ms
al_community.js
896 ms
context_static_r1084.js
1035 ms
188 ms
xd_arbiter.php
331 ms
10502764764175473429
325 ms
abg.js
386 ms
m_js_controller.js
602 ms
googlelogo_color_112x36dp.png
156 ms
x_button_blue2.png
206 ms
s
89 ms
IVL3ckfH-JY.jpg
926 ms
camera_50.png
203 ms
t5wmEJ8OOg4.jpg
1080 ms
e_a1cd3fe1.jpg
1251 ms
xwC2YTg9Sx0.jpg
3449 ms
1Cj2yxnCuAk.jpg
1630 ms
f_nuYuZxSYk.jpg
1700 ms
83OhW3vqq84.jpg
1698 ms
QKJo6PjJrPU.jpg
1699 ms
JsunYCAXu5k.jpg
1809 ms
w_logo.png
191 ms
j6SDDiQit5YY48GNgPpnCluJgoNCzbKlh5o6eVjReZI.js
81 ms
139678
256 ms
watch.js
0 ms
y150
813 ms
top100.scn
220 ms
1431687237.jpg
853 ms
2ae371c3e92319b0fce29ae49ac6ab2b.jpg
420 ms
582231caf0021800d535fa84133e9689.png
6461 ms
like_box.php
330 ms
MxOchIADMT_.css
308 ms
3w3jujerapC.css
408 ms
SRSW8M763HA.js
555 ms
4uFOsJeWEIM.js
689 ms
y97Ig99UVTs.js
554 ms
KHAtULXOQuz.js
552 ms
veBs87dwiCXgZb9CwomBYiW1hyWXgp0ohA3Vj3gnbUg.js
288 ms
ad_status.js
293 ms
10978627_777695428963036_5366009565284203506_n.jpg
373 ms
10312838_777696992296213_246949212291670671_n.png
457 ms
12141557_1683234345242132_7459698971167536528_n.jpg
523 ms
12592262_1543502822610631_6118841599261081866_n.jpg
570 ms
11219678_510250882484553_7027418530585320769_n.jpg
607 ms
264505_598134546878237_662747435_n.jpg
568 ms
735239_1718074351740158_4062162956688543012_n.jpg
577 ms
12196108_548968648588480_1488830292789523661_n.jpg
582 ms
wL6VQj7Ab77.png
127 ms
1JLnMyDN79z.png
125 ms
VXcANLwwL5J.js
71 ms
i8XO-4kv8i7.js
75 ms
when-release.ru accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
when-release.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
when-release.ru SEO score
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise When-release.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that When-release.ru 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.ru
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: