13.4 sec in total
680 ms
12.4 sec
348 ms
Visit watchcasa.com now to see the best up-to-date Watchcasa content for Greece and also check out these interesting facts you probably never knew about watchcasa.com
Luxotis
Visit watchcasa.comWe analyzed Watchcasa.com page load time and found that the first response time was 680 ms and then it took 12.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
watchcasa.com performance score
name
value
score
weighting
Value17.5 s
0/100
10%
Value40.1 s
0/100
25%
Value26.0 s
0/100
10%
Value1,780 ms
10/100
30%
Value1.024
2/100
15%
Value42.3 s
0/100
10%
680 ms
971 ms
667 ms
271 ms
273 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Watchcasa.com, 84% (98 requests) were made to Watchcasa.gr and 5% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (8.6 sec) relates to the external source Watchcasa.gr.
Page size can be reduced by 2.1 MB (32%)
6.5 MB
4.4 MB
In fact, the total size of Watchcasa.com main page is 6.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.4 MB which makes up the majority of the site volume.
Potential reduce by 168.8 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 31.7 kB, which is 17% 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 168.8 kB or 89% of the original size.
Potential reduce by 427.2 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. Watchcasa images are well optimized though.
Potential reduce by 898.0 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 898.0 kB or 71% of the original size.
Potential reduce by 588.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. Watchcasa.com needs all CSS files to be minified and compressed as it can save up to 588.6 kB or 86% of the original size.
Number of requests can be reduced by 53 (50%)
105
52
The browser has sent 105 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Watchcasa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
watchcasa.com
680 ms
971 ms
jquery.min.js
667 ms
jquery-migrate.min.js
271 ms
mod_cart_up.js
273 ms
css
44 ms
bootstrap.css
416 ms
k2.css
280 ms
system.css
284 ms
legacy-grid.css
402 ms
font-awesome.min.css
403 ms
template.css
420 ms
megamenu.css
425 ms
font-awesome.min.css
534 ms
custom.css
805 ms
custom-responsive.css
552 ms
more_custom.css
558 ms
mailchimpsignup.css
565 ms
chosen.css
722 ms
facebox.css
723 ms
modal.css
723 ms
settings.css
724 ms
dynamic-captions.css
794 ms
static-captions.css
798 ms
jquery.mCustomScrollbar.css
828 ms
style.css
834 ms
mootools-core.js
1132 ms
core.js
927 ms
k2.js
930 ms
opcping.js
935 ms
caption.js
968 ms
bootstrap.js
974 ms
jquery.tap.min.js
1061 ms
script.js
1062 ms
menu.js
1068 ms
vmprices2.js
1107 ms
nav-collapse.js
1113 ms
custom.js
1195 ms
conversion.js
18 ms
mailchimpsignup.js
1071 ms
mootools-more.js
1209 ms
modal.js
985 ms
chosen.jquery.min.js
983 ms
dynupdate.js
998 ms
vmsite.js
935 ms
facebox.js
933 ms
cookiealert.js
979 ms
jquery-ias.js
981 ms
jquery.themepunch.tools.min.js
1560 ms
jquery.themepunch.revolution.min.js
1075 ms
allscripts.js
920 ms
linescript.js
973 ms
system.css
825 ms
fbevents.js
10 ms
Logo-01_regular.png
146 ms
el.gif
145 ms
en.gif
144 ms
hugoboss222.png
8562 ms
tommy999.png
1631 ms
bannerfossil15.png
1334 ms
dwbg.png
275 ms
dw1.png
803 ms
dw22.png
411 ms
dw3.png
1508 ms
AR2418.jpg
800 ms
ju15041-3.jpg
1066 ms
es1058020047_290x270.jpg
939 ms
MK5145.jpg
1079 ms
MKWB.jpg
1461 ms
W0448L3.jpg
1218 ms
K2V214DX.jpg
1356 ms
MK6135.jpg
1466 ms
1512447.jpg
1497 ms
MK5569.jpg
1595 ms
ES103342002.jpg
1602 ms
MK6204.jpg
1634 ms
CH2991.jpg
2224 ms
ES105452010.jpg
1727 ms
c7341.jpg
1735 ms
W0232L2.jpg
1785 ms
K3Y2M11F.jpg
1777 ms
W0387G3.jpg
1860 ms
1791114.jpg
1867 ms
W0674G2.jpg
1917 ms
AR1407.jpg
1924 ms
K4C2M116.jpg
1994 ms
ju14487jsg-59m.jpg
2002 ms
analytics.js
10 ms
W0599G2.jpg
2056 ms
ES107132005.jpg
2062 ms
110 ms
Fl4y0QdOxyyTHEGMXX8kcT8E0i7KZn-EPnyo3HZu7kw.woff
23 ms
G1l_KMKj5pga7ZKths0iTfesZW2xOQ-xsNqO47m55DA.woff
24 ms
Y5yuUJGDLtmYv2_3fMB4fA.woff
24 ms
oHi30kwQWvpCWqAhzHcCSD8E0i7KZn-EPnyo3HZu7kw.woff
25 ms
isZ-wbCXNKAbnjo6_TwHTj8E0i7KZn-EPnyo3HZu7kw.woff
23 ms
3Y_xCyt7TNunMGg0Et2pnj8E0i7KZn-EPnyo3HZu7kw.woff
24 ms
ec.js
15 ms
collect
22 ms
collect
56 ms
ga-audiences
39 ms
fontawesome-webfont.woff
1988 ms
diesel50.png
2132 ms
%CE%9C%CE%9A40.png
2195 ms
emporioarmani60.png
1929 ms
guess60.png
1996 ms
ajax-loader.gif
1933 ms
jquery.mousewheel.min.js
34 ms
230 ms
top-menu-marker.gif
1567 ms
footer_bg.png
1608 ms
31 ms
bubble.png
1536 ms
fancybox_loading.gif
1416 ms
loader.gif
1427 ms
coloredbg.png
1309 ms
fancybox_loading.gif
1213 ms
watchcasa.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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
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
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.
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
watchcasa.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
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
watchcasa.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
EL
EL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Watchcasa.com can be misinterpreted by Google and other search engines. Our service has detected that Greek is used on the page, and it matches the claimed language. Our system also found out that Watchcasa.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.
watchcasa.com
Open Graph description is not detected on the main page of Watchcasa. 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: