8.5 sec in total
393 ms
8 sec
151 ms
Welcome to dat.dk homepage info - get ready to check Dat best content for Denmark right away, or after learning these important things about dat.dk
Velkommen til Danish Air Transport a/s, Verden er fuld af oplevelser
Visit dat.dkWe analyzed Dat.dk page load time and found that the first response time was 393 ms and then it took 8.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
dat.dk performance score
name
value
score
weighting
Value6.7 s
2/100
10%
Value8.4 s
2/100
25%
Value6.7 s
37/100
10%
Value940 ms
30/100
30%
Value0.001
100/100
15%
Value14.5 s
9/100
10%
393 ms
2862 ms
232 ms
42 ms
344 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 80% of them (52 requests) were addressed to the original Dat.dk, 5% (3 requests) were made to Fonts.googleapis.com and 5% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Dat.dk.
Page size can be reduced by 415.8 kB (30%)
1.4 MB
976.5 kB
In fact, the total size of Dat.dk main page is 1.4 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. 35% of websites need less resources to load. Images take 869.9 kB which makes up the majority of the site volume.
Potential reduce by 33.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. 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 33.5 kB or 79% of the original size.
Potential reduce by 27.8 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. Dat images are well optimized though.
Potential reduce by 199.6 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 199.6 kB or 67% of the original size.
Potential reduce by 154.8 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. Dat.dk needs all CSS files to be minified and compressed as it can save up to 154.8 kB or 85% of the original size.
Number of requests can be reduced by 28 (47%)
59
31
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dat. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
dat.dk
393 ms
2862 ms
style.css
232 ms
jquery.min.js
42 ms
jquery.scrollTo.js
344 ms
css3-mediaqueries.js
457 ms
css
72 ms
css
88 ms
css
100 ms
dynamic_booking.nocache.js
1196 ms
default.css
681 ms
styles.css
583 ms
qts-default.css
588 ms
slider.css
588 ms
colorbox.min.css
615 ms
jquery.js
921 ms
jquery-migrate.min.js
699 ms
promoslider.js
700 ms
steal.js
1459 ms
scalefix.js
1417 ms
jquery.form.min.js
809 ms
scripts.js
810 ms
jquery.colorbox.1.5.9-min.js
927 ms
helper.min.js
926 ms
functions.js
1030 ms
jsbenchmark.min.js
267 ms
style.css
822 ms
fbds.js
301 ms
dc.js
75 ms
__utm.gif
23 ms
undefined.cache.js
122 ms
wp-emoji-release.min.js
135 ms
116 ms
logo.png
859 ms
stordlink.png
694 ms
bornholmlink.png
122 ms
dk.png
122 ms
no.png
125 ms
gb.png
123 ms
3.jpg
494 ms
2.jpg
562 ms
1.jpg
674 ms
banner_fly1.jpg
731 ms
banner_personale.jpg
938 ms
banner_fly2.jpg
1005 ms
banner_fly3.jpg
1006 ms
pilot.jpg
1243 ms
inflight_4_12_15.jpg
853 ms
bagageregler.jpg
975 ms
onlinecheckin.jpg
1092 ms
klippekort.jpg
1050 ms
gtm.js
144 ms
dev.js
1655 ms
mobile_bg.png
1101 ms
nav.png
1102 ms
shadow1.jpg
1147 ms
menu_bg_hov.png
1196 ms
menu_bg2.png
1211 ms
shadow2.jpg
1212 ms
big_bg.png
1258 ms
shadow3.jpg
1235 ms
box_bg.png
1243 ms
SEGtf14iTx9LLFPd4dg2mg.ttf
67 ms
FdRwzw_u8N6bH7J9qw5OUfesZW2xOQ-xsNqO47m55DA.ttf
99 ms
Sr4SZjJG2shlLRwOkNqcEqCWcynf_cDxXwCLxiixG1c.ttf
82 ms
dat.dk 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
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
dat.dk SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dat.dk can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Dat.dk 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.
dat.dk
Open Graph description is not detected on the main page of Dat. 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: