46.2 sec in total
4.7 sec
41.1 sec
376 ms
Welcome to 126pu.com homepage info - get ready to check 126 Pu best content right away, or after learning these important things about 126pu.com
聚氨酯联盟是聚氨酯行业专业提供信息与技术共享交流的平台,为氨酯企业及从业人员提供聚氨酯软泡、聚氨酯硬泡、聚氨酯弹性体及海绵发泡经验分享,疑难问题咨询,并邀请了聚氨酯行业著名专家开设专栏讲解生产应用中遇到的各类问题及技巧。定期开办:聚氨酯技术培训、聚氨酯技术转让交流会,聚氨酯软泡技术应用、硬泡技术应用、弹性体技术、发泡设备以及聚氨酯原料价格最新信息等,聚氨酯联盟网行业逐步形成一条完美结合的产业链。
Visit 126pu.comWe analyzed 126pu.com page load time and found that the first response time was 4.7 sec and then it took 41.5 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 7 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
126pu.com performance score
4695 ms
1879 ms
989 ms
1500 ms
1003 ms
Our browser made a total of 154 requests to load all elements on the main page. We found that 79% of them (122 requests) were addressed to the original 126pu.com, 5% (7 requests) were made to Bdimg.share.baidu.com and 3% (5 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain 126pu.com.
Page size can be reduced by 524.9 kB (52%)
1.0 MB
476.5 kB
In fact, the total size of 126pu.com main page is 1.0 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. 35% of websites need less resources to load. Javascripts take 355.2 kB which makes up the majority of the site volume.
Potential reduce by 145.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 145.2 kB or 83% of the original size.
Potential reduce by 52.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. Obviously, 126 Pu needs image optimization as it can save up to 52.4 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 228.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 228.8 kB or 64% of the original size.
Potential reduce by 98.5 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. 126pu.com needs all CSS files to be minified and compressed as it can save up to 98.5 kB or 80% of the original size.
Number of requests can be reduced by 44 (31%)
144
100
The browser has sent 144 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 126 Pu. 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 5 to 1 for CSS and as a result speed up the page load time.
126pu.com
4695 ms
style_8_common.css
1879 ms
style_8_forum_index.css
989 ms
common.js
1500 ms
forum.js
1003 ms
extend_module.css
1484 ms
abase.js
4016 ms
logging.js
1502 ms
md5.js
1507 ms
jquery.js
10336 ms
hdp.js
6035 ms
MSClass.js
1513 ms
bg_html.png
1412 ms
wxbutton.gif
468 ms
logo.png
4479 ms
wechat_login.png
613 ms
qq_login.gif
936 ms
collapsed_no.gif
1111 ms
91f4b23d2cc12060dd6a5d4c8c6092ff.jpg
3211 ms
95581ec53355898853ba52067eafe5ab.jpg
12007 ms
0351657f66d91645c44f79a58200a1fa.jpg
5810 ms
50929b3100b8641927d2058decec3f7b.jpg
12078 ms
c8dad4d36f46a92c0a3725e9386134fd.jpg
20439 ms
2263fccb5a41e0c2423263a8d60b26f9.jpg
9635 ms
70a599f6ff81c33ce03566a65930ac8f.jpg
9113 ms
ddc337cb2af5b5b47bc2e888bd504c04.jpg
20438 ms
25f799e2137b6dc9465bbcabdf10b2d8.jpg
16448 ms
2d335ec1ad3baadffcc749af95f1c945.jpg
13426 ms
bg_toptb.png
1441 ms
153352gmvfrrvzvfcdu1r0.jpg
9129 ms
151408a68n36hr363lh6h6.gif
9751 ms
112501hujwyjuqcpyql8p1.gif
4059 ms
142958rlicrisjzd4czvsr.gif
5215 ms
142823ljs0w0sxsr6xismr.gif
7628 ms
144158pz26212ocqf24zm2.gif
3358 ms
150429fh8kj78ezr87r7j7.jpg
5630 ms
091929nyqdykd7np7qqluf.gif
6017 ms
150554gt99cc97v4vvtoti.jpg
9270 ms
115630p5vcut55tkdvwg32.gif
11853 ms
162503f9f68ffwzb73ke6y.gif
8868 ms
switch_width.gif
7989 ms
tiptitle.js
12209 ms
blockstyle.css
11536 ms
ping.js
512 ms
discuz_tips.js
483 ms
user.png
13971 ms
green.png
14151 ms
common_248_icon.jpg
14152 ms
88.jpg
14441 ms
93.jpg
16324 ms
92.jpg
16349 ms
common_95_icon.jpg
18175 ms
yellow.png
18069 ms
forum.gif
16800 ms
wxqr.jpg
19258 ms
qr.png
17283 ms
logo_wx.png
20428 ms
logo_ft.png
20429 ms
site_qq.jpg
19804 ms
security.png
19740 ms
logo.gif
20225 ms
topnav_s.gif
19815 ms
button_51.gif
530 ms
button_51.gif
493 ms
button_51.gif
481 ms
04_avatar_small.jpg
5750 ms
02_avatar_small.jpg
4451 ms
index.php
503 ms
titlebg.png
12277 ms
30_avatar_small.jpg
4489 ms
53_avatar_small.jpg
4454 ms
mobile.css
88 ms
jquery-1.8.2.min.js
211 ms
57_avatar_small.jpg
4571 ms
b0.png
10 ms
h.js
2762 ms
35_avatar_small.jpg
6083 ms
noavatar_small.gif
6646 ms
48_avatar_small.jpg
4556 ms
18_avatar_small.jpg
4411 ms
98_avatar_small.jpg
4708 ms
03_avatar_small.jpg
5277 ms
43_avatar_small.jpg
4981 ms
noavatar_small.gif
4209 ms
71_avatar_small.jpg
4309 ms
53_avatar_small.jpg
4195 ms
35_avatar_small.jpg
7008 ms
53_avatar_small.jpg
4189 ms
36_avatar_small.jpg
4498 ms
avatar.php
19581 ms
26_avatar_small.jpg
4166 ms
noavatar_small.gif
4215 ms
89_avatar_small.jpg
4553 ms
93_avatar_small.jpg
4429 ms
17_avatar_small.jpg
4514 ms
21.gif
1009 ms
b0.png
55 ms
hm.gif
420 ms
96_avatar_small.jpg
4356 ms
42_avatar_small.jpg
4415 ms
noavatar_small.gif
6609 ms
noavatar_small.gif
4501 ms
noavatar_small.gif
4594 ms
47_avatar_small.jpg
4424 ms
noavatar_small.gif
5471 ms
jz52top3.png
8925 ms
share.js
1126 ms
toss_11.gif
237 ms
OTQ5OTg0NQ==.js
562 ms
stat.php
862 ms
noavatar_small.gif
4400 ms
hm.gif
3308 ms
47_avatar_small.jpg
4607 ms
55_avatar_small.jpg
4818 ms
stat.htm
698 ms
core.php
1157 ms
noavatar_small.gif
4596 ms
noavatar_small.gif
4730 ms
9.gif
755 ms
pic1.gif
2669 ms
h.js
609 ms
hm.gif
343 ms
share_api.js
377 ms
share_view.js
774 ms
app.gif
1061 ms
tangram.js
20102 ms
api_base.js
784 ms
px.png
4425 ms
pn.png
4518 ms
view_base.js
554 ms
search.png
5030 ms
pt_item.png
4484 ms
chart.png
4603 ms
bg_title_bbs.gif
4562 ms
bg_ft.png
20314 ms
01_avatar_small.jpg
8342 ms
noavatar_small.gif
3644 ms
noavatar_small.gif
3654 ms
00_avatar_big.jpg
5960 ms
logger.js
332 ms
noavatar_small.gif
3103 ms
noavatar_small.gif
3150 ms
11_avatar_small.jpg
3216 ms
noavatar_small.gif
3074 ms
09_avatar_small.jpg
4182 ms
noavatar_small.gif
4776 ms
noavatar_small.gif
3039 ms
noavatar_small.gif
4440 ms
06_avatar_small.jpg
5050 ms
noavatar_small.gif
5536 ms
07_avatar_small.jpg
4681 ms
00_avatar_small.jpg
4933 ms
04_avatar_small.jpg
5927 ms
01_avatar_small.jpg
6520 ms
126pu.com SEO score
![]()
ZH
![]()
N/A
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 126pu.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 126pu.com main page’s claimed encoding is gbk. 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.
126pu.com
Open Graph description is not detected on the main page of 126 Pu. 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: