Access inclusioncharter.org. Five steps to inclusion in humanitarian response

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

51/100

25%

SI (Speed Index)

Value5.3 s

59/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

inclusioncharter.org

1003 ms

bootstrap.css

250 ms

style.css

170 ms

color.css

167 ms

responsive.css

176 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 87% of them (67 requests) were addressed to the original Inclusioncharter.org, 5% (4 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Inclusioncharter.org.

Content Size

8.7 MB

After Optimization

7.5 MB

In fact, the total size of Inclusioncharter.org main page is 8.7 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. 60% of websites need less resources to load. Images take 8.3 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 68.8 kB

Original 81.4 kB
After minification 59.6 kB
After compression 12.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. This page needs HTML code to be minified as it can gain 21.8 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 68.8 kB or 85% of the original size.

Image Optimization

-13%

Potential reduce by 1.1 MB

Original 8.3 MB
After minification 7.2 MB

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, Inclusion Charter needs image optimization as it can save up to 1.1 MB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-28%

Potential reduce by 90.9 kB

Original 329.3 kB
After minification 326.7 kB
After compression 238.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 90.9 kB or 28% of the original size.

CSS Optimization

-47%

Potential reduce by 35.0 kB

Original 74.5 kB
After minification 70.2 kB
After compression 39.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. Inclusioncharter.org needs all CSS files to be minified and compressed as it can save up to 35.0 kB or 47% of the original size.

Requests Now

After Optimization

The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Inclusion Charter. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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.

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

EN
Language Claimed

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Inclusioncharter.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 Inclusioncharter.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.

Social Sharing Optimization

inclusioncharter.org

Open Graph description is not detected on the main page of Inclusion Charter. 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:

Report Summary

Performance

Accessibility

Best Practices

SEO

Five steps to inclusion in humanitarian response | Inclusion Charter

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

inclusioncharter.org

bootstrap.css

style.css

color.css

responsive.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

inclusioncharter.org

bootstrap.css

style.css

color.css

responsive.css

scheme37.css

magnific-popup.css

font-awesome.css

css

settings.css

style.css

jquery.js

bootstrap.min.js

triger.js

jquery.themepunch.plugins.min.js

jquery.themepunch.revolution.min.js

owl.carousel.js

goalProgress.js

sorting.js

jquery.fancybox.pack.js

jquery.magnific-popup.js

js

map.js

addthis_widget.js

hompage-tab-4_1998x1332.jpg

homepage-tab2_1920x750.jpg

homepage-tab3_1920x750.jpg

inclusion-charter_1920x1080.jpg

participation.png

data.png

funding.png

capacity.png

coordination.png

574bcc9c68e08.jpg

572b677d31be9.jpg

5734f2a900006.png

5730b7a6b433f.jpg

5730b90f93f9d.png

57309876da256.jpg

5730b3ae24fd4.png

573099806c857.jpg

5730af39b0aa2.jpg

5730b00347223.png