Tools & Wizards About Us
wecare.tw screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

wecare.tw

WeCare 威克佳文共賞網站 - 入口網站首頁

Page Load Speed

6 sec in total

First Response

844 ms

Resources Loaded

4.9 sec

Page Rendered

287 ms

wecare.tw screenshot

About Website

Visit wecare.tw now to see the best up-to-date We Care content for Taiwan and also check out these interesting facts you probably never knew about wecare.tw

WeCare佳文共賞網站的心願很簡單：將網路流傳的優質文章予以整理、分類、放在平台網站上，省去個人重複收集、整理、分類、儲存所需花的精力，每位網友只要每天打開WeCare網站就可以看到新文章，或臨時想要尋找哪類的文章，很輕易就能找到，不用再從眾多的email中翻箱倒櫃苦苦尋找。 公益網站,心靈雞湯,心靈快遞,天下新鮮事,職場生存,佳文共賞,佳文,健康,保健,知識填充,戀戀英文,親情關係,親子

Visit wecare.tw

Key Findings

We analyzed Wecare.tw page load time and found that the first response time was 844 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

wecare.tw performance score

0

Network Requests Diagram

wecare.tw

844 ms

PortalHome.asp

2425 ms

pagestyle.css

661 ms

common.js

674 ms

ch_fonts.js

995 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 34% of them (28 requests) were addressed to the original Wecare.tw, 34% (28 requests) were made to Wecare.tw and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Wecare.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 220.0 kB (50%)

Content Size

437.7 kB

After Optimization

217.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wecare.tw main page is 437.7 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. 20% of websites need less resources to load. HTML takes 208.3 kB which makes up the majority of the site volume.

HTML Optimization

-93%

Potential reduce by 194.0 kB

  • Original 208.3 kB
  • After minification 206.0 kB
  • After compression 14.3 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 194.0 kB or 93% of the original size.

Image Optimization

-6%

Potential reduce by 12.5 kB

  • Original 195.7 kB
  • After minification 183.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. We Care images are well optimized though.

JavaScript Optimization

-24%

Potential reduce by 5.8 kB

  • Original 24.4 kB
  • After minification 22.3 kB
  • After compression 18.5 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 5.8 kB or 24% of the original size.

CSS Optimization

-82%

Potential reduce by 7.7 kB

  • Original 9.4 kB
  • After minification 8.2 kB
  • After compression 1.7 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. Wecare.tw needs all CSS files to be minified and compressed as it can save up to 7.7 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (53%)

Requests Now

80

After Optimization

38

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wecare.tw

wecare.tw

844 ms

PortalHome.asp

PortalHome.asp

2425 ms

pagestyle.css

pagestyle.css

661 ms

common.js

common.js

674 ms

ch_fonts.js

ch_fonts.js

995 ms

portalHome.css

portalHome.css

233 ms

ga.js

ga.js

9 ms

bgL.gif

bgL.gif

220 ms

bullet-27.gif

bullet-27.gif

472 ms

__utm.gif

__utm.gif

29 ms

clear.gif

clear.gif

242 ms

wecare.4550_wecare_165_logo_2.GIF

wecare.4550_wecare_165_logo_2.GIF

474 ms

41952.3159_300[head2.JPG

41952.3159_300[head2.JPG

1048 ms

41.1105_0000.jpg

41.1105_0000.jpg

490 ms

78.1036_00s00.jpg

78.1036_00s00.jpg

457 ms

30.5429_00s000.jpg

30.5429_00s000.jpg

740 ms

1.1929_0R000q1.jpg

1.1929_0R000q1.jpg

638 ms

42.1131_00~0i0.jpg

42.1131_00~0i0.jpg

678 ms

39.1216_0p000.jpg

39.1216_0p000.jpg

717 ms

34.1202_00q00.jpg

34.1202_00q00.jpg

734 ms

37133.1755_2100.JPG

37133.1755_2100.JPG

856 ms

45811.2149_dogbit.gif

45811.2149_dogbit.gif

918 ms

27566.0909_0P0n000.JPG

27566.0909_0P0n000.JPG

959 ms

7900.3553_00[head4.JPG

7900.3553_00[head4.JPG

1712 ms

headline.gif

headline.gif

993 ms

new_articles.gif

new_articles.gif

1064 ms

clear.gif

clear.gif

246 ms

shadowL.gif

shadowL.gif

406 ms

bgLogo.gif

bgLogo.gif

442 ms

menu-l.gif

menu-l.gif

441 ms

menu-arrow.gif

menu-arrow.gif

446 ms

menu-m.gif

menu-m.gif

462 ms

menu-r.gif

menu-r.gif

490 ms

login_01.gif

login_01.gif

622 ms

10706.2827_1.gif

10706.2827_1.gif

621 ms

login_03.gif

login_03.gif

641 ms

login_11.gif

login_11.gif

659 ms

login_14.gif

login_14.gif

685 ms

login_02.gif

login_02.gif

733 ms

clear.gif

clear.gif

831 ms

bullet-130.gif

bullet-130.gif

819 ms

121957.1628_wecare_09002.GIF

121957.1628_wecare_09002.GIF

872 ms

10764.3710_article.gif

10764.3710_article.gif

885 ms

bg_menu.gif

bg_menu.gif

892 ms

login_05.gif

login_05.gif

939 ms

login_04.gif

login_04.gif

983 ms

login_06.gif

login_06.gif

999 ms

login_12.gif

login_12.gif

1052 ms

76565.4633_0L02.JPG

76565.4633_0L02.JPG

736 ms

76564.2802_0y02.JPG

76564.2802_0y02.JPG

808 ms

49521.1842_kongshi.gif

49521.1842_kongshi.gif

1094 ms

39245.5819_0C0g002.JPG

39245.5819_0C0g002.JPG

844 ms

132066.5641_0S0i0s0i0.JPG

132066.5641_0S0i0s0i0.JPG

861 ms

64284.0026_000J00T.JPG

64284.0026_000J00T.JPG

968 ms

121603.1451_0j0a00C2.JPG

121603.1451_0j0a00C2.JPG

1049 ms

47155.1655_000S042.JPG

47155.1655_000S042.JPG

1060 ms

10763.2914_image012.gif

10763.2914_image012.gif

718 ms

10765.2259_news_title.gif

10765.2259_news_title.gif

736 ms

NEWS2-24.gif

NEWS2-24.gif

811 ms

NEWS2-26.gif

NEWS2-26.gif

812 ms

NEWS2-32.gif

NEWS2-32.gif

833 ms

NEWS2-25.gif

NEWS2-25.gif

894 ms

NEWS2-27.gif

NEWS2-27.gif

927 ms

NEWS2-28.gif

NEWS2-28.gif

971 ms

NEWS2-31.gif

NEWS2-31.gif

1052 ms

NEWS2-29.gif

NEWS2-29.gif

1011 ms

NEWS2-30.gif

NEWS2-30.gif

1038 ms

NEWS2-33.gif

NEWS2-33.gif

1110 ms

NEWS2-35.gif

NEWS2-35.gif

1143 ms

NEWS2-36.gif

NEWS2-36.gif

1195 ms

NEWS2-16.gif

NEWS2-16.gif

1214 ms

NEWS2-17.gif

NEWS2-17.gif

1244 ms

NEWS2-37.gif

NEWS2-37.gif

1280 ms

NEWS2-19.gif

NEWS2-19.gif

1307 ms

NEWS2-20.gif

NEWS2-20.gif

1336 ms

NEWS2-38.gif

NEWS2-38.gif

1381 ms

NEWS2-18.gif

NEWS2-18.gif

1348 ms

NEWS2-1.gif

NEWS2-1.gif

1263 ms

74557.2905_wecare00y6.JPG

74557.2905_wecare00y6.JPG

1356 ms

bgFooter.gif

bgFooter.gif

1338 ms

shadowR.gif

shadowR.gif

1337 ms

bgR.gif

bgR.gif

1353 ms

SEO Factors

wecare.tw SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    ZH

  • Encoding

    BIG5

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wecare.tw can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed Chinese language. Our system also found out that Wecare.tw main page’s claimed encoding is big5. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

wecare.tw

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