7.2 sec in total
676 ms
5 sec
1.5 sec
Click here to check amazing Mothernode content for United States. Otherwise, check out these important facts you probably never knew about mothernode.com
Visit mothernode.comWe analyzed Mothernode.com page load time and found that the first response time was 676 ms and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
mothernode.com performance score
name
value
score
weighting
Value7.0 s
1/100
10%
Value11.9 s
0/100
25%
Value14.0 s
1/100
10%
Value320 ms
76/100
30%
Value0.018
100/100
15%
Value15.7 s
6/100
10%
676 ms
24 ms
130 ms
86 ms
130 ms
Our browser made a total of 135 requests to load all elements on the main page. We found that 67% of them (90 requests) were addressed to the original Mothernode.com, 10% (13 requests) were made to Login.mothernode.com and 10% (13 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Mothernode.com.
Page size can be reduced by 2.9 MB (57%)
5.1 MB
2.2 MB
In fact, the total size of Mothernode.com main page is 5.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. Javascripts take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 73.9 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 73.9 kB or 82% of the original size.
Potential reduce by 289.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. Obviously, Mothernode needs image optimization as it can save up to 289.9 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.8 MB
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 1.8 MB or 77% of the original size.
Potential reduce by 814.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. Mothernode.com needs all CSS files to be minified and compressed as it can save up to 814.8 kB or 87% of the original size.
Number of requests can be reduced by 65 (55%)
118
53
The browser has sent 118 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mothernode. 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 27 to 1 for CSS and as a result speed up the page load time.
www.mothernode.com
676 ms
css
24 ms
wp-emoji-release.min.js
130 ms
cnss.css
86 ms
layerslider.css
130 ms
css
15 ms
style.css
86 ms
nivo-lightbox.css
86 ms
default.css
168 ms
ppm-side-popup.css
169 ms
wpsm.css
170 ms
style.css
206 ms
stylesheet.min.css
586 ms
style_dynamic.css
265 ms
font-awesome.min.css
332 ms
style.min.css
335 ms
responsive.min.css
431 ms
style_dynamic_responsive.css
304 ms
js_composer.css
769 ms
custom_css.css
387 ms
css
21 ms
style.css
723 ms
font-awesome.min.css
500 ms
style.css
558 ms
style.css
618 ms
css.css
618 ms
jquery.js
853 ms
jquery-migrate.min.js
664 ms
cnss.js
670 ms
greensock.js
808 ms
layerslider.kreaturamedia.jquery.js
912 ms
layerslider.transitions.js
805 ms
jquery.baslider.min.js
844 ms
nivo-lightbox.min.js
834 ms
script.js
887 ms
jquery-ui.js
1194 ms
js.js
947 ms
social-likes_flat.css
959 ms
social-likes.min.js
948 ms
webform.js
285 ms
ppm-side-popup.js
781 ms
jquery.cookie.js
816 ms
jquery.easymodal.js
829 ms
wp-site-mapping.js
830 ms
qode-like.js
861 ms
plugins.js
1443 ms
jquery.carouFredSel-6.2.1.js
1162 ms
jquery.fullPage.min.js
991 ms
lemmon-slider.js
952 ms
jquery.mousewheel.min.js
936 ms
jquery.touchSwipe.min.js
1022 ms
isotope.pkgd.min.js
1060 ms
default_dynamic.js
953 ms
default.min.js
1193 ms
custom_js.js
971 ms
comment-reply.min.js
1008 ms
js_composer_front.js
981 ms
analytics.js
82 ms
MothernodeCRM-Logo.png
237 ms
Mothernode_www.png
161 ms
blank.gif
230 ms
DnvrCrptFlrng.jpg
341 ms
izonecase.jpg
371 ms
asicase.jpg
397 ms
iPhone_6_Vert_Slvr_sRGB_0914-584x1024.png
763 ms
Work-Order-Interface.png
945 ms
Outlook-Integration.png
459 ms
HubSpot-Mothernode.png
457 ms
Calendar_Integration.png
485 ms
Mailchimp-Mothernode.png
575 ms
Gmail-Integration.png
535 ms
Infusionsoft-Mothernode.png
560 ms
Constant-Contact-Mothernode1.png
759 ms
QuickBooks-Mothernode.png
759 ms
lg-8.png
627 ms
web_imc.png
712 ms
web_eag.png
826 ms
web_sum.png
826 ms
web_den.png
876 ms
lg-11.png
877 ms
lg1.png
876 ms
lg-10.png
940 ms
lg-9.png
939 ms
lg-4.png
1580 ms
lg-3.png
1577 ms
lg-7.png
1585 ms
BADGE_Apple_Store-300x81.png
142 ms
BADGE_Google_Play-300x81.png
141 ms
facebook-1.png
144 ms
linkedin.png
146 ms
twitter-1.png
146 ms
googleplus.png
145 ms
youtube.png
218 ms
DesktopSmallerb.png
1784 ms
Ecampaign-MAILER_SM.jpg
1686 ms
do7-0avPC2vxor6SN2THGA.ttf
60 ms
Li18TEFObx_yGdzKDoI_ci3USBnSvpkopQaUR-2r7iU.ttf
64 ms
ZKwULyCG95tk6mOqHQfRBC3USBnSvpkopQaUR-2r7iU.ttf
67 ms
cbAbzEjxTdN5KKmS-gA0tS3USBnSvpkopQaUR-2r7iU.ttf
61 ms
rr0ijB5_2nAJsAoZ6vECXaCWcynf_cDxXwCLxiixG1c.ttf
61 ms
STBOO2waD2LpX45SXYjQBS3USBnSvpkopQaUR-2r7iU.ttf
62 ms
WmVKXVcOuffP_qmCpFuyzS3USBnSvpkopQaUR-2r7iU.ttf
62 ms
QoPu455RxV2raYSIFXAMBS3USBnSvpkopQaUR-2r7iU.ttf
63 ms
Ji5epXNcpHu3r63lhS0cTi3USBnSvpkopQaUR-2r7iU.ttf
62 ms
ElegantIcons.woff
1520 ms
linkid.js
43 ms
fontawesome-webfont.woff
1566 ms
fontawesome-webfont.woff
1597 ms
l8qaLjygvOkDEU2G6-cjfQ.ttf
27 ms
7PivP8Zvs2qn6F6aNbSQe_esZW2xOQ-xsNqO47m55DA.ttf
27 ms
ZCcPJiCGOzh84o2siPk48V02b4v3fUxqf9CZJ1qUoIA.ttf
25 ms
collect
49 ms
collect
76 ms
webform.php
261 ms
5xAt7XK2vkUdjhGtt98uneGMkauwsY7KZ6tVtEZSDQ4.ttf
25 ms
i2cal.css
758 ms
CalendarPopup.js
947 ms
jquery-ui.css
917 ms
jquery-1.9.1.js
1206 ms
jquery-ui.js
1244 ms
prototype.js
1064 ms
i2.js
916 ms
effects.js
1203 ms
country_state_select.js
1201 ms
skin.css
245 ms
fql
200 ms
gpp.xml
990 ms
N+6gaV3IxODy2bWFDYGFxcA620lLw==
1 ms
skin.png
69 ms
MothernodeCRM1d.jpg
344 ms
CRMDEMO.png
149 ms
indicator.gif
129 ms
ajax-loading.gif
160 ms
MothernodeCRM1e.jpg
298 ms
loading.gif
89 ms
mothernode.com 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.
mothernode.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
mothernode.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
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 Mothernode.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 Mothernode.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.
mothernode.com
Open Graph description is not detected on the main page of Mothernode. 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: