3.8 sec in total
424 ms
3.2 sec
159 ms
Visit flagshipstore.telefonica.es now to see the best up-to-date Flagshipstore Telefonica content for Spain and also check out these interesting facts you probably never knew about flagshipstore.telefonica.es
Movistar Gran Vía 28, en Madrid. Vive experiencias únicas en un espacio que es mucho más que una tienda Movistar.
Visit flagshipstore.telefonica.esWe analyzed Flagshipstore.telefonica.es page load time and found that the first response time was 424 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
flagshipstore.telefonica.es performance score
name
value
score
weighting
Value2.2 s
78/100
10%
Value6.7 s
8/100
25%
Value3.9 s
83/100
10%
Value40 ms
100/100
30%
Value0.152
75/100
15%
Value3.5 s
92/100
10%
424 ms
252 ms
330 ms
671 ms
453 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 74% of them (54 requests) were addressed to the original Flagshipstore.telefonica.es, 10% (7 requests) were made to Calendar.google.com and 5% (4 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Flagshipstore.telefonica.es.
Page size can be reduced by 710.4 kB (56%)
1.3 MB
553.8 kB
In fact, the total size of Flagshipstore.telefonica.es main page is 1.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. 35% of websites need less resources to load. Javascripts take 689.4 kB which makes up the majority of the site volume.
Potential reduce by 26.7 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 6.1 kB, which is 18% 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 26.7 kB or 79% of the original size.
Potential reduce by 4.4 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. Flagshipstore Telefonica images are well optimized though.
Potential reduce by 454.2 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 454.2 kB or 66% of the original size.
Potential reduce by 225.1 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. Flagshipstore.telefonica.es needs all CSS files to be minified and compressed as it can save up to 225.1 kB or 81% of the original size.
Number of requests can be reduced by 54 (75%)
72
18
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Flagshipstore 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 42 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
flagshipstore.telefonica.es
424 ms
252 ms
package-sf.css
330 ms
package-sf.js
671 ms
StorefrontStyle_33.css
453 ms
style-ie.css
221 ms
ico_s_basket.png
214 ms
es-ES.js
212 ms
EUR.js
251 ms
string.js
595 ms
browser.js
252 ms
scope.js
409 ms
json.js
408 ms
base64.js
412 ms
inject-sec-token.js
425 ms
cookie.js
459 ms
button.js
591 ms
draggable.js
600 ms
resizable.js
610 ms
$pub.js
611 ms
class.js
630 ms
mime.js
763 ms
$dict.js
826 ms
core.js
823 ms
support.js
821 ms
$tmpl.js
821 ms
load.js
845 ms
touch.js
970 ms
version.js
1022 ms
validate.js
1030 ms
storage.js
1051 ms
de_epages.js
1031 ms
ico_s_search.png
1061 ms
Cabecera.png
1277 ms
bgr_top_button_active.png
1248 ms
bgr_top_button_floatin_active.png
1245 ms
bgr_top_button.png
1254 ms
bgr_top_button_floatin.png
1259 ms
imagenes_lectura_digital_cuadrado_h.png
1364 ms
xspain_1000x1000_h.jpg
1298 ms
MotoGP1000x1000_h.jpg
1303 ms
MotoGP1000x1000.jpg
1841 ms
embed
301 ms
bgr_right_boxbody_floatin.png
1295 ms
bgr_right_boxbody.png
1315 ms
analytics.js
36 ms
megamenu.js
1460 ms
$ready.js
1480 ms
collect
12 ms
cookiemessage.js
1319 ms
energylabel.js
1334 ms
utf8.js
1351 ms
f7e12ba16863d79ebc50b5ad512d0dd5embedcompiled_fastui.css
23 ms
f7e12ba16863d79ebc50b5ad512d0dd5embedcompiled__en.js
54 ms
client.js
109 ms
cb=gapi.loaded_0
39 ms
postmessageRelay
35 ms
api.js
36 ms
core:rpc:shindig.random:shindig.sha1.js
60 ms
2536007149-postmessagerelay.js
57 ms
logo-plus.png
41 ms
googlelogo_color_46x16dp.png
69 ms
proxy.html
75 ms
blank.gif
35 ms
menu_arrow_open.gif
33 ms
combined_v22.png
44 ms
dict.es.json
1068 ms
cb=gapi.loaded_0
11 ms
events
138 ms
masonry.js
253 ms
simpledialog.js
226 ms
contentslider.js
217 ms
cycle.js
109 ms
flagshipstore.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.
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
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.
flagshipstore.telefonica.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
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
flagshipstore.telefonica.es SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
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 Flagshipstore.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 Flagshipstore.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.
flagshipstore.telefonica.es
Open Graph description is not detected on the main page of Flagshipstore 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: