3.9 sec in total
968 ms
2.6 sec
330 ms
Welcome to cartong.org homepage info - get ready to check CartONG best content for Mali right away, or after learning these important things about cartong.org
pour l’humanitaire et le développement…
Visit cartong.orgWe analyzed Cartong.org page load time and found that the first response time was 968 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
cartong.org performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value6.1 s
12/100
25%
Value9.8 s
10/100
10%
Value650 ms
46/100
30%
Value0.002
100/100
15%
Value10.5 s
23/100
10%
968 ms
165 ms
242 ms
179 ms
286 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 53% of them (49 requests) were addressed to the original Cartong.org, 10% (9 requests) were made to Maps.google.com and 9% (8 requests) were made to Tile.openstreetmap.org. The less responsive or slowest element that took the longest time to load (999 ms) belongs to the original domain Cartong.org.
Page size can be reduced by 865.9 kB (42%)
2.1 MB
1.2 MB
In fact, the total size of Cartong.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. 70% of websites need less resources to load. Images take 993.1 kB which makes up the majority of the site volume.
Potential reduce by 159.6 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 159.6 kB or 86% of the original size.
Potential reduce by 61.2 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. CartONG images are well optimized though.
Potential reduce by 547.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 547.2 kB or 70% of the original size.
Potential reduce by 97.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. Cartong.org needs all CSS files to be minified and compressed as it can save up to 97.8 kB or 80% of the original size.
Number of requests can be reduced by 59 (68%)
87
28
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CartONG. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
cartong.org
968 ms
css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
165 ms
css_6mfSGwcu8XLp-wKbhRaA2oDVnKVUYf7MqChj5hUto-Y.css
242 ms
css_3HKHEBMVmCJsWh9amhzYLxgaNOVcCKb3j-kIfzTwnrI.css
179 ms
css_Th5bBMw2c0pxdddaAD6rAivS8mhTPFVjHFyzewh1NZE.css
286 ms
jquery.min.js
483 ms
jquery.once.js
244 ms
drupal.js
255 ms
jquery.cookie.js
263 ms
jquery.form.min.js
320 ms
ajax.js
397 ms
jquery_update.js
339 ms
contextual_flyout_links.js
347 ms
views_slideshow.js
376 ms
formoptions.js
397 ms
OpenLayers.js
55 ms
openlayers.js
422 ms
openlayers_layer_type_xyz.js
431 ms
openlayers_views_vector.js
466 ms
openlayers_layer_type_google.js
468 ms
js
51 ms
openlayers_behavior_layerswitcher.js
468 ms
openlayers_behavior_attribution.js
692 ms
openlayers_behavior_permalink.js
692 ms
openlayers_behavior_navigation.js
693 ms
openlayers_behavior_zoompanel.js
691 ms
openlayers_behavior_popup.js
691 ms
openlayers_behavior_keyboarddefaults.js
689 ms
base.js
688 ms
progress.js
689 ms
googleanalytics.js
690 ms
ajax_view.js
689 ms
superfish.js
691 ms
hoverIntent.js
693 ms
gardens_features.js
694 ms
local.js
695 ms
analytics.js
356 ms
header-background.png
637 ms
nav-top-icons.png
278 ms
CartONG_logo_siteweb_big2-transparence_small_1.png
999 ms
logo-redd.png
275 ms
logo-android-project.png
282 ms
logo-gredd.png
282 ms
geomatique_secours_refugies_300.png
797 ms
Nomad-Logo.png
428 ms
widgets.js
243 ms
style.css
205 ms
common.js
163 ms
map.js
164 ms
2.png
566 ms
marker-cartong-small.png
166 ms
layer-switcher-maximize.png
164 ms
layer-switcher-minimize.png
191 ms
arrows.png
189 ms
2.png
442 ms
2.png
442 ms
2.png
441 ms
1.png
440 ms
1.png
442 ms
1.png
528 ms
1.png
528 ms
openlayers_style.css
179 ms
collect
129 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
134 ms
util.js
76 ms
onion.js
81 ms
ViewportInfoService.GetViewportInfo
90 ms
stats.js
23 ms
controls.js
73 ms
syndication
149 ms
345148238577410048
238 ms
zoom-panel.png
101 ms
transparent.png
86 ms
css
81 ms
vt
13 ms
vt
10 ms
google4.png
75 ms
mapcnt6.png
76 ms
AuthenticationService.Authenticate
71 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
21 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
20 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
21 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
17 ms
proxy.jpg
104 ms
1f603.png
102 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
41 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
44 ms
cartong_logo_normal.gif
144 ms
ixx7R8eZ_normal.jpg
172 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
36 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
25 ms
proxy.jpg
19 ms
cartong.org 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.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
cartong.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
cartong.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
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 Cartong.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 Cartong.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.
cartong.org
Open Graph description is not detected on the main page of CartONG. 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: