7.6 sec in total
302 ms
7.1 sec
229 ms
Welcome to pil.tw homepage info - get ready to check Pil best content for Taiwan right away, or after learning these important things about pil.tw
討論區 ,PALMisLIFE 討論區
Visit pil.twWe analyzed Pil.tw page load time and found that the first response time was 302 ms and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
pil.tw performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value3.5 s
63/100
25%
Value5.0 s
63/100
10%
Value60 ms
100/100
30%
Value0
100/100
15%
Value4.5 s
82/100
10%
302 ms
484 ms
10 ms
234 ms
440 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Pil.tw, 69% (81 requests) were made to F.pil.tw and 8% (9 requests) were made to Brain.adbot.tw. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source F.pil.tw.
Page size can be reduced by 68.5 kB (11%)
629.1 kB
560.6 kB
In fact, the total size of Pil.tw main page is 629.1 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. 45% of websites need less resources to load. Javascripts take 381.6 kB which makes up the majority of the site volume.
Potential reduce by 50.7 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 50.7 kB or 75% of the original size.
Potential reduce by 15.7 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. Pil images are well optimized though.
Potential reduce by 1.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. This website has mostly compressed JavaScripts.
Potential reduce by 262 B
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. Pil.tw has all CSS files already compressed.
Number of requests can be reduced by 41 (38%)
108
67
The browser has sent 108 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pil. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and as a result speed up the page load time.
forum.php
302 ms
forum.php
484 ms
jquery.min.js
10 ms
style_7_common.css
234 ms
style_7_forum_index.css
440 ms
common.js
664 ms
bootstrap.min.js
747 ms
forum.js
472 ms
show_ads.js
69 ms
top.js
1056 ms
fb.js
1061 ms
ping.js
449 ms
discuz_tips.js
1281 ms
jquery.min.js
380 ms
7892388000_1a09aec5ca_o.jpg
16 ms
6175509572_6d544c4f6d_o.png
15 ms
3199753976_b53fd04f82_o.gif
16 ms
logolinks.gif
393 ms
07a7168b3e66be69074c8a3b2e072b0a9e1fd3b2.png
95 ms
eis_body.gif
237 ms
eis_toptb.gif
235 ms
pil_logox.png
235 ms
collapsed_no.gif
234 ms
common_68_icon.gif
440 ms
common_80_icon.gif
441 ms
common_67_icon.png
447 ms
common_75_icon.gif
453 ms
common_76_icon.gif
544 ms
common_77_icon.gif
591 ms
common_1_icon.gif
658 ms
common_2_icon.gif
658 ms
common_46_icon.gif
670 ms
common_16_icon.gif
679 ms
common_3_icon.gif
757 ms
common_65_icon.gif
768 ms
common_4_icon.gif
876 ms
common_23_icon.gif
877 ms
common_30_icon.gif
894 ms
common_74_icon.gif
905 ms
common_54_icon.gif
981 ms
common_66_icon.gif
996 ms
common_19_icon.gif
1094 ms
common_45_icon.gif
1094 ms
common_72_icon.gif
1117 ms
common_47_icon.gif
1131 ms
common_43_icon.gif
1206 ms
common_9_icon.gif
1225 ms
common_10_icon.gif
1313 ms
common_28_icon.gif
1313 ms
common_61_icon.gif
1342 ms
common_60_icon.gif
1360 ms
common_62_icon.gif
1431 ms
common_55_icon.gif
1454 ms
6175433724_b5e0f77887_o.png
11 ms
6175509572_6d544c4f6d_o.png
160 ms
7892388000_1a09aec5ca_o.jpg
148 ms
3199753976_b53fd04f82_o.gif
142 ms
6175433724_b5e0f77887_o.png
123 ms
adsbygoogle.js
153 ms
show_ads_impl.js
247 ms
afr.php
1328 ms
afr.php
1323 ms
afr.php
1345 ms
common_8_icon.gif
1354 ms
common_11_icon.gif
1356 ms
ga.js
15 ms
common_34_icon.gif
1372 ms
all.js
30 ms
__utm.gif
32 ms
all.js
5 ms
40 ms
618f9dbdb692406872c2bae8ba228145.min.js
196 ms
common_18_icon.gif
1336 ms
common_13_icon.gif
1341 ms
forum.gif
1355 ms
collapsed_yes.gif
1364 ms
zrt_lookup.html
54 ms
ads
61 ms
security.png
1296 ms
eis_header.gif
1551 ms
ypalocation.js
184 ms
icon
43 ms
ypakeywords.js
364 ms
js.cookie.min.js
546 ms
md5.min.js
553 ms
data.min.js
551 ms
func.min.js
916 ms
lineads.min.js
552 ms
adskeyword
241 ms
eis_nv.gif
1337 ms
qmenu.png
1340 ms
eis_nv_a.gif
1355 ms
eis_1.gif
1363 ms
eis_2.gif
1354 ms
eis_3.gif
1444 ms
eis_4.gif
1341 ms
eis_5.gif
1372 ms
eis_6.gif
1375 ms
eis_7.gif
1431 ms
eis_8.gif
1390 ms
eis_sc.gif
1435 ms
search.png
1342 ms
arrwd.gif
1378 ms
pt_item.png
1378 ms
chart.png
1430 ms
eis_bar_bg.gif
1393 ms
eis_bar_l.gif
1423 ms
eis_bar_r.gif
1341 ms
csdn.png
1382 ms
scrolltop.png
1380 ms
tip_bottom.png
1426 ms
latfpkws.js
756 ms
da356fc9f4d88363cf207b49eac477bc.jpg
1275 ms
lg.php
1325 ms
038985033a9e5a79cbb6f6525e492861.png
1316 ms
lg.php
1367 ms
b7c65601969476da06c50f7de5ee1cda.jpg
1598 ms
lg.php
1438 ms
pil.tw 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
pil.tw best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
pil.tw SEO score
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
Tap targets are not sized appropriately
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pil.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 Pil.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.
pil.tw
Open Graph description is not detected on the main page of Pil. 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: