21.5 sec in total
2.9 sec
17.9 sec
806 ms
Welcome to heartfook.com homepage info - get ready to check Heartfook best content right away, or after learning these important things about heartfook.com
恒达福钻石
Visit heartfook.comWe analyzed Heartfook.com page load time and found that the first response time was 2.9 sec and then it took 18.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
heartfook.com performance score
name
value
score
weighting
Value2.3 s
73/100
10%
Value8.2 s
2/100
25%
Value12.5 s
3/100
10%
Value790 ms
37/100
30%
Value0.736
6/100
15%
Value16.6 s
5/100
10%
2859 ms
2447 ms
2709 ms
1028 ms
693 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 26% of them (25 requests) were addressed to the original Heartfook.com, 61% (60 requests) were made to Image.heartfook.com and 7% (7 requests) were made to 53ex.com. The less responsive or slowest element that took the longest time to load (9.5 sec) relates to the external source Cnzz.mmstat.com.
Page size can be reduced by 449.4 kB (11%)
4.2 MB
3.8 MB
In fact, the total size of Heartfook.com main page is 4.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. 70% of websites need less resources to load. Images take 3.9 MB which makes up the majority of the site volume.
Potential reduce by 24.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 5.5 kB, which is 18% 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 24.8 kB or 83% of the original size.
Potential reduce by 208.4 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. Heartfook images are well optimized though.
Potential reduce by 152.0 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 152.0 kB or 69% of the original size.
Potential reduce by 64.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. Heartfook.com needs all CSS files to be minified and compressed as it can save up to 64.3 kB or 82% of the original size.
Number of requests can be reduced by 17 (18%)
96
79
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Heartfook. 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 from 4 to 1 for CSS and as a result speed up the page load time.
heartfook.com
2859 ms
style.css
2447 ms
jquery.js
2709 ms
slide.js
1028 ms
xstyle.css
693 ms
nav.js
692 ms
jquery.let_it_snow.js
1055 ms
help.css
347 ms
2_01.png
3288 ms
20150526095508_60424.jpg
1759 ms
top_zuan_shi.gif
335 ms
logo.png
336 ms
20160104092439_39978.jpg
1688 ms
help.jpg
1005 ms
phone_number.gif
340 ms
weixin.jpg
338 ms
20150526095508_96583.jpg
2439 ms
20150526095509_25856.jpg
2145 ms
20150526095509_55181.jpg
2145 ms
20150526095509_38352.jpg
2146 ms
20150526095509_36411.jpg
5818 ms
20150526095509_20220.jpg
2440 ms
2_02.png
3703 ms
2_03.png
1947 ms
2_04.png
2636 ms
2_05.png
3308 ms
2_06.png
3335 ms
2_07.png
3656 ms
2_08.png
4742 ms
2_09.png
3624 ms
2_10.png
3655 ms
2_11.png
4406 ms
2_12.png
4680 ms
2_13.png
4723 ms
2_14.png
4343 ms
2_15.png
4808 ms
2_16.png
4694 ms
2_17.png
5112 ms
2_18.png
5011 ms
2_19.png
5350 ms
2_20.png
5385 ms
2_21.png
5396 ms
2_22.png
5157 ms
2_23.png
5337 ms
2_24.png
5448 ms
2_25.png
5492 ms
2_26.png
6340 ms
2_27.png
6783 ms
2_28.png
5732 ms
2_29.png
5734 ms
2_30.png
6165 ms
2_31.png
6208 ms
2_32.png
6445 ms
2_33.png
6116 ms
2_34.png
6488 ms
2_35.png
6546 ms
2_36.png
6583 ms
top_cart.gif
656 ms
top2_bg_bak.jpg
656 ms
search_bt.gif
662 ms
2.jpg
3436 ms
bigbox_arrow.gif
993 ms
snow.html
992 ms
z_stat.php
1186 ms
style.css
345 ms
jquery-1.7.2.min.js
1074 ms
jquery.let_it_snow.js
347 ms
stat.htm
158 ms
core.php
955 ms
2_37.png
5083 ms
white-snowflake.png
339 ms
9.gif
9480 ms
pic1.gif
1123 ms
floatbg.jpg
348 ms
2_38.png
4168 ms
2_39.png
3557 ms
2_40.png
3596 ms
2_41.png
3952 ms
2_42.png
3509 ms
2_43.png
3488 ms
2_44.png
3875 ms
2_45.png
3935 ms
2_46.png
3021 ms
2_47.png
3076 ms
2_48.png
2850 ms
2_49.png
3276 ms
2_50.png
2983 ms
2_51.png
3089 ms
2_52.png
3073 ms
2_53.png
2871 ms
2_54.png
3304 ms
2_55.png
2897 ms
2_56.png
3185 ms
2_57.png
2881 ms
2_58.png
2846 ms
2_59.png
2918 ms
%E5%88%86%E9%9A%94%E7%AC%A6.gif
2955 ms
app.gif
1633 ms
heartfook.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
Buttons do not have an accessible name
Links do not have a discernible name
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.
heartfook.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
heartfook.com SEO score
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Heartfook.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 Heartfook.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.
heartfook.com
Open Graph description is not detected on the main page of Heartfook. 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: