2.8 sec in total
538 ms
1.8 sec
394 ms
Click here to check amazing LIFE content for Taiwan. Otherwise, check out these important facts you probably never knew about life.com.tw
台灣生活網 | 關心生活大小事
Visit life.com.twWe analyzed Life.com.tw page load time and found that the first response time was 538 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
life.com.tw performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value25.7 s
0/100
25%
Value8.4 s
19/100
10%
Value3,400 ms
2/100
30%
Value0.651
9/100
15%
Value23.1 s
1/100
10%
538 ms
43 ms
71 ms
39 ms
37 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 4% of them (4 requests) were addressed to the original Life.com.tw, 33% (30 requests) were made to Fc2.sharewa.com and 26% (24 requests) were made to Images.900.tw. The less responsive or slowest element that took the longest time to load (538 ms) belongs to the original domain Life.com.tw.
Page size can be reduced by 1.2 MB (35%)
3.3 MB
2.2 MB
In fact, the total size of Life.com.tw main page is 3.3 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. Images take 3.2 MB which makes up the majority of the site volume.
Potential reduce by 36.4 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 36.4 kB or 78% of the original size.
Potential reduce by 1.1 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, LIFE needs image optimization as it can save up to 1.1 MB or 34% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 9.8 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 9.8 kB or 20% of the original size.
Potential reduce by 76.3 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. Life.com.tw needs all CSS files to be minified and compressed as it can save up to 76.3 kB or 87% of the original size.
Number of requests can be reduced by 42 (47%)
90
48
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LIFE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and as a result speed up the page load time.
www.life.com.tw
538 ms
jquery.min.js
43 ms
jsapi
71 ms
jquery.Xslider.js
39 ms
jquery.sticky.js
37 ms
imgLiquid-min.js
36 ms
searchGoogle.js
37 ms
index.css
67 ms
banner
186 ms
banner
205 ms
show_ads.js
26 ms
headbg-blue.gif
16 ms
logo.png
14 ms
969b8bd278786fff2096ad998c6d90da.jpg
20 ms
home.png
7 ms
hot-up.png
11 ms
line.gif
13 ms
searchbg.png
11 ms
searchbtn.png
8 ms
nav-rightbg.png
13 ms
home-cur.png
11 ms
bg-top.jpg
11 ms
bg-bot.jpg
17 ms
08aa0b2e04c14b799b988bed83208b81.jpg
29 ms
390972.png
45 ms
398292.jpeg
18 ms
398289.jpeg
22 ms
398286.jpeg
16 ms
398082.jpeg
32 ms
398009.jpeg
23 ms
397998.png
27 ms
397692.png
46 ms
397645.jpeg
30 ms
397345.jpeg
30 ms
398267.jpeg
35 ms
398252.jpeg
77 ms
398240.jpeg
33 ms
398324.jpeg
47 ms
398318.jpeg
36 ms
398228.jpeg
40 ms
398323.jpeg
43 ms
398004.jpeg
42 ms
398305.jpeg
45 ms
398149.jpeg
462 ms
398300.jpeg
47 ms
398313.jpeg
57 ms
hotarticle-bg.png
18 ms
hot-article-titlebg.png
130 ms
h-more.png
134 ms
hot-listbg.png
136 ms
point.png
135 ms
home-bannertxt.png
128 ms
home-bannerbtn-h.png
128 ms
home-bannerbtn.png
133 ms
tab-titlebg.jpg
134 ms
opacity.png
133 ms
author_iicon.png
132 ms
ca-pub-5677318061671730.js
198 ms
zrt_lookup.html
189 ms
show_ads_impl.js
133 ms
ga.js
181 ms
atrk.js
217 ms
fbds.js
179 ms
petbg.png
31 ms
eatbg.png
31 ms
travelbg.png
31 ms
mobilebg.png
32 ms
financebg.png
30 ms
socialbg.png
30 ms
blue-thead.gif
81 ms
blue-arrow-up.png
82 ms
blue-tbody.gif
82 ms
point01.png
86 ms
top-blue.png
81 ms
ads
205 ms
osd.js
38 ms
ads
268 ms
134 ms
__utm.gif
14 ms
atrk.gif
33 ms
test.png
170 ms
1636947521873339579
40 ms
abg.js
42 ms
m_js_controller.js
54 ms
googlelogo_color_112x36dp.png
92 ms
s
27 ms
redir.html
54 ms
x_button_blue2.png
27 ms
45 ms
iframe.html
41 ms
ui
41 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
2 ms
life.com.tw accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
life.com.tw best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
life.com.tw SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Life.com.tw can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 Life.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.
life.com.tw
Open Graph data is detected on the main page of LIFE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: