2.5 sec in total
202 ms
1.9 sec
412 ms
Click here to check amazing Rosetta Esa content for China. Otherwise, check out these important facts you probably never knew about rosetta.esa.int
Visit rosetta.esa.intWe analyzed Rosetta.esa.int page load time and found that the first response time was 202 ms and then it took 2.3 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.
rosetta.esa.int performance score
name
value
score
weighting
Value1.9 s
86/100
10%
Value1.9 s
97/100
25%
Value10.1 s
9/100
10%
Value26,910 ms
0/100
30%
Value0
100/100
15%
Value34.3 s
0/100
10%
202 ms
48 ms
27 ms
35 ms
106 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 48% of them (24 requests) were addressed to the original Rosetta.esa.int, 6% (3 requests) were made to Ajax.googleapis.com and 6% (3 requests) were made to S.yimg.com. The less responsive or slowest element that took the longest time to load (865 ms) relates to the external source Ajax.googleapis.com.
Page size can be reduced by 598.0 kB (50%)
1.2 MB
600.6 kB
In fact, the total size of Rosetta.esa.int main page is 1.2 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. 65% of websites need less resources to load. Images take 708.7 kB which makes up the majority of the site volume.
Potential reduce by 9.1 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 9.1 kB or 71% of the original size.
Potential reduce by 247.8 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. Obviously, Rosetta Esa needs image optimization as it can save up to 247.8 kB or 35% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 138.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 138.2 kB or 59% of the original size.
Potential reduce by 202.8 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. Rosetta.esa.int needs all CSS files to be minified and compressed as it can save up to 202.8 kB or 83% of the original size.
Number of requests can be reduced by 18 (42%)
43
25
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rosetta Esa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
rosetta.esa.int
202 ms
css
48 ms
font-awesome.min.css
27 ms
style.css
35 ms
jquery-latest.min.js
106 ms
socialize.js
102 ms
twitterFetcher_v10_min.js
103 ms
analytics.js
145 ms
sdk.js
191 ms
rosetta-at-comet.html
137 ms
videoseries
312 ms
title.png
151 ms
esa_logo.png
145 ms
Comet_on_19_March_2016_NavCam_R.jpg
276 ms
rosetta_logo.png
146 ms
nasa.png
167 ms
dlr.png
162 ms
mps.png
163 ms
cnes.png
163 ms
asi.png
150 ms
connect_youtube.png
253 ms
connect_twitter.png
248 ms
connect_flickr.png
257 ms
connect_google.png
254 ms
connect_facebook.png
252 ms
connect_livestream.png
253 ms
491973570537332736
218 ms
PLbyvawxScNbtAhH8vHAYl-pyEirPi-4Ad
169 ms
load
539 ms
load
861 ms
load
865 ms
notesesabol-webfont.ttf
202 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
158 ms
fontawesome-webfont.woff
198 ms
collect
132 ms
www-embed-player-vfl-z2BtK.css
166 ms
www-embed-player.js
236 ms
base.js
400 ms
230 ms
xd_arbiter.php
137 ms
xd_arbiter.php
286 ms
proxy.jpg
241 ms
player
266 ms
3.11.0
535 ms
3.11.0
597 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
364 ms
ad_status.js
364 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
507 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
643 ms
3.11.0
168 ms
rosetta.esa.int 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
Image elements do not have [alt] attributes
Links do not have a discernible name
rosetta.esa.int best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
rosetta.esa.int SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rosetta.esa.int 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 Rosetta.esa.int 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.
rosetta.esa.int
Open Graph description is not detected on the main page of Rosetta Esa. 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: