Tools & Wizards About Us
phpvar.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

phpvar.com

Phpvar's Blog - WEB前端技术分享，APP开发，PHP编程学习 - phpvar.com

Page Load Speed

31.5 sec in total

First Response

903 ms

Resources Loaded

30.1 sec

Page Rendered

437 ms

phpvar.com screenshot

About Website

Welcome to phpvar.com homepage info - get ready to check Phpvar best content for China right away, or after learning these important things about phpvar.com

关注Web前端:DIV+CSS/JQuery/HTML5+CSS3，学习分享PHP、Smarty。 phpvar's blog提供jquery,php,html5+css3,js,photoshop, wordpress,互联网资讯等阅读信息。

Visit phpvar.com

Key Findings

We analyzed Phpvar.com page load time and found that the first response time was 903 ms and then it took 30.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

phpvar.com performance score

0

Network Requests Diagram

phpvar.com

903 ms

www.phpvar.com

2047 ms

style.css

528 ms

comments.css

544 ms

jquery-1.7.2.min.js

827 ms

Our browser made a total of 146 requests to load all elements on the main page. We found that 35% of them (51 requests) were addressed to the original Phpvar.com, 8% (12 requests) were made to Gravatar.duoshuo.com and 5% (8 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (15.7 sec) relates to the external source Q.qlogo.cn.

Page Optimization Overview & Recommendations

Page size can be reduced by 819.2 kB (44%)

Content Size

1.9 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 89.5 kB

  • Original 115.2 kB
  • After minification 109.7 kB
  • After compression 25.7 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 89.5 kB or 78% of the original size.

Image Optimization

-8%

Potential reduce by 54.5 kB

  • Original 643.8 kB
  • After minification 589.2 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. Phpvar images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 552.4 kB

  • Original 942.5 kB
  • After minification 922.3 kB
  • After compression 390.1 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 552.4 kB or 59% of the original size.

CSS Optimization

-80%

Potential reduce by 122.8 kB

  • Original 152.7 kB
  • After minification 144.6 kB
  • After compression 29.9 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. Phpvar.com needs all CSS files to be minified and compressed as it can save up to 122.8 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 61 (45%)

Requests Now

136

After Optimization

75

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

phpvar.com

phpvar.com

903 ms

www.phpvar.com

www.phpvar.com

2047 ms

style.css

style.css

528 ms

comments.css

comments.css

544 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

827 ms

pirobox.min.js

pirobox.min.js

552 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

564 ms

myscript.js

myscript.js

758 ms

wb.js

wb.js

1318 ms

style.css

style.css

1002 ms

jquery.js

jquery.js

2308 ms

jquery-migrate.min.js

jquery-migrate.min.js

1020 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

1036 ms

jquery.fader.js

jquery.fader.js

1290 ms

slideplayer.js

slideplayer.js

1313 ms

adsbygoogle.js

adsbygoogle.js

68 ms

show_ads.js

show_ads.js

96 ms

o.js

o.js

1246 ms

avatar.php

avatar.php

972 ms

icon_sub01.gif

icon_sub01.gif

1032 ms

avatar.php

avatar.php

1102 ms

avatar.php

avatar.php

974 ms

avatar.php

avatar.php

1101 ms

avatar.php

avatar.php

1102 ms

avatar.php

avatar.php

1088 ms

bg_fixed.jpg

bg_fixed.jpg

1225 ms

icon_sub01.gif

icon_sub01.gif

549 ms

radom.jpg

radom.jpg

484 ms

skin_select_flag.png

skin_select_flag.png

550 ms

bg2.jpg

bg2.jpg

504 ms

bg3.jpg

bg3.jpg

587 ms

bg4.jpg

bg4.jpg

967 ms

bg5.jpg

bg5.jpg

1212 ms

bg_thumb.jpg

bg_thumb.jpg

1025 ms

20120824134434287951.JPG

20120824134434287951.JPG

1632 ms

4.jpg

4.jpg

1311 ms

2.jpg

2.jpg

1693 ms

jdb.jpg

jdb.jpg

1850 ms

comment_pic9.png

comment_pic9.png

1672 ms

comment_pic7.png

comment_pic7.png

1697 ms

comment_pic4.png

comment_pic4.png

1819 ms

comment_pic6.png

comment_pic6.png

2139 ms

alipay_qr.jpg

alipay_qr.jpg

2163 ms

bbs.jpg

bbs.jpg

2098 ms

ca-pub-5711620247461684.js

ca-pub-5711620247461684.js

156 ms

zrt_lookup.html

zrt_lookup.html

154 ms

show_ads_impl.js

show_ads_impl.js

155 ms

comment.gif

comment.gif

2058 ms

x.jpg

x.jpg

2167 ms

quote.png

quote.png

2169 ms

wcnm

wcnm

2440 ms

ads

ads

389 ms

osd.js

osd.js

96 ms

ads

ads

351 ms

m_js_controller.js

m_js_controller.js

94 ms

abg.js

abg.js

111 ms

3724551677886892671

3724551677886892671

161 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

73 ms

favicon

favicon

75 ms

mobile_unified_button_icon_white.png

mobile_unified_button_icon_white.png

66 ms

s

s

49 ms

x_button_blue2.png

x_button_blue2.png

28 ms

j6SDDiQit5YY48GNgPpnCluJgoNCzbKlh5o6eVjReZI.js

j6SDDiQit5YY48GNgPpnCluJgoNCzbKlh5o6eVjReZI.js

14 ms

2be6312b64d141bb3497655286af52fb

2be6312b64d141bb3497655286af52fb

195 ms

e2b0c27c2a2ef862a280789c2e56a6de

e2b0c27c2a2ef862a280789c2e56a6de

234 ms

75e215cea7a9364665ca688b5a23a58a

75e215cea7a9364665ca688b5a23a58a

228 ms

d9266a95c9f7c061be6fabcc45b4ee84

d9266a95c9f7c061be6fabcc45b4ee84

225 ms

d41d8cd98f00b204e9800998ecf8427e

d41d8cd98f00b204e9800998ecf8427e

210 ms

1d8bed157478baca1c97b8303d08b0da

1d8bed157478baca1c97b8303d08b0da

206 ms

activeview

activeview

23 ms

activeview

activeview

39 ms

bigfuns.jpg

bigfuns.jpg

678 ms

wcnm

wcnm

1235 ms

embed.js

embed.js

318 ms

ads

ads

293 ms

index.php

index.php

12325 ms

index.php

index.php

928 ms

icon_top.png

icon_top.png

483 ms

footer.png

footer.png

488 ms

h.js

h.js

1158 ms

2673383875329918000

2673383875329918000

71 ms

embed.default.css

embed.default.css

103 ms

embed.compat.js

embed.compat.js

259 ms

listVisitors.json

listVisitors.json

2833 ms

counts.json

counts.json

1708 ms

jquery.js

jquery.js

759 ms

quickfollownewstyle2.css

quickfollownewstyle2.css

542 ms

follow_quick_05.js

follow_quick_05.js

545 ms

hm.gif

hm.gif

332 ms

stat.php

stat.php

1592 ms

quickfollowbgnew.gif

quickfollowbgnew.gif

220 ms

stat.htm

stat.htm

399 ms

core.php

core.php

870 ms

100

100

15478 ms

158472.jpg

158472.jpg

1152 ms

noavatar_default.png

noavatar_default.png

126 ms

50

50

15590 ms

1

1

1060 ms

1aee5c70d25798c23ff6590012acf62f

1aee5c70d25798c23ff6590012acf62f

319 ms

48222.jpg

48222.jpg

1173 ms

117855.jpg

117855.jpg

1184 ms

63409.jpg

63409.jpg

1219 ms

212590.jpg

212590.jpg

1218 ms

50

50

15588 ms

50

50

15598 ms

50

50

15637 ms

50

50

15656 ms

100

100

15492 ms

100

100

15535 ms

100

100

15488 ms

100

100

15536 ms

100

100

15491 ms

100

100

15701 ms

9.gif

9.gif

890 ms

ga.js

ga.js

157 ms

close_btn.png

close_btn.png

620 ms

t_l.png

t_l.png

676 ms

t_c.png

t_c.png

674 ms

t_r.png

t_r.png

676 ms

c_l.png

c_l.png

1051 ms

c_r.png

c_r.png

1115 ms

b_l.png

b_l.png

1116 ms

b_c.png

b_c.png

1149 ms

b_r.png

b_r.png

1500 ms

play.png

play.png

1463 ms

prev.png

prev.png

1548 ms

next.png

next.png

1545 ms

__utm.gif

__utm.gif

44 ms

app.gif

app.gif

921 ms

weiboShow.css

weiboShow.css

611 ms

skin_default.css

skin_default.css

616 ms

gaea_1_19.js

gaea_1_19.js

660 ms

show.js

show.js

6 ms

suda.js

suda.js

4 ms

1

1

1947 ms

btns_bg.png

btns_bg.png

38 ms

icon_follow.png

icon_follow.png

36 ms

bg_trans.png

bg_trans.png

25 ms

icon_tips.png

icon_tips.png

25 ms

tmp.gif

tmp.gif

686 ms

o.htm

o.htm

685 ms

ui

ui

37 ms

hm.gif

hm.gif

762 ms

wh.js

wh.js

691 ms

ac.js

ac.js

505 ms

fp.htm

fp.htm

679 ms

SEO Factors

phpvar.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 Phpvar.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 Phpvar.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

phpvar.com

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