7.8 sec in total
1.2 sec
6.2 sec
376 ms
Visit wunderkammer.ki.se now to see the best up-to-date Wunderkammer Ki content for Sweden and also check out these interesting facts you probably never knew about wunderkammer.ki.se
Here you can read about and look at pictures of old and rare books within a wide range of biomedical subjects.
Visit wunderkammer.ki.seWe analyzed Wunderkammer.ki.se page load time and found that the first response time was 1.2 sec and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
wunderkammer.ki.se performance score
name
value
score
weighting
Value7.3 s
1/100
10%
Value8.1 s
2/100
25%
Value10.2 s
8/100
10%
Value750 ms
39/100
30%
Value0.364
29/100
15%
Value9.9 s
27/100
10%
1152 ms
1392 ms
127 ms
1528 ms
160 ms
Our browser made a total of 33 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Wunderkammer.ki.se, 6% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source Hagstromerlibrary.ki.se.
Page size can be reduced by 261.9 kB (20%)
1.3 MB
1.0 MB
In fact, the total size of Wunderkammer.ki.se 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. 30% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 25.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 5.8 kB, which is 19% 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 25.4 kB or 85% of the original size.
Potential reduce by 4.0 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. Wunderkammer Ki images are well optimized though.
Potential reduce by 50 B
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 232.5 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. Wunderkammer.ki.se needs all CSS files to be minified and compressed as it can save up to 232.5 kB or 90% of the original size.
We found no issues to fix!
32
32
The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wunderkammer Ki. According to our analytics all requests are already optimized.
wunderkammer
1152 ms
application-5c695e272230fd9cb87db70c0130a012.css
1392 ms
css
127 ms
application-f597e5e6286b8fa4a3cd9d4ae44df1d7.js
1528 ms
js
160 ms
hs-logo.png
243 ms
wklist.jpg
355 ms
wklist.jpg
829 ms
wklist.jpg
475 ms
wklist.jpg
820 ms
wklist.jpg
1054 ms
wklist.jpg
1168 ms
wklist.jpg
810 ms
wklist.jpg
941 ms
wklist.jpg
1275 ms
wklist.jpg
1400 ms
wklist.jpg
1520 ms
wklist.jpg
1413 ms
wklist.jpg
1630 ms
wklist.jpg
1867 ms
wklist.jpg
1787 ms
wklist.jpg
1983 ms
wklist.jpg
2109 ms
wklist.jpg
2332 ms
wklist.jpg
2211 ms
wklist.jpg
2250 ms
hs-logo-footer.png
2217 ms
ki-logo-72004e4596fd37c9f093d7cdf17d8513.png
2333 ms
sls-logo-0d8c481516e6879f75acd7b784f10d2c.png
2460 ms
BauWeb-Medium.woff
2638 ms
BauWeb-Regular.woff
2653 ms
analytics.js
40 ms
collect
16 ms
wunderkammer.ki.se 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
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
wunderkammer.ki.se 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
wunderkammer.ki.se SEO score
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wunderkammer.ki.se can be misinterpreted by Google and other search engines. Our service has detected that English 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 Wunderkammer.ki.se 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.
wunderkammer.ki.se
Open Graph description is not detected on the main page of Wunderkammer Ki. 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: