6.6 sec in total
972 ms
5.4 sec
211 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 972 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
digitalarchives.tw performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value4.9 s
28/100
25%
Value10.9 s
6/100
10%
Value2,520 ms
4/100
30%
Value0
100/100
15%
Value18.3 s
3/100
10%
972 ms
209 ms
412 ms
596 ms
817 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 40% of them (25 requests) were addressed to the original Digitalarchives.tw, 10% (6 requests) were made to Apis.google.com and 10% (6 requests) were made to Static.addtoany.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Digitalarchives.tw.
Page size can be reduced by 62.6 kB (8%)
823.1 kB
760.4 kB
In fact, the total size of Digitalarchives.tw main page is 823.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. 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 458.4 kB which makes up the majority of the site volume.
Potential reduce by 30.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 30.9 kB or 70% of the original size.
Potential reduce by 16.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. Digitalarchives images are well optimized though.
Potential reduce by 14.2 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 851 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. Digitalarchives.tw has all CSS files already compressed.
Number of requests can be reduced by 24 (44%)
54
30
The browser has sent 54 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 22 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
digitalarchives.tw
972 ms
main.css
209 ms
index.css
412 ms
autocomplete.css
596 ms
jquery-1.4.4.min.js
817 ms
jquery-ui-1.8.7.custom.min.js
1054 ms
autocomplete.js
619 ms
js
61 ms
plusone.js
17 ms
page.js
45 ms
page.js
38 ms
ics.js
802 ms
cb=gapi.loaded_0
115 ms
hMQEMda4LJQ
262 ms
like.php
423 ms
1367300.jpg
788 ms
2474524.jpg
788 ms
2484667.jpg
789 ms
TO128.jpg
350 ms
taggin180x180.jpg
327 ms
90_anni_banner.jpg
328 ms
teldapblog200x40.jpg
786 ms
dd.jpg
787 ms
ebook200.jpg
992 ms
NTCH.jpg
993 ms
game01.jpg
1138 ms
game02.jpg
991 ms
js
81 ms
analytics.js
157 ms
sm.25.html
151 ms
eso.BRQnzO8v.js
151 ms
cb=gapi.loaded_1
98 ms
fastbutton
94 ms
eso.BRQnzO8v.js
82 ms
bg2010_0.jpg
948 ms
www-player.css
44 ms
www-embed-player.js
99 ms
base.js
177 ms
collect
73 ms
postmessageRelay
137 ms
zh-TW.js
87 ms
developers.google.com
615 ms
collect
71 ms
TttXWwYVW0v.js
360 ms
FEppCFCt76d.png
358 ms
h1.jpg
775 ms
ga-audiences
530 ms
3604799710-postmessagerelay.js
361 ms
rpc:shindig_random.js
329 ms
ad_status.js
215 ms
vTEfc-jlr9e_tfMt-BR8Zcc1_6XGLRk25TFtjqWuknE.js
125 ms
embed.js
49 ms
KFOmCnqEu92Fr1Mu4mxM.woff
170 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
171 ms
share_save_171_16.png
401 ms
footer.jpg
410 ms
CCC200X40.jpg
409 ms
3463.jpg
417 ms
cb=gapi.loaded_0
43 ms
Create
139 ms
id
15 ms
GenerateIT
15 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
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
Page has valid source maps
digitalarchives.tw SEO score
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: