5.2 sec in total
1.2 sec
3.8 sec
242 ms
Click here to check amazing Eplay content for Russia. Otherwise, check out these important facts you probably never knew about eplay.ru
Интернет-магазин eplay
Visit eplay.ruWe analyzed Eplay.ru page load time and found that the first response time was 1.2 sec and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster. This domain responded with an error, which can significantly jeopardize Eplay.ru rating and web reputation
eplay.ru performance score
1159 ms
657 ms
280 ms
1207 ms
690 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 98% of them (86 requests) were addressed to the original Eplay.ru, 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Eplay.ru.
Page size can be reduced by 334.7 kB (20%)
1.7 MB
1.3 MB
In fact, the total size of Eplay.ru main page is 1.7 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. 40% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 23.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 23.8 kB or 77% of the original size.
Potential reduce by 65.3 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. Eplay images are well optimized though.
Potential reduce by 206.5 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 206.5 kB or 76% of the original size.
Potential reduce by 39.0 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. Eplay.ru needs all CSS files to be minified and compressed as it can save up to 39.0 kB or 82% of the original size.
Number of requests can be reduced by 28 (33%)
86
58
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eplay. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
eplay.ru
1159 ms
screen.css
657 ms
csshorizontalmenu.css
280 ms
jquery-1.4.2.js
1207 ms
jquery.fancybox.js
690 ms
jquery.pngFix.pack.js
279 ms
jquery.metadata.js
413 ms
jquery.cookie.js
419 ms
fancy.css
533 ms
cusel.css
546 ms
cusel-min-2.1.js
697 ms
nivo-slider.css
666 ms
jquery.nivo.slider.pack.js
813 ms
eplay_full.js
780 ms
swfobject.js
800 ms
topbar_left_arr.gif
699 ms
eplay.jpg
713 ms
left_arr_white.gif
787 ms
btn_search.gif
813 ms
2597387569574555.jpg
1092 ms
4919697198544998.png
1106 ms
3445484238323905.png
1038 ms
7966284831709227.png
1428 ms
6864824606825532.png
1487 ms
9903642245614378.jpg
1210 ms
2535879174586296.jpg
1316 ms
big_arr.png
1225 ms
bigfish_cover.jpg
1247 ms
bigfish_cover.jpg
1348 ms
classic_cover.jpg
1359 ms
classic_cover.jpg
1384 ms
classic_cover.jpg
1457 ms
classic_cover.jpg
1482 ms
classic_cover.jpg
1493 ms
classic_cover.jpg
1520 ms
classic_98911_box_350.jpg
1554 ms
classic_1045793_box_350.jpg
1586 ms
classic_1043718_box_350.jpg
1605 ms
classic_1084671_box_350.jpg
1491 ms
classic_1018661_box_350.jpg
1484 ms
favorit_cover.jpg
1506 ms
favorit_cover.jpg
1420 ms
favorit_cover.jpg
1458 ms
favorit_cover.jpg
1361 ms
favorit_cover.jpg
1355 ms
top100_100725_box_350.jpg
1343 ms
top100_1084666_box_350.jpg
1363 ms
top100_780373_box_350.jpg
1299 ms
top100_cover.jpg
1341 ms
top100_cover.jpg
1334 ms
top100_100723_box_350.jpg
1334 ms
top100_cover.jpg
1326 ms
top100_969403_box_350.jpg
1284 ms
top100_1114187_box_350.jpg
1272 ms
top100_1045796_box_350.jpg
1071 ms
ga.js
15 ms
__utm.gif
11 ms
eplay_small.jpg
984 ms
ym.png
942 ms
qiwi.png
933 ms
rbk.png
861 ms
wm.png
851 ms
bl.png
907 ms
mts.png
848 ms
meg.png
819 ms
inplat.png
813 ms
bg_log.jpg
822 ms
bg_log_left.jpg
782 ms
bg_log_right.jpg
831 ms
bg_promo.jpg
821 ms
info.gif
816 ms
info_hover.png
812 ms
bg_promo.png
822 ms
nav_left.gif
782 ms
nav_right.gif
825 ms
bg_search.png
820 ms
nav_bg.gif
821 ms
delimiter.gif
812 ms
carousel_bg.jpg
807 ms
bg_bigfish.jpg
791 ms
big_fish.png
815 ms
bg_acc.jpg
820 ms
bg_acc_top.jpg
817 ms
megafon.png
819 ms
bg_acc_bot.jpg
804 ms
btn_act1.gif
138 ms
left_ar.png
143 ms
right_ar.png
137 ms
eplay.ru SEO score
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eplay.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Eplay.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.
eplay.ru
Open Graph description is not detected on the main page of Eplay. 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: