7.2 sec in total
1 sec
5.9 sec
296 ms
Welcome to life2c.com homepage info - get ready to check Life2c best content for Taiwan right away, or after learning these important things about life2c.com
「Life2c」 生活平台 - 提供會員Jetso優惠, 星座運勢, 免費宣傳平台, 一切娛樂!
Visit life2c.comWe analyzed Life2c.com page load time and found that the first response time was 1 sec and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
life2c.com performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value4.2 s
43/100
25%
Value4.2 s
77/100
10%
Value560 ms
53/100
30%
Value0.102
89/100
15%
Value8.4 s
39/100
10%
1010 ms
500 ms
1659 ms
495 ms
506 ms
Our browser made a total of 119 requests to load all elements on the main page. We found that 39% of them (46 requests) were addressed to the original Life2c.com, 13% (16 requests) were made to Static.xx.fbcdn.net and 7% (8 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Life2c.com.
Page size can be reduced by 437.0 kB (75%)
584.3 kB
147.3 kB
In fact, the total size of Life2c.com main page is 584.3 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. 70% of websites need less resources to load. Javascripts take 303.0 kB which makes up the majority of the site volume.
Potential reduce by 146.1 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 146.1 kB or 79% of the original size.
Potential reduce by 242 B
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. Life2c images are well optimized though.
Potential reduce by 216.7 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 216.7 kB or 72% of the original size.
Potential reduce by 74.0 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. Life2c.com needs all CSS files to be minified and compressed as it can save up to 74.0 kB or 88% of the original size.
Number of requests can be reduced by 59 (54%)
110
51
The browser has sent 110 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Life2c. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
life2c.com
1010 ms
style.css
500 ms
jquery-1.8.1.js
1659 ms
jquery.alerts.js
495 ms
jquery.ui.draggable.js
506 ms
jquery.alerts.css
674 ms
mobile_style.css
1179 ms
common.css
950 ms
colorbox.css
956 ms
jquery.colorbox.js
1192 ms
commonjs.js
1177 ms
swfobject.js
1408 ms
jquery.cycle.all.js
1870 ms
addthis_widget.js
18 ms
css
29 ms
all.js
9 ms
adsbygoogle.js
7 ms
css
15 ms
webfont.js
105 ms
12720115_10153994969219561_1401523748_n.jpg
108 ms
special_content.png
478 ms
bg2.png
1610 ms
logo.png
463 ms
top_head.png
463 ms
member.png
486 ms
facebook.png
736 ms
share.png
736 ms
instagram.png
980 ms
post.png
974 ms
home.png
1148 ms
play_icon.png
1222 ms
749910640895.JPG
1223 ms
798413862224.jpg
1427 ms
979113495383.jpg
1430 ms
953856427399.png
1657 ms
654387243072.jpg
2815 ms
601425472015.jpg
2435 ms
642913523260.jpg
2910 ms
12719691_1127031963988322_910207039_n.jpg
97 ms
12323481_1141634619194723_1032178987_n.jpg
105 ms
12066891_1197185506980205_125094235_n.jpg
95 ms
11838487_1198102660221823_287373120_n.jpg
104 ms
11114450_1136253133065912_1232260840_n.jpg
102 ms
new_jetso_content.png
908 ms
new_content.png
734 ms
view_icon.png
734 ms
new_video_content.png
964 ms
play_icon.png
924 ms
more_btn.png
1151 ms
funny_picture_content.png
1361 ms
left_arrow.png
1212 ms
right_arrow.png
1378 ms
189 ms
sdk.js
40 ms
xd_arbiter.php
58 ms
xd_arbiter.php
136 ms
css
56 ms
top_line_bg.png
1981 ms
top_long_bg.png
2157 ms
top_menu_bg.png
2208 ms
center_bg.png
2449 ms
mfglabsiconset-webfont.svg
3282 ms
-g5pDUSRgvxvOl5u-a_WHw.woff
43 ms
ca-pub-7635929195042665.js
117 ms
zrt_lookup.html
112 ms
show_ads_impl.js
75 ms
analytics.js
84 ms
300lo.json
52 ms
sh.8e5f85691f9aaa082472a194.html
46 ms
ie67-css.d5089428ac7f05efd372.js
47 ms
overlay.png
2529 ms
ads
397 ms
osd.js
25 ms
collect
38 ms
page.php
180 ms
ads
329 ms
layers.e5ea973510bf60b3db41.js
12 ms
ads
335 ms
collect
192 ms
lC5byrMk91f.css
34 ms
zUnijUuZBag.css
43 ms
haVjXmh8926.css
46 ms
q68gy-v_YMF.js
39 ms
k19Xse48j5I.js
64 ms
ihptErjAmMX.js
42 ms
3So47A9WcrL.js
64 ms
cUsKAwzqrQw.js
75 ms
10696306_822977101081699_7532039111027750843_n.jpg
108 ms
safe_image.php
2527 ms
lRyN50VcaFW.js
52 ms
safe_image.php
2034 ms
safe_image.php
1425 ms
safe_image.php
1607 ms
safe_image.php
1546 ms
10882131_822976681081741_6089966264664027703_n.png
51 ms
wL6VQj7Ab77.png
50 ms
s7jcwEQH7Sx.png
48 ms
GtIpNnEyqq_.png
49 ms
m_js_controller.js
55 ms
abg.js
80 ms
css
123 ms
favicon
127 ms
googlelogo_color_112x36dp.png
103 ms
favicon
134 ms
nessie_icon_tiamat_white.png
50 ms
s
36 ms
x_button_blue2.png
31 ms
imgad
28 ms
nessie_icon_magazine_black.png
9 ms
nessie_icon_magazine_white.png
8 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
13 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
23 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
26 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
34 ms
layersIE6.css
25 ms
R9a_DtVRZgv.js
6 ms
cUDgRFxaoIk.js
7 ms
0JBr1QHp8Gi.js
9 ms
kDOzhTr2W91.js
7 ms
life2c.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Links do not have a discernible name
life2c.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Uses deprecated APIs
Browser errors were logged to the console
life2c.com SEO score
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Life2c.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 Life2c.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.
life2c.com
Open Graph description is not detected on the main page of Life2c. 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: