24.1 sec in total
1.3 sec
22.1 sec
718 ms
Visit 4zn.ru now to see the best up-to-date 4 Zn content for Russia and also check out these interesting facts you probably never knew about 4zn.ru
Новости Apple, обзоры, новинки Apple, iPhone, iPad, iPod, MacBook, iMac, Apple Watch, iOS, iOS приложения, iOS игры, игры для iPhone, игры для iPad, приложения
Visit 4zn.ruWe analyzed 4zn.ru page load time and found that the first response time was 1.3 sec and then it took 22.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
4zn.ru performance score
1267 ms
179 ms
520 ms
524 ms
311 ms
Our browser made a total of 28 requests to load all elements on the main page. We found that 79% of them (22 requests) were addressed to the original 4zn.ru, 11% (3 requests) were made to Cdn.admitad.com and 4% (1 request) were made to Nyc-brooklyn.ru. The less responsive or slowest element that took the longest time to load (19.9 sec) relates to the external source Informer.yandex.ru.
Page size can be reduced by 261.7 kB (32%)
807.9 kB
546.2 kB
In fact, the total size of 4zn.ru main page is 807.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 460.7 kB which makes up the majority of the site volume.
Potential reduce by 41.2 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 9.6 kB, which is 20% 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 41.2 kB or 85% of the original size.
Potential reduce by 2.5 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. 4 Zn images are well optimized though.
Potential reduce by 104.9 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 104.9 kB or 68% of the original size.
Potential reduce by 113.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. 4zn.ru needs all CSS files to be minified and compressed as it can save up to 113.2 kB or 79% of the original size.
Number of requests can be reduced by 11 (44%)
25
14
The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 4 Zn. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
4zn.ru
1267 ms
wp-emoji-release.min.js
179 ms
style.css
520 ms
genericons.css
524 ms
responsive.css
311 ms
ie.css
319 ms
jquery.js
534 ms
jquery-migrate.min.js
319 ms
jquery.sidr.min.js
525 ms
catchflames-ielte8.min.js
925 ms
fitvids.min.js
550 ms
jquery.waypoints.min.js
655 ms
catchflames-custom.min.js
653 ms
wp-embed.min.js
661 ms
Black-Friday-2014-%D0%B2-%D0%A0%D0%BE%D1%81%D1%81%D0%B8%D0%B8.jpg
1008 ms
1_0_FFFFFFFF_F1F1F1FF_0_pageviews
19916 ms
logo.png
312 ms
1.-%D0%9E%D0%B1%D0%B7%D0%BE%D1%80-%D0%B8-%D1%85%D0%B0%D1%80%D0%B0%D0%BA%D1%82%D0%B5%D1%80%D0%B8%D1%81%D1%82%D0%B8%D0%BA%D0%B8-iPhone-6S.jpg
229 ms
1.-MARVEL-%D0%91%D0%B8%D1%82%D0%B2%D0%B0-%D1%87%D0%B5%D0%BC%D0%BF%D0%B8%D0%BE%D0%BD%D0%BE%D0%B2.jpg
480 ms
0.-%D0%A0%D0%B5%D0%B3%D0%B8%D1%81%D1%82%D1%80%D0%B0%D1%86%D0%B8%D1%8F-%D0%B2-Tsu-%D1%81%D0%BE%D1%86%D0%B8%D0%B0%D0%BB%D1%8C%D0%BD%D0%BE%D0%B9-%D1%81%D0%B5%D1%82%D0%B8.jpg
767 ms
1.-%D0%9E%D0%B1%D0%B7%D0%BE%D1%80-iOS-7.jpg
473 ms
1.-%D0%9E%D0%B1%D0%B7%D0%BE%D1%80-%D0%B8-%D1%85%D0%B0%D1%80%D0%B0%D0%BA%D1%82%D0%B5%D1%80%D0%B8%D1%81%D1%82%D0%B8%D0%BA%D0%B8-iPhone-5C.jpg
308 ms
1.-%D0%9E%D0%B1%D0%B7%D0%BE%D1%80-%D0%B8-%D1%85%D0%B0%D1%80%D0%B0%D0%BA%D1%82%D0%B5%D1%80%D0%B8%D1%81%D1%82%D0%B8%D0%BA%D0%B8-iPhone-5S.jpg
323 ms
1.-%D0%95%D0%B6%D0%B5%D0%B3%D0%BE%D0%B4%D0%BD%D0%B0%D1%8F-%D0%92%D1%81%D0%B5%D0%BC%D0%B8%D1%80%D0%BD%D0%B0%D1%8F-%D0%BA%D0%BE%D0%BD%D1%84%D0%B5%D1%80%D0%B5%D0%BD%D1%86%D0%B8%D1%8F-%D1%80%D0%B0%D0%B7%D1%80%D0%B0%D0%B1%D0%BE%D1%82%D1%87%D0%B8%D0%BA%D0%BE%D0%B2-WWDC-2013-%D0%B2-%D0%A1%D0%B0%D0%BD-%D0%A4%D1%80%D0%B0%D0%BD%D1%86%D0%B8%D1%81%D0%BA%D0%BE.jpg
607 ms
watch.js
191 ms
ffda87c3876d14fd68522da477a7ab89.gif
672 ms
a685395ccebc43730442c8d10bdc9c59.png
729 ms
5ab5346af997d9539d12e95bd5067584.jpg
716 ms
4zn.ru SEO score
N/A
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 4zn.ru can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Russian. Our system also found out that 4zn.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.
4zn.ru
Open Graph description is not detected on the main page of 4 Zn. 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: