1.6 sec in total
66 ms
1.2 sec
259 ms
Visit protocol.un.org now to see the best up-to-date Protocol Un content for United States and also check out these interesting facts you probably never knew about protocol.un.org
About the Service | Registration Processes | Meetings Reference Materials | Notes Verbales | Workshops Please note that the Protocol and Liaison Service has launched the eMission self-service module f...
Visit protocol.un.orgWe analyzed Protocol.un.org page load time and found that the first response time was 66 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
protocol.un.org performance score
name
value
score
weighting
Value8.3 s
0/100
10%
Value11.5 s
0/100
25%
Value19.9 s
0/100
10%
Value2,280 ms
5/100
30%
Value0.051
99/100
15%
Value40.3 s
0/100
10%
66 ms
380 ms
21 ms
42 ms
45 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Protocol.un.org, 64% (54 requests) were made to Un.org and 17% (14 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (451 ms) relates to the external source Un.org.
Page size can be reduced by 104.1 kB (22%)
463.5 kB
359.4 kB
In fact, the total size of Protocol.un.org main page is 463.5 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 189.4 kB which makes up the majority of the site volume.
Potential reduce by 74.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 74.4 kB or 83% of the original size.
Potential reduce by 6.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. Protocol Un images are well optimized though.
Potential reduce by 22.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 22.2 kB or 18% of the original size.
Potential reduce by 806 B
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. Protocol.un.org has all CSS files already compressed.
Number of requests can be reduced by 46 (71%)
65
19
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Protocol Un. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
protocol.un.org
66 ms
protocol
380 ms
css_qrTJ7O3MfKrNXqwpJUHDNClm070OdqyRNr8oWAaAA-0.css
21 ms
css_ElbrpSff9s_qRInRkOoWfa5N2T13EeH2KtBYSfhzRDk.css
42 ms
css_jGoOWnosVP9GvkPf-M5TJp9SfaKCmVXYCliIPPenPhY.css
45 ms
css_MsVSFPnyvxoETOaAhf5JDtlViuHB9ZVWuWA2Tydd7jE.css
43 ms
css
80 ms
css
88 ms
css
99 ms
css
101 ms
font-awesome.min.css
69 ms
notonaskharabic.css
100 ms
droidarabickufi.css
102 ms
css_e5bBtxxIBxANnAnS25nUT5mZwRuoLWmMqMAF-3CQyKE.css
41 ms
bootstrap.min.css
72 ms
css_MR0vmJ43x2pwujbeQM-EY6-seeN4U-FNtFl6DXSfqAM.css
53 ms
css_PxsPpITToy8ZnO0bJDA1TEC6bbFpGTfSWr2ZP8LuFYo.css
48 ms
respond.min.js
70 ms
jquery.min.js
70 ms
jquery-extend-3.4.0.js
66 ms
jquery-html-prefilter-3.5.0-backport.js
76 ms
jquery.once.js
77 ms
drupal.js
84 ms
jquery.ui.core.min.js
83 ms
jquery.ui.widget.min.js
83 ms
jquery.ui.tabs.min.js
83 ms
jquery.ui.accordion.min.js
84 ms
bootstrap.js
84 ms
panopoly-images.js
82 ms
panopoly-admin.js
131 ms
panopoly-magic.js
91 ms
panopoly-accordion.js
97 ms
caption-filter.js
133 ms
lightbox.js
132 ms
jquery.imagesloaded.min.js
94 ms
googleanalytics.js
137 ms
superfish.js
135 ms
supposition.js
139 ms
sfsmallscreen.js
141 ms
jquery.hoverIntent.minified.js
143 ms
supersubs.js
145 ms
superfish.js
151 ms
bootstrap.min.js
145 ms
respond.min.js
146 ms
script.js
147 ms
panopoly-widgets.js
146 ms
panopoly-widgets-spotlight.js
147 ms
bootstrap.js
182 ms
analytics.js
306 ms
UN-logo.svg
281 ms
UN-text-EN.svg
286 ms
unani.gif
451 ms
bluebook.blue_.gif
288 ms
delegateshandbook77unga2022bookcover.jpg
289 ms
protocol0273_thumb.002.jpg
288 ms
dgacmthumb.jpg
348 ms
77ungalogosep2022.jpg
349 ms
photojeandenoue1stchiefprotocol.jpg
348 ms
logo-en-reverse.svg
346 ms
arrows-grey.png
113 ms
shadow.png
161 ms
arrows-black.png
159 ms
arrows-ffffff.png
160 ms
arrows-black.png
160 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
55 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
58 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
113 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
151 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
135 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
151 ms
ieVi2ZhZI2eCN5jzbjEETS9weq8-32meGCQYag.ttf
152 ms
ieVl2ZhZI2eCN5jzbjEETS9weq8-19K7CA.ttf
151 ms
glyphicons-halflings-regular.woff
159 ms
glyphicons-halflings-regular.woff
29 ms
fontawesome-webfont.woff
45 ms
KFOkCnqEu92Fr1Mu51xIIzc.ttf
151 ms
KFOjCnqEu92Fr1Mu51S7ACc6CsE.ttf
160 ms
KFOjCnqEu92Fr1Mu51TjASc6CsE.ttf
163 ms
KFOiCnqEu92Fr1Mu51QrEzAdKg.ttf
163 ms
KFOjCnqEu92Fr1Mu51TzBic6CsE.ttf
163 ms
KFOjCnqEu92Fr1Mu51TLBCc6CsE.ttf
160 ms
linkid.js
33 ms
collect
60 ms
collect
62 ms
protocol.un.org 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
protocol.un.org 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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
protocol.un.org 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 Protocol.un.org 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 Protocol.un.org 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.
protocol.un.org
Open Graph description is not detected on the main page of Protocol Un. 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: