6.4 sec in total
1.6 sec
3.9 sec
939 ms
Visit leafly.es now to see the best up-to-date Leafly content for Mexico and also check out these interesting facts you probably never knew about leafly.es
Visit leafly.esWe analyzed Leafly.es page load time and found that the first response time was 1.6 sec and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
leafly.es performance score
1552 ms
142 ms
16 ms
11 ms
29 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 7% of them (6 requests) were addressed to the original Leafly.es, 26% (22 requests) were made to D3h17ltqi8v019.cloudfront.net and 8% (7 requests) were made to Use.typekit.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Cdn.goroost.com.
Page size can be reduced by 1.1 MB (30%)
3.5 MB
2.5 MB
In fact, the total size of Leafly.es main page is 3.5 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 2.2 MB which makes up the majority of the site volume.
Potential reduce by 136.6 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. This page needs HTML code to be minified as it can gain 23.0 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 136.6 kB or 83% of the original size.
Potential reduce by 130.7 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. Leafly images are well optimized though.
Potential reduce by 543.5 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 543.5 kB or 63% of the original size.
Potential reduce by 243.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. Leafly.es needs all CSS files to be minified and compressed as it can save up to 243.8 kB or 84% of the original size.
Number of requests can be reduced by 36 (47%)
76
40
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Leafly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.leafly.es
1552 ms
jxt3mrq.js
142 ms
leaflycss
16 ms
flexboxgrid.min.css
11 ms
global-css
29 ms
1374371252.js
179 ms
platform.js
114 ms
xqoubu2vdg7fcxkp1qt4rmerl2lg23ij
1800 ms
libsjs
22 ms
global-js
22 ms
leaflyjs
35 ms
conversion.js
34 ms
www.leafly.es
131 ms
ados.js
116 ms
az8RtgcG8PK6bFQR_JaBbSF6TvCP5CDbwQOBwONMx99ffV_VMUMdeMJ6Mk6fw6NuSh90iY83ZAlTifoRdhXtM3.woff
62 ms
JfSSg2_aJzxfqyRALnf8PwqPlWdmMIUX55di_dDuvbvffJ2bMUMdeMJ6Mk6fw6NuSh90iY83ZAlTifoRdhXtMb.woff
136 ms
ozJyr_a4mb17uqoViAHByVnuPveB5AyPaEAbTm232JSffJVbMUMdeMJ6Mk6fw6NuSh90iY83ZAlTifoRdhXtgb.woff
881 ms
MB6NIrYxvBsMQMItcx2jug2nd9IWSvuiuKqdIdCuQL3ffJWbMUMdeMJ6Mk6fw6NuSh90iY83ZAlTifoRdhXtg3.woff
1228 ms
VmGQLCoWvmwBbjWfWmSil_ov2bWYq7gRdbt7PQhZohCffJLbMUMdeMJ6Mk6fw6NuSh90iY83ZAlTifoRdhXtfb.woff
1226 ms
crop
599 ms
mqdefault.jpg
1207 ms
app-store-btn@2x.png
109 ms
goog-play-btn@2x.png
836 ms
mqdefault.jpg
1407 ms
mqdefault.jpg
1438 ms
crop
1123 ms
crop
1121 ms
crop
1121 ms
crop
1404 ms
crop
1183 ms
pad
1183 ms
w120
1183 ms
w120
1183 ms
w120
1193 ms
gtm.js
1194 ms
ados
1167 ms
leafly-logo-dark.png
80 ms
home-dispensaries-tall.png
1168 ms
home-news-tall.png
1166 ms
home-strains-tall.png
1167 ms
IGrwTRy3hQo
1364 ms
QlFOatWMxkE
1437 ms
eyywB2x8QSA
1595 ms
headache.jpg
1354 ms
leafly.woff
955 ms
svg-download-apple.svg
952 ms
svg-download-google.svg
1024 ms
www-widgetapi.js
882 ms
mixpanel-2.2.min.js
548 ms
v1.js
761 ms
cb=gapi.loaded_0
442 ms
cb=gapi.loaded_1
454 ms
subscribe_embed
976 ms
7341.js
427 ms
p.gif
751 ms
ip
350 ms
icon-star-filled.svg
145 ms
icon-star-empty.svg
293 ms
123 ms
analytics.js
102 ms
_biz-a.js
160 ms
postmessageRelay
161 ms
s
113 ms
u
131 ms
pageconfig
98 ms
b2c17d50538a48a2882e9dccbca57f84.jpg
57 ms
i.gif
67 ms
8897ee14801440b0bbaf542e43e8b045.png
54 ms
i.gif
84 ms
IGrwTRy3hQo
274 ms
collect
21 ms
collect
255 ms
www-embed-player-vflQrT_sR.css
55 ms
www-embed-player.js
131 ms
api.js
122 ms
core:rpc:shindig.random:shindig.sha1.js
216 ms
2536007149-postmessagerelay.js
208 ms
pageview
78 ms
SURBVAjXY2BgYGBUEgCSDEx3FUCUyd0AIJneGbWBQUizPQHI1r1iwICgtq4ECwKV9ED0mUD0MYH1MXBHbQAATRQO8Wsew14AAAAASUVORK5CYII=
50 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
140 ms
ad_status.js
138 ms
www-subscribe-embed-vflWJjAep.css
52 ms
www-subscribe-embed.js
70 ms
ga-audiences
109 ms
www-hitchhiker-vfluKv9vH.png
88 ms
cb=gapi.loaded_0
63 ms
leafly.es SEO score
EN
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Leafly.es can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Spanish language. Our system also found out that Leafly.es 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.
leafly.es
Open Graph description is not detected on the main page of Leafly. 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: