Report Summary

  • 18

    Performance

    Renders faster than
    35% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

yes.fm

Escucha LOS40 en directo - Todos Los Éxitos

Page Load Speed

3.1 sec in total

First Response

263 ms

Resources Loaded

2.7 sec

Page Rendered

124 ms

yes.fm screenshot

About Website

Click here to check amazing Yes content for Spain. Otherwise, check out these important facts you probably never knew about yes.fm

LOS40 en directo, la emisora de radio musical más escuchada del país. ¡Disfruta de las principales canciones, la Lista y los programas más divertidos.

Visit yes.fm

Key Findings

We analyzed Yes.fm page load time and found that the first response time was 263 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

yes.fm performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

48/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value11.3 s

5/100

10%

TBT (Total Blocking Time)

Value4,720 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.156

74/100

15%

TTI (Time to Interactive)

Value30.7 s

0/100

10%

Network Requests Diagram

yes.fm

263 ms

www.yes.fm

1028 ms

main.css

465 ms

satelliteLib-eba69cb9fc3bdebdedb3cfd25f50d4665b055fe1.js

204 ms

api:client.js

96 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 48% of them (40 requests) were addressed to the original Yes.fm, 27% (23 requests) were made to Cdncf.yes.fm and 4% (3 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Yes.fm.

Page Optimization Overview & Recommendations

Page size can be reduced by 980.3 kB (29%)

Content Size

3.4 MB

After Optimization

2.4 MB

In fact, the total size of Yes.fm main page is 3.4 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. 75% 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 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 32.9 kB

  • Original 41.1 kB
  • After minification 32.9 kB
  • After compression 8.2 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 8.2 kB, which is 20% 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 32.9 kB or 80% of the original size.

Image Optimization

-3%

Potential reduce by 66.7 kB

  • Original 2.1 MB
  • After minification 2.0 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. Yes images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 682.5 kB

  • Original 967.1 kB
  • After minification 883.6 kB
  • After compression 284.6 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 682.5 kB or 71% of the original size.

CSS Optimization

-83%

Potential reduce by 198.2 kB

  • Original 240.0 kB
  • After minification 229.4 kB
  • After compression 41.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. Yes.fm needs all CSS files to be minified and compressed as it can save up to 198.2 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (49%)

Requests Now

78

After Optimization

40

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

Accessibility Review

yes.fm accessibility score

74

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

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

yes.fm 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

High

Page has valid source maps

SEO Factors

yes.fm SEO score

84

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    ES

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yes.fm can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Yes.fm 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

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