4.9 sec in total
614 ms
3.6 sec
708 ms
Visit unog.ch now to see the best up-to-date Unog content for Switzerland and also check out these interesting facts you probably never knew about unog.ch
Visit unog.chWe analyzed Unog.ch page load time and found that the first response time was 614 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
unog.ch performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value8.2 s
2/100
25%
Value10.3 s
8/100
10%
Value350 ms
73/100
30%
Value0.15
76/100
15%
Value18.2 s
3/100
10%
614 ms
108 ms
386 ms
738 ms
293 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Unog.ch, 9% (4 requests) were made to Googletagmanager.com and 4% (2 requests) were made to Webstats.unog.ch. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Ungeneva.org.
Page size can be reduced by 497.9 kB (13%)
3.9 MB
3.4 MB
In fact, the total size of Unog.ch main page is 3.9 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. 70% of websites need less resources to load. Images take 3.4 MB which makes up the majority of the site volume.
Potential reduce by 46.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 7.9 kB, which is 14% 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 46.2 kB or 79% of the original size.
Potential reduce by 268.7 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. Unog images are well optimized though.
Potential reduce by 176.4 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 176.4 kB or 52% of the original size.
Potential reduce by 6.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. Unog.ch needs all CSS files to be minified and compressed as it can save up to 6.6 kB or 11% of the original size.
Number of requests can be reduced by 9 (24%)
37
28
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Unog. 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 as a result speed up the page load time.
614 ms
en
108 ms
gtag.js
386 ms
matomo.js
738 ms
google_tag.script.js
293 ms
google_tag.script.js
293 ms
css_imPYJUasZt0PoijrutVUaYg_ICPqjFqwC5eO-A8avJI.css
423 ms
css_8TUf5opmarfDR1B_2wQwOwn6iosGLo3c_h397Ol3qag.css
541 ms
css_0sOfnqfyTH0njIbt4DkpvVZCq3vCgHIycuz_WWR8Mxs.css
314 ms
js_JRwl2e2WQajuU2BGvm6a6k7923MMWBWen0wo7K-NajI.js
630 ms
logo.svg
532 ms
PALAIS_HERO%20BANNER_Night.png
1972 ms
dma3mP1sUPL30N1T-A_j2MggWHBBF1owyfdDrwfi9R8.jpg
479 ms
QMvbi0VxzXpNG1MF6lnlXBM4TlfhHI4WzKinqEbSWUo.jpg
835 ms
tHYcT1P_RSPNYOeoxW1-6eqLvWdtqnVTyWq5VrUssMM.jpg
668 ms
quaTMm7LuMf6CojF20Ne3MIEJmNrMI4-xbv5osob89c.jpg
774 ms
9NNNt7nhls1DVpaSFj0W0skJ-WmnSQxiJZRzCrouGUk.jpg
937 ms
CRC.jpg
925 ms
Background%20%2810%29.png
1149 ms
LnIe4mlp9c17Y16KYgMNJTihZQb9LXB9-JPN4loIZrA.jpg
960 ms
Publication.svg
939 ms
History.svg
961 ms
Intern.svg
1041 ms
Map.svg
1044 ms
ypp.svg
1056 ms
Palais-v2.svg
1058 ms
logo-en-reverse.svg
1152 ms
js
70 ms
analytics.js
18 ms
collect
58 ms
fa-brands-400.ttf
787 ms
collect
119 ms
arrow_practical-info.svg
594 ms
search_icon.png
595 ms
arrow_practical-info-white.svg
684 ms
gtm.js
42 ms
gtm.js
94 ms
roboto-bold-webfont.woff
628 ms
roboto-medium-webfont.woff
613 ms
roboto-regular-webfont.woff
627 ms
roboto-light-webfont.woff
704 ms
RobotoCondensed-Bold.woff
717 ms
RobotoCondensed-Regular.woff
740 ms
RobotoCondensed-Light.woff
741 ms
ga-audiences
52 ms
matomo.php
372 ms
js
55 ms
unog.ch accessibility score
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
[role]s are not contained by their required parent element
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
unog.ch 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
unog.ch 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Unog.ch 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 Unog.ch 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.
unog.ch
Open Graph description is not detected on the main page of Unog. 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: