2.3 sec in total
106 ms
1.9 sec
266 ms
Click here to check amazing Local Lily content. Otherwise, check out these important facts you probably never knew about locallily.com
NO GOOD REASON, JUST GOOD TIMES
Visit locallily.comWe analyzed Locallily.com page load time and found that the first response time was 106 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
locallily.com performance score
106 ms
1268 ms
35 ms
39 ms
46 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 77% of them (41 requests) were addressed to the original Locallily.com, 4% (2 requests) were made to Ssl.google-analytics.com and 4% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Locallily.com.
Page size can be reduced by 378.6 kB (8%)
4.6 MB
4.2 MB
In fact, the total size of Locallily.com main page is 4.6 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. 70% of websites need less resources to load. Images take 4.2 MB which makes up the majority of the site volume.
Potential reduce by 36.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. 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 36.6 kB or 77% of the original size.
Potential reduce by 155.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. Local Lily images are well optimized though.
Potential reduce by 157.2 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 157.2 kB or 61% of the original size.
Potential reduce by 29.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. Locallily.com needs all CSS files to be minified and compressed as it can save up to 29.7 kB or 77% of the original size.
Number of requests can be reduced by 22 (46%)
48
26
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Local Lily. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
locallily.com
106 ms
locallily.com
1268 ms
wp-emoji-release.min.js
35 ms
wpfp.css
39 ms
styles.css
46 ms
fball_fbbutton.css
40 ms
css
82 ms
style.css
74 ms
styles.css
44 ms
jquery.js
71 ms
jquery-migrate.min.js
50 ms
wpfp.js
59 ms
fball_connect.js
60 ms
js
160 ms
jquery.bxslider.js
96 ms
jquery.bxslider.css
102 ms
jquery.adrotate.dyngroup.js
116 ms
jquery.adrotate.clicktracker.js
109 ms
jquery.form.min.js
108 ms
scripts.js
100 ms
jquery.infinitescroll.js
99 ms
navigation.js
113 ms
wp-embed.min.js
116 ms
sdk.js
31 ms
ll-logo-navy.png
54 ms
heart.png
55 ms
LookAhead_Blog_Head_March-2016.png
362 ms
Adult-Birthday_Blog_Head_Jan-2016.jpg
93 ms
WholeFoodsSpring2016.png
165 ms
Fairs_And_Festivals.jpg
53 ms
wholefoodsbadge.jpg
63 ms
subscribe.png
92 ms
facebook.jpg
61 ms
Insta.jpg
91 ms
Tourist.jpg
178 ms
Lost_Our_Home.jpg
105 ms
LFA_banner%20ad.jpg
122 ms
LL_banner%20ad.jpg
125 ms
facebook_LL30.jpg
345 ms
twitter_LL30.jpg
346 ms
instagram_LL30.jpg
179 ms
rss_LL30.jpg
358 ms
112 ms
xd_arbiter.php
103 ms
quant.js
95 ms
ga.js
101 ms
k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf
233 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
251 ms
pixel;r=1912867625;a=p-0eEtvfU_vU5Eg;fpan=1;fpa=P0-485617774-1458440639603;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458440639602;tzo=-180;ref=;url=https%3A%2F%2Flocallily.com%2F;ogl=locale.en_US%2Ctype.website%2Ctitle.Locallily%252Ecom%20-%20Good%20Times%20Guide%2Cdescription.Good%20Times%20Guide%2Curl.https%3A%2F%2Flocallily%252Ecom%2Csite_name.Locallily%252Ecom
178 ms
bx_loader.gif
48 ms
controls.png
49 ms
__utm.gif
39 ms
collect
55 ms
locallily.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Locallily.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 Locallily.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.
locallily.com
Open Graph data is detected on the main page of Local Lily. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: