7.9 sec in total
1.1 sec
6.3 sec
550 ms
Visit huabaike.com now to see the best up-to-date Huabaike content for China and also check out these interesting facts you probably never knew about huabaike.com
花百科,陪伴您的养花生活。达人和花友每日分享专业的养花知识、技巧和图片。让您30天成为养花达人!
Visit huabaike.comWe analyzed Huabaike.com page load time and found that the first response time was 1.1 sec and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
huabaike.com performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value10.8 s
0/100
25%
Value9.6 s
11/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value6.5 s
58/100
10%
1082 ms
1071 ms
220 ms
419 ms
591 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 21% of them (20 requests) were addressed to the original Huabaike.com, 32% (31 requests) were made to Img.huabaike.com and 32% (31 requests) were made to Wenda.huabaike.com. The less responsive or slowest element that took the longest time to load (3.5 sec) relates to the external source Img.huabaike.com.
Page size can be reduced by 282.0 kB (5%)
5.4 MB
5.1 MB
In fact, the total size of Huabaike.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. 55% of websites need less resources to load. Images take 5.3 MB which makes up the majority of the site volume.
Potential reduce by 61.9 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 61.9 kB or 82% of the original size.
Potential reduce by 216.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. Huabaike images are well optimized though.
Potential reduce by 1.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. This website has mostly compressed JavaScripts.
Potential reduce by 1.4 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. Huabaike.com needs all CSS files to be minified and compressed as it can save up to 1.4 kB or 22% of the original size.
Number of requests can be reduced by 7 (7%)
94
87
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Huabaike. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
huabaike.com
1082 ms
www.huabaike.com
1071 ms
home.css
220 ms
main.css
419 ms
jquery.1.9.1.min.js
591 ms
main.js
608 ms
jquery.SuperSlide.2.1.1.js
603 ms
checkmobile.js
654 ms
header_line.js
620 ms
footer_li.js
812 ms
5b2a0cba9cccd.jpg
1630 ms
5ffb0edb97731.jpg
643 ms
1587010362_835560.jpg
389 ms
logo-2020.png
212 ms
left.png
198 ms
right.png
240 ms
wechat_code.png
275 ms
bp_6110dcb344b97.jpg
1883 ms
bp_6110dc39ea0f4.jpg
2113 ms
bp_6110dbc69a62b.jpg
2212 ms
bp_6110db5b3874d.jpg
2228 ms
5657ecae0736b.jpg
2206 ms
56b066d43f2c9.jpg
2225 ms
56482cda266bc.jpg
2207 ms
57ada672be24e.jpg
2333 ms
56789ba343c8c.jpg
2409 ms
56dfebbe8d7fd.jpg
2596 ms
58ad3b3ab3ced.jpg
2425 ms
58ae89c0a09f9.jpg
2428 ms
5a83ef85b5b98.jpg
2849 ms
5a82a696aa7ad.jpg
2622 ms
5a829ea6c53c6.jpg
3031 ms
5a829aceae7f2.jpg
2996 ms
mk_20200929170920_3992.jpg
2831 ms
5a800e69758bf.jpg
3073 ms
5a800030a67bd.jpg
2879 ms
mk_20200810153516_6777.jpg
3085 ms
5a7eb8051570d.jpg
3133 ms
5a7d5e7f3b319.jpg
3141 ms
57eb9f0e7a7a5.jpg
3228 ms
57eb9f94c750d.jpg
3297 ms
57eba011e23ce.jpg
3292 ms
57eba08ac685c.jpg
3313 ms
57eba0f4e0ca2.jpg
3348 ms
57eba12cc97a3.jpg
3377 ms
57eba158edbe0.jpg
3443 ms
57eba185dd10f.jpg
3519 ms
5e95804a71b2d.jpg
725 ms
5e957fb4e0f48.jpg
702 ms
5e957f361666d.jpg
697 ms
5e957ed7b845b.jpg
723 ms
5e957e7d7481c.jpg
693 ms
5e957e1da2ac3.jpg
768 ms
5e957d9bd8797.jpg
780 ms
5e957d50132b4.jpg
784 ms
5e957cf6d703d.jpg
787 ms
5e957c976d7ca.jpg
841 ms
5e957c4467524.jpg
810 ms
5e957bece2d7b.jpg
845 ms
5e957bd69a83c.jpg
864 ms
5e957b3529975.jpg
993 ms
5e957b1d377d1.jpg
871 ms
5e957a6c43604.jpg
911 ms
5e9579f0ece81.jpg
903 ms
5e95798eda326.jpg
931 ms
5e957524c6436.jpg
949 ms
5e95749da80fd.jpg
960 ms
5e95743a16a4b.jpg
970 ms
5e9573d80f7b3.jpg
987 ms
5e95737f79678.jpg
1014 ms
5e95736234fe1.jpg
1018 ms
5e957274b3e1a.jpg
1040 ms
5e957225b740f.jpg
1047 ms
5e9571d1a1c24.jpg
1072 ms
5e957150641a2.jpg
1069 ms
5e9570de5601d.jpg
1091 ms
5e95708b1475a.jpg
1074 ms
1570698571_010060.jpg
431 ms
5de8e2a036d27.jpg
407 ms
1570746692_537640.jpg
426 ms
1568786988_005040.jpg
431 ms
1574893794_488328.jpg
571 ms
1578469375_886593.jpg
421 ms
5c0df1081524d.JPG
570 ms
1571489466_093840.jpg
569 ms
1577054060_782313.jpg
569 ms
1570247337_043970.jpg
568 ms
1574565593_210883.jpg
569 ms
search_ico.png
203 ms
index.html
387 ms
eye.png
336 ms
time_time.png
358 ms
app_ewm.jpg
301 ms
wx_ewm.jpg
450 ms
push.js
1277 ms
hm.js
1065 ms
hm.gif
316 ms
huabaike.com accessibility score
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
huabaike.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
huabaike.com SEO score
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
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Huabaike.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 Huabaike.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.
huabaike.com
Open Graph description is not detected on the main page of Huabaike. 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: