5 sec in total
1.9 sec
2.7 sec
458 ms
Click here to check amazing Open Data Charter content for Mexico. Otherwise, check out these important facts you probably never knew about opendatacharter.net
Accessible, Comparable and Timely Data for All
Visit opendatacharter.netWe analyzed Opendatacharter.net page load time and found that the first response time was 1.9 sec and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
opendatacharter.net performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value9.8 s
0/100
25%
Value5.1 s
62/100
10%
Value260 ms
83/100
30%
Value0.813
4/100
15%
Value9.5 s
30/100
10%
1889 ms
28 ms
30 ms
42 ms
71 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 68% of them (69 requests) were addressed to the original Opendatacharter.net, 11% (11 requests) were made to Fonts.gstatic.com and 6% (6 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Opendatacharter.net.
Page size can be reduced by 2.4 MB (77%)
3.1 MB
702.7 kB
In fact, the total size of Opendatacharter.net main page is 3.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. CSS take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 74.0 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 74.0 kB or 79% of the original size.
Potential reduce by 50.6 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, Open Data Charter needs image optimization as it can save up to 50.6 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 908.6 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 908.6 kB or 75% of the original size.
Potential reduce by 1.4 MB
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. Opendatacharter.net needs all CSS files to be minified and compressed as it can save up to 1.4 MB or 90% of the original size.
Number of requests can be reduced by 66 (75%)
88
22
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Open Data 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 40 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
opendatacharter.net
1889 ms
wp-emoji-release.min.js
28 ms
settings.css
30 ms
css
42 ms
css
71 ms
css
93 ms
settings.css
35 ms
woocommerce-layout.css
46 ms
woocommerce.css
41 ms
mainstyle.css
48 ms
css
104 ms
css
95 ms
css
103 ms
fontello.css
50 ms
style.css
69 ms
shortcodes.css
50 ms
core.animation.css
58 ms
tribe-style.css
63 ms
skin.css
93 ms
custom-style.css
73 ms
responsive.css
73 ms
skin-responsive.css
80 ms
mediaelementplayer.min.css
85 ms
wp-mediaelement.css
97 ms
js_composer.css
108 ms
jetpack.css
98 ms
jquery.js
102 ms
jquery-migrate.min.js
101 ms
lightbox.js
102 ms
jquery.themepunch.tools.min.js
103 ms
jquery.themepunch.essential.min.js
103 ms
jquery.themepunch.revolution.min.js
206 ms
add-to-cart.min.js
101 ms
jquery.bxSlider.min.js
210 ms
tmt_core.js
211 ms
tmt_form.js
210 ms
tmt_validator.js
212 ms
lib.js
214 ms
wach.calendar.js
213 ms
woocommerce-add-to-cart.js
213 ms
idangerous.swiper.css
213 ms
photon.js
212 ms
devicepx-jetpack.js
32 ms
gprofiles.js
100 ms
e-201611.js
31 ms
jquery.blockUI.min.js
206 ms
woocommerce.min.js
201 ms
jquery.cookie.min.js
199 ms
cart-fragments.min.js
192 ms
wpgroho.js
187 ms
plugins.js
185 ms
functions.js
184 ms
superfish.min.js
176 ms
core.utils.js
176 ms
core.init.js
181 ms
mediaelement-and-player.min.js
182 ms
wp-mediaelement.js
172 ms
social-share.js
164 ms
comment-reply.min.js
162 ms
wp-embed.min.js
162 ms
shortcodes.js
157 ms
js_composer_front.js
150 ms
idangerous.swiper-2.7.js
145 ms
idangerous.swiper.scrollbar-2.4.js
144 ms
hotjar-80986.js
476 ms
odc_cover_web-06.png
48 ms
odcharter_logo-color-para-fondo-blanco.png
48 ms
odcharter_logo-color1.png
49 ms
OPEN_DATA_CHARTER_cover-01.png
45 ms
Captura-de-pantalla-2016-02-25-a-las-10.42.05.png
44 ms
testimonials_header.png
53 ms
unlock-278x300.png
47 ms
clock-278x300.png
47 ms
key-278x300.png
48 ms
overlap-278x300.png
48 ms
bank-278x300.png
48 ms
bulb-278x300.png
48 ms
turkey-g20.jpg
45 ms
Untitled-design-1.png
42 ms
g30.png
57 ms
bg_over.png
57 ms
3NHH5PYzHHrzDjzWZmlY1A.woff
48 ms
ZVUDGNBaEPTwTwYVkvzUow.woff
51 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
51 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
50 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
50 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
48 ms
EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff
48 ms
zhcz-_WihjSQC0oHJ9TCYBsxEYwM7FgeyaSgU71cLG0.woff
51 ms
IQHow_FEYlDC4Gzy_m8fcgFhaRv2pGgT5Kf0An0s4MM.woff
50 ms
woocommerce-smallscreen.css
358 ms
P82D7rv6xi_0CR2eFvCvZw.woff
365 ms
VGX2f8JCsYx_8T55JDhTUg.woff
365 ms
fontello.woff
365 ms
hovercard.css
94 ms
services.css
95 ms
maxresdefault.jpg
71 ms
loader.gif
58 ms
coloredbg.png
58 ms
g.gif
24 ms
modules-043c1e6abe660c48857202e419ff9d8a.js
35 ms
opendatacharter.net 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
Links do not have a discernible name
opendatacharter.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
opendatacharter.net 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
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 Opendatacharter.net 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 Opendatacharter.net 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.
opendatacharter.net
Open Graph data is detected on the main page of Open Data Charter. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: