2.6 sec in total
259 ms
2.1 sec
243 ms
Visit olavthon.no now to see the best up-to-date Olav Thon content for Norway and also check out these interesting facts you probably never knew about olavthon.no
Olav Thon Gruppen er en samlebetegnelse for alle virksomheter og selskaper hvor Olav Thon direkte, eller indirekte har minst 50 % eierandel.
Visit olavthon.noWe analyzed Olavthon.no page load time and found that the first response time was 259 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 45% of websites can load faster.
olavthon.no performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value7.9 s
3/100
25%
Value5.1 s
62/100
10%
Value10 ms
100/100
30%
Value0.056
98/100
15%
Value5.4 s
71/100
10%
259 ms
516 ms
38 ms
235 ms
236 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 90% of them (43 requests) were addressed to the original Olavthon.no, 6% (3 requests) were made to Google-analytics.com and 2% (1 request) were made to Static.dudamobile.com. The less responsive or slowest element that took the longest time to load (821 ms) belongs to the original domain Olavthon.no.
Page size can be reduced by 600.2 kB (68%)
886.0 kB
285.8 kB
In fact, the total size of Olavthon.no main page is 886.0 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. 40% of websites need less resources to load. Javascripts take 696.6 kB which makes up the majority of the site volume.
Potential reduce by 15.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 2.3 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 15.6 kB or 71% of the original size.
Potential reduce by 6.1 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. Olav Thon images are well optimized though.
Potential reduce by 541.0 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 541.0 kB or 78% of the original size.
Potential reduce by 37.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. Olavthon.no needs all CSS files to be minified and compressed as it can save up to 37.6 kB or 78% of the original size.
Number of requests can be reduced by 32 (71%)
45
13
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Olav Thon. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
olavthon.no
259 ms
www.olavthon.no
516 ms
DM_redirect.js
38 ms
applesearch.css
235 ms
otg-bolig.css
236 ms
otg-story.css
236 ms
otg-content.css
356 ms
otg-global.css
239 ms
otg-grid.css
345 ms
otg-hotel.css
351 ms
otg-kjopesenter.css
351 ms
otg-naeringseiendom.css
352 ms
otg-nav.css
355 ms
otg-typo.css
461 ms
sifr.css
467 ms
jquery.lightbox-0.5.css
467 ms
jquery-ui-1.9.1.custom.min.css
478 ms
sifr.js
521 ms
sifr-config.js
365 ms
jquery-1.8.2.min.js
701 ms
jquery-ui-1.9.1.custom.min.js
821 ms
jquery-custom.js
475 ms
jquery.lightbox-0.5.pack.js
484 ms
WebResource.axd
614 ms
ScriptResource.axd
615 ms
ScriptResource.axd
491 ms
analytics.js
50 ms
ga.js
57 ms
body-background.gif
122 ms
ImageHandler.ashx
131 ms
srch_l.gif
128 ms
srch_bg.gif
129 ms
srch_r.gif
128 ms
search_go.gif
128 ms
mainmenu-background.gif
190 ms
kjopesenter-kvadrat-3.jpg
253 ms
story-frontpage-background-200.png
247 ms
white-dot.png
250 ms
gatelangs-teaser.jpg
254 ms
bolig-kvadrat-3.jpg
247 ms
standard-room-double.jpg
311 ms
story-frontpage-others.jpg
362 ms
hvit-footer.gif
367 ms
ThonEiendom_logo_2015_RGB_300x300.png
367 ms
ThonHotels_logo_2015_RGB_v2.png
366 ms
collect
22 ms
collect
78 ms
print.css
119 ms
olavthon.no 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
Links do not have a discernible name
olavthon.no 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
olavthon.no SEO score
NO
NO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Olavthon.no can be misinterpreted by Google and other search engines. Our service has detected that Norwegian is used on the page, and it matches the claimed language. Our system also found out that Olavthon.no 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.
olavthon.no
Open Graph description is not detected on the main page of Olav Thon. 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: