13.2 sec in total
2.8 sec
9 sec
1.4 sec
Click here to check amazing GDACS content for United States. Otherwise, check out these important facts you probably never knew about gdacs.org
Visit gdacs.orgWe analyzed Gdacs.org page load time and found that the first response time was 2.8 sec and then it took 10.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
gdacs.org performance score
name
value
score
weighting
Value11.2 s
0/100
10%
Value29.8 s
0/100
25%
Value21.5 s
0/100
10%
Value2,090 ms
7/100
30%
Value0.133
81/100
15%
Value38.7 s
0/100
10%
2803 ms
900 ms
1213 ms
929 ms
709 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 71% of them (67 requests) were addressed to the original Gdacs.org, 17% (16 requests) were made to Gisco-services.ec.europa.eu and 11% (10 requests) were made to Arcgis.jrc.ec.europa.eu. The less responsive or slowest element that took the longest time to load (4.5 sec) belongs to the original domain Gdacs.org.
Page size can be reduced by 1.5 MB (18%)
8.2 MB
6.7 MB
In fact, the total size of Gdacs.org main page is 8.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. 55% of websites need less resources to load. Images take 6.6 MB which makes up the majority of the site volume.
Potential reduce by 184.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 184.1 kB or 81% of the original size.
Potential reduce by 248.9 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. GDACS images are well optimized though.
Potential reduce by 512.7 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 512.7 kB or 68% of the original size.
Potential reduce by 541.5 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. Gdacs.org needs all CSS files to be minified and compressed as it can save up to 541.5 kB or 89% of the original size.
Number of requests can be reduced by 30 (33%)
92
62
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GDACS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
gdacs.org
2803 ms
jquery-3.6.4.min.js
900 ms
bootstrap.min.css
1213 ms
gdacs_2.0.css
929 ms
bootstrap.bundle.min.js
709 ms
ol.css
410 ms
ol3-layerswitcher.css
932 ms
gdacs_mapstyle.css
1282 ms
slick.css
1123 ms
slick-theme.css
1123 ms
ol.js
2634 ms
ol3-layerswitcher.js
1443 ms
slick.min.js
1529 ms
gdacs_2.0_bootstrap4to5.css
1345 ms
load.js
19 ms
UNOSAT_A3_Natural_Landscape_FL20240426KEN_1May2024_Nairobi_1.jpg
3122 ms
Background-02.png
1316 ms
header_bkg.png
277 ms
gdacs_logo_ecs_medium3.png
270 ms
un_eu.png
298 ms
gdacs_20_banner.png
144 ms
arrow_sliding_news.png
302 ms
gdacs_20_logo.png
302 ms
calendar_icon.png
836 ms
pdfBlue.png
831 ms
right_arrow_gts_large.png
835 ms
EQ.png
830 ms
EQ_PAST.png
838 ms
TC_PAST.png
1106 ms
TC_PAST.png
1317 ms
FL.png
1798 ms
FL_PAST.png
1109 ms
FL_PAST.png
1106 ms
VO_PAST.png
2090 ms
VO_PAST.png
1745 ms
DR_PAST.png
1745 ms
DR_PAST.png
2088 ms
WF_PAST.png
2089 ms
WF_PAST.png
2368 ms
thin_bar.png
2144 ms
android_app.png
2366 ms
ios_app.png
2515 ms
rss.png
2594 ms
kml.png
2366 ms
commonfeed.png
2548 ms
cap.png
2945 ms
facebook.png
2936 ms
twitter.png
2940 ms
ec.png
3349 ms
ocha.png
3113 ms
unitar.png
3108 ms
UNOSAT_A3_Natural_Landscape_FL20240426KEN_20240501_Nairobi.jpg
2812 ms
UNOSAT_A3_Natural_Landscape_FL20240426KEN_20240501_MaiMahiu.jpg
4272 ms
UNOSAT_A3_Natural_Landscape_FL20240426KEN_20240429_GarissaCity_1.jpg
3356 ms
UNOSAT_A3_Natural_Landscape_FL20240426KEN_20240429_GarissaCity_(1)_1.jpg
2868 ms
Screenshot_2024-05-01_144124.jpg
1635 ms
MAP
4484 ms
MAP
3352 ms
vosoccjson.aspx
3787 ms
unosat.png
3212 ms
rainfall_legend.png
3579 ms
export
886 ms
3.png
452 ms
export
895 ms
export
897 ms
export
895 ms
export
891 ms
export
906 ms
export
1060 ms
export
1078 ms
2.png
449 ms
1.png
515 ms
0.png
463 ms
3.png
445 ms
2.png
464 ms
1.png
525 ms
0.png
590 ms
1.png
589 ms
0.png
525 ms
3.png
526 ms
2.png
591 ms
3.png
624 ms
2.png
622 ms
1.png
624 ms
0.png
655 ms
ico-layers.png
3129 ms
slick.woff
3139 ms
ajax-loader.gif
3225 ms
new_red.png
3331 ms
new_blue.png
3591 ms
export
188 ms
export
172 ms
gdacs_device_2.0.css
627 ms
gdacs_minidevice_2.0.css
440 ms
gdacs.org accessibility score
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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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.
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
gdacs.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
gdacs.org SEO score
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gdacs.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 Gdacs.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.
gdacs.org
Open Graph description is not detected on the main page of GDACS. 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: