Tools & Wizards About Us
lifewin.com.tw screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

lifewin.com.tw

Lifewin 生活贏家 - 您的線上市調網

Page Load Speed

7.1 sec in total

First Response

2.1 sec

Resources Loaded

4.8 sec

Page Rendered

207 ms

lifewin.com.tw screenshot

About Website

Click here to check amazing Lifewin content. Otherwise, check out these important facts you probably never knew about lifewin.com.tw

Lifewin 線上市調網是一個免費賺點省荷包的網路市調平台，登入 Lifewin 線上市調網及參與推薦、填問卷、投票等活動，即可免費賺「購物金」，「購物金」可享購物折抵。

Visit lifewin.com.tw

Key Findings

We analyzed Lifewin.com.tw page load time and found that the first response time was 2.1 sec and then it took 5 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

lifewin.com.tw performance score

0

Network Requests Diagram

lifewin.com.tw

2056 ms

jquery.min.js

1618 ms

base.css

403 ms

ExampleStyle.css

409 ms

ExampleScripts.js

635 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 72% of them (57 requests) were addressed to the original Lifewin.com.tw, 8% (6 requests) were made to Pagead2.googlesyndication.com and 5% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Lifewin.com.tw.

Page Optimization Overview & Recommendations

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

Content Size

430.7 kB

After Optimization

216.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-91%

Potential reduce by 82.8 kB

  • Original 91.4 kB
  • After minification 43.1 kB
  • After compression 8.6 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 48.4 kB, which is 53% 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 82.8 kB or 91% of the original size.

Image Optimization

-8%

Potential reduce by 5.0 kB

  • Original 63.8 kB
  • After minification 58.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. Lifewin images are well optimized though.

JavaScript Optimization

-44%

Potential reduce by 115.2 kB

  • Original 261.2 kB
  • After minification 257.3 kB
  • After compression 146.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 115.2 kB or 44% of the original size.

CSS Optimization

-81%

Potential reduce by 11.6 kB

  • Original 14.3 kB
  • After minification 9.0 kB
  • After compression 2.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. Lifewin.com.tw needs all CSS files to be minified and compressed as it can save up to 11.6 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

75

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lifewin.com.tw

lifewin.com.tw

2056 ms

jquery.min.js

jquery.min.js

1618 ms

base.css

base.css

403 ms

ExampleStyle.css

ExampleStyle.css

409 ms

ExampleScripts.js

ExampleScripts.js

635 ms

adroder.js

adroder.js

216 ms

adsbygoogle.js

adsbygoogle.js

5 ms

ga.js

ga.js

5 ms

layout.css

layout.css

217 ms

about.css

about.css

215 ms

member.css

member.css

216 ms

desire.css

desire.css

212 ms

vote.css

vote.css

208 ms

star.css

star.css

487 ms

SpryTabbedPanels.css

SpryTabbedPanels.css

496 ms

__utm.gif

__utm.gif

12 ms

01_headLogo.gif

01_headLogo.gif

301 ms

01_headBanner.gif

01_headBanner.gif

448 ms

02_menu1Link.gif

02_menu1Link.gif

213 ms

02_menu2.gif

02_menu2.gif

206 ms

02_menu3.gif

02_menu3.gif

202 ms

02_menu4.gif

02_menu4.gif

303 ms

02_menu5.gif

02_menu5.gif

403 ms

02_menu6.gif

02_menu6.gif

421 ms

02_menu7.gif

02_menu7.gif

447 ms

03_searchBtnSend.gif

03_searchBtnSend.gif

514 ms

05_loginBtnLogin.gif

05_loginBtnLogin.gif

521 ms

AuthCode.php

AuthCode.php

613 ms

05_loginBtnAddmem.gif

05_loginBtnAddmem.gif

623 ms

05_loginBtnForget.gif

05_loginBtnForget.gif

648 ms

05_loginBtnVerify.gif

05_loginBtnVerify.gif

650 ms

05_loginBtnEpaper.gif

05_loginBtnEpaper.gif

727 ms

05_loginBtnService.gif

05_loginBtnService.gif

738 ms

AD_Fortune.gif

AD_Fortune.gif

1214 ms

%E9%84%AD%E5%A4%A7%E5%B8%AB_175x65.gif

%E9%84%AD%E5%A4%A7%E5%B8%AB_175x65.gif

1032 ms

ad2.gif

ad2.gif

861 ms

08_newsHead.gif

08_newsHead.gif

863 ms

09_chartHead.gif

09_chartHead.gif

941 ms

example14-6174.png

example14-6174.png

1175 ms

user_RankPhoto.gif

user_RankPhoto.gif

1075 ms

jym_join_masterstw_261x68.gif

jym_join_masterstw_261x68.gif

1086 ms

11_voteHead.gif

11_voteHead.gif

1154 ms

surveyBtn.gif

surveyBtn.gif

1235 ms

13_shopHead.gif

13_shopHead.gif

1288 ms

file1.jpg

file1.jpg

1309 ms

file1.jpg

file1.jpg

1369 ms

file1.jpg

file1.jpg

1611 ms

file1.jpg

file1.jpg

1427 ms

t.js

t.js

720 ms

02_menuBg.gif

02_menuBg.gif

1425 ms

03_searchBg1.gif

03_searchBg1.gif

1487 ms

03_searchBg2.gif

03_searchBg2.gif

1507 ms

03_searchBg3.gif

03_searchBg3.gif

1568 ms

analytics.js

analytics.js

5 ms

collect

collect

43 ms

ca-pub-9941021777691973.js

ca-pub-9941021777691973.js

120 ms

zrt_lookup.html

zrt_lookup.html

37 ms

show_ads_impl.js

show_ads_impl.js

59 ms

collect

collect

83 ms

ads

ads

224 ms

osd.js

osd.js

5 ms

04_crumbBg.gif

04_crumbBg.gif

1434 ms

05_loginBg.gif

05_loginBg.gif

1445 ms

06_banner.gif

06_banner.gif

1732 ms

08_newsBg.gif

08_newsBg.gif

1454 ms

09_chartBg.gif

09_chartBg.gif

1502 ms

m_js_controller.js

m_js_controller.js

20 ms

abg.js

abg.js

33 ms

11_voteBg.gif

11_voteBg.gif

1432 ms

favicon

favicon

43 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

33 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

27 ms

s

s

17 ms

x_button_blue2.png

x_button_blue2.png

7 ms

13_shopBg.gif

13_shopBg.gif

1410 ms

14_qlinkBg.gif

14_qlinkBg.gif

1412 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

3 ms

s.gif

s.gif

362 ms

activeview

activeview

13 ms

SEO Factors

lifewin.com.tw 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 Lifewin.com.tw 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 Lifewin.com.tw 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

lifewin.com.tw

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