7.5 sec in total
341 ms
6.8 sec
374 ms
Visit sentinel.esa.int now to see the best up-to-date Sentinel Esa content for China and also check out these interesting facts you probably never knew about sentinel.esa.int
Explore Copernicus Sentinel missions, instruments, data, and technical insights. Your go-to source for efficient access and up-to-date information.
Visit sentinel.esa.intWe analyzed Sentinel.esa.int page load time and found that the first response time was 341 ms and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
sentinel.esa.int performance score
name
value
score
weighting
Value5.4 s
7/100
10%
Value15.2 s
0/100
25%
Value8.9 s
15/100
10%
Value430 ms
65/100
30%
Value0.005
100/100
15%
Value14.3 s
9/100
10%
341 ms
501 ms
1070 ms
478 ms
358 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 87% of them (55 requests) were addressed to the original Sentinel.esa.int, 3% (2 requests) were made to Google.com and 3% (2 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Sentinel.esa.int.
Page size can be reduced by 924.7 kB (46%)
2.0 MB
1.1 MB
In fact, the total size of Sentinel.esa.int main page is 2.0 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. 35% of websites need less resources to load. Javascripts take 828.6 kB which makes up the majority of the site volume.
Potential reduce by 125.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. This page needs HTML code to be minified as it can gain 41.1 kB, which is 27% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 125.2 kB or 84% of the original size.
Potential reduce by 70.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. Sentinel Esa images are well optimized though.
Potential reduce by 535.9 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 535.9 kB or 65% of the original size.
Potential reduce by 192.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. Sentinel.esa.int needs all CSS files to be minified and compressed as it can save up to 192.9 kB or 82% of the original size.
Number of requests can be reduced by 25 (42%)
59
34
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sentinel 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 12 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
sentinel.esa.int
341 ms
sentinel.esa.int
501 ms
home
1070 ms
jquery-1.9.0.min.js
478 ms
custom-javascript.min.js
358 ms
sentinels-animation-min.js
359 ms
main.css
493 ms
main.css
364 ms
main.css
364 ms
barebone.jsp
1200 ms
main.css
826 ms
brand
37 ms
addthis_widget.js
67 ms
main.js
711 ms
brand
35 ms
ga.js
155 ms
bg1.jpg
596 ms
banner.jpg
206 ms
logo.png
379 ms
ec-logo.png
380 ms
sentinel-satellites.png
482 ms
input_shadow.png
382 ms
search.png
516 ms
minimize.png
728 ms
sentinel-data-access.jpg
982 ms
S3A-mission-launch.jpg
981 ms
S3A-mission-overview.jpg
1278 ms
S3A-mission-status.jpg
1199 ms
Sentinel-2_Mission_Status
1408 ms
history.png
1084 ms
facebook.png
1345 ms
twitter.png
1345 ms
Sentinel-App
1443 ms
ERS_Envisat_multitemporal_interferometric_subsidence_Phoenix_home.jpg
1562 ms
ASAR_Oil_spill_Caspian_Sea_tm.jpg
1638 ms
image_gallery
1777 ms
Sentinel-2-bw-120.jpg
1699 ms
Sentinel-3-ocean-120.jpg
1883 ms
ground-segment-1.jpg
1799 ms
ground-segment-3.jpg
1923 ms
ground-segment-2.jpg
1993 ms
image_gallery
2149 ms
image_gallery
2205 ms
image_gallery
2247 ms
image_gallery
2350 ms
image_gallery
2510 ms
image_gallery
2451 ms
nav-button-right.png
2483 ms
nav-button-left.png
2544 ms
google_custom_search_watermark.gif
96 ms
2460 ms
__utm.gif
13 ms
li-style.png
2516 ms
li-ext.png
2622 ms
footer-bg.png
2812 ms
300lo.json
64 ms
sh.8e5f85691f9aaa082472a194.html
69 ms
246 ms
198 ms
pause.png
349 ms
prev.png
353 ms
next.png
353 ms
available_languages.jsp
353 ms
sentinel.esa.int 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
Image elements do not have [alt] attributes
Links do not have a discernible 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.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
sentinel.esa.int 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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
sentinel.esa.int 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
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 Sentinel.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 Sentinel.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.
sentinel.esa.int
Open Graph description is not detected on the main page of Sentinel 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: