wit.ru

wit.ru is SSL secured

Free website and domain report on wit.ru

Last Updated: 22nd June, 2021 Update Now
Overview

Snoop Summary for wit.ru

This is a free and comprehensive report about wit.ru. Wit.ru is hosted in Russia on a server with an IP address of 81.177.166.40, where RUB is the local currency and the local language is Russian. Our records indicate that wit.ru is owned/operated by WIT Company. If wit.ru was to be sold it would possibly be worth $584 USD (based on the daily revenue potential of the website over a 24 month period). Wit.ru is somewhat popular with an estimated 276 daily unique visitors. This report was last updated 22nd June, 2021.

About wit.ru

Site Preview: wit.ru wit.ru
Title: Компания WIT
Description: Интернет магазин: сервера Intel и SuperMicro, системы хранения данных Infortrend и Synology, сетевое оборудование Linlsys, Cisco, Mikrotik, лицензионное программное обеспечение Microsoft. Доставка.
Keywords and Tags: intel, internet services, microsoft, supermicro, Интел, Микрософт, Сервер, Супермикро
Related Terms: mikrotik, mikrotik routeros, synology connect, synology login, synology me, synology nas, synology quick connect, synology quickconnect, synology rt2600ac, wit
Fav Icon:
Age: Over 27 years old
Domain Created: 21st October, 1996
Domain Updated:
Domain Expires: 31st October, 2021
Review

Snoop Score

1/5

Valuation

$584 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 5,096,225
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 276
Monthly Visitors: 8,404
Yearly Visitors: 100,777
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $24 USD
Yearly Revenue: $287 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: wit.ru 6
Domain Name: wit 3
Extension (TLD): ru 2
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 71
Performance 85
Accessibility 73
Best Practices 80
SEO 100
Progressive Web App 18
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
85

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for wit.ru. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.9 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 1.0 s
The timing of the largest text or image that is painted.
Time to Interactive — 1.8 s
The time taken for the page to become fully interactive.
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Opportunities

Eliminate render-blocking resources — Potential savings of 0 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Wit.ru should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
http://wit.ru/css/style.css
9770
70
Properly size images — Potential savings of 28 KiB
Images can slow down the page's load time. Wit.ru should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://wit.ru/images/sannas/GS3016.png
33638
15900
http://wit.ru/images/server/sys-7048r-tr.png
27614
13052
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Wit.ru should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 3 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Wit.ru should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://wit.ru/css/style.css
9770
3081
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Wit.ru should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Wit.ru should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript — Potential savings of 34 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://mc.yandex.ru/metrika/tag.js
71382
34490
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 51 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://wit.ru/images/sannas/GS3016.png
33638
28714
http://wit.ru/images/server/sys-7048r-tr.png
27614
23716
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 390 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
http://wit.ru/
392.956
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Wit.ru should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Wit.ru should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 257 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://mc.yandex.ru/metrika/tag.js
71382
https://www.googletagmanager.com/gtag/js?id=UA-141526195-1
37069
http://wit.ru/images/sannas/GS3016.png
33888
http://wit.ru/images/server/sys-7048r-tr.png
27864
https://www.google-analytics.com/analytics.js
20313
http://wit.ru/
12449
http://wit.ru/css/style.css
9770
http://wit.ru/images/wit_logo_81.png
6914
http://wit.ru/images/microsoft175.png
4524
http://wit.ru/js/ajax.js
3617
Avoids an excessive DOM size — 421 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
421
Maximum DOM Depth
b
12
Maximum Child Elements
17
Avoid chaining critical requests — 3 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Wit.ru should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 32 requests • 257 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
32
263678
Script
5
134887
Image
20
102041
Document
1
12449
Stylesheet
1
9770
Other
5
4531
Media
0
0
Font
0
0
Third-party
9
133669
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 14 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://mc.yandex.ru/metrika/tag.js
692
257
https://mc.yandex.ru/metrika/tag.js
1473
124
https://mc.yandex.ru/metrika/tag.js
959
106
https://mc.yandex.ru/metrika/tag.js
1650
104
https://www.google-analytics.com/analytics.js
1065
103
http://wit.ru/
401
87
https://www.googletagmanager.com/gtag/js?id=UA-141526195-1
611
81
Unattributable
202
72
https://mc.yandex.ru/metrika/tag.js
1754
71
Unattributable
289
67
http://wit.ru/js/ajax.js
1281
63
https://mc.yandex.ru/metrika/tag.js
1597
53
https://mc.yandex.ru/metrika/tag.js
1231
50
https://mc.yandex.ru/metrika/tag.js
1423
50
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Other

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://wit.ru/
http/1.1
0
391.96000003722
12449
32017
200
text/html
Document
https://www.googletagmanager.com/gtag/js?id=UA-141526195-1
h2
487.05200001132
583.82100006565
37069
91512
200
application/javascript
Script
http://wit.ru/css/style.css
http/1.1
487.46199999005
990.65900000278
9770
35169
200
text/css
Stylesheet
http://wit.ru/images/menu/servers-icon.png
http/1.1
499.57600003108
883.16399999894
1451
1202
200
image/png
Image
http://wit.ru/images/menu/computers-icon.png
http/1.1
500.24000008125
989.20900002122
1579
1330
200
image/png
Image
http://wit.ru/images/menu/storage-icon.png
http/1.1
500.57400006335
1087.8619999858
1691
1442
200
image/png
Image
http://wit.ru/images/menu/network-icon.png
http/1.1
501.37700000778
682.99200001638
1582
1333
200
image/png
Image
http://wit.ru/images/menu/software-icon.png
http/1.1
501.63200008683
994.70300006215
1770
1521
200
image/png
Image
http://wit.ru/images/menu/ups-icon.png
http/1.1
501.88200001139
892.38800003659
2006
1758
200
image/png
Image
http://wit.ru/images/menu/racks-icon.png
http/1.1
502.12199997623
1010.9020000091
2126
1877
200
image/png
Image
http://wit.ru/images/menu/thermoracks-icon.png
http/1.1
502.37400003243
900.18600004259
1659
1410
200
image/png
Image
http://wit.ru/images/menu/about-icon.png
http/1.1
502.57700006478
1088.8050000649
2054
1805
200
image/png
Image
http://wit.ru/images/menu/support-icon.png
http/1.1
502.83500005025
892.8859999869
2040
1791
200
image/png
Image
http://wit.ru/images/menu/delivery-icon.png
http/1.1
503.68900003377
988.39000007138
1985
1736
200
image/png
Image
http://wit.ru/images/menu/lease-icon.png
http/1.1
504.00499999523
989.62600005325
1638
1389
200
image/png
Image
http://wit.ru/images/wit_logo_81.png
http/1.1
504.19300002977
1086.4430000074
6914
6666
200
image/png
Image
http://wit.ru/images/cart_icon-white.png
http/1.1
504.96900000144
990.03700003959
2276
2027
200
image/png
Image
http://wit.ru/images/loupe_icon-29.png
http/1.1
505.2109999815
1093.467000057
2421
2172
200
image/png
Image
http://wit.ru/images/server/sys-7048r-tr.png
http/1.1
505.68000006024
1088.3039999753
27864
27614
200
image/png
Image
http://wit.ru/images/sannas/GS3016.png
http/1.1
508.24300001841
1196.2800000329
33888
33638
200
image/png
Image
http://wit.ru/images/microsoft175.png
http/1.1
508.46200005617
987.07500007004
4524
4275
200
image/png
Image
http://wit.ru/images/wit_logo.gif
http/1.1
508.67600005586
812.92000005487
2199
1950
200
image/gif
Image
http://wit.ru/js/ajax.js
http/1.1
494.20200008899
883.81600007415
3617
10199
200
application/javascript
Script
http://wit.ru/js/navigate.js
http/1.1
494.45200001355
995.15199998859
2506
6630
200
application/javascript
Script
https://mc.yandex.ru/metrika/tag.js
h2
509.04700008687
992.33100004494
71382
223752
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
692.21600005403
699.39000008162
20313
49377
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j91&a=1024084159&t=pageview&_s=1&dl=http%3A%2F%2Fwit.ru%2F&ul=en-us&de=UTF-8&dt=%D0%A1%D0%B5%D1%80%D0%B2%D0%B5%D1%80%D1%8B%20%D0%98%D0%BD%D1%82%D0%B5%D0%BB%20%D0%B8%20%D0%A1%D1%83%D0%BF%D0%B5%D1%80%D0%BC%D0%B8%D0%BA%D1%80%D0%BE%2C%20%D0%B4%D0%B8%D1%81%D0%BA%D0%BE%D0%B2%D1%8B%D0%B5%20%D1%85%D1%80%D0%B0%D0%BD%D0%B8%D0%BB%D0%B8%D1%89%D0%B0%20Infortrend%2C%20%D1%82%D0%B5%D1%80%D0%BC%D0%BE%D1%88%D0%BA%D0%B0%D1%84%D1%8B%2C%20%D0%BB%D0%B8%D1%86%D0%B5%D0%BD%D0%B7%D0%B8%D0%BE%D0%BD%D0%BD%D0%BE%D0%B5%20%D0%BF%D1%80%D0%BE%D0%B3%D1%80%D0%B0%D0%BC%D0%BC%D0%BD%D0%BE%D0%B5%20%D0%BE%D0%B1%D0%B5%D1%81%D0%BF%D0%B5%D1%87%D0%B5%D0%BD%D0%B8%D0%B5&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YEBAAUABAAAAAC~&jid=419178266&gjid=1476369123&cid=1079760999.1624334106&tid=UA-141526195-1&_gid=585181156.1624334106&_r=1&gtm=2ou6g0&z=2010565510
h2
982.55499999505
996.16600002628
630
1
200
text/plain
XHR
https://mc.yandex.ru/watch/22701025?wmode=7&page-url=http%3A%2F%2Fwit.ru%2F&charset=utf-8&browser-info=pv%3A1%3Agdpr%3A14%3Avf%3Alvg2sn1re60e0fel%3Afu%3A0%3Aen%3Autf-8%3Ala%3Aen-US%3Av%3A562%3Acn%3A1%3Adp%3A0%3Als%3A571336697316%3Ahid%3A24849086%3Az%3A-420%3Ai%3A20210621205506%3Aet%3A1624334106%3Ac%3A1%3Arn%3A863915721%3Arqn%3A1%3Au%3A1624334106222589951%3Aw%3A1350x940%3As%3A800x600x24%3Ask%3A1%3Antf%3A1%3Ans%3A1624334105150%3Ads%3A0%2C0%2C393%2C0%2C1%2C0%2C%2C%2C%2C%2C%2C%2C%3Adsn%3A0%2C0%2C%2C0%2C0%2C0%2C%2C%2C%2C%2C%2C%2C%3Awv%3A2%3Arqnl%3A1%3Ati%3A2%3Ast%3A1624334107%3At%3A%D0%A1%D0%B5%D1%80%D0%B2%D0%B5%D1%80%D1%8B%20%D0%98%D0%BD%D1%82%D0%B5%D0%BB%20%D0%B8%20%D0%A1%D1%83%D0%BF%D0%B5%D1%80%D0%BC%D0%B8%D0%BA%D1%80%D0%BE%2C%20%D0%B4%D0%B8%D1%81%D0%BA%D0%BE%D0%B2%D1%8B%D0%B5%20%D1%85%D1%80%D0%B0%D0%BD%D0%B8%D0%BB%D0%B8%D1%89%D0%B0%20Infortrend%2C%20%D1%82%D0%B5%D1%80%D0%BC%D0%BE%D1%88%D0%BA%D0%B0%D1%84%D1%8B%2C%20%D0%BB%D0%B8%D1%86%D0%B5%D0%BD%D0%B7%D0%B8%D0%BE%D0%BD%D0%BD%D0%BE%D0%B5%20%D0%BF%D1%80%D0%BE%D0%B3%D1%80%D0%B0%D0%BC%D0%BC%D0%BD%D0%BE%D0%B5%20%D0%BE%D0%B1%D0%B5%D1%81%D0%BF%D0%B5%D1%87%D0%B5%D0%BD%D0%B8%D0%B5
http/1.1
1618.5779999942
1788.4360000025
2273
0
302
https://mc.yandex.ru/metrika/advert.gif
h2
1689.3990000244
1883.6870000232
374
43
200
image/gif
Image
https://mc.yandex.ru/watch/22701025/1?wmode=7&page-url=http%3A%2F%2Fwit.ru%2F&charset=utf-8&browser-info=pv%3A1%3Agdpr%3A14%3Avf%3Alvg2sn1re60e0fel%3Afu%3A0%3Aen%3Autf-8%3Ala%3Aen-US%3Av%3A562%3Acn%3A1%3Adp%3A0%3Als%3A571336697316%3Ahid%3A24849086%3Az%3A-420%3Ai%3A20210621205506%3Aet%3A1624334106%3Ac%3A1%3Arn%3A863915721%3Arqn%3A1%3Au%3A1624334106222589951%3Aw%3A1350x940%3As%3A800x600x24%3Ask%3A1%3Antf%3A1%3Ans%3A1624334105150%3Ads%3A0%2C0%2C393%2C0%2C1%2C0%2C%2C%2C%2C%2C%2C%2C%3Adsn%3A0%2C0%2C%2C0%2C0%2C0%2C%2C%2C%2C%2C%2C%2C%3Awv%3A2%3Arqnl%3A1%3Ati%3A2%3Ast%3A1624334107%3At%3A%D0%A1%D0%B5%D1%80%D0%B2%D0%B5%D1%80%D1%8B%20%D0%98%D0%BD%D1%82%D0%B5%D0%BB%20%D0%B8%20%D0%A1%D1%83%D0%BF%D0%B5%D1%80%D0%BC%D0%B8%D0%BA%D1%80%D0%BE%2C%20%D0%B4%D0%B8%D1%81%D0%BA%D0%BE%D0%B2%D1%8B%D0%B5%20%D1%85%D1%80%D0%B0%D0%BD%D0%B8%D0%BB%D0%B8%D1%89%D0%B0%20Infortrend%2C%20%D1%82%D0%B5%D1%80%D0%BC%D0%BE%D1%88%D0%BA%D0%B0%D1%84%D1%8B%2C%20%D0%BB%D0%B8%D1%86%D0%B5%D0%BD%D0%B7%D0%B8%D0%BE%D0%BD%D0%BD%D0%BE%D0%B5%20%D0%BF%D1%80%D0%BE%D0%B3%D1%80%D0%B0%D0%BC%D0%BC%D0%BD%D0%BE%D0%B5%20%D0%BE%D0%B1%D0%B5%D1%81%D0%BF%D0%B5%D1%87%D0%B5%D0%BD%D0%B8%D0%B5
h2
1789.1750000417
1982.8720000805
674
184
200
application/json
XHR
https://mc.yandex.ru/webvisor/22701025?wmode=0&wv-part=1&wv-hit=24849086&page-url=http%3A%2F%2Fwit.ru%2F&rn=564638629&wv-type=3&browser-info=bt%3A1%3Agdpr%3A14%3Aet%3A1624334110%3Aw%3A1350x940%3Av%3A562%3Az%3A-420%3Ai%3A20210621205509%3Au%3A1624334106222589951%3Avf%3Alvg2sn1re60e0fel%3Awe%3A1%3Ati%3A2%3Ast%3A1624334110
h2
4813.2459999761
4986.9640000397
477
43
200
image/gif
XHR
https://mc.yandex.ru/webvisor/22701025?wmode=0&wv-part=1&wv-hit=24849086&page-url=http%3A%2F%2Fwit.ru%2F&rn=1001067629&wv-type=3&browser-info=gdpr%3A14%3Aet%3A1624334110%3Aw%3A1350x940%3Av%3A562%3Az%3A-420%3Ai%3A202106212055010%3Au%3A1624334106222589951%3Avf%3Alvg2sn1re60e0fel%3Awe%3A1%3Ati%3A2%3Ast%3A1624334110
h2
4898.6880000448
5082.5269999914
477
43
200
image/gif
XHR
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
488.515
12.209
502.614
71.802
574.993
15.462
687.572
12.413
700.503
80.86
799.155
205.763
1005.82
67.43
1088.892
89.281
1194.229
514.299
1708.55
7.801
1716.89
62.908
1787.207
86.719
1977.998
5.071
2074.405
6.523
2081.199
8.458
2289.435
10.208
2499.607
106.47
2674.484
20.735
2745.244
27.528
2792.377
14.273
2822.62
50.419
2993.737
20.34
3063.976
27.727
3141.621
31.204
3222.722
50.129
3372.375
123.991
3923.205
52.882
4801.392
103.635
4905.368
70.839
6327.562
44.925
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

Speed Index — 1.5 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 270 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

First Meaningful Paint — 1.0 s
The time taken for the primary content of the page to be rendered.

Diagnostics

Reduce JavaScript execution time — 1.4 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://mc.yandex.ru/metrika/tag.js
1273.159
1064.057
6.995
http://wit.ru/
268.005
52.365
2.226
https://www.google-analytics.com/analytics.js
207.251
111.865
1.755
Unattributable
184.496
6.294
0.235
https://www.googletagmanager.com/gtag/js?id=UA-141526195-1
96.531
92.081
2.988
http://wit.ru/js/ajax.js
56.101
0.34
55.628
Minimize main-thread work — 2.1 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
1327.084
Style & Layout
352.305
Other
209.881
Rendering
96.678
Script Parsing & Compilation
71.203
Parse HTML & CSS
20.545
Garbage Collection
11.675

Other

Max Potential First Input Delay — 260 ms
Users could experience a delay when interacting with the page.

Diagnostics

Serve static assets with an efficient cache policy — 25 resources found
Wit.ru can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
http://wit.ru/images/sannas/GS3016.png
0
33888
http://wit.ru/images/server/sys-7048r-tr.png
0
27864
http://wit.ru/css/style.css
0
9770
http://wit.ru/images/wit_logo_81.png
0
6914
http://wit.ru/images/microsoft175.png
0
4524
http://wit.ru/js/ajax.js
0
3617
http://wit.ru/js/navigate.js
0
2506
http://wit.ru/images/loupe_icon-29.png
0
2421
http://wit.ru/images/cart_icon-white.png
0
2276
http://wit.ru/images/wit_logo.gif
0
2199
http://wit.ru/images/menu/racks-icon.png
0
2126
http://wit.ru/images/menu/about-icon.png
0
2054
http://wit.ru/images/menu/support-icon.png
0
2040
http://wit.ru/images/menu/ups-icon.png
0
2006
http://wit.ru/images/menu/delivery-icon.png
0
1985
http://wit.ru/images/menu/software-icon.png
0
1770
http://wit.ru/images/menu/storage-icon.png
0
1691
http://wit.ru/images/menu/thermoracks-icon.png
0
1659
http://wit.ru/images/menu/lease-icon.png
0
1638
http://wit.ru/images/menu/network-icon.png
0
1582
http://wit.ru/images/menu/computers-icon.png
0
1579
http://wit.ru/images/menu/servers-icon.png
0
1451
https://mc.yandex.ru/metrika/tag.js
3600000
71382
https://mc.yandex.ru/metrika/advert.gif
3600000
374
https://www.google-analytics.com/analytics.js
7200000
20313
Reduce the impact of third-party code — Third-party code blocked the main thread for 670 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
75657
541.792
20943
99.589
37069
30.1
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
http://wit.ru/images/wit_logo_81.png
http://wit.ru/images/loupe_icon-29.png
http://wit.ru/images/cart_icon-white.png
http://wit.ru/images/wit_logo.gif
http://wit.ru/images/menu/racks-icon.png
http://wit.ru/images/menu/about-icon.png
http://wit.ru/images/menu/support-icon.png
http://wit.ru/images/menu/ups-icon.png
http://wit.ru/images/menu/delivery-icon.png
http://wit.ru/images/menu/software-icon.png
http://wit.ru/images/menu/storage-icon.png
http://wit.ru/images/menu/thermoracks-icon.png
http://wit.ru/images/menu/lease-icon.png
img
http://wit.ru/images/menu/network-icon.png
http://wit.ru/images/menu/computers-icon.png
http://wit.ru/images/menu/servers-icon.png
73

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of wit.ru. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

Background and foreground colors have a sufficient contrast ratio
Many (if not most) users find low-contrast text difficult or impossible to read.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Wit.ru may provide assistance to deaf or hearing-impaired users with captions on videos.

Navigation

Heading elements are not in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
Failing Elements

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
Failing Elements

Tables and lists

Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
Failing Elements

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
80

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that wit.ru should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 23 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://wit.ru/
Allowed
http://wit.ru/css/style.css
Allowed
http://wit.ru/images/menu/servers-icon.png
Allowed
http://wit.ru/images/menu/computers-icon.png
Allowed
http://wit.ru/images/menu/storage-icon.png
Allowed
http://wit.ru/images/menu/network-icon.png
Allowed
http://wit.ru/images/menu/software-icon.png
Allowed
http://wit.ru/images/menu/ups-icon.png
Allowed
http://wit.ru/images/menu/racks-icon.png
Allowed
http://wit.ru/images/menu/thermoracks-icon.png
Allowed
http://wit.ru/images/menu/about-icon.png
Allowed
http://wit.ru/images/menu/support-icon.png
Allowed
http://wit.ru/images/menu/delivery-icon.png
Allowed
http://wit.ru/images/menu/lease-icon.png
Allowed
http://wit.ru/images/wit_logo_81.png
Allowed
http://wit.ru/images/cart_icon-white.png
Allowed
http://wit.ru/images/loupe_icon-29.png
Allowed
http://wit.ru/images/server/sys-7048r-tr.png
Allowed
http://wit.ru/images/sannas/GS3016.png
Allowed
http://wit.ru/images/microsoft175.png
Allowed
http://wit.ru/images/wit_logo.gif
Allowed
http://wit.ru/js/ajax.js
Allowed
http://wit.ru/js/navigate.js
Allowed

Audits

Displays images with incorrect aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
URL Aspect Ratio (Displayed) Aspect Ratio (Actual)
http://wit.ru/images/sannas/GS3016.png
175 x 113 (1.55)
250 x 150 (1.67)
http://wit.ru/images/server/sys-7048r-tr.png
175 x 113 (1.55)
250 x 150 (1.67)

Audits

Registers an `unload` listener
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Source
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for wit.ru. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of wit.ru on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
18

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of wit.ru. This includes details about web app manifests.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of wit.ru on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 69
Performance 88
Accessibility 73
Best Practices 73
SEO 95
Progressive Web App 17
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
88

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for wit.ru. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Speed Index — 2.8 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 3.1 s
The time taken for the page to become fully interactive.
Total Blocking Time — 180 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.001
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Max Potential First Input Delay — 130 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://wit.ru/
http/1.1
0
148.93600007053
12449
32017
200
text/html
Document
https://www.googletagmanager.com/gtag/js?id=UA-141526195-1
h2
163.57900004368
190.0649999734
37072
91512
200
application/javascript
Script
http://wit.ru/css/style.css
http/1.1
163.75199996401
312.49499996193
9770
35169
200
text/css
Stylesheet
http://wit.ru/images/menu/servers-icon.png
http/1.1
168.10000000987
575.73599996977
1451
1202
200
image/png
Image
http://wit.ru/images/menu/computers-icon.png
http/1.1
168.35000005085
536.12199996132
1579
1330
200
image/png
Image
http://wit.ru/images/menu/storage-icon.png
http/1.1
168.4870000463
314.74800000433
1691
1442
200
image/png
Image
http://wit.ru/images/menu/network-icon.png
http/1.1
168.68500004057
315.65999996383
1582
1333
200
image/png
Image
http://wit.ru/images/menu/software-icon.png
http/1.1
168.84499997832
420.94300000463
1770
1521
200
image/png
Image
http://wit.ru/images/menu/ups-icon.png
http/1.1
168.98299998138
420.60299997684
2006
1758
200
image/png
Image
http://wit.ru/images/menu/racks-icon.png
http/1.1
169.15400000289
332.4390000198
2126
1877
200
image/png
Image
http://wit.ru/images/menu/thermoracks-icon.png
http/1.1
169.41299999598
465.83600004669
1659
1410
200
image/png
Image
http://wit.ru/images/menu/about-icon.png
http/1.1
169.63200003374
366.66599998716
2054
1805
200
image/png
Image
http://wit.ru/images/menu/support-icon.png
http/1.1
169.76600000635
316.19200005662
2040
1791
200
image/png
Image
http://wit.ru/images/menu/delivery-icon.png
http/1.1
169.9250000529
313.80300002638
1985
1736
200
image/png
Image
http://wit.ru/images/menu/lease-icon.png
http/1.1
170.10600003414
315.94999996014
1638
1389
200
image/png
Image
http://wit.ru/images/wit_logo_81.png
http/1.1
170.28500000015
315.26399997529
6914
6666
200
image/png
Image
http://wit.ru/images/cart_icon-white.png
http/1.1
170.46000005212
583.15299998503
2276
2027
200
image/png
Image
http://wit.ru/images/loupe_icon-29.png
http/1.1
170.56400002912
313.0339999916
2421
2172
200
image/png
Image
http://wit.ru/images/server/sys-7048r-tr.png
http/1.1
170.78000004403
583.96800002083
27864
27614
200
image/png
Image
http://wit.ru/images/sannas/GS3016.png
http/1.1
170.970999985
448.68000003044
33888
33638
200
image/png
Image
http://wit.ru/images/microsoft175.png
http/1.1
171.21499998029
314.07500000205
4524
4275
200
image/png
Image
http://wit.ru/images/wit_logo.gif
http/1.1
171.98199999984
2314.7330000065
2199
1950
200
image/gif
Image
http://wit.ru/js/ajax.js
http/1.1
167.65099996701
313.44699999318
3617
10199
200
application/javascript
Script
http://wit.ru/js/navigate.js
http/1.1
167.92999999598
310.91200001538
2506
6630
200
application/javascript
Script
https://mc.yandex.ru/metrika/tag.js
h2
172.11400007363
581.79600001313
71382
223752
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
216.52100002393
221.14300006069
20221
49153
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j90&a=258021524&t=pageview&_s=1&dl=http%3A%2F%2Fwit.ru%2F&ul=en-us&de=UTF-8&dt=%D0%A1%D0%B5%D1%80%D0%B2%D0%B5%D1%80%D1%8B%20%D0%98%D0%BD%D1%82%D0%B5%D0%BB%20%D0%B8%20%D0%A1%D1%83%D0%BF%D0%B5%D1%80%D0%BC%D0%B8%D0%BA%D1%80%D0%BE%2C%20%D0%B4%D0%B8%D1%81%D0%BA%D0%BE%D0%B2%D1%8B%D0%B5%20%D1%85%D1%80%D0%B0%D0%BD%D0%B8%D0%BB%D0%B8%D1%89%D0%B0%20Infortrend%2C%20%D1%82%D0%B5%D1%80%D0%BC%D0%BE%D1%88%D0%BA%D0%B0%D1%84%D1%8B%2C%20%D0%BB%D0%B8%D1%86%D0%B5%D0%BD%D0%B7%D0%B8%D0%BE%D0%BD%D0%BD%D0%BE%D0%B5%20%D0%BF%D1%80%D0%BE%D0%B3%D1%80%D0%B0%D0%BC%D0%BC%D0%BD%D0%BE%D0%B5%20%D0%BE%D0%B1%D0%B5%D1%81%D0%BF%D0%B5%D1%87%D0%B5%D0%BD%D0%B8%D0%B5&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=YEBAAUABAAAAAC~&jid=941179128&gjid=1951307910&cid=251354389.1624334145&tid=UA-141526195-1&_gid=1269726009.1624334145&_r=1&gtm=2ou6g0&z=762527416
h2
269.1750000231
272.38300000317
630
1
200
text/plain
XHR
https://mc.yandex.ru/watch/22701025?wmode=7&page-url=http%3A%2F%2Fwit.ru%2F&charset=utf-8&browser-info=pv%3A1%3Agdpr%3A14%3Avf%3Alvg2sn1re60e0fel%3Afp%3A345%3Afu%3A0%3Aen%3Autf-8%3Ala%3Aen-US%3Av%3A562%3Acn%3A1%3Adp%3A0%3Als%3A1466687272297%3Ahid%3A209308262%3Az%3A-420%3Ai%3A20210621205545%3Aet%3A1624334145%3Ac%3A1%3Arn%3A936934532%3Arqn%3A1%3Au%3A1624334145876304671%3Aw%3A360x640%3As%3A360x640x24%3Ask%3A2.625%3Antf%3A1%3Ans%3A1624334144455%3Ads%3A0%2C0%2C150%2C0%2C0%2C0%2C%2C218%2C0%2C%2C%2C%2C372%3Adsn%3A0%2C0%2C%2C0%2C0%2C0%2C%2C222%2C1%2C%2C%2C%2C372%3Awv%3A2%3Arqnl%3A1%3Ati%3A2%3Ast%3A1624334145%3At%3A%D0%A1%D0%B5%D1%80%D0%B2%D0%B5%D1%80%D1%8B%20%D0%98%D0%BD%D1%82%D0%B5%D0%BB%20%D0%B8%20%D0%A1%D1%83%D0%BF%D0%B5%D1%80%D0%BC%D0%B8%D0%BA%D1%80%D0%BE%2C%20%D0%B4%D0%B8%D1%81%D0%BA%D0%BE%D0%B2%D1%8B%D0%B5%20%D1%85%D1%80%D0%B0%D0%BD%D0%B8%D0%BB%D0%B8%D1%89%D0%B0%20Infortrend%2C%20%D1%82%D0%B5%D1%80%D0%BC%D0%BE%D1%88%D0%BA%D0%B0%D1%84%D1%8B%2C%20%D0%BB%D0%B8%D1%86%D0%B5%D0%BD%D0%B7%D0%B8%D0%BE%D0%BD%D0%BD%D0%BE%D0%B5%20%D0%BF%D1%80%D0%BE%D0%B3%D1%80%D0%B0%D0%BC%D0%BC%D0%BD%D0%BE%D0%B5%20%D0%BE%D0%B1%D0%B5%D1%81%D0%BF%D0%B5%D1%87%D0%B5%D0%BD%D0%B8%D0%B5
http/1.1
662.76400000788
803.36400005035
2303
0
302
https://mc.yandex.ru/metrika/advert.gif
h2
666.3379999809
821.63400005084
374
43
200
image/gif
Image
https://mc.yandex.ru/watch/22701025/1?wmode=7&page-url=http%3A%2F%2Fwit.ru%2F&charset=utf-8&browser-info=pv%3A1%3Agdpr%3A14%3Avf%3Alvg2sn1re60e0fel%3Afp%3A345%3Afu%3A0%3Aen%3Autf-8%3Ala%3Aen-US%3Av%3A562%3Acn%3A1%3Adp%3A0%3Als%3A1466687272297%3Ahid%3A209308262%3Az%3A-420%3Ai%3A20210621205545%3Aet%3A1624334145%3Ac%3A1%3Arn%3A936934532%3Arqn%3A1%3Au%3A1624334145876304671%3Aw%3A360x640%3As%3A360x640x24%3Ask%3A2.625%3Antf%3A1%3Ans%3A1624334144455%3Ads%3A0%2C0%2C150%2C0%2C0%2C0%2C%2C218%2C0%2C%2C%2C%2C372%3Adsn%3A0%2C0%2C%2C0%2C0%2C0%2C%2C222%2C1%2C%2C%2C%2C372%3Awv%3A2%3Arqnl%3A1%3Ati%3A2%3Ast%3A1624334145%3At%3A%D0%A1%D0%B5%D1%80%D0%B2%D0%B5%D1%80%D1%8B%20%D0%98%D0%BD%D1%82%D0%B5%D0%BB%20%D0%B8%20%D0%A1%D1%83%D0%BF%D0%B5%D1%80%D0%BC%D0%B8%D0%BA%D1%80%D0%BE%2C%20%D0%B4%D0%B8%D1%81%D0%BA%D0%BE%D0%B2%D1%8B%D0%B5%20%D1%85%D1%80%D0%B0%D0%BD%D0%B8%D0%BB%D0%B8%D1%89%D0%B0%20Infortrend%2C%20%D1%82%D0%B5%D1%80%D0%BC%D0%BE%D1%88%D0%BA%D0%B0%D1%84%D1%8B%2C%20%D0%BB%D0%B8%D1%86%D0%B5%D0%BD%D0%B7%D0%B8%D0%BE%D0%BD%D0%BD%D0%BE%D0%B5%20%D0%BF%D1%80%D0%BE%D0%B3%D1%80%D0%B0%D0%BC%D0%BC%D0%BD%D0%BE%D0%B5%20%D0%BE%D0%B1%D0%B5%D1%81%D0%BF%D0%B5%D1%87%D0%B5%D0%BD%D0%B8%D0%B5
h2
803.65799996071
950.30899997801
674
184
200
application/json
XHR
https://mc.yandex.ru/webvisor/22701025?wmode=0&wv-part=1&wv-hit=209308262&page-url=http%3A%2F%2Fwit.ru%2F&rn=509514682&wv-type=3&browser-info=bt%3A1%3Agdpr%3A14%3Aet%3A1624334148%3Aw%3A360x640%3Av%3A562%3Az%3A-420%3Ai%3A20210621205547%3Au%3A1624334145876304671%3Avf%3Alvg2sn1re60e0fel%3Awe%3A1%3Ati%3A2%3Ast%3A1624334148
h2
3415.8339999849
3586.9470000034
477
43
200
image/gif
XHR
https://mc.yandex.ru/webvisor/22701025?wmode=0&wv-part=1&wv-hit=209308262&page-url=http%3A%2F%2Fwit.ru%2F&rn=889952371&wv-type=3&browser-info=gdpr%3A14%3Aet%3A1624334148%3Aw%3A360x640%3Av%3A562%3Az%3A-420%3Ai%3A20210621205547%3Au%3A1624334145876304671%3Avf%3Alvg2sn1re60e0fel%3Awe%3A1%3Ati%3A2%3Ast%3A1624334148
h2
3429.2660000501
3569.8560000164
477
43
200
image/gif
XHR
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
160.302
7.846
170.96
8.492
207.691
7.557
215.91
8.711
234.559
43.479
324.239
21.03
350.788
7.754
360.763
16.549
610.668
60.138
962.504
8.4
1170.826
26.138
1242.125
21.944
1314.002
30.785
1392.468
7.586
1400.191
32.848
3397.277
28.664
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Opportunities

Eliminate render-blocking resources — Potential savings of 0 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Wit.ru should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
http://wit.ru/css/style.css
9770
180
Properly size images
Images can slow down the page's load time. Wit.ru should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Wit.ru should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 3 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Wit.ru should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://wit.ru/css/style.css
9770
3081
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Wit.ru should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Wit.ru should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 150 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
http://wit.ru/
149.933
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Wit.ru should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Wit.ru should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 257 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://mc.yandex.ru/metrika/tag.js
71382
https://www.googletagmanager.com/gtag/js?id=UA-141526195-1
37072
http://wit.ru/images/sannas/GS3016.png
33888
http://wit.ru/images/server/sys-7048r-tr.png
27864
https://www.google-analytics.com/analytics.js
20221
http://wit.ru/
12449
http://wit.ru/css/style.css
9770
http://wit.ru/images/wit_logo_81.png
6914
http://wit.ru/images/microsoft175.png
4524
http://wit.ru/js/ajax.js
3617
Avoids an excessive DOM size — 421 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
421
Maximum DOM Depth
b
12
Maximum Child Elements
17
Avoid chaining critical requests — 3 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Wit.ru should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 1.2 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://mc.yandex.ru/metrika/tag.js
1016.52
945.752
21.26
http://wit.ru/
494.776
14.5
6.736
https://www.google-analytics.com/analytics.js
179.984
91.296
4.744
Unattributable
141.696
10.348
0.8
https://www.googletagmanager.com/gtag/js?id=UA-141526195-1
71.404
59.612
8.472
Minimizes main-thread work — 1.9 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
1122.508
Style & Layout
350.164
Other
263.14
Rendering
79.132
Script Parsing & Compilation
46.016
Parse HTML & CSS
44.48
Garbage Collection
13.76
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 32 requests • 257 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
32
263619
Script
5
134798
Image
20
102041
Document
1
12449
Stylesheet
1
9770
Other
5
4561
Media
0
0
Font
0
0
Third-party
9
133610
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 2 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.00085677083333333
0
0.00018359375
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 7 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://mc.yandex.ru/metrika/tag.js
3047
131
https://mc.yandex.ru/metrika/tag.js
2807
123
https://mc.yandex.ru/metrika/tag.js
2494
120
https://mc.yandex.ru/metrika/tag.js
3178
115
https://mc.yandex.ru/metrika/tag.js
2614
105
https://mc.yandex.ru/metrika/tag.js
2719
88
https://www.google-analytics.com/analytics.js
2930
87
Avoid non-composited animations — 2 animated elements found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
×

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

First Contentful Paint — 2.8 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 2.9 s
The timing of the largest text or image that is painted.

Other

First Meaningful Paint — 2.8 s
The time taken for the primary content of the page to be rendered.

Opportunities

Reduce unused JavaScript — Potential savings of 34 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://mc.yandex.ru/metrika/tag.js
71382
34466
Serve images in next-gen formats — Potential savings of 51 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://wit.ru/images/sannas/GS3016.png
33638
28714
http://wit.ru/images/server/sys-7048r-tr.png
27614
23716

Diagnostics

Serve static assets with an efficient cache policy — 25 resources found
Wit.ru can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
http://wit.ru/images/sannas/GS3016.png
0
33888
http://wit.ru/images/server/sys-7048r-tr.png
0
27864
http://wit.ru/css/style.css
0
9770
http://wit.ru/images/wit_logo_81.png
0
6914
http://wit.ru/images/microsoft175.png
0
4524
http://wit.ru/js/ajax.js
0
3617
http://wit.ru/js/navigate.js
0
2506
http://wit.ru/images/loupe_icon-29.png
0
2421
http://wit.ru/images/cart_icon-white.png
0
2276
http://wit.ru/images/wit_logo.gif
0
2199
http://wit.ru/images/menu/racks-icon.png
0
2126
http://wit.ru/images/menu/about-icon.png
0
2054
http://wit.ru/images/menu/support-icon.png
0
2040
http://wit.ru/images/menu/ups-icon.png
0
2006
http://wit.ru/images/menu/delivery-icon.png
0
1985
http://wit.ru/images/menu/software-icon.png
0
1770
http://wit.ru/images/menu/storage-icon.png
0
1691
http://wit.ru/images/menu/thermoracks-icon.png
0
1659
http://wit.ru/images/menu/lease-icon.png
0
1638
http://wit.ru/images/menu/network-icon.png
0
1582
http://wit.ru/images/menu/computers-icon.png
0
1579
http://wit.ru/images/menu/servers-icon.png
0
1451
https://mc.yandex.ru/metrika/tag.js
3600000
71382
https://mc.yandex.ru/metrika/advert.gif
3600000
374
https://www.google-analytics.com/analytics.js
7200000
20221
Reduce the impact of third-party code — Third-party code blocked the main thread for 480 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
75687
423.832
20851
58.6
37072
0
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
http://wit.ru/images/wit_logo_81.png
http://wit.ru/images/loupe_icon-29.png
http://wit.ru/images/cart_icon-white.png
http://wit.ru/images/wit_logo.gif
http://wit.ru/images/menu/racks-icon.png
http://wit.ru/images/menu/about-icon.png
http://wit.ru/images/menu/support-icon.png
http://wit.ru/images/menu/ups-icon.png
http://wit.ru/images/menu/delivery-icon.png
http://wit.ru/images/menu/software-icon.png
http://wit.ru/images/menu/storage-icon.png
http://wit.ru/images/menu/thermoracks-icon.png
http://wit.ru/images/menu/lease-icon.png
img
http://wit.ru/images/menu/network-icon.png
http://wit.ru/images/menu/computers-icon.png
http://wit.ru/images/menu/servers-icon.png

Other

First Contentful Paint (3G) — 5346 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
73

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of wit.ru. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Wit.ru may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Navigation

Heading elements are not in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
Failing Elements

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
Failing Elements

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
73

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that wit.ru should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 23 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://wit.ru/
Allowed
http://wit.ru/css/style.css
Allowed
http://wit.ru/images/menu/servers-icon.png
Allowed
http://wit.ru/images/menu/computers-icon.png
Allowed
http://wit.ru/images/menu/storage-icon.png
Allowed
http://wit.ru/images/menu/network-icon.png
Allowed
http://wit.ru/images/menu/software-icon.png
Allowed
http://wit.ru/images/menu/ups-icon.png
Allowed
http://wit.ru/images/menu/racks-icon.png
Allowed
http://wit.ru/images/menu/thermoracks-icon.png
Allowed
http://wit.ru/images/menu/about-icon.png
Allowed
http://wit.ru/images/menu/support-icon.png
Allowed
http://wit.ru/images/menu/delivery-icon.png
Allowed
http://wit.ru/images/menu/lease-icon.png
Allowed
http://wit.ru/images/wit_logo_81.png
Allowed
http://wit.ru/images/cart_icon-white.png
Allowed
http://wit.ru/images/loupe_icon-29.png
Allowed
http://wit.ru/images/server/sys-7048r-tr.png
Allowed
http://wit.ru/images/sannas/GS3016.png
Allowed
http://wit.ru/images/microsoft175.png
Allowed
http://wit.ru/images/wit_logo.gif
Allowed
http://wit.ru/js/ajax.js
Allowed
http://wit.ru/js/navigate.js
Allowed

Audits

Displays images with incorrect aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
URL Aspect Ratio (Displayed) Aspect Ratio (Actual)
http://wit.ru/images/sannas/GS3016.png
175 x 113 (1.55)
250 x 150 (1.67)
http://wit.ru/images/server/sys-7048r-tr.png
175 x 113 (1.55)
250 x 150 (1.67)
Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
http://wit.ru/images/sannas/GS3016.png
175 x 113
250 x 150
350 x 226
http://wit.ru/images/server/sys-7048r-tr.png
175 x 113
250 x 150
350 x 226
http://wit.ru/images/wit_logo_81.png
74 x 81
74 x 81
148 x 162
http://wit.ru/images/cart_icon-white.png
42 x 40
42 x 40
84 x 80
http://wit.ru/images/loupe_icon-29.png
29 x 29
29 x 29
58 x 58
http://wit.ru/images/menu/about-icon.png
20 x 20
20 x 20
40 x 40
http://wit.ru/images/menu/computers-icon.png
20 x 20
20 x 20
40 x 40
http://wit.ru/images/menu/delivery-icon.png
20 x 20
20 x 20
40 x 40
http://wit.ru/images/menu/lease-icon.png
20 x 20
20 x 20
40 x 40
http://wit.ru/images/menu/network-icon.png
20 x 20
20 x 20
40 x 40
http://wit.ru/images/menu/racks-icon.png
20 x 20
20 x 20
40 x 40
http://wit.ru/images/menu/servers-icon.png
20 x 20
20 x 20
40 x 40
http://wit.ru/images/menu/software-icon.png
20 x 20
20 x 20
40 x 40
http://wit.ru/images/menu/storage-icon.png
20 x 20
20 x 20
40 x 40
http://wit.ru/images/menu/support-icon.png
20 x 20
20 x 20
40 x 40
http://wit.ru/images/menu/thermoracks-icon.png
20 x 20
20 x 20
40 x 40
http://wit.ru/images/menu/ups-icon.png
20 x 20
20 x 20
40 x 40

Audits

Registers an `unload` listener
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Source
95

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for wit.ru. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of wit.ru on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
100.00%
≥ 12px

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Tap targets are not sized appropriately — 38% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.
Tap Target Size Overlapping Target
165x14
217x14
161x14

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
17

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of wit.ru. This includes details about web app manifests.

PWA Optimized

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of wit.ru on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is not sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 81.177.166.40
Continent: Europe
Country: Russia
Russia Flag
Region:
City:
Longitude: 37.6068
Latitude: 55.7386
Currencies: RUB
Languages: Russian

Web Hosting Provider

Name IP Address
In-Solve/1Gb.ru hosting services provider
Registration

Domain Registrant

Private Registration: No
Name:
Organization: WIT Company
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness: 75/100
WOT Child Safety: 97/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: wit.ru
Issued By: Thawte RSA CA 2018
Valid From: 22nd June, 2020
Valid To: 5th August, 2021
Subject: CN = wit.ru
O = OOO WIT Company
L = Moscow
S = RU
Hash: 82a69056
Issuer: CN = Thawte RSA CA 2018
OU = www.digicert.com
O = DigiCert Inc
S = US
Version: 2
Serial Number: 20503260167829149967997724794589870220
Serial Number (Hex): 0F6CC8C603FF02602A521B3EAFFCF88C
Valid From: 22nd June, 2024
Valid To: 5th August, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:A3:C8:5E:65:54:E5:30:78:C1:05:EA:07:0A:6A:59:CC:B9:FE:DE:5A
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://cdp.thawte.com/ThawteRSACA2018.crl

Certificate Policies: Policy: 2.16.840.1.114412.1.1
CPS: https://www.digicert.com/CPS
Policy: 2.23.140.1.2.2

Authority Information Access: OCSP - URI:http://status.thawte.com
CA Issuers - URI:http://cacerts.thawte.com/ThawteRSACA2018.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
Timestamp : Jun 22 15:06:03.602 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:58:AB:D5:00:2D:53:D0:DB:C1:AE:EE:BC:
F9:89:70:DA:7A:6B:24:66:FB:AD:EA:FA:F2:1D:AE:E5:
6D:6F:46:5A:02:20:0F:7D:71:20:0E:E5:D5:17:FF:D1:
80:E4:AC:24:31:51:30:50:E8:8F:2D:FA:2C:06:4A:26:
AC:03:E4:8E:23:08
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
Timestamp : Jun 22 15:06:03.648 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:43:3D:C6:CC:F5:C7:A4:13:28:AF:51:AB:
57:EB:F4:3F:A3:86:86:47:6B:2D:EB:3A:7B:80:2D:4D:
82:C8:2B:05:02:20:64:1F:AC:22:E5:9A:8F:4F:EF:4D:
F0:A2:F7:C5:82:1D:B8:93:5D:5C:D2:DF:DC:CC:D6:5A:
4F:64:93:C2:83:D0
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:www.wit.ru
DNS:wit.ru
Technical

DNS Lookup

SOA Records

Domain Name Primary NS Responsible Email TTL
wit.ru. ns3-l2.nic.ru. support.wit.ru. 3599

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html; charset=utf-8
Server: Microsoft-IIS/10.0
Date: 22nd June, 2021
Content-Length: 32017
Set-Cookie: *
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET

Whois Lookup

Created: 21st October, 1996
Changed:
Expires: 31st October, 2021
Registrar: RU-CENTER-RU
Status:
Nameservers: ns3-l2.nic.ru
ns4-cloud.nic.ru
ns4-l2.nic.ru
ns8-cloud.nic.ru
ns8-l2.nic.ru
Owner Organization: WIT Company
Full Whois: % By submitting a query to RIPN's Whois Service
% you agree to abide by the following terms of use:
% http://www.ripn.net/about/servpol.html#3.2 (in Russian)
% http://www.ripn.net/about/en/servpol.html#3.2 (in English).

domain: WIT.RU
nserver: ns3-l2.nic.ru.
nserver: ns4-cloud.nic.ru.
nserver: ns4-l2.nic.ru.
nserver: ns8-cloud.nic.ru.
nserver: ns8-l2.nic.ru.
state: REGISTERED, DELEGATED, VERIFIED
org: WIT Company
registrar: RU-CENTER-RU
admin-contact: https://www.nic.ru/whois
created: 1996-10-21T15:36:33Z
paid-till: 2021-10-31T21:00:00Z
free-date: 2021-12-02
source: TCI

Last updated on 2021-06-22T03:51:30Z

Nameservers

Name IP Address
ns3-l2.nic.ru 193.232.146.1
ns4-cloud.nic.ru 89.104.93.30
ns4-l2.nic.ru 91.217.20.20
ns8-cloud.nic.ru 89.104.93.31
ns8-l2.nic.ru 91.217.21.20
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
$1,995 USD 2/5
0/5
$3,961 USD 1/5
0/5
0/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
$459 USD
0/5

Sites hosted on the same IP address