11.5 sec in total
342 ms
10.5 sec
675 ms
Click here to check amazing Yoigo content. Otherwise, check out these important facts you probably never knew about yoigo.es
Yoigo, tu compañía de internet y telefonía (Fibra Óptica y ADSL) con ofertas de internet para casa, tarifas de móvil y muchos móviles.
Visit yoigo.esWe analyzed Yoigo.es page load time and found that the first response time was 342 ms and then it took 11.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
yoigo.es performance score
name
value
score
weighting
Value3.5 s
33/100
10%
Value14.5 s
0/100
25%
Value8.9 s
15/100
10%
Value3,990 ms
1/100
30%
Value0.001
100/100
15%
Value15.5 s
7/100
10%
342 ms
580 ms
213 ms
227 ms
245 ms
Our browser made a total of 209 requests to load all elements on the main page. We found that 0% of them (1 request) were addressed to the original Yoigo.es, 29% (60 requests) were made to Yoigo.com and 10% (21 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Yoigo.com.
Page size can be reduced by 909.9 kB (40%)
2.3 MB
1.4 MB
In fact, the total size of Yoigo.es main page is 2.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. 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 1.1 MB which makes up the majority of the site volume.
Potential reduce by 113.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 17.4 kB, which is 13% 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 113.9 kB or 84% of the original size.
Potential reduce by 22.8 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. Yoigo images are well optimized though.
Potential reduce by 566.7 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 566.7 kB or 72% of the original size.
Potential reduce by 206.5 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. Yoigo.es needs all CSS files to be minified and compressed as it can save up to 206.5 kB or 86% of the original size.
Number of requests can be reduced by 100 (53%)
188
88
The browser has sent 188 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yoigo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
yoigo.es
342 ms
www.yoigo.com
580 ms
general.css
213 ms
cabecera.css
227 ms
portada.css
245 ms
banner-portada.css
247 ms
portada-tarifas.css
255 ms
moviles-destacados.css
326 ms
pie.css
413 ms
consejero.css
500 ms
jquery-ui.css
508 ms
general.js
488 ms
jquery-all-menu.js
647 ms
consejero-slider.js
954 ms
portada.js
643 ms
include_head.js
717 ms
ga-settings.js
733 ms
wreport.js
659 ms
wbo_performance_rnat_v2.1.js
758 ms
conversion.js
21 ms
adperf_conversion.js
60 ms
cabecera-destacados.css
665 ms
widgets.js
26 ms
j.php
36 ms
gtm.js
152 ms
logo_yoigo_rosa.gif
160 ms
check.gif
142 ms
mosca_rosa.png
329 ms
samsung-galaxy-j5-negro.jpg
433 ms
flecha_boton.gif
331 ms
revista.jpg
434 ms
palomitas.png
433 ms
ico_altavoz_rosa_inact.png
430 ms
pinguino.png
637 ms
disco-dientes.png
838 ms
ico_consejero_llamadas.gif
635 ms
ico_consejero_fotos.gif
634 ms
ico_consejero_mensajes.gif
633 ms
ico_consejero_videos.gif
634 ms
huawei-p8-lite-negro.jpg
921 ms
alcatel-onetouch-pop-3-5-4g-oro.jpg
983 ms
zte-blade-a452-oro.jpg
982 ms
alcatel-onetouch-pixi-3-blanco.jpg
981 ms
spot-atracon-sinfin.jpg
1138 ms
ico_localizacion.gif
1132 ms
ico_tarjetas.gif
1105 ms
PayPal.png
1234 ms
ico_confianza_online.gif
1227 ms
ico_pie_facebook.gif
1234 ms
ico_pie_twitter.gif
1532 ms
ico_pie_gplus.gif
1533 ms
samsung-galaxy-s7-movil.png
1464 ms
descuentooeo-bot-azul.jpg
1452 ms
samsung-j3-rompepistas.png
1955 ms
guitarra.png
1839 ms
ico-4g-wh-ros-osc.gif
1821 ms
ico-4g-trans.png
1816 ms
altavoz-conborde.png
1890 ms
4g-libre.gif
1888 ms
movil-libre.gif
2016 ms
ico_bot_play_1.png
2026 ms
TradeGothicW01Light.woff
2297 ms
TradeGothicW01Bold.woff
2220 ms
TradeGothicW01Bold_2.woff
2032 ms
v.gif
32 ms
ico_bot_cerrar.png
1874 ms
products.js
99 ms
comptage_wreport.fcgi
298 ms
256 ms
analytics.js
216 ms
yoigo-universal24.js
332 ms
0595.js
207 ms
external_all.html
182 ms
comptage_wreport.fcgi
274 ms
zanox.js
450 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
282 ms
327 ms
external_libs.js
140 ms
comptage_wreport.fcgi
271 ms
ec.js
117 ms
comptage_wreport.fcgi
257 ms
dispatch.fcgi
312 ms
s
258 ms
u
282 ms
yoigo-universal24_934_0_0.js
156 ms
jquery-1.11.3.js
257 ms
yoigo-universal24_957_0_1.js
286 ms
external_tracking.fcgi
603 ms
dispatch.fcgi
263 ms
dispatch.fcgi
287 ms
collect
73 ms
collect
181 ms
syndication
201 ms
490055952616275968
198 ms
2916610B4B834B9402D3
460 ms
yoigo-es24.js
394 ms
ga-audiences
58 ms
transp.gif
55 ms
transp.gif
291 ms
transp.gif
290 ms
transp.gif
287 ms
transp.gif
276 ms
weborama.js
412 ms
proxy.jpg
664 ms
1f601.png
620 ms
proxy.jpg
633 ms
proxy.jpg
614 ms
proxy.jpg
616 ms
proxy.jpg
672 ms
proxy.jpg
909 ms
proxy.jpg
687 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
247 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
320 ms
yoigo-es24_933_0_0.js
135 ms
transp.gif
129 ms
13071801.js
124 ms
transp.gif
118 ms
transp.gif
113 ms
mGr5xomM_normal.png
444 ms
G8qQjskT_normal.jpg
453 ms
xt15Cs--_normal.jpg
461 ms
oXw036P-_normal.jpg
461 ms
CdbLgJ0WoAAfuMZ.jpg:small
464 ms
CdRUcAvXEAAU5Bj.jpg:small
465 ms
CcjsSyTXEAIIVIL.jpg:small
498 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
422 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
449 ms
ytc.js
430 ms
793 ms
i.cid
477 ms
get
467 ms
hdmr.sddan.com
465 ms
graphinium_match.php
452 ms
pixel.gif
454 ms
dn_iframe.js
450 ms
transp.gif
76 ms
401736.gif
77 ms
proxy.jpg
59 ms
proxy.jpg
59 ms
proxy.jpg
57 ms
proxy.jpg
55 ms
proxy.jpg
58 ms
proxy.jpg
768 ms
proxy.jpg
55 ms
sp.pl
44 ms
dn.html
204 ms
bat.js
110 ms
pixel
135 ms
dn.js
215 ms
i.match
153 ms
jot.html
113 ms
156 ms
get_delivery_data.php
341 ms
c.aspx
20 ms
c2cmosca_rosa.png
301 ms
15E068844C7985DB6CA2
277 ms
t
174 ms
likebox.php
336 ms
pix.aspx
175 ms
rteasdt.html
649 ms
script_graphinium.php
607 ms
kyEKgjk51ZE.css
115 ms
kTub4bakEmM.css
120 ms
Czh0gDTFcBt.css
112 ms
N-k91nHCZS2.css
142 ms
ZeuPykSxSED.css
124 ms
FAHeNGXgPup.js
154 ms
FJmpeSpHpjS.js
184 ms
0wM5s1Khldu.js
180 ms
1bNoFZUdlYZ.js
180 ms
njO1TPvGzoR.js
180 ms
1QuX41zDRrx.js
196 ms
Oagsvfb4VWi.js
170 ms
m-2AbGY1fWh.js
210 ms
1FCa-btixu2.js
208 ms
t
652 ms
pixel
58 ms
10406804_10152905621312329_3867411544663653952_n.png
301 ms
safe_image.php
284 ms
safe_image.php
269 ms
10411081_10152905621647329_2502420616007429795_n.png
271 ms
12791092_10153985039587329_576199914503854755_n.jpg
304 ms
HEyyDkPknAC.png
248 ms
wL6VQj7Ab77.png
423 ms
s7jcwEQH7Sx.png
250 ms
QDwYpIaRyfG.png
248 ms
K00K-UgnsKu.png
247 ms
retrieve.js
161 ms
pixel
53 ms
setgoogid.aspx
128 ms
retrieve_frame.html
180 ms
I6-MnjEovm5.js
5 ms
pQrUxxo5oQp.js
10 ms
Pug
43 ms
transparent.gif
49 ms
36 ms
tap.php
51 ms
rum
39 ms
44 ms
match
26 ms
setgoogid.aspx
108 ms
retrieve_ec.js
166 ms
rum
35 ms
sd
12 ms
36 ms
33 ms
rs
37 ms
pixtrk.aspx
97 ms
retarget
197 ms
yoigo.es accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
yoigo.es 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
yoigo.es 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
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yoigo.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Yoigo.es 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.
yoigo.es
Open Graph data is detected on the main page of Yoigo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: