6.7 sec in total
366 ms
4.8 sec
1.5 sec
Visit watchtown.ru now to see the best up-to-date Watch Town content for Russia and also check out these interesting facts you probably never knew about watchtown.ru
У нас вы сможете позволить себе подобрать качественные и надежные наручные часы на любой вкус. Презентабельный наручный аксессуар, купленный у нас, станет способом продемонстрировать вашу статусность ...
Visit watchtown.ruWe analyzed Watchtown.ru page load time and found that the first response time was 366 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
watchtown.ru performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value17.0 s
0/100
25%
Value6.5 s
39/100
10%
Value2,620 ms
4/100
30%
Value0.065
97/100
15%
Value18.0 s
3/100
10%
366 ms
1072 ms
70 ms
131 ms
49 ms
Our browser made a total of 137 requests to load all elements on the main page. We found that 83% of them (114 requests) were addressed to the original Watchtown.ru, 4% (5 requests) were made to Top-fwz1.mail.ru and 2% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Watchtown.ru.
Page size can be reduced by 247.6 kB (7%)
3.6 MB
3.4 MB
In fact, the total size of Watchtown.ru main page is 3.6 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 3.1 MB which makes up the majority of the site volume.
Potential reduce by 71.1 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 19.8 kB, which is 22% 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 71.1 kB or 80% of the original size.
Potential reduce by 146.1 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. Watch Town images are well optimized though.
Potential reduce by 27.5 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. This website has mostly compressed JavaScripts.
Potential reduce by 2.9 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. Watchtown.ru has all CSS files already compressed.
Number of requests can be reduced by 59 (46%)
127
68
The browser has sent 127 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Watch Town. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
watchtown.ru
366 ms
watchtown.ru
1072 ms
gtm.js
70 ms
core.css
131 ms
css2
49 ms
style.css
260 ms
swiper.min.css
375 ms
jquery.fancybox.min.css
375 ms
nice-select.css
381 ms
magnific-popup.css
382 ms
main.css
516 ms
style.css
389 ms
style.css
498 ms
style.css
499 ms
styles.css
506 ms
template_styles.css
507 ms
simplebar.min.css
183 ms
font-awesome.min.css
193 ms
core.js
786 ms
script.js
619 ms
api.js
49 ms
jquery.min.js
749 ms
swiper.min.js
759 ms
jquery.fancybox.min.js
760 ms
scrollreveal.min.js
638 ms
jquery.nice-select.min.js
740 ms
jquery.mask.min.js
766 ms
jquery.magnific-popup.min.js
867 ms
main.js
872 ms
O1.js
885 ms
Emitter.js
886 ms
Component.js
891 ms
Form.js
916 ms
emmiter.js
987 ms
script.js
995 ms
numberAnimate.js
1011 ms
script.js
1011 ms
script.js
1019 ms
js
77 ms
simplebar.min.js
388 ms
popup.js
498 ms
logo.svg
950 ms
logo.png
987 ms
supermarket.svg
992 ms
b23e13ee5f8eb5f1b182a94c108926c3.png
1269 ms
be4034e4e51047278fb4bfd531794364.png
1525 ms
28c37d8fe3f3a4a5e72c82a17a2885fd.jpg
1275 ms
1421385c16946e2a86222fa734cb7659.png
1183 ms
218ab1fedc06454318ca6235b481cefa.jpg
1488 ms
016737226e3a4a3c5640ca8a9cd69624.png
1248 ms
539627c8c9dd440a146b43b39f47620c.jpg
1284 ms
1a85a3c7649385a51a0492273825d3b1.jpg
1285 ms
70e46fb38568c981fdd5479a04146ff1.jpg
1187 ms
5ae1d637b19378537d53506afacb2b28.svg
1206 ms
f97231b52ecc18450d2b2769e3e54613.jpg
1249 ms
openapi.c340c125c61ec5745ebb2a98626e46ab.js
240 ms
d3257ddff05445ca7d97a879306396f3.svg
1284 ms
fe5b262849b7a8673e91da681da9d294.jpg
1284 ms
tag.js
918 ms
Gilroy-MediumItalic.woff
1256 ms
code.js
768 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4k.woff
22 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4k.woff
29 ms
Gilroy-Medium.woff
1211 ms
Gilroy-Regular.woff
1231 ms
rtrg
139 ms
Gilroy-SemiBold.woff
1173 ms
Gilroy-Bold.woff
1165 ms
Gilroy-ExtraBold.woff
1168 ms
f2c05f169579daa590e448a575d7d653.svg
1200 ms
e59386756a828e085c5808e2f150cbf5.jpg
1216 ms
59a9818cde9884a968de1471ce17fe18.svg
1129 ms
929304e0fafdfde456542c47d72056e3.jpg
1170 ms
ab4a0e8d40961f87f8e6fcab8ef1f243.png
1166 ms
378745e0913ef9fc407ae49514a3e593.jpg
1159 ms
a2ee528ab653f41251b1046f3c0cb0dd.png
1202 ms
18d43296f933a430a6078238d7702352.jpg
1212 ms
d65a0ac5e9758ad24146b3a577212b5b.svg
1198 ms
4b745bacc358ebfbbe5c8ff4bb68399b.jpg
1176 ms
98adde4c1b776611c9d314baf9a2469b.svg
1171 ms
16f00672d78ab8d78f3dc9f453379d82.svg
1158 ms
1abbc594f7a4d5dac68dee643effc7d9.jpg
1206 ms
ajax_counter.php
1544 ms
js
60 ms
bd64a7d56662e31bb7a4747bf7b32787.png
1126 ms
b15bd61c2924faf84ed9348dfa39623d.jpg
1185 ms
dc73247687af38e5decadfde9bf36688.svg
1179 ms
sync-loader.js
873 ms
counter
168 ms
dyn-goal-config.js
257 ms
counter
382 ms
30f12b6cf5098db0546dbdf4e9ae98be.jpg
906 ms
a05dc369a8c5730f9f105b94c8c91ce7.png
946 ms
f94acb2774fdbf0f4d25ca23792f426e.jpg
926 ms
advert.gif
765 ms
ada0289eee6c4000b026a1f7321b08f7.svg
848 ms
17d705b580898b7cd906fd9c1b6e5aaf.jpg
801 ms
68b4125c2f4a5bde7beec4ce3171b5c6.svg
772 ms
d76afd58b202d1573bee10adb8518667.jpg
822 ms
dc7c7a008071ff2a23f74232d7165a25.svg
827 ms
27e7ebc516764a815b7f2b73dbde1e25.jpg
843 ms
c989af89f5e0415b483f208a2d4c2c71.png
803 ms
c0b0c9bd43a1c6e36d89223725cd6be8.svg
769 ms
bf3775ced2779d717f2a964390c7d7d3.svg
822 ms
5c67480803d9b2b8849e5c50eec905a5.svg
810 ms
youtube.svg
831 ms
vk.svg
815 ms
ok.svg
802 ms
icons8-unionpay-96.svg
830 ms
icons8-%D0%B2%D0%B8%D0%B7%D0%B0-96.svg
810 ms
icons8-%D0%BC%D0%B0%D1%81%D1%82%D0%B5%D1%80%D0%BA%D0%B0%D1%80%D0%B4-96.svg
796 ms
sberpay_.svg
838 ms
tinkof_pej.svg
821 ms
YooMoney.svg
816 ms
mir-logo-h14px.svg
821 ms
ya_market.svg
834 ms
google.svg
822 ms
telegram.svg
836 ms
viber.svg
825 ms
message.svg
826 ms
search.svg
819 ms
tabs-close.svg
821 ms
phone-call.svg
830 ms
sale.svg
833 ms
user.svg
819 ms
sync_cookie_image_decide
163 ms
5b0b6451d66eb6de2ec8b6a3cfae70d9.jpg
901 ms
18c0affe11c643524be6f0610e5c32e8.jpg
808 ms
640942d645c76da7bda1e2dd928ed172.jpg
813 ms
ec9a9655cda282780307b808533a0d40.jpg
781 ms
swiper-arrow.png
832 ms
stars5_grey.svg
773 ms
stars5_yellow.svg
813 ms
arrow.svg
802 ms
chat.svg
785 ms
1
533 ms
tracker
129 ms
watchtown.ru 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
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
[id] attributes on active, focusable elements are not unique
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 IDs are not unique
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.
watchtown.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
watchtown.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Watchtown.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Watchtown.ru 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.
watchtown.ru
Open Graph description is not detected on the main page of Watch Town. 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: