Tools & Wizards About Us
1p1g.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

1p1g.com

一瓶一罐化妆品网站_专业化妆品试用网站

Page Load Speed

46.1 sec in total

First Response

4.1 sec

Resources Loaded

41.5 sec

Page Rendered

495 ms

1p1g.com screenshot

About Website

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

一瓶一罐，是一家全方位的美妆体验口碑推广平台！ 主供平台展示，精准派样，整合化营销，粉丝招新，达人评测、社交媒体等服务，为客户打造“品牌力”，为会员提供丰富的试用礼遇。

Visit 1p1g.com

Key Findings

We analyzed 1p1g.com page load time and found that the first response time was 4.1 sec and then it took 42 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 6 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

1p1g.com performance score

0

Network Requests Diagram

1p1g.com

4080 ms

www.1p1g.com

11638 ms

css

1749 ms

wb.js

35 ms

base.min.js

1197 ms

Our browser made a total of 100 requests to load all elements on the main page. We found that 76% of them (76 requests) were addressed to the original 1p1g.com, 4% (4 requests) were made to Tjs.sjs.sinajs.cn and 3% (3 requests) were made to Js.t.sinajs.cn. The less responsive or slowest element that took the longest time to load (20.2 sec) belongs to the original domain 1p1g.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 256.6 kB (31%)

Content Size

818.2 kB

After Optimization

561.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 1p1g.com main page is 818.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. 35% of websites need less resources to load. Images take 438.8 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 37.0 kB

  • Original 52.9 kB
  • After minification 52.9 kB
  • After compression 15.9 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 37.0 kB or 70% of the original size.

Image Optimization

-7%

Potential reduce by 29.2 kB

  • Original 438.8 kB
  • After minification 409.6 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. 1 P G images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 186.0 kB

  • Original 320.5 kB
  • After minification 278.8 kB
  • After compression 134.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 186.0 kB or 58% of the original size.

CSS Optimization

-74%

Potential reduce by 4.4 kB

  • Original 5.9 kB
  • After minification 5.9 kB
  • After compression 1.5 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. 1p1g.com needs all CSS files to be minified and compressed as it can save up to 4.4 kB or 74% of the original size.

Requests Breakdown

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

Requests Now

91

After Optimization

80

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

1p1g.com

1p1g.com

4080 ms

www.1p1g.com

www.1p1g.com

11638 ms

css

css

1749 ms

wb.js

wb.js

35 ms

base.min.js

base.min.js

1197 ms

js

js

1016 ms

query

query

1138 ms

0

0

253 ms

15989 ms

0

0

241 ms

ico.jpg

ico.jpg

1268 ms

index-top_29.gif

index-top_29.gif

1665 ms

index-top_25.gif

index-top_25.gif

4922 ms

index-top_26.gif

index-top_26.gif

1359 ms

index-top_34.jpg

index-top_34.jpg

1756 ms

index_fenglei.gif

index_fenglei.gif

1802 ms

banner_201603140846.jpg

banner_201603140846.jpg

20005 ms

banner_201601161019.jpg

banner_201601161019.jpg

17112 ms

banner201512151053.jpg

banner201512151053.jpg

3918 ms

banner201512081044.jpg

banner201512081044.jpg

9105 ms

banner_201603041320.jpg

banner_201603041320.jpg

9418 ms

xyh201511121732.jpg

xyh201511121732.jpg

7901 ms

button_bj.gif

button_bj.gif

9642 ms

index-more_58.jpg

index-more_58.jpg

8708 ms

2016033014285150x8tf.jpg

2016033014285150x8tf.jpg

13266 ms

20160330142925wyqstr.jpg

20160330142925wyqstr.jpg

20001 ms

20140212164306my1vl3.jpg

20140212164306my1vl3.jpg

9824 ms

201401021220170s2qd5.jpg

201401021220170s2qd5.jpg

11076 ms

201309211128525myft0.jpg

201309211128525myft0.jpg

10237 ms

banner_201508171825.jpg

banner_201508171825.jpg

13909 ms

20140724171450mt2e3b.jpg

20140724171450mt2e3b.jpg

15269 ms

20151027144718btp6jw.jpg

20151027144718btp6jw.jpg

14079 ms

20140102115626fnbmn6.jpg

20140102115626fnbmn6.jpg

14353 ms

20150304165025dn329g.jpg

20150304165025dn329g.jpg

14832 ms

20140529174619ybk24q.jpg

20140529174619ybk24q.jpg

15228 ms

2014010211513874pdcu.jpg

2014010211513874pdcu.jpg

15209 ms

20150910152535_50_50.jpg

20150910152535_50_50.jpg

15568 ms

20160106172603_50_50.jpg

20160106172603_50_50.jpg

15642 ms

20150918142836_50_50.jpg

20150918142836_50_50.jpg

17125 ms

20151026010826_50_50.jpg

20151026010826_50_50.jpg

15974 ms

20150313181005_50_50.jpg

20150313181005_50_50.jpg

16092 ms

20160127234828_50_50.jpg

20160127234828_50_50.jpg

16364 ms

20150804123452_50_50.jpg

20150804123452_50_50.jpg

16340 ms

20160122124012_50_50.jpg

20160122124012_50_50.jpg

16206 ms

hm.js

hm.js

950 ms

ga.js

ga.js

1533 ms

20140930171415_50_50.jpg

20140930171415_50_50.jpg

16144 ms

pic1.gif

pic1.gif

16410 ms

20140730215510_50_50.jpg

20140730215510_50_50.jpg

16161 ms

20160331110313_50_50.jpg

20160331110313_50_50.jpg

15991 ms

20160328134627_50_50.jpg

20160328134627_50_50.jpg

17260 ms

20160321154309dvkfr5.jpg

20160321154309dvkfr5.jpg

20203 ms

hm.gif

hm.gif

867 ms

s.js

s.js

20144 ms

__utm.gif

__utm.gif

326 ms

201603211601178c46ut.jpg

201603211601178c46ut.jpg

18626 ms

201603211603561v7g6m.jpg

201603211603561v7g6m.jpg

16762 ms

20160321153711oho0rs.jpg

20160321153711oho0rs.jpg

17418 ms

loading1.gif

loading1.gif

79 ms

bundle.js

bundle.js

79 ms

checklogin

checklogin

12610 ms

client.js

client.js

18 ms

xd.jsp

xd.jsp

304 ms

getuserpanel

getuserpanel

12282 ms

xd.js

xd.js

578 ms

20160321153451y5v23y.jpg

20160321153451y5v23y.jpg

19897 ms

iframeWidget.js

iframeWidget.js

47 ms

aj_relationship.php

aj_relationship.php

1817 ms

20160321155052ely3v6.jpg

20160321155052ely3v6.jpg

19586 ms

20160321154012l23ipc.jpg

20160321154012l23ipc.jpg

14762 ms

201603211529168lpn2j.jpg

201603211529168lpn2j.jpg

18612 ms

Logo_pic_200.gif

Logo_pic_200.gif

14037 ms

Logo_pic_34.gif

Logo_pic_34.gif

13737 ms

followbutton.php

followbutton.php

798 ms

followButton.css

followButton.css

37 ms

sso.js

sso.js

26 ms

followButton.js

followButton.js

25 ms

suda.js

suda.js

23 ms

b.gif

b.gif

946 ms

bg_flbtn.png

bg_flbtn.png

6 ms

Logo_pic_36.gif

Logo_pic_36.gif

11565 ms

Logo_whoo-2.gif

Logo_whoo-2.gif

13177 ms

jurlique.gif

jurlique.gif

12285 ms

logo_maysu.gif

logo_maysu.gif

14091 ms

givenchy.gif

givenchy.gif

12388 ms

logo02.gif

logo02.gif

12806 ms

lancaster.gif

lancaster.gif

12365 ms

sooryehanlogo.gif

sooryehanlogo.gif

12686 ms

yuemuzhiyuan-2.jpg

yuemuzhiyuan-2.jpg

12745 ms

Logo_pic_71.gif

Logo_pic_71.gif

18157 ms

logo71.gif

logo71.gif

12818 ms

Logo_pic_69.gif

Logo_pic_69.gif

16221 ms

wei.gif

wei.gif

14023 ms

index-bottom-img_76.jpg

index-bottom-img_76.jpg

12816 ms

index-bottom-img_78.jpg

index-bottom-img_78.jpg

13188 ms

index-bottom-img_80.jpg

index-bottom-img_80.jpg

13202 ms

xuanfu_52.gif

xuanfu_52.gif

17016 ms

login_06.gif

login_06.gif

9462 ms

login_11.gif

login_11.gif

9724 ms

login_13.gif

login_13.gif

10534 ms

SEO Factors

1p1g.com SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 1p1g.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that 1p1g.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

1p1g.com

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