15.6 sec in total
6.7 sec
8.5 sec
345 ms
Visit pulilife.com now to see the best up-to-date Pulilife content for Taiwan and also check out these interesting facts you probably never knew about pulilife.com
大埔里報曾獲得文化部「全國最佳社區報獎」表揚,是埔里、國姓、仁愛、魚池在地社區報,秉持專業獨立的原則,報導在地民眾關心的地方事,並提供求職求才、房地產、特產、名產服務需求,獨立辦報、公民媒體是我們的特色,在傳統媒體捨棄在地觀點的報導角度,我們翻轉過來,讓地方人為中心,報導地方事。
Visit pulilife.comWe analyzed Pulilife.com page load time and found that the first response time was 6.7 sec and then it took 8.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
pulilife.com performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value34.3 s
0/100
25%
Value26.2 s
0/100
10%
Value22,150 ms
0/100
30%
Value0
100/100
15%
Value35.7 s
0/100
10%
6731 ms
14 ms
148 ms
8 ms
148 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 49% of them (53 requests) were addressed to the original Pulilife.com, 21% (23 requests) were made to Static.xx.fbcdn.net and 13% (14 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (6.7 sec) belongs to the original domain Pulilife.com.
Page size can be reduced by 554.6 kB (17%)
3.4 MB
2.8 MB
In fact, the total size of Pulilife.com main page is 3.4 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. 70% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 113.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 113.3 kB or 81% of the original size.
Potential reduce by 88.6 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. Pulilife images are well optimized though.
Potential reduce by 200.6 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 200.6 kB or 64% of the original size.
Potential reduce by 152.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. Pulilife.com needs all CSS files to be minified and compressed as it can save up to 152.0 kB or 83% of the original size.
Number of requests can be reduced by 44 (42%)
106
62
The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pulilife. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
pulilife.com
6731 ms
ga.js
14 ms
style.css
148 ms
font-awesome.css
8 ms
polls-css.css
148 ms
style.css
148 ms
style.css
151 ms
style.css
150 ms
style.css
422 ms
jetpack.css
388 ms
addtoany.min.css
211 ms
jquery.js
678 ms
jquery-migrate.min.js
282 ms
conect_js.js
274 ms
javascript.js
280 ms
responsive.js
483 ms
__utm.gif
14 ms
rps.js
585 ms
scroll-back-to-top.js
296 ms
polls-js.js
323 ms
devicepx-jetpack.js
12 ms
gprofiles.js
59 ms
wpgroho.js
371 ms
javascript.js
499 ms
effect.min.js
570 ms
effect-transfer.min.js
487 ms
e-201611.js
10 ms
pulilifelogo.png
434 ms
1040621-Wildgingerflower.jpg
662 ms
1040211-sakura.png
947 ms
1040709-paper.jpg
467 ms
1040824-frontcover.jpg
588 ms
1040621-familydoctor.png
217 ms
1040705-newhomeland.png
467 ms
1041109-newera.png
578 ms
1040512-cowtail.png
590 ms
1050318-pub05.jpg
742 ms
1050304-pol01.jpg
658 ms
1050104-pub01.jpg
809 ms
1041016-pub03.jpg
816 ms
1041013-pub01.jpg
878 ms
1041013-pub05.jpg
850 ms
1041012-pub01.jpg
954 ms
1040901-edu01.jpg
955 ms
1050318-peo01.jpg
960 ms
1050318-pub01.jpg
925 ms
1050317-pub01.jpg
952 ms
1050316-pol01.jpg
1067 ms
1050316-art01.jpg
1019 ms
1050307-art01.jpg
1027 ms
1050313-tra01.jpg
1172 ms
1050312-tra01.jpg
1104 ms
1050312-life01.jpg
1041 ms
Facebook-icon.png
1091 ms
twitter_icon.png
1099 ms
rss-icon.png
1113 ms
Arrow-left.png
1127 ms
Arrow-right.png
1150 ms
search.jpg
1150 ms
all.js
28 ms
page.js
27 ms
fontawesome-webfont.woff
23 ms
g.gif
20 ms
likebox.php
325 ms
hovercard.css
30 ms
services.css
59 ms
116 ms
xd_arbiter.php
26 ms
xd_arbiter.php
63 ms
GQC5fPqoIZg.css
41 ms
53PWlu84QA_.css
44 ms
n8nvUYC7DwC.css
48 ms
kArENQJk9d4.css
57 ms
h9QRFUUhEdT.css
51 ms
jL8HIF05Xri.css
47 ms
TKuNj0xVh4A.js
45 ms
ehA1CqzHyzE.js
70 ms
0wM5s1Khldu.js
48 ms
1bNoFZUdlYZ.js
48 ms
njO1TPvGzoR.js
45 ms
1QuX41zDRrx.js
77 ms
Oagsvfb4VWi.js
78 ms
LTv6ZK-5zxz.js
81 ms
1FCa-btixu2.js
77 ms
12806108_998234733563145_5911816577277902264_n.jpg
100 ms
safe_image.php
124 ms
10551016_733972783322676_6750183915623410647_n.jpg
26 ms
12341582_148178142212765_6494054760093437967_n.jpg
26 ms
10632714_142170506167334_2294985175555618251_n.jpg
29 ms
10629850_864076773610210_6992729662735265011_n.jpg
46 ms
11870672_422509931266259_2198537204982203051_n.jpg
27 ms
10346458_757021881057146_7163354193959401683_n.jpg
28 ms
12020005_795575940554980_6128165126328635_n.jpg
29 ms
12032017_632943100142272_414889717947490663_n.jpg
58 ms
10580227_1051030141634240_3212262391602341713_n.jpg
60 ms
564446_1009968445723107_1761344954455815468_n.jpg
143 ms
1780738_1050709621666292_710880709401799405_n.jpg
99 ms
1383032_1050720901665164_3071037840228960393_n.jpg
47 ms
12805725_1050396018364319_4321133652716473519_n.jpg
160 ms
wL6VQj7Ab77.png
21 ms
s7jcwEQH7Sx.png
22 ms
QDwYpIaRyfG.png
23 ms
bNvHN6v1NeH.png
22 ms
t-wz8gw1xG1.png
21 ms
K00K-UgnsKu.png
22 ms
I6-MnjEovm5.js
4 ms
pQrUxxo5oQp.js
6 ms
ping
69 ms
pulilife.com accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
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
[id] attributes on active, focusable elements are not unique
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
pulilife.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
pulilife.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
JA
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pulilife.com 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 Pulilife.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.
pulilife.com
Open Graph data is detected on the main page of Pulilife. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: