3 sec in total
552 ms
2.1 sec
332 ms
Visit icann.org now to see the best up-to-date ICANN content for United States and also check out these interesting facts you probably never knew about icann.org
ICANN’s mission is to help ensure a stable, secure, and unified global Internet.
Visit icann.orgWe analyzed Icann.org page load time and found that the first response time was 552 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
icann.org performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value12.5 s
0/100
25%
Value4.6 s
71/100
10%
Value5,180 ms
0/100
30%
Value0.24
52/100
15%
Value12.4 s
14/100
10%
552 ms
328 ms
747 ms
212 ms
402 ms
Our browser made a total of 30 requests to load all elements on the main page. We found that 73% of them (22 requests) were addressed to the original Icann.org, 10% (3 requests) were made to Widget.uservoice.com and 7% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (747 ms) belongs to the original domain Icann.org.
Page size can be reduced by 2.6 MB (61%)
4.3 MB
1.7 MB
In fact, the total size of Icann.org main page is 4.3 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. 15% of websites need less resources to load. Javascripts take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 29.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. 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 29.2 kB or 71% of the original size.
Potential reduce by 70.3 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. ICANN images are well optimized though.
Potential reduce by 1.6 MB
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 1.6 MB or 68% of the original size.
Potential reduce by 960.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. Icann.org needs all CSS files to be minified and compressed as it can save up to 960.4 kB or 79% of the original size.
Number of requests can be reduced by 6 (24%)
25
19
The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ICANN. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
www.icann.org
552 ms
application-54619be9d02f19583404adcef43d3e77.css
328 ms
application-5a608b6a067ad45acc65ad489e798963.js
747 ms
uservoice-2dcfa02f2685efa541080d64daf81a94.js
212 ms
glossary_terms.js
402 ms
ga.js
40 ms
icann_logo-2b08a348dacd091333bdba6d5c589675.png
70 ms
hero1_Luna_Feature_MEAC_Report-01.png
338 ms
hero1_how_are_gtld_policies_implemented_en_microcontent_icannorg.png
138 ms
hero1_ICANN55_Marrakech_Feature.jpg
220 ms
hero1_host-a-remote-hub.png
209 ms
thumb_ICANN4Biz_Bottom_Feature.png
417 ms
thumb_220x125.jpg
289 ms
thumb_ICANN55_Logo_Bottom_Feature_Sized-01.jpg
278 ms
thumb_fellows.jpg
288 ms
myicann-logo-big-84036ee8d733df3ae3f12e049b948107.png
345 ms
myicann-signup-df41faa4329e85b5a04f30e09f60f159.jpg
724 ms
home_groups-31f505810548b4c69f1f5a1a8bb7e0d5.png
625 ms
__utm.gif
13 ms
Vs0f8Q6YW6msp6vUKhtX0A.js
108 ms
ccwg-accountability_delivers_final_report.jpg
200 ms
fontawesome-webfont-9b04cd5f549e3341232616cfa419f0df.woff
138 ms
Lato-Regular-5ae30e034de901aa11259c263a8421b0.woff
341 ms
Lato-Light-5153b25f7097ef9cfac8270b204885cd.woff
323 ms
Lato-Bold-18d7205a7f9f4c16ea189f9d69725179.woff
401 ms
feedback-tab.png
3 ms
tab-horizontal-dark-3efc2033e3bb06b1eefaa3431d3d47d8.png
36 ms
nr-852.min.js
40 ms
track.js
160 ms
90fa9cd0bb
121 ms
icann.org 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.
icann.org 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
icann.org 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
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 Icann.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 Icann.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.
icann.org
Open Graph description is not detected on the main page of ICANN. 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: