7.7 sec in total
293 ms
6.5 sec
895 ms
Click here to check amazing Gnar Jars content. Otherwise, check out these important facts you probably never knew about gnarjars.com
Visit gnarjars.comWe analyzed Gnarjars.com page load time and found that the first response time was 293 ms and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
gnarjars.com performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value11.6 s
0/100
25%
Value6.8 s
34/100
10%
Value100 ms
98/100
30%
Value0.013
100/100
15%
Value7.9 s
43/100
10%
293 ms
898 ms
289 ms
447 ms
450 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 81% of them (82 requests) were addressed to the original Gnarjars.com, 16% (16 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Gnarjars.com.
Page size can be reduced by 1.8 MB (11%)
15.4 MB
13.6 MB
In fact, the total size of Gnarjars.com main page is 15.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. 65% of websites need less resources to load. Images take 14.7 MB which makes up the majority of the site volume.
Potential reduce by 324.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. 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 324.0 kB or 83% of the original size.
Potential reduce by 1.4 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. Gnar Jars images are well optimized though.
Potential reduce by 45.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 45.4 kB or 15% of the original size.
Potential reduce by 5.7 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. Gnarjars.com needs all CSS files to be minified and compressed as it can save up to 5.7 kB or 17% of the original size.
Number of requests can be reduced by 42 (51%)
82
40
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gnar Jars. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
gnarjars.com
293 ms
gnarjars.com
898 ms
style.css
289 ms
woocommerce-layout.css
447 ms
woocommerce.css
450 ms
css
30 ms
css
20 ms
photoswipe.min.css
306 ms
default-skin.min.css
408 ms
select2.css
414 ms
jquery.min.js
593 ms
jquery-migrate.min.js
475 ms
jquery.blockUI.min.js
472 ms
js.cookie.min.js
542 ms
woocommerce.min.js
581 ms
jquery.zoom.min.js
701 ms
jquery.flexslider.min.js
702 ms
photoswipe.min.js
701 ms
photoswipe-ui-default.min.js
709 ms
single-product.min.js
753 ms
cart-fragments.min.js
781 ms
country-select.min.js
783 ms
address-i18n.min.js
786 ms
checkout.min.js
868 ms
select2.full.min.js
1029 ms
selectWoo.full.min.js
1055 ms
wc-blocks.css
919 ms
mediaelementplayer-legacy.min.css
923 ms
wp-mediaelement.min.css
928 ms
add-to-cart.min.js
1004 ms
app.js
1078 ms
omnisend-snippet-script.js
1078 ms
launcher-v2.js
46 ms
omnisend-front-script.js
1080 ms
scripts.min.js
1438 ms
jquery.fitvids.js
1192 ms
easypiechart.js
1195 ms
salvattore.js
1275 ms
sourcebuster.min.js
1243 ms
order-attribution.min.js
1274 ms
common.js
1397 ms
mediaelement-and-player.min.js
1395 ms
mediaelement-migrate.min.js
1116 ms
wp-mediaelement.min.js
1121 ms
gnarjarsREgistered.png
1200 ms
slide.png
1350 ms
GnarJarsHero.png
1779 ms
high-times-logo.webp
950 ms
budsfeed.png
971 ms
leafly-logo.webp
1063 ms
merry-jane-logo.webp
1101 ms
dank-city-logo.webp
1032 ms
FRESH.ICON_.png
1379 ms
PROTECTION.ICON_.png
1502 ms
et-divi-dynamic-tb-9848-9-late.css
1212 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
25 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVc.ttf
32 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
32 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
31 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
31 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf
31 ms
pxiByp8kv8JHgFVrLGT9Z1JlEA.ttf
32 ms
pxiEyp8kv8JHgFVrJJnedw.ttf
32 ms
pxiByp8kv8JHgFVrLDz8Z1JlEA.ttf
34 ms
pxiByp8kv8JHgFVrLFj_Z1JlEA.ttf
33 ms
pxiGyp8kv8JHgFVrLPTufntF.ttf
32 ms
pxiByp8kv8JHgFVrLEj6Z1JlEA.ttf
33 ms
pxiByp8kv8JHgFVrLCz7Z1JlEA.ttf
43 ms
pxiByp8kv8JHgFVrLDD4Z1JlEA.ttf
44 ms
pxiByp8kv8JHgFVrLBT5Z1JlEA.ttf
44 ms
1cXxaUPXBpj2rGoU7C9WhnGA.ttf
44 ms
modules.woff
1320 ms
NOODOR.ICON_.png
1507 ms
DUAL.ICON_.png
1420 ms
71yN4IfeF3L._SL1600_.jpg
1420 ms
71QkLZ1sdGL._SL1600_.jpg
1988 ms
Screenshot-2024-08-25-120810.png
1933 ms
61FJuDc8uXL._SL1600_.jpg
1610 ms
Screenshot-2024-08-25-120736.png
1916 ms
arrow6.png
1496 ms
arrow1.png
1626 ms
GnarJarswebsite2.png
2010 ms
arrow5.png
1660 ms
arrow4.png
1839 ms
setsusapartmobile.png
2042 ms
herbguard4-1080x1080.jpg
2714 ms
herbguard2-1229x1536.jpg
1814 ms
herbguard3-1229x1536.jpg
1886 ms
Screenshot-2024-08-25-112919-1080x866.png
1975 ms
check.png
1904 ms
Screenshot-2024-08-25-163350-400x250.png
1927 ms
enviormentblog-400x250.jpg
1863 ms
DALL%C2%B7E-2024-08-25-16.18.37-An-image-showing-a-plastic-baggie-filled-with-cannabis-flower-and-a-plastic-pop-container.-Both-items-should-be-clearly-visible-but-have-a-large-red-c-400x250.webp
1884 ms
gnarjarsEBC.png
1892 ms
gnarjars.com
2989 ms
herbguard4-100x100.jpg
1195 ms
herbguard2-100x100.jpg
1207 ms
herbguard3-100x100.jpg
1240 ms
Screenshot-2024-08-25-112919-100x100.png
1309 ms
herbguard4.jpg
1455 ms
woocommerce-smallscreen.css
151 ms
gnarjars.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
Image elements do not have [alt] attributes
Form elements do not have associated labels
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.
gnarjars.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
gnarjars.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Gnarjars.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 Gnarjars.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.
gnarjars.com
Open Graph description is not detected on the main page of Gnar Jars. 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: