5.7 sec in total
502 ms
4.7 sec
516 ms
Visit chrono12.de now to see the best up-to-date Chrono12 content for Romania and also check out these interesting facts you probably never knew about chrono12.de
WATCHES
Visit chrono12.deWe analyzed Chrono12.de page load time and found that the first response time was 502 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
chrono12.de performance score
name
value
score
weighting
Value4.0 s
22/100
10%
Value11.4 s
0/100
25%
Value8.5 s
18/100
10%
Value1,430 ms
15/100
30%
Value0.348
32/100
15%
Value19.5 s
2/100
10%
502 ms
1059 ms
244 ms
34 ms
20 ms
Our browser made a total of 129 requests to load all elements on the main page. We found that 83% of them (107 requests) were addressed to the original Chrono12.de, 2% (2 requests) were made to Secure2.plationline.ro and 2% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Chrono12.de.
Page size can be reduced by 273.4 kB (9%)
2.9 MB
2.6 MB
In fact, the total size of Chrono12.de main page is 2.9 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. 65% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 83.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 83.4 kB or 82% of the original size.
Potential reduce by 145.9 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. Chrono12 images are well optimized though.
Potential reduce by 40.4 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 40.4 kB or 18% of the original size.
Potential reduce by 3.7 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. Chrono12.de needs all CSS files to be minified and compressed as it can save up to 3.7 kB or 23% of the original size.
Number of requests can be reduced by 28 (22%)
125
97
The browser has sent 125 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Chrono12. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
chrono12.de
502 ms
chrono12.de
1059 ms
styles.css
244 ms
css
34 ms
jquery.min.js
20 ms
jquery-ui.min.js
24 ms
jquery.flexslider.js
359 ms
jquery.easing.js
359 ms
jquery.jcarousel.js
361 ms
jquery.jtweetsanywhere-1.3.1.min.js
362 ms
simpletabs_1.3.js
364 ms
form_elements.js
367 ms
custom.js
478 ms
saja.js
480 ms
cookieconsent.min.css
37 ms
cookieconsent.min.js
47 ms
conversion.js
49 ms
reset.css
242 ms
flexslider.css
243 ms
jcarousel_tango.css
246 ms
simpletabs.css
251 ms
short_codes.css
358 ms
base.css
361 ms
responsive.css
366 ms
gtm.js
82 ms
analytics.js
54 ms
logo_02.jpg
153 ms
top-banner2.jpg
261 ms
search_btn.png
147 ms
menu_bck.png
148 ms
cart_icon.png
146 ms
sdk.js
82 ms
PP_logo_h_150x38.png
97 ms
16.png
535 ms
uhren-teaser-bossart-02.jpg
594 ms
uhren-teaser-ingersoll.jpg
563 ms
uhren-teaser-perigaum.jpg
487 ms
uhren-teaser-rothenschild-02.jpg
495 ms
uhren-teaser-welder.jpg
610 ms
promo_hb_2.jpg
370 ms
0013ad1f8f2f8c4dca4976589ca961b3.jpg
494 ms
a10c912110c5c142611dc1822323bb27.jpg
608 ms
4e0793acb71a55b79bf7d087803570f9.jpg
618 ms
623df19f1d52abd271fb30b7a0277e7d.jpg
621 ms
5d0ceaf152e5dd30c622727ce8eaa6f2.jpg
691 ms
17e114419717ae3adf590c6aabe926df.jpg
715 ms
3155e9a46b74c150d918d10afe4cc2fb.jpg
735 ms
c0098ae1872e5d016d874f8ebb13ef93.jpg
736 ms
b92cfa916722680ea7834adb1dc2f5e3.jpg
744 ms
49644e65e4444dec8705ae433fe3a962.jpg
748 ms
937c7ff37f1442461c5e02ec2d473f5e.jpg
821 ms
78eea1854e1febf10c7c73dd0ead0f92.jpg
1364 ms
8270da6bbd8c2ec290616a5d63369d10.jpg
1363 ms
bffd7aa9bae442c832b6f9de52aabda3.jpg
1364 ms
0f425045be5c366dcd08f76a1c243a44.jpg
1365 ms
acbf6652b597661cb5fd586a64e24c48.jpg
1365 ms
8eca6bf3e734f6fdcfcbcd27763f9cc5.png
1366 ms
e36a8f01396b0d24d3f4197fcf6d4ffc.jpg
1367 ms
d82fa6886e9a27a15cc78af081b2486e.jpg
1367 ms
998e327673159b5a80829e08b9e0e4d9.jpg
1368 ms
fee08bdca1d072201a683764c7041e01.jpg
1368 ms
d9842144b9dce325040134fdf3322fe8.jpg
1368 ms
659f5eae13d4ad4d2959c18149e3a324.jpg
1369 ms
638d53b4911c36b6f53d265841dfdbbd.jpg
1370 ms
8fb73254839e61262562a4ef9010ca48.jpg
1372 ms
font
144 ms
698 ms
collect
49 ms
logo.js
238 ms
sdk.js
27 ms
65 ms
149XS5CG663FVB.js
752 ms
js
78 ms
4583e89c3b92507282fc4e24c30d9271.jpg
1279 ms
07aeb5ac2091c790bf54421bf54546e3.jpg
1249 ms
7aa24cbc30e205b990ea0bad47147e5e.jpg
1248 ms
ce7757c4786f40291f5d61abe2256c22.jpg
1248 ms
49 ms
0bf12cb7c4e77c50a03eed6210d70dde.jpg
1135 ms
07fcce629e78b07fa3b83156321aa824.jpg
1132 ms
e4f34e98679d2fe6afd775b5c56c9b33.jpg
1017 ms
ff9452763b6cb0def83de88fcfe30e16.jpg
1011 ms
f26709cd7cf101554d5eb86809fe9649.jpg
1012 ms
4347beb233297ff610e299ad60e9b698.jpg
945 ms
82df8bf0d6c984f0095eb096521a361a.jpg
911 ms
95e6370920d7227e95e333427034cb61.jpg
1016 ms
c62f64b9d4b7d598a2469f5fd68ba901.jpg
1018 ms
3e71f51e09e93ff8cedc10037ba03586.jpg
1017 ms
44197fcbb392a7add66678748c27f3fa.jpg
1011 ms
7636f45ec077169e4c1417f189242b84.jpg
944 ms
0971937f332cd984abeb6e4a8375db72.jpg
922 ms
iframe_ready.css
778 ms
PO_VS_MC_wide.png
892 ms
3adb73c5c6b5465f8a1930d41cc4e0b9.jpg
1013 ms
a0c01993da77d99d441b33bcc3f5b853.jpg
1015 ms
6be05e04aac58a21c7dc6feddd08db01.jpg
1017 ms
817efd30d517b31e8e6257d42b09a581.jpg
1018 ms
dd42e54f114dec3f1702ff71cfd49d36.jpg
943 ms
e3d7ca87d4d3aab1ab0209e5b935aff7.jpg
405 ms
f7fa99f681ee54da2812386dc1d26e60.jpg
509 ms
b6ace3ff0657309ea3993d2950e7ce1d.jpg
510 ms
7a0fb07cedfe31f2ef68086086e9b7e6.jpg
529 ms
72040b431941c533c21c6d55f680d2cd.jpg
524 ms
5586c2bf3be0425dfa28973d67d695b2.jpg
524 ms
ff177c0e8c13648c2018128f557f003d.jpg
529 ms
be2d27d0f95856e3b7069766ff4e8539.jpg
627 ms
74e72ec50bf49adc8790c9081c360a71.png
637 ms
275e5fdd57eba9f6b70b3f4d1911c464.png
653 ms
07355a982da986868ba15905dda6b1dd.png
651 ms
9709f7f982c3248de6cab890a4b83265.jpg
649 ms
8368069fd64cdfddfd029f04335955c3.png
651 ms
478e520746718a579759c8771b72d30e.png
863 ms
b8a0b28ca25700b2409cf8ab104f67e0.png
754 ms
6f5edc9ff4f39e08b53c49305e82020e.png
771 ms
28048cb8c4b0a3aea6b3c4f71d6b2198.png
777 ms
a6b6718d746769589e2561e1295bd3be.png
778 ms
2787687fa871a141fc0d9c22ac6e33f2.png
783 ms
c2c673955260bef2e17165f7df83b963.png
754 ms
67afb21ca95a74f1c7a60d68b556bd20.png
775 ms
c7fe0a07a51ba90003b44edfd97a82cf.jpg
776 ms
acbcda723f96b7aaf6b67472f9f9b7e0.jpg
777 ms
24e92e2fa95044778a0d97a630be59b1.jpg
777 ms
delivery_suppliers.jpg
855 ms
facebook.png
756 ms
subscribe_textfield.png
776 ms
subscribe_btn.png
774 ms
shipping.png
771 ms
banner_rotator_left.png
770 ms
banner_rotator_right.png
846 ms
chrono12.de 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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
chrono12.de 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
chrono12.de SEO score
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
![]()
RO
![]()
RO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Chrono12.de can be misinterpreted by Google and other search engines. Our service has detected that Romanian is used on the page, and it matches the claimed language. Our system also found out that Chrono12.de 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.
chrono12.de
Open Graph description is not detected on the main page of Chrono12. 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: