Tools & Wizards About Us
frequencemagic.com screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

frequencemagic.com

FREQUENCE MAGIC, LA WEBRADIO N°1 MADE IN LIMOUSIN, LIMOGES ET NOUVELLE-AQUITAINE

Page Load Speed

5.5 sec in total

First Response

314 ms

Resources Loaded

4.8 sec

Page Rendered

371 ms

frequencemagic.com screenshot

About Website

Visit frequencemagic.com now to see the best up-to-date FREQUENCE MAGIC content and also check out these interesting facts you probably never knew about frequencemagic.com

FREQUENCE MAGIC: Bien plus qu'une webradio... c'est la bande originale de vos journées. Derniers hits, découvertes musicales, infos, chroniques exclusives et cadeaux: osez la différence ! Bienvenue su...

Visit frequencemagic.com

Key Findings

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

Performance Metrics

frequencemagic.com performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value24.9 s

0/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0.2

62/100

15%

TTI (Time to Interactive)

Value5.5 s

70/100

10%

Network Requests Diagram

frequencemagic.com

314 ms

bootstrap.css

287 ms

font-awesome.css

188 ms

flexslider.css

187 ms

style.css

193 ms

Our browser made a total of 116 requests to load all elements on the main page. We found that 65% of them (75 requests) were addressed to the original Frequencemagic.com, 17% (20 requests) were made to Static.xx.fbcdn.net and 6% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Frequencemagic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 401.0 kB (8%)

Content Size

4.9 MB

After Optimization

4.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Frequencemagic.com main page is 4.9 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 4.7 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 47.6 kB

  • Original 56.1 kB
  • After minification 41.5 kB
  • After compression 8.4 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.6 kB, which is 26% 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 47.6 kB or 85% of the original size.

Image Optimization

-7%

Potential reduce by 334.4 kB

  • Original 4.7 MB
  • After minification 4.4 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. FREQUENCE MAGIC images are well optimized though.

JavaScript Optimization

-18%

Potential reduce by 16.5 kB

  • Original 90.2 kB
  • After minification 88.8 kB
  • After compression 73.8 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 16.5 kB or 18% of the original size.

CSS Optimization

-8%

Potential reduce by 2.5 kB

  • Original 30.5 kB
  • After minification 30.5 kB
  • After compression 28.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. Frequencemagic.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 48 (44%)

Requests Now

108

After Optimization

60

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

frequencemagic.com

frequencemagic.com

314 ms

bootstrap.css

bootstrap.css

287 ms

font-awesome.css

font-awesome.css

188 ms

flexslider.css

flexslider.css

187 ms

style.css

style.css

193 ms

jquery.js

jquery.js

281 ms

jquery-migrate-1.2.1.min.js

jquery-migrate-1.2.1.min.js

190 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

368 ms

superfish.js

superfish.js

369 ms

jquery.jrumble.1.3.min.js

jquery.jrumble.1.3.min.js

369 ms

jquery.flexslider.js

jquery.flexslider.js

374 ms

jquery-scroller-v1.min.js

jquery-scroller-v1.min.js

461 ms

jquery.caroufredsel.js

jquery.caroufredsel.js

1068 ms

jquery.touchSwipe.min.js

jquery.touchSwipe.min.js

987 ms

jquery.ui.totop.js

jquery.ui.totop.js

988 ms

jquery.equalheights.js

jquery.equalheights.js

989 ms

script.js

script.js

989 ms

sdk.js

sdk.js

15 ms

counter.js

counter.js

448 ms

bootstrap.min.js

bootstrap.min.js

989 ms

streaminfo.js

streaminfo.js

309 ms

css

css

18 ms

css

css

31 ms

btn_donateCC_LG.gif

btn_donateCC_LG.gif

201 ms

logo.png

logo.png

278 ms

rs1.png

rs1.png

207 ms

rs2.png

rs2.png

208 ms

rs3.png

rs3.png

209 ms

rs4.png

rs4.png

210 ms

logoplay.png

logoplay.png

209 ms

slideA.jpg

slideA.jpg

724 ms

slideB.jpg

slideB.jpg

726 ms

slideC.jpg

slideC.jpg

729 ms

slideD.jpg

slideD.jpg

730 ms

slideE.jpg

slideE.jpg

726 ms

slideF.jpg

slideF.jpg

724 ms

slideG.jpg

slideG.jpg

1260 ms

bannerA.jpg

bannerA.jpg

1086 ms

bannerB.jpg

bannerB.jpg

1085 ms

bannerC.jpg

bannerC.jpg

1086 ms

progA.jpg

progA.jpg

1088 ms

progB.jpg

progB.jpg

1087 ms

progC.jpg

progC.jpg

1444 ms

progD.jpg

progD.jpg

1443 ms

progE.jpg

progE.jpg

1446 ms

progF.jpg

progF.jpg

1445 ms

progG.jpg

progG.jpg

1357 ms

progH.jpg

progH.jpg

1617 ms

progI.jpg

progI.jpg

1714 ms

progJ.jpg

progJ.jpg

1804 ms

progK.jpg

progK.jpg

1804 ms

progL.jpg

progL.jpg

1803 ms

bannerAA.jpg

bannerAA.jpg

1804 ms

bannerEE.jpg

bannerEE.jpg

1975 ms

bannerCC.jpg

bannerCC.jpg

2071 ms

bannerDD.jpg

bannerDD.jpg

2163 ms

bannerBB.jpg

bannerBB.jpg

2163 ms

bannerFF.jpg

bannerFF.jpg

2164 ms

home01.jpg

home01.jpg

2075 ms

pixel.gif

pixel.gif

193 ms

home02.jpg

home02.jpg

2242 ms

sdk.js

sdk.js

189 ms

4iCs6KVjbNBYlgoKfw7z.ttf

4iCs6KVjbNBYlgoKfw7z.ttf

152 ms

4iCv6KVjbNBYlgoCjC3jsGyI.ttf

4iCv6KVjbNBYlgoCjC3jsGyI.ttf

153 ms

4iCv6KVjbNBYlgoC1CzjsGyI.ttf

4iCv6KVjbNBYlgoC1CzjsGyI.ttf

154 ms

4iCv6KVjbNBYlgoCxCvjsGyI.ttf

4iCv6KVjbNBYlgoCxCvjsGyI.ttf

155 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf

119 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYA.ttf

121 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf

118 ms

counter.php

counter.php

477 ms

pointeur.gif

pointeur.gif

343 ms

home03.jpg

home03.jpg

2140 ms

home04.jpg

home04.jpg

2145 ms

home05.jpg

home05.jpg

2251 ms

home06.jpg

home06.jpg

2251 ms

31 ms

logosacem.png

logosacem.png

2376 ms

top1.jpg

top1.jpg

2156 ms

marker0.png

marker0.png

1805 ms

px1.png

px1.png

1811 ms

px2.png

px2.png

1887 ms

wave1.png

wave1.png

2181 ms

mic1.png

mic1.png

2266 ms

mic2.png

mic2.png

2333 ms

vl1.png

vl1.png

1628 ms

corner1_dark.png

corner1_dark.png

1706 ms

btn1.png

btn1.png

1730 ms

corner1_light.png

corner1_light.png

1806 ms

li_st0.png

li_st0.png

1885 ms

vl3.png

vl3.png

1737 ms

totop.gif

totop.gif

1714 ms

prev.png

prev.png

280 ms

next.png

next.png

281 ms

page.php

page.php

96 ms

sZdzC0E8mxC.css

sZdzC0E8mxC.css

28 ms

_2VhZS3Kxb6.css

_2VhZS3Kxb6.css

33 ms

5Pl3zEpBQpl.css

5Pl3zEpBQpl.css

30 ms

BFVUlNP835L.js

BFVUlNP835L.js

38 ms

BECqV_OB-Tv.js

BECqV_OB-Tv.js

35 ms

teTZ2tZqwkq.js

teTZ2tZqwkq.js

71 ms

XC4Un5GdVZt.js

XC4Un5GdVZt.js

35 ms

p55HfXW__mM.js

p55HfXW__mM.js

35 ms

e7Tp58KLYmo.js

e7Tp58KLYmo.js

73 ms

q4SZVAjzsaO.js

q4SZVAjzsaO.js

75 ms

cMurRu-0m07.js

cMurRu-0m07.js

79 ms

rMzNGFrxoTb.js

rMzNGFrxoTb.js

93 ms

pVjo_zNwXCB.js

pVjo_zNwXCB.js

76 ms

JVpNdAH_hLQ.js

JVpNdAH_hLQ.js

91 ms

HkvD17iqK-X.js

HkvD17iqK-X.js

76 ms

Glmz_lYOBT1.js

Glmz_lYOBT1.js

89 ms

HzxD9aAXSyD.js

HzxD9aAXSyD.js

90 ms

373535374_778290670965973_2045590995896737008_n.jpg

373535374_778290670965973_2045590995896737008_n.jpg

87 ms

302130103_491415866320123_6627494022868309723_n.jpg

302130103_491415866320123_6627494022868309723_n.jpg

93 ms

kCwDvxe1QsQ.js

kCwDvxe1QsQ.js

22 ms

44y2ROYOC9X.js

44y2ROYOC9X.js

24 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

22 ms

Accessibility Review

frequencemagic.com accessibility score

80

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

frequencemagic.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

frequencemagic.com SEO score

90

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Frequencemagic.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 Frequencemagic.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

frequencemagic.com

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