Tools & Wizards About Us
div63.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

div63.com

朱腾鹏 - 像素癖 - 个人网站2015版 - div63.com-DIV路上

Page Load Speed

82.8 sec in total

First Response

1.8 sec

Resources Loaded

80.8 sec

Page Rendered

306 ms

div63.com screenshot

About Website

Welcome to div63.com homepage info - get ready to check Div 63 best content right away, or after learning these important things about div63.com

zhutengpeng,xiangsupi,朱腾鹏个人网站,深圳网页设计,深圳网站建设,广东网站设计,广州网站设计,视觉交互设计,集团网站设计,企业网站设计,网页设计,网页设计师,互动设计,个人作品,div,css,photoshop

Visit div63.com

Key Findings

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

Performance Metrics

div63.com performance score

0

Network Requests Diagram

div63.com

1752 ms

effect1.css

4676 ms

jquery-1.9.1.min.js

2751 ms

modernizr.custom.js

1827 ms

common.js

9458 ms

Our browser made a total of 139 requests to load all elements on the main page. We found that 99% of them (138 requests) were addressed to the original Div63.com, 1% (1 request) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Div63.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 200.4 kB (20%)

Content Size

1.0 MB

After Optimization

800.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-87%

Potential reduce by 57.7 kB

  • Original 66.2 kB
  • After minification 64.1 kB
  • After compression 8.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. 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 57.7 kB or 87% of the original size.

Image Optimization

-9%

Potential reduce by 79.8 kB

  • Original 850.6 kB
  • After minification 770.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. Div 63 images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 52.8 kB

  • Original 71.0 kB
  • After minification 52.7 kB
  • After compression 18.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 52.8 kB or 74% of the original size.

CSS Optimization

-80%

Potential reduce by 10.1 kB

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

Requests Breakdown

Number of requests can be reduced by 46 (41%)

Requests Now

113

After Optimization

67

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

div63.com

div63.com

1752 ms

effect1.css

effect1.css

4676 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

2751 ms

modernizr.custom.js

modernizr.custom.js

1827 ms

common.js

common.js

9458 ms

skrollr.min.js

skrollr.min.js

3320 ms

easingAndLazyload.js

easingAndLazyload.js

19610 ms

classie.js

classie.js

3766 ms

pathLoader.js

pathLoader.js

2670 ms

main.js

main.js

3348 ms

parallax.js

parallax.js

4659 ms

logo.gif

logo.gif

4170 ms

pxpi.jpg

pxpi.jpg

3944 ms

nianlun4.png

nianlun4.png

1497 ms

nianlun7.png

nianlun7.png

1767 ms

nianlun6.png

nianlun6.png

2663 ms

nianlun5.png

nianlun5.png

2682 ms

nianlun3.png

nianlun3.png

3384 ms

nianlun2.png

nianlun2.png

2824 ms

nianlun1.png

nianlun1.png

11996 ms

boat.png

boat.png

6379 ms

mountain.jpg

mountain.jpg

5453 ms

words.png

words.png

6537 ms

birds.png

birds.png

4362 ms

shu.jpg

shu.jpg

6624 ms

5.png

5.png

6209 ms

cc.jpg

cc.jpg

11991 ms

cc_1.jpg

cc_1.jpg

11393 ms

cc_weixin_1.jpg

cc_weixin_1.jpg

10750 ms

cc_weixin_2.jpg

cc_weixin_2.jpg

8674 ms

cc_weixin_3.jpg

cc_weixin_3.jpg

9524 ms

cc_weixin_4.jpg

cc_weixin_4.jpg

11663 ms

2015.jpg

2015.jpg

11311 ms

2015_1.jpg

2015_1.jpg

13352 ms

byd.jpg

byd.jpg

13426 ms

byd_1.jpg

byd_1.jpg

19181 ms

touch.jpg

touch.jpg

15705 ms

touch_1.jpg

touch_1.jpg

19983 ms

fumd.jpg

fumd.jpg

16049 ms

fumd_1.jpg

fumd_1.jpg

19022 ms

hione.jpg

hione.jpg

15375 ms

hione_1.jpg

hione_1.jpg

19983 ms

bsd.jpg

bsd.jpg

17541 ms

bsd_1.jpg

bsd_1.jpg

19983 ms

allove.jpg

allove.jpg

19984 ms

allove_1.jpg

allove_1.jpg

19983 ms

hm.js

hm.js

1182 ms

allove_2.jpg

allove_2.jpg

19949 ms

allove_3.jpg

allove_3.jpg

20490 ms

hanyufang.jpg

hanyufang.jpg

20221 ms

hanyufang_1.jpg

hanyufang_1.jpg

20325 ms

crl.jpg

crl.jpg

19061 ms

crl_1.jpg

crl_1.jpg

19892 ms

choutaifook.jpg

choutaifook.jpg

19227 ms

choutaifook_1.jpg

choutaifook_1.jpg

20045 ms

85years.jpg

85years.jpg

19820 ms

85years_1.jpg

85years_1.jpg

19624 ms

bet16.jpg

bet16.jpg

19533 ms

bet16_1.jpg

bet16_1.jpg

19777 ms

bet16_2.jpg

bet16_2.jpg

19607 ms

bet16_3.jpg

bet16_3.jpg

20449 ms

hyxt.jpg

hyxt.jpg

20360 ms

hyxt_1.jpg

hyxt_1.jpg

20310 ms

yidong.jpg

yidong.jpg

20018 ms

yidong_1.jpg

yidong_1.jpg

20233 ms

jmc.jpg

jmc.jpg

18801 ms

jmc_1.jpg

jmc_1.jpg

19591 ms

line.jpg

line.jpg

20320 ms

contact_me.jpg

contact_me.jpg

19994 ms

QQ.jpg

QQ.jpg

18646 ms

line2.jpg

line2.jpg

17680 ms

weibo.jpg

weibo.jpg

17742 ms

sprite.jpg

sprite.jpg

19607 ms

dot.jpg

dot.jpg

15992 ms

line3.jpg

line3.jpg

16147 ms

menu.gif

menu.gif

3770 ms

a1.png

a1.png

1612 ms

a2.png

a2.png

1089 ms

a3.png

a3.png

533 ms

b1.png

b1.png

1059 ms

b2.png

b2.png

1851 ms

b3.png

b3.png

1597 ms

c1.png

c1.png

1511 ms

c2.png

c2.png

1933 ms

c3.png

c3.png

5549 ms

d1.png

d1.png

2135 ms

d2.png

d2.png

2396 ms

d3.png

d3.png

2360 ms

d4.png

d4.png

2664 ms

d5.png

d5.png

2780 ms

e1.png

e1.png

2941 ms

e2.png

e2.png

3198 ms

e3.png

e3.png

5193 ms

f1.png

f1.png

3477 ms

f2.png

f2.png

3721 ms

f3.png

f3.png

4020 ms

g1.png

g1.png

8833 ms

g2.png

g2.png

6494 ms

g3.png

g3.png

4563 ms

g4.png

g4.png

5102 ms

g5.png

g5.png

5646 ms

h1.png

h1.png

5614 ms

h2.png

h2.png

10226 ms

h3.png

h3.png

7811 ms

h4.png

h4.png

6175 ms

h5.png

h5.png

6703 ms

i1.png

i1.png

7897 ms

i2.png

i2.png

8030 ms

i3.png

i3.png

8220 ms

i4.png

i4.png

8413 ms

obj_16.png

obj_16.png

11353 ms

obj_28.png

obj_28.png

9102 ms

obj_2.png

obj_2.png

8952 ms

obj_8.png

obj_8.png

20116 ms

obj_20.png

obj_20.png

9133 ms

obj_12.png

obj_12.png

8497 ms

obj_7.png

obj_7.png

9001 ms

obj_18.png

obj_18.png

8925 ms

obj_30.png

obj_30.png

9909 ms

obj_25.png

obj_25.png

9398 ms

obj_19.png

obj_19.png

12135 ms

obj_4.png

obj_4.png

10266 ms

obj_29.png

obj_29.png

12845 ms

obj_22.png

obj_22.png

14450 ms

obj_10.png

obj_10.png

9829 ms

obj_9.png

obj_9.png

10079 ms

obj_6.png

obj_6.png

11995 ms

obj_26.png

obj_26.png

9949 ms

obj_24.png

obj_24.png

11201 ms

obj_11.png

obj_11.png

16266 ms

obj_23.png

obj_23.png

12578 ms

obj_14.png

obj_14.png

10618 ms

obj_3.png

obj_3.png

10573 ms

obj_1.png

obj_1.png

13283 ms

obj_17.png

obj_17.png

18369 ms

obj_21.png

obj_21.png

13172 ms

obj_15.png

obj_15.png

11718 ms

obj_5.png

obj_5.png

12838 ms

kuang.png

kuang.png

13015 ms

SEO Factors

div63.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 Div63.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 Div63.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

div63.com

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