4.9 sec in total
994 ms
3.6 sec
307 ms
Click here to check amazing Digitalarchives content for Taiwan. Otherwise, check out these important facts you probably never knew about digitalarchives.tw
典藏台灣 Taiwan Digitalarchives ,是中央研究院數位文化中心呈現數位典藏歷年成果與服務的網站平台 ,誠摯邀請您參與科技與文化的知識饗宴 ...
Visit digitalarchives.twWe analyzed Digitalarchives.tw page load time and found that the first response time was 994 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
digitalarchives.tw performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value4.8 s
31/100
25%
Value9.5 s
12/100
10%
Value2,230 ms
6/100
30%
Value0
100/100
15%
Value14.9 s
8/100
10%
994 ms
411 ms
417 ms
1499 ms
414 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 45% of them (25 requests) were addressed to the original Digitalarchives.tw, 13% (7 requests) were made to Apis.google.com and 9% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Char.iis.sinica.edu.tw.
Page size can be reduced by 740.9 kB (59%)
1.3 MB
523.6 kB
In fact, the total size of Digitalarchives.tw main page is 1.3 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. 50% of websites need less resources to load. Javascripts take 643.0 kB which makes up the majority of the site volume.
Potential reduce by 45.9 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 45.9 kB or 75% of the original size.
Potential reduce by 51.3 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. Obviously, Digitalarchives needs image optimization as it can save up to 51.3 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 420.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 420.3 kB or 65% of the original size.
Potential reduce by 223.4 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. Digitalarchives.tw needs all CSS files to be minified and compressed as it can save up to 223.4 kB or 83% of the original size.
Number of requests can be reduced by 23 (44%)
52
29
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Digitalarchives. 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 from 4 to 1 for CSS and as a result speed up the page load time.
digitalarchives.tw
994 ms
main.css
411 ms
index.css
417 ms
ics.js
1499 ms
autocomplete.css
414 ms
jquery-1.4.4.min.js
1107 ms
jquery-ui-1.8.7.custom.min.js
1348 ms
autocomplete.js
660 ms
plusone.js
50 ms
page.js
11 ms
urchin.js
22 ms
ga.js
96 ms
cb=gapi.loaded_0
149 ms
bg2010_0.jpg
619 ms
get_flash_player.gif
75 ms
__utm.gif
67 ms
h1.jpg
250 ms
1282.jpg
673 ms
4502693.jpg
840 ms
2484686.jpg
671 ms
294649.jpg
849 ms
TO008.jpg
467 ms
taggin180x180.jpg
678 ms
EncounterOldTaipei.jpg
1217 ms
CCC200X40.jpg
890 ms
teldapblog200x40.jpg
889 ms
dd.jpg
899 ms
ebook200.jpg
1044 ms
NTCH.jpg
1054 ms
game01.jpg
1107 ms
game02.jpg
1108 ms
share_save_171_16.png
1118 ms
__utm.gif
46 ms
hMQEMda4LJQ
142 ms
like.php
117 ms
zh-TW.js
81 ms
footer.jpg
1151 ms
cb=gapi.loaded_1
37 ms
fastbutton
121 ms
postmessageRelay
48 ms
vpc6VNjRPXV.js
207 ms
LVx-xkvaJ0b.png
206 ms
sm13.html
40 ms
api.js
57 ms
core:rpc:shindig.random:shindig.sha1.js
109 ms
2536007149-postmessagerelay.js
98 ms
www-embed-player-vflZsBgOl.css
120 ms
www-embed-player.js
148 ms
cb=gapi.loaded_0
64 ms
cb=gapi.loaded_1
54 ms
ga.js
110 ms
grlryt2bdKIyfMSOhzd1eA.woff
144 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
27 ms
ad_status.js
29 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
20 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
51 ms
digitalarchives.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
Form elements do not have associated labels
<object> elements do not have alternate text
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
digitalarchives.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
digitalarchives.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
ZH
N/A
BIG5
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Digitalarchives.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 Digitalarchives.tw main page’s claimed encoding is big5. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
digitalarchives.tw
Open Graph description is not detected on the main page of Digitalarchives. 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: