Tools & Wizards About Us
fruitday.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

fruitday.com

天天果园-水果网购|生鲜食品|蔬菜配送首选品牌，只为一份极致

Page Load Speed

41.9 sec in total

First Response

1.3 sec

Resources Loaded

40.1 sec

Page Rendered

487 ms

fruitday.com screenshot

About Website

Visit fruitday.com now to see the best up-to-date Fruitday content for China and also check out these interesting facts you probably never knew about fruitday.com

天天果园官方网站是专业的进口生鲜水果食品网络购物平台，提供水果网购，水果配送，生鲜食品和蔬菜配送服务，精选全球高端生鲜水果送货上门，天天果园是您首选的生鲜电商。

Visit fruitday.com

Key Findings

We analyzed Fruitday.com page load time and found that the first response time was 1.3 sec and then it took 40.6 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.

Performance Metrics

fruitday.com performance score

0

Network Requests Diagram

fruitday.com

1321 ms

www.fruitday.com

4412 ms

bootstrap.css

2898 ms

common.css

1442 ms

style.css

2954 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 33% of them (25 requests) were addressed to the original Fruitday.com, 11% (8 requests) were made to Img1.fruitday.com and 8% (6 requests) were made to Cdn.fruitday.com. The less responsive or slowest element that took the longest time to load (18.3 sec) belongs to the original domain Fruitday.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 349.6 kB (58%)

Content Size

603.2 kB

After Optimization

253.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fruitday.com main page is 603.2 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. 40% of websites need less resources to load. Javascripts take 292.2 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 65.2 kB

  • Original 74.2 kB
  • After minification 42.1 kB
  • After compression 9.0 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 32.1 kB, which is 43% 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 65.2 kB or 88% of the original size.

Image Optimization

-37%

Potential reduce by 55.3 kB

  • Original 148.4 kB
  • After minification 93.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. Obviously, Fruitday needs image optimization as it can save up to 55.3 kB or 37% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-53%

Potential reduce by 155.3 kB

  • Original 292.2 kB
  • After minification 245.0 kB
  • After compression 136.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 155.3 kB or 53% of the original size.

CSS Optimization

-83%

Potential reduce by 73.7 kB

  • Original 88.5 kB
  • After minification 86.1 kB
  • After compression 14.7 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. Fruitday.com needs all CSS files to be minified and compressed as it can save up to 73.7 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (52%)

Requests Now

71

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fruitday.com

fruitday.com

1321 ms

www.fruitday.com

www.fruitday.com

4412 ms

bootstrap.css

bootstrap.css

2898 ms

common.css

common.css

1442 ms

style.css

style.css

2954 ms

guan_jquery-1.11.0.min.js

guan_jquery-1.11.0.min.js

6979 ms

cart.js

cart.js

987 ms

index.css

index.css

986 ms

require.js

require.js

974 ms

wb.js

wb.js

9 ms

guan_btn01.jpg

guan_btn01.jpg

4483 ms

logo.svg

logo.svg

6649 ms

guan_ewcode2.jpg

guan_ewcode2.jpg

489 ms

guan_ewcode1.jpg

guan_ewcode1.jpg

2519 ms

guan_EmptyHome@2x.png

guan_EmptyHome@2x.png

1318 ms

guan_xinp.png

guan_xinp.png

2030 ms

guan_jink.png

guan_jink.png

3796 ms

guan_guoc.png

guan_guoc.png

2136 ms

guan_liw.png

guan_liw.png

5309 ms

cha.png

cha.png

478 ms

guan_btn02.jpg

guan_btn02.jpg

3208 ms

guan_default.png

guan_default.png

4880 ms

iconfont.woff

iconfont.woff

5414 ms

5ace3b62f9c110f9e9560f29e6c34f8d.jpg

5ace3b62f9c110f9e9560f29e6c34f8d.jpg

5399 ms

kefu

kefu

2495 ms

0d43ca4afc2c8912e501c61e024bb597.jpg

0d43ca4afc2c8912e501c61e024bb597.jpg

14086 ms

d374f0e74a874fbae9197798adbd9cfa.jpg

d374f0e74a874fbae9197798adbd9cfa.jpg

9523 ms

fc86897d2039c23518c4872708783f8f.jpg

fc86897d2039c23518c4872708783f8f.jpg

5967 ms

7979210582242ba8f843f99361b1af21.jpg

7979210582242ba8f843f99361b1af21.jpg

8603 ms

f117b8208ffc22980e20d99874ec924c.jpg

f117b8208ffc22980e20d99874ec924c.jpg

11014 ms

icons.png

icons.png

16744 ms

kf.png

kf.png

494 ms

icon.png

icon.png

5843 ms

logo1.svg

logo1.svg

8105 ms

guan_shgs.gif

guan_shgs.gif

2325 ms

hm.js

hm.js

2406 ms

utrace

utrace

5918 ms

loading1.gif

loading1.gif

302 ms

bundle.js

bundle.js

626 ms

main.js

main.js

5825 ms

kf.js

kf.js

9907 ms

client.js

client.js

13 ms

iframeWidget.js

iframeWidget.js

4 ms

aj_relationship.php

aj_relationship.php

1180 ms

followbutton.php

followbutton.php

686 ms

hm.gif

hm.gif

379 ms

followButton.css

followButton.css

336 ms

sso.js

sso.js

5 ms

followButton.js

followButton.js

12 ms

suda.js

suda.js

13 ms

bg_flbtn.png

bg_flbtn.png

11 ms

b.gif

b.gif

1340 ms

guan_jquery-1.11.0.min.js

guan_jquery-1.11.0.min.js

5936 ms

guan_jquery-1.11.0.min.js

guan_jquery-1.11.0.min.js

2646 ms

fa.js

fa.js

2303 ms

default.json

default.json

410 ms

track

track

527 ms

theme2.css

theme2.css

1063 ms

track

track

1425 ms

dialog.js

dialog.js

1284 ms

back.js

back.js

514 ms

base64.min.js

base64.min.js

552 ms

evaluate.js

evaluate.js

503 ms

ajax.js

ajax.js

18263 ms

topindex.js

topindex.js

506 ms

index.js

index.js

2167 ms

bootstrap.min.js

bootstrap.min.js

545 ms

jquery.lazyload.min.js

jquery.lazyload.min.js

540 ms

sly.min.js

sly.min.js

1531 ms

sendmsg.jsp

sendmsg.jsp

1088 ms

sendmsg.jsp

sendmsg.jsp

1152 ms

5678c6986b749.png

5678c6986b749.png

438 ms

sendmsg.jsp

sendmsg.jsp

880 ms

sendmsg.jsp

sendmsg.jsp

861 ms

sendmsg.jsp

sendmsg.jsp

857 ms

SEO Factors

fruitday.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 Fruitday.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 Fruitday.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

fruitday.com

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