3.2 sec in total
302 ms
2.4 sec
455 ms
Click here to check amazing IAU content for United States. Otherwise, check out these important facts you probably never knew about iau.org
Visit iau.orgWe analyzed Iau.org page load time and found that the first response time was 302 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
iau.org performance score
name
value
score
weighting
Value2.6 s
62/100
10%
Value9.2 s
1/100
25%
Value5.5 s
54/100
10%
Value900 ms
32/100
30%
Value0.001
100/100
15%
Value9.3 s
31/100
10%
302 ms
811 ms
201 ms
47 ms
46 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 77% of them (41 requests) were addressed to the original Iau.org, 6% (3 requests) were made to Platform.twitter.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (984 ms) belongs to the original domain Iau.org.
Page size can be reduced by 260.9 kB (20%)
1.3 MB
1.1 MB
In fact, the total size of Iau.org main page is 1.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. 50% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 60.0 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 60.0 kB or 83% of the original size.
Potential reduce by 40.5 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. IAU images are well optimized though.
Potential reduce by 32.5 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 32.5 kB or 60% of the original size.
Potential reduce by 127.9 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. Iau.org needs all CSS files to be minified and compressed as it can save up to 127.9 kB or 83% of the original size.
Number of requests can be reduced by 6 (12%)
50
44
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IAU. 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.
iau.org
302 ms
www.iau.org
811 ms
base.a310ec1db135.css
201 ms
jsapi
47 ms
feed2js.php
46 ms
base.cef047eec3d9.js
608 ms
widgets.js
92 ms
IAU_backimage.bdd6a2035456.jpg
690 ms
sprites.6b63c57dc76d.png
198 ms
iau1601a.jpg
333 ms
iau1514a.jpg
460 ms
iau_wb.jpg
296 ms
iau1513a.jpg
529 ms
iau1512a.jpg
509 ms
iau1601a.jpg
460 ms
iau1514a.jpg
484 ms
iau1513a.jpg
508 ms
iau1512a.jpg
531 ms
isya_2015.jpg
575 ms
ann16010a.jpg
592 ms
iauoadlogo.jpg
591 ms
ann16008a.jpg
626 ms
naming_exoplanets2.jpg
629 ms
buyingstars3.jpg
674 ms
why_is_astronomy_important2.jpg
689 ms
pluto2.jpg
690 ms
citizen-science-projects.jpg
821 ms
naming2.jpg
727 ms
image_archive.jpg
772 ms
video_archive.jpg
784 ms
ad_iauga.jpg
787 ms
ad_enewsletter.jpg
789 ms
ad_enewsletter_subs.jpg
825 ms
ad_heritage.jpg
870 ms
ad_capjournal18.jpg
882 ms
ad_directory_world.jpg
886 ms
ad_oad.jpg
984 ms
ad_oao.jpg
919 ms
ad_outreachnl.jpg
924 ms
ad_astroedu.jpg
969 ms
ad_strategicplan.jpg
981 ms
ad_pttu_iau_org.jpg
984 ms
sdk.js
35 ms
analytics.js
22 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
142 ms
extlink-gray.png
566 ms
glyphicons-halflings-regular.fa2772327f55.woff
586 ms
collect
28 ms
63 ms
xd_arbiter.php
50 ms
xd_arbiter.php
74 ms
tweet_button.6a78875565a912489e9aef879c881358.en.html
43 ms
jot
94 ms
iau.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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
iau.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
Issues were logged in the Issues panel in Chrome Devtools
iau.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
Image elements do not have [alt] attributes
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iau.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Iau.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.
iau.org
Open Graph description is not detected on the main page of IAU. 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: