sasisa.ru

sasisa.ru is SSL secured

Free website and domain report on sasisa.ru

Last Updated: 30th October, 2023 Update Now
Overview

Snoop Summary for sasisa.ru

This is a free and comprehensive report about sasisa.ru. Sasisa.ru is hosted in Paris, Île-de-France in France on a server with an IP address of 212.129.52.124, where the local currency is EUR and French is the local language. Sasisa.ru is expected to earn an estimated $18 USD per day from advertising revenue. The sale of sasisa.ru would possibly be worth $13,093 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Sasisa.ru is very popular with an estimated 6,288 daily unique visitors. This report was last updated 30th October, 2023.

About sasisa.ru

Site Preview:
Title: SASISA.ru: Мобильный WAP портал развлечений и общения - бесплатный мобильный сайт
Description: SASISA.ru - Мобильный сайт загрузок, игр, приложений, музыки, бесплатных картинок, свежих горячих новостей. Регистрируйтесь, общайтесь, скачивайте и загружайте файлы. Общайтесь на форуме.
Keywords and Tags: blogs, popular, sasisa, wiki, бесплатное, главная, мобильный портал
Related Terms:
Fav Icon:
Age: Over 19 years old
Domain Created: 12th January, 2005
Domain Updated:
Domain Expires: 12th January, 2024
Review

Snoop Score

3/5 (Great!)

Valuation

$13,093 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 78,774
Alexa Reach: 0.0006%
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Rank By Country

Country Alexa Rank
Latvia Flag Latvia 518
Russian Federation Flag Russian Federation 7,298

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 6,288
Monthly Visitors: 191,395
Yearly Visitors: 2,295,223
Note: All visitors figures are estimates.

Visitors By Country

Country Visitors (Unique) Percentage
Latvia Flag Latvia Daily: 1,195
Monthly: 36,365
Yearly: 436,092
19%
Other Daily: 1,214
Monthly: 36,939
Yearly: 442,978
19.3%
Russian Federation Flag Russian Federation Daily: 3,880
Monthly: 118,091
Yearly: 1,416,153
61.7%
Note: All visitors figures are estimates.
Revenue

Revenue

Daily Revenue: $18 USD
Monthly Revenue: $545 USD
Yearly Revenue: $6,541 USD
Note: All revenue figures are estimates.

Revenue By Country

Country Revenue Percentage
Latvia Flag Latvia Daily: $1 USD
Monthly: $20 USD
Yearly: $241 USD
3.7%
Other Daily: $0 USD
Monthly: $0 USD
Yearly: $0 USD
<0.1%
Russian Federation Flag Russian Federation Daily: $17 USD
Monthly: $525 USD
Yearly: $6,301 USD
96.3%
Note: All revenue figures are estimates.
SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: sasisa.ru 9
Domain Name: sasisa 6
Extension (TLD): ru 2
Expiry Check:

Page Speed Analysis

Average Load Time: 0.31 seconds
Load Time Comparison: Faster than 98% of sites

PageSpeed Insights

Avg. (All Categories) 72
Performance 99
Accessibility 62
Best Practices 83
SEO 92
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://sasisa.ru
Updated: 2nd February, 2023

0.35 seconds
First Contentful Paint (FCP)
99%
1%
0%

0.00 seconds
First Input Delay (FID)
100%
0%
0%

99

Performance

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

Metrics

First Contentful Paint — 0.2 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.7 s
The time taken for the page to become fully interactive.
Speed Index — 0.2 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 0 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).
Largest Contentful Paint — 0.5 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.088
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 60 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.2 s
The time taken for the primary content of the page to be rendered.
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://sasisa.ru/
http/1.1
0
124.24999999348
6361
18244
200
text/html
Document
http://sasisa.ru/images/sock.gif
http/1.1
132.85299995914
229.40099996049
2253
1997
200
image/gif
Image
http://sasisa.ru/images/logo/logo2.gif
http/1.1
132.99499999266
231.89499997534
3383
3127
200
image/gif
Image
http://sasisa.ru/images/fol.gif
http/1.1
141.92399999592
279.25299992785
741
486
200
image/gif
Image
http://cstat.wap.sasisa.ru/3932576246/counter3.gif
http/1.1
142.07599998917
225.99099995568
288
35
200
image/gif
Image
http://duamilsyr.com/i/npage/1815622/code.js
http/1.1
142.23100000527
872.68599995878
62659
213897
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
158.88300002553
163.85999997146
20593
50234
200
text/javascript
Script
https://mc.yandex.ru/metrika/watch.js
h2
159.75799993612
305.4589999374
58779
166106
200
application/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j99&a=1009384865&t=pageview&_s=1&dl=http%3A%2F%2Fsasisa.ru%2F&ul=en-us&de=UTF-8&dt=SASISA.ru%3A%20%D0%9C%D0%BE%D0%B1%D0%B8%D0%BB%D1%8C%D0%BD%D1%8B%D0%B9%20WAP%20%D0%BF%D0%BE%D1%80%D1%82%D0%B0%D0%BB%20%D1%80%D0%B0%D0%B7%D0%B2%D0%BB%D0%B5%D1%87%D0%B5%D0%BD%D0%B8%D0%B9%20%D0%B8%20%D0%BE%D0%B1%D1%89%D0%B5%D0%BD%D0%B8%D1%8F%20-%20%D0%B1%D0%B5%D1%81%D0%BF%D0%BB%D0%B0%D1%82%D0%BD%D1%8B%D0%B9%20%D0%BC%D0%BE%D0%B1%D0%B8%D0%BB%D1%8C%D0%BD%D1%8B%D0%B9%20%D1%81%D0%B0%D0%B9%D1%82&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAEABAAAAACAAI~&jid=1215405808&gjid=1120217965&cid=1859378366.1675323141&tid=UA-43108437-6&_gid=34155150.1675323141&_r=1&_slc=1&z=1974861809
h2
193.77499993425
199.97199997306
493
4
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j99&tid=UA-43108437-6&cid=1859378366.1675323141&jid=1215405808&gjid=1120217965&_gid=34155150.1675323141&_u=IEBAAEAAAAAAACAAI~&z=1202034074
h2
202.67899997998
208.62599997781
563
1
200
text/plain
XHR
https://mc.yandex.ru/watch/49004468?wmode=7&page-url=http%3A%2F%2Fsasisa.ru%2F&charset=utf-8&browser-info=pv%3A1%3Avf%3A3kqlg6e9sjiwxr6f2njdv%3Afp%3A184%3Afu%3A0%3Aen%3Autf-8%3Ala%3Aen-US%3Av%3A960%3Acn%3A1%3Adp%3A0%3Als%3A780168105368%3Ahid%3A567470715%3Az%3A-480%3Ai%3A20230201233221%3Aet%3A1675323141%3Ac%3A1%3Arn%3A631552051%3Arqn%3A1%3Au%3A1675323141922190693%3Aw%3A1350x940%3As%3A800x600x24%3Ask%3A1%3Ads%3A0%2C0%2C%2C0%2C0%2C0%2C%2C36%2C0%2C%2C%2C%2C161%3Aco%3A0%3Antf%3A1%3Ans%3A1675323141073%3Arqnl%3A1%3Ast%3A1675323141%3At%3ASASISA.ru%3A%20%D0%9C%D0%BE%D0%B1%D0%B8%D0%BB%D1%8C%D0%BD%D1%8B%D0%B9%20WAP%20%D0%BF%D0%BE%D1%80%D1%82%D0%B0%D0%BB%20%D1%80%D0%B0%D0%B7%D0%B2%D0%BB%D0%B5%D1%87%D0%B5%D0%BD%D0%B8%D0%B9%20%D0%B8%20%D0%BE%D0%B1%D1%89%D0%B5%D0%BD%D0%B8%D1%8F%20-%20%D0%B1%D0%B5%D1%81%D0%BF%D0%BB%D0%B0%D1%82%D0%BD%D1%8B%D0%B9%20%D0%BC%D0%BE%D0%B1%D0%B8%D0%BB%D1%8C%D0%BD%D1%8B%D0%B9%20%D1%81%D0%B0%D0%B9%D1%82&t=gdpr(14)clc(0-0-0)rqnt(1)aw(1)ti(2)
http/1.1
364.62000000756
423.07200003415
2447
0
302
text/plain
https://mc.yandex.ru/metrika/advert.gif
h2
365.95999996644
424.79900002945
664
43
200
image/gif
Image
https://mc.yandex.ru/watch/49004468/1?wmode=7&page-url=http%3A%2F%2Fsasisa.ru%2F&charset=utf-8&browser-info=pv%3A1%3Avf%3A3kqlg6e9sjiwxr6f2njdv%3Afp%3A184%3Afu%3A0%3Aen%3Autf-8%3Ala%3Aen-US%3Av%3A960%3Acn%3A1%3Adp%3A0%3Als%3A780168105368%3Ahid%3A567470715%3Az%3A-480%3Ai%3A20230201233221%3Aet%3A1675323141%3Ac%3A1%3Arn%3A631552051%3Arqn%3A1%3Au%3A1675323141922190693%3Aw%3A1350x940%3As%3A800x600x24%3Ask%3A1%3Ads%3A0%2C0%2C%2C0%2C0%2C0%2C%2C36%2C0%2C%2C%2C%2C161%3Aco%3A0%3Antf%3A1%3Ans%3A1675323141073%3Arqnl%3A1%3Ast%3A1675323141%3At%3ASASISA.ru%3A%20%D0%9C%D0%BE%D0%B1%D0%B8%D0%BB%D1%8C%D0%BD%D1%8B%D0%B9%20WAP%20%D0%BF%D0%BE%D1%80%D1%82%D0%B0%D0%BB%20%D1%80%D0%B0%D0%B7%D0%B2%D0%BB%D0%B5%D1%87%D0%B5%D0%BD%D0%B8%D0%B9%20%D0%B8%20%D0%BE%D0%B1%D1%89%D0%B5%D0%BD%D0%B8%D1%8F%20-%20%D0%B1%D0%B5%D1%81%D0%BF%D0%BB%D0%B0%D1%82%D0%BD%D1%8B%D0%B9%20%D0%BC%D0%BE%D0%B1%D0%B8%D0%BB%D1%8C%D0%BD%D1%8B%D0%B9%20%D1%81%D0%B0%D0%B9%D1%82&t=gdpr%2814%29clc%280-0-0%29rqnt%281%29aw%281%29ti%282%29
h2
423.41199994553
476.37899999972
1211
428
200
application/json
XHR
https://duamilsyr.com/get/1815622?zoneid=1815622&jp=_cl66whzmm1vqqfplkc1qxm&nojs=0&ix=0&abvar=2&t=0&x=1350&y=940&wcks=1&wgl=1&cnvs=1&os=480&md=0&bb=0&lang=en-US&pf=Linux%20x86_64&cd=24&freq=0&cid=5457818534996207
h2
949.67699993867
1456.1220000032
958
7
200
text/javascript
Script
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)
128.908
11.646
144.18
11.946
156.8
5.682
171.723
23.214
319.646
45.569
894.676
55.98
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.

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Sasisa.ru should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Sasisa.ru should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Sasisa.ru should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Sasisa.ru should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Sasisa.ru should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Sasisa.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 32 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/watch.js
58779
32504
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
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 130 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://sasisa.ru/
125.239
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Sasisa.ru should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Sasisa.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.
Avoids enormous network payloads — Total size was 158 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
http://duamilsyr.com/i/npage/1815622/code.js
62659
https://mc.yandex.ru/metrika/watch.js
58779
https://www.google-analytics.com/analytics.js
20593
http://sasisa.ru/
6361
http://sasisa.ru/images/logo/logo2.gif
3383
https://mc.yandex.ru/watch/49004468?wmode=7&page-url=http%3A%2F%2Fsasisa.ru%2F&charset=utf-8&browser-info=pv%3A1%3Avf%3A3kqlg6e9sjiwxr6f2njdv%3Afp%3A184%3Afu%3A0%3Aen%3Autf-8%3Ala%3Aen-US%3Av%3A960%3Acn%3A1%3Adp%3A0%3Als%3A780168105368%3Ahid%3A567470715%3Az%3A-480%3Ai%3A20230201233221%3Aet%3A1675323141%3Ac%3A1%3Arn%3A631552051%3Arqn%3A1%3Au%3A1675323141922190693%3Aw%3A1350x940%3As%3A800x600x24%3Ask%3A1%3Ads%3A0%2C0%2C%2C0%2C0%2C0%2C%2C36%2C0%2C%2C%2C%2C161%3Aco%3A0%3Antf%3A1%3Ans%3A1675323141073%3Arqnl%3A1%3Ast%3A1675323141%3At%3ASASISA.ru%3A%20%D0%9C%D0%BE%D0%B1%D0%B8%D0%BB%D1%8C%D0%BD%D1%8B%D0%B9%20WAP%20%D0%BF%D0%BE%D1%80%D1%82%D0%B0%D0%BB%20%D1%80%D0%B0%D0%B7%D0%B2%D0%BB%D0%B5%D1%87%D0%B5%D0%BD%D0%B8%D0%B9%20%D0%B8%20%D0%BE%D0%B1%D1%89%D0%B5%D0%BD%D0%B8%D1%8F%20-%20%D0%B1%D0%B5%D1%81%D0%BF%D0%BB%D0%B0%D1%82%D0%BD%D1%8B%D0%B9%20%D0%BC%D0%BE%D0%B1%D0%B8%D0%BB%D1%8C%D0%BD%D1%8B%D0%B9%20%D1%81%D0%B0%D0%B9%D1%82&t=gdpr(14)clc(0-0-0)rqnt(1)aw(1)ti(2)
2447
http://sasisa.ru/images/sock.gif
2253
https://mc.yandex.ru/watch/49004468/1?wmode=7&page-url=http%3A%2F%2Fsasisa.ru%2F&charset=utf-8&browser-info=pv%3A1%3Avf%3A3kqlg6e9sjiwxr6f2njdv%3Afp%3A184%3Afu%3A0%3Aen%3Autf-8%3Ala%3Aen-US%3Av%3A960%3Acn%3A1%3Adp%3A0%3Als%3A780168105368%3Ahid%3A567470715%3Az%3A-480%3Ai%3A20230201233221%3Aet%3A1675323141%3Ac%3A1%3Arn%3A631552051%3Arqn%3A1%3Au%3A1675323141922190693%3Aw%3A1350x940%3As%3A800x600x24%3Ask%3A1%3Ads%3A0%2C0%2C%2C0%2C0%2C0%2C%2C36%2C0%2C%2C%2C%2C161%3Aco%3A0%3Antf%3A1%3Ans%3A1675323141073%3Arqnl%3A1%3Ast%3A1675323141%3At%3ASASISA.ru%3A%20%D0%9C%D0%BE%D0%B1%D0%B8%D0%BB%D1%8C%D0%BD%D1%8B%D0%B9%20WAP%20%D0%BF%D0%BE%D1%80%D1%82%D0%B0%D0%BB%20%D1%80%D0%B0%D0%B7%D0%B2%D0%BB%D0%B5%D1%87%D0%B5%D0%BD%D0%B8%D0%B9%20%D0%B8%20%D0%BE%D0%B1%D1%89%D0%B5%D0%BD%D0%B8%D1%8F%20-%20%D0%B1%D0%B5%D1%81%D0%BF%D0%BB%D0%B0%D1%82%D0%BD%D1%8B%D0%B9%20%D0%BC%D0%BE%D0%B1%D0%B8%D0%BB%D1%8C%D0%BD%D1%8B%D0%B9%20%D1%81%D0%B0%D0%B9%D1%82&t=gdpr%2814%29clc%280-0-0%29rqnt%281%29aw%281%29ti%282%29
1211
https://duamilsyr.com/get/1815622?zoneid=1815622&jp=_cl66whzmm1vqqfplkc1qxm&nojs=0&ix=0&abvar=2&t=0&x=1350&y=940&wcks=1&wgl=1&cnvs=1&os=480&md=0&bb=0&lang=en-US&pf=Linux%20x86_64&cd=24&freq=0&cid=5457818534996207
958
http://sasisa.ru/images/fol.gif
741
Avoids an excessive DOM size — 179 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
179
Maximum DOM Depth
4
Maximum Child Elements
53
Avoid chaining critical requests
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Sasisa.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 — 0.1 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/watch.js
62.234
57.364
2.688
http://duamilsyr.com/i/npage/1815622/code.js
55.98
52.754
3.079
http://sasisa.ru/
50.97
5.389
2.051
Minimizes main-thread work — 0.2 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
140.492
Other
34.099
Style & Layout
13.943
Rendering
10.735
Script Parsing & Compilation
8.717
Parse HTML & CSS
4.217
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 — 14 requests • 158 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
14
161393
Script
4
142989
Image
5
7329
Document
1
6361
Other
4
4714
Stylesheet
0
0
Media
0
0
Font
0
0
Third-party
9
148367
Minimize third-party usage — Third-party code blocked the main thread for 0 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)
63101
0
21086
0
563
0
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
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.0099664470711847
0.0099664470711847
0.0099664470711847
0.0099664470711847
0.0099664470711847
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 — 1 long task 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)
http://duamilsyr.com/i/npage/1815622/code.js
628
56
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
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 sasisa.ru on mobile screens.
Avoids `unload` event listeners
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.

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

Serve static assets with an efficient cache policy — 9 resources found
Sasisa.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://duamilsyr.com/i/npage/1815622/code.js
0
62659
http://sasisa.ru/images/logo/logo2.gif
0
3383
http://sasisa.ru/images/sock.gif
0
2253
https://duamilsyr.com/get/1815622?zoneid=1815622&jp=_cl66whzmm1vqqfplkc1qxm&nojs=0&ix=0&abvar=2&t=0&x=1350&y=940&wcks=1&wgl=1&cnvs=1&os=480&md=0&bb=0&lang=en-US&pf=Linux%20x86_64&cd=24&freq=0&cid=5457818534996207
0
958
http://sasisa.ru/images/fol.gif
0
741
http://cstat.wap.sasisa.ru/3932576246/counter3.gif
0
288
https://mc.yandex.ru/metrika/watch.js
3600000
58779
https://mc.yandex.ru/metrika/advert.gif
3600000
664
https://www.google-analytics.com/analytics.js
7200000
20593
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
http://sasisa.ru/images/logo/logo2.gif
http://sasisa.ru/images/sock.gif
http://sasisa.ru/images/fol.gif
http://sasisa.ru/images/fol.gif
http://sasisa.ru/images/fol.gif
http://sasisa.ru/images/fol.gif
http://sasisa.ru/images/fol.gif
http://sasisa.ru/images/fol.gif
http://sasisa.ru/images/fol.gif
http://sasisa.ru/images/fol.gif
http://sasisa.ru/images/fol.gif
http://sasisa.ru/images/fol.gif
http://sasisa.ru/images/fol.gif
http://sasisa.ru/images/fol.gif
http://sasisa.ru/images/fol.gif
http://sasisa.ru/images/fol.gif
http://sasisa.ru/images/fol.gif
http://sasisa.ru/images/fol.gif
http://sasisa.ru/images/fol.gif
http://sasisa.ru/images/fol.gif
http://sasisa.ru/images/fol.gif
http://sasisa.ru/images/fol.gif
http://sasisa.ru/images/fol.gif
http://sasisa.ru/images/fol.gif
http://sasisa.ru/images/fol.gif
http://sasisa.ru/images/fol.gif
http://sasisa.ru/images/fol.gif
http://sasisa.ru/images/fol.gif
http://sasisa.ru/images/fol.gif
http://sasisa.ru/images/fol.gif
http://sasisa.ru/images/fol.gif
http://sasisa.ru/images/fol.gif
http://sasisa.ru/images/fol.gif
http://cstat.wap.sasisa.ru/3932576246/counter3.gif
62

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of sasisa.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.
Heading elements appear 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.
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.
`<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.
`<object>` elements have alternate 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.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Sasisa.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

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

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
Links do not 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.

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

Best Practices

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

Audits

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.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
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

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

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 — 6 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://sasisa.ru/
Allowed
http://sasisa.ru/images/sock.gif
Allowed
http://sasisa.ru/images/logo/logo2.gif
Allowed
http://sasisa.ru/images/fol.gif
Allowed
http://cstat.wap.sasisa.ru/3932576246/counter3.gif
Allowed
http://duamilsyr.com/i/npage/1815622/code.js
Allowed

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
92

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for sasisa.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 sasisa.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.
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.

Content Best Practices

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

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

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of sasisa.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 sasisa.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.
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 85
Accessibility 66
Best Practices 75
SEO 90
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://sasisa.ru/
Updated: 2nd February, 2023

1.08 seconds
First Contentful Paint (FCP)
89%
6%
5%

0.02 seconds
First Input Delay (FID)
96%
3%
1%

85

Performance

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

Metrics

First Contentful Paint — 0.7 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 2.6 s
The time taken for the page to become fully interactive.
Speed Index — 1.4 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 80 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).
Largest Contentful Paint — 1.6 s
The timing of the largest text or image that is painted.

Audits

First Meaningful Paint — 0.7 s
The time taken for the primary content of the page to be rendered.
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://sasisa.ru/
http/1.1
0
213.99699999893
5220
16018
200
text/html
Document
http://sasisa.ru/images/sock.gif
http/1.1
221.52500000084
259.50100000773
2253
1997
200
image/gif
Image
http://sasisa.ru/images/logo/logo2.gif
http/1.1
221.6960000078
354.23900000751
3383
3127
200
image/gif
Image
http://sasisa.ru/images/touch/icons_8m/ucweb/4v.gif
http/1.1
228.36500000267
254.93400001142
5005
4748
200
image/gif
Image
http://sasisa.ru/images/touch/icons_8m/ucweb/5v.gif
http/1.1
228.52000000421
372.17500001134
5127
4870
200
image/gif
Image
http://sasisa.ru/images/touch/icons_8m/ucweb/2v.gif
http/1.1
228.8860000117
321.61900000938
4910
4653
200
image/gif
Image
http://sasisa.ru/images/touch/icons_8m/calend/32_2.gif
http/1.1
229.60099999909
337.73700000893
1825
1569
200
image/gif
Image
http://sasisa.ru/images/touch/icons_8m/22.gif
http/1.1
229.88900000928
341.03200001118
1794
1538
200
image/gif
Image
http://sasisa.ru/images/touch/icons_8m/31.gif
http/1.1
229.95400000946
272.46500000183
1816
1560
200
image/gif
Image
http://sasisa.ru/images/touch/icons_8m/30.gif
http/1.1
230.361000009
601.27600000123
1764
1508
200
image/gif
Image
http://sasisa.ru/images/touch/icons_8m/1.gif
http/1.1
230.55800001021
328.67800000531
1913
1657
200
image/gif
Image
http://sasisa.ru/images/touch/icons_8m/19a.gif
http/1.1
230.62400000344
412.66400000313
1851
1595
200
image/gif
Image
http://sasisa.ru/images/touch/icons_8m/3.gif
http/1.1
230.71400000481
358.82100000163
1854
1598
200
image/gif
Image
http://sasisa.ru/images/touch/icons_8m/21.gif
http/1.1
230.80699999991
333.69100000709
1769
1513
200
image/gif
Image
http://sasisa.ru/images/touch/icons_8m/23a.gif
http/1.1
230.85700000229
273.11600001121
1864
1608
200
image/gif
Image
http://sasisa.ru/images/touch/icons_8m/6.gif
http/1.1
231.59999999916
271.96300000651
1784
1528
200
image/gif
Image
http://sasisa.ru/images/touch/icons_8m/7.gif
http/1.1
231.82100000849
330.71999999811
1840
1584
200
image/gif
Image
http://sasisa.ru/images/touch/icons_8m/8.gif
http/1.1
232.71200001182
269.17100000719
1862
1606
200
image/gif
Image
http://sasisa.ru/images/touch/icons_8m/9.gif
http/1.1
232.78600000776
322.35300001048
1913
1657
200
image/gif
Image
http://sasisa.ru/images/touch/icons_8m/10.gif
http/1.1
232.85300000862
371.04300000647
1778
1522
200
image/gif
Image
http://sasisa.ru/images/touch/icons_8m/11.gif
http/1.1
232.91000000609
334.06800001103
1832
1576
200
image/gif
Image
http://sasisa.ru/images/touch/icons_8m/12.gif
http/1.1
233.00000000745
273.56100000907
1857
1601
200
image/gif
Image
http://sasisa.ru/images/touch/icons_8m/13.gif
http/1.1
233.05500000424
334.78900000046
1813
1557
200
image/gif
Image
http://sasisa.ru/images/touch/icons_8m/14.gif
http/1.1
233.12100001203
371.63600001077
1905
1649
200
image/gif
Image
http://sasisa.ru/images/touch/icons_8m/15.gif
http/1.1
233.1780000095
349.87900000124
1873
1617
200
image/gif
Image
http://sasisa.ru/images/touch/icons_8m/16.gif
http/1.1
233.49900000903
335.27500000491
1743
1487
200
image/gif
Image
http://sasisa.ru/images/touch/icons_8m/17.gif
http/1.1
233.58100000769
365.26900000172
1933
1677
200
image/gif
Image
http://sasisa.ru/images/touch/icons_8m/18.gif
http/1.1
233.64400000719
322.58500000171
1840
1584
200
image/gif
Image
http://sasisa.ru/images/touch/icons_8m/24.gif
http/1.1
233.70599999907
374.18500000786
1853
1597
200
image/gif
Image
http://sasisa.ru/images/touch/icons_8m/20.gif
http/1.1
233.78300000331
334.60100000957
1804
1548
200
image/gif
Image
http://sasisa.ru/images/touch/icons_8m/5.gif
http/1.1
233.85800000688
266.98200000101
1882
1626
200
image/gif
Image
http://sasisa.ru/images/touch/icons_8m/28.gif
http/1.1
233.95200000959
362.32800000289
2067
1811
200
image/gif
Image
http://sasisa.ru/images/touch/icons_8m/1n.gif
http/1.1
234.11200000555
348.41200000665
3216
2960
200
image/gif
Image
http://sasisa.ru/images/touch/icons_8m/2n.gif
http/1.1
234.21600001166
367.11200000718
2940
2684
200
image/gif
Image
http://sasisa.ru/images/touch/icons_8m/3n.gif
http/1.1
234.34799999814
362.08800000895
3202
2946
200
image/gif
Image
http://cstat.wap.sasisa.ru/9663943621/counter3.gif
http/1.1
234.42800001067
319.44600000861
288
35
200
image/gif
Image
http://tstat.wap.sasisa.ru/9663943621/counter3.gif
http/1.1
234.4790000061
359.30200001167
288
35
200
image/gif
Image
http://duamilsyr.com/i/npage/1815622/code.js
http/1.1
234.6530000068
938.86700000439
62781
214009
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
246.04300000647
251.58100000408
20594
50234
200
text/javascript
Script
https://mc.yandex.ru/metrika/watch.js
h2
246.38399999822
349.54900000594
58832
166301
200
application/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j99&a=2112405845&t=pageview&_s=1&dl=http%3A%2F%2Fsasisa.ru%2F&ul=en-us&de=UTF-8&dt=SASISA.ru%3A%20%D0%9C%D0%BE%D0%B1%D0%B8%D0%BB%D1%8C%D0%BD%D1%8B%D0%B9%20WAP%20%D0%BF%D0%BE%D1%80%D1%82%D0%B0%D0%BB%20%D1%80%D0%B0%D0%B7%D0%B2%D0%BB%D0%B5%D1%87%D0%B5%D0%BD%D0%B8%D0%B9%20%D0%B8%20%D0%BE%D0%B1%D1%89%D0%B5%D0%BD%D0%B8%D1%8F%20-%20%D0%B1%D0%B5%D1%81%D0%BF%D0%BB%D0%B0%D1%82%D0%BD%D1%8B%D0%B9%20%D0%BC%D0%BE%D0%B1%D0%B8%D0%BB%D1%8C%D0%BD%D1%8B%D0%B9%20%D1%81%D0%B0%D0%B9%D1%82&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=IEBAAEABAAAAACAAI~&jid=288846822&gjid=221464260&cid=1307501246.1675323158&tid=UA-43108437-6&_gid=452427841.1675323158&_r=1&_slc=1&z=379393108
h2
273.50700000534
277.00700001151
493
4
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j99&tid=UA-43108437-6&cid=1307501246.1675323158&jid=288846822&gjid=221464260&_gid=452427841.1675323158&_u=IEBAAEAAAAAAACAAI~&z=1372375707
h2
280.05500001018
283.56399999757
563
1
200
text/plain
XHR
https://mc.yandex.com/sync_cookie_image_check
http/1.1
393.81500000309
452.62799999909
526
0
302
text/plain
https://mc.yandex.com/metrika/advert.gif
h2
400.9950000036
457.61300000595
664
43
200
image/gif
Image
https://mc.yandex.ru/sync_cookie_image_start?redirect_domain=mc.yandex.com&token=9902.A3iGXS0WR8fXeg-S11x0bgIKJbYv2j70MAQfPlZ13I0GPvVz0BUY3HhvULzz4Mak.ruUC9UMUK3xNN5wZjs6_rGjPHbQ%2C
http/1.1
452.89500000945
508.25400000031
544
0
302
text/plain
https://mc.yandex.com/sync_cookie_image_decide?token=9902.HWOs08HKb4MJXMm94YMbSgCv8WnblxH5XQzaVQoNX8JgM9t1hlO4p4079Vwy5MLPue1Kw5cCdlhsn_34W9v_oOFA9D2FkOBRwqo_4zbjH2w%2C.GTX91CKiIfrTDhH38SdbA2aRaWo%2C
h2
508.54500000423
557.73900001077
217
43
200
image/gif
Image
https://mc.yandex.com/watch/49004468?wmode=7&page-url=http%3A%2F%2Fsasisa.ru%2F&charset=utf-8&browser-info=pv%3A1%3Avf%3A3llbk0t3v1opl3fs6ve8z%3Afp%3A250%3Afu%3A0%3Aen%3Autf-8%3Ala%3Aen-US%3Av%3A960%3Acn%3A1%3Adp%3A0%3Als%3A757294243004%3Ahid%3A135338752%3Az%3A-480%3Ai%3A20230201233238%3Aet%3A1675323158%3Ac%3A1%3Arn%3A629478371%3Arqn%3A1%3Au%3A1675323158659009430%3Aw%3A360x640%3As%3A360x640x24%3Ask%3A2.625%3Ads%3A0%2C0%2C%2C0%2C0%2C0%2C%2C33%2C0%2C%2C%2C%2C248%3Aco%3A0%3Antf%3A1%3Ans%3A1675323157866%3Aadb%3A2%3Arqnl%3A1%3Ast%3A1675323158%3At%3ASASISA.ru%3A%20%D0%9C%D0%BE%D0%B1%D0%B8%D0%BB%D1%8C%D0%BD%D1%8B%D0%B9%20WAP%20%D0%BF%D0%BE%D1%80%D1%82%D0%B0%D0%BB%20%D1%80%D0%B0%D0%B7%D0%B2%D0%BB%D0%B5%D1%87%D0%B5%D0%BD%D0%B8%D0%B9%20%D0%B8%20%D0%BE%D0%B1%D1%89%D0%B5%D0%BD%D0%B8%D1%8F%20-%20%D0%B1%D0%B5%D1%81%D0%BF%D0%BB%D0%B0%D1%82%D0%BD%D1%8B%D0%B9%20%D0%BC%D0%BE%D0%B1%D0%B8%D0%BB%D1%8C%D0%BD%D1%8B%D0%B9%20%D1%81%D0%B0%D0%B9%D1%82&t=gdpr(14)clc(0-0-0)rqnt(1)aw(1)ti(2)
http/1.1
560.67600000824
613.62699999881
2464
0
302
text/plain
https://mc.yandex.com/watch/49004468/1?wmode=7&page-url=http%3A%2F%2Fsasisa.ru%2F&charset=utf-8&browser-info=pv%3A1%3Avf%3A3llbk0t3v1opl3fs6ve8z%3Afp%3A250%3Afu%3A0%3Aen%3Autf-8%3Ala%3Aen-US%3Av%3A960%3Acn%3A1%3Adp%3A0%3Als%3A757294243004%3Ahid%3A135338752%3Az%3A-480%3Ai%3A20230201233238%3Aet%3A1675323158%3Ac%3A1%3Arn%3A629478371%3Arqn%3A1%3Au%3A1675323158659009430%3Aw%3A360x640%3As%3A360x640x24%3Ask%3A2.625%3Ads%3A0%2C0%2C%2C0%2C0%2C0%2C%2C33%2C0%2C%2C%2C%2C248%3Aco%3A0%3Antf%3A1%3Ans%3A1675323157866%3Aadb%3A2%3Arqnl%3A1%3Ast%3A1675323158%3At%3ASASISA.ru%3A%20%D0%9C%D0%BE%D0%B1%D0%B8%D0%BB%D1%8C%D0%BD%D1%8B%D0%B9%20WAP%20%D0%BF%D0%BE%D1%80%D1%82%D0%B0%D0%BB%20%D1%80%D0%B0%D0%B7%D0%B2%D0%BB%D0%B5%D1%87%D0%B5%D0%BD%D0%B8%D0%B9%20%D0%B8%20%D0%BE%D0%B1%D1%89%D0%B5%D0%BD%D0%B8%D1%8F%20-%20%D0%B1%D0%B5%D1%81%D0%BF%D0%BB%D0%B0%D1%82%D0%BD%D1%8B%D0%B9%20%D0%BC%D0%BE%D0%B1%D0%B8%D0%BB%D1%8C%D0%BD%D1%8B%D0%B9%20%D1%81%D0%B0%D0%B9%D1%82&t=gdpr%2814%29clc%280-0-0%29rqnt%281%29aw%281%29ti%282%29
h2
613.8890000002
672.18400001002
1211
428
200
application/json
XHR
https://mc.yandex.com/sync_cookie_image_check_secondary
http/1.1
674.43700000877
727.0370000042
539
0
302
text/plain
https://mc.yandex.ru/sync_cookie_image_start_secondary?redirect_domain=mc.yandex.com&token=9902.fxhxi8vLHbZ4OLaGngM1ai9iiBJzNKMdVebRqZvclHJQr4T0S3BTCKYLhmmbTfFO.16CWt-rs0YkIrxBQYoKjghmMSbU%2C
http/1.1
727.42000001017
783.96200000134
555
0
302
text/plain
https://mc.yandex.com/sync_cookie_image_decide_secondary?token=9902.yEoMK94v99xHTixNe5bXP6c2LpaWhG3Kz8D4Lu1Clf16Nuac034MWZdxdpCY6nb0g28LYu9JqI5W0fWQGYpwELEuA9EZycYPEoKATi4GFyk%2C.CXvOcXIAVLd1QfY91DOchsEc4gQ%2C
h2
784.21199999866
832.44300000661
217
43
200
image/gif
Image
https://duamilsyr.com/get/1815622?zoneid=1815622&jp=_cllqs750t6odmhmgzfzo7g&nojs=0&ix=0&abvar=3&t=1&x=801&y=801&wcks=1&wgl=1&cnvs=1&os=480&md=0&bb=0&lang=en-US&pf=Linux%20x86_64&cd=24&freq=0&cid=4613393605874250
h2
1009.3540000089
1489.4730000087
958
7
200
text/javascript
Script
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)
217.452
10.346
233.006
10.697
259.058
15.48
365.658
28.899
959.976
50.343
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.

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Sasisa.ru should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Sasisa.ru should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Sasisa.ru should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Sasisa.ru should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Sasisa.ru should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Sasisa.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 32 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/watch.js
58832
32490
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
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 210 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://sasisa.ru/
214.985
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Sasisa.ru should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Sasisa.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.
Avoids enormous network payloads — Total size was 230 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
http://duamilsyr.com/i/npage/1815622/code.js
62781
https://mc.yandex.ru/metrika/watch.js
58832
https://www.google-analytics.com/analytics.js
20594
http://sasisa.ru/
5220
http://sasisa.ru/images/touch/icons_8m/ucweb/5v.gif
5127
http://sasisa.ru/images/touch/icons_8m/ucweb/4v.gif
5005
http://sasisa.ru/images/touch/icons_8m/ucweb/2v.gif
4910
http://sasisa.ru/images/logo/logo2.gif
3383
http://sasisa.ru/images/touch/icons_8m/1n.gif
3216
http://sasisa.ru/images/touch/icons_8m/3n.gif
3202
Avoids an excessive DOM size — 205 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
205
Maximum DOM Depth
8
Maximum Child Elements
20
Avoid chaining critical requests
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Sasisa.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 — 0.5 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)
http://duamilsyr.com/i/npage/1815622/code.js
201.372
186.32
14.468
http://sasisa.ru/
198.112
16.228
6.356
https://mc.yandex.ru/metrika/watch.js
180.944
159.192
11.212
Unattributable
139.908
4.8
0
https://www.google-analytics.com/analytics.js
69.884
59.376
3.84
Minimizes main-thread work — 0.8 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
426.132
Other
198.188
Style & Layout
65.78
Rendering
42.752
Script Parsing & Compilation
36.168
Parse HTML & CSS
21.956
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 — 52 requests • 230 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
52
235019
Script
4
143165
Image
39
79739
Other
8
6895
Document
1
5220
Stylesheet
0
0
Media
0
0
Font
0
0
Third-party
15
151158
Minimize third-party usage — Third-party code blocked the main thread for 50 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)
59931
48.5
21087
4.724
563
0
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
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.17525436675228
0.13771723180017
0.066731532715568
0.058436835718179
0.053776866015959
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 — 2 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)
http://duamilsyr.com/i/npage/1815622/code.js
2677
201
https://mc.yandex.ru/metrika/watch.js
2610
58
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
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 sasisa.ru on mobile screens.
Avoids `unload` event listeners
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.
First Contentful Paint (3G) — 1271 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

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.

Audits

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

Metrics

Cumulative Layout Shift — 0.678
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Serve static assets with an efficient cache policy — 43 resources found
Sasisa.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://duamilsyr.com/i/npage/1815622/code.js
0
62781
http://sasisa.ru/images/touch/icons_8m/ucweb/5v.gif
0
5127
http://sasisa.ru/images/touch/icons_8m/ucweb/4v.gif
0
5005
http://sasisa.ru/images/touch/icons_8m/ucweb/2v.gif
0
4910
http://sasisa.ru/images/logo/logo2.gif
0
3383
http://sasisa.ru/images/touch/icons_8m/1n.gif
0
3216
http://sasisa.ru/images/touch/icons_8m/3n.gif
0
3202
http://sasisa.ru/images/touch/icons_8m/2n.gif
0
2940
http://sasisa.ru/images/sock.gif
0
2253
http://sasisa.ru/images/touch/icons_8m/28.gif
0
2067
http://sasisa.ru/images/touch/icons_8m/17.gif
0
1933
http://sasisa.ru/images/touch/icons_8m/1.gif
0
1913
http://sasisa.ru/images/touch/icons_8m/9.gif
0
1913
http://sasisa.ru/images/touch/icons_8m/14.gif
0
1905
http://sasisa.ru/images/touch/icons_8m/5.gif
0
1882
http://sasisa.ru/images/touch/icons_8m/15.gif
0
1873
http://sasisa.ru/images/touch/icons_8m/23a.gif
0
1864
http://sasisa.ru/images/touch/icons_8m/8.gif
0
1862
http://sasisa.ru/images/touch/icons_8m/12.gif
0
1857
http://sasisa.ru/images/touch/icons_8m/3.gif
0
1854
http://sasisa.ru/images/touch/icons_8m/24.gif
0
1853
http://sasisa.ru/images/touch/icons_8m/19a.gif
0
1851
http://sasisa.ru/images/touch/icons_8m/18.gif
0
1840
http://sasisa.ru/images/touch/icons_8m/7.gif
0
1840
http://sasisa.ru/images/touch/icons_8m/11.gif
0
1832
http://sasisa.ru/images/touch/icons_8m/calend/32_2.gif
0
1825
http://sasisa.ru/images/touch/icons_8m/31.gif
0
1816
http://sasisa.ru/images/touch/icons_8m/13.gif
0
1813
http://sasisa.ru/images/touch/icons_8m/20.gif
0
1804
http://sasisa.ru/images/touch/icons_8m/22.gif
0
1794
http://sasisa.ru/images/touch/icons_8m/6.gif
0
1784
http://sasisa.ru/images/touch/icons_8m/10.gif
0
1778
http://sasisa.ru/images/touch/icons_8m/21.gif
0
1769
http://sasisa.ru/images/touch/icons_8m/30.gif
0
1764
http://sasisa.ru/images/touch/icons_8m/16.gif
0
1743
https://duamilsyr.com/get/1815622?zoneid=1815622&jp=_cllqs750t6odmhmgzfzo7g&nojs=0&ix=0&abvar=3&t=1&x=801&y=801&wcks=1&wgl=1&cnvs=1&os=480&md=0&bb=0&lang=en-US&pf=Linux%20x86_64&cd=24&freq=0&cid=4613393605874250
0
958
http://cstat.wap.sasisa.ru/9663943621/counter3.gif
0
288
http://tstat.wap.sasisa.ru/9663943621/counter3.gif
0
288
https://mc.yandex.com/sync_cookie_image_decide_secondary?token=9902.yEoMK94v99xHTixNe5bXP6c2LpaWhG3Kz8D4Lu1Clf16Nuac034MWZdxdpCY6nb0g28LYu9JqI5W0fWQGYpwELEuA9EZycYPEoKATi4GFyk%2C.CXvOcXIAVLd1QfY91DOchsEc4gQ%2C
0
217
https://mc.yandex.com/sync_cookie_image_decide?token=9902.HWOs08HKb4MJXMm94YMbSgCv8WnblxH5XQzaVQoNX8JgM9t1hlO4p4079Vwy5MLPue1Kw5cCdlhsn_34W9v_oOFA9D2FkOBRwqo_4zbjH2w%2C.GTX91CKiIfrTDhH38SdbA2aRaWo%2C
0
217
https://mc.yandex.ru/metrika/watch.js
3600000
58832
https://mc.yandex.com/metrika/advert.gif
3600000
664
https://www.google-analytics.com/analytics.js
7200000
20594
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
http://sasisa.ru/images/logo/logo2.gif
http://sasisa.ru/images/touch/icons_8m/ucweb/4v.gif
http://sasisa.ru/images/touch/icons_8m/ucweb/5v.gif
http://sasisa.ru/images/touch/icons_8m/ucweb/2v.gif
http://sasisa.ru/images/touch/icons_8m/1n.gif
http://sasisa.ru/images/touch/icons_8m/2n.gif
http://sasisa.ru/images/touch/icons_8m/3n.gif
http://sasisa.ru/images/touch/icons_8m/calend/32_2.gif
http://sasisa.ru/images/touch/icons_8m/22.gif
http://sasisa.ru/images/touch/icons_8m/31.gif
http://sasisa.ru/images/touch/icons_8m/30.gif
http://sasisa.ru/images/touch/icons_8m/1.gif
http://sasisa.ru/images/touch/icons_8m/19a.gif
http://sasisa.ru/images/touch/icons_8m/3.gif
http://sasisa.ru/images/touch/icons_8m/21.gif
http://sasisa.ru/images/touch/icons_8m/23a.gif
http://sasisa.ru/images/touch/icons_8m/6.gif
http://sasisa.ru/images/touch/icons_8m/7.gif
http://sasisa.ru/images/touch/icons_8m/8.gif
http://sasisa.ru/images/touch/icons_8m/9.gif
http://sasisa.ru/images/touch/icons_8m/10.gif
http://sasisa.ru/images/touch/icons_8m/11.gif
http://sasisa.ru/images/touch/icons_8m/12.gif
http://sasisa.ru/images/touch/icons_8m/13.gif
http://sasisa.ru/images/touch/icons_8m/14.gif
http://sasisa.ru/images/touch/icons_8m/15.gif
http://sasisa.ru/images/touch/icons_8m/16.gif
http://sasisa.ru/images/touch/icons_8m/17.gif
http://sasisa.ru/images/touch/icons_8m/18.gif
http://sasisa.ru/images/touch/icons_8m/24.gif
http://sasisa.ru/images/touch/icons_8m/20.gif
http://sasisa.ru/images/touch/icons_8m/5.gif
http://sasisa.ru/images/touch/icons_8m/28.gif
http://sasisa.ru/images/sock.gif
http://cstat.wap.sasisa.ru/9663943621/counter3.gif
http://tstat.wap.sasisa.ru/9663943621/counter3.gif
66

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of sasisa.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.
Heading elements appear 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.
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.
`<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.
`<object>` elements have alternate 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.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Sasisa.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

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

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
Links do not 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.

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

Best Practices

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

Audits

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.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

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

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 — 38 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://sasisa.ru/
Allowed
http://sasisa.ru/images/sock.gif
Allowed
http://sasisa.ru/images/logo/logo2.gif
Allowed
http://sasisa.ru/images/touch/icons_8m/ucweb/4v.gif
Allowed
http://sasisa.ru/images/touch/icons_8m/ucweb/5v.gif
Allowed
http://sasisa.ru/images/touch/icons_8m/ucweb/2v.gif
Allowed
http://sasisa.ru/images/touch/icons_8m/calend/32_2.gif
Allowed
http://sasisa.ru/images/touch/icons_8m/22.gif
Allowed
http://sasisa.ru/images/touch/icons_8m/31.gif
Allowed
http://sasisa.ru/images/touch/icons_8m/30.gif
Allowed
http://sasisa.ru/images/touch/icons_8m/1.gif
Allowed
http://sasisa.ru/images/touch/icons_8m/19a.gif
Allowed
http://sasisa.ru/images/touch/icons_8m/3.gif
Allowed
http://sasisa.ru/images/touch/icons_8m/21.gif
Allowed
http://sasisa.ru/images/touch/icons_8m/23a.gif
Allowed
http://sasisa.ru/images/touch/icons_8m/6.gif
Allowed
http://sasisa.ru/images/touch/icons_8m/7.gif
Allowed
http://sasisa.ru/images/touch/icons_8m/8.gif
Allowed
http://sasisa.ru/images/touch/icons_8m/9.gif
Allowed
http://sasisa.ru/images/touch/icons_8m/10.gif
Allowed
http://sasisa.ru/images/touch/icons_8m/11.gif
Allowed
http://sasisa.ru/images/touch/icons_8m/12.gif
Allowed
http://sasisa.ru/images/touch/icons_8m/13.gif
Allowed
http://sasisa.ru/images/touch/icons_8m/14.gif
Allowed
http://sasisa.ru/images/touch/icons_8m/15.gif
Allowed
http://sasisa.ru/images/touch/icons_8m/16.gif
Allowed
http://sasisa.ru/images/touch/icons_8m/17.gif
Allowed
http://sasisa.ru/images/touch/icons_8m/18.gif
Allowed
http://sasisa.ru/images/touch/icons_8m/24.gif
Allowed
http://sasisa.ru/images/touch/icons_8m/20.gif
Allowed
http://sasisa.ru/images/touch/icons_8m/5.gif
Allowed
http://sasisa.ru/images/touch/icons_8m/28.gif
Allowed
http://sasisa.ru/images/touch/icons_8m/1n.gif
Allowed
http://sasisa.ru/images/touch/icons_8m/2n.gif
Allowed
http://sasisa.ru/images/touch/icons_8m/3n.gif
Allowed
http://cstat.wap.sasisa.ru/9663943621/counter3.gif
Allowed
http://tstat.wap.sasisa.ru/9663943621/counter3.gif
Allowed
http://duamilsyr.com/i/npage/1815622/code.js
Allowed

Audits

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://sasisa.ru/images/logo/logo2.gif
94 x 70
94 x 70
188 x 140
http://sasisa.ru/images/touch/icons_8m/ucweb/2v.gif
75 x 73
75 x 73
150 x 146
http://sasisa.ru/images/touch/icons_8m/ucweb/4v.gif
75 x 73
75 x 73
150 x 146
http://sasisa.ru/images/touch/icons_8m/ucweb/5v.gif
75 x 73
75 x 73
150 x 146
http://sasisa.ru/images/touch/icons_8m/1.gif
50 x 49
50 x 49
100 x 98
http://sasisa.ru/images/touch/icons_8m/10.gif
50 x 49
50 x 49
100 x 98
http://sasisa.ru/images/touch/icons_8m/11.gif
50 x 49
50 x 49
100 x 98
http://sasisa.ru/images/touch/icons_8m/12.gif
50 x 49
50 x 49
100 x 98
http://sasisa.ru/images/touch/icons_8m/13.gif
50 x 49
50 x 49
100 x 98
http://sasisa.ru/images/touch/icons_8m/14.gif
50 x 49
50 x 49
100 x 98
http://sasisa.ru/images/touch/icons_8m/15.gif
50 x 49
50 x 49
100 x 98
http://sasisa.ru/images/touch/icons_8m/16.gif
50 x 49
50 x 49
100 x 98
http://sasisa.ru/images/touch/icons_8m/17.gif
50 x 49
50 x 49
100 x 98
http://sasisa.ru/images/touch/icons_8m/18.gif
50 x 49
50 x 49
100 x 98
http://sasisa.ru/images/touch/icons_8m/19a.gif
50 x 49
50 x 49
100 x 98
http://sasisa.ru/images/touch/icons_8m/20.gif
50 x 49
50 x 49
100 x 98
http://sasisa.ru/images/touch/icons_8m/21.gif
50 x 49
50 x 49
100 x 98
http://sasisa.ru/images/touch/icons_8m/22.gif
50 x 49
50 x 49
100 x 98
http://sasisa.ru/images/touch/icons_8m/23a.gif
50 x 49
50 x 49
100 x 98
http://sasisa.ru/images/touch/icons_8m/24.gif
50 x 49
50 x 49
100 x 98
http://sasisa.ru/images/touch/icons_8m/3.gif
50 x 49
50 x 49
100 x 98
http://sasisa.ru/images/touch/icons_8m/30.gif
50 x 49
50 x 49
100 x 98
http://sasisa.ru/images/touch/icons_8m/31.gif
50 x 49
50 x 49
100 x 98
http://sasisa.ru/images/touch/icons_8m/6.gif
50 x 49
50 x 49
100 x 98
http://sasisa.ru/images/touch/icons_8m/7.gif
50 x 49
50 x 49
100 x 98
http://sasisa.ru/images/touch/icons_8m/8.gif
50 x 49
50 x 49
100 x 98
http://sasisa.ru/images/touch/icons_8m/9.gif
50 x 49
50 x 49
100 x 98
http://sasisa.ru/images/touch/icons_8m/calend/32_2.gif
50 x 49
50 x 49
100 x 98
http://sasisa.ru/images/sock.gif
84 x 16
84 x 16
168 x 32

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
90

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for sasisa.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 sasisa.ru on mobile screens.
Document uses legible font sizes — 91.72% 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
div.zero
8.28%
11px
91.72%
≥ 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.
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 — 61% 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
19x12
19x12
29x12
27x12
28x12
31x12
29x12
33x12
31x12
34x12
33x12
33x12
34x12
36x12
42x12
41x12
42x12
42x12
44x12
44x12
44x12
55x12
45x12
46x12
49x12
RSS
56x12
63x12
55x12
64x12
90x16

Content Best Practices

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

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

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of sasisa.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 sasisa.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.
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.
Hosting

Server Location

Server IP Address: 212.129.52.124
Continent: Europe
Country: France
France Flag
Region: Île-de-France
City: Paris
Longitude: 2.3491
Latitude: 48.8579
Currencies: EUR
Languages: French

Web Hosting Provider

Name IP Address
Scaleway Dedibox IPFO
Registration

Domain Registrant

Private Registration: No
Name:
Organization:
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: Yes
McAfee WebAdvisor Rating: Unknown
WOT Rating:
WOT Trustworthiness: 76/100
WOT Child Safety: 31/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: sasisa.org
Issued By: R3
Valid From: 19th February, 2023
Valid To: 20th May, 2023
Subject: CN = sasisa.org
Hash: 758f2dd1
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x04BB5F4EE9BC22D093C84F5CABBFDDA1263F
Serial Number (Hex): 04BB5F4EE9BC22D093C84F5CABBFDDA1263F
Valid From: 19th February, 2024
Valid To: 20th May, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org

Authority Information Access: OCSP - URI:http://r3.o.lencr.org
CA Issuers - URI:http://r3.i.lencr.org/

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7A:32:8C:54:D8:B7:2D:B6:20:EA:38:E0:52:1E:E9:84:
16:70:32:13:85:4D:3B:D2:2B:C1:3A:57:A3:52:EB:52
Timestamp : Feb 19 21:48:39.376 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:90:F9:9C:E5:EF:FB:9E:92:48:24:C5:
DA:D1:DA:D3:C4:B5:91:D0:25:16:72:59:4C:07:C8:CA:
EC:E4:DF:0C:1C:02:20:33:D4:78:BE:25:7F:87:A3:62:
B6:5B:5E:00:81:62:DD:E2:6C:B1:6C:86:C9:80:19:FD:
5D:26:3F:0A:2D:67:CC
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : E8:3E:D0:DA:3E:F5:06:35:32:E7:57:28:BC:89:6B:C9:
03:D3:CB:D1:11:6B:EC:EB:69:E1:77:7D:6D:06:BD:6E
Timestamp : Feb 19 21:48:39.348 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:C4:47:4F:8C:EC:0A:9C:32:0C:12:B8:
DB:D3:57:F0:CD:1E:5E:5C:EF:E3:FD:3E:36:19:49:77:
B5:E9:DE:A0:36:02:21:00:B6:EC:1A:52:34:ED:58:16:
ED:65:EB:16:DE:D8:15:1E:A2:A2:C5:3F:4A:99:8D:2F:
62:5C:4C:B7:27:09:C2:1E
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:sasisa.org
Technical

DNS Lookup

A Records

Host IP Address Class TTL
sasisa.ru. 212.129.52.124 IN 600

NS Records

Host Nameserver Class TTL
sasisa.ru. ns2.wapsus.ru. IN 600
sasisa.ru. ns1.wapsus.ru. IN 600

MX Records

Priority Host Server Class TTL
10 sasisa.ru. mail.sasisa.ru. IN 600

SOA Records

Domain Name Primary NS Responsible Email TTL
sasisa.ru. sasisa.org. root.sasisa.org. 600

TXT Records

Host Value Class TTL
sasisa.ru. v=spf1 IN 600

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx
Date: 1st March, 2023
Content-Type: text/html; charset=utf-8
Expires: 19th November, 1981
Cache-Control: post-check=0, pre-check=0
Connection: keep-alive
Keep-Alive: timeout=20
X-Powered-By: PHP/8.0.27
Set-Cookie: *
Pragma: no-cache

Whois Lookup

Created: 12th January, 2005
Changed:
Expires: 12th January, 2024
Registrar: REGTIME-RU
Status:
Nameservers: ns1.wapsus.ru
ns2.wapsus.ru
Full Whois: % TCI Whois Service. Terms of use:
% https://tcinet.ru/documents/whois_ru_rf.pdf (in Russian)
% https://tcinet.ru/documents/whois_su.pdf (in Russian)

domain: SASISA.RU
nserver: ns1.wapsus.ru.
nserver: ns2.wapsus.ru.
state: REGISTERED, DELEGATED, VERIFIED
person: Private Person
registrar: REGTIME-RU
admin-contact: https://whois.webnames.ru
created: 2005-01-12T21:00:00Z
paid-till: 2024-01-12T21:00:00Z
free-date: 2024-02-13
source: TCI

Last updated on 2023-03-01T07:06:31Z

Nameservers

Name IP Address
ns1.wapsus.ru 85.17.28.40
ns2.wapsus.ru 85.17.28.34
Related

Subdomains

Domain Subdomain
wap

Similar Sites

Domain Valuation Snoop Score
$10,471 USD 2/5
$5,196,899 USD 4/5
$3,855 USD 3/5
$599 USD
0/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address