11.6 sec in total
327 ms
11.1 sec
211 ms
Visit telefonica.es now to see the best up-to-date Telefonica content for Spain and also check out these interesting facts you probably never knew about telefonica.es
Visit telefonica.esWe analyzed Telefonica.es page load time and found that the first response time was 327 ms and then it took 11.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
telefonica.es performance score
name
value
score
weighting
Value7.5 s
1/100
10%
Value12.6 s
0/100
25%
Value17.6 s
0/100
10%
Value17,860 ms
0/100
30%
Value0
100/100
15%
Value28.5 s
0/100
10%
327 ms
3339 ms
690 ms
370 ms
363 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 83% of them (90 requests) were addressed to the original Telefonica.es, 3% (3 requests) were made to Telefonica.com and 3% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Telefonica.es.
Page size can be reduced by 3.6 MB (66%)
5.5 MB
1.9 MB
In fact, the total size of Telefonica.es main page is 5.5 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. 55% of websites need less resources to load. Javascripts take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 226.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. This page needs HTML code to be minified as it can gain 78.9 kB, which is 30% 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 226.5 kB or 87% of the original size.
Potential reduce by 126.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. Obviously, Telefonica needs image optimization as it can save up to 126.7 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.9 MB
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 1.9 MB or 72% of the original size.
Potential reduce by 1.4 MB
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. Telefonica.es needs all CSS files to be minified and compressed as it can save up to 1.4 MB or 85% of the original size.
Number of requests can be reduced by 68 (70%)
97
29
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Telefonica. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 41 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
telefonica.es
327 ms
3339 ms
jquery-1.11.1.min.js
690 ms
jquery-ui.structure.css
370 ms
slick.css
363 ms
jquery.mCustomScrollbar.css
504 ms
jquery-ui.js
906 ms
jquery.mmenu.all.css
639 ms
demo.css
709 ms
lightbox.css
714 ms
lightbox.js
930 ms
jquery.mmenu.min.all.js
1124 ms
jquery.cookie.js
997 ms
jquery.cookiecuttr.js
1074 ms
jquery.mapael.js
1086 ms
raphael-min.js
1472 ms
world_countries.js
1494 ms
jquery.orgchart.js
1274 ms
ics.deps.min.js
1292 ms
slick.js
1497 ms
jquery.mCustomScrollbar.concat.min.js
1513 ms
tagcloud.jquery.js
1608 ms
masonry-docs.min.js
1750 ms
sharelinks.js
1816 ms
init.js
1966 ms
main.js
1861 ms
aui.css
2175 ms
main.css
2151 ms
main.css
2072 ms
main.css
2144 ms
main.css
2281 ms
main.css
2395 ms
main.css
2451 ms
barebone.jsp
2931 ms
analytics.min.js
2832 ms
liferay-analytics-api.js
2495 ms
pinit.js
15 ms
widgets.js
440 ms
main.css
2924 ms
liferay-analytics-processor.js
2486 ms
main.js
2626 ms
navigation.js
2432 ms
main.js
2719 ms
main.js
2645 ms
sharesStockExchange.js
2642 ms
main.js
2522 ms
472 ms
721 ms
6d2380da-8ef1-4b90-b19d-fae65f6b3b6d
813 ms
d3c05b5b-5efa-441e-9ba9-2b267112e1da
1370 ms
4d1b702f-53a4-4200-9644-c20e89597711
1444 ms
close.png
222 ms
loading.gif
499 ms
prev.png
497 ms
next.png
497 ms
bg-header.png
720 ms
company_logo
819 ms
logoMovistar.png
622 ms
logoO2.png
821 ms
logoVivo.png
875 ms
dbb54527-dfe7-417c-8120-1b9d181c0d5a
894 ms
2f31e6bc-95d3-41af-807e-9979b5f0f3bf
1165 ms
article
1404 ms
article
1589 ms
ico_link.png
1493 ms
8ca8de53-6c66-4917-a19a-221ebb212ef2
1313 ms
102e810e-2d66-4e35-8c29-c8fdecfd7355
1228 ms
4ad6cad4-3c38-49f3-9357-7b0f1b71329a
1505 ms
4717ce6c-b159-44be-8d0d-dbf5db4e6fb6
1598 ms
twitter_share.png
1641 ms
linkedin_share.png
1722 ms
yammer_share.png
1830 ms
facebook_share.png
1835 ms
google+_share.png
1916 ms
tuenti_share.png
1926 ms
lnk_externo.gif
1984 ms
7719e2f7-591e-4675-b3b4-f2d8061b9909
2057 ms
b0350291-b900-4c76-b729-c73771f7ef09
2198 ms
ce0391b3-b27b-4885-ae43-17a9f863ad9a
2314 ms
ad63617c-1451-458e-a1a0-d82c1e71c86a
2339 ms
gtm.js
215 ms
bgd_buscador.png
2232 ms
ico_lupa01.png
2301 ms
homeBlue.png
2383 ms
edb26472-a7f6-4cd1-9d37-24447aa64298
2815 ms
34af8927-4320-4eb8-bd8c-658365482221
3275 ms
TelefonicaText.woff
2837 ms
7h3GhXrbOdM
176 ms
TelefonicaCAP.otf
2688 ms
analytics.js
43 ms
TelefonicaHeadline-Light.otf
2640 ms
pinit_main.js
38 ms
collect
8 ms
collect
88 ms
www-embed-player-vflZsBgOl.css
27 ms
www-embed-player.js
61 ms
base.js
85 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
63 ms
ad_status.js
51 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
39 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
41 ms
2223 ms
ico_mas_azul.png
2553 ms
bg_cal_down.png
2686 ms
flecha-arriba.png
2560 ms
desplegable.png
2496 ms
available_languages.jsp
496 ms
631 ms
telefonica.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.
telefonica.es best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
telefonica.es SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Telefonica.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 Telefonica.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.
telefonica.es
Open Graph description is not detected on the main page of Telefonica. 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: