13.7 sec in total
281 ms
13 sec
370 ms
Visit godthaab.no now to see the best up-to-date Godthaab content and also check out these interesting facts you probably never knew about godthaab.no
Gjenvinn funksjonsevne som er tapt på grunn av sykdom eller skade gjennom trening og behandling! Godthaab tar imot pasienter som kommer direkte fra sykehus, og hjemmeboende som har søkt om rehabiliter...
Visit godthaab.noWe analyzed Godthaab.no page load time and found that the first response time was 281 ms and then it took 13.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
godthaab.no performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value4.7 s
32/100
25%
Value6.6 s
37/100
10%
Value810 ms
36/100
30%
Value0.729
6/100
15%
Value10.7 s
22/100
10%
281 ms
83 ms
156 ms
164 ms
25 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 30% of them (31 requests) were addressed to the original Godthaab.no, 13% (13 requests) were made to Wpstatic.idium.no and 13% (13 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (11.7 sec) relates to the external source Maps.gstatic.com.
Page size can be reduced by 1.1 MB (51%)
2.2 MB
1.1 MB
In fact, the total size of Godthaab.no main page is 2.2 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. 65% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 28.2 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 4.1 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 28.2 kB or 78% of the original size.
Potential reduce by 15.6 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. Godthaab images are well optimized though.
Potential reduce by 909.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 909.1 kB or 69% of the original size.
Potential reduce by 155.0 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. Godthaab.no needs all CSS files to be minified and compressed as it can save up to 155.0 kB or 75% of the original size.
Number of requests can be reduced by 61 (66%)
92
31
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Godthaab. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
godthaab.no
281 ms
wp-emoji-release.min.js
83 ms
breadcrumbs.css
156 ms
font-awesome.min.css
164 ms
css
25 ms
style.css
243 ms
magnific-popup.css
163 ms
dashicons.min.css
255 ms
jquery-ui-dialog.min.css
170 ms
footerLinkPopup.css
229 ms
jquery.js
324 ms
jquery-migrate.min.js
250 ms
jquery.cycle2.min.js
252 ms
jquery.cycle2.swipe.min.js
301 ms
jRespond.min.js
319 ms
jquery.magnific-popup.min.js
343 ms
magnific-bind.js
344 ms
buttons.js
11 ms
hoverIntent.min.js
363 ms
app.js
410 ms
jquery.cookie.js
415 ms
accessibility.js
415 ms
core.min.js
415 ms
widget.min.js
414 ms
mouse.min.js
424 ms
resizable.min.js
458 ms
draggable.min.js
500 ms
button.min.js
497 ms
position.min.js
498 ms
dialog.min.js
498 ms
footerLinkPopup.js
509 ms
ga.js
20 ms
godthaab-logo.jpg
750 ms
idium-logo.png
256 ms
DM39578-Edit-2-1280x500.jpg
948 ms
MG_07561-1280x500.jpg
748 ms
DM39671-Edit-2-1280x500.jpg
607 ms
MG_0699-Edit-2-412x275.jpg
532 ms
MG_0783-412x275.jpg
749 ms
DM39504-Edit-2-412x275.jpg
764 ms
DM39759-Edit-2-412x275.jpg
672 ms
DM39434-Edit-2-412x275.jpg
751 ms
DM39738-Edit-2-412x275.jpg
826 ms
Mestring-412x287.jpg
829 ms
Your-body-412x287.jpg
830 ms
DM39704-Edit-2-412x287.jpg
904 ms
gtm.js
71 ms
embed
244 ms
__utm.gif
17 ms
gk5FxslNkTTHtojXrkp-xGtXp_56cyzG87rk01y3A5nr7w4p9aSvGirXi6XmeXNA.ttf
9 ms
gk5FxslNkTTHtojXrkp-xEb5azEPpng8GbF4Y4e4kqzr7w4p9aSvGirXi6XmeXNA.ttf
12 ms
fontawesome-webfont.woff
246 ms
analytics.js
3 ms
collect
3 ms
collect
149 ms
getAllAppDefault.esi
261 ms
js
76 ms
init_embed.js
41 ms
common.js
54 ms
map.js
54 ms
google4.png
19 ms
overlay.js
17 ms
util.js
109 ms
onion.js
79 ms
search_impl.js
101 ms
StaticMapService.GetMapImage
134 ms
stats.js
91 ms
ViewportInfoService.GetViewportInfo
59 ms
transparent.png
52 ms
kh
119 ms
getSegment.php
42 ms
checkOAuth.esi
112 ms
t.dhj
44 ms
controls.js
37 ms
vt
101 ms
vt
86 ms
vt
109 ms
vt
83 ms
vt
89 ms
t.dhj
55 ms
css
83 ms
mapcnt6.png
11727 ms
cm
27 ms
s-3271.xgi
13 ms
hbpix
39 ms
4 ms
xrefid.xgi
5 ms
15 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
17 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
20 ms
Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf
25 ms
d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf
23 ms
AuthenticationService.Authenticate
21 ms
pixel
19 ms
pixel
16 ms
2981
27 ms
__utm.gif
7 ms
index.2d85e55d89f85ae69e4f2ca5ab9438b7.html
76 ms
buttons.ab966a004186897711de4a5ed256c924.css
9 ms
stcommon.2b05accc08f1ee42fe1983647ab923ea.js
4 ms
st.1188278743c14064d5e8ae56c8ada29c.js
8 ms
QuotaService.RecordEvent
13 ms
godthaab.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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
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.
godthaab.no best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
godthaab.no 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
NO
NB
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Godthaab.no can be misinterpreted by Google and other search engines. Our service has detected that Norwegian is used on the page, and it does not match the claimed language. Our system also found out that Godthaab.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.
godthaab.no
Open Graph description is not detected on the main page of Godthaab. 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: