5.7 sec in total
1.4 sec
3.6 sec
677 ms
Visit ezka.ru now to see the best up-to-date Ezka content for Ukraine and also check out these interesting facts you probably never knew about ezka.ru
Что приготовить на ужин, на завтрак? Как украсить праздничные блюда? Самые вкусные кулинарные рецепты! Блюда из тыквы, мяса, курицы, грибов, картофеля, рыбы, творога, капусты, кабачков и многого друго...
Visit ezka.ruWe analyzed Ezka.ru page load time and found that the first response time was 1.4 sec and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
ezka.ru performance score
name
value
score
weighting
Value2.4 s
72/100
10%
Value3.2 s
72/100
25%
Value2.4 s
98/100
10%
Value120 ms
97/100
30%
Value0.367
29/100
15%
Value3.0 s
96/100
10%
1392 ms
125 ms
255 ms
247 ms
273 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 46% of them (41 requests) were addressed to the original Ezka.ru, 16% (14 requests) were made to Zn2.gnezdo.ru and 8% (7 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Ezka.ru.
Page size can be reduced by 294.4 kB (23%)
1.3 MB
1.0 MB
In fact, the total size of Ezka.ru main page is 1.3 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.0 MB which makes up the majority of the site volume.
Potential reduce by 64.3 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 64.3 kB or 82% of the original size.
Potential reduce by 99.9 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. Ezka images are well optimized though.
Potential reduce by 100.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 100.9 kB or 68% of the original size.
Potential reduce by 29.3 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. Ezka.ru needs all CSS files to be minified and compressed as it can save up to 29.3 kB or 85% of the original size.
Number of requests can be reduced by 32 (37%)
87
55
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ezka. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and as a result speed up the page load time.
ezka.ru
1392 ms
script.js
125 ms
style.css
255 ms
basic.js
247 ms
wp-page-numbers.css
273 ms
modal-window-min.js
274 ms
adsbygoogle.js
8 ms
wp-embed.min.js
271 ms
teasers-min.js
492 ms
wp-emoji-release.min.js
146 ms
banner.jpg
816 ms
3_0_FB90B3FF_DB7093FF_0_pageviews
354 ms
page_t.jpg
141 ms
page_gl.png
503 ms
header.jpg
508 ms
menuitem.png
142 ms
postheadericon.png
141 ms
postdateicon.png
354 ms
postauthoricon.png
354 ms
01-300x200.jpg
375 ms
postcategoryicon.png
354 ms
postcommentsicon.png
364 ms
%D0%BA%D0%B0%D0%BA-%D0%BE%D1%82%D0%BC%D0%B5%D1%87%D0%B0%D1%82%D1%8C-%D0%BC%D0%B0%D1%81%D0%BB%D0%B5%D0%BD%D0%B8%D1%86%D1%83-300x203.jpg
501 ms
10-300x225.jpg
506 ms
99870181_Kruzhevnuyeblinuy-300x220.jpg
608 ms
10-3-300x200.jpg
744 ms
70b69631e7_1000x-300x200.jpg
1192 ms
salat_iz_cvetnou_kapysti_tikvi-300x201.jpg
617 ms
%D0%BA%D1%83%D0%BF%D0%B0%D0%BD%D0%B8%D0%B5-%D0%B2-%D0%BA%D1%80%D0%B5%D1%89%D0%B5%D0%BD%D1%81%D0%BA%D0%BE%D0%B9-%D0%BF%D1%80%D0%BE%D1%80%D1%83%D0%B1%D0%B8-256x300.jpg
617 ms
16418-300x254.jpg
620 ms
08-300x200.jpg
855 ms
%D0%BA%D0%B0%D0%BA-%D0%BF%D1%80%D0%B8%D0%B3%D0%BE%D1%82%D0%BE%D0%B2%D0%B8%D1%82%D1%8C-%D0%BA%D1%83%D0%BB%D0%B8%D1%87-150x150.jpg
740 ms
%D0%BA%D0%BE%D0%BC%D0%BF%D0%BE%D1%82-%D0%B8%D0%B7-%D1%81%D0%BB%D0%B8%D0%B2-%D0%BD%D0%B0-%D0%B7%D0%B8%D0%BC%D1%83-150x150.jpg
741 ms
f2f972aff39adaad5e342915338593da-150x150.jpg
744 ms
ca-pub-0073473387455640.js
61 ms
zrt_lookup.html
54 ms
show_ads_impl.js
70 ms
pbody.jpg
846 ms
blockheader.png
847 ms
blockcontent_s.png
848 ms
blockcontent_h.png
850 ms
blockcontent_v.png
959 ms
blockcontent_c.png
975 ms
block_a.js
1168 ms
blockcontentbullets.png
936 ms
button.png
934 ms
vmenuitem.png
938 ms
block_a.js
529 ms
rssicon.png
1040 ms
footer.png
1877 ms
hit
292 ms
watch.js
287 ms
160.js
317 ms
ads
285 ms
osd.js
13 ms
ads
285 ms
teasers.php
171 ms
watch.js
465 ms
block.js
124 ms
320.jpg
124 ms
304.jpg
248 ms
309.jpg
247 ms
18194026534780498877
39 ms
abg.js
42 ms
m_js_controller.js
40 ms
googlelogo_color_112x36dp.png
76 ms
15340351990612254652
58 ms
s
31 ms
x_button_blue2.png
11 ms
MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js
13 ms
tzr.fcgi
141 ms
405769_3648eb6f8f.jpg
399 ms
405675_87fa873f11.jpg
395 ms
399157_3772947462.jpg
398 ms
405773_6dab805472.jpg
404 ms
405710_eded929491.jpg
407 ms
397262_83b552c9f1.jpg
407 ms
advert.gif
91 ms
1
91 ms
tzr.fcgi
131 ms
404049_6e815794c9.jpg
135 ms
404542_991c788c04.jpg
141 ms
404050_eb558eb463.jpg
140 ms
350950_f6625edb59.jpg
138 ms
391825_71d4170942.jpg
133 ms
404739_c300280890.jpg
134 ms
402819_8347182576.jpg
264 ms
404094_0ee84f9186.jpg
262 ms
activeview
15 ms
activeview
19 ms
ezka.ru accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
ezka.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ezka.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 Ezka.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.
ezka.ru
Open Graph description is not detected on the main page of Ezka. 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: