Tools & Wizards About Us
whir.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

whir.net

北京万户软件技术有限公司

Page Load Speed

36.1 sec in total

First Response

1.7 sec

Resources Loaded

34.1 sec

Page Rendered

239 ms

whir.net screenshot

About Website

Welcome to whir.net homepage info - get ready to check Whir best content for China right away, or after learning these important things about whir.net

万户软件是业内普遍认可的智慧政务办公专家,OA系统国家行业标准编制组长单位,协同软件国家行业标准编制组长单位,22年专注协同管理领域.为您提供定制化的智慧政务一体化办公解决方案,政务OA系统,移动OA,政府OA,公文管理,信息报送,督查督办,协同OA,政务办公自动化,可以免费试用

Visit whir.net

Key Findings

We analyzed Whir.net page load time and found that the first response time was 1.7 sec and then it took 34.4 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

whir.net performance score

0

Network Requests Diagram

whir.net

1699 ms

bootstrap.css

1329 ms

css_whir.css

811 ms

wpa.php

767 ms

LOGO.jpg

890 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 63% of them (45 requests) were addressed to the original Whir.net, 7% (5 requests) were made to Qiao.baidu.com and 6% (4 requests) were made to V3.jiathis.com. The less responsive or slowest element that took the longest time to load (20.3 sec) belongs to the original domain Whir.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 848.4 kB (30%)

Content Size

2.8 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whir.net main page is 2.8 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. 30% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 54.8 kB

  • Original 72.5 kB
  • After minification 60.7 kB
  • After compression 17.8 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 11.8 kB, which is 16% 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 54.8 kB or 76% of the original size.

Image Optimization

-21%

Potential reduce by 472.5 kB

  • Original 2.3 MB
  • After minification 1.8 MB

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, Whir needs image optimization as it can save up to 472.5 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-48%

Potential reduce by 109.6 kB

  • Original 229.9 kB
  • After minification 228.6 kB
  • After compression 120.4 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 109.6 kB or 48% of the original size.

CSS Optimization

-86%

Potential reduce by 211.7 kB

  • Original 245.5 kB
  • After minification 202.7 kB
  • After compression 33.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. Whir.net needs all CSS files to be minified and compressed as it can save up to 211.7 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

68

After Optimization

43

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whir.net

whir.net

1699 ms

bootstrap.css

bootstrap.css

1329 ms

css_whir.css

css_whir.css

811 ms

wpa.php

wpa.php

767 ms

LOGO.jpg

LOGO.jpg

890 ms

11940380.js

11940380.js

962 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

931 ms

bootstrap.min.js

bootstrap.min.js

378 ms

demo.js

demo.js

380 ms

jia.js

jia.js

628 ms

banner.js

banner.js

517 ms

jia_this_img.jpg

jia_this_img.jpg

287 ms

navbar-toggle_03.jpg

navbar-toggle_03.jpg

285 ms

search_btn_03.jpg

search_btn_03.jpg

295 ms

search_pc_03.jpg

search_pc_03.jpg

494 ms

201304151428172817.jpg

201304151428172817.jpg

1089 ms

201305101026562656.jpg

201305101026562656.jpg

589 ms

201305061031493149.jpg

201305061031493149.jpg

600 ms

%E5%8C%97%E4%BA%AC%E5%B8%82%E5%9B%BD%E8%B5%84%E5%A7%94.jpg

%E5%8C%97%E4%BA%AC%E5%B8%82%E5%9B%BD%E8%B5%84%E5%A7%94.jpg

9737 ms

201304171028312831.jpg

201304171028312831.jpg

1068 ms

201304241718221822.jpg

201304241718221822.jpg

882 ms

%E5%93%88%E8%8D%AF%E9%9B%86%E5%9B%A2.jpg

%E5%93%88%E8%8D%AF%E9%9B%86%E5%9B%A2.jpg

10569 ms

20130415142406246.jpg

20130415142406246.jpg

970 ms

mobile_close_03.jpg

mobile_close_03.jpg

1152 ms

icon_menu_more_03.png

icon_menu_more_03.png

1270 ms

icon_menu_back.jpg

icon_menu_back.jpg

1384 ms

point_btn_1.png

point_btn_1.png

1377 ms

18%E5%B9%B4%E4%B8%93%E6%B3%A8%E5%B0%8F%E5%9B%BE.jpg

18%E5%B9%B4%E4%B8%93%E6%B3%A8%E5%B0%8F%E5%9B%BE.jpg

4744 ms

%E5%9F%8E%E5%B8%82%E5%B0%8F%E5%9B%BE.png

%E5%9F%8E%E5%B8%82%E5%B0%8F%E5%9B%BE.png

8815 ms

evo%E5%B0%8F%E5%9B%BE2.jpg

evo%E5%B0%8F%E5%9B%BE2.jpg

20333 ms

%E5%8C%BB%E7%96%97%E5%B0%8F%E5%9B%BE.jpg

%E5%8C%BB%E7%96%97%E5%B0%8F%E5%9B%BE.jpg

10014 ms

index_prev_03.png

index_prev_03.png

5005 ms

index_next_03.png

index_next_03.png

5279 ms

evo-V4%E5%B0%8F%E5%9B%BE2.jpg

evo-V4%E5%B0%8F%E5%9B%BE2.jpg

7710 ms

%E8%A7%86%E9%A2%91%E8%A7%A3%E5%86%B3%E6%96%B9%E6%A1%88%E5%B0%8F%E5%9B%BE.jpg

%E8%A7%86%E9%A2%91%E8%A7%A3%E5%86%B3%E6%96%B9%E6%A1%88%E5%B0%8F%E5%9B%BE.jpg

10999 ms

11.3%E5%8F%91%E5%B8%83.jpg

11.3%E5%8F%91%E5%B8%83.jpg

20331 ms

codePic_1.jpg

codePic_1.jpg

12385 ms

codePic_2.jpg

codePic_2.jpg

11058 ms

codePic_3.jpg

codePic_3.jpg

11628 ms

Panel.js

Panel.js

729 ms

localStorage.js

localStorage.js

748 ms

icon_9.gif

icon_9.gif

814 ms

brek_top_03.png

brek_top_03.png

10619 ms

jiathis_utility.html

jiathis_utility.html

8 ms

jiathis_share.css

jiathis_share.css

16 ms

plugin.client.js

plugin.client.js

7 ms

h.js

h.js

807 ms

contains.js

contains.js

264 ms

r.cgi

r.cgi

817 ms

ta.php

ta.php

3748 ms

crmqq.php

crmqq.php

16031 ms

wpa_first_heart_beat.php

wpa_first_heart_beat.php

663 ms

b.js

b.js

3592 ms

hm.gif

hm.gif

429 ms

index_close.png

index_close.png

9791 ms

index_dd_03.jpg

index_dd_03.jpg

9962 ms

index_ban_bg_03.png

index_ban_bg_03.png

10035 ms

18%E5%B9%B4%E4%B8%93%E6%B3%A8.jpg

18%E5%B9%B4%E4%B8%93%E6%B3%A8.jpg

12874 ms

%E5%9F%8E%E5%B8%82.png

%E5%9F%8E%E5%B8%82.png

19764 ms

%E7%A7%BB%E5%8A%A8%E4%BA%92%E8%81%94%E5%A4%A7%E5%9B%BExiao.jpg

%E7%A7%BB%E5%8A%A8%E4%BA%92%E8%81%94%E5%A4%A7%E5%9B%BExiao.jpg

15657 ms

%E5%8C%BB%E7%96%97xiao2.jpg

%E5%8C%BB%E7%96%97xiao2.jpg

14232 ms

bsl.js

bsl.js

879 ms

Enter.php

Enter.php

840 ms

main_icon_invite_mess_api.js

main_icon_invite_mess_api.js

1801 ms

main.css

main.css

17232 ms

fix.css

fix.css

898 ms

version.js

version.js

3544 ms

nopic.jpg

nopic.jpg

588 ms

12.jpg

12.jpg

8877 ms

hm.gif

hm.gif

2008 ms

hb.crm2.qq.com

hb.crm2.qq.com

1047 ms

hb.crm2.qq.com

hb.crm2.qq.com

541 ms

SEO Factors

whir.net 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 Whir.net 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 Whir.net 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

whir.net

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