6.8 sec in total
1.5 sec
4.9 sec
388 ms
Click here to check amazing Invedin content. Otherwise, check out these important facts you probably never knew about invedin.org
INVEDIN asociación civil sin fines de lucro dedicada a la atención de niños y jóvenes con trastornos del neurodesarrollo, problemas emocionales y/o de conducta
Visit invedin.orgWe analyzed Invedin.org page load time and found that the first response time was 1.5 sec and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
invedin.org performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value26.2 s
0/100
25%
Value11.9 s
4/100
10%
Value1,090 ms
24/100
30%
Value0.001
100/100
15%
Value19.7 s
2/100
10%
1459 ms
76 ms
43 ms
414 ms
186 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 63% of them (53 requests) were addressed to the original Invedin.org, 15% (13 requests) were made to Fonts.gstatic.com and 6% (5 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Invedin.org.
Page size can be reduced by 608.0 kB (15%)
4.1 MB
3.5 MB
In fact, the total size of Invedin.org main page is 4.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. 75% 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. Images take 3.2 MB which makes up the majority of the site volume.
Potential reduce by 187.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 187.1 kB or 83% of the original size.
Potential reduce by 291.3 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. Invedin images are well optimized though.
Potential reduce by 67.3 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 67.3 kB or 14% of the original size.
Potential reduce by 62.3 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. Invedin.org needs all CSS files to be minified and compressed as it can save up to 62.3 kB or 36% of the original size.
Number of requests can be reduced by 46 (70%)
66
20
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Invedin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
www.invedin.org
1459 ms
js
76 ms
css2
43 ms
styles.css
414 ms
wp_head.css
186 ms
pagenavi-css.css
198 ms
all.css
43 ms
css
35 ms
style.min.css
232 ms
css
17 ms
magnific_popup.css
94 ms
magnific_popup.css
91 ms
swiper.css
162 ms
popup.css
167 ms
animate.css
189 ms
readmore.css
192 ms
style.css
200 ms
frontend-gtag.min.js
227 ms
element
432 ms
mediaelementplayer-legacy.min.css
258 ms
wp-mediaelement.min.css
260 ms
hooks.min.js
258 ms
i18n.min.js
265 ms
index.js
312 ms
index.js
319 ms
jquery.min.js
373 ms
jquery-migrate.min.js
322 ms
scripts.min.js
539 ms
jquery.fitvids.js
333 ms
jquery.mobile.js
381 ms
easypiechart.js
387 ms
salvattore.js
395 ms
magnific-popup.js
400 ms
common.js
539 ms
api.js
36 ms
wp-polyfill.min.js
539 ms
index.js
539 ms
wp_footer.js
540 ms
mediaelement-and-player.min.js
542 ms
mediaelement-migrate.min.js
540 ms
wp-mediaelement.min.js
541 ms
logo-invedin-new.svg
491 ms
conoce-los-servicio-de-nuestro-centro-de-evaluaciones-y-tratamiento.png
681 ms
conoce-los-servicio-de-nuestro-centro-de-evaluaciones-y-tratamiento.svg
906 ms
congreso-venezolano-de-neurodesarrollo-familia-y-comunidad-1.svg
1312 ms
linea-de-atencion-psicoemocional-1.svg
580 ms
proyecto-petare-1.webp
541 ms
proyecto-caracas.jpeg
467 ms
programa-corazones-blancos-1.jpeg
637 ms
evaluacion-y-tratamientos.jpg
636 ms
educacion-especial.webp
640 ms
logo-congreso-1-400x250.png
84 ms
diseno-sin-titulo-43-400x250.png
184 ms
photo-14-2024-05-16-16-56-43-400x250.jpg
185 ms
img-20240510-wa0027-1-400x250.jpg
185 ms
photo-6-2024-05-16-16-36-33-400x250.jpg
184 ms
logo-50-invedin-01-4-400x250.png
185 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
168 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
254 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
342 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
344 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf
345 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exQ.ttf
345 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exQ.ttf
342 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exQ.ttf
343 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exQ.ttf
342 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exQ.ttf
345 ms
fa-solid-900.woff
99 ms
fa-regular-400.woff
165 ms
fa-brands-400.woff
166 ms
modules.woff
252 ms
recaptcha__en.js
200 ms
anchor
43 ms
styles__ltr.css
6 ms
recaptcha__en.js
10 ms
8Di8FwPovzey2LLchqkPL-96dOmJYGvPM2IDY7x7VBc.js
37 ms
webworker.js
72 ms
logo_48.png
25 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
7 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
6 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
32 ms
recaptcha__en.js
9 ms
style.min.css
85 ms
style.min.css
80 ms
invedin.org 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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.
invedin.org 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
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
invedin.org SEO score
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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Invedin.org can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Invedin.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.
invedin.org
Open Graph description is not detected on the main page of Invedin. 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: