9.8 sec in total
2.2 sec
6.8 sec
747 ms
Welcome to lightsandmusic.com homepage info - get ready to check Lightsandmusic best content right away, or after learning these important things about lightsandmusic.com
Visit lightsandmusic.comWe analyzed Lightsandmusic.com page load time and found that the first response time was 2.2 sec and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
lightsandmusic.com performance score
2224 ms
124 ms
26 ms
131 ms
133 ms
Our browser made a total of 151 requests to load all elements on the main page. We found that 67% of them (101 requests) were addressed to the original Lightsandmusic.com, 15% (23 requests) were made to Static.xx.fbcdn.net and 6% (9 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Lightsandmusic.com.
Page size can be reduced by 860.2 kB (41%)
2.1 MB
1.2 MB
In fact, the total size of Lightsandmusic.com main page is 2.1 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. 85% 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.0 MB which makes up the majority of the site volume.
Potential reduce by 102.8 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 14.8 kB, which is 12% 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 102.8 kB or 84% of the original size.
Potential reduce by 60.0 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. Lightsandmusic images are well optimized though.
Potential reduce by 555.4 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 555.4 kB or 72% of the original size.
Potential reduce by 142.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. Lightsandmusic.com needs all CSS files to be minified and compressed as it can save up to 142.0 kB or 86% of the original size.
Number of requests can be reduced by 64 (43%)
148
84
The browser has sent 148 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lightsandmusic. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 48 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
www.lightsandmusic.com
2224 ms
style.css
124 ms
css
26 ms
cardozafacebook.css
131 ms
fbseo-style.css
133 ms
jquery.js
228 ms
jquery.cycle.all.min.js
197 ms
jquery.tools.min.js
145 ms
jquery.color.js
181 ms
jquery.jplayer.min.js
198 ms
effects.js
198 ms
jquery.tweet.js
211 ms
jquery.prettyPhoto.js
250 ms
jquery.tipsy.js
272 ms
jquery.fitvids.js
264 ms
jquery.li-scroller.1.0.js
263 ms
history.js
276 ms
jquery.scrollTo-min.js
301 ms
ajaxify.js
307 ms
soundmanager2.js
400 ms
jquery-ui-1.8.21.custom.min.js
403 ms
playlist.js
349 ms
jquery.cookies.js
343 ms
cardozafacebook.js
374 ms
ajax-page-loader.js
375 ms
reload_code.js
427 ms
multicolor-subscribe-widget.css
436 ms
widgets.js
79 ms
custom.js
381 ms
jquery.form.min.js
369 ms
jquery.infinitescroll.js
448 ms
jquery.easing.js
404 ms
dynamic.to.top.min.js
421 ms
style.css
442 ms
jquery-ui-1.8.21.custom.css
450 ms
sdk.js
55 ms
prettyPhoto.css
412 ms
shortcodes.css
428 ms
ga.js
69 ms
Running%20Woman.gif
87 ms
seamless-jute1-copy.jpg
98 ms
search_icon.png
78 ms
New-Logo42-285x152.png
98 ms
home_icon.png
76 ms
fb.png
76 ms
t.png
123 ms
g.png
114 ms
yt.png
135 ms
rss.png
136 ms
timthumb.php
1852 ms
timthumb.php
562 ms
timthumb.php
378 ms
timthumb.php
714 ms
timthumb.php
699 ms
timthumb.php
825 ms
timthumb.php
825 ms
timthumb.php
963 ms
timthumb.php
964 ms
timthumb.php
963 ms
timthumb.php
962 ms
timthumb.php
962 ms
timthumb.php
1147 ms
timthumb.php
1059 ms
timthumb.php
1569 ms
timthumb.php
1058 ms
timthumb.php
1058 ms
timthumb.php
1266 ms
timthumb.php
1225 ms
timthumb.php
1300 ms
timthumb.php
1536 ms
timthumb.php
1518 ms
timthumb.php
1347 ms
timthumb.php
1383 ms
timthumb.php
1433 ms
timthumb.php
1468 ms
__utm.gif
34 ms
-SXnV4mZjf4oh1IBw13WZw.woff
31 ms
ZzUearZLklGfoL18Ti0GaQ.woff
30 ms
timthumb.php
1457 ms
timthumb.php
1487 ms
timthumb.php
1526 ms
timthumb.php
1542 ms
timthumb.php
1537 ms
timthumb.php
1549 ms
timthumb.php
1548 ms
timthumb.php
1548 ms
timthumb.php
1575 ms
like.php
240 ms
vid-pho.png
1545 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
139 ms
like.php
179 ms
like.php
216 ms
like.php
189 ms
like.php
200 ms
like.php
215 ms
like.php
311 ms
likebox.php
439 ms
like.php
438 ms
qeKvIRsJabD.js
87 ms
LVx-xkvaJ0b.png
187 ms
social_icons.png
1334 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
150 ms
qeKvIRsJabD.js
167 ms
qeKvIRsJabD.js
264 ms
qeKvIRsJabD.js
258 ms
qeKvIRsJabD.js
253 ms
qeKvIRsJabD.js
249 ms
qeKvIRsJabD.js
252 ms
qeKvIRsJabD.js
235 ms
qeKvIRsJabD.js
236 ms
qeKvIRsJabD.js
172 ms
inf-loading-254908730.gif
1189 ms
ebiMDO3r-8l.css
108 ms
jGc-59L_9lo.css
109 ms
q68gy-v_YMF.js
119 ms
FJmpeSpHpjS.js
141 ms
0wM5s1Khldu.js
140 ms
1bNoFZUdlYZ.js
140 ms
qeKvIRsJabD.js
219 ms
qeKvIRsJabD.js
209 ms
player_back.png
1027 ms
logo.png
1036 ms
558067_518322508224825_973964125_n.jpg
299 ms
999780_583226478401094_1660737790_n.jpg
252 ms
12512394_604042846414335_7915581511952845865_n.jpg
250 ms
12321390_967819019961766_5681891502083448945_n.jpg
247 ms
12369000_10101267346898717_2281077092060598611_n.jpg
250 ms
12715521_911799218918245_5342797337383987766_n.jpg
248 ms
12642498_2769430191325_6264382582846508059_n.jpg
246 ms
12510362_10204553721278113_7287677018196002675_n.jpg
250 ms
wL6VQj7Ab77.png
239 ms
s7jcwEQH7Sx.png
146 ms
sound.png
949 ms
box.png
876 ms
mute.png
827 ms
pre2.png
865 ms
play3.png
876 ms
next2.png
877 ms
shuffle_false.png
879 ms
download.png
788 ms
arrow.png
860 ms
ti_icon.png
861 ms
I6-MnjEovm5.js
11 ms
pQrUxxo5oQp.js
10 ms
fac_icon.png
778 ms
jot.html
28 ms
go_icon.png
698 ms
play_button.png
654 ms
playlist-back.png
636 ms
slide_cap.png
632 ms
ui-bg_glass_100_f6f6f6_1x400.png
585 ms
lightsandmusic.com SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lightsandmusic.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Lightsandmusic.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.
lightsandmusic.com
Open Graph description is not detected on the main page of Lightsandmusic. 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: