Tools & Wizards About Us
lovefm.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

lovefm.com

Love FM Belize News & Music Power – Latest Belize News Updates & Belize Radio Station Live Streaming

Page Load Speed

3.8 sec in total

First Response

883 ms

Resources Loaded

2.6 sec

Page Rendered

323 ms

lovefm.com screenshot

About Website

Visit lovefm.com now to see the best up-to-date Love FM content for Belize and also check out these interesting facts you probably never knew about lovefm.com

Visit lovefm.com

Key Findings

We analyzed Lovefm.com page load time and found that the first response time was 883 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

lovefm.com performance score

0

Network Requests Diagram

lovefm.com

883 ms

style.css

74 ms

wp-forecast-default.css

87 ms

bwp-recent-comments.css

88 ms

gallery-bank.css

93 ms

Our browser made a total of 102 requests to load all elements on the main page. We found that 67% of them (68 requests) were addressed to the original Lovefm.com, 20% (20 requests) were made to Static.xx.fbcdn.net and 9% (9 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (883 ms) belongs to the original domain Lovefm.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 560.6 kB (25%)

Content Size

2.2 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lovefm.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. 55% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 43.9 kB

  • Original 53.9 kB
  • After minification 50.7 kB
  • After compression 10.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 43.9 kB or 82% of the original size.

Image Optimization

-7%

Potential reduce by 115.6 kB

  • Original 1.6 MB
  • After minification 1.5 MB

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. Love FM images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 293.0 kB

  • Original 392.1 kB
  • After minification 321.1 kB
  • After compression 99.1 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 293.0 kB or 75% of the original size.

CSS Optimization

-70%

Potential reduce by 108.0 kB

  • Original 154.4 kB
  • After minification 125.2 kB
  • After compression 46.4 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. Lovefm.com needs all CSS files to be minified and compressed as it can save up to 108.0 kB or 70% of the original size.

Requests Breakdown

Number of requests can be reduced by 62 (62%)

Requests Now

100

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Love FM. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

lovefm.com

lovefm.com

883 ms

style.css

style.css

74 ms

wp-forecast-default.css

wp-forecast-default.css

87 ms

bwp-recent-comments.css

bwp-recent-comments.css

88 ms

gallery-bank.css

gallery-bank.css

93 ms

prettyPhoto.css

prettyPhoto.css

92 ms

style.css

style.css

85 ms

dashicons.min.css

dashicons.min.css

162 ms

desktop_style.css

desktop_style.css

132 ms

styles.css

styles.css

129 ms

magnific-popup.min.css

magnific-popup.min.css

142 ms

youtube-channel.css

youtube-channel.css

130 ms

lazyest-style.css

lazyest-style.css

171 ms

_slideshow.css

_slideshow.css

210 ms

_ajax.css

_ajax.css

182 ms

jquery.js

jquery.js

291 ms

jquery-migrate.min.js

jquery-migrate.min.js

213 ms

jquery.masonry.min.js

jquery.masonry.min.js

218 ms

isotope.pkgd.js

isotope.pkgd.js

252 ms

imgLiquid.js

imgLiquid.js

245 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

248 ms

wpf_update.js

wpf_update.js

248 ms

front_end_script.js

front_end_script.js

270 ms

jquery.flexslider.js

jquery.flexslider.js

288 ms

jquery.elastislide.js

jquery.elastislide.js

284 ms

scripts.js

scripts.js

297 ms

ticker.js

ticker.js

288 ms

respond.min.js

respond.min.js

309 ms

reset.css

reset.css

302 ms

flexslider.css

flexslider.css

300 ms

css

css

23 ms

colorbox-4.css

colorbox-4.css

256 ms

jquery.form.min.js

jquery.form.min.js

257 ms

scripts.js

scripts.js

259 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

260 ms

lazyest-gallery.js

lazyest-gallery.js

259 ms

wp-embed.min.js

wp-embed.min.js

260 ms

custom.js

custom.js

260 ms

jquery.colorbox.js

jquery.colorbox.js

258 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

86 ms

BG2.png

BG2.png

404 ms

search-icon.png

search-icon.png

189 ms

light-bg.png

light-bg.png

190 ms

Lovefm-header_logo.png

Lovefm-header_logo.png

318 ms

lovefm-logo2.png

lovefm-logo2.png

204 ms

latest.png

latest.png

191 ms

nav-bg.png

nav-bg.png

202 ms

mobi-bg.png

mobi-bg.png

202 ms

Ma-Jing-yeou.jpg

Ma-Jing-yeou.jpg

261 ms

default610.jpg

default610.jpg

302 ms

ow-town-hall.jpg

ow-town-hall.jpg

340 ms

Black-March-2016.jpg

Black-March-2016.jpg

336 ms

heading-bg.gif

heading-bg.gif

304 ms

Ma-Jing-yeou-145x95.jpg

Ma-Jing-yeou-145x95.jpg

344 ms

default145.jpg

default145.jpg

341 ms

ow-town-hall-145x95.jpg

ow-town-hall-145x95.jpg

366 ms

Black-March-2016-145x95.jpg

Black-March-2016-145x95.jpg

379 ms

Guatemala-Belize-145x95.jpg

Guatemala-Belize-145x95.jpg

397 ms

David-Jones-5-145x95.jpg

David-Jones-5-145x95.jpg

433 ms

DPM-Vega-300x197.jpg

DPM-Vega-300x197.jpg

423 ms

Mario-Trotman-body-found-300x197.jpg

Mario-Trotman-body-found-300x197.jpg

459 ms

love-fm-web-banner1.png

love-fm-web-banner1.png

441 ms

38.gif

38.gif

436 ms

17.gif

17.gif

439 ms

18.gif

18.gif

460 ms

social-but.png

social-but.png

481 ms

gk5FxslNkTTHtojXrkp-xJhsE6jcpsD2oq89kgohWx0.ttf

gk5FxslNkTTHtojXrkp-xJhsE6jcpsD2oq89kgohWx0.ttf

151 ms

plusone.js

plusone.js

178 ms

nav-arrows2.png

nav-arrows2.png

299 ms

likebox.php

likebox.php

373 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

6 ms

McLpmVM3wCm.css

McLpmVM3wCm.css

180 ms

VH4VPudaxfN.css

VH4VPudaxfN.css

224 ms

6JjmkAGJU83.css

6JjmkAGJU83.css

263 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

376 ms

FJmpeSpHpjS.js

FJmpeSpHpjS.js

395 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

300 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

303 ms

OloiM1PZafe.js

OloiM1PZafe.js

302 ms

LTv6ZK-5zxz.js

LTv6ZK-5zxz.js

417 ms

1FCa-btixu2.js

1FCa-btixu2.js

410 ms

Oagsvfb4VWi.js

Oagsvfb4VWi.js

410 ms

pObvZSrFc_4.js

pObvZSrFc_4.js

409 ms

Kt4tkgSRvHH.js

Kt4tkgSRvHH.js

415 ms

H3EKDTObx05.js

H3EKDTObx05.js

454 ms

eR-qA8bp1RM.js

eR-qA8bp1RM.js

456 ms

11988564_433840676821808_6288816732937107674_n.jpg

11988564_433840676821808_6288816732937107674_n.jpg

210 ms

181237_114263192112893_1780219239_n.jpg

181237_114263192112893_1780219239_n.jpg

248 ms

1425534_1024732374267229_9083389709260386300_n.jpg

1425534_1024732374267229_9083389709260386300_n.jpg

322 ms

1471172_174379772941525_4531509478518580463_n.jpg

1471172_174379772941525_4531509478518580463_n.jpg

326 ms

12798982_545870238915305_1442513386357772764_n.jpg

12798982_545870238915305_1442513386357772764_n.jpg

329 ms

10363795_927763300623067_6873215543455454659_n.jpg

10363795_927763300623067_6873215543455454659_n.jpg

334 ms

11173353_803331929758805_7864701272761754316_n.jpg

11173353_803331929758805_7864701272761754316_n.jpg

330 ms

12540920_1670814433179770_304263150158685907_n.jpg

12540920_1670814433179770_304263150158685907_n.jpg

332 ms

12814759_1577242615900159_6166071830565441347_n.jpg

12814759_1577242615900159_6166071830565441347_n.jpg

363 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

96 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

97 ms

gxbPuQdXIZP.png

gxbPuQdXIZP.png

41 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

42 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

79 ms

featured-bg.png

featured-bg.png

41 ms

bg_control_nav.png

bg_control_nav.png

54 ms

SEO Factors

lovefm.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lovefm.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 Lovefm.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.

Social Sharing Optimization

lovefm.com

Open Graph description is not detected on the main page of Love FM. 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: