7.1 sec in total
1 sec
4 sec
2.1 sec
Click here to check amazing FAOD content for Denmark. Otherwise, check out these important facts you probably never knew about faod.dk
Information om ansættelsesforhold, lønninger, overenskomster mv. for arkitekter og designere. Mange kontante fordele ved at være medlem.
Visit faod.dkWe analyzed Faod.dk page load time and found that the first response time was 1 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
faod.dk performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value6.1 s
12/100
25%
Value6.3 s
42/100
10%
Value1,050 ms
25/100
30%
Value0.044
99/100
15%
Value6.3 s
61/100
10%
1020 ms
583 ms
1084 ms
339 ms
340 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 58% of them (56 requests) were addressed to the original Faod.dk, 14% (13 requests) were made to Cdn1.siteworks.dk and 13% (12 requests) were made to A.disquscdn.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Faod.dk.
Page size can be reduced by 1.3 MB (26%)
5.0 MB
3.7 MB
In fact, the total size of Faod.dk main page is 5.0 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. 80% 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. Images take 3.2 MB which makes up the majority of the site volume.
Potential reduce by 102.6 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 14.5 kB, which is 11% 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 102.6 kB or 80% of the original size.
Potential reduce by 13.2 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. FAOD images are well optimized though.
Potential reduce by 917.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 917.2 kB or 69% of the original size.
Potential reduce by 253.1 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. Faod.dk needs all CSS files to be minified and compressed as it can save up to 253.1 kB or 85% of the original size.
Number of requests can be reduced by 30 (34%)
89
59
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FAOD. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.faod.dk
1020 ms
styles.asp
583 ms
top_script.asp
1084 ms
universal_script_js_min.js
339 ms
universal_script_css_min_less.css
340 ms
flexslider.css
347 ms
jquery.fancybox.css
349 ms
cookiecuttr.min.css
347 ms
font-awesome.min.css
462 ms
jquery.flexslider-min.js
347 ms
jquery.fancybox.pack.js
462 ms
jquery.nicescroll.min.js
569 ms
jquery.cookie.min.js
343 ms
jquery.cookiecuttr.min.js
344 ms
hyphenator.js
794 ms
packery.pkgd.min.js
569 ms
imagesloaded.pkgd.min.js
462 ms
jquery.inlinestyler.src.js
124 ms
addthis_widget.js
13 ms
dc.js
56 ms
whitenoise-460x460.png
493 ms
faod-logo.png
268 ms
favicon.png
252 ms
nyhed-25167-1-103.jpg
254 ms
nyhed-25165-1-4438.jpg
255 ms
nyhed-25176-1-26088.jpg
452 ms
nyhed-25164-1-25340.jpg
371 ms
nyhed-25145-1-6317.jpg
442 ms
nyhed-25172-1-13506.jpg
573 ms
nyhed-25170-1-11608.jpg
702 ms
nyhed-25171-1-28027.jpg
456 ms
nyhed-25161-1-29564.jpg
565 ms
nyhed-25163-1-4465.jpg
830 ms
nyhed-25160-1-19508.jpg
700 ms
nyhed-25169-1-21331.jpg
569 ms
nyhed-25157-1-19841.jpg
830 ms
nyhed-25168-1-26333.jpg
702 ms
nyhed-25142-1-16113.jpg
937 ms
nyhed-25166-1-16989.jpg
1028 ms
nyhed-25136-1-25140.jpg
929 ms
nyhed-25158-1-21425.jpg
829 ms
nyhed-25146-1-17544.jpg
929 ms
nyhed-25150-1-13405.jpg
928 ms
nyhed-25144-1-9764.jpg
1040 ms
nyhed-25152-1-15295.jpg
1164 ms
nyhed-25147-1-2369.jpg
1164 ms
nyhed-25134-1-6505.jpg
1040 ms
nyhed-25143-1-3225.jpg
1278 ms
nyhed-25133-1-625.jpg
1252 ms
nyhed-25140-1-8030.jpg
1164 ms
nyhed-25141-1-2621.jpg
1163 ms
nyhed-25135-1-4181.jpg
1278 ms
nyhed-25130-1-8294.jpg
1277 ms
nyhed-25131-1-12757.jpg
1276 ms
nyhed-25132-1-8313.jpg
1274 ms
kalender-10537-1-2649.jpg
1399 ms
kalender-10420-1-27738.jpg
1402 ms
embed.js
297 ms
kalender-10589-1-27827.jpg
1261 ms
kalender-10600-1-17156.jpg
1155 ms
kalender-10617-1-26169.jpg
1153 ms
Effra-Regular.woff
1153 ms
fontawesome-webfont.woff
340 ms
__utm.gif
79 ms
164 ms
Effra-Bold.woff
1085 ms
Effra-Heavy.woff
1171 ms
glyphicons-halflings-regular.woff
1075 ms
kalender-10612-1-837.jpg
1050 ms
lounge.load.85ba7336856f5be9db0e468752c2dad5.js
16 ms
kalender-10620-1-14981.jpg
964 ms
kalender-10622-1-8807.jpg
1027 ms
kalender-10536-1-19556.jpg
1065 ms
lounge.f668c82e65f78693a6a62a5c7d3e54b8.css
31 ms
config.js
25 ms
common.bundle.9054241a18d1ec2777a52f6dcc96dfb6.js
58 ms
da.js
36 ms
lounge.bundle.b75817c8b9cd25c332ba61b6a5c58c0d.js
56 ms
kalender-10481-1-28678.jpg
938 ms
1x1.gif
938 ms
557-446558-8045.png
933 ms
ga.js
73 ms
loader.5cc23909da9c4a9874500d7a85c4125f.gif
21 ms
discovery.449c10a436c997c3eee5afd5021da3a2.css
48 ms
155 ms
sprite.06bad3144429d24544aa8b00ffd77160.png
40 ms
icons.dcb5405f8abc9a80e5628869f735eaf0.woff
40 ms
discovery.bundle.188b7afdc0cb75bb665bca3eb0ce9ba7.js
42 ms
alfie.f51946af45e0b561c60f768335c9eb79.js
40 ms
noavatar92.4549c5353ccf103d32a8b81a856576ed.png
38 ms
__utm.gif
20 ms
ping
163 ms
listRelated.json
248 ms
event.gif
96 ms
listTopPost.json
210 ms
da.js
42 ms
faod.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
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.
faod.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
Missing source maps for large first-party JavaScript
faod.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
N/A
DA
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Faod.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 Danish. Our system also found out that Faod.dk main page’s claimed encoding is iso-8859-1. 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.
faod.dk
Open Graph description is not detected on the main page of FAOD. 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: