4.2 sec in total
470 ms
3.6 sec
187 ms
Click here to check amazing GNSSN Iaea content for China. Otherwise, check out these important facts you probably never knew about gnssn.iaea.org
Visit gnssn.iaea.orgWe analyzed Gnssn.iaea.org page load time and found that the first response time was 470 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
gnssn.iaea.org performance score
name
value
score
weighting
Value9.4 s
0/100
10%
Value33.4 s
0/100
25%
Value26.1 s
0/100
10%
Value600 ms
49/100
30%
Value0
100/100
15%
Value27.3 s
0/100
10%
470 ms
356 ms
331 ms
539 ms
446 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that 98% of them (44 requests) were addressed to the original Gnssn.iaea.org, 2% (1 request) were made to Silverlight.dlservice.microsoft.com. The less responsive or slowest element that took the longest time to load (899 ms) belongs to the original domain Gnssn.iaea.org.
Page size can be reduced by 1.5 MB (72%)
2.1 MB
581.0 kB
In fact, the total size of Gnssn.iaea.org main page is 2.1 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. 45% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 106.9 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 106.9 kB or 77% of the original size.
Potential reduce by 12.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. GNSSN Iaea images are well optimized though.
Potential reduce by 1.0 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.0 MB or 75% of the original size.
Potential reduce by 359.0 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. Gnssn.iaea.org needs all CSS files to be minified and compressed as it can save up to 359.0 kB or 78% of the original size.
Number of requests can be reduced by 24 (59%)
41
17
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GNSSN Iaea. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
gnssn.iaea.org
470 ms
default.aspx
356 ms
init.js
331 ms
minisp.js
539 ms
ScriptResource.axd
446 ms
blank.js
532 ms
ScriptResource.axd
535 ms
ScriptResx.ashx
760 ms
sp.runtime.js
455 ms
sp.userprofiles.js
568 ms
jquery-1.11.0.min.js
898 ms
custom.css
661 ms
WebResource.axd
566 ms
bootstrap.min.js
899 ms
nucleus.min.js
607 ms
custom.js
696 ms
Common.js
696 ms
corev15.css
251 ms
pagelayouts15-ACE7C7F2.themedcss
139 ms
reset-grid.css
133 ms
nucleus.min.css
351 ms
spcommon.png
114 ms
spcommon-B35BB0A9.themedpng
137 ms
searchresultui-61174269.themedpng
138 ms
GNSSNLogo.jpg
132 ms
home_page_bg.jpg
130 ms
blank.gif
113 ms
IAEA_Standards.png
132 ms
annur_logo_news.jpg
239 ms
GNSSN_logo_news.jpg
253 ms
fgimg.png
241 ms
header-bg.jpg
236 ms
wpadder_graygrad.png
223 ms
sprite-main.png
237 ms
fontello.woff
348 ms
videoembedplayer.aspx
528 ms
videoembedplayer.aspx
528 ms
initstrings.js
338 ms
sp.init.js
338 ms
controls15.css
264 ms
ScriptResx.ashx
131 ms
mediaplayer.js
242 ms
strings.js
129 ms
core.js
336 ms
InstallSilverlight.png
45 ms
gnssn.iaea.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.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
gnssn.iaea.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
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
gnssn.iaea.org SEO score
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 Gnssn.iaea.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 Gnssn.iaea.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.
gnssn.iaea.org
Open Graph description is not detected on the main page of GNSSN Iaea. 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: