4 sec in total
132 ms
3.1 sec
730 ms
Click here to check amazing Recharge Smoothies content. Otherwise, check out these important facts you probably never knew about rechargesmoothies.com
Visit rechargesmoothies.comWe analyzed Rechargesmoothies.com page load time and found that the first response time was 132 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
rechargesmoothies.com performance score
name
value
score
weighting
Value4.5 s
16/100
10%
Value6.3 s
10/100
25%
Value15.4 s
0/100
10%
Value6,750 ms
0/100
30%
Value0.727
6/100
15%
Value23.8 s
1/100
10%
132 ms
341 ms
514 ms
210 ms
192 ms
Our browser made a total of 128 requests to load all elements on the main page. We found that 76% of them (97 requests) were addressed to the original Rechargesmoothies.com, 5% (6 requests) were made to Lh3.googleusercontent.com and 4% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Rechargesmoothies.com.
Page size can be reduced by 640.9 kB (18%)
3.5 MB
2.9 MB
In fact, the total size of Rechargesmoothies.com 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. 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. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 229.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 229.6 kB or 83% of the original size.
Potential reduce by 9.3 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. Recharge Smoothies images are well optimized though.
Potential reduce by 333.4 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 333.4 kB or 28% of the original size.
Potential reduce by 68.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. Rechargesmoothies.com needs all CSS files to be minified and compressed as it can save up to 68.5 kB or 35% of the original size.
Number of requests can be reduced by 85 (72%)
118
33
The browser has sent 118 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Recharge Smoothies. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 70 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
rechargesmoothies.com
132 ms
rechargesmoothies.com
341 ms
www.rechargesmoothies.com
514 ms
dashicons.min.css
210 ms
extra.min.css
192 ms
woocommerce-layout.css
224 ms
woocommerce.css
275 ms
front.min.css
222 ms
style.min.css
203 ms
style.min.css
307 ms
magnific_popup.css
230 ms
swiper.css
248 ms
popup.css
257 ms
animate.css
273 ms
readmore.css
276 ms
modern.css
292 ms
element.js
437 ms
jquery.min.js
398 ms
jquery-migrate.min.js
360 ms
jquery.blockUI.min.js
340 ms
add-to-cart.min.js
367 ms
js.cookie.min.js
380 ms
woocommerce.min.js
400 ms
ie-compat.min.js
423 ms
ewm2.js
158 ms
js
108 ms
js
178 ms
js
190 ms
wc-blocks.css
393 ms
trustindex-google-widget.css
578 ms
rs6.css
579 ms
rbtools.min.js
910 ms
rs6.min.js
820 ms
sourcebuster.min.js
577 ms
order-attribution.min.js
577 ms
wp-polyfill-inert.min.js
828 ms
regenerator-runtime.min.js
634 ms
wp-polyfill.min.js
635 ms
react.min.js
853 ms
hooks.min.js
778 ms
loader.js
26 ms
deprecated.min.js
775 ms
dom.min.js
783 ms
react-dom.min.js
777 ms
escape-html.min.js
802 ms
element.min.js
789 ms
is-shallow-equal.min.js
814 ms
i18n.min.js
795 ms
keycodes.min.js
775 ms
priority-queue.min.js
795 ms
compose.min.js
783 ms
private-apis.min.js
771 ms
redux-routine.min.js
766 ms
data.min.js
762 ms
lodash.min.js
833 ms
wc-blocks-registry.js
773 ms
url.min.js
736 ms
api-fetch.min.js
740 ms
wc-settings.js
739 ms
data-controls.min.js
739 ms
html-entities.min.js
748 ms
notices.min.js
737 ms
wc-blocks-middleware.js
742 ms
wc-blocks-data.js
748 ms
dom-ready.min.js
737 ms
gtm.js
165 ms
fbevents.js
165 ms
AD5-WCl3Cg43XTzCFycX1Csoa1owM88Hv3HwGoUKfNFt4g=s120-c-c-rp-w64-h64-mo-br100
362 ms
AEdFTp7Bi58PZjKvErppuVN_GMPBOxsYiqhm14cFNxHm=s120-c-c-rp-w64-h64-mo-br100
398 ms
AEdFTp6LaHYgULALfSz8Mo732soFTwCHacwDdb9C-08a=s120-c-c-rp-w64-h64-mo-br100
448 ms
AEdFTp5_oDPaDvw8WUleRFGa-MzLPQREVxlY4Y_xGTbq=s120-c-c-rp-w64-h64-mo-br100
409 ms
AEdFTp4KiFMAgt9E44U61R9PKrTrKgT2XMfWYqdx6_0j=s120-c-c-rp-w64-h64-mo-br100
435 ms
AD5-WCmLOTEyOMjDwEY0oVgdkhvjjnY9K0qb6bMl_1o3rA=s120-c-c-rp-w64-h64-mo-ba4-br100
436 ms
a11y.min.js
628 ms
embed
393 ms
224 ms
loader.js
216 ms
primitives.min.js
577 ms
warning.min.js
597 ms
blocks-components.js
592 ms
blocks-checkout.js
668 ms
analytics.js
197 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkM0o58i-xw.ttf
234 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58i-xw.ttf
404 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkKEo58i-xw.ttf
259 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkCEv58i-xw.ttf
314 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkBgv58i-xw.ttf
298 ms
order-attribution-blocks.min.js
566 ms
icon.svg
100 ms
front.min.js
464 ms
f.svg
25 ms
scripts.min.js
497 ms
smoothscroll.js
454 ms
call-tracking_7.js
21 ms
62 ms
collect
13 ms
collect
38 ms
jquery.fitvids.js
422 ms
frontend-bundle.min.js
465 ms
common.js
452 ms
dsm-shuffle.js
454 ms
ga-audiences
91 ms
gsap.min.js
463 ms
wcm
38 ms
revealFX.js
414 ms
frontend.min.js
447 ms
js
57 ms
sticky-elements.js
500 ms
modules.woff
445 ms
recharge-smoothies-logo.png
464 ms
dummy.png
453 ms
Inside-a-Smoothie-Shop-Recharge-Smoothies-Sunrise-Florida.jpg
585 ms
slim-body.png
583 ms
bolt.png
577 ms
healthy-living.png
573 ms
muscle.png
873 ms
instagram.jpg
1031 ms
telephone.png
522 ms
mail.png
515 ms
location.png
795 ms
payments.png
512 ms
banmner.jpg
537 ms
ordinary-fruits-with-amazing-health-benefits-05-1440x810-1.jpg
576 ms
avocado-kiwi-green-smoothie-1114x800-1.jpg
196 ms
kabocha-squash-with-mango-1-960x540-1.jpg
196 ms
Strawberry-Smoothies-e1504924049391-881x800-1.jpg
242 ms
Chocolate-Chia-Banana-Smoothie-ig-800x800-1.jpg
291 ms
woocommerce-smallscreen.css
64 ms
rechargesmoothies.com accessibility score
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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 IDs are not unique
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.
rechargesmoothies.com 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
rechargesmoothies.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 Rechargesmoothies.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 Rechargesmoothies.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.
rechargesmoothies.com
Open Graph description is not detected on the main page of Recharge Smoothies. 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: