4.7 sec in total
578 ms
3.7 sec
341 ms
Welcome to weec2013.org homepage info - get ready to check Weec 2013 best content for Mexico right away, or after learning these important things about weec2013.org
The Seventh World Environmental Education Congress will be held in Marrakech (Morocco) from 9 to 14 June 2013.
Visit weec2013.orgWe analyzed Weec2013.org page load time and found that the first response time was 578 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
weec2013.org performance score
name
value
score
weighting
Value7.7 s
0/100
10%
Value8.7 s
1/100
25%
Value10.3 s
8/100
10%
Value1,340 ms
17/100
30%
Value0
100/100
15%
Value17.0 s
5/100
10%
578 ms
187 ms
284 ms
388 ms
521 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 87% of them (96 requests) were addressed to the original Weec2013.org, 5% (5 requests) were made to Youtube.com and 2% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (884 ms) belongs to the original domain Weec2013.org.
Page size can be reduced by 713.3 kB (20%)
3.5 MB
2.8 MB
In fact, the total size of Weec2013.org main page is 3.5 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. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 43.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 43.6 kB or 79% of the original size.
Potential reduce by 71.5 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. Weec 2013 images are well optimized though.
Potential reduce by 399.1 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 399.1 kB or 53% of the original size.
Potential reduce by 199.1 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. Weec2013.org needs all CSS files to be minified and compressed as it can save up to 199.1 kB or 67% of the original size.
Number of requests can be reduced by 77 (72%)
107
30
The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Weec 2013. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 46 to 1 for CSS and as a result speed up the page load time.
index.php
578 ms
widgetkit-7a5c66f9.css
187 ms
template.css
284 ms
bootstrap.min.css
388 ms
mootools-core.js
521 ms
core.js
318 ms
caption.js
319 ms
jquery.js
474 ms
widgetkit-05688b59.js
388 ms
base.css
427 ms
layout.css
427 ms
menus.css
483 ms
modules.css
484 ms
tools.css
639 ms
system.css
547 ms
extensions.css
569 ms
custom.css
578 ms
animations.css
579 ms
green.css
615 ms
cardboard.css
642 ms
lucida.css
665 ms
georgia.css
674 ms
lucida.css
674 ms
style.css
710 ms
print.css
745 ms
warp.js
749 ms
accordionmenu.js
760 ms
dropdownmenu.js
768 ms
template.js
769 ms
lightbox.js
265 ms
mediaelement-and-player.js
415 ms
spotlight.js
312 ms
base.css
314 ms
layout.css
319 ms
menus.css
319 ms
modules.css
358 ms
system.css
418 ms
system.css
408 ms
system-all.css
417 ms
tools.css
326 ms
print.css
254 ms
ILt7ly2KTj8
123 ms
frontend.php
537 ms
menu_line_item.png
108 ms
icons_social_mini.png
107 ms
logo.png
537 ms
BADGE2_mini.png
115 ms
menubar.png
100 ms
menu_dropdown_level1_current.png
107 ms
cover_atti.jpg
404 ms
banner_8_weec.jpg
536 ms
ecoresponsability.jpg
535 ms
rete_weec_copia.jpg
387 ms
fm6_big.jpg
387 ms
buttons.png
403 ms
nav.png
403 ms
content.png
536 ms
printButton.png
535 ms
mod_box_header.png
534 ms
proceedings.jpg
884 ms
article_links.png
612 ms
francobollo_weec2013.jpg
844 ms
mod_box.png
613 ms
facebook.png
613 ms
mod_box_header_color1.png
614 ms
rete_weec_homemini.jpg
677 ms
Logo-FM6.jpg
685 ms
mod_box_bottom.png
716 ms
weec_pastCongresses.jpg
717 ms
menara_MARRAKECH.jpg
804 ms
weec_galleryBottom.jpg
803 ms
mod_line_bottom.png
793 ms
footer.png
789 ms
totop_scroller.png
862 ms
ga.js
36 ms
slideshow.js
847 ms
__utm.gif
12 ms
www-player.css
7 ms
www-embed-player.js
25 ms
base.js
46 ms
ad_status.js
139 ms
hkwQPN6l4_SNpHVtjw8vAhWItmV3wkCVMuKaKCsfQ0c.js
97 ms
embed.js
35 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
31 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
33 ms
id
17 ms
Create
21 ms
reset.css
109 ms
text.css
189 ms
form.css
212 ms
buttons.css
212 ms
frontend.css
223 ms
style.css
223 ms
base.css
224 ms
layout.css
283 ms
modules.css
317 ms
tools.css
325 ms
green.css
325 ms
jquery-ui-1.9.2.custom.min.css
429 ms
jquery.tooltip.css
333 ms
jquery-1.5.2.min.js
566 ms
jquery-ui-1.9.2.custom.min.js
739 ms
jquery.tooltip.min.js
430 ms
jquery.validate.min.js
431 ms
functions.js
443 ms
GenerateIT
13 ms
base.css
313 ms
layout.css
254 ms
modules.css
221 ms
tools.css
231 ms
weec2013.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.
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
<frame> or <iframe> elements do not have a title
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.
weec2013.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
weec2013.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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Weec2013.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 Weec2013.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.
weec2013.org
Open Graph description is not detected on the main page of Weec 2013. 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: