2.8 sec in total
306 ms
2 sec
413 ms
Welcome to neezz.com homepage info - get ready to check Neezz best content right away, or after learning these important things about neezz.com
Visit neezz.comWe analyzed Neezz.com page load time and found that the first response time was 306 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
neezz.com performance score
306 ms
589 ms
81 ms
274 ms
134 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 93% of them (96 requests) were addressed to the original Neezz.com, 3% (3 requests) were made to Staticxx.facebook.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (638 ms) belongs to the original domain Neezz.com.
Page size can be reduced by 379.5 kB (45%)
846.4 kB
466.9 kB
In fact, the total size of Neezz.com main page is 846.4 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. Javascripts take 386.5 kB which makes up the majority of the site volume.
Potential reduce by 53.6 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 53.6 kB or 81% of the original size.
Potential reduce by 27.6 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. Neezz images are well optimized though.
Potential reduce by 265.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 265.5 kB or 69% of the original size.
Potential reduce by 32.7 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. Neezz.com needs all CSS files to be minified and compressed as it can save up to 32.7 kB or 80% of the original size.
Number of requests can be reduced by 3 (5%)
57
54
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Neezz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
neezz.com
306 ms
www.neezz.com
589 ms
style.1.3.css
81 ms
style.1.3.css
274 ms
all.js
134 ms
jquery.1.3.js
551 ms
m.1.3.js
316 ms
ga.js
42 ms
user25.jpg
159 ms
1319370_1434703990.jpg
158 ms
1319367_1433957422.jpg
163 ms
1319366_1433956440.jpg
170 ms
1319357_1382422492.jpg
179 ms
1319355_1380871779.jpg
236 ms
1319349_1375197180.jpg
237 ms
290086_1355383827.jpg
241 ms
1319279_1362830999.jpg
256 ms
1319278_1362783200.jpg
256 ms
1316528_1360742386.jpg
312 ms
1305174_1343081889.jpg
315 ms
1305173_1343081889.jpg
321 ms
1305172_1343081888.jpg
446 ms
1305171_1343081888.jpg
444 ms
1305170_1343081886.jpg
448 ms
1305169_1343081886.jpg
449 ms
1305168_1343081885.jpg
473 ms
1305167_1343081885.jpg
472 ms
1305166_1343081885.jpg
472 ms
1305165_1343081884.jpg
472 ms
1305162_1343081883.jpg
531 ms
1305161_1343081882.jpg
533 ms
1305160_1343081882.jpg
537 ms
1305159_1343081881.jpg
533 ms
1305158_1343081880.jpg
565 ms
1305157_1343081880.jpg
565 ms
1305156_1343081880.jpg
609 ms
1305155_1343081879.jpg
610 ms
1305154_1343081879.jpg
612 ms
1305153_1343081875.jpg
619 ms
1305152_1343081875.jpg
638 ms
nz-sprite.v2.png
165 ms
neezz_gradient.png
80 ms
__utm.gif
12 ms
1305151_1343081874.jpg
548 ms
user25.jpg
83 ms
1319370_1434703990.jpg
101 ms
1319367_1433957422.jpg
154 ms
1319366_1433956440.jpg
149 ms
1305150_1343081874.jpg
522 ms
1305149_1343081874.jpg
524 ms
1305148_1343081874.jpg
528 ms
1305147_1343081874.jpg
536 ms
1319357_1382422492.jpg
297 ms
1319355_1380871779.jpg
92 ms
1319349_1375197180.jpg
211 ms
1305146_1343081873.jpg
486 ms
1305145_1343081873.jpg
486 ms
1305144_1343081872.jpg
533 ms
290086_1355383827.jpg
209 ms
1319279_1362830999.jpg
219 ms
1319278_1362783200.jpg
218 ms
1305143_1343081872.jpg
516 ms
1305142_1343081872.jpg
523 ms
mosquito.png
540 ms
1316528_1360742386.jpg
163 ms
1305174_1343081889.jpg
161 ms
1305173_1343081889.jpg
167 ms
122 ms
1305171_1343081888.jpg
94 ms
1305172_1343081888.jpg
86 ms
1305170_1343081886.jpg
88 ms
1305169_1343081886.jpg
83 ms
xd_arbiter.php
79 ms
xd_arbiter.php
134 ms
1305167_1343081885.jpg
98 ms
1305168_1343081885.jpg
97 ms
1305165_1343081884.jpg
140 ms
1305166_1343081885.jpg
140 ms
1305164_1343081884.jpg
141 ms
1305163_1343081884.jpg
141 ms
xd_arbiter.php
49 ms
1305162_1343081883.jpg
112 ms
1305161_1343081882.jpg
106 ms
1305159_1343081881.jpg
152 ms
1305160_1343081882.jpg
150 ms
1305158_1343081880.jpg
130 ms
1305157_1343081880.jpg
134 ms
1305156_1343081880.jpg
106 ms
1305155_1343081879.jpg
120 ms
1305154_1343081879.jpg
150 ms
1305153_1343081875.jpg
145 ms
1305152_1343081875.jpg
130 ms
1305151_1343081874.jpg
141 ms
1305150_1343081874.jpg
104 ms
1305149_1343081874.jpg
121 ms
1305148_1343081874.jpg
146 ms
1305147_1343081874.jpg
138 ms
1305146_1343081873.jpg
131 ms
1305145_1343081873.jpg
144 ms
1305144_1343081872.jpg
104 ms
1305143_1343081872.jpg
131 ms
1305142_1343081872.jpg
146 ms
mosquito.png
132 ms
neezz.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Neezz.com 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 Neezz.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.
neezz.com
Open Graph description is not detected on the main page of Neezz. 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: