76.4 sec in total
4.6 sec
69.7 sec
2.2 sec
Click here to check amazing Badu content for China. Otherwise, check out these important facts you probably never knew about badu.com
百度(baidu)总部地点在中国北京,成立于2000年1月,年营业额为79.15亿人民币(约合11.99亿美元),员工人数上万人,董事长室李彦宏,占中国搜索份额83%,公司地址在北京海淀区上地十街10号百度大厦,公司的口号为“百度一下,你就知道”。
Visit badu.comWe analyzed Badu.com page load time and found that the first response time was 4.6 sec and then it took 71.8 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.
badu.com performance score
name
value
score
weighting
Value1.4 s
97/100
10%
Value1.4 s
100/100
25%
Value2.0 s
99/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value1.4 s
100/100
10%
4570 ms
4649 ms
11808 ms
3238 ms
5493 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Badu.com, 16% (8 requests) were made to Cpro.baidustatic.com and 14% (7 requests) were made to V2.jiathis.com. The less responsive or slowest element that took the longest time to load (11.8 sec) relates to the external source Cdn.lvse.com.
Page size can be reduced by 459.4 kB (51%)
894.4 kB
435.0 kB
In fact, the total size of Badu.com main page is 894.4 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. 55% of websites need less resources to load. Javascripts take 442.9 kB which makes up the majority of the site volume.
Potential reduce by 91.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. This page needs HTML code to be minified as it can gain 22.3 kB, which is 19% 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 91.8 kB or 80% of the original size.
Potential reduce by 21.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. Badu images are well optimized though.
Potential reduce by 242.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 242.4 kB or 55% of the original size.
Potential reduce by 104.0 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. Badu.com needs all CSS files to be minified and compressed as it can save up to 104.0 kB or 83% of the original size.
Number of requests can be reduced by 30 (60%)
50
20
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Badu. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
baidu-com-1226.html
4570 ms
lvse.comm.js
4649 ms
global.css
11808 ms
page.site_info.css
3238 ms
jia.js
5493 ms
1340 ms
c.php
2144 ms
jiathis_utility.html
17 ms
jiathis_share.css
16 ms
plugin.client.js
57 ms
jiathis_ico.png
108 ms
jiathis_counter.css
71 ms
shares.php
977 ms
counter.gif
20 ms
shell_v2.js
1368 ms
c.js
1931 ms
adsbygoogle.js
4 ms
bds_s_v2.js
809 ms
acom
884 ms
ca-pub-3872269047709300.js
50 ms
zrt_lookup.html
42 ms
show_ads_impl.js
60 ms
stat.htm
345 ms
core.php
3298 ms
logger.js
468 ms
ads
209 ms
bdsstyle.css
409 ms
r2.gif
500 ms
osd.js
8 ms
15869979730071487789
3 ms
abg.js
7 ms
m_js_controller.js
17 ms
googlelogo_color_112x36dp.png
46 ms
s
31 ms
x_button_blue2.png
31 ms
-Wxc5n6ag8mSVPmrosQZJ6hEHpQooK3Qr1Gxv0lUkvE.js
4 ms
acom
3881 ms
activeview
11 ms
cpro.js
676 ms
adx.php
4005 ms
icon_12px.png
415 ms
reduce_bd-logo1_oper.png
464 ms
closefeedback.min.js
472 ms
reduce_promotion_oper.png
461 ms
bd_logo.png
453 ms
bg_rb.png
461 ms
o.htm
1299 ms
ac.js
1527 ms
wh.js
1741 ms
fp.htm
1774 ms
fp.htm
976 ms
badu.com accessibility score
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
Document doesn't have a <title> element
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
badu.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
badu.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Badu.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Badu.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.
badu.com
Open Graph description is not detected on the main page of Badu. 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: