2.5 sec in total
388 ms
1.9 sec
266 ms
Click here to check amazing Gnome Grown Wpengine content for United States. Otherwise, check out these important facts you probably never knew about gnomegrown.wpengine.com
We’re here to enhance your cannabis-buying experience with accessible expertise, a carefully curated shelf, and above-and-beyond service.
Visit gnomegrown.wpengine.comWe analyzed Gnomegrown.wpengine.com page load time and found that the first response time was 388 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
gnomegrown.wpengine.com performance score
name
value
score
weighting
Value6.8 s
2/100
10%
Value12.5 s
0/100
25%
Value18.7 s
0/100
10%
Value1,070 ms
25/100
30%
Value0.021
100/100
15%
Value43.0 s
0/100
10%
388 ms
31 ms
29 ms
26 ms
37 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Gnomegrown.wpengine.com, 86% (60 requests) were made to Gnomegrownorganics.com and 6% (4 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Rdwinery.com.
Page size can be reduced by 100.1 kB (5%)
1.9 MB
1.8 MB
In fact, the total size of Gnomegrown.wpengine.com main page is 1.9 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.1 MB which makes up the majority of the site volume.
Potential reduce by 71.4 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 71.4 kB or 78% of the original size.
Potential reduce by 16.4 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. Gnome Grown Wpengine images are well optimized though.
Potential reduce by 1.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. This website has mostly compressed JavaScripts.
Potential reduce by 11.0 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. Gnomegrown.wpengine.com has all CSS files already compressed.
Number of requests can be reduced by 45 (79%)
57
12
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gnome Grown Wpengine. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
gnomegrownorganics.com
388 ms
style.min.css
31 ms
linearicons.css
29 ms
font-awesome.min.css
26 ms
frontend.css
37 ms
gnome-grown-dc-public.css
34 ms
dashicons.min.css
52 ms
uaf.css
51 ms
easy-social-share-buttons.min.css
53 ms
front.min.css
52 ms
js_composer.min.css
71 ms
Defaults.css
59 ms
ultimate.min.css
85 ms
bootstrap.min.css
60 ms
base.min.css
63 ms
style.min.css
83 ms
other.min.css
102 ms
style.css
106 ms
custom-skin.css
98 ms
kvj4ulk.css
133 ms
jquery.min.js
102 ms
jquery-migrate.min.js
102 ms
linearicons.js
105 ms
gnome-grown-dc-public.js
105 ms
rbtools.min.js
124 ms
rs6.min.js
136 ms
ultimate-params.min.js
115 ms
av.js
110 ms
email-decode.min.js
55 ms
css
62 ms
animate.min.css
61 ms
all.min.css
72 ms
rs6.css
65 ms
front.min.js
80 ms
gsap.min.js
84 ms
ScrollToPlugin.min.js
77 ms
ScrollMagic.min.js
85 ms
animation.gsap.min.js
85 ms
sticky-header.min.js
87 ms
js_composer_front.min.js
92 ms
vc-waypoints.min.js
93 ms
jquery-appear.min.js
94 ms
ultimate_bg.min.js
195 ms
custom.min.js
95 ms
main.min.js
276 ms
styles.css
277 ms
p.css
22 ms
whitedown1.png
1003 ms
footer.jpg
534 ms
main.js
490 ms
AVlogo.png
110 ms
white-gnome-logo.png
109 ms
dummy.png
109 ms
oregon-cannabis-dispensary.jpg
110 ms
Gnome-Grown_Logomark-Horizontal_Light-Gray-.png
110 ms
popup-image.png
162 ms
loading.gif
161 ms
round-prof.png
162 ms
d
77 ms
d
99 ms
d
99 ms
5349Dublin.woff
426 ms
flaticon.woff
317 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrc.woff
105 ms
fa-brands-400.ttf
99 ms
fa-regular-400.ttf
526 ms
fa-solid-900.ttf
693 ms
fa-v4compatibility.ttf
381 ms
fontawesome-webfont.woff
558 ms
AVbg.jpg
305 ms
gnomegrown.wpengine.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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
gnomegrown.wpengine.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
gnomegrown.wpengine.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
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 Gnomegrown.wpengine.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 Gnomegrown.wpengine.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.
gnomegrown.wpengine.com
Open Graph data is detected on the main page of Gnome Grown Wpengine. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: