6.1 sec in total
583 ms
5.4 sec
171 ms
Click here to check amazing Pure Mmj content for United States. Otherwise, check out these important facts you probably never knew about puremmj.com
Visit puremmj.comWe analyzed Puremmj.com page load time and found that the first response time was 583 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
puremmj.com performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value9.1 s
1/100
25%
Value8.8 s
16/100
10%
Value1,160 ms
22/100
30%
Value0.006
100/100
15%
Value14.9 s
8/100
10%
583 ms
24 ms
35 ms
46 ms
193 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 28% of them (25 requests) were addressed to the original Puremmj.com, 38% (33 requests) were made to Maps.googleapis.com and 16% (14 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Puremmj.com.
Page size can be reduced by 1.5 MB (68%)
2.2 MB
693.6 kB
In fact, the total size of Puremmj.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. 60% of websites need less resources to load. Javascripts take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 81.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 81.5 kB or 86% of the original size.
Potential reduce by 8.1 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. Pure Mmj images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 76% of the original size.
Potential reduce by 293.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. Puremmj.com needs all CSS files to be minified and compressed as it can save up to 293.0 kB or 87% of the original size.
Number of requests can be reduced by 41 (57%)
72
31
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pure Mmj. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
puremmj.com
583 ms
css
24 ms
css
35 ms
css
46 ms
formidablepro.css
193 ms
layout.css
200 ms
style.css
346 ms
fontello.css
1533 ms
styles.css
1470 ms
tp_twitter_plugin.css
2580 ms
checkbox.min.css
255 ms
wpgmza_style.css
259 ms
jquery.js
390 ms
jquery-migrate.min.js
324 ms
swfobject.js
388 ms
data_table_front.css
349 ms
jquery.form.min.js
395 ms
scripts.js
394 ms
script.compact.js
607 ms
js
80 ms
ajax-forms.min.js
455 ms
jquery.dataTables.js
571 ms
core.js
525 ms
css
13 ms
NEW_PURE_LOGO_255x85.png
243 ms
PURE_LOGO_255x85_WHITE.png
240 ms
js
41 ms
analytics.js
165 ms
LeFlHvsZjXu2c3ZRgBq9nD8E0i7KZn-EPnyo3HZu7kw.woff
156 ms
PIbvSEyHEdL91QLOQRnZ13hCUOGz7vYGh680lGh-uXM.woff
156 ms
HQXBIwLHsOJCNEQeX9kNz3hCUOGz7vYGh680lGh-uXM.woff
158 ms
Wreg0Be4tcFGM2t6VWytvHl4twXkwp3_u9ZoePkT564.woff
157 ms
eCpfeMZI7q4jLksXVRWPQxsxEYwM7FgeyaSgU71cLG0.woff
156 ms
lJAvZoKA5NttpPc9yc6lPQFhaRv2pGgT5Kf0An0s4MM.woff
155 ms
toadOcfmlt9b38dHJxOBGNbE_oMaV8t2eFeISPpzbdE.woff
154 ms
ODelI1aHBYDBqgeIAH2zlBM0YzuT7MdOe03otPbuUS0.woff
155 ms
toadOcfmlt9b38dHJxOBGJ6-ys_j0H4QL65VLqzI3wI.woff
154 ms
toadOcfmlt9b38dHJxOBGFkQc6VGVFSmCnC_l7QZG60.woff
154 ms
one.ttf
155 ms
common.js
65 ms
map.js
77 ms
util.js
152 ms
geometry.js
84 ms
directions.js
130 ms
2markers.xml
72 ms
3markers.xml
75 ms
4markers.xml
74 ms
collect
77 ms
StaticMapService.GetMapImage
160 ms
StaticMapService.GetMapImage
160 ms
StaticMapService.GetMapImage
345 ms
marker.js
73 ms
infowindow.js
73 ms
onion.js
55 ms
openhand_8_8.cur
141 ms
ViewportInfoService.GetViewportInfo
65 ms
stats.js
85 ms
controls.js
111 ms
ViewportInfoService.GetViewportInfo
79 ms
ViewportInfoService.GetViewportInfo
106 ms
css
238 ms
transparent.png
54 ms
mapcnt6.png
36 ms
vt
158 ms
vt
249 ms
vt
245 ms
vt
175 ms
vt
177 ms
spotlight-poi.png
165 ms
vt
67 ms
vt
68 ms
vt
68 ms
google4.png
94 ms
sv5.png
94 ms
vt
45 ms
vt
33 ms
vt
38 ms
vt
41 ms
vt
45 ms
vt
43 ms
vt
43 ms
tmapctrl.png
35 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
42 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
54 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
54 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
54 ms
tmapctrl4.png
38 ms
AuthenticationService.Authenticate
41 ms
puremmj.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.
puremmj.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
puremmj.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
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 Puremmj.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 Puremmj.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.
puremmj.com
Open Graph description is not detected on the main page of Pure Mmj. 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: