2.7 sec in total
418 ms
2 sec
234 ms
Welcome to henninglarsen.com homepage info - get ready to check Henning Larsen best content for Denmark right away, or after learning these important things about henninglarsen.com
Working across architecture, landscape, and urbanism, we co-create and innovate – cultivating desirable futures through our designs.
Visit henninglarsen.comWe analyzed Henninglarsen.com page load time and found that the first response time was 418 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
henninglarsen.com performance score
name
value
score
weighting
Value2.8 s
56/100
10%
Value4.0 s
48/100
25%
Value4.7 s
69/100
10%
Value70 ms
99/100
30%
Value0
100/100
15%
Value4.2 s
85/100
10%
418 ms
450 ms
258 ms
257 ms
257 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 96% of them (45 requests) were addressed to the original Henninglarsen.com, 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (681 ms) belongs to the original domain Henninglarsen.com.
Page size can be reduced by 260.7 kB (48%)
538.7 kB
278.0 kB
In fact, the total size of Henninglarsen.com main page is 538.7 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. 20% of websites need less resources to load. Javascripts take 282.4 kB which makes up the majority of the site volume.
Potential reduce by 14.8 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 14.8 kB or 70% of the original size.
Potential reduce by 2.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. Henning Larsen images are well optimized though.
Potential reduce by 195.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 195.2 kB or 69% of the original size.
Potential reduce by 48.6 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. Henninglarsen.com needs all CSS files to be minified and compressed as it can save up to 48.6 kB or 85% of the original size.
Number of requests can be reduced by 36 (80%)
45
9
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Henning Larsen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
henninglarsen.com
418 ms
frontpage.aspx
450 ms
layout.css
258 ms
screenuk.css
257 ms
fpscreen.css
257 ms
fpscreenuk.css
251 ms
flavor4.css
250 ms
flavor4uk.css
360 ms
sifr.css
358 ms
jquery-1.3.2.min.js
574 ms
jquery.metadata.min.js
356 ms
jquery.swapimage.min.js
257 ms
jquery.equalheights.js
324 ms
jquerypngfix.js
359 ms
jquery-ui-1.7.2.custom.min.20090612.js
574 ms
jquery.checkbox.min.js
360 ms
jquery.nyroModal-1.5.0.min.js
467 ms
nyroModal.css
430 ms
thickbox.3.1.js
462 ms
sifr.js
576 ms
main.js
537 ms
sifr-config.js
566 ms
hla.js
575 ms
screen.css
432 ms
bg_gradient.gif
113 ms
icon_tooltip.gif
108 ms
logo.png
113 ms
menu1.png
115 ms
menu2_architecture_neg_opacity.png
113 ms
menu3_people_neg_opacity.png
214 ms
menu4_about_neg_opacity.png
217 ms
menu5.png
218 ms
menu6.png
219 ms
ImageGen.ashx
439 ms
icon_arrowOrange.gif
226 ms
icon_arrowUpOrange.gif
320 ms
icon_arrowSmallOrange.gif
326 ms
icon_hideBlue.png
316 ms
icon_folderMinusOrange.gif
316 ms
icon_newsletterBlue.png
322 ms
icon_searchBlue.png
413 ms
icon_gallery_forwardOrange.gif
419 ms
ga.js
31 ms
__utm.gif
11 ms
loadingAnimation.gif
360 ms
Forum_Medicum_FP_BG_BLURRED_2.jpg
681 ms
icon_plusOrange.gif
367 ms
henninglarsen.com 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.
henninglarsen.com 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
General
Impact
Issue
Detected JavaScript libraries
henninglarsen.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 doesn't use legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Henninglarsen.com 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 Henninglarsen.com 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.
henninglarsen.com
Open Graph description is not detected on the main page of Henning Larsen. 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: