25.6 sec in total
734 ms
24.3 sec
630 ms
Welcome to cortinawatch.com homepage info - get ready to check Cortina Watch best content for Thailand right away, or after learning these important things about cortinawatch.com
Discover timeless elegance with Cortina Watch. Elevate your style with our luxury watches and explore the artistry of horology in our exquisite collection for men and women.
Visit cortinawatch.comWe analyzed Cortinawatch.com page load time and found that the first response time was 734 ms and then it took 24.9 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
cortinawatch.com performance score
name
value
score
weighting
Value9.0 s
0/100
10%
Value16.6 s
0/100
25%
Value21.2 s
0/100
10%
Value1,600 ms
12/100
30%
Value0.586
11/100
15%
Value20.5 s
2/100
10%
734 ms
1445 ms
702 ms
468 ms
1399 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 80% of them (39 requests) were addressed to the original Cortinawatch.com, 6% (3 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (20 sec) belongs to the original domain Cortinawatch.com.
Page size can be reduced by 705.1 kB (19%)
3.8 MB
3.1 MB
In fact, the total size of Cortinawatch.com main page is 3.8 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. 30% of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 53.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. 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 53.5 kB or 75% of the original size.
Potential reduce by 109.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. Cortina Watch images are well optimized though.
Potential reduce by 329.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 329.2 kB or 70% of the original size.
Potential reduce by 212.6 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. Cortinawatch.com needs all CSS files to be minified and compressed as it can save up to 212.6 kB or 88% of the original size.
Number of requests can be reduced by 23 (56%)
41
18
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cortina Watch. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
cortinawatch.com
734 ms
1445 ms
wp-emoji-release.min.js
702 ms
styles.css
468 ms
jquery.js
1399 ms
jquery-migrate.min.js
662 ms
swiper.min.css
1165 ms
animate.css
1362 ms
normalize.css
1892 ms
classic.css
1320 ms
classic.date.css
1397 ms
fonts.css
1629 ms
css
54 ms
css
66 ms
font-awesome.min.css
38 ms
app.css
2482 ms
jquery.form.min.js
1402 ms
scripts.js
1438 ms
wp-embed.min.js
1439 ms
jquery-3.1.1.min.js
2373 ms
swiper.min.js
2805 ms
picker.js
2387 ms
picker.date.js
2386 ms
legacy.js
2290 ms
wow.min.js
2522 ms
app.js
2990 ms
analytics.js
97 ms
cortina.jpg
1222 ms
gfx-time.png
1689 ms
IMG_0267.01.jpg
1689 ms
center-store.jpg
1836 ms
feature-image-1.jpg
2584 ms
feature-image-2-1.jpg
3476 ms
featured-image-3.jpg
2851 ms
timepiece.png
2389 ms
Cortina-Watch-IMAGO-Shopping-Mall-1.jpg
19988 ms
Montblanc-TimeWalker-Minerva.png
8593 ms
400.jpg
4023 ms
Baselworld2017-Trilogy_amb.jpg
3750 ms
calendar.png
3317 ms
select_arrow.jpg
3782 ms
store-locator.jpg
5584 ms
KYNzioYhDai7mTMnx_gDgkXX4kpEMIkMuCYjxR86fn4.ttf
21 ms
11EDm-lum6tskJMBbdy9af7cR9bDBM2wtBUNpqAqtuE.ttf
40 ms
TKyx_-JJ6MdpQruNk-t-PGlrf7sQ1DEW_ZXPNbrNues.ttf
41 ms
fontawesome-webfont.woff
42 ms
collect
25 ms
collect
50 ms
ajax-loader.gif
3297 ms
cortinawatch.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
cortinawatch.com 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
cortinawatch.com 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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cortinawatch.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Cortinawatch.com 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.
cortinawatch.com
Open Graph data is detected on the main page of Cortina Watch. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: