Tools & Wizards About Us
hicay.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

80.4 sec in total

First Response

8.3 sec

Resources Loaded

71.5 sec

Page Rendered

565 ms

hicay.com screenshot

About Website

Click here to check amazing Hicay content. Otherwise, check out these important facts you probably never knew about hicay.com

Visit hicay.com

Key Findings

We analyzed Hicay.com page load time and found that the first response time was 8.3 sec and then it took 72.1 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. Unfortunately, there were 63 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

hicay.com performance score

0

Network Requests Diagram

hicay.com

8312 ms

pic.js

7557 ms

jh.js

1445 ms

hicay.js

5184 ms

html5.js

1005 ms

Our browser made a total of 118 requests to load all elements on the main page. We found that 98% of them (116 requests) were addressed to the original Hicay.com, 2% (2 requests) were made to Count39.51yes.com. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain Hicay.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 519.6 kB (32%)

Content Size

1.6 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hicay.com main page is 1.6 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. Only 5% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 72.9 kB

  • Original 89.5 kB
  • After minification 72.7 kB
  • After compression 16.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. This page needs HTML code to be minified as it can gain 16.8 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 72.9 kB or 82% of the original size.

Image Optimization

-18%

Potential reduce by 227.3 kB

  • Original 1.2 MB
  • After minification 1.0 MB

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, Hicay needs image optimization as it can save up to 227.3 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-68%

Potential reduce by 178.1 kB

  • Original 261.7 kB
  • After minification 241.8 kB
  • After compression 83.6 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 178.1 kB or 68% of the original size.

CSS Optimization

-80%

Potential reduce by 41.3 kB

  • Original 51.3 kB
  • After minification 45.0 kB
  • After compression 10.1 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. Hicay.com needs all CSS files to be minified and compressed as it can save up to 41.3 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (80%)

Requests Now

54

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hicay. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

hicay.com

hicay.com

8312 ms

pic.js

pic.js

7557 ms

jh.js

jh.js

1445 ms

hicay.js

hicay.js

5184 ms

html5.js

html5.js

1005 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

19571 ms

top.js

top.js

1917 ms

jquery.ad-gallery.js

jquery.ad-gallery.js

3444 ms

main.css

main.css

11617 ms

Public.css

Public.css

12223 ms

flashslibings.css

flashslibings.css

7899 ms

contentsbling.css

contentsbling.css

8235 ms

sitebase.js

sitebase.js

3449 ms

20150427-70.js

20150427-70.js

6516 ms

20140430-48.js

20140430-48.js

8396 ms

20140430-49.js

20140430-49.js

6845 ms

20140430-50.js

20140430-50.js

6983 ms

20140516-66.js

20140516-66.js

7319 ms

getweekstart.ashx

getweekstart.ashx

7974 ms

netsoftok_web_userhy_list.ashx

netsoftok_web_userhy_list.ashx

8359 ms

20140516-67.js

20140516-67.js

8452 ms

20140430-53.js

20140430-53.js

11165 ms

20140430-52.js

20140430-52.js

8859 ms

20140430-51.js

20140430-51.js

8921 ms

20140516-68.js

20140516-68.js

554 ms

jQuery.js

jQuery.js

19686 ms

jquery.slides.js

jquery.slides.js

8439 ms

click.aspx

click.aspx

1019 ms

slider.js

slider.js

5699 ms

main.js

main.js

6627 ms

ad20159851656286263.jpg

ad20159851656286263.jpg

19989 ms

logo.png

logo.png

3276 ms

ad.jpg

ad.jpg

11216 ms

im1.jpg

im1.jpg

10723 ms

im2.jpg

im2.jpg

8548 ms

im3.jpg

im3.jpg

10359 ms

im4.jpg

im4.jpg

8865 ms

im5.jpg

im5.jpg

12137 ms

im6.jpg

im6.jpg

18855 ms

1.jpg

1.jpg

19985 ms

2.jpg

2.jpg

19985 ms

3.jpg

3.jpg

19986 ms

4.jpg

4.jpg

19987 ms

5.jpg

5.jpg

19986 ms

6.jpg

6.jpg

19987 ms

7.jpg

7.jpg

19988 ms

8.jpg

8.jpg

19987 ms

s.jpg

s.jpg

19988 ms

s.jpg

s.jpg

19988 ms

s.jpg

s.jpg

19988 ms

s.jpg

s.jpg

19989 ms

index_19.jpg

index_19.jpg

19990 ms

face.png

face.png

19991 ms

face.png

face.png

19992 ms

index_57.jpg

index_57.jpg

19992 ms

100-100.jpg

100-100.jpg

19992 ms

face.png

face.png

19992 ms

index_72.jpg

index_72.jpg

19992 ms

201604053258156980660.jpg

201604053258156980660.jpg

19993 ms

index_84.jpg

index_84.jpg

19994 ms

index_87.jpg

index_87.jpg

19994 ms

index_94.jpg

index_94.jpg

19994 ms

s.jpg

s.jpg

19995 ms

s.jpg

s.jpg

19995 ms

s.jpg

s.jpg

19995 ms

ad20159821296702037.jpg

ad20159821296702037.jpg

19995 ms

ad20159813921565465.jpg

ad20159813921565465.jpg

19996 ms

ad201451558794910614.jpg

ad201451558794910614.jpg

19995 ms

ad201451616935460177.jpg

ad201451616935460177.jpg

19996 ms

20100704360815239748.jpg

20100704360815239748.jpg

11334 ms

201007043336937695109.jpg

201007043336937695109.jpg

19996 ms

201007043137656322598.jpg

201007043137656322598.jpg

19995 ms

s.jpg

s.jpg

19995 ms

s.jpg

s.jpg

19710 ms

count6.gif

count6.gif

406 ms

s.jpg

s.jpg

19977 ms

s.jpg

s.jpg

18426 ms

s.jpg

s.jpg

17230 ms

s.jpg

s.jpg

18268 ms

s.jpg

s.jpg

18398 ms

f1.gif

f1.gif

19769 ms

f2.jpg

f2.jpg

18069 ms

f3.gif

f3.gif

10717 ms

f4.gif

f4.gif

11453 ms

f5.gif

f5.gif

10090 ms

topbj.gif

topbj.gif

10089 ms

sh2.png

sh2.png

10566 ms

im1.png

im1.png

12265 ms

f.png

f.png

12594 ms

s24.png

s24.png

19994 ms

fg.gif

fg.gif

11933 ms

ax2.gif

ax2.gif

11988 ms

h1.png

h1.png

19320 ms

n1r.gif

n1r.gif

12850 ms

adjs201542734714316020.png

adjs201542734714316020.png

19990 ms

adjs20159614332301636.jpg

adjs20159614332301636.jpg

19989 ms

adjs20159617239973394.jpg

adjs20159617239973394.jpg

19989 ms

adjs20159622192367585.jpg

adjs20159622192367585.jpg

19988 ms

adjs201542727839761316.png

adjs201542727839761316.png

19989 ms

face.png

face.png

19988 ms

face.png

face.png

19988 ms

114-139.jpg

114-139.jpg

19987 ms

index04_03.jpg

index04_03.jpg

19987 ms

face.png

face.png

19986 ms

face.png

face.png

19986 ms

face.png

face.png

19986 ms

face.png

face.png

19985 ms

face.png

face.png

19984 ms

face.png

face.png

19984 ms

face.png

face.png

19979 ms

face.png

face.png

19998 ms

2015090645645899568.jpg

2015090645645899568.jpg

19998 ms

adjs20159653567140110.jpg

adjs20159653567140110.jpg

19889 ms

adjs20159610739947462.jpg

adjs20159610739947462.jpg

20011 ms

adjs2015965160279074.jpg

adjs2015965160279074.jpg

20357 ms

2015090614114933281.jpg

2015090614114933281.jpg

19863 ms

index_100.jpg

index_100.jpg

20412 ms

100-100.jpg

100-100.jpg

19756 ms

SEO Factors

hicay.com SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hicay.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 Hicay.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.

Social Sharing Optimization

hicay.com

Open Graph description is not detected on the main page of Hicay. 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: