6.6 sec in total
222 ms
4.5 sec
1.8 sec
Visit mumbys.com now to see the best up-to-date Mumbys content and also check out these interesting facts you probably never knew about mumbys.com
Live-in care care specialists, Mumby's carefully match professional carers to live with your loved one in their home and support their needs
Visit mumbys.comWe analyzed Mumbys.com page load time and found that the first response time was 222 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
mumbys.com performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value39.9 s
0/100
25%
Value20.0 s
0/100
10%
Value2,050 ms
7/100
30%
Value0
100/100
15%
Value37.2 s
0/100
10%
222 ms
483 ms
153 ms
232 ms
237 ms
Our browser made a total of 143 requests to load all elements on the main page. We found that 73% of them (105 requests) were addressed to the original Mumbys.com, 10% (15 requests) were made to Fonts.gstatic.com and 3% (5 requests) were made to Stcdn.leadconnectorhq.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Link.hexxie.io.
Page size can be reduced by 1.8 MB (18%)
9.7 MB
7.9 MB
In fact, the total size of Mumbys.com main page is 9.7 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 8.9 MB which makes up the majority of the site volume.
Potential reduce by 235.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 235.8 kB or 87% of the original size.
Potential reduce by 1.5 MB
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, Mumbys needs image optimization as it can save up to 1.5 MB 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 63.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 63.3 kB or 17% of the original size.
Potential reduce by 25.5 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. Mumbys.com needs all CSS files to be minified and compressed as it can save up to 25.5 kB or 15% of the original size.
Number of requests can be reduced by 80 (68%)
118
38
The browser has sent 118 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mumbys. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 39 to 1 for CSS and as a result speed up the page load time.
mumbys.com
222 ms
www.mumbys.com
483 ms
flick.css
153 ms
www.mumbys.com
232 ms
main.min.css
237 ms
elementor-icons.min.css
239 ms
custom-frontend-lite.min.css
314 ms
swiper.min.css
240 ms
post-10.css
242 ms
custom-pro-frontend-lite.min.css
305 ms
main.css
311 ms
global.css
320 ms
post-7.css
321 ms
post-3274.css
327 ms
post-265.css
382 ms
text-animations.min.css
388 ms
frontend.min.css
469 ms
all.min.css
493 ms
css
29 ms
fontawesome.min.css
399 ms
brands.min.css
405 ms
solid.min.css
459 ms
regular.min.css
465 ms
jquery.min.js
561 ms
jquery-migrate.min.js
506 ms
scrollTo.js
536 ms
jquery.form.min.js
544 ms
mailchimp.js
545 ms
core.min.js
551 ms
datepicker.js
638 ms
custom-pro-widget-nav-menu.min.css
613 ms
review_widget_carousel.js
367 ms
form_embed.js
158 ms
custom-widget-icon-list.min.css
559 ms
wpr-animations.min.css
557 ms
wpr-link-animations.min.css
564 ms
button-animations.min.css
702 ms
loading-animations.min.css
710 ms
lightgallery.min.css
710 ms
frontend.min.js
711 ms
ooohboi-steroids.js
709 ms
particles.js
633 ms
jarallax.min.js
555 ms
parallax.min.js
780 ms
jquery.smartmenus.min.js
776 ms
isotope.min.js
775 ms
slick.min.js
785 ms
lightgallery.min.js
710 ms
webpack-pro.runtime.min.js
714 ms
webpack.runtime.min.js
807 ms
frontend-modules.min.js
872 ms
wp-polyfill-inert.min.js
872 ms
regenerator-runtime.min.js
872 ms
wp-polyfill.min.js
818 ms
hooks.min.js
810 ms
i18n.min.js
795 ms
frontend.min.js
856 ms
waypoints.min.js
802 ms
frontend.min.js
795 ms
elements-handlers.min.js
769 ms
frontend.min.js
758 ms
modal-popups.min.js
758 ms
jquery.sticky.min.js
768 ms
underscore.min.js
762 ms
wp-util.min.js
759 ms
frontend.min.js
754 ms
gtm.js
271 ms
Image-1-156x67.png
655 ms
Group-1362-e1681840733880.png
1124 ms
CQC.png
667 ms
AA3I5927.png
1151 ms
Live-in-care.png
911 ms
AA3I5797.png
840 ms
0QN2VBa7jPSGSihHogG9
1380 ms
Gidole-Regular.ttf
250 ms
Kollektif-Bold.ttf
427 ms
Kollektif.ttf
506 ms
fa-brands-400.woff
731 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
144 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
237 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
294 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf
297 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf
346 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
296 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
297 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf
297 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf
297 ms
eicons.woff
766 ms
AA3I5967.png
959 ms
AA3I9335.png
900 ms
FullSupport.png
988 ms
Group-1362-2.png
914 ms
Group-1363.png
961 ms
js
122 ms
loader.js
121 ms
fa-solid-900.woff
765 ms
fa-regular-400.woff
812 ms
CompanionCare.png
904 ms
CancerCare.png
906 ms
CoupleCareLink.png
913 ms
AfterStroke.png
908 ms
call-tracking_7.js
31 ms
Dementia-Care.png
722 ms
Elderly-Care-1.png
726 ms
Emergency-Care.png
828 ms
Mental-Health-Care.png
830 ms
MS-Care.png
910 ms
Group-1364-e1687524885798-1024x299.png
834 ms
Group-1364-1.png
822 ms
ann-trevor-scaled-new.png
794 ms
iStock-126015675-qgstv20g4qt2y1d2rofc217wcv3fbds1vwvqwggbes.png
846 ms
How-do-I-go-about-paying-for-care-at-home-qicl6gyj8rz46cpy6fqpv424vzx3xrj0ulz1wkrmbo.jpg
846 ms
Live-in-Care-for-Couples-scaled-qji35bzyuwnqdy421diha70hcr1covrhb29d54dq6c.jpg
847 ms
New-Year-Resolutions-of-Senior-qgphwhcqe107i4bz7g8qsb6zbasnlqc94ygrj5n8w4.png
850 ms
Last-will-and-testament-qf120vvqdwyebjchpor82ilby39irqbyjjv1z6on9g.png
866 ms
wcm
57 ms
Movember_Iconic-Mo_Black-255x180-1-qf0z8s2ij3x1ukr89ezlis02eso906x2s2ng0b41xg.png
944 ms
Lung-cancer-qf0tj08gds8a7pnitywt67cct4wixl0hhl9sum7q2s.webp
941 ms
anthony-da-cruz-Tdm8mnRWLSc-unsplash-scaled-qeq4cqzks6dbaf5y17cbib01udx2fuxnpzp5w9unyc.jpg
943 ms
group-happy-seniors-playing-chess-having-fun-together-home-scaled-qeocnrl4tng575ung1ruyxjtk3qp8vy74rzwc9oipw.jpg
904 ms
20220709_131012-qedhxtilb487s5f8oysnlfa7eh01i148kt1r1peeh0.jpg
898 ms
Group-1365-2-e1681926880472.png
889 ms
MumbysFooter.png
784 ms
regular.css
153 ms
solid.css
188 ms
brands.css
224 ms
iframeResizer.contentWindow.min.js
21 ms
pixel.js
25 ms
css
18 ms
css
26 ms
FormComponent.88256abd.css
30 ms
vue-multiselect.eb3eab67.css
83 ms
app.d57d23cd.css
84 ms
TextElement.b602ad61.css
84 ms
OptionElement.05aaf420.css
83 ms
fbevents.js
21 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
4 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
4 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
9 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
10 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
9 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
8 ms
widget_carousel.css
331 ms
mumbys.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
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
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
Links do not have a discernible name
mumbys.com 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
Page has valid source maps
mumbys.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
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 Mumbys.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 Mumbys.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.
mumbys.com
Open Graph data is detected on the main page of Mumbys. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: