4.8 sec in total
96 ms
4.4 sec
313 ms
Click here to check amazing Mobot content for United States. Otherwise, check out these important facts you probably never knew about mobot.org
Home
Visit mobot.orgWe analyzed Mobot.org page load time and found that the first response time was 96 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
mobot.org performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value7.3 s
5/100
25%
Value8.4 s
18/100
10%
Value2,140 ms
6/100
30%
Value0.486
17/100
15%
Value21.2 s
1/100
10%
96 ms
1416 ms
137 ms
109 ms
83 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Mobot.org, 88% (95 requests) were made to Missouribotanicalgarden.org and 4% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Missouribotanicalgarden.org.
Page size can be reduced by 518.9 kB (18%)
2.9 MB
2.4 MB
In fact, the total size of Mobot.org main page is 2.9 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. 35% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 58.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. This page needs HTML code to be minified as it can gain 15.4 kB, which is 22% 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 58.8 kB or 83% of the original size.
Potential reduce by 99.9 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. Mobot images are well optimized though.
Potential reduce by 283.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 283.3 kB or 72% of the original size.
Potential reduce by 76.9 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. Mobot.org needs all CSS files to be minified and compressed as it can save up to 76.9 kB or 83% of the original size.
Number of requests can be reduced by 50 (48%)
105
55
The browser has sent 105 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobot. 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 15 to 1 for CSS and as a result speed up the page load time.
mobot.org
96 ms
www.missouribotanicalgarden.org
1416 ms
default.css
137 ms
module.css
109 ms
module.css
83 ms
skin.css
104 ms
container.css
80 ms
Main.css
278 ms
portal.css
279 ms
MobotMegaMenu.css
110 ms
jquery.min.js
750 ms
jquery.tweet.js
337 ms
jquery.query-2.1.7.js
154 ms
MoBotSlideShow.js
308 ms
WebResource.axd
178 ms
jquery.hoverIntent.minified.js
210 ms
MobotMegaMenu.js
243 ms
Telerik.Web.UI.WebResource.axd
338 ms
dnncore.js
697 ms
branding.css
23 ms
branding.css
65 ms
initWidgets.js
258 ms
eventdetails.css
241 ms
stylesheetwidget.css
246 ms
megamenu.css
262 ms
analytics.js
26 ms
body-bg.jpg
720 ms
home-icon-simple.png
44 ms
logo.gif
45 ms
PageHeaderNavigation-Right-Tail.png
89 ms
whatshappeningnow-off.png
424 ms
eventsexhibits-off.png
75 ms
gardenattractions-off.png
103 ms
research-off.png
95 ms
education-off.png
121 ms
members-off.png
178 ms
familyofattractions-off.png
154 ms
OS_Homepage.jpg
604 ms
SCI_SNR_Vegetation.jpg
667 ms
EDU_Classes_springsummer_2016.jpg
714 ms
NewSpecies_2015_Catharanthus-makayensis.jpg
475 ms
PageBodyContentRight-top.png
464 ms
Crassula%20ovata%20bloom%20and%20orange%20leaves.jpg
1740 ms
e-newsletter-submit-button.gif
512 ms
PageBodyContentRight-bottom.png
557 ms
PageFooter-Top.png
589 ms
Support-The-Garden-Button.png
623 ms
Become-A-Member-Button.png
635 ms
mbg-logo-micro.gif
656 ms
social-facebook-icon.png
669 ms
social-twitter-icon.png
687 ms
social-googleplus-icon.png
698 ms
social-flickr-icon.png
729 ms
social-youtube-icon.png
721 ms
social-instagram-icon.png
731 ms
social-pinterest-icon.png
808 ms
PageFooter-Bottom.png
748 ms
PageHeader-Top-bg.png
744 ms
pageHeaderContent-bg.gif
743 ms
PageHeaderNavigation-Left-Shadow.png
746 ms
PageHeaderNavigation-bg.png
763 ms
page-bg.png
767 ms
collect
22 ms
whatshappeningnow-on.png
776 ms
eventsexhibits-on.png
775 ms
widgets.js
90 ms
DotNetNukeAjaxShared.js
746 ms
whatshappening.xml
743 ms
eventsexhibits-shadow.png
779 ms
gardenattractions-on.png
762 ms
gardenattractions-shadow.png
754 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
127 ms
research-on.png
717 ms
research-shadow.png
1022 ms
syndication
101 ms
603672517904101378
118 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
31 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
56 ms
education-on.png
489 ms
hJF51qrW_normal.jpeg
22 ms
education-shadow.png
458 ms
members-on.png
453 ms
members-shadow.png
413 ms
familyofattractions-on.png
418 ms
familyofattractions-shadow.png
386 ms
navbottom-shadow.png
377 ms
PageBodyContent-top-bg.png
346 ms
link-arrow.gif
369 ms
PageBodyContentRight-bg.png
360 ms
PageBodyContentCalloutNewsletter-bg.png
368 ms
e-newsletter-input-bg-right-tail.png
346 ms
PageFooter-bg.png
351 ms
PageFooter-Green-Bib.png
352 ms
PageFooterNewsletterSignup-bg.png
338 ms
navbottom-off.png
371 ms
jot
29 ms
widgets.js
252 ms
ORCH_WebHeader_2016.jpg
802 ms
icon_on.png
249 ms
icon_off.png
274 ms
EVT_2016_HoneysuckleSweep.jpg
1121 ms
EVT_CloudForests.jpg
484 ms
ORCH_Lecture_Tariq.jpg
1073 ms
StyleSheetWidget.js
202 ms
smalltext.css
34 ms
textsmallhover.png
34 ms
textmedium.png
35 ms
textlarge.png
66 ms
mobot.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
Image elements do not have [alt] attributes
<input type="image"> elements do not have [alt] text
Form elements do not have associated labels
Links do not have a discernible name
mobot.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
mobot.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
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobot.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 Mobot.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.
mobot.org
Open Graph description is not detected on the main page of Mobot. 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: