Tools & Wizards About Us
tdnobel.ru screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

tdnobel.ru

Салон элитных часов и аксессуаров Нобель - Официальный дилер

Page Load Speed

4.8 sec in total

First Response

551 ms

Resources Loaded

3.9 sec

Page Rendered

300 ms

tdnobel.ru screenshot

About Website

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

Купить элитные часы и аксессуары Вы можете в интернет магазине Нобель. Мы являемся официальным дилером.

Visit tdnobel.ru

Key Findings

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

Performance Metrics

tdnobel.ru performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

48/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

34/100

25%

SI (Speed Index)

Value9.7 s

11/100

10%

TBT (Total Blocking Time)

Value1,160 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.595

11/100

15%

TTI (Time to Interactive)

Value12.2 s

15/100

10%

Network Requests Diagram

tdnobel.ru

551 ms

tdnobel.ru

738 ms

bootstrap.min.css

283 ms

owl.carousel.css

416 ms

main.css

419 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 81% of them (44 requests) were addressed to the original Tdnobel.ru, 6% (3 requests) were made to Code.jivosite.com and 4% (2 requests) were made to Mc.yandex.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Tdnobel.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 73.4 kB (5%)

Content Size

1.6 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tdnobel.ru main page is 1.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. 30% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 21.2 kB

  • Original 27.0 kB
  • After minification 20.6 kB
  • After compression 5.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 6.5 kB, which is 24% 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 21.2 kB or 78% of the original size.

Image Optimization

-5%

Potential reduce by 47.5 kB

  • Original 1.0 MB
  • After minification 974.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. Tdnobel images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.5 kB

  • Original 526.0 kB
  • After minification 526.0 kB
  • After compression 522.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. This website has mostly compressed JavaScripts.

CSS Optimization

-4%

Potential reduce by 1.1 kB

  • Original 27.3 kB
  • After minification 27.3 kB
  • After compression 26.1 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. Tdnobel.ru has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 19 (37%)

Requests Now

51

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tdnobel. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

tdnobel.ru

tdnobel.ru

551 ms

tdnobel.ru

tdnobel.ru

738 ms

bootstrap.min.css

bootstrap.min.css

283 ms

owl.carousel.css

owl.carousel.css

416 ms

main.css

main.css

419 ms

jquery.min.js

jquery.min.js

25 ms

default.css

default.css

432 ms

bootstrap.min.js

bootstrap.min.js

433 ms

switches.js

switches.js

431 ms

owl.carousel.min.js

owl.carousel.min.js

431 ms

js

js

57 ms

vUJRsocKzw

vUJRsocKzw

208 ms

default.js

default.js

549 ms

jquery.jgrowl.min.css

jquery.jgrowl.min.css

141 ms

main-logo.png

main-logo.png

140 ms

phone-icon.png

phone-icon.png

140 ms

search__icon.png

search__icon.png

137 ms

basket-icon.png

basket-icon.png

142 ms

nav-icons.png

nav-icons.png

141 ms

%D0%B1%D0%B0%D0%BD%D0%B5%D1%80%20%D1%85%D0%BE%D1%85%D0%BB%D0%BE%D0%BC%D0%B0.jpg

%D0%B1%D0%B0%D0%BD%D0%B5%D1%80%20%D1%85%D0%BE%D1%85%D0%BB%D0%BE%D0%BC%D0%B0.jpg

706 ms

grimaldi_logo.jpg

grimaldi_logo.jpg

950 ms

corum_banner.jpg

corum_banner.jpg

279 ms

montblank_banner_new.jpg

montblank_banner_new.jpg

696 ms

logo-top-1_v_1.png

logo-top-1_v_1.png

282 ms

waldmann.png

waldmann.png

281 ms

perrelet.png

perrelet.png

418 ms

artya.png

artya.png

423 ms

pesvaento.png

pesvaento.png

423 ms

ball.png

ball.png

558 ms

corum.png

corum.png

562 ms

montegrappa.png

montegrappa.png

563 ms

lepee.png

lepee.png

696 ms

gourji.png

gourji.png

703 ms

dupont.png

dupont.png

704 ms

montblanc.png

montblanc.png

834 ms

piaget.png

piaget.png

835 ms

panerai.png

panerai.png

843 ms

Jaeger.png

Jaeger.png

844 ms

baume.png

baume.png

845 ms

whatsapp_logo.png

whatsapp_logo.png

973 ms

banner-vintage.jpg

banner-vintage.jpg

975 ms

corum_new.jpg

corum_new.jpg

982 ms

abc1237.jpg

abc1237.jpg

1264 ms

1123123123.jpg

1123123123.jpg

984 ms

more-arrow.png

more-arrow.png

1090 ms

tag.js

tag.js

934 ms

top100.js

top100.js

659 ms

jquery.jgrowl.min.js

jquery.jgrowl.min.js

1036 ms

HelveticaNeueCyr-Light.woff

HelveticaNeueCyr-Light.woff

1036 ms

vUJRsocKzw

vUJRsocKzw

393 ms

vUJRsocKzw

vUJRsocKzw

595 ms

advert.gif

advert.gif

710 ms

sync_cookie_image_decide

sync_cookie_image_decide

155 ms

bundle_ru_RU.js

bundle_ru_RU.js

50 ms

Accessibility Review

tdnobel.ru accessibility score

74

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

tdnobel.ru best practices score

75

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

High

Page has valid source maps

SEO Factors

tdnobel.ru SEO score

89

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Tdnobel.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 Tdnobel.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

tdnobel.ru

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