3.6 sec in total
879 ms
2.6 sec
118 ms
Welcome to igm.no homepage info - get ready to check IGM best content for Norway right away, or after learning these important things about igm.no
IGM er et kompetansesenter innen digital kommunikasjon. Kurs og høgskole studier i Adobe programmer, markedsføring, interaksjonsdesign, video, web, design og design thinking.
Visit igm.noWe analyzed Igm.no page load time and found that the first response time was 879 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
igm.no performance score
name
value
score
weighting
Value12.5 s
0/100
10%
Value20.8 s
0/100
25%
Value23.2 s
0/100
10%
Value18,480 ms
0/100
30%
Value0.073
96/100
15%
Value41.1 s
0/100
10%
879 ms
346 ms
594 ms
240 ms
243 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 65% of them (35 requests) were addressed to the original Igm.no, 9% (5 requests) were made to Btn.createsend1.com and 4% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Igm.no.
Page size can be reduced by 1.1 MB (66%)
1.7 MB
578.3 kB
In fact, the total size of Igm.no main page is 1.7 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. 50% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 37.4 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 37.4 kB or 77% of the original size.
Potential reduce by 2.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. IGM images are well optimized though.
Potential reduce by 741.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 741.0 kB or 70% of the original size.
Potential reduce by 330.7 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. Igm.no needs all CSS files to be minified and compressed as it can save up to 330.7 kB or 84% of the original size.
Number of requests can be reduced by 39 (76%)
51
12
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IGM. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
igm.no
879 ms
wp-emoji-release.min.js
346 ms
formidablepro.css
594 ms
front.css
240 ms
crellyslider.css
243 ms
main.css
365 ms
jquery-ui.min.css
347 ms
theme.css
476 ms
font-awesome.min.css
5 ms
page-builder-styles.css
363 ms
crelly-slider-styles.css
459 ms
style.css
466 ms
jquery.mmenu.css
604 ms
jquery.js
725 ms
jquery-migrate.min.js
574 ms
core.min.js
585 ms
jquery.crellyslider.min.js
712 ms
widget.min.js
689 ms
position.min.js
706 ms
menu.min.js
709 ms
selectmenu.min.js
726 ms
main.js
1147 ms
webfont.js
7 ms
navigation.js
607 ms
skip-link-focus-fix.js
609 ms
comment-reply.min.js
611 ms
js
21 ms
effect.min.js
625 ms
scripts.js
1026 ms
retina.js
728 ms
wp-embed.min.js
729 ms
style.css
843 ms
analytics.js
36 ms
fbevents.js
180 ms
hotjar-163258.js
179 ms
igm-logo-60x60.png
172 ms
utsikt_1400x393-1400x393.jpg
388 ms
fjell_1400x393-1400x393.jpg
620 ms
veien_1400x393-1400x393.jpg
376 ms
makingdesign-logo16-160x160.png
173 ms
video-160x160.png
172 ms
sb.min.js
134 ms
fontawesome-webfont.woff
132 ms
iframe_api
142 ms
collect
45 ms
collect
102 ms
subscribe
10 ms
modules-d7af38b5aa5145ab899bd263964bf1f5.js
73 ms
34 ms
www-widgetapi.js
34 ms
subscribe-button.min.css
17 ms
subscribe-button-modal.min.css
22 ms
subscribebutton.noncc.min.js
31 ms
ga-audiences
26 ms
igm.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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
igm.no 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
igm.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
NO
NB
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Igm.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 Igm.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.
igm.no
Open Graph data is detected on the main page of IGM. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: