58.3 sec in total
1.2 sec
56.2 sec
855 ms
Click here to check amazing Yzmg content for United States. Otherwise, check out these important facts you probably never knew about yzmg.com
亿智蘑菇是深入移动互联网与智能硬件行业的众测科技媒体,向厂商及用户提供媒体资讯、智能硬件试用、酷玩产品导购、社会化媒体传播等多元服务。
Visit yzmg.comWe analyzed Yzmg.com page load time and found that the first response time was 1.2 sec and then it took 57.1 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 6 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
yzmg.com performance score
1243 ms
5691 ms
374 ms
1176 ms
128 ms
Our browser made a total of 153 requests to load all elements on the main page. We found that 6% of them (9 requests) were addressed to the original Yzmg.com, 64% (98 requests) were made to Images.yzmg.com and 7% (11 requests) were made to Yjs.yzmg.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source T12.baidu.com.
Page size can be reduced by 787.0 kB (14%)
5.4 MB
4.7 MB
In fact, the total size of Yzmg.com main page is 5.4 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. 45% of websites need less resources to load. Images take 4.8 MB which makes up the majority of the site volume.
Potential reduce by 132.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. 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 132.1 kB or 80% of the original size.
Potential reduce by 338.1 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. Yzmg images are well optimized though.
Potential reduce by 293.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 293.5 kB or 67% of the original size.
Potential reduce by 23.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. Yzmg.com needs all CSS files to be minified and compressed as it can save up to 23.3 kB or 74% of the original size.
Number of requests can be reduced by 28 (19%)
144
116
The browser has sent 144 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yzmg. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and as a result speed up the page load time.
yzmg.com
1243 ms
www.yzmg.com
5691 ms
index.css
374 ms
index.js
1176 ms
jquery.min.js
128 ms
owl.carousel.min.js
112 ms
owl.demo.js
104 ms
wenji-index-menu-bottom.js
1040 ms
logo.png
89 ms
mgfa.png
280 ms
16-01-11-79-26228.jpg
1344 ms
14-47-13-15-3387.jpg
1275 ms
13-47-55-96-16987.jpg
2641 ms
11-40-35-97-16987.jpg
1607 ms
19-04-20-25-9609.png
1346 ms
top_line.png
2113 ms
mgcp.js
659 ms
09-25-16-11-14419.jpg
1355 ms
17-19-58-13-10131.jpg
2798 ms
mgstup.png
1949 ms
appa.png
2710 ms
appios.png
2384 ms
17-13-03-93-65.jpeg
4578 ms
17-10-03-15-16987.jpg
3226 ms
17-12-39-73-26228.png
15614 ms
16-48-56-33-26228.png
6863 ms
16-46-52-72-14419.jpg
3953 ms
16-48-18-56-3387.jpg
3646 ms
16-43-33-82-26228.png
5444 ms
16-13-00-15-26228.jpg
5010 ms
16-11-56-18-3387.jpg
4722 ms
15-08-16-82-16987.png
6491 ms
14-49-42-50-26228.png
6598 ms
14-47-56-26-16987.png
7208 ms
14-41-06-96-26228.png
15494 ms
17-11-13-89-3387.jpg
7417 ms
13-40-12-91-26228.png
7275 ms
17-05-21-65-10131.jpg
7490 ms
15-40-00-28-3387.jpg
12745 ms
13-42-05-58-3387.jpg
7950 ms
10-11-11-29-26228.jpg
13248 ms
17-07-13-35-3387.jpg
9155 ms
10-33-53-54-26228.jpg
8597 ms
16-00-14-39-3387.jpg
9871 ms
14-28-57-73-16987.jpg
12466 ms
14-03-17-79-16987.jpg
11122 ms
13-52-11-41-3387.jpg
12022 ms
13-44-38-66-3387.jpg
13468 ms
1113_lqf_techHP_icons_V11.png
462 ms
share.png
478 ms
11-13-28-67-3387.jpg
12548 ms
16-47-20-22-3387.jpg
12699 ms
10-57-10-17-26228.jpg
12863 ms
17-25-17-81-65.jpg
12932 ms
16-26-51-55-10131.jpg
13631 ms
16-14-01-74-65.jpg
12331 ms
14-49-18-73-65.jpg
13408 ms
14-39-41-40-65.jpg
13097 ms
14-32-11-59-65.jpg
17357 ms
tupian.index.middle.js
4607 ms
c.js
1065 ms
tupian.index.middle.3.js
4315 ms
tupian.index.right.top.js
823 ms
14-22-14-45-65.png
13855 ms
bds_s_v2.js
1932 ms
stat.php
3532 ms
aq_auth.js
8009 ms
jquery.qrcode.min.js
95 ms
apps.png
311 ms
appb.png
55 ms
wechats.png
148 ms
wechatb.png
174 ms
14-06-47-39-10131.png
14338 ms
down_btn.png
15770 ms
16-17-14-88-10131.jpg
13327 ms
16-08-21-80-10131.jpg
12164 ms
16-03-34-22-10131.jpg
13171 ms
16-00-41-86-65.jpg
13386 ms
15-59-04-43-10131.jpg
13488 ms
15-55-21-82-65.jpg
12154 ms
19-28-13-98-9609.png
13315 ms
17-25-59-40-9609.png
19625 ms
17-19-57-27-9609.png
13701 ms
17-13-32-72-9609.png
14212 ms
ecim
1031 ms
16-52-42-84-9609.png
13469 ms
bdsstyle.css
408 ms
16-45-29-41-9609.png
15093 ms
stat.htm
298 ms
core.php
810 ms
16-33-03-67-9609.jpg
13559 ms
ecim
532 ms
16-27-48-72-14419.jpg
14145 ms
9.gif
930 ms
adx.php
912 ms
u=4051960355,4260193977&fm=76
1363 ms
u=1146189510,1448531799&fm=76
19503 ms
bg.png
1999 ms
u=2094864468,2265193632&fm=76
1123 ms
u=1001317196,1216311997&fm=76
6560 ms
u=1928637557,2586947551&fm=76
20492 ms
u=1888141085,2579454619&fm=76
20491 ms
u=3280280684,3595811120&fm=76
2930 ms
reduce_bd-logo1_oper.png
20473 ms
17-04-23-87-65.jpg
12873 ms
app.gif
2005 ms
16-45-01-96-10131.jpg
12939 ms
15-22-06-42-10131.jpg
14455 ms
task.js.php
1650 ms
14-38-48-41-10131.jpg
10690 ms
14-09-39-25-65.jpg
14179 ms
11-41-17-81-65.jpg
12181 ms
toplogin1.jpg
2886 ms
2270 ms
toplogin2.jpg
3866 ms
toploginsub.jpg
2796 ms
toploginreg.jpg
4388 ms
11-05-40-39-65.jpg
13800 ms
11-23-01-85-65.jpg
11310 ms
16-17-05-63-14419.jpg
12979 ms
15-12-15-48-14419.jpg
11596 ms
14-12-16-28-14419.jpg
11544 ms
14-02-21-42-14419.jpg
11525 ms
13-55-53-65-14419.jpg
11706 ms
11-05-14-64-14419.jpg
12172 ms
10-58-18-21-14419.jpg
12109 ms
hy_124x47.png
12484 ms
10-47-29-76-14419.jpg
12775 ms
10-37-16-24-14419.jpg
12224 ms
10-34-57-67-9609.jpg
12383 ms
18-19-52-95-9609.jpg
11669 ms
13-26-56-71-14419.jpg
11343 ms
13-19-59-48-14419.jpg
11428 ms
13-14-28-15-14419.jpg
11367 ms
ico.png
10250 ms
565c13bdd25d5.jpg
11141 ms
567d02a83239a.gif
10325 ms
56d3a2751883d.jpg
10707 ms
56d68168ddc77.jpg
10330 ms
568f61619ec5d.gif
9964 ms
5631e70ac4b3b.png
10986 ms
5631e77eefd75.png
8869 ms
top_qq.jpg
8757 ms
ico.png
8242 ms
bg16.png
9059 ms
bg15.png
8414 ms
closefeedback.min.js
612 ms
reduce_promotion_oper.png
661 ms
bd_logo.png
659 ms
bg_rb.png
667 ms
o.htm
1832 ms
ac.js
2478 ms
wh.js
19582 ms
yzmg.com SEO score
ZH
N/A
GB2312
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yzmg.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Yzmg.com main page’s claimed encoding is gb2312. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
yzmg.com
Open Graph description is not detected on the main page of Yzmg. 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: