43.8 sec in total
3.1 sec
40.3 sec
380 ms
Click here to check amazing Iezk content. Otherwise, check out these important facts you probably never knew about iezk.com
抢红包,薅羊毛,白菜价,网购省钱第一站
Visit iezk.comWe analyzed Iezk.com page load time and found that the first response time was 3.1 sec and then it took 40.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 7 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
iezk.com performance score
3062 ms
6061 ms
3515 ms
1509 ms
2873 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 47% of them (33 requests) were addressed to the original Iezk.com, 17% (12 requests) were made to Asearch.alicdn.com and 6% (4 requests) were made to Img.alicdn.com. The less responsive or slowest element that took the longest time to load (19.8 sec) belongs to the original domain Iezk.com.
Page size can be reduced by 195.3 kB (61%)
322.5 kB
127.3 kB
In fact, the total size of Iezk.com main page is 322.5 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. 30% of websites need less resources to load. Javascripts take 191.7 kB which makes up the majority of the site volume.
Potential reduce by 45.0 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 45.0 kB or 82% of the original size.
Potential reduce by 1.7 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. Iezk images are well optimized though.
Potential reduce by 115.8 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 115.8 kB or 60% 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. Iezk.com needs all CSS files to be minified and compressed as it can save up to 32.7 kB or 82% of the original size.
Number of requests can be reduced by 22 (37%)
60
38
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Iezk. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and as a result speed up the page load time.
www.iezk.com
3062 ms
wp-emoji-release.min.js
6061 ms
style.css
3515 ms
mediaqueries.css
1509 ms
wp-sns-share.js
2873 ms
jquery.min.js
3843 ms
script.js
2484 ms
jquery.sidr.min.js
2701 ms
jquery.infinitescroll.min.js
6299 ms
wp-embed.min.js
2263 ms
%E9%98%BF%E9%87%8C%E7%BD%97%E7%81%AB%E7%81%AB%E5%85%94-300x300.jpg
16553 ms
%E5%B0%8F%E9%BE%99%E5%93%88%E5%BD%BC%E5%A9%B4%E5%84%BF%E6%89%8B%E6%8E%A8%E8%BD%A6-300x300.jpg
2914 ms
%E6%8A%98%E5%8F%A0%E8%A1%A3%E6%9E%B6%E4%BE%BF%E6%90%BA%E5%BC%8F%E8%A1%A3%E6%9E%B67.5%E5%8C%85%E9%82%AE-300x298.jpg
3701 ms
9.9%E5%85%83%E5%8C%85%E9%82%AE%EF%BC%8C%E5%84%BF%E7%AB%A5%E7%94%B5%E5%AD%90%E7%90%B4%E5%B8%A6%E9%BA%A6%E5%85%8B%E9%A3%8E-300x300.jpg
16532 ms
TB2yZuoiVXXXXaEXXXXXXXXXXXX_1848621775.jpg_430x430q90-300x300.jpg
9812 ms
TB2W9rliFXXXXcoXXXXXXXXXXXX_741924377.jpg_430x430q90-300x300.jpg
6074 ms
%E7%BE%8E%E7%9A%84%E6%99%BA%E8%83%BD%E5%8E%8B%E5%8A%9B%E9%94%85%E5%8F%8C12%E9%9B%B6%E7%82%B9%E5%89%8D100%E5%90%8D238%E5%85%83-300x300.jpg
7609 ms
%E7%BE%8E%E7%9A%84%E6%99%BA%E8%83%BD12%E5%B0%8F%E6%97%B6%E9%A2%84%E7%BA%A6%E5%8E%8B%E5%8A%9B%E9%94%85-300x300.jpg
9029 ms
default.jpg
8355 ms
Pure%E4%BC%8A%E8%8A%99%E4%B8%BD2015%E5%86%AC%E6%96%B0%E6%AC%BE%E7%BF%BB%E9%A2%86%E6%AF%9B%E5%91%A2%E5%A4%96%E5%A5%97499-300x300.jpg
14841 ms
%E6%9E%81%E5%9C%B0%E9%BC%A0%E6%97%B6%E5%B0%9A%E5%84%BF%E7%AB%A5%E7%BE%BD%E7%BB%92%E6%9C%8D%E5%86%85%E8%83%86-17%E5%8C%85%E9%82%AE-300x300.jpg
11315 ms
%E7%94%B7%E5%A5%B3%E7%AB%A5%E7%BE%BD%E7%BB%92%E6%A3%89%E8%83%8C%E5%BF%83-29%E5%8C%85%E9%82%AE-300x300.png
19756 ms
%E4%BF%AE%E8%BA%AB%E9%95%BF%E6%AC%BE%E9%95%BF%E8%A2%96%E9%AB%98%E9%A2%86%E7%BE%8A%E6%AF%9B%E6%89%93%E5%BA%95%E8%A1%AB-%E5%A4%A9%E7%8C%AB-51.8%E5%85%83%E5%8C%85%E9%82%AE-300x300.jpg
12901 ms
%E6%96%97%E7%AF%B7%E5%BC%8F%E5%A6%AE%E5%AD%90%E5%A4%A7%E8%A1%A3-%E5%A4%A9%E7%8C%AB-87.8%E5%85%83%E5%8C%85%E9%82%AE-300x300.jpg
15567 ms
19.9%E7%BE%8A%E7%BB%92%E6%8A%A4%E8%86%9D-300x300.jpg
19757 ms
%E9%98%BF%E6%9D%8E%E7%BD%97%E7%81%AB%E7%81%AB%E5%85%94R1%E6%99%BA%E8%83%BD%E7%94%B5%E5%AD%90%E6%91%87%E9%93%83-300x300.jpg
19757 ms
%E6%B3%A2%E5%8F%B8%E7%99%BB%E5%A4%A9%E9%B9%85%E7%BB%92%E9%AB%98%E8%85%B0%E6%89%93%E5%BA%95%E9%93%85%E7%AC%94%E8%A3%A4%EF%BC%8C%E5%A4%A9%E7%8C%AB49%E5%85%83-300x300.jpg
18057 ms
%E7%BE%8E%E7%9A%84%E5%A4%A7%E7%81%AB%E5%8A%9B%E7%94%B5%E7%A3%81%E7%82%89%E5%A4%A9%E7%8C%AB%E5%8F%8C%E5%8D%81%E4%BA%8C199%E5%85%83-300x300.jpg
19756 ms
%E8%B6%85%E4%BA%BA%E5%89%83%E9%A1%BB%E5%88%8055-300x300.jpg
19757 ms
%E5%A4%A9%E7%8C%AB%E8%B6%85%E5%B8%82320.jpg
19757 ms
ex
1890 ms
ality.woff
19682 ms
hm.js
550 ms
hm.gif
283 ms
tanxssp.js
341 ms
ex
827 ms
acbeacon2.html
446 ms
spf
783 ms
TB1DmcoJXXXXXavXpXXXXXXXXXX-26-26.png
400 ms
creation-164857uaSd33GHMrk-437386.html
449 ms
TB1Lt7aJXXXXXcjXVXXXXXXXXXX-117-26.png
399 ms
TB1rRQpJXXXXXcvXXXXXXXXXXXX-40-26.png
400 ms
TB1upAiJXXXXXa5aXXXXXXXXXXX-116-30.png
399 ms
loading.gif
17116 ms
t.gif
1046 ms
tanxclick.js
27 ms
tns.simba.taobao.com
4941 ms
app.gif
807 ms
um.js
363 ms
img
1132 ms
um.json
2951 ms
getDeviceInfo
1215 ms
TB2HOndlpXXXXX8XpXXXXXXXXXX_!!0-saturn_solar.jpg_sum.jpg
102 ms
feature_v1.htm
3143 ms
TB2HOndlpXXXXX8XpXXXXXXXXXX_!!0-saturn_solar.jpg_250x250.jpg
123 ms
TB2CSgampXXXXcgXXXXXXXXXXXX_!!0-saturn_solar.jpg_250x250.jpg
104 ms
TB2auwIkVXXXXX3XpXXXXXXXXXX_!!0-saturn_solar.jpg_250x250.jpg
107 ms
TB23qb7lVXXXXakXXXXXXXXXXXX_!!0-saturn_solar.jpg_250x250.jpg
108 ms
TB2LS9pmpXXXXcmXXXXXXXXXXXX_!!0-saturn_solar.jpg_250x250.jpg
108 ms
TB21DXFlVXXXXXuXXXXXXXXXXXX_!!0-saturn_solar.jpg_250x250.jpg
125 ms
TB2J8LImpXXXXbRXpXXXXXXXXXX_!!0-saturn_solar.jpg_250x250.jpg
120 ms
TB2zk55kpXXXXabXXXXXXXXXXXX_!!0-saturn_solar.jpg_250x250.jpg
131 ms
TB2QI6ZlFXXXXcXXpXXXXXXXXXX_!!0-saturn_solar.jpg_250x250.jpg
116 ms
TB2uDuQlXXXXXcYXXXXXXXXXXXX_!!0-saturn_solar.jpg_250x250.jpg
116 ms
TB28.myiFXXXXbNXXXXXXXXXXXX_!!33693409-0-saturn_solar.jpg_250x250.jpg
133 ms
TB11KimHpXXXXXJXXXXQKC3FVXX-27-59.png
294 ms
TB1Mng.HpXXXXb4XFXX1qpgFpXX-20-14.gif
137 ms
TB1LKo.HpXXXXbiXFXX91dEGXXX-29-16.png
643 ms
getDeviceInfo
967 ms
ality.ttf
10387 ms
iezk.com SEO score
ZH
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iezk.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that Iezk.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.
iezk.com
Open Graph description is not detected on the main page of Iezk. 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: