12.1 sec in total
2.3 sec
9.4 sec
392 ms
Visit test.businessweekly.com.tw now to see the best up-to-date Test Businessweekly content for Taiwan and also check out these interesting facts you probably never knew about test.businessweekly.com.tw
全台最有影響力財經雜誌《商業周刊》網站,每日更新最新「經濟、焦點、國際、職場、財經、生活」等深度報導文章。幫你掌握國家經濟時事、分析國際大事、財經洞察、管理知識、職場進修及新生活風格。培養競爭力,立即訂閱商周!
Visit test.businessweekly.com.twWe analyzed Test.businessweekly.com.tw page load time and found that the first response time was 2.3 sec and then it took 9.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
test.businessweekly.com.tw performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value18.9 s
0/100
25%
Value27.2 s
0/100
10%
Value700 ms
42/100
30%
Value0.714
7/100
15%
Value17.8 s
4/100
10%
2287 ms
903 ms
681 ms
462 ms
34 ms
Our browser made a total of 191 requests to load all elements on the main page. We found that 9% of them (17 requests) were addressed to the original Test.businessweekly.com.tw, 42% (80 requests) were made to Adspending01.bwnet.com.tw and 34% (65 requests) were made to Ibw.bwnet.com.tw. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source Adspending01.bwnet.com.tw.
Page size can be reduced by 589.8 kB (29%)
2.0 MB
1.4 MB
In fact, the total size of Test.businessweekly.com.tw main page is 2.0 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. 55% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 135.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. This page needs HTML code to be minified as it can gain 42.1 kB, which is 25% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 135.4 kB or 81% of the original size.
Potential reduce by 100.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. Test Businessweekly images are well optimized though.
Potential reduce by 299.0 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 299.0 kB or 58% of the original size.
Potential reduce by 54.6 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. Test.businessweekly.com.tw needs all CSS files to be minified and compressed as it can save up to 54.6 kB or 79% of the original size.
Number of requests can be reduced by 45 (24%)
186
141
The browser has sent 186 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Test Businessweekly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
test.businessweekly.com.tw
2287 ms
style.css
903 ms
home.css
681 ms
ie10.css
462 ms
jquery.min.js
34 ms
jquery.scrollTo-min.js
456 ms
navscript.js
458 ms
jquery.als.min.js
708 ms
swfobject.js
889 ms
jquery.cycle.all.js
1145 ms
jquery.idle.home.js
892 ms
jquery_lazyload.js
916 ms
slides.min.jquery.js
732 ms
WebResource.axd
946 ms
ScriptResource.axd
939 ms
ScriptResource.axd
966 ms
default.aspx
1443 ms
s
671 ms
s
465 ms
s
467 ms
s
466 ms
s
516 ms
s
520 ms
s
869 ms
s
872 ms
s
903 ms
s
905 ms
s
948 ms
s
951 ms
s
1280 ms
s
1316 ms
s
1306 ms
s
1342 ms
s
1415 ms
s
1415 ms
s
1687 ms
s
1719 ms
s
1731 ms
s
1783 ms
s
1803 ms
s
1832 ms
s
2097 ms
s
2131 ms
s
2172 ms
s
2194 ms
s
2242 ms
s
2237 ms
s
2546 ms
s
2533 ms
s
2583 ms
s
2653 ms
s
2647 ms
s
2645 ms
jquery.SuperSlide.2.1.1.js
546 ms
s
2504 ms
s
2533 ms
s
2540 ms
s
2608 ms
dc.js
27 ms
analytics.js
6 ms
collect
44 ms
LOGOslogan.png
1343 ms
s
2586 ms
0000001479.jpg
1561 ms
0000000088.jpg
1360 ms
0000000531.jpg
1570 ms
27647-1453455192_100.jpg
1570 ms
28909_310.jpg
1576 ms
28908_310.jpg
1945 ms
28907_310.jpg
1804 ms
28822-1458265509_310.jpg
1971 ms
28707-1456455540.gif
2012 ms
s
2585 ms
__utm.gif
14 ms
__utm.gif
10 ms
collect
62 ms
s
2502 ms
s
2540 ms
s
2540 ms
s
2581 ms
s
2560 ms
s
2591 ms
system_icon.png
1054 ms
line_dotted_v.png
1061 ms
white_line.png
1261 ms
black_70.png
1262 ms
cse.js
17 ms
s
2533 ms
cse.js
47 ms
s
2511 ms
s
2555 ms
jsapi
32 ms
s
2587 ms
default+zh_TW.css
4 ms
minimalist.css
45 ms
default+zh_TW.I.js
15 ms
minimalist.css
6 ms
s
2504 ms
s
2573 ms
s
2539 ms
s
2500 ms
s
2599 ms
s
2585 ms
s
2580 ms
s
2597 ms
s
2571 ms
s
2536 ms
s
2603 ms
s
2587 ms
s
2570 ms
s
2635 ms
s
2577 ms
s
2560 ms
s
2635 ms
s
2590 ms
s
2573 ms
s
2677 ms
s
2577 ms
s
2558 ms
s
2633 ms
s
2586 ms
new_icon.png
210 ms
arrowformore_2.png
208 ms
content_bg.png
209 ms
s
1426 ms
arrow_36.png
208 ms
line_dotted_h.png
217 ms
0647b1954b3482ab15044f1221170a2e.jpg
206 ms
line_dotted_v.png
216 ms
channel_icon_all.png
215 ms
system_icon.png
311 ms
black_line.png
288 ms
line_dotted_h.png
312 ms
circle_48.png
374 ms
button.png
403 ms
7d4127be442801014ab3abd1bc0a4b26.jpg
386 ms
black_line.png
486 ms
71707a5a78ba83a8a09b3294347215e3.jpg
416 ms
f7c5f29daa6160dd47a745a981c9f803.jpg
210 ms
7142118f31fc9cce4d078b1f0ceeeb9f.jpg
264 ms
89eb9245224abf1164957f1956181f90.jpg
298 ms
2043a8c335318f75ddee211ecf5562e0.gif
1565 ms
f9ca39d699bb75640dbcce4a87804820.jpg
684 ms
445c56abd715b683c98d84593978d456.jpg
209 ms
591f9ce407423b6186f12c0fedbcfa74.jpg
1427 ms
1dd1e17a568a139fa8cf4e1e1f8685d4.jpg
207 ms
s-140502.jpg
619 ms
0bd9e26330d11843b993110758a903a9.jpg
460 ms
548964734b1accd03367f1b686c8b2bb.jpg
450 ms
edbb1cad06775d46403857854ad1360d.jpg
244 ms
black_80.png
236 ms
beacon.js
125 ms
atrk.js
143 ms
plusone.js
163 ms
s
325 ms
s
495 ms
s
494 ms
discuss_2537_20160319122614.jpg
1304 ms
async-ads.js
89 ms
google_custom_search_watermark.gif
45 ms
black_60.png
231 ms
28905_190.jpg
221 ms
739d87037ef0265659d8da4bed10c819_100.jpg
221 ms
4c1ed828a73da314ff1cd281ef0aa32e_100.png
267 ms
7dc9a453bbb7a724254eff7b23ec8736_100.png
296 ms
f4009b0860834de7071ff41da5618796_100.jpg
407 ms
13861ae6f6499fb2e06b32d9888f0c47_250.jpg
845 ms
7a01e062f29ae06d0464bb9791e932d4_250.jpg
635 ms
70a737503bcd2e6fab2e3a848cc40b2a_250.jpg
434 ms
90e4f462f780de80a4d95eb03e77f8d4_250.jpg
665 ms
2293519285f702ac33d895df43428f18_250.jpg
922 ms
a77d8a16e2753216b63115495c616061_250.jpg
612 ms
016aaad40b4d469002fe6b93d5c1c9fc_250.jpg
849 ms
a9c4c2df4a2b285755d8e9d14f385a0f_250.jpg
1021 ms
b255a7912608c595a89d195910384f73_250.jpg
843 ms
479bce5744c112a853175d45fec75c08_250.jpg
1071 ms
cc051508b890a6a6b951bfc0b3002415_250.jpg
1054 ms
b20f3f98cb2283a2e4b1c1da463cb4fc_250.jpg
1057 ms
a0192c62c9e1a8f96cac52b714c2ac2c_250.jpg
1070 ms
2d375ce14191dc6595aee10260164157_250.jpg
1354 ms
2ef059c6ae37ffd87a759c81be15fb15_250.jpg
1229 ms
8af54aeeabba69467e493caf89c169a1_250.jpg
1471 ms
28677.gif
1266 ms
28507_250.jpg
1277 ms
small-logo.png
20 ms
clear.gif
20 ms
google_custom_search_watermark.gif
27 ms
atrk.gif
55 ms
test.png
301 ms
cb=gapi.loaded_0
23 ms
0_64.jpg
1193 ms
test.businessweekly.com.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.
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
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
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
test.businessweekly.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
test.businessweekly.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
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 Test.businessweekly.com.tw 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 Test.businessweekly.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.
test.businessweekly.com.tw
Open Graph data is detected on the main page of Test Businessweekly. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: