5.5 sec in total
434 ms
4.7 sec
393 ms
Welcome to blink.com.tw homepage info - get ready to check Blink best content for Taiwan right away, or after learning these important things about blink.com.tw
做大夢、做大事、論大議題、寫大觀點,走出同溫層,大學生優質觀點文章。
Visit blink.com.twWe analyzed Blink.com.tw page load time and found that the first response time was 434 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
blink.com.tw performance score
name
value
score
weighting
Value7.4 s
1/100
10%
Value24.4 s
0/100
25%
Value26.2 s
0/100
10%
Value1,250 ms
19/100
30%
Value0.334
34/100
15%
Value40.8 s
0/100
10%
434 ms
1504 ms
5 ms
359 ms
575 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 14% of them (11 requests) were addressed to the original Blink.com.tw, 47% (36 requests) were made to Thumbor.blink.com.tw and 5% (4 requests) were made to V2.zopim.com. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source Thumbor.blink.com.tw.
Page size can be reduced by 688.3 kB (36%)
1.9 MB
1.2 MB
In fact, the total size of Blink.com.tw main page is 1.9 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 230.0 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 230.0 kB or 71% of the original size.
Potential reduce by 46.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. Blink images are well optimized though.
Potential reduce by 164.5 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 164.5 kB or 60% of the original size.
Potential reduce by 247.1 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. Blink.com.tw needs all CSS files to be minified and compressed as it can save up to 247.1 kB or 83% of the original size.
Number of requests can be reduced by 15 (22%)
67
52
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Blink. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
blink.com.tw
434 ms
www.blink.com.tw
1504 ms
font-awesome.min.css
5 ms
animate-custom.css
359 ms
component.css
575 ms
colorbox.css
400 ms
load.sumome.com
377 ms
dc.js
92 ms
analytics.js
88 ms
fbevents.js
89 ms
5344_83uaudvvaqg2e5nvtp56501gf.png
1625 ms
logo_blinkbear.gif
363 ms
btn_app_store.png
396 ms
btn_google_play.png
402 ms
logo_footer.png
400 ms
presskit.png
402 ms
5344_b26zvf39vzaervfjf9u2fyhk8.png
1478 ms
5344_2o4m0bhwkpoqwe8ps89lxzqjp.png
1680 ms
5344_6lmq3uynxwk7q55rlxfjonzwb.png
1528 ms
5344_d906efw51vu7cb4y1h5yil8zl.png
1463 ms
5344_99t234uwrcgqtg6u3w48tdynd.png
1932 ms
20515_7h9cpgvip5k46ribfu4o4zbox.png
1641 ms
5344_bnbhc13hkk194yuwbvfgpt54z.jpg
1658 ms
16_a9h6h95d3om3124xwrssi5yh7.png
1726 ms
27116_30pjz17cl2yig17r5s1cs1vfc.jpg
1792 ms
1_eyn4tumk0fqkypyq919czg1xc.jpg
1836 ms
45440_11gamo729uebwohtqm1yp39jk.jpg
1852 ms
5344_9uyg0zegx8a16zda87j8bpv72.jpg
1879 ms
5292_10ctd81rd7z4eih9fg7ycg6up.jpg
1924 ms
5292_7hj7pjbhdaaajdptydiqh3x12.jpg
1980 ms
5344_e6rqivnodpgh2jr43gqcfpskv.png
2012 ms
73470_2kx3i2gb8c15rhtmt51np1qnr.png
2212 ms
73470_9cvq2elyg7e3v6cbprt5al13l.jpg
2066 ms
73470_cay8aabkfdvjju3usxl1tffpa.jpg
2120 ms
73470_3qn0jon7fyjxydfgli2fimk00.jpg
2129 ms
73470_524488t4qi1uqu2he337xrae3.jpg
2149 ms
29814_7rgzooz9rjddrnhrdxo8si0kw.png
2187 ms
list_bg.png
2251 ms
5292_5iru7kmrqxf240khril9jkle8.jpg
2319 ms
5292_2bvke18uvw96orf5oy1iy6o9u.jpg
2328 ms
5292_ciu3txw6hgd81dwyagtlt3mth.jpg
2320 ms
66ffdgyt0wt1f55fja476zlkv.jpg
2364 ms
dyysbykkiffoktvcx2keth7q3.jpg
2391 ms
a7r5w38h69g06nte1w6r5i01a.jpg
2436 ms
a8dnes6vpekp92gzcw9cbqt0e.jpg
2520 ms
6ngtknaz96gtzra9at35ugg4r.jpg
2491 ms
5292_6nmw4akw0g25jo6doqb6dkgft.jpg
2526 ms
5292_ay9sw5ch9yp34s9nl2belkgbm.jpg
2538 ms
5292_4i1wizjub7t3yr9igjt01x7hi.jpg
2571 ms
5292_2k8d6ruuzkxxqfjn9lt70bpsk.jpg
2622 ms
5292_f2mwo7pz9vmtzwxh4o7x377u.jpg
2661 ms
sdk.js
74 ms
arr.png
436 ms
widget_v2.132.js
68 ms
sSns2mwVoNk
164 ms
fontawesome-webfont.woff
65 ms
collect
144 ms
236 ms
__utm.gif
125 ms
__$$__stringtable_lang_zh_CN.js
80 ms
collect
165 ms
ga-audiences
151 ms
www-embed-player-vflQrT_sR.css
112 ms
www-embed-player.js
127 ms
base.js
163 ms
149 ms
xd_arbiter.php
101 ms
xd_arbiter.php
230 ms
ga-audiences
80 ms
yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js
10 ms
ad_status.js
45 ms
CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff
34 ms
RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff
35 ms
__$$__stringtable_lang_zh_TW.js
4 ms
avatar_simple_visitor.png
72 ms
aL63HcygAAVYuCCsAAA==
1 ms
blink.com.tw 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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
blink.com.tw 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
Missing source maps for large first-party JavaScript
blink.com.tw SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blink.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 Blink.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.
blink.com.tw
Open Graph data is detected on the main page of Blink. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: