5.4 sec in total
231 ms
4.3 sec
890 ms
Visit gmoevidence.com now to see the best up-to-date GMO Evidence content for United States and also check out these interesting facts you probably never knew about gmoevidence.com
GMO Evidence is a GMO library of research and cases of GMO harm dedicated to presenting GMO evidence of harm. There is a strong focus on the research of Gilles-Eric Seralini on GMO Evidence. We also p...
Visit gmoevidence.comWe analyzed Gmoevidence.com page load time and found that the first response time was 231 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
gmoevidence.com performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value9.1 s
1/100
25%
Value8.2 s
20/100
10%
Value510 ms
57/100
30%
Value0.096
90/100
15%
Value10.4 s
24/100
10%
231 ms
1133 ms
91 ms
72 ms
128 ms
Our browser made a total of 143 requests to load all elements on the main page. We found that 50% of them (71 requests) were addressed to the original Gmoevidence.com, 11% (16 requests) were made to Maps.googleapis.com and 7% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Gmoevidence.com.
Page size can be reduced by 1.3 MB (52%)
2.5 MB
1.2 MB
In fact, the total size of Gmoevidence.com main page is 2.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. 85% 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. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 238.8 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 238.8 kB or 84% of the original size.
Potential reduce by 32.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. GMO Evidence images are well optimized though.
Potential reduce by 869.8 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 869.8 kB or 67% of the original size.
Potential reduce by 177.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. Gmoevidence.com needs all CSS files to be minified and compressed as it can save up to 177.8 kB or 85% of the original size.
Number of requests can be reduced by 78 (59%)
132
54
The browser has sent 132 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GMO Evidence. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 55 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
gmoevidence.com
231 ms
www.gmoevidence.com
1133 ms
js
91 ms
css
72 ms
css
128 ms
style.css
259 ms
media.css
262 ms
styles.css
264 ms
tp_twitter_plugin.css
257 ms
plugin.styles.css
255 ms
layerslider.css
266 ms
jquery.js
410 ms
jquery-migrate.min.js
335 ms
script.js
329 ms
layerslider.kreaturamedia.jquery.js
409 ms
jquery-easing-1.3.js
336 ms
jquerytransit.js
332 ms
layerslider.transitions.js
397 ms
quant.js
57 ms
navbar_styles.css
399 ms
www.gmoevidence.com
615 ms
jquery.form.min.js
346 ms
scripts.js
403 ms
modernizr.js
405 ms
jquery.carouFredSel-6.2.1-packed.js
407 ms
jquery.prettyPhoto.js
414 ms
jquery.isotope.min.js
415 ms
jquery.flexslider-min.js
476 ms
jquery.cycle.lite.js
480 ms
jquery.fitvids.js
480 ms
jquery.hoverIntent.minified.js
481 ms
jquery.eislideshow.js
486 ms
froogaloop.js
548 ms
jquery.placeholder.js
549 ms
jquery.waypoint.js
550 ms
gmap.js
551 ms
gauge.js
555 ms
jquery.ddslick.min.js
697 ms
jquery.infinitescroll.min.js
694 ms
main.js
696 ms
jsapi
44 ms
site.js
704 ms
markerclustererplus.js
706 ms
style.css
523 ms
all.css
126 ms
pixel;r=71165366;a=p-BZTgQU5p0Zkgp;fpan=1;fpa=P0-1294891058-1458479074437;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458479074436;tzo=-180;ref=;url=http%3A%2F%2Fwww.gmoevidence.com%2F;ogl=
86 ms
ga.js
82 ms
iframe_api
197 ms
sustainablepulse-small.png
432 ms
gmoevidence-small.png
440 ms
gmoseralini-small.png
438 ms
gmojudycarman_btmbar.png
431 ms
facebook.png
436 ms
bg-popup.png
439 ms
twitter.png
579 ms
rss.png
577 ms
gmoevidence.png
587 ms
pig_slide.jpg
742 ms
stamp-donate.png
585 ms
3rats_slide.jpg
740 ms
farmers_slide.jpg
1190 ms
hydrocefalia_slide.jpg
1590 ms
pesticides_slide.jpg
1103 ms
gmo-world-map-e1370124459700.jpg
1161 ms
3-rats-tumors.jpg
1031 ms
ico-04.png
983 ms
death-ROUNDUP-2-320x202.jpg
1187 ms
Daphnia-magna-320x202.jpg
1163 ms
Roundup-008.jpg
1670 ms
rss.png
1295 ms
bg-title.gif
1226 ms
bg-blockquote.gif
1337 ms
ico-user.gif
1336 ms
bg-line.gif
1344 ms
divider-02.gif
1360 ms
UFoEz2uiuMypUGZL1NKoeg.ttf
110 ms
F51BEgHuR0tYHxF0bD4vwvesZW2xOQ-xsNqO47m55DA.ttf
112 ms
8c9q46CAcsp9TiRX9KLgZC3USBnSvpkopQaUR-2r7iU.ttf
112 ms
likebox.php
406 ms
yls9EYWOd496wiu7qzfgNg.ttf
180 ms
lILlYDvubYemzYzN7GbLkC3USBnSvpkopQaUR-2r7iU.ttf
181 ms
common.js
121 ms
util.js
198 ms
geocoder.js
198 ms
skin.css
1154 ms
js
105 ms
mobile_menu_bg.png
1092 ms
__utm.gif
38 ms
www-widgetapi.js
42 ms
common.js
12 ms
map.js
13 ms
overlay.js
12 ms
util.js
12 ms
marker.js
11 ms
onion.js
39 ms
openhand_8_8.cur
36 ms
410ucuAGgaJ.css
294 ms
tSbl8xBI27R.css
358 ms
1kPfZUdGrka.js
493 ms
Yuj_Y8xNH2C.js
627 ms
Mpe38fuBVZ2.js
514 ms
n8qIhCw3vMx.js
513 ms
ViewportInfoService.GetViewportInfo
68 ms
stats.js
54 ms
transparent.png
59 ms
kh
57 ms
kh
59 ms
controls.js
47 ms
kh
93 ms
kh
91 ms
infowindow.js
76 ms
m2.png
31 ms
css
66 ms
m1.png
48 ms
vt
27 ms
google4.png
27 ms
vt
10 ms
vt
11 ms
vt
11 ms
vt
16 ms
mapcnt6.png
18 ms
sv5.png
21 ms
tmapctrl.png
15 ms
tmapctrl4.png
16 ms
google_white5.png
21 ms
271180_470977149601066_1305648910_n.jpg
359 ms
551585_470506806314767_422008791_n.png
429 ms
12308411_10205759964775432_5506420554339045986_n.jpg
498 ms
12246716_1206382822709374_348825571757233488_n.jpg
560 ms
10354686_10150004552801856_220367501106153455_n.jpg
560 ms
11169487_10153172217853403_7745366419998293810_n.jpg
561 ms
12802720_1756199407944525_1833680571517685398_n.jpg
562 ms
11694919_120689071654983_1470286765477798365_n.jpg
561 ms
wL6VQj7Ab77.png
155 ms
s7jcwEQH7Sx.png
154 ms
blank.gif
148 ms
skin.png
116 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
8 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
6 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
32 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
31 ms
VXcANLwwL5J.js
70 ms
AmlxWlqMvlv.js
135 ms
gmoevidence.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
button, link, and menuitem elements do not have accessible names.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
gmoevidence.com 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
gmoevidence.com 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
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 Gmoevidence.com 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 Gmoevidence.com 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.
gmoevidence.com
Open Graph description is not detected on the main page of GMO Evidence. 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: