12.6 sec in total
2.7 sec
7.3 sec
2.6 sec
Visit buddersweed.com now to see the best up-to-date Budders Weed content and also check out these interesting facts you probably never knew about buddersweed.com
Visit buddersweed.comWe analyzed Buddersweed.com page load time and found that the first response time was 2.7 sec and then it took 9.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
buddersweed.com performance score
name
value
score
weighting
Value14.7 s
0/100
10%
Value23.8 s
0/100
25%
Value17.7 s
0/100
10%
Value490 ms
58/100
30%
Value0.006
100/100
15%
Value26.9 s
0/100
10%
2654 ms
329 ms
478 ms
589 ms
474 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 77% of them (77 requests) were addressed to the original Buddersweed.com, 20% (20 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Buddersweed.com.
Page size can be reduced by 3.1 MB (37%)
8.2 MB
5.1 MB
In fact, the total size of Buddersweed.com main page is 8.2 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. Images take 5.6 MB which makes up the majority of the site volume.
Potential reduce by 159.0 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 20.5 kB, which is 11% 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 159.0 kB or 87% of the original size.
Potential reduce by 989.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. Obviously, Budders Weed needs image optimization as it can save up to 989.6 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 602.1 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 602.1 kB or 69% of the original size.
Potential reduce by 1.3 MB
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. Buddersweed.com needs all CSS files to be minified and compressed as it can save up to 1.3 MB or 88% of the original size.
Number of requests can be reduced by 60 (79%)
76
16
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Budders Weed. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
buddersweed.com
2654 ms
styles.css
329 ms
woocommerce-layout.css
478 ms
woocommerce.css
589 ms
frontend.min.css
474 ms
style.min.css
372 ms
theme.min.css
461 ms
frontend-lite.min.css
889 ms
post-11.css
557 ms
elementor-icons.min.css
630 ms
swiper.min.css
632 ms
frontend-lite.min.css
659 ms
global.css
837 ms
post-15.css
742 ms
post-31117.css
752 ms
post-32066.css
757 ms
ekiticons.css
1093 ms
style.css
866 ms
widget-styles.css
1518 ms
widget-styles-pro.css
1178 ms
responsive.css
1114 ms
css
77 ms
fontawesome.min.css
1015 ms
brands.min.css
1139 ms
wp-polyfill-inert.min.js
1209 ms
regenerator-runtime.min.js
1232 ms
wp-polyfill.min.js
1327 ms
hooks.min.js
1319 ms
w.js
271 ms
jquery.min.js
1467 ms
jquery-migrate.min.js
1312 ms
jquery.blockUI.min.js
1317 ms
add-to-cart.min.js
1408 ms
js.cookie.min.js
1413 ms
woocommerce.min.js
1423 ms
widget-icon-list.min.css
681 ms
animations.min.css
738 ms
index.js
742 ms
index.js
739 ms
underscore.min.js
740 ms
wp-util.min.js
739 ms
api-request.min.js
742 ms
i18n.min.js
744 ms
url.min.js
742 ms
api-fetch.min.js
742 ms
frontend.min.js
743 ms
hello-frontend.min.js
744 ms
frontend-script.js
744 ms
widget-scripts.js
745 ms
imagesloaded.min.js
781 ms
webpack-pro.runtime.min.js
781 ms
webpack.runtime.min.js
779 ms
frontend-modules.min.js
780 ms
frontend.min.js
780 ms
waypoints.min.js
780 ms
core.min.js
927 ms
frontend.min.js
929 ms
elements-handlers.min.js
931 ms
animate-circle.min.js
930 ms
elementor.js
926 ms
elementor.js
930 ms
swiper.min.js
1253 ms
g.gif
451 ms
Budders-Weed-Dispensary.png
722 ms
image_05_1920x800_crop_top.webp
721 ms
8qeyfgqe8f.png
723 ms
874f5.png
2770 ms
Icon-delivery.png
718 ms
image_11_1920x600_crop_top.webp
836 ms
s-img.png
915 ms
Icon-trust-150x150-1-q8rqp8mo9w5orc0gyr8g6rfseso07xqn239bu8c8cs.png
836 ms
Icon-quality-150x150-1-q8v2r7hep2lu4k42pg8jgmmmog8hq8njluhfli44ek.png
696 ms
Icon-delivery-q8v2rlkzjl54ypjlf4by012jl8azxp7ins9psnj7t8.png
696 ms
Icon-service-150x150-1-q8v2rzoke3ofsuz44sfcjfigi0di55rhpq1zzsyb7w.png
697 ms
footer-bgimg.jpg
875 ms
pay.png
696 ms
rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAkJxRSW3w.woff
190 ms
rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAopxRSW3w.woff
187 ms
rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwA_JxRSW3w.woff
188 ms
rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAIpxRSW3w.woff
281 ms
rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAop1RSW3w.woff
283 ms
rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAfJtRSW3w.woff
189 ms
rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwARZtRSW3w.woff
192 ms
rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAIptRSW3w.woff
191 ms
rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAC5tRSW3w.woff
281 ms
elementskit.woff
1110 ms
kmKiZrc3Hgbbcjq75U4uslyuy4kn0qviTgY3KcY.woff
191 ms
kmKnZrc3Hgbbcjq75U4uslyuy4kn0qNZaxU.woff
192 ms
star.woff
707 ms
pxiEyp8kv8JHgFVrJJfedA.woff
192 ms
pxiByp8kv8JHgFVrLGT9Z1xlEw.woff
190 ms
pxiByp8kv8JHgFVrLDz8Z1xlEw.woff
271 ms
pxiByp8kv8JHgFVrLFj_Z1xlEw.woff
272 ms
pxiGyp8kv8JHgFVrLPTucHtG.woff
273 ms
pxiByp8kv8JHgFVrLEj6Z1xlEw.woff
273 ms
pxiByp8kv8JHgFVrLCz7Z1xlEw.woff
271 ms
pxiByp8kv8JHgFVrLDD4Z1xlEw.woff
274 ms
pxiByp8kv8JHgFVrLBT5Z1xlEw.woff
274 ms
fa-brands-400.woff
689 ms
woocommerce-smallscreen.css
125 ms
buddersweed.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.
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
buddersweed.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
Page has valid source maps
buddersweed.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Buddersweed.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 Buddersweed.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.
buddersweed.com
Open Graph description is not detected on the main page of Budders Weed. 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: