1.9 sec in total
36 ms
1.5 sec
392 ms
Welcome to 2funguys.com homepage info - get ready to check 2 Fun Guys best content right away, or after learning these important things about 2funguys.com
Mushroom growers 2 Fun Guys, based in Atlanta, Georgia, grows and sells shiitake and oyster mushrooms, and also inoculates logs.
Visit 2funguys.comWe analyzed 2funguys.com page load time and found that the first response time was 36 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
2funguys.com performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value19.5 s
0/100
25%
Value11.7 s
4/100
10%
Value2,280 ms
5/100
30%
Value0.564
12/100
15%
Value20.8 s
2/100
10%
36 ms
56 ms
75 ms
115 ms
173 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original 2funguys.com, 79% (89 requests) were made to 2funguys.b-cdn.net and 6% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (353 ms) relates to the external source Fonts.gstatic.com.
Page size can be reduced by 422.5 kB (30%)
1.4 MB
990.9 kB
In fact, the total size of 2funguys.com main page is 1.4 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. Javascripts take 870.5 kB which makes up the majority of the site volume.
Potential reduce by 267.5 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 267.5 kB or 88% of the original size.
Potential reduce by 63 B
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. 2 Fun Guys images are well optimized though.
Potential reduce by 91.9 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 91.9 kB or 11% of the original size.
Potential reduce by 63.1 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. 2funguys.com needs all CSS files to be minified and compressed as it can save up to 63.1 kB or 27% of the original size.
Number of requests can be reduced by 93 (92%)
101
8
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 2 Fun Guys. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 77 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
2funguys.com
36 ms
2funguys.com
56 ms
wp-polyfill-inert.min.js
75 ms
regenerator-runtime.min.js
115 ms
wp-polyfill.min.js
173 ms
hooks.min.js
81 ms
w.js
82 ms
jquery.min.js
195 ms
jquery-migrate.min.js
135 ms
underscore.min.js
118 ms
wp-util.min.js
152 ms
jquery.blockUI.min.js
134 ms
add-to-cart-variation.min.js
146 ms
simple-banner.js
136 ms
add-to-cart.min.js
136 ms
js.cookie.min.js
143 ms
woocommerce.min.js
149 ms
woocommerce-add-to-cart.js
148 ms
modernizr.min.js
155 ms
js
112 ms
lazysizes.min.js
242 ms
accounting.min.js
157 ms
addons.min.js
159 ms
rbtools.min.js
240 ms
rs6.min.js
300 ms
sourcebuster.min.js
183 ms
order-attribution.min.js
236 ms
react.min.js
185 ms
deprecated.min.js
237 ms
dom.min.js
302 ms
react-dom.min.js
305 ms
escape-html.min.js
288 ms
element.min.js
306 ms
is-shallow-equal.min.js
240 ms
i18n.min.js
290 ms
keycodes.min.js
288 ms
priority-queue.min.js
290 ms
compose.min.js
292 ms
private-apis.min.js
297 ms
redux-routine.min.js
293 ms
api.js
100 ms
data.min.js
233 ms
lodash.min.js
237 ms
wc-blocks-registry.js
196 ms
url.min.js
195 ms
api-fetch.min.js
181 ms
wc-settings.js
178 ms
data-controls.min.js
181 ms
html-entities.min.js
181 ms
notices.min.js
177 ms
wc-blocks-middleware.js
177 ms
wc-blocks-data.js
179 ms
dom-ready.min.js
174 ms
a11y.min.js
171 ms
primitives.min.js
169 ms
warning.min.js
162 ms
blocks-components.js
161 ms
blocks-checkout.js
153 ms
order-attribution-blocks.min.js
138 ms
dummy.png
284 ms
custom.js
103 ms
superfish.js
139 ms
core.utils.js
111 ms
core.init.js
110 ms
theme.init.js
99 ms
seopress-analytics.min.js
96 ms
4UaHrEJCrhhnVA3DgluA96rp4g.ttf
353 ms
theme.shortcodes.js
60 ms
cart-fragments.min.js
48 ms
core.messages.js
86 ms
jquery.magnific-popup.min.js
49 ms
js_composer_front.min.js
134 ms
core.min.js
135 ms
tabs.min.js
136 ms
effect.min.js
130 ms
effect-fade.min.js
77 ms
502d71fbba0c07db537cec3151d787bd.js
191 ms
recaptcha__en.js
185 ms
g.gif
147 ms
simple-banner.css
70 ms
woocommerce-layout.css
15 ms
b829ad4cebc881fd0d99a39c50a5334cd80ca106.js
65 ms
anchor
34 ms
woocommerce-smallscreen.css
12 ms
woocommerce.css
90 ms
styles__ltr.css
5 ms
recaptcha__en.js
13 ms
KkWFeSURekXGycdprVC-UY6ED-ZF5ll2JCMiHhJE2Rk.js
38 ms
webworker.js
85 ms
logo_48.png
30 ms
style.css
49 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
19 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
61 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
60 ms
recaptcha__en.js
53 ms
fontello.css
45 ms
bg_stripe_top.png
51 ms
bg_stripe.png
51 ms
style.css
16 ms
fontello.woff
18 ms
core.animation.css
20 ms
theme.shortcodes.css
18 ms
plugin.woocommerce.css
17 ms
theme.css
30 ms
custom-style.css
20 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
25 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
26 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
24 ms
responsive.css
25 ms
js_composer.min.css
36 ms
core.messages.min.css
19 ms
magnific-popup.min.css
17 ms
rs6.css
23 ms
2funguys.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.
2funguys.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
2funguys.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 2funguys.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 2funguys.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.
2funguys.com
Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: