4.5 sec in total
760 ms
3 sec
764 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 760 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.
gnomegrown.wpengine.com performance score
name
value
score
weighting
Value6.7 s
2/100
10%
Value15.8 s
0/100
25%
Value35.3 s
0/100
10%
Value70,700 ms
0/100
30%
Value0.005
100/100
15%
Value93.4 s
0/100
10%
760 ms
38 ms
41 ms
60 ms
476 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, 89% (62 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.1 sec) relates to the external source Gnomegrownorganics.com.
Page size can be reduced by 133.2 kB (6%)
2.2 MB
2.1 MB
In fact, the total size of Gnomegrown.wpengine.com main page is 2.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. 80% 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.7 MB which makes up the majority of the site volume.
Potential reduce by 86.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 86.0 kB or 81% of the original size.
Potential reduce by 24.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. Gnome Grown Wpengine images are well optimized though.
Potential reduce by 861 B
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 21.8 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 (76%)
59
14
The browser has sent 59 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
760 ms
wp-emoji-release.min.js
38 ms
style.min.css
41 ms
linearicons.css
60 ms
font-awesome.min.css
476 ms
frontend.css
490 ms
gnome-grown-dc-public.css
60 ms
dashicons.min.css
61 ms
uaf.css
425 ms
easy-social-share-buttons.min.css
106 ms
front.min.css
92 ms
js_composer.min.css
126 ms
Defaults.css
101 ms
ultimate.min.css
160 ms
bootstrap.min.css
226 ms
base.min.css
195 ms
style.min.css
224 ms
other.min.css
231 ms
style.css
230 ms
custom-skin.css
239 ms
kvj4ulk.css
259 ms
jquery.min.js
242 ms
jquery-migrate.min.js
244 ms
linearicons.js
242 ms
gnome-grown-dc-public.js
244 ms
rbtools.min.js
246 ms
rs6.min.js
251 ms
ultimate-params.min.js
246 ms
av.js
250 ms
email-decode.min.js
245 ms
css
151 ms
animate.min.css
245 ms
all.min.css
245 ms
rs6.css
250 ms
front.min.js
248 ms
gsap.min.js
248 ms
ScrollToPlugin.min.js
250 ms
ScrollMagic.min.js
254 ms
styles.css
251 ms
animation.gsap.min.js
230 ms
sticky-header.min.js
225 ms
js_composer_front.min.js
218 ms
vc-waypoints.min.js
216 ms
jquery-appear.min.js
217 ms
ultimate_bg.min.js
187 ms
custom.min.js
154 ms
main.min.js
129 ms
p.css
32 ms
whitedown1.png
754 ms
AVlogo.png
79 ms
white-gnome-logo.png
466 ms
dummy.png
80 ms
oregon-cannabis-dispensary.jpg
650 ms
oregon-biodynamic-farm.jpg
650 ms
best-cannabis-strains.jpg
712 ms
Gnome-Grown_Logomark-Horizontal_Light-Gray-.png
80 ms
loading.gif
81 ms
round-prof.png
106 ms
d
76 ms
d
78 ms
d
77 ms
5349Dublin.woff
539 ms
flaticon.woff
427 ms
footer.jpg
536 ms
popup-image.png
1108 ms
fontawesome-webfont.woff
264 ms
AVbg.jpg
73 ms
fa-brands-400.ttf
580 ms
fa-regular-400.ttf
540 ms
fa-solid-900.ttf
749 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
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
gnomegrown.wpengine.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
Image elements do not have [alt] attributes
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 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: