6.8 sec in total
1.7 sec
4.7 sec
428 ms
Visit m.ezadar.hr now to see the best up-to-date M Ezadar content for Croatia and also check out these interesting facts you probably never knew about m.ezadar.hr
Visit m.ezadar.hrWe analyzed M.ezadar.hr page load time and found that the first response time was 1.7 sec and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
m.ezadar.hr performance score
name
value
score
weighting
Value0.7 s
100/100
10%
Value0.7 s
100/100
25%
Value0.9 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.7 s
100/100
10%
1664 ms
281 ms
287 ms
676 ms
303 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 45% of them (25 requests) were addressed to the original M.ezadar.hr, 36% (20 requests) were made to Ezadar.hr and 13% (7 requests) were made to Mas.nth.ch. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Ezadar.hr.
Page size can be reduced by 71.6 kB (48%)
149.7 kB
78.1 kB
In fact, the total size of M.ezadar.hr main page is 149.7 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. 45% of websites need less resources to load. Javascripts take 93.7 kB which makes up the majority of the site volume.
Potential reduce by 13.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. 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 13.2 kB or 73% of the original size.
Potential reduce by 1.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. M Ezadar images are well optimized though.
Potential reduce by 51.2 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 51.2 kB or 55% of the original size.
Potential reduce by 5.8 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. M.ezadar.hr needs all CSS files to be minified and compressed as it can save up to 5.8 kB or 76% of the original size.
Number of requests can be reduced by 22 (43%)
51
29
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of M Ezadar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
m.ezadar.hr
1664 ms
language-selector.css
281 ms
modernizr-2.6.2.min.js
287 ms
bootstrap.min.css
676 ms
owl.carousel.css
303 ms
main.css
304 ms
layout7_custom_4.css
312 ms
jquery.js
592 ms
jquery-migrate.js
319 ms
jquery-1.11.0.min.js
606 ms
bootstrap.min.js
322 ms
owl.carousel.min.js
346 ms
main.js
346 ms
nav.js
441 ms
ssba.min.js
478 ms
wp-embed.js
478 ms
twemoji.js
537 ms
wp-emoji.js
538 ms
logo_ezadar.png
1424 ms
icon-search.png
230 ms
8989137bf22a6d228990e66a97ac658d_xxl.jpg
806 ms
icon-nav.png
220 ms
3eebb0febb885b862bed600776da9540_xxl.jpg
1142 ms
a24e47cadadfb9bb0be044245c2b6353_xxl.jpg
799 ms
230d7dd339738c9c8868c7f001b6c97e_xxl.jpg
989 ms
16170800763a831e8297f4433b45271b_xxl.jpg
808 ms
f91d96ac6d5bd7303189695376e00042_xxl.jpg
808 ms
2bc3e87c81d211728a095f1923d8a1ba_xxl.jpg
1284 ms
cb5e0c79475b2f05516af93cf28ecd6f_xxl.jpg
1147 ms
4222b52df4ca38c1c25bbc0674925d44_xxl.jpg
1144 ms
adc688bbe6f047ac06a76124f0f20836_xxl.jpg
1150 ms
260800a07b0a6ce0c5d722ff44a16727_xxl.jpg
1153 ms
2c276b11a551b77f574795c078dc81ba_xxl.jpg
1277 ms
8462fdee7fb53d222add5d0b893473b6_xxl.jpg
1423 ms
765185af094fe48b929f62afa1ee9e3d_xxl.jpg
1428 ms
8b585f1f6e3ff8ec4b77844c7e6560e9_xxl.jpg
1437 ms
4f1b0e72d2bbf0eb80224f5dbb67ff7b_xxl.jpg
1295 ms
ed23a30d44efa582056a2a72e003bc9f_xxl.jpg
1552 ms
8731109b3b07acdb5d3a40d56836fe29_xxl.jpg
1849 ms
de40a819ad2fbd195c06e2488c7f5e9a_xxl.jpg
1613 ms
ff79d02bec9360d8e889b3715fe7fc1c_xxl.jpg
1707 ms
mas.jsp
442 ms
ptsans-regular-webfont.woff
359 ms
aleo-italic_0-webfont.woff
379 ms
mas.jsp
454 ms
mas.jsp
435 ms
mas.jsp
435 ms
mas.jsp
445 ms
icon-load.png
232 ms
icon-top.png
237 ms
analytics.js
237 ms
aleo-regular_0-webfont.woff
666 ms
collect
53 ms
verifyIdIframe.jsp
244 ms
mas_imp.jsp
345 ms
m.ezadar.hr accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
m.ezadar.hr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
m.ezadar.hr SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise M.ezadar.hr can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that M.ezadar.hr 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.
m.ezadar.hr
Open Graph description is not detected on the main page of M Ezadar. 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: