10 sec in total
677 ms
8.5 sec
797 ms
Click here to check amazing Buildface content for China. Otherwise, check out these important facts you probably never knew about buildface.com
筑脸网为建筑行业上下游企业提供材价查询服务,采购管理系统,供应商管理系统,项目成本管控系统,工程项目信息,工程成本控制服务等;筑脸为全国建筑行业人士与中小建筑建材企业生成一个一个筑脸,构筑建筑产业互联网生态圈,提供找人脉,找资源等服务。
Visit buildface.comWe analyzed Buildface.com page load time and found that the first response time was 677 ms and then it took 9.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
buildface.com performance score
name
value
score
weighting
Value6.0 s
3/100
10%
Value13.0 s
0/100
25%
Value10.3 s
8/100
10%
Value20 ms
100/100
30%
Value0.409
24/100
15%
Value8.9 s
35/100
10%
677 ms
2053 ms
641 ms
596 ms
830 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 33% of them (27 requests) were addressed to the original Buildface.com, 28% (23 requests) were made to Cdn.buildface.com and 22% (18 requests) were made to Pic.buildface.com. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Buildface.com.
Page size can be reduced by 954.3 kB (17%)
5.7 MB
4.7 MB
In fact, the total size of Buildface.com main page is 5.7 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. 50% of websites need less resources to load. Images take 5.1 MB which makes up the majority of the site volume.
Potential reduce by 42.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. This page needs HTML code to be minified as it can gain 9.5 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 42.1 kB or 77% of the original size.
Potential reduce by 555.9 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, Buildface needs image optimization as it can save up to 555.9 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 104.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 104.5 kB or 67% of the original size.
Potential reduce by 251.8 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. Buildface.com needs all CSS files to be minified and compressed as it can save up to 251.8 kB or 85% of the original size.
Number of requests can be reduced by 11 (14%)
76
65
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Buildface. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
buildface.com
677 ms
www.buildface.com
2053 ms
bootstrap.min.css
641 ms
iconfont.css
596 ms
B.css
830 ms
city.css
1069 ms
font_4130297_8qco6rusaxx.css
24 ms
jquery-3.2.1.min.js
1088 ms
jquery.form.min.js
35 ms
layer.min.js
52 ms
popper.min.js
869 ms
bootstrap.min.js
1186 ms
font_768565_fd07h6gjuk.css
9 ms
1200_6580008b46d13.jpg
1407 ms
4ccd911389f6a79a175f341cbe4e4953.jpeg
1312 ms
pa
400 ms
pa
404 ms
pa
406 ms
logo_in.gif
201 ms
headmenu.gif
208 ms
app_logo.png
218 ms
yyz_banner.png
2638 ms
hz_banner.png
3632 ms
yuanxiu_banner.png
3106 ms
zlqz.jpg
3249 ms
zlxmt.jpg
630 ms
caicai_banner.png
653 ms
qhzy.jpg
1244 ms
s-app-erwm.png
871 ms
s-weixin-erwm.png
2394 ms
beian.png
1452 ms
zlewmimg1.jpg
1660 ms
zlewmimg2.jpg
1868 ms
zlewmimg3.jpg
2282 ms
index.gif
2489 ms
1200_6396be317fd98.jpg
1232 ms
1200_648bd44b0b097.jpg
1498 ms
6040810b98480.gif
1709 ms
6647063ab9737.gif
1074 ms
361_6585516f1e796.jpg
1289 ms
361_604f22a61a004.jpg
1288 ms
361_6040847a66d50.jpg
1440 ms
607953c6c2d0d.gif
1501 ms
3555f1bb0e8fdc754aa06f8ee2c61cfd.jpeg
1010 ms
8e840e614f8e13e729c0e0329cce0b38.jpeg
1214 ms
layer.css
197 ms
font_4130297_8qco6rusaxx.woff
566 ms
font_768565_fd07h6gjuk.woff
907 ms
hm.js
1112 ms
lists.html
3282 ms
hm.gif
311 ms
button_21.gif
916 ms
button_21.gif
918 ms
button_21.gif
921 ms
4ccd911389f6a79a175f341cbe4e4953.jpeg!n43
270 ms
400_6549d3f0a58ea.jpg
447 ms
400_6549d400a6f9d.jpg
430 ms
400_6549d40f78183.jpg
395 ms
400_6549fa7442e10.jpg
220 ms
400_6549fa91b53e3.jpg
434 ms
400_6549faa49ddae.jpg
221 ms
400_5f9fad9220fd9.png
1111 ms
400_5f9fada1f077f.png
651 ms
400_5f9fadb076a4d.png
805 ms
3555f1bb0e8fdc754aa06f8ee2c61cfd.jpeg!n43
364 ms
8e840e614f8e13e729c0e0329cce0b38.jpeg!n43
65 ms
14e6c9449d96699ae39bfb1df0dc6daa.jpeg!n43
131 ms
51ff1f60fcec9dd429c02c54b6a59998.jpeg!n43
192 ms
8478a31b7b2f4c78c118937b78d7bb55.jpeg!n43
194 ms
4ba4566a21e8400936f329305c51f365.jpeg!n43
217 ms
85e28a01f0003f50bf7ace49e6799b4a.jpeg!n43
241 ms
320225913f3d960bf15524050d3e0e60.png!n43
334 ms
e5199ef80f5b1f6569222d1075fc5a7c.jpeg!n43
258 ms
c401cee893fc5616ab222bbda7810261.jpeg!n43
290 ms
ebbfcdd31925776a5ceeb38c36911f6c.jpg!n43
324 ms
ead782c3839874c71d1bcfb082d672e5.jpeg!n43
323 ms
8ec4b24ba4d65024e7b0dffb0f4ec121.png!n43
327 ms
d156ab34701c1661d1c08a0db10a2592.jpeg!n43
364 ms
7e2c76256403a5eda65cbea0d0e28b66.jpg!n43
385 ms
e3272610a92a320129fb1ed7a8619c8a.jpeg!n43
404 ms
72221216dc01a57f46905eee29b31bd0.jpg!n43
391 ms
064c669cd58f558d3388c38fef04796a.jpeg!n43
397 ms
c4dff9b0aa120eeef6cec438a2cb6eb5.png!n43
426 ms
buildface.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Image elements do not have [alt] attributes
buildface.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
buildface.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Buildface.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 Buildface.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.
buildface.com
Open Graph description is not detected on the main page of Buildface. 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: