3.1 sec in total
263 ms
2.7 sec
124 ms
Click here to check amazing Yes content for Spain. Otherwise, check out these important facts you probably never knew about yes.fm
Escucha cuando y como quieras los mejores programas de LOS40 - LOS40
Visit yes.fmWe 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 a poor result, as 50% of websites can load faster.
yes.fm performance score
name
value
score
weighting
Value3.1 s
48/100
10%
Value7.0 s
6/100
25%
Value11.3 s
5/100
10%
Value4,720 ms
0/100
30%
Value0.156
74/100
15%
Value30.7 s
0/100
10%
263 ms
1028 ms
465 ms
204 ms
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 size can be reduced by 870.9 kB (26%)
3.3 MB
2.5 MB
In fact, the total size of Yes.fm main page is 3.3 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.
Potential reduce by 32.9 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.
Potential reduce by 66.7 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. Yes images are well optimized though.
Potential reduce by 573.0 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 573.0 kB or 61% of the original size.
Potential reduce by 198.2 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.
Number of requests can be reduced by 38 (49%)
78
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.
yes.fm
263 ms
www.yes.fm
1028 ms
main.css
465 ms
satelliteLib-eba69cb9fc3bdebdedb3cfd25f50d4665b055fe1.js
204 ms
api:client.js
96 ms
ima3.js
27 ms
pbs.slots.js
320 ms
statistics.min.js
499 ms
yesfm.js
881 ms
routing
173 ms
dojo.js
106 ms
jquery.min.js
31 ms
satellite-55fa9b25666337001700054e.js
74 ms
cb=gapi.loaded_0
27 ms
amzn_ads.js
103 ms
gpt.js
39 ms
rta.js
39 ms
postmessageRelay
38 ms
api.js
37 ms
core:rpc:shindig.random:shindig.sha1.js
69 ms
2536007149-postmessagerelay.js
20 ms
bid
30 ms
pubads_impl_81.js
22 ms
container.html
12 ms
admiracion.png
84 ms
20151061845672.jpeg
158 ms
20152760638615.jpeg
126 ms
Viernes-en-la-Oficina.jpg
146 ms
20152762413139.jpeg
123 ms
me-siento-feliz.jpg
145 ms
19dd97b7ba0d832b8f140b43660e9502.png
147 ms
20151631118365.jpeg
125 ms
Musica-Para-Cocinar.jpg
146 ms
8aba7be5f00274c2ac78aa5d01fe0664.png
154 ms
Grandes-exitos-del-pop.jpg
144 ms
20151396374815.jpeg
147 ms
20152662832831.jpeg
146 ms
Infinita-Tristeza.jpg
147 ms
20153069124598.jpeg
146 ms
20151857445740.jpeg
145 ms
20152405939192.jpeg
147 ms
20152594215898.jpeg
147 ms
20152471772574.jpeg
147 ms
1fe513ee4a29255593c1c73cbeb967fb.png
151 ms
20152728981465.jpeg
305 ms
100-Canciones-Inolvidables.jpg
147 ms
lo---escuchado-en-espana.jpg
148 ms
Lo-mas-oido.jpg
149 ms
publicidad.gif
83 ms
logo_prisa_musica.png
78 ms
logo.png
79 ms
iniciar-sesion.png
146 ms
buscar.svg
154 ms
cerrar_resultados.png
157 ms
emisora.png
161 ms
enlaces.png
163 ms
yes.png
164 ms
click_go.png
220 ms
radio_fm.svg
231 ms
favorito.svg
235 ms
play.svg
242 ms
radio_yes.svg
243 ms
paginacion.png
244 ms
publicidad_izq.png
303 ms
player.png
307 ms
mas.png
312 ms
facebook_footer.png
323 ms
twiiter_footer.png
324 ms
instagram_footer.png
326 ms
google_plus_footer.png
384 ms
youtube_footer.png
383 ms
arrow_up.png
387 ms
lato-regular.woff
463 ms
lato-light.woff
547 ms
lato-bold.woff
472 ms
lato-black.woff
513 ms
boton_play.png
444 ms
back_publi_radio2.png
442 ms
siguiente.png
520 ms
volume.png
528 ms
bg-track.png
542 ms
handle.png
552 ms
s-code-contents-4ffb1d866a1126f032be24a2e01661442ae5dcfe.js
87 ms
r2
5 ms
yes.fm accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[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
Some elements have a [tabindex] value greater than 0
yes.fm best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
yes.fm SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
ES
N/A
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.
yes.fm
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: