12.7 sec in total
381 ms
12.2 sec
134 ms
Welcome to seiko.es homepage info - get ready to check SEIKO best content for Spain right away, or after learning these important things about seiko.es
Seiko es una de las pocas manufacturas de relojes totalmente integradas en el mundo. Hacemos desde investigación, desarrollo y fabricación de nuestros propios movimientos utilizando tecnología en punt...
Visit seiko.esWe analyzed Seiko.es page load time and found that the first response time was 381 ms and then it took 12.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.
seiko.es performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value10.0 s
0/100
25%
Value12.0 s
4/100
10%
Value1,150 ms
22/100
30%
Value0.038
100/100
15%
Value12.3 s
15/100
10%
381 ms
416 ms
230 ms
226 ms
231 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 90% of them (72 requests) were addressed to the original Seiko.es, 4% (3 requests) were made to Google-analytics.com and 3% (2 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (9.8 sec) belongs to the original domain Seiko.es.
Page size can be reduced by 885.1 kB (14%)
6.4 MB
5.5 MB
In fact, the total size of Seiko.es main page is 6.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. 25% of websites need less resources to load. Images take 5.7 MB which makes up the majority of the site volume.
Potential reduce by 21.4 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 21.4 kB or 77% of the original size.
Potential reduce by 378.5 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. SEIKO images are well optimized though.
Potential reduce by 384.9 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 384.9 kB or 77% of the original size.
Potential reduce by 100.3 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. Seiko.es needs all CSS files to be minified and compressed as it can save up to 100.3 kB or 87% of the original size.
Number of requests can be reduced by 42 (54%)
78
36
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SEIKO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
seiko.es
381 ms
www.seiko.es
416 ms
0_loader_fs.css
230 ms
iview_style.css
226 ms
iview.css
231 ms
0_loader.js
232 ms
raphael-min.js
590 ms
jquery.easing.js
233 ms
iview.js
564 ms
jquery.colorbox.js
461 ms
colorbox.css
349 ms
home.js
353 ms
1x_reset.css
128 ms
2a_tags_fs.css
236 ms
3a_classes_fs.css
590 ms
4a_override_fs.css
248 ms
jquery-1.8.3.js
685 ms
sequence.jquery-min.js
249 ms
styleswitcher.js
141 ms
common.js
141 ms
pulldown.js
142 ms
rollover.js
144 ms
openwin.js
251 ms
jquery.regionselect.js
253 ms
flashwrite.js
254 ms
all.js
7 ms
sociallinks.js
253 ms
123 ms
ci.png
119 ms
cccccc.png
119 ms
bt_collections.png
123 ms
bt_worldofseiko.png
126 ms
bt_stores.png
129 ms
bt_support.png
130 ms
bt_seikotv.png
233 ms
bt_globalsite.png
242 ms
bt_internetpurchasewarning.png
242 ms
icn_facebook.png
252 ms
icn_twitter.png
254 ms
icn_youtube.png
256 ms
icn_pinterest.png
343 ms
icn_flickr.png
352 ms
icn_rss.png
352 ms
tab_whatsnew.png
373 ms
sorteo_prospex.jpg
6119 ms
bg.jpg
2270 ms
bg.png
4274 ms
bg.jpg
2233 ms
bg.png
9751 ms
btn_catalogo_gs_2015.png
561 ms
bg.png
8600 ms
bg.png
9176 ms
bg.png
7399 ms
bg.png
8822 ms
bn_grandseiko.png
7513 ms
bn_astron.png
8640 ms
bn_prospex.png
8673 ms
bn_ttpe.jpg
9183 ms
bn_seiko_boutique.png
9193 ms
bn_whatsnew.png
9238 ms
chr_copyright.png
9251 ms
ga.js
62 ms
xd_arbiter.php
28 ms
xd_arbiter.php
62 ms
ping
56 ms
bg_header.png
9587 ms
mk_close.png
9589 ms
bg_whatsnew.png
9589 ms
__utm.gif
26 ms
__utm.gif
20 ms
mk_arrow_right.png
9524 ms
bg_footer.png
9526 ms
loading.gif
9650 ms
controls.png
9649 ms
icn_facebook_onm.png
120 ms
icn_twitter_onm.png
126 ms
icn_youtube_onm.png
130 ms
icn_pinterest_onm.png
124 ms
icn_flickr_onm.png
123 ms
icn_rss_onm.png
123 ms
seiko.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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
seiko.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
seiko.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 Seiko.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 Seiko.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.
seiko.es
Open Graph description is not detected on the main page of SEIKO. 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: