Tools & Wizards About Us
radioline.fr screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

radioline.fr

Radioline

Page Load Speed

1.8 sec in total

First Response

250 ms

Resources Loaded

1.3 sec

Page Rendered

206 ms

radioline.fr screenshot

About Website

Visit radioline.fr now to see the best up-to-date Radioline content for Morocco and also check out these interesting facts you probably never knew about radioline.fr

110 000 Radio Stations (FM, AM, Internet) & Podcasts in one place!

Visit radioline.fr

Key Findings

We analyzed Radioline.fr page load time and found that the first response time was 250 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

radioline.fr performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

65/100

10%

LCP (Largest Contentful Paint)

Value24.5 s

0/100

25%

SI (Speed Index)

Value20.0 s

0/100

10%

TBT (Total Blocking Time)

Value9,900 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.225

55/100

15%

TTI (Time to Interactive)

Value34.0 s

0/100

10%

Network Requests Diagram

radioline.fr

250 ms

www.radioline.co

341 ms

en

100 ms

e9c082f1c60b301b.css

166 ms

11bd5b7cb194fbb3.css

174 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Radioline.fr, 81% (22 requests) were made to Radioline.co and 7% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (645 ms) relates to the external source Radioline.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 30.1 kB (31%)

Content Size

98.1 kB

After Optimization

68.0 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Radioline.fr main page is 98.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 64.5 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 22.6 kB

  • Original 28.1 kB
  • After minification 28.1 kB
  • After compression 5.5 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 22.6 kB or 80% of the original size.

Image Optimization

-7%

Potential reduce by 4.2 kB

  • Original 64.5 kB
  • After minification 60.2 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. Radioline images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 3.2 kB

  • Original 5.6 kB
  • After minification 5.6 kB
  • After compression 2.3 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 3.2 kB or 58% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (64%)

Requests Now

22

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

radioline.fr

radioline.fr

250 ms

www.radioline.co

www.radioline.co

341 ms

en

en

100 ms

e9c082f1c60b301b.css

e9c082f1c60b301b.css

166 ms

11bd5b7cb194fbb3.css

11bd5b7cb194fbb3.css

174 ms

29dd8373b07bd422.css

29dd8373b07bd422.css

165 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

287 ms

webpack-54a26b4c7e31989c.js

webpack-54a26b4c7e31989c.js

164 ms

framework-5cb9f477c8eda777.js

framework-5cb9f477c8eda777.js

305 ms

main-9f8c2f4f84d7e3af.js

main-9f8c2f4f84d7e3af.js

329 ms

_app-3a42f34f3be747a1.js

_app-3a42f34f3be747a1.js

645 ms

5675-0d9f5cff670241f8.js

5675-0d9f5cff670241f8.js

303 ms

2962-c4a4c06b0a556270.js

2962-c4a4c06b0a556270.js

308 ms

4357-650c438b82b5e7fc.js

4357-650c438b82b5e7fc.js

352 ms

index-ccc3ab436ea272f3.js

index-ccc3ab436ea272f3.js

353 ms

_buildManifest.js

_buildManifest.js

354 ms

_ssgManifest.js

_ssgManifest.js

354 ms

css2

css2

34 ms

vlyby-player-floating.html

vlyby-player-floating.html

410 ms

attc-3Kx24kdRpatbdYQGN.min.js

attc-3Kx24kdRpatbdYQGN.min.js

433 ms

radioline.png

radioline.png

413 ms

App_Store.png

App_Store.png

415 ms

app_gallery.png

app_gallery.png

420 ms

Google_Play_Store.png

Google_Play_Store.png

419 ms

gradientUpsideDown.jpg

gradientUpsideDown.jpg

322 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

45 ms

KFOlCnqEu92Fr1MmWUlvAw.ttf

KFOlCnqEu92Fr1MmWUlvAw.ttf

45 ms

Accessibility Review

radioline.fr accessibility score

78

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a valid value for its [lang] attribute.

Best Practices

radioline.fr best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

radioline.fr SEO score

93

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

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 Radioline.fr 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 Radioline.fr 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

radioline.fr

Open Graph data is detected on the main page of Radioline. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: