Tools & Wizards About Us
365pp.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

365pp.com

阿芙，就是精油！

Page Load Speed

40.7 sec in total

First Response

4.4 sec

Resources Loaded

36 sec

Page Rendered

268 ms

365pp.com screenshot

About Website

Welcome to 365pp.com homepage info - get ready to check 365 Pp best content for Taiwan right away, or after learning these important things about 365pp.com

阿芙(AFU)源自希腊神话中'爱与美的女神之名',现在化身为全球领先的精油品牌之名。品牌核心价值,是捍卫精油行业的秘密

Visit 365pp.com

Key Findings

We analyzed 365pp.com page load time and found that the first response time was 4.4 sec and then it took 36.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 3 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

365pp.com performance score

0

Network Requests Diagram

365pp.com

4373 ms

Frames

7083 ms

basic.css

1501 ms

page.css

2697 ms

jquery-1.4.min.js

7683 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 86% of them (61 requests) were addressed to the original 365pp.com, 1% (1 request) were made to S4.cnzz.com and 1% (1 request) were made to Tajs.qq.com. The less responsive or slowest element that took the longest time to load (19.9 sec) belongs to the original domain 365pp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 180.4 kB (52%)

Content Size

345.6 kB

After Optimization

165.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 37.9 kB

  • Original 46.2 kB
  • After minification 33.3 kB
  • After compression 8.2 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 12.9 kB, which is 28% 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 37.9 kB or 82% of the original size.

Image Optimization

-8%

Potential reduce by 9.9 kB

  • Original 120.7 kB
  • After minification 110.8 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. 365 Pp images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 105.9 kB

  • Original 145.3 kB
  • After minification 116.8 kB
  • After compression 39.3 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 105.9 kB or 73% of the original size.

CSS Optimization

-80%

Potential reduce by 26.6 kB

  • Original 33.5 kB
  • After minification 29.2 kB
  • After compression 6.8 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. 365pp.com needs all CSS files to be minified and compressed as it can save up to 26.6 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (19%)

Requests Now

64

After Optimization

52

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

365pp.com

365pp.com

4373 ms

Frames

Frames

7083 ms

basic.css

basic.css

1501 ms

page.css

page.css

2697 ms

jquery-1.4.min.js

jquery-1.4.min.js

7683 ms

ShoppingCart.js

ShoppingCart.js

5114 ms

common.js

common.js

1653 ms

js.js

js.js

1883 ms

css.css

css.css

3636 ms

jquery.js

jquery.js

3782 ms

jquery.ulscroll.js

jquery.ulscroll.js

3076 ms

index.js

index.js

3458 ms

index-lunbo.js

index-lunbo.js

3835 ms

lunbo-all.js

lunbo-all.js

4046 ms

stat.php

stat.php

2268 ms

gdt.php

gdt.php

5349 ms

afujingyou_01.png

afujingyou_01.png

545 ms

afujingyou_02.png

afujingyou_02.png

423 ms

afujingyou_03.png

afujingyou_03.png

2467 ms

afujingyou_04.png

afujingyou_04.png

5771 ms

afujingyou_05.png

afujingyou_05.png

5422 ms

afujingyou_06.png

afujingyou_06.png

399 ms

afujingyou_07.png

afujingyou_07.png

857 ms

afujingyou_08.png

afujingyou_08.png

2203 ms

afujingyou_09.png

afujingyou_09.png

5335 ms

afujingyou_10.png

afujingyou_10.png

2420 ms

afujingyou_11.png

afujingyou_11.png

2619 ms

fangxiangzhilv_01.png

fangxiangzhilv_01.png

2849 ms

fangxiangzhilv_02.png

fangxiangzhilv_02.png

5386 ms

fangxiangzhilv_03.png

fangxiangzhilv_03.png

5853 ms

fangxiangzhilv_04.png

fangxiangzhilv_04.png

4555 ms

fangxiangzhilv_05.png

fangxiangzhilv_05.png

7486 ms

fangxiangzhilv_06.png

fangxiangzhilv_06.png

5882 ms

fangxiangzhilv_07.png

fangxiangzhilv_07.png

7475 ms

fangxiangzhilv_08.png

fangxiangzhilv_08.png

7196 ms

fangxiangzhilv_09.png

fangxiangzhilv_09.png

9383 ms

fangxiangzhilv_10.png

fangxiangzhilv_10.png

7939 ms

fangxiangzhilv_11.png

fangxiangzhilv_11.png

9926 ms

jingyouketang_01.png

jingyouketang_01.png

7606 ms

jingyouketang_02.png

jingyouketang_02.png

7871 ms

jingyouketang_03.png

jingyouketang_03.png

9949 ms

jingyouketang_04.png

jingyouketang_04.png

16048 ms

jingyouketang_05.png

jingyouketang_05.png

8289 ms

jingyouketang_06.png

jingyouketang_06.png

8381 ms

daili_01.jpg

daili_01.jpg

8703 ms

daili_02.jpg

daili_02.jpg

8798 ms

1.jpg

1.jpg

19600 ms

2.jpg

2.jpg

19600 ms

3.jpg

3.jpg

18681 ms

4.jpg

4.jpg

19599 ms

renzheng.jpg

renzheng.jpg

10351 ms

top_bg.jpg

top_bg.jpg

11589 ms

GetCartAll

GetCartAll

11639 ms

icon.png

icon.png

13929 ms

nav_bg.jpg

nav_bg.jpg

17658 ms

stat.htm

stat.htm

242 ms

core.php

core.php

996 ms

navtext.png

navtext.png

16492 ms

9.gif

9.gif

914 ms

pic1.gif

pic1.gif

1124 ms

icon.png

icon.png

16455 ms

chanpinzhongxin_bg.png

chanpinzhongxin_bg.png

16184 ms

ico.png

ico.png

19927 ms

lunbo_arrow.png

lunbo_arrow.png

17216 ms

app.gif

app.gif

2039 ms

nav_bg.jpg

nav_bg.jpg

17531 ms

script

script

841 ms

h.js

h.js

1754 ms

footer_bg.jpg

footer_bg.jpg

18609 ms

Categories

Categories

15149 ms

button_old_171.gif

button_old_171.gif

465 ms

SEO Factors

365pp.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 365pp.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 365pp.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

365pp.com

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