5.1 sec in total
1.3 sec
3.5 sec
293 ms
Visit huarenli.com now to see the best up-to-date Huarenli content and also check out these interesting facts you probably never knew about huarenli.com
Default Description
Visit huarenli.comWe analyzed Huarenli.com page load time and found that the first response time was 1.3 sec and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
huarenli.com performance score
name
value
score
weighting
Value4.0 s
22/100
10%
Value4.9 s
29/100
25%
Value6.6 s
38/100
10%
Value610 ms
49/100
30%
Value0.345
32/100
15%
Value6.0 s
64/100
10%
1291 ms
37 ms
72 ms
74 ms
25 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 96% of them (53 requests) were addressed to the original Huarenli.com, 2% (1 request) were made to Fonts.googleapis.com and 2% (1 request) were made to Livechat.volusion.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Huarenli.com.
Page size can be reduced by 15.5 kB (74%)
20.9 kB
5.4 kB
In fact, the total size of Huarenli.com main page is 20.9 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. 50% of websites need less resources to load. HTML takes 20.9 kB which makes up the majority of the site volume.
Potential reduce by 15.5 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 15.5 kB or 74% of the original size.
Number of requests can be reduced by 23 (51%)
45
22
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Huarenli. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.huarenli.com
1291 ms
prettyPhoto.css
37 ms
lrtk.css
72 ms
pptBox.js
74 ms
css
25 ms
styles.css
77 ms
widgets.css
68 ms
prototype.js
110 ms
ccard.js
74 ms
validation.js
103 ms
builder.js
102 ms
effects.js
104 ms
dragdrop.js
103 ms
controls.js
105 ms
slider.js
134 ms
js.js
135 ms
form.js
137 ms
menu.js
137 ms
translate.js
137 ms
cookies.js
142 ms
jquery-1.5.1.js
247 ms
jquery.nivo.slider.js
166 ms
jquery.easing.1.3.js
168 ms
liteaccordion.jquery.js
168 ms
jquery.infinite-carousel.js
169 ms
jquery.prettyPhoto.js
176 ms
script.aspx
383 ms
bg.jpg
50 ms
indextop_bgimg.jpg
53 ms
menu_right.gif
50 ms
logo.gif
48 ms
indexBanner001.jpg
143 ms
indNav001.jpg
68 ms
indNav002.jpg
69 ms
indNav003.jpg
69 ms
indexbotlogo.jpg
70 ms
btn_search.gif
61 ms
headdes.jpg
83 ms
how3bg.jpg
84 ms
head_row3.gif
632 ms
menuzhu_right.gif
85 ms
nav_hover.gif
85 ms
nav_hover.png
123 ms
head_row31.gif
124 ms
tmslider1_bg.jpg
125 ms
360videoshopping001.jpg
289 ms
360videoshopping002.jpg
210 ms
360videoshopping003.jpg
245 ms
02.png
147 ms
01.png
149 ms
index_title.gif
157 ms
li_rk.png
159 ms
huarenlileft.jpg
190 ms
livechat_offline.gif
772 ms
print.css
36 ms
huarenli.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.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
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
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.
huarenli.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Issues were logged in the Issues panel in Chrome Devtools
huarenli.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Huarenli.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Huarenli.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.
huarenli.com
Open Graph description is not detected on the main page of Huarenli. 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: