4.8 sec in total
1 sec
3.6 sec
153 ms
Welcome to teldap.tw homepage info - get ready to check TELDAP best content for Taiwan right away, or after learning these important things about teldap.tw
呈現臺灣多樣性,深化數位學習!數位典藏與數位學習國家型科技計畫是由行政院國家科學委員會所執行的國家型科技計畫...
Visit teldap.twWe analyzed Teldap.tw page load time and found that the first response time was 1 sec and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
teldap.tw performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value3.8 s
55/100
25%
Value8.4 s
18/100
10%
Value1,340 ms
17/100
30%
Value0.14
79/100
15%
Value14.3 s
9/100
10%
1029 ms
406 ms
43 ms
15 ms
244 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that 44% of them (20 requests) were addressed to the original Teldap.tw, 18% (8 requests) were made to Google.com and 11% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Teldap.tw.
Page size can be reduced by 72.0 kB (10%)
705.9 kB
633.9 kB
In fact, the total size of Teldap.tw main page is 705.9 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. 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. Javascripts take 375.2 kB which makes up the majority of the site volume.
Potential reduce by 22.5 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 7.7 kB, which is 26% 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 22.5 kB or 75% of the original size.
Potential reduce by 4.1 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. TELDAP images are well optimized though.
Potential reduce by 33.3 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 12.2 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. Teldap.tw needs all CSS files to be minified and compressed as it can save up to 12.2 kB or 15% of the original size.
Number of requests can be reduced by 19 (49%)
39
20
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of TELDAP. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
teldap.tw
1029 ms
teldap.css
406 ms
cse.js
43 ms
ga.js
15 ms
234X60cn.jpg
244 ms
234X60kw.jpg
658 ms
234X60brg.jpg
657 ms
234X60EQCC.jpg
912 ms
234X60wiki.jpg
745 ms
Teldap-tw_C2.jpg
919 ms
RSS.jpg
744 ms
icon_w3c_xhtml.jpg
864 ms
icon_wcag_a.jpg
860 ms
icon_w3c_css.jpg
919 ms
97prize2-1.jpg
1116 ms
norm_right_on.jpg
1031 ms
norm_left_on.jpg
1041 ms
norm_right.jpg
1082 ms
norm_left.jpg
1088 ms
array01.jpg
1089 ms
array02.jpg
1229 ms
__utm.gif
34 ms
footer.jpg
1216 ms
collect
55 ms
uYPRFWmuPA4
126 ms
cse_element__zh_tw.js
28 ms
default+zh_TW.css
53 ms
default.css
56 ms
ga-audiences
63 ms
async-ads.js
28 ms
branding.png
20 ms
clear.png
19 ms
nav_logo114.png
22 ms
www-player.css
6 ms
www-embed-player.js
26 ms
base.js
53 ms
ad_status.js
248 ms
LvMrC3vzHFP8SzxjvqNWRksbkOPiJTf11ILX4Pq8Ybc.js
81 ms
embed.js
38 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
125 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
129 ms
id
13 ms
Create
22 ms
GenerateIT
14 ms
validUser
796 ms
teldap.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.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
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
teldap.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
Page has valid source maps
teldap.tw SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document uses plugins
JA
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Teldap.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 Teldap.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.
teldap.tw
Open Graph description is not detected on the main page of TELDAP. 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: