kakopis.ru

kakopis.ru is SSL secured

Free website and domain report on kakopis.ru

Last Updated: 3rd April, 2024
Overview

Snoop Summary for kakopis.ru

This is a free and comprehensive report about kakopis.ru. Kakopis.ru is hosted in United States on a server with an IP address of 172.67.167.1, where USD is the local currency and the local language is English. Kakopis.ru has the potential to be earning an estimated $13 USD per day from advertising revenue. If kakopis.ru was to be sold it would possibly be worth $9,312 USD (based on the daily revenue potential of the website over a 24 month period). Kakopis.ru is quite popular with an estimated 4,471 daily unique visitors. This report was last updated 3rd April, 2024.

About kakopis.ru

Site Preview: kakopis.ru kakopis.ru
Title: Какающие, писающие девушки и копро порно KakoPis.Ru
Description: Много онлайн видео с какающими и писающими девушками и женщинами, скрытые камеры в женских туалетах. Какающие, писающие девушки и копро порно KakoPis.Ru
Keywords and Tags: adult content
Related Terms:
Fav Icon:
Age: Over 11 years old
Domain Created: 20th November, 2012
Domain Updated:
Domain Expires: 21st November, 2024
Review

Snoop Score

3/5 (Great!)

Valuation

$9,312 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 137,155
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 4,471
Monthly Visitors: 136,083
Yearly Visitors: 1,631,915
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $13 USD
Monthly Revenue: $388 USD
Yearly Revenue: $4,651 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: kakopis.ru 10
Domain Name: kakopis 7
Extension (TLD): ru 2
Expiry Check:

Page Speed Analysis

Average Load Time: 0.42 seconds
Load Time Comparison: Faster than 97% of sites

PageSpeed Insights

Avg. (All Categories) 84
Performance 100
Accessibility 95
Best Practices 92
SEO 100
PWA 33
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://kakopis.ru/
Updated: 7th January, 2023

0.83 seconds
First Contentful Paint (FCP)
95%
3%
2%

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

Simulate loading on desktop
100

Performance

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

Metrics

First Contentful Paint — 0.3 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.3 s
The time taken for the page to become fully interactive.
Speed Index — 0.7 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.4 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.026
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 40 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.3 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://kakopis.ru/
http/1.1
0
40.097999968566
706
0
301
text/plain
https://kakopis.ru/
h2
40.391999995336
506.04999996722
6610
31678
200
text/html
Document
https://d.smopy.com/d/?resource=pubJS
http/1.1
512.26800004952
1723.066000035
11970
35576
200
text/html
Script
https://kakopis.ru/img/logo2.jpg
h2
512.50900002196
814.18400001712
7600
6860
200
image/jpeg
Image
https://kakopis.ru/pics/00/milanasmelly_really_new_years_feeding.webp
h2
524.96399998199
1032.1189999813
6691
5964
200
image/webp
Image
https://kakopis.ru/pics/00/78_march2013newmodel3.webp
h2
525.66799998749
1015.0879999856
8705
7980
200
image/webp
Image
https://kakopis.ru/pics/00/amateur_close_up_pooping.webp
h2
525.78500006348
1029.7700000228
2400
1670
200
image/webp
Image
https://kakopis.ru/pics/00/001_12.webp
h2
525.92300006654
1031.8980000447
5737
5010
200
image/webp
Image
https://kakopis.ru/pics/00/g_bom2912_wmv.webp
h2
526.05300000869
573.79699999001
6121
5378
200
image/webp
Image
https://kakopis.ru/pics/00/20221127_11735500.webp
h2
526.13999997266
577.97400001436
4161
3424
200
image/webp
Image
https://kakopis.ru/pics/00/lesbian_woman_wmv.webp
h2
526.23800002038
1030.65900004
9319
8588
200
image/webp
Image
https://kakopis.ru/pics/00/p1081.webp
h2
526.35900001042
1107.4120000703
4997
4266
200
image/webp
Image
https://kakopis.ru/pics/00/20170530_japanese_girl_scat.webp
h2
526.45200002007
1042.8410000168
5251
4522
200
image/webp
Image
https://kakopis.ru/pics/00/schoolgirls_pooping_on_camera.webp
h2
526.59500006121
1052.953000064
6037
5312
200
image/webp
Image
https://kakopis.ru/pics/00/blowjob_and_shitting_in_the_woods.webp
h2
526.67599997949
1077.4280000478
9213
8484
200
image/webp
Image
https://kakopis.ru/pics/00/23717_wmv.webp
h2
526.76799998153
1031.2740000663
8757
8030
200
image/webp
Image
https://kakopis.ru/pics/00/20221229_12083140.webp
h2
526.90900000744
609.567000065
9967
9220
200
image/webp
Image
https://kakopis.ru/pics/00/20221215_butt_exam_4.webp
h2
527.01600000728
582.96400005929
5143
4400
200
image/webp
Image
https://kakopis.ru/pics/00/20221215_butt_exam_3.webp
h2
527.09700004198
580.808000057
4726
3990
200
image/webp
Image
https://kakopis.ru/pics/00/20221215_butt_exam_2.webp
h2
527.21700002439
578.54400004726
4232
3488
200
image/webp
Image
https://kakopis.ru/pics/00/20221215_butt_exam_1.webp
h2
527.31499995571
607.2479999857
5971
5224
200
image/webp
Image
https://kakopis.ru/pics/00/20221219_10449985.webp
h2
527.43700006977
575.29199996497
5022
4278
200
image/webp
Image
https://kakopis.ru/pics/00/20221213_11970370.webp
h2
527.52000000328
573.59399995767
8806
8060
200
image/webp
Image
https://kakopis.ru/pics/00/20221212_11931730.webp
h2
527.62399998028
560.96000003163
2693
1954
200
image/webp
Image
https://kakopis.ru/pics/00/20221212_11931740.webp
h2
527.73099998012
583.76499998849
4203
3460
200
image/webp
Image
https://kakopis.ru/pics/00/20221203_black_scat_couple_having_dirty_anal_sex_in_the_public.webp
h2
527.81600004528
583.37500004563
8600
7856
200
image/webp
Image
https://kakopis.ru/pics/00/20221203_black_scat_couple.webp
h2
528.07999996003
576.48300006986
4924
4186
200
image/webp
Image
https://kakopis.ru/pics/00/20221127_women_pooping_3.webp
h2
528.18200003821
562.73999996483
7008
6260
200
image/webp
Image
https://kakopis.ru/pics/00/20221127_women_pooping_2.webp
h2
528.31399999559
1127.6040000375
6623
5898
200
image/webp
Image
https://kakopis.ru/pics/00/20221127_women_pooping_1.webp
h2
528.44600006938
597.35100006219
5875
5134
200
image/webp
Image
https://kakopis.ru/pics/00/20221127_11865710.webp
h2
528.65800005384
578.19200004451
10352
9610
200
image/webp
Image
https://kakopis.ru/pics/00/20221127_11735505.webp
h2
528.7229999667
1038.6970000109
7227
6498
200
image/webp
Image
https://kakopis.ru/pics/00/20221127_11735495.webp
h2
528.82999996655
576.20000001043
6080
5336
200
image/webp
Image
https://kakopis.ru/pics/00/20221127_11735490.webp
h2
528.91800005455
1110.6340000406
4306
3576
200
image/webp
Image
https://kakopis.ru/pics/00/22021127_11864265.webp
h2
529.03800003696
579.38800007105
6152
5412
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_chikako_rock_and_pebbles_poop.webp
h2
529.14999995846
577.78100005817
8598
7856
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_chigusa_has_a_tail.webp
h2
529.27699999418
583.16499995999
4569
3832
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_chifuyu_dine_and_dump.webp
h2
529.39100004733
583.55199999642
7875
7132
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_chieko_returns_another_monster_poop.webp
h2
529.51400005259
600.08200001903
4986
4242
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_chieko_bombs_away.webp
h2
529.59299995564
578.37500004098
6759
6020
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_chieko_births_a_monster_2.webp
h2
529.66700005345
602.34500002116
5112
4372
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_chieko_births_a_monster_1.webp
h2
529.77899997495
1076.6960000619
4732
4006
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_chiasa_pooping_pebbles.webp
h2
529.88899999764
579.92300007027
6688
5944
200
image/webp
Image
https://kakopis.ru/pics/00/21102022_french_girl.webp
h2
529.98200000729
577.56500004325
12952
12208
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_chiakis_struggle.webp
h2
530.08599998429
565.33999997191
4405
3668
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_blooper_from_mikoi.webp
h2
530.17699997872
636.54700003099
6793
6046
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_best_of_saki_part_1.webp
h2
530.28199996334
573.31300002988
4147
3404
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_best_of_chieko.webp
h2
530.37499997299
606.15300002974
6504
5756
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_ayaka_false_start.webp
h2
530.51000006963
1106.5609999932
5241
4516
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_atsuki_fun_with_poop.webp
h2
530.60100006405
598.13399997074
4788
4050
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_ayumi_is_endless.webp
h2
531.09199996106
640.97000006586
3428
2686
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_ayumi_frontal_pooping.webp
h2
531.16500005126
557.5040000258
4858
4108
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_ayumi2_desk_poop.webp
h2
531.25400003046
580.59400005732
5760
5018
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_an_explosion_from_yukie.webp
h2
531.3839999726
1077.0989999874
6537
5812
200
image/webp
Image
https://kakopis.ru/pics/00/22020906_extreme_ap_scat_and_puke_comp.webp
h2
531.47899999749
584.21800006181
5450
4706
200
image/webp
Image
https://kakopis.ru/pics/00/22020906_11477105.webp
h2
531.54100000393
591.30500000902
6186
5442
200
image/webp
Image
https://kakopis.ru/pics/00/22020906_11472542.webp
h2
531.64000005927
621.79899995681
8140
7400
200
image/webp
Image
https://kakopis.ru/pics/00/18082022_nanasaki_fuuka_insult_scatology_cosplay_rape_kihana_rin_opud_201_2018.webp
h2
531.71999996994
1077.9059999622
8189
7460
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_asuka_peek_a_boo_poop.webp
h2
531.86300001107
604.6830000123
4448
3710
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_aneko_perfect_circle.webp
h2
531.946000061
615.34100002609
7636
6890
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_chihiro_rooftop_session.webp
h2
532.02200005762
605.04599998239
7748
7006
200
image/webp
Image
https://kakopis.ru/pics/00/22032022_unlawfulparallelblowfish.webp
h2
532.10800001398
596.76300000865
6738
5994
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_ami_quality_poop.webp
h2
532.22000005189
591.03000001051
4424
3682
200
image/webp
Image
data
545.35000002943
545.4219999956
0
42
200
image/gif
Image
https://counter.yadro.ru/hit?t44.6;r;s800*600*24;uhttps%3A//kakopis.ru/;h%u041A%u0430%u043A%u0430%u044E%u0449%u0438%u0435%2C%20%u043F%u0438%u0441%u0430%u044E%u0449%u0438%u0435%20%u0434%u0435%u0432%u0443%u0448%u043A%u0438%20%u0438%20%u043A%u043E%u043F%u0440%u043E%20%u043F%u043E%u0440%u043D%u043E%20KakoPis.Ru;0.6135720145325829
http/1.1
546.81299999356
768.33200000692
838
0
302
text/html
https://counter.yadro.ru/hit?q;t44.6;r;s800*600*24;uhttps%3A//kakopis.ru/;h%u041A%u0430%u043A%u0430%u044E%u0449%u0438%u0435%2C%20%u043F%u0438%u0441%u0430%u044E%u0449%u0438%u0435%20%u0434%u0435%u0432%u0443%u0448%u043A%u0438%20%u0438%20%u043A%u043E%u043F%u0440%u043E%20%u043F%u043E%u0440%u043D%u043E%20KakoPis.Ru;0.6135720145325829
http/1.1
768.61400005873
1035.5470000068
618
132
200
image/gif
Image
https://d.pssy.xyz/d/?resource=bundler&nada=1&widgets=2328948:1&isct=undefined&reqc=1&ver=022cd702e89d466b.1673091510817&page=aHR0cHM6Ly9rYWtvcGlzLnJ1Lw==
http/1.1
1748.8329999615
3115.4220000608
37040
91746
200
application/json
XHR
https://d.pssy.xyz/t.php
http/1.1
2750.284000067
3461.3540000282
410
0
200
text/html
Image
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)
510.064
12.076
522.467
6
528.476
9.158
540.188
5.413
1739.139
10.578
3117.062
40.294
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. Kakopis.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. Kakopis.ru should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Kakopis.ru should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Kakopis.ru should consider minifying CSS files.
Minify JavaScript — Potential savings of 2 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Kakopis.ru should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://d.smopy.com/d/?resource=pubJS
11970
2424
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Kakopis.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
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
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 470 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)
https://kakopis.ru/
466.653
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Kakopis.ru should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://kakopis.ru/
190
https://kakopis.ru/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Kakopis.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 — Potential savings of 0 KiB
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.
URL Potential Savings (Bytes)
https://d.smopy.com/d/?resource=pubJS
68
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://kakopis.ru/pics/00/g_bom2912_wmv.webp
0
Avoids enormous network payloads — Total size was 425 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://d.pssy.xyz/d/?resource=bundler&nada=1&widgets=2328948:1&isct=undefined&reqc=1&ver=022cd702e89d466b.1673091510817&page=aHR0cHM6Ly9rYWtvcGlzLnJ1Lw==
37040
https://kakopis.ru/pics/00/21102022_french_girl.webp
12952
https://d.smopy.com/d/?resource=pubJS
11970
https://kakopis.ru/pics/00/20221127_11865710.webp
10352
https://kakopis.ru/pics/00/20221229_12083140.webp
9967
https://kakopis.ru/pics/00/lesbian_woman_wmv.webp
9319
https://kakopis.ru/pics/00/blowjob_and_shitting_in_the_woods.webp
9213
https://kakopis.ru/pics/00/20221213_11970370.webp
8806
https://kakopis.ru/pics/00/23717_wmv.webp
8757
https://kakopis.ru/pics/00/78_march2013newmodel3.webp
8705
Uses efficient cache policy on static assets — 2 resources found
Kakopis.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)
https://d.smopy.com/d/?resource=pubJS
0
11970
https://d.pssy.xyz/t.php
0
410
Avoids an excessive DOM size — 281 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
281
Maximum DOM Depth
5
Maximum Child Elements
70
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Kakopis.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://d.smopy.com/d/?resource=pubJS
61.654
51.519
7.479
https://kakopis.ru/
61.423
3.585
1.241
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
56.83
Other
56.415
Rendering
18.22
Style & Layout
11.807
Parse HTML & CSS
9.361
Script Parsing & Compilation
8.72
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 — 67 requests • 425 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
67
434782
Image
62
377618
Other
3
38584
Script
1
11970
Document
1
6610
Stylesheet
0
0
Media
0
0
Font
0
0
Third-party
5
50876
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
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.
Element
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.024075520411937
0.00062679884825209
0.00053998263615882
0.00053998263615882
0.00053998263615882
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
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
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 kakopis.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

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
https://kakopis.ru/img/logo2.jpg
95

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of kakopis.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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<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.

Contrast

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

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
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 `[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.
`<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"]`
Kakopis.ru may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that kakopis.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

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

Audits

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 — 1 insecure request 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://kakopis.ru/
Allowed
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for kakopis.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 kakopis.ru on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

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

Crawling and Indexing

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

Manual Checks

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

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 kakopis.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 kakopis.ru on mobile screens.
Provides 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.

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
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) 83
Performance 99
Accessibility 95
Best Practices 83
SEO 100
PWA 40
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://kakopis.ru/
Updated: 7th January, 2023

0.97 seconds
First Contentful Paint (FCP)
94%
4%
2%

0.02 seconds
First Input Delay (FID)
97%
2%
1%

Simulate loading on mobile
99

Performance

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

Metrics

First Contentful Paint — 1.1 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 1.2 s
The time taken for the page to become fully interactive.
Speed Index — 1.1 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 — 1.3 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.075
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 — 1.1 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://kakopis.ru/
http/1.1
0
29.939000029117
711
0
301
text/plain
https://kakopis.ru/
h2
30.312999850139
173.0680000037
6643
31390
200
text/html
Document
https://d.smopy.com/d/?resource=pubJS
http/1.1
181.85699987225
1366.8279999401
11968
35576
200
text/html
Script
https://kakopis.ru/img/logo2.jpg
h2
182.02299997211
200.09499997832
7602
6860
200
image/jpeg
Image
https://kakopis.ru/pics/00/nice_poop_girl_in_the_toilet.webp
h2
193.79599997774
644.55399988219
6545
5816
200
image/webp
Image
https://kakopis.ru/pics/00/clip_640_2006_01.webp
h2
194.38699982129
658.00699987449
4288
3560
200
image/webp
Image
https://kakopis.ru/pics/00/scat_2_gif_by_boomanshee.webp
h2
194.49299992993
220.22799984552
4917
4170
200
image/webp
Image
https://kakopis.ru/pics/00/video3.webp
h2
194.58199990913
654.01499997824
11342
10612
200
image/webp
Image
https://kakopis.ru/pics/00/89_masha2_4.webp
h2
194.63999988511
724.39999994822
4861
4132
200
image/webp
Image
https://kakopis.ru/pics/00/2070309_0.webp
h2
194.72399982624
214.70999997109
5208
4472
200
image/webp
Image
https://kakopis.ru/pics/00/p1021_isabella.webp
h2
194.79099987075
701.50399999693
10063
9332
200
image/webp
Image
https://kakopis.ru/pics/00/sc1127.webp
h2
194.89399995655
737.4289999716
5697
4964
200
image/webp
Image
https://kakopis.ru/pics/00/scg_34_5.webp
h2
194.98399994336
685.28699991293
3032
2298
200
image/webp
Image
https://kakopis.ru/pics/00/4758dem5blnd_rir.webp
h2
195.05999982357
684.70799992792
5285
4550
200
image/webp
Image
https://kakopis.ru/pics/00/img_4081.webp
h2
195.17800002359
687.8499998711
5431
4694
200
image/webp
Image
https://kakopis.ru/pics/00/29818.webp
h2
195.25199988857
640.38600004278
6193
5460
200
image/webp
Image
https://kakopis.ru/pics/00/20221229_12083140.webp
h2
195.32800000161
217.82499994151
9967
9220
200
image/webp
Image
https://kakopis.ru/pics/00/20221215_butt_exam_4.webp
h2
195.42500004172
215.6749998685
5147
4400
200
image/webp
Image
https://kakopis.ru/pics/00/20221215_butt_exam_3.webp
h2
195.52099984139
322.11899990216
4726
3990
200
image/webp
Image
https://kakopis.ru/pics/00/20221215_butt_exam_2.webp
h2
195.61499985866
241.06199992821
4234
3488
200
image/webp
Image
https://kakopis.ru/pics/00/20221215_butt_exam_1.webp
h2
195.70899987593
728.07199996896
5963
5224
200
image/webp
Image
https://kakopis.ru/pics/00/20221219_10449985.webp
h2
195.85200003348
219.82200001366
5016
4278
200
image/webp
Image
https://kakopis.ru/pics/00/20221213_11970370.webp
h2
195.93199994415
216.29399992526
8800
8060
200
image/webp
Image
https://kakopis.ru/pics/00/20221212_11931730.webp
h2
196.00300001912
215.97399981692
2691
1954
200
image/webp
Image
https://kakopis.ru/pics/00/20221212_11931740.webp
h2
196.09300000593
218.38500001468
4199
3460
200
image/webp
Image
https://kakopis.ru/pics/00/20221203_black_scat_couple_having_dirty_anal_sex_in_the_public.webp
h2
196.27800001763
234.04400004074
8598
7856
200
image/webp
Image
https://kakopis.ru/pics/00/20221203_black_scat_couple.webp
h2
196.4039998129
214.99999985099
4931
4186
200
image/webp
Image
https://kakopis.ru/pics/00/20221127_women_pooping_3.webp
h2
196.52799982578
691.54499983415
6997
6260
200
image/webp
Image
https://kakopis.ru/pics/00/20221127_women_pooping_2.webp
h2
196.6170000378
218.96099997684
6642
5898
200
image/webp
Image
https://kakopis.ru/pics/00/20221127_women_pooping_1.webp
h2
196.71599986032
218.07099995203
5878
5134
200
image/webp
Image
https://kakopis.ru/pics/00/20221127_11865710.webp
h2
196.78999995813
217.53799985163
10351
9610
200
image/webp
Image
https://kakopis.ru/pics/00/20221127_11735505.webp
h2
196.87999994494
219.24400003627
7229
6498
200
image/webp
Image
https://kakopis.ru/pics/00/20221127_11735500.webp
h2
196.98200002313
226.67000000365
4163
3424
200
image/webp
Image
https://kakopis.ru/pics/00/20221127_11735495.webp
h2
197.07999983802
215.31599992886
6074
5336
200
image/webp
Image
https://kakopis.ru/pics/00/20221127_11735490.webp
h2
197.24599993788
214.27499991842
4310
3576
200
image/webp
Image
https://kakopis.ru/pics/00/22021127_11864265.webp
h2
197.35399982892
238.49799996242
6156
5412
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_chikako_rock_and_pebbles_poop.webp
h2
197.43199995719
213.99399987422
8600
7856
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_chigusa_has_a_tail.webp
h2
197.50000000931
235.66899984144
4571
3832
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_chifuyu_dine_and_dump.webp
h2
197.5809999276
228.65699999966
7873
7132
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_chieko_returns_another_monster_poop.webp
h2
197.65300001018
229.66399998404
4986
4242
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_chieko_bombs_away.webp
h2
197.71199999377
219.56099988893
6756
6020
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_chieko_births_a_monster_2.webp
h2
197.7889998816
216.89399983734
5118
4372
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_chieko_births_a_monster_1.webp
h2
198.12199985608
223.18700002506
4746
4006
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_chiasa_pooping_pebbles.webp
h2
198.22399993427
217.24499994889
6692
5944
200
image/webp
Image
https://kakopis.ru/pics/00/21102022_french_girl.webp
h2
198.30699986778
218.67399988696
12954
12208
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_chiakis_struggle.webp
h2
198.40199989267
322.63199985027
4398
3668
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_blooper_from_mikoi.webp
h2
198.52099986747
731.82999994606
6773
6046
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_best_of_saki_part_1.webp
h2
198.61499988474
216.61300002597
4143
3404
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_best_of_chieko.webp
h2
198.67399986833
643.89199996367
6487
5756
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_ayaka_false_start.webp
h2
198.75300000422
262.66300003044
5255
4516
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_atsuki_fun_with_poop.webp
h2
198.86599993333
313.83399991319
4789
4050
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_ayumi_is_endless.webp
h2
198.94399982877
234.44699984975
3431
2686
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_ayumi_frontal_pooping.webp
h2
199.02699999511
230.41699989699
4848
4108
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_ayumi2_desk_poop.webp
h2
199.07599990256
269.52999993227
5768
5018
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_an_explosion_from_yukie.webp
h2
199.14599996991
232.77099989355
6556
5812
200
image/webp
Image
https://kakopis.ru/pics/00/22020906_extreme_ap_scat_and_puke_comp.webp
h2
199.31399985217
225.46799993142
5448
4706
200
image/webp
Image
https://kakopis.ru/pics/00/22020906_11477105.webp
h2
199.58100002259
229.22499990091
6179
5442
200
image/webp
Image
https://kakopis.ru/pics/00/22020906_11472542.webp
h2
199.63499996811
233.34799986333
8144
7400
200
image/webp
Image
https://kakopis.ru/pics/00/18082022_nanasaki_fuuka_insult_scatology_cosplay_rape_kihana_rin_opud_201_2018.webp
h2
199.69499995932
227.46700001881
8197
7460
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_asuka_peek_a_boo_poop.webp
h2
199.76500002667
236.11099994741
4452
3710
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_aneko_perfect_circle.webp
h2
199.86899988726
249.06999990344
7628
6890
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_chihiro_rooftop_session.webp
h2
199.95099981315
230.18600000069
7746
7006
200
image/webp
Image
https://kakopis.ru/pics/00/22032022_unlawfulparallelblowfish.webp
h2
200.01200004481
236.48500000127
6740
5994
200
image/webp
Image
https://kakopis.ru/pics/00/13062022_ami_quality_poop.webp
h2
200.3750000149
235.40899995714
4424
3682
200
image/webp
Image
data
221.82599990629
221.94399987347
0
42
200
image/gif
Image
https://counter.yadro.ru/hit?t44.6;r;s360*640*24;uhttps%3A//kakopis.ru/;h%u041A%u0430%u043A%u0430%u044E%u0449%u0438%u0435%2C%20%u043F%u0438%u0441%u0430%u044E%u0449%u0438%u0435%20%u0434%u0435%u0432%u0443%u0448%u043A%u0438%20%u0438%20%u043A%u043E%u043F%u0440%u043E%20%u043F%u043E%u0440%u043D%u043E%20KakoPis.Ru;0.008106666696034548
http/1.1
223.55999983847
453.19399982691
840
0
302
text/html
https://counter.yadro.ru/hit?q;t44.6;r;s360*640*24;uhttps%3A//kakopis.ru/;h%u041A%u0430%u043A%u0430%u044E%u0449%u0438%u0435%2C%20%u043F%u0438%u0441%u0430%u044E%u0449%u0438%u0435%20%u0434%u0435%u0432%u0443%u0448%u043A%u0438%20%u0438%20%u043A%u043E%u043F%u0440%u043E%20%u043F%u043E%u0440%u043D%u043E%20KakoPis.Ru;0.008106666696034548
http/1.1
453.5709999036
673.78399986774
618
132
200
image/gif
Image
https://d.pssy.xyz/d/?resource=bundler&nada=1&widgets=2328948:1&isct=undefined&reqc=1&ver=7be0f060d1255aae.1673091532328&page=aHR0cHM6Ly9rYWtvcGlzLnJ1Lw==
http/1.1
1393.2789999526
2560.707999859
343
27
200
application/json
XHR
https://d.pssy.xyz/t.php
http/1.1
2394.4159999955
3590.0979998987
410
0
200
text/html
Image
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)
176.713
14.656
191.647
7.889
199.549
11.788
214.756
7.301
1383.622
10.83
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. Kakopis.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. Kakopis.ru should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Kakopis.ru should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Kakopis.ru should consider minifying CSS files.
Minify JavaScript — Potential savings of 2 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Kakopis.ru should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://d.smopy.com/d/?resource=pubJS
11968
2423
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Kakopis.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
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
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 140 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)
https://kakopis.ru/
143.75
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Kakopis.ru should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://kakopis.ru/
630
https://kakopis.ru/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Kakopis.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 — Potential savings of 0 KiB
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.
URL Potential Savings (Bytes)
https://d.smopy.com/d/?resource=pubJS
68
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 388 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://kakopis.ru/pics/00/21102022_french_girl.webp
12954
https://d.smopy.com/d/?resource=pubJS
11968
https://kakopis.ru/pics/00/video3.webp
11342
https://kakopis.ru/pics/00/20221127_11865710.webp
10351
https://kakopis.ru/pics/00/p1021_isabella.webp
10063
https://kakopis.ru/pics/00/20221229_12083140.webp
9967
https://kakopis.ru/pics/00/20221213_11970370.webp
8800
https://kakopis.ru/pics/00/13062022_chikako_rock_and_pebbles_poop.webp
8600
https://kakopis.ru/pics/00/20221203_black_scat_couple_having_dirty_anal_sex_in_the_public.webp
8598
https://kakopis.ru/pics/00/18082022_nanasaki_fuuka_insult_scatology_cosplay_rape_kihana_rin_opud_201_2018.webp
8197
Uses efficient cache policy on static assets — 2 resources found
Kakopis.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)
https://d.smopy.com/d/?resource=pubJS
0
11968
https://d.pssy.xyz/t.php
0
410
Avoids an excessive DOM size — 279 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
279
Maximum DOM Depth
5
Maximum Child Elements
70
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Kakopis.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://kakopis.ru/
255.808
17.276
5.704
Unattributable
171.14
6.312
0
https://d.smopy.com/d/?resource=pubJS
61.576
53.836
2.552
Minimizes main-thread work — 0.5 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)
Other
244.192
Script Evaluation
77.424
Style & Layout
63.72
Rendering
52.804
Parse HTML & CSS
42.128
Script Parsing & Compilation
8.256
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 — 68 requests • 388 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
68
397771
Image
63
377266
Script
1
11968
Document
1
6643
Other
3
1894
Stylesheet
0
0
Media
0
0
Font
0
0
Third-party
5
14179
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
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.040547541645419
0.010505499426313
0.0080813503140523
0.0080813503140523
0.0080813503140523
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)
https://kakopis.ru/
1110
59
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 kakopis.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) — 2184 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.

Other

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
https://kakopis.ru/img/logo2.jpg
95

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of kakopis.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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<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.

Contrast

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

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
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 `[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.
`<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"]`
Kakopis.ru may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

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

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

Audits

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 — 1 insecure request 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://kakopis.ru/
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
https://kakopis.ru/pics/00/nice_poop_girl_in_the_toilet.webp
300 x 200
300 x 200
600 x 400
https://kakopis.ru/img/logo2.jpg
300 x 73
300 x 73
600 x 146
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for kakopis.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 kakopis.ru on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
100.00%
≥ 12px
Tap targets are sized appropriately — 100% 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.

Content Best Practices

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

Crawling and Indexing

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

Manual Checks

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

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 kakopis.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 kakopis.ru on mobile screens.
Provides 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.

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
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: 172.67.167.1
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Cloudflare, Inc.
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: Not Likely
McAfee WebAdvisor Rating: Unknown
WOT Rating:
WOT Trustworthiness: 60/100
WOT Child Safety: 10/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: kakopis.ru
Issued By: GTS CA 1P5
Valid From: 15th February, 2024
Valid To: 15th May, 2024
Subject: CN = kakopis.ru
Hash: 477b16d6
Issuer: CN = GTS CA 1P5
O = Google Trust Services LLC
S = US
Version: 2
Serial Number: 0xD777A66CBD29686A1117000251B59381
Serial Number (Hex): D777A66CBD29686A1117000251B59381
Valid From: 15th February, 2024
Valid To: 15th May, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:D5:FC:9E:0D:DF:1E:CA:DD:08:97:97:6E:2B:C5:5F:C5:2B:F5:EC:B8
Extended Key Usage: TLS Web Server Authentication
CRL Distribution Points:
Full Name:
URI:http://crls.pki.goog/gts1p5/9Msi4aemqSQ.crl

Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.11129.2.5.3

Authority Information Access: OCSP - URI:http://ocsp.pki.goog/s/gts1p5/kuOi-RUlK4A
CA Issuers - URI:http://pki.goog/repo/certs/gts1p5.der

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
Timestamp : Feb 15 10:24:40.587 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:EA:5B:3A:BC:9D:53:B5:B0:75:E7:CC:
77:C6:A4:29:35:94:42:F4:54:F2:74:EF:D4:FA:39:25:
BB:58:E3:C9:FC:02:21:00:CF:6D:2E:77:60:B0:F1:F1:
C2:31:86:3F:40:2E:80:68:95:B9:44:D5:A0:60:16:47:
04:E5:61:24:40:4A:87:83
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
Timestamp : Feb 15 10:24:40.550 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:FB:6E:A0:3D:7F:64:EA:33:F3:5E:65:
36:BC:A5:CF:C5:34:4D:66:55:40:34:A8:48:BD:44:09:
1B:BC:E9:E6:83:02:21:00:8B:2A:A1:5F:F7:05:52:61:
F5:82:FD:34:54:D3:D0:F7:9E:A5:AD:D9:FA:1D:0B:D2:
0A:21:6F:96:43:FA:22:D2
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.kakopis.ru
DNS:kakopis.ru
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/2 200
date: 3rd April, 2024
content-type: text/html; charset=UTF-8
server: cloudflare
vary: Accept-Encoding
cf-cache-status: DYNAMIC
report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v4?s=NCxCI3MXtjlwNoIDPh4Duz0Hd%2B%2F0vtgq0%2BRKOWQKcbvCbC3sNCj1G2lQ9rgGwoVbX6kiO6A8EouQ0kcQbIZwHO1Irk2e78%2FEEPakrinmyGc7RxXrupWI%2FpdAsx5F"}],"group":"cf-nel","max_age":604800}
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
cf-ray: 86e76505eef057e5-IAD
alt-svc: h3=":443"; ma=86400

Whois Lookup

Created: 20th November, 2012
Changed:
Expires: 21st November, 2024
Registrar: REGRU-RU
Status:
Nameservers: eva.ns.cloudflare.com
rick.ns.cloudflare.com
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: KAKOPIS.RU
nserver: eva.ns.cloudflare.com.
nserver: rick.ns.cloudflare.com.
state: REGISTERED, DELEGATED, VERIFIED
person: Private Person
registrar: REGRU-RU
admin-contact: http://www.reg.ru/whois/admin_contact
created: 2012-11-20T23:35:49Z
paid-till: 2024-11-21T00:35:49Z
free-date: 2024-12-22
source: TCI

Last updated on 2024-04-03T07:36:30Z

Nameservers

Name IP Address
eva.ns.cloudflare.com 108.162.192.114
rick.ns.cloudflare.com 172.64.33.139
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
0/5
0/5
0/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
0/5