3.2 sec in total
387 ms
2.5 sec
290 ms
Visit iom.no now to see the best up-to-date IOM content and also check out these interesting facts you probably never knew about iom.no
Visit iom.noWe analyzed Iom.no page load time and found that the first response time was 387 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
iom.no performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value13.7 s
0/100
25%
Value9.1 s
14/100
10%
Value990 ms
27/100
30%
Value0.487
17/100
15%
Value13.6 s
11/100
10%
387 ms
622 ms
110 ms
59 ms
141 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Iom.no, 50% (50 requests) were made to Norway.iom.int and 40% (40 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Norway.iom.int.
Page size can be reduced by 427.2 kB (29%)
1.4 MB
1.0 MB
In fact, the total size of Iom.no main page is 1.4 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. Images take 821.6 kB which makes up the majority of the site volume.
Potential reduce by 108.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. This page needs HTML code to be minified as it can gain 17.8 kB, which is 13% 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 108.8 kB or 82% of the original size.
Potential reduce by 96.8 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. Obviously, IOM needs image optimization as it can save up to 96.8 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 3.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. This website has mostly compressed JavaScripts.
Potential reduce by 218.4 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. Iom.no needs all CSS files to be minified and compressed as it can save up to 218.4 kB or 63% of the original size.
Number of requests can be reduced by 14 (25%)
55
41
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IOM. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
iom.no
387 ms
norway.iom.int
622 ms
google_tag.script.js
110 ms
js
59 ms
css_8BvBZFdqngQfuaOTuIdoWrjwe15q-WD-mwgtfH3Ll4I.css
141 ms
css
41 ms
css2
70 ms
css
69 ms
css_e2HoEy-LB1D4iWziprgaOfWLyHCu3N4GJnfpDMoBANw.css
175 ms
css_UIe0lYlJOyH5Hs3czAVjQItKhx0ikmCIq8JxU1sE1TM.css
112 ms
all.min.js
43 ms
v4-shims.min.js
54 ms
js_wnjSuBCw27kccOOG1a5KExIZLgESCuHao_jrN9iwJ6Y.js
46 ms
accordion.frontend.min.js
78 ms
js_RPWKK1C0fxf1RHwmgBKuYPbk5bDF4DSC7jp7vC6rTrY.js
68 ms
2e714205-afe2-4a54-9ea5-70e331406c96.js
631 ms
gtm.js
174 ms
logonorway.svg
35 ms
ico-arrow.png
568 ms
IOM-logo-standin_0.jpg
438 ms
ico-arrow-white.png
516 ms
SDG_Wheel_Transparent_WEB.png
412 ms
icons-sprite-sheet.svg
58 ms
sdg.png
88 ms
e_web_01_0.png
92 ms
SDG_1_No%20Poverty.jpg
159 ms
e-web-goal-02.png
164 ms
SDG_2_Zero%20Hunger.jpg
168 ms
e_web_03.png
169 ms
SDG_3_Good%20Health%20and%20Well-being.jpg
169 ms
e_web_04.png
169 ms
SDG_4_Quality%20Education_0.jpg
170 ms
e_print_06.jpg
170 ms
SDG_6_Clean%20Water%20and%20Sanitation.jpg
170 ms
sdg-7.svg
233 ms
SDG_7_Affordable%20and%20Clean%20Energy.jpg
236 ms
e_web_08.png
235 ms
SDG_8_Decent%20Work%20and%20Economic%20Growth.jpg
235 ms
e_web_05.png
236 ms
SDG_5_Gender%20Equality.jpg
237 ms
e_sdg-goals_icons-individual-rgb-09.png
237 ms
SDG_9_Infrastructure.jpg
237 ms
e_web_10.png
237 ms
SDG_10_Reduced%20Inequalities%20%281%29.jpg
245 ms
e_web_11.png
245 ms
SDG_11_Sustainable%20Communities.jpg
258 ms
sdg-12%5B1%5D.svg
390 ms
SDG_12_Responsible%20Consumption.jpg
269 ms
e_web_13.png
288 ms
SDG_13_Climate%20Action%20%281%29.jpg
304 ms
sdg-14%5B1%5D.svg
319 ms
SDG_14_Life%20Below%20Water%20%281%29.jpg
335 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff
63 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQGxA.woff
77 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4vaVQGxA.woff
80 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x5OaVQGxA.woff
78 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x5caVQGxA.woff
80 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4iaVQGxA.woff
77 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4jaVQGxA.woff
78 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4saVQGxA.woff
79 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4kaVQGxA.woff
82 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4taVQGxA.woff
81 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff
83 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQGxA.woff
81 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4vaVQGxA.woff
80 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x5OaVQGxA.woff
82 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x5caVQGxA.woff
83 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4iaVQGxA.woff
85 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4jaVQGxA.woff
85 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4saVQGxA.woff
85 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4kaVQGxA.woff
84 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4taVQGxA.woff
84 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff
85 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQGxA.woff
150 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4vaVQGxA.woff
147 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B5OaVQGxA.woff
150 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B5caVQGxA.woff
149 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4iaVQGxA.woff
149 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4jaVQGxA.woff
150 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4saVQGxA.woff
150 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4kaVQGxA.woff
152 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4taVQGxA.woff
152 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff
150 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQGxA.woff
151 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4vaVQGxA.woff
152 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B5OaVQGxA.woff
154 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B5caVQGxA.woff
155 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4iaVQGxA.woff
155 ms
fontawesome-webfont.woff
1071 ms
sdg-15%5B1%5D.svg
354 ms
SDG_15_Life%20on%20Land.jpg
846 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4jaVQGxA.woff
83 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4saVQGxA.woff
82 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4kaVQGxA.woff
81 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4taVQGxA.woff
81 ms
e_web_16.png
342 ms
SDG_16_Peace%20Justice.jpg
357 ms
e_web_17.png
296 ms
SDG_17_Partnership.jpg
341 ms
ppms.js
466 ms
ppms.php
102 ms
iom.no 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.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
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
iom.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
Page has valid source maps
iom.no 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 uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iom.no can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Iom.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.
iom.no
Open Graph description is not detected on the main page of IOM. 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: