Tools & Wizards About Us
watch.ru screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

watch.ru

Watch.ru : Часы.ру - Чайкина Casiotron часовой 11, Ракета BIG ZERO Arabic, GRØNE OLDENZAAL бренд

Page Load Speed

10 sec in total

First Response

1.8 sec

Resources Loaded

7.9 sec

Page Rendered

362 ms

watch.ru screenshot

About Website

Welcome to watch.ru homepage info - get ready to check Watch best content for Russia right away, or after learning these important things about watch.ru

Часовой портал, новости часового рынка и новинки часов, обзоры, отзывы и опыт владения часами. Маркет, где можно купить или продать часы, украшения, предметы искусства и роскоши. Клуб про стиль, путеш...

Visit watch.ru

Key Findings

We analyzed Watch.ru page load time and found that the first response time was 1.8 sec and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

watch.ru performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

39/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value6.9 s

33/100

10%

TBT (Total Blocking Time)

Value220 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0.176

68/100

15%

TTI (Time to Interactive)

Value8.7 s

36/100

10%

Network Requests Diagram

watch.ru

1757 ms

style-e958bdba-00003.css

362 ms

vbulletin_important.css

364 ms

nelement-common.css

1215 ms

nelement.css

1216 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 8% of them (5 requests) were addressed to the original Watch.ru, 44% (28 requests) were made to Clock.ru and 28% (18 requests) were made to Forum.watch.ru. The less responsive or slowest element that took the longest time to load (4.6 sec) relates to the external source Red-dot.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 325.6 kB (9%)

Content Size

3.6 MB

After Optimization

3.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Watch.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. 55% of websites need less resources to load. Images take 3.4 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 41.1 kB

  • Original 53.3 kB
  • After minification 48.6 kB
  • After compression 12.2 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 41.1 kB or 77% of the original size.

Image Optimization

-7%

Potential reduce by 245.2 kB

  • Original 3.4 MB
  • After minification 3.2 MB

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 images are well optimized though.

JavaScript Optimization

-23%

Potential reduce by 32.0 kB

  • Original 138.3 kB
  • After minification 138.3 kB
  • After compression 106.3 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 32.0 kB or 23% of the original size.

CSS Optimization

-40%

Potential reduce by 7.3 kB

  • Original 18.2 kB
  • After minification 17.6 kB
  • After compression 10.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. Watch.ru needs all CSS files to be minified and compressed as it can save up to 7.3 kB or 40% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (49%)

Requests Now

63

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 15 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

watch.ru

watch.ru

1757 ms

style-e958bdba-00003.css

style-e958bdba-00003.css

362 ms

vbulletin_important.css

vbulletin_important.css

364 ms

nelement-common.css

nelement-common.css

1215 ms

nelement.css

nelement.css

1216 ms

yahoo-dom-event.js

yahoo-dom-event.js

1216 ms

connection-min.js

connection-min.js

1215 ms

vbulletin_global.js

vbulletin_global.js

1222 ms

vbulletin_menu.js

vbulletin_menu.js

1220 ms

jquery-2.2.4.min.js

jquery-2.2.4.min.js

1562 ms

jquery-migrate-1.4.1.min.js

jquery-migrate-1.4.1.min.js

1333 ms

neat-tooltip.js

neat-tooltip.js

1334 ms

neat-tooltip.css

neat-tooltip.css

1333 ms

neat-tooltip_extra.css

neat-tooltip_extra.css

1338 ms

js.cookie.js

js.cookie.js

1340 ms

definenextrandomslot.js

definenextrandomslot.js

1448 ms

etime_dgt_rev2016.js

etime_dgt_rev2016.js

1449 ms

js

js

50 ms

vbulletin_md5.js

vbulletin_md5.js

365 ms

tag.js

tag.js

847 ms

hit;watchclock

hit;watchclock

507 ms

attachment.php

attachment.php

1772 ms

refresh-etime_blue.png

refresh-etime_blue.png

161 ms

53236569785_80baf8fcaa_z.jpg

53236569785_80baf8fcaa_z.jpg

62 ms

index.php

index.php

4638 ms

bg_main.gif

bg_main.gif

165 ms

bg_main_box.gif

bg_main_box.gif

164 ms

similarweb.svg

similarweb.svg

161 ms

google_analytics.svg

google_analytics.svg

164 ms

yandex_metrica.svg

yandex_metrica.svg

162 ms

swissign_trust_logo.svg

swissign_trust_logo.svg

361 ms

logo_paykeeper_bw_vertical.svg

logo_paykeeper_bw_vertical.svg

233 ms

picture.php

picture.php

1472 ms

picture.php

picture.php

1078 ms

attachment.php

attachment.php

1426 ms

attachment.php

attachment.php

2005 ms

attachment.php

attachment.php

277 ms

attachment.php

attachment.php

444 ms

attachment.php

attachment.php

603 ms

attachment.php

attachment.php

758 ms

attachment.php

attachment.php

919 ms

attachment.php

attachment.php

1071 ms

attachment.php

attachment.php

1233 ms

attachment.php

attachment.php

1232 ms

attachment.php

attachment.php

1848 ms

attachment.php

attachment.php

2103 ms

16x16progress-etime.gif

16x16progress-etime.gif

229 ms

52790138338_125d983e58_z.jpg

52790138338_125d983e58_z.jpg

59 ms

logo

logo

249 ms

logo_watchru_original_light.svg

logo_watchru_original_light.svg

201 ms

bg_menu_form.gif

bg_menu_form.gif

203 ms

bg_menu.jpg

bg_menu.jpg

201 ms

js

js

60 ms

analytics.js

analytics.js

54 ms

bg_form_search.gif

bg_form_search.gif

179 ms

wru_search.png

wru_search.png

289 ms

bg_list_center_news.gif

bg_list_center_news.gif

294 ms

icons18_v2.png

icons18_v2.png

295 ms

collect

collect

61 ms

et_get_server_time.php

et_get_server_time.php

274 ms

et_get_delta_time.php

et_get_delta_time.php

292 ms

advert.gif

advert.gif

642 ms

sync_cookie_image_decide

sync_cookie_image_decide

133 ms

1

1

141 ms

Accessibility Review

watch.ru accessibility score

85

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

watch.ru best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

watch.ru SEO score

77

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Watch.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 Watch.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.

Social Sharing Optimization

watch.ru

Open Graph description is not detected on the main page of Watch. 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: