5.2 sec in total
400 ms
4.3 sec
473 ms
Click here to check amazing Sa content for Spain. Otherwise, check out these important facts you probably never knew about sa.dk
Vi indsamler, bevarer og leverer originale data og dokumenter, der kaster lys over det danske samfunds udvikling.
Visit sa.dkWe analyzed Sa.dk page load time and found that the first response time was 400 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
sa.dk performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value8.7 s
1/100
25%
Value8.4 s
18/100
10%
Value250 ms
84/100
30%
Value0.057
98/100
15%
Value10.6 s
23/100
10%
400 ms
2278 ms
236 ms
332 ms
539 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 87% of them (45 requests) were addressed to the original Sa.dk, 8% (4 requests) were made to Cdnjs.cloudflare.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Sa.dk.
Page size can be reduced by 1.4 MB (49%)
2.8 MB
1.4 MB
In fact, the total size of Sa.dk main page is 2.8 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. 60% of websites need less resources to load. CSS take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 40.0 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 40.0 kB or 82% of the original size.
Potential reduce by 21.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. Sa images are well optimized though.
Potential reduce by 297.1 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 297.1 kB or 68% of the original size.
Potential reduce by 1.0 MB
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. Sa.dk needs all CSS files to be minified and compressed as it can save up to 1.0 MB or 87% of the original size.
Number of requests can be reduced by 36 (77%)
47
11
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
sa.dk
400 ms
www.sa.dk
2278 ms
wp-emoji-release.min.js
236 ms
formreset.css
332 ms
formsmain.css
539 ms
readyclass.css
460 ms
browsers.css
351 ms
semantic.min.css
69 ms
mediaelementplayer.min.css
432 ms
select2.css
341 ms
bootstrap.css
726 ms
screen.css
772 ms
jquery.js
800 ms
jquery-migrate.min.js
532 ms
jquery.json-1.3.js
557 ms
jquery.placeholders.2.1.1.min.js
629 ms
gravityforms.js
739 ms
modernizr-dev.js
681 ms
device.min.js
737 ms
semantic.min.js
110 ms
angular.min.js
109 ms
angular-sanitize.min.js
109 ms
mediaelement-and-player.min.js
884 ms
carousel.js
876 ms
collapse.js
876 ms
transition.js
876 ms
scrollspy.js
876 ms
isotope.pkgd.min.js
876 ms
select2.min.js
929 ms
select2_locale_da.js
937 ms
phpjs.js
938 ms
_global.js
971 ms
navigation.js
974 ms
socialshare.js
977 ms
sa_old_validation.js
1025 ms
mobile.js
1025 ms
events.js
1027 ms
css
62 ms
placeholders.js
1018 ms
analytics.js
172 ms
nedloebsroer-med-kongekrone-rigsarkivet.jpg
647 ms
sa_logo.svg
149 ms
2-elever-besoeger-rigsarkivets-skoletjeneste1-1024x576.jpg
239 ms
myndighedsfoto1-1024x576.jpg
264 ms
vejledning-paa-rigsarkivets-laesesal1-1024x576.jpg
348 ms
udsnit-fra-kongeloven1-1024x576.jpg
287 ms
grundlov-561915-300x200.jpg
225 ms
soldater-aabenraa1-300x192.jpg
324 ms
SourceSansPro-Regular.woff
279 ms
SourceSansPro-Bold.woff
319 ms
icomoon.woff
319 ms
collect
25 ms
sa.dk 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
sa.dk best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
sa.dk 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
Tap targets are not sized appropriately
DA
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sa.dk can be misinterpreted by Google and other search engines. Our service has detected that Danish 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 Sa.dk main page’s claimed encoding is . 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.
sa.dk
Open Graph description is not detected on the main page of Sa. 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: