5.3 sec in total
681 ms
4.2 sec
435 ms
Visit myzeezo.com now to see the best up-to-date Myzeezo content and also check out these interesting facts you probably never knew about myzeezo.com
Visit myzeezo.comWe analyzed Myzeezo.com page load time and found that the first response time was 681 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
myzeezo.com performance score
681 ms
518 ms
284 ms
220 ms
194 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 72% of them (53 requests) were addressed to the original Myzeezo.com, 11% (8 requests) were made to Maps.gstatic.com and 9% (7 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Myzeezo.com.
Page size can be reduced by 750.8 kB (34%)
2.2 MB
1.4 MB
In fact, the total size of Myzeezo.com main page is 2.2 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.2 MB which makes up the majority of the site volume.
Potential reduce by 58.1 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 7.4 kB, which is 11% 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 58.1 kB or 84% of the original size.
Potential reduce by 61.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. Myzeezo images are well optimized though.
Potential reduce by 455.3 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 455.3 kB or 67% of the original size.
Potential reduce by 176.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. Myzeezo.com needs all CSS files to be minified and compressed as it can save up to 176.0 kB or 76% of the original size.
Number of requests can be reduced by 36 (55%)
65
29
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Myzeezo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
www.myzeezo.com
681 ms
bootstrap.min.css
518 ms
font-awesome.css
284 ms
blog.css
220 ms
ie10-viewport-bug-workaround.css
194 ms
ie-emulation-modes-warning.js
182 ms
theme-my-login.css
179 ms
styles.css
245 ms
css
68 ms
genericons.css
363 ms
jquery.js
508 ms
jquery-migrate.min.js
765 ms
trigger_buttons.min.css
804 ms
jquery.fancybox-1.3.4.min.css
817 ms
font-awesome.min.css
890 ms
nextgen_basic_thumbnails.min.css
825 ms
style.min.css
826 ms
nggallery.css
833 ms
jquery.min.js
1285 ms
bootstrap.min.js
897 ms
ie10-viewport-bug-workaround.js
775 ms
js
41 ms
jquery.form.min.js
776 ms
scripts.js
819 ms
functions.js
846 ms
ajax.min.js
842 ms
common.min.js
845 ms
nextgen_basic_thumbnails.min.js
853 ms
lightbox_context.min.js
920 ms
jquery.easing-1.3.pack.js
921 ms
jquery.fancybox-1.3.4.pack.js
922 ms
nextgen_fancybox_init.min.js
915 ms
wp-emoji-release.min.js
560 ms
Banner32.jpg
838 ms
Banner13.jpg
629 ms
federal-lights.jpg
467 ms
young-empires-takeover-bowery.jpg
629 ms
MinerBa640.jpg
547 ms
Cate-Blanchett-Carol-Cat-Eye-Sunglasses-752x440.jpg
629 ms
Rembrandt-blog480.jpg
671 ms
blos-sides.jpg
630 ms
search.png
527 ms
thumbs_gallery-eight.jpg
528 ms
thumbs_gallery-five.jpg
560 ms
thumbs_gallery-four.jpg
594 ms
thumbs_gallery-one.jpg
589 ms
thumbs_gallery-seven.jpg
616 ms
thumbs_gallery-six.jpg
620 ms
thumbs_gallery-three.jpg
621 ms
thumbs_gallery-two.jpg
650 ms
thumbs_gallery-four-1.jpg
655 ms
banner.jpg
824 ms
fontawesome-webfont.woff
855 ms
fontawesome-webfont.woff
743 ms
Oswald-Bold_gdi.woff
684 ms
common.js
23 ms
map.js
35 ms
util.js
23 ms
onion.js
20 ms
controls.js
31 ms
transparent.png
102 ms
css
46 ms
marker.js
23 ms
google4.png
90 ms
mapcnt6.png
81 ms
sv5.png
82 ms
tmapctrl.png
90 ms
cb_scout5.png
113 ms
tmapctrl4.png
90 ms
imgs8.png
98 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
41 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
59 ms
Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf
59 ms
d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf
65 ms
myzeezo.com SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Myzeezo.com 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 English. Our system also found out that Myzeezo.com 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.
myzeezo.com
Open Graph description is not detected on the main page of Myzeezo. 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: