6.8 sec in total
1.3 sec
5.2 sec
299 ms
Visit 38.hn now to see the best up-to-date 38 content and also check out these interesting facts you probably never knew about 38.hn
绿之韵集团
Visit 38.hnWe analyzed 38.hn page load time and found that the first response time was 1.3 sec and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
38.hn performance score
1264 ms
254 ms
437 ms
654 ms
440 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that all of those requests were addressed to 38.hn and no external sources were called. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain 38.hn.
Page size can be reduced by 549.8 kB (17%)
3.2 MB
2.6 MB
In fact, the total size of 38.hn main page is 3.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. 35% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 26.8 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 26.8 kB or 77% of the original size.
Potential reduce by 78.3 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. 38 images are well optimized though.
Potential reduce by 325.4 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 325.4 kB or 75% of the original size.
Potential reduce by 119.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. 38.hn needs all CSS files to be minified and compressed as it can save up to 119.3 kB or 84% of the original size.
Number of requests can be reduced by 16 (25%)
65
49
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 38. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
38.hn
1264 ms
common.css
254 ms
index.css
437 ms
jquery-1.9.1.js
654 ms
jquery.js
440 ms
jquery-ui-1.js
702 ms
beliving.js
440 ms
common.js
472 ms
transport.js
669 ms
common.js
668 ms
check_login.js
668 ms
user.js
721 ms
jquery.lazyload.js
867 ms
public.js
871 ms
jquery.J_BPWidget.js
874 ms
logo_beliving.png
232 ms
brand_nxjkhl.png
643 ms
brand_yyzb.png
667 ms
brand_glny.png
793 ms
brand_jcns.png
820 ms
brand_bjyp.png
1009 ms
brand_jjxl.png
1189 ms
member.png
866 ms
goodcart.png
888 ms
fwrx.png
1012 ms
homebanner1.jpg
1493 ms
homebanner3.jpg
1503 ms
homebanner4.jpg
1526 ms
ico_main_banner1.png
1234 ms
ico_main_banner2.png
1233 ms
middlebanner.jpg
2137 ms
ningjiao.png
1664 ms
nvertie.png
1507 ms
nanyonghudian.jpg
1714 ms
product_glt.jpg
1738 ms
new_product_banner2.jpg
1754 ms
new_product_banner4.jpg
1762 ms
new_product_banner5.jpg
1951 ms
new_product_banner6.jpg
1975 ms
new_product_banner7.jpg
1994 ms
rightbanner.jpg
1989 ms
product_132.png
2015 ms
product_97.png
2218 ms
product_46.png
2239 ms
product_31.png
2249 ms
product_29.png
2256 ms
product_21.png
2240 ms
footerlogo.png
2351 ms
xinyong.png
2285 ms
bg_gnb_m1_layer.png
2300 ms
login_bg.png
2287 ms
flow.php
2132 ms
btn_srch.png
1909 ms
cpzx.png
1870 ms
fkzd.png
1859 ms
xwzx.png
1814 ms
syjc.png
1904 ms
yszq.png
1871 ms
bg_banner_arrow.png
1886 ms
bg_line.gif
1711 ms
bg_tit.png
1759 ms
btn_control.png
1774 ms
logo_beliving2.png
1598 ms
bg_bar.png
1613 ms
btn_paging.png
1609 ms
grey.gif
1684 ms
38.hn SEO score
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 38.hn 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 38.hn 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.
38.hn
Open Graph description is not detected on the main page of 38. 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: