ebalka.kim

ebalka.kim is SSL secured

Free website and domain report on ebalka.kim

Last Updated: 18th October, 2022 Update Now
Overview

Snoop Summary for ebalka.kim

This is a free and comprehensive report about ebalka.kim. Ebalka.kim is hosted in United States on a server with an IP address of 104.26.12.96, where the local currency is USD and English is the local language. Ebalka.kim is expected to earn an estimated $125 USD per day from advertising revenue. The sale of ebalka.kim would possibly be worth $90,937 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Ebalka.kim is wildly popular with an estimated 29,454 daily unique visitors. This report was last updated 18th October, 2022.

About ebalka.kim

Site Preview:
Title: Just a moment...
Description:
Keywords and Tags: adult content, popular
Related Terms:
Fav Icon:
Age: Over 2 years old
Domain Created: 25th June, 2022
Domain Updated: 30th June, 2022
Domain Expires: 25th June, 2023
Review

Snoop Score

2/5

Valuation

$90,937 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 26,582
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: 29,454
Monthly Visitors: 896,487
Yearly Visitors: 10,750,710
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $125 USD
Monthly Revenue: $3,791 USD
Yearly Revenue: $45,464 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: ebalka.kim 10
Domain Name: ebalka 6
Extension (TLD): kim 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 73
Performance 80
Accessibility 88
Best Practices 83
SEO 92
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://sex.ebalka.kim/
Updated: 18th October, 2022

0.96 seconds
First Contentful Paint (FCP)
91%
5%
4%

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

80

Performance

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

Metrics

Time to Interactive — 1.0 s
The time taken for the page to become fully interactive.
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).

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://ebalka.kim/
http/1.1
0
294.17099989951
683
0
301
text/html
http://sex.ebalka.kim/
http/1.1
294.55699992832
724.69199995976
16873
89233
200
text/html
Document
http://sex.ebalka.kim/static/1524304640913/main.css
http/1.1
736.47000000346
1009.5710000023
13361
60707
200
text/css
Stylesheet
http://sex.ebalka.kim/js/KernelTeamVideoSharingSystem.js?v=5.5.0
http/1.1
739.32499997318
1052.7669999283
2736
6116
200
application/javascript
Script
http://sex.ebalka.kim/static/1524258613548/combine.js
http/1.1
739.46399998385
837.33000000939
66516
197948
200
application/javascript
Script
https://www.googletagmanager.com/gtag/js?id=G-NK7DRKKFN7
h2
1010.8359999722
1056.300999946
75593
213320
200
application/javascript
Script
https://fonts.googleapis.com/css?family=Open+Sans+Condensed:300,700&subset=latin,latin-ext&display=swap
h2
1011.4109999267
1030.224999995
1423
5010
200
text/css
Stylesheet
http://sex.ebalka.kim/?mode=async&action=js_stats&rand=1666088238900
http/1.1
1057.429999928
1307.9610000132
662
43
200
image/gif
Image
http://sex.ebalka.kim/img/bg.png
http/1.1
1060.3129999945
1368.6250000028
57348
56599
200
image/png
Image
http://sex.ebalka.kim/images/vkIcon.png
http/1.1
1062.1159999864
1361.0039999476
1210
464
200
image/png
Image
http://sex.ebalka.kim/images/okIcon.png
http/1.1
1062.2629999416
1301.4620000031
1280
528
200
image/png
Image
http://sex.ebalka.kim/images/facebookIcon.png
http/1.1
1062.8909999505
1106.262999936
1155
409
200
image/png
Image
http://sex.ebalka.kim/images/twitterIcon.png
http/1.1
1062.9979999503
1323.6749999924
1206
467
200
image/png
Image
http://sex.ebalka.kim/images/googleIcon.png
http/1.1
1063.2149999728
1353.9790000068
1273
533
200
image/png
Image
http://sex.ebalka.kim/images/mailIcon.png
http/1.1
1063.3239999879
1344.7709999746
1324
589
200
image/png
Image
http://sex.ebalka.kim/img/logo_small_blue_new.png
http/1.1
1065.6249999302
1126.053999993
4084
3327
200
image/png
Image
http://sex.ebalka.kim/img/logos.png
http/1.1
1065.8909999765
1340.5969999731
8046
7300
200
image/png
Image
http://sex.ebalka.kim/img/nav-bg.png
http/1.1
1066.0269999644
1100.4109999631
851
95
200
image/png
Image
http://sex.ebalka.kim/img/img.png
http/1.1
1066.1540000001
1398.8539999118
6452
5706
200
image/png
Image
https://fonts.gstatic.com/s/opensanscondensed/v23/z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff0GmDuHMR7eS2AopSg.woff2
h2
1066.2659999216
1070.1209999388
7459
6532
200
font/woff2
Font
https://fonts.gstatic.com/s/opensanscondensed/v23/z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff0GmDuXMR7eS2Ao.woff2
h2
1069.4989999756
1073.6729999771
11200
10272
200
font/woff2
Font
http://site.yandex.net/v2.0/js/all.js
http/1.1
1082.3849999579
1467.9389999947
15957
57430
200
application/javascript
Script
data
1079.1939999908
1079.3059999123
0
42
200
image/gif
Image
http://sex.ebalka.kim/img/search-btn.jpg
http/1.1
1109.6229999093
1201.3969999971
1970
1200
200
image/jpeg
Image
http://sex.ebalka.kim/?mode=async&action=js_stats&rand=1666088239026
http/1.1
1214.7859999677
1492.4299999839
660
43
200
image/gif
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135023/240x180/1.jpg
http/1.1
1215.1430000085
1364.2690000124
11020
10259
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/118000/118624/240x180/1.jpg
http/1.1
1215.2810000116
1372.224999941
15742
14985
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/112000/112921/240x180/1.jpg
http/1.1
1215.3829999734
1553.8599999854
17171
16426
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/104000/104992/240x180/1.jpg
http/1.1
1215.9889999311
1489.5689999685
8019
7275
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/99000/99300/240x180/1.jpg
http/1.1
1216.1699999124
1484.5759999007
13078
12335
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/96000/96267/240x180/1.jpg
http/1.1
1216.5219999151
1489.935999969
16981
16242
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/89000/89115/240x180/1.jpg
http/1.1
1216.6659999639
1516.140999971
13499
12758
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/89000/89066/240x180/1.jpg
http/1.1
1216.8689999962
1602.8630000073
16655
15916
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/82000/82600/240x180/1.jpg
http/1.1
1217.8659999045
1602.1019999171
16265
15522
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/82000/82062/240x180/1.jpg
http/1.1
1220.1139999088
1509.7090000054
12749
12002
200
image/jpeg
Image
https://www.google-analytics.com/g/collect?v=2&tid=G-NK7DRKKFN7&gtm=2oeaa0&_p=2013803307&cid=1294473612.1666088239&ul=en-us&sr=800x600&_s=1&sid=1666088239&sct=1&seg=0&dl=http%3A%2F%2Fsex.ebalka.kim%2F&dt=%D0%A0%D1%83%D1%81%D1%81%D0%BA%D0%BE%D0%B5%20%D0%BF%D0%BE%D1%80%D0%BD%D0%BE%3A%20%D0%BD%D0%BE%D0%B2%D0%B8%D0%BD%D0%BA%D0%B8%20%D0%B2%20HD%20%D0%B8%20%D1%8D%D0%BA%D1%81%D0%BA%D0%BB%D1%8E%D0%B7%D0%B8%D0%B2%20%7C%20%D0%95%D0%B1%D0%B0%D0%BB%D0%BA%D0%B0&en=page_view&_fv=1&_nsi=1&_ss=1&_ee=1
1263.8349999906
1268.3579999721
0
0
-1
Ping
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)
731.453
12.045
1059.063
17.263
1085.714
22.799
1109.268
48.607
1159.472
59.222
1219.331
12.647
1232.023
5.074
1238.216
27.652
1506.688
11.95
1526.143
12.509
1541.918
6.708
1565.172
13.299
1609.842
9.446
1673.287
5.706
1707.27
6.622
1713.937
20.548
1808.826
8.879
1827.799
6.859
1856.892
7.567
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

Properly size images
Images can slow down the page's load time. Ebalka.kim should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Ebalka.kim should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Ebalka.kim should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Ebalka.kim should consider minifying JS files.
Reduce unused CSS — Potential savings of 11 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Ebalka.kim should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://sex.ebalka.kim/static/1524304640913/main.css
13361
11273
Reduce unused JavaScript — Potential savings of 70 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://sex.ebalka.kim/static/1524258613548/combine.js
66516
40245
https://www.googletagmanager.com/gtag/js?id=G-NK7DRKKFN7
75593
31153
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 430 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://sex.ebalka.kim/
431.129
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Ebalka.kim should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://ebalka.kim/
190
http://sex.ebalka.kim/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Ebalka.kim 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 — Potential savings of 70 ms
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
http://sex.ebalka.kim/contents/videos_screenshots/135000/135023/240x180/1.jpg
70
Avoids enormous network payloads — Total size was 430 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.googletagmanager.com/gtag/js?id=G-NK7DRKKFN7
75593
http://sex.ebalka.kim/static/1524258613548/combine.js
66516
http://sex.ebalka.kim/img/bg.png
57348
http://sex.ebalka.kim/contents/videos_screenshots/112000/112921/240x180/1.jpg
17171
http://sex.ebalka.kim/contents/videos_screenshots/96000/96267/240x180/1.jpg
16981
http://sex.ebalka.kim/
16873
http://sex.ebalka.kim/contents/videos_screenshots/89000/89066/240x180/1.jpg
16655
http://sex.ebalka.kim/contents/videos_screenshots/82000/82600/240x180/1.jpg
16265
http://site.yandex.net/v2.0/js/all.js
15957
http://sex.ebalka.kim/contents/videos_screenshots/118000/118624/240x180/1.jpg
15742
Uses efficient cache policy on static assets — 4 resources found
Ebalka.kim 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://sex.ebalka.kim/?mode=async&action=js_stats&rand=1666088238900
0
662
http://sex.ebalka.kim/?mode=async&action=js_stats&rand=1666088239026
0
660
http://site.yandex.net/v2.0/js/all.js
216013000
15957
http://sex.ebalka.kim/js/KernelTeamVideoSharingSystem.js?v=5.5.0
604800000
2736
Avoids an excessive DOM size — 809 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
809
Maximum DOM Depth
10
Maximum Child Elements
199
Avoid chaining critical requests — 4 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Ebalka.kim 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)
http://sex.ebalka.kim/
266.489
4.463
1.472
http://sex.ebalka.kim/static/1524258613548/combine.js
131.543
85.584
3.508
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)
Rendering
136.658
Script Evaluation
133.88
Style & Layout
106.318
Other
84.074
Parse HTML & CSS
13.465
Script Parsing & Compilation
9.782
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 — 35 requests • 430 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
35
440501
Image
24
228700
Script
4
160802
Font
2
18659
Document
1
16873
Stylesheet
2
14784
Other
2
683
Media
0
0
Third-party
6
111632
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)
75593
0
20082
0
0
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.
Element
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.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
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 ebalka.kim 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.

Metrics

First Contentful Paint — 1.0 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 1.3 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 1.5 s
The timing of the largest text or image that is painted.

Audits

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

Other

Eliminate render-blocking resources — Potential savings of 430 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Ebalka.kim should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
http://sex.ebalka.kim/static/1524304640913/main.css
13361
70
http://sex.ebalka.kim/js/KernelTeamVideoSharingSystem.js?v=5.5.0
2736
110
Serve images in next-gen formats — Potential savings of 94 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://sex.ebalka.kim/img/bg.png
56599
51928.15
http://sex.ebalka.kim/contents/videos_screenshots/112000/112921/240x180/1.jpg
16426
9539.6
http://sex.ebalka.kim/contents/videos_screenshots/89000/89066/240x180/1.jpg
15916
9227.95
http://sex.ebalka.kim/contents/videos_screenshots/82000/82600/240x180/1.jpg
15522
9068.7
http://sex.ebalka.kim/contents/videos_screenshots/96000/96267/240x180/1.jpg
16242
8611.45
http://sex.ebalka.kim/contents/videos_screenshots/118000/118624/240x180/1.jpg
14985
8378.85

Metrics

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

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of ebalka.kim. 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

`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"]`
Ebalka.kim may provide assistance to deaf or hearing-impaired users with captions on videos.

ARIA

`[aria-*]` attributes do not match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
Failing Elements

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 ebalka.kim 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.
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
Host allowlists can frequently be bypassed. Consider using CSP nonces or hashes instead, along with 'strict-dynamic' if necessary.
script-src
High
'unsafe-inline' allows the execution of unsafe in-page scripts and event handlers. Consider using CSP nonces or hashes to allow scripts individually.
script-src
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.
Name Version
jQuery
1.9.1
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 — 30 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://ebalka.kim/
Allowed
http://sex.ebalka.kim/
Allowed
http://sex.ebalka.kim/static/1524304640913/main.css
Allowed
http://sex.ebalka.kim/js/KernelTeamVideoSharingSystem.js?v=5.5.0
Allowed
http://sex.ebalka.kim/static/1524258613548/combine.js
Allowed
http://sex.ebalka.kim/?mode=async&action=js_stats&rand=1666088238900
Allowed
http://sex.ebalka.kim/img/bg.png
Allowed
http://sex.ebalka.kim/images/vkIcon.png
Allowed
http://sex.ebalka.kim/images/okIcon.png
Allowed
http://sex.ebalka.kim/images/facebookIcon.png
Allowed
http://sex.ebalka.kim/images/twitterIcon.png
Allowed
http://sex.ebalka.kim/images/googleIcon.png
Allowed
http://sex.ebalka.kim/images/mailIcon.png
Allowed
http://sex.ebalka.kim/img/logo_small_blue_new.png
Allowed
http://sex.ebalka.kim/img/logos.png
Allowed
http://sex.ebalka.kim/img/nav-bg.png
Allowed
http://sex.ebalka.kim/img/img.png
Allowed
http://site.yandex.net/v2.0/js/all.js
Allowed
http://sex.ebalka.kim/img/search-btn.jpg
Allowed
http://sex.ebalka.kim/?mode=async&action=js_stats&rand=1666088239026
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135023/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/118000/118624/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/112000/112921/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/104000/104992/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/99000/99300/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/96000/96267/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/89000/89115/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/89000/89066/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/82000/82600/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/82000/82062/240x180/1.jpg
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 4 vulnerabilities detected
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.
Library Version Vulnerability Count Highest Severity
4
Medium
92

SEO

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

Crawling and Indexing

Links are not 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.

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 ebalka.kim. 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 ebalka.kim 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 64
Accessibility 87
Best Practices 75
SEO 91
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://sex.ebalka.kim/
Updated: 18th October, 2022

1.11 seconds
First Contentful Paint (FCP)
89%
7%
4%

0.06 seconds
First Input Delay (FID)
96%
4%
0%

64

Performance

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

Other

Properly size images
Images can slow down the page's load time. Ebalka.kim should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Ebalka.kim should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Ebalka.kim should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Ebalka.kim should consider minifying JS files.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 260 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://sex.ebalka.kim/
257.275
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Ebalka.kim should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://ebalka.kim/
630
http://sex.ebalka.kim/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Ebalka.kim 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.
Avoids enormous network payloads — Total size was 922 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.googletagmanager.com/gtag/js?id=G-NK7DRKKFN7
75627
http://sitewithg.com/sweetie/hello.min.js?id=1629881082
70081
http://sex.ebalka.kim/static/1524258613548/combine.js
66522
http://sex.ebalka.kim/img/bg.png
57354
http://sex.ebalka.kim/contents/videos_screenshots/135000/135063/240x180/1.jpg
19801
http://sex.ebalka.kim/contents/videos_screenshots/135000/135118/240x180/1.jpg
19035
http://sex.ebalka.kim/contents/videos_screenshots/135000/135115/240x180/1.jpg
18067
http://sex.ebalka.kim/contents/videos_screenshots/112000/112921/240x180/1.jpg
17165
http://sex.ebalka.kim/
17048
http://sex.ebalka.kim/contents/videos_screenshots/96000/96267/240x180/1.jpg
16983
Avoids an excessive DOM size — 810 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
810
Maximum DOM Depth
10
Maximum Child Elements
199
Avoid chaining critical requests — 4 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Ebalka.kim 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.7 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://sex.ebalka.kim/
846.456
20.104
7.592
http://sex.ebalka.kim/static/1524258613548/combine.js
443.792
228.344
16.228
https://www.googletagmanager.com/gtag/js?id=G-NK7DRKKFN7
304.848
270.088
19.588
Unattributable
248.088
8.664
0
http://sitewithg.com/sweetie/hello.min.js?id=1629881082
92.088
68.276
19.736
Minimizes main-thread work — 2.0 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
613.852
Style & Layout
469.692
Other
377.408
Rendering
375.496
Parse HTML & CSS
73.308
Script Parsing & Compilation
68.916
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 — 64 requests • 922 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
64
944050
Image
51
661643
Script
6
231225
Font
2
18659
Document
1
17048
Stylesheet
2
14792
Other
2
683
Media
0
0
Third-party
8
182044
Minimize third-party usage — Third-party code blocked the main thread for 100 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)
75627
102.712
20082
0
0
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.
Element
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 7 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.googletagmanager.com/gtag/js?id=G-NK7DRKKFN7
3868
164
https://www.googletagmanager.com/gtag/js?id=G-NK7DRKKFN7
4032
150
http://sex.ebalka.kim/
1468
138
http://sex.ebalka.kim/static/1524258613548/combine.js
3660
133
https://www.googletagmanager.com/gtag/js?id=G-NK7DRKKFN7
3793
75
http://sitewithg.com/sweetie/hello.min.js?id=1629881082
3590
70
http://sex.ebalka.kim/
1410
50
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
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 ebalka.kim 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.

Audits

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://ebalka.kim/
http/1.1
0
279.94200005196
683
0
301
text/html
http://sex.ebalka.kim/
http/1.1
280.39199998602
536.67300008237
17048
89373
200
text/html
Document
http://sex.ebalka.kim/static/1524304640913/main.css
http/1.1
549.11400005221
805.48300000373
13369
60707
200
text/css
Stylesheet
http://sex.ebalka.kim/js/KernelTeamVideoSharingSystem.js?v=5.5.0
http/1.1
549.45000004955
576.38500002213
2741
6116
200
application/javascript
Script
http://sex.ebalka.kim/static/1524258613548/combine.js
http/1.1
549.71500008833
577.99700007308
66522
197948
200
application/javascript
Script
https://www.googletagmanager.com/gtag/js?id=G-NK7DRKKFN7
h2
593.35300000384
626.9420000026
75627
213320
200
application/javascript
Script
http://sitewithg.com/sweetie/hello.min.js?id=1629881082
http/1.1
649.13300005719
1054.7329999972
70081
204640
200
application/javascript
Script
https://fonts.googleapis.com/css?family=Open+Sans+Condensed:300,700&subset=latin,latin-ext&display=swap
h2
807.58100003004
827.63900002465
1423
5010
200
text/css
Stylesheet
http://sex.ebalka.kim/?mode=async&action=js_stats&rand=1666088257969
http/1.1
831.9350000238
1065.3630000306
656
43
200
image/gif
Image
http://sex.ebalka.kim/img/bg.png
http/1.1
835.17700002994
861.00100004114
57354
56599
200
image/png
Image
http://site.yandex.net/v2.0/js/all.js
http/1.1
838.45800010022
1206.8880000152
15957
57430
200
application/javascript
Script
data
839.07800004818
839.21200002078
0
42
200
image/gif
Image
http://sex.ebalka.kim/img/logo_small_blue_new.png
http/1.1
876.04400003329
1115.6160000246
4072
3327
200
image/png
Image
http://sex.ebalka.kim/img/nav-icon.png
http/1.1
876.27700006124
901.44200006034
896
141
200
image/png
Image
https://fonts.gstatic.com/s/opensanscondensed/v23/z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff0GmDuHMR7eS2AopSg.woff2
h2
885.31600008719
889.88900010008
7459
6532
200
font/woff2
Font
https://fonts.gstatic.com/s/opensanscondensed/v23/z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff0GmDuXMR7eS2Ao.woff2
h2
888.2010000525
891.33800007403
11200
10272
200
font/woff2
Font
http://sex.ebalka.kim/img/search-btn.jpg
http/1.1
1025.9160000132
1278.4550000215
1965
1200
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135023/240x180/1.jpg
http/1.1
1031.355000101
1057.2990000946
11029
10259
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/118000/118624/240x180/1.jpg
http/1.1
1031.4850000432
1393.7300000107
15724
14985
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/112000/112921/240x180/1.jpg
http/1.1
1032.0570000913
1385.3540000273
17165
16426
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/104000/104992/240x180/1.jpg
http/1.1
1032.2790000355
1284.970000037
8019
7275
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/99000/99300/240x180/1.jpg
http/1.1
1032.61200001
1276.1560000945
13108
12335
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/96000/96267/240x180/1.jpg
http/1.1
1032.9430000857
1386.4360000007
16983
16242
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/89000/89115/240x180/1.jpg
http/1.1
1033.2800000906
1282.5290000765
13501
12758
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/89000/89066/240x180/1.jpg
http/1.1
1033.6320000933
1126.1990000494
16682
15916
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/82000/82600/240x180/1.jpg
http/1.1
1033.8470001006
1389.9560000282
16267
15522
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/82000/82062/240x180/1.jpg
http/1.1
1034.2220000457
1116.8690000195
12764
12002
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135152/240x180/1.jpg
http/1.1
1034.454000066
1285.2670000866
8367
7607
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135142/240x180/1.jpg
http/1.1
1034.6380000701
1170.6450000638
15518
14755
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135141/240x180/1.jpg
http/1.1
1035.2060000878
1281.8210000405
13125
12360
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135134/240x180/1.jpg
http/1.1
1036.22800007
1166.9890000485
9285
8523
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135133/240x180/1.jpg
http/1.1
1036.3990000915
1172.9530000594
11502
10741
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135130/240x180/1.jpg
http/1.1
1036.6110000759
1069.9790000217
11524
10768
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135118/240x180/1.jpg
http/1.1
1037.0260000927
1064.1450000694
19035
18263
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135117/240x180/1.jpg
http/1.1
1037.4280000106
1171.871000086
13492
12733
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135115/240x180/1.jpg
http/1.1
1037.6080001006
1285.635999986
18067
17302
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135114/240x180/1.jpg
http/1.1
1037.9670000402
1309.5290000783
11267
10506
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135112/240x180/1.jpg
http/1.1
1038.0870000226
1080.9170000721
15925
15154
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135110/240x180/1.jpg
http/1.1
1038.9229999855
1076.3670000015
16901
16125
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135108/240x180/1.jpg
http/1.1
1039.2310000025
1064.7779999999
13775
13011
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135105/240x180/1.jpg
http/1.1
1039.4540000707
1312.4500000849
16153
15388
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135104/240x180/1.jpg
http/1.1
1039.5870000357
1070.8300000988
15897
15134
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135103/240x180/1.jpg
http/1.1
1039.7710000398
1070.398000069
12362
11589
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135102/240x180/1.jpg
http/1.1
1040.0620000437
1104.3920000084
15021
14260
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135096/240x180/1.jpg
http/1.1
1040.2510000858
1326.659000013
9080
8318
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135085/240x180/1.jpg
http/1.1
1040.605999995
1200.4900000757
8571
7803
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135084/240x180/1.jpg
http/1.1
1040.8950001001
1096.4410000015
8950
8188
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135080/240x180/1.jpg
http/1.1
1041.9170000823
1325.0760000665
7534
6768
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135078/240x180/1.jpg
http/1.1
1042.2080000862
1083.10300007
11501
10737
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135077/240x180/1.jpg
http/1.1
1042.426
1317.5880000927
15620
14851
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135076/240x180/1.jpg
http/1.1
1042.6070000976
1304.9270000774
14130
13361
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135073/240x180/1.jpg
http/1.1
1042.8000000538
1091.3060000166
11158
10394
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135070/240x180/1.jpg
http/1.1
1042.9320000112
1094.5630000206
8806
8041
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135067/240x180/1.jpg
http/1.1
1043.5760000255
1102.5310000405
11450
10687
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135066/240x180/1.jpg
http/1.1
1043.7650000677
1092.430000077
12142
11375
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135065/240x180/1.jpg
http/1.1
1044.9440000812
1115.2340000262
10917
10153
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135064/240x180/1.jpg
http/1.1
1049.3530000094
1099.5760000078
9569
8799
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135063/240x180/1.jpg
http/1.1
1049.4900000049
1100.0010001007
19801
19030
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135062/240x180/1.jpg
http/1.1
1049.6430000057
1099.1130000912
10419
9657
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135061/240x180/1.jpg
http/1.1
1049.7750000795
1305.7920000283
14957
14188
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135060/240x180/1.jpg
http/1.1
1049.8960000696
1308.6950000143
16943
16174
200
image/jpeg
Image
http://sex.ebalka.kim/contents/videos_screenshots/135000/135059/240x180/1.jpg
http/1.1
1053.8830000442
1097.5470000412
16028
15263
200
image/jpeg
Image
http://sex.ebalka.kim/?mode=async&action=js_stats&rand=1666088258126
http/1.1
1054.0350000374
1291.6310000001
666
43
200
image/gif
Image
https://www.google-analytics.com/g/collect?v=2&tid=G-NK7DRKKFN7&gtm=2oeaa0&_p=178355073&cid=98278072.1666088258&ul=en-us&sr=360x640&_s=1&sid=1666088258&sct=1&seg=0&dl=http%3A%2F%2Fsex.ebalka.kim%2F&dt=%D0%A0%D1%83%D1%81%D1%81%D0%BA%D0%BE%D0%B5%20%D0%BF%D0%BE%D1%80%D0%BD%D0%BE%3A%20%D0%BD%D0%BE%D0%B2%D0%B8%D0%BD%D0%BA%D0%B8%20%D0%B2%20HD%20%D0%B8%20%D1%8D%D0%BA%D1%81%D0%BA%D0%BB%D1%8E%D0%B7%D0%B8%D0%B2%20%7C%20%D0%95%D0%B1%D0%B0%D0%BB%D0%BA%D0%B0&en=page_view&_fv=1&_nsi=1&_ss=1&_ee=1
1091.9960000319
1116.3769999985
0
0
-1
Ping
https://sitewithg.com/osvald/1753?n=bm8c53d&ab=true&ts=1666088258364&fg=null&mb=null&rt=false&id=1666088258363&tz=420&ps=1666088257136&action=init
h2
1227.676999988
1559.8000000464
297
42
200
text/html
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)
541.967
12.576
841.856
33.329
875.957
68.828
945.951
18.647
964.624
81.904
1046.555
6.169
1056.869
37.529
1095.119
11.178
1123.128
8.641
1139.244
9.878
1149.246
17.377
1181.785
9.639
1203.088
6.148
1284.304
9.246
1298.288
10.873
1315.134
8.065
1332.086
8.987
1399.525
12.442
1664.123
21.737
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

Time to Interactive — 4.2 s
The time taken for the page to become fully interactive.
Speed Index — 3.7 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 220 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).

Audits

Max Potential First Input Delay — 160 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 3.3 s
The time taken for the primary content of the page to be rendered.

Other

Reduce unused CSS — Potential savings of 12 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Ebalka.kim should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://sex.ebalka.kim/static/1524304640913/main.css
13369
12268
Reduce unused JavaScript — Potential savings of 110 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://sex.ebalka.kim/static/1524258613548/combine.js
66522
44435
http://sitewithg.com/sweetie/hello.min.js?id=1629881082
70081
36913
https://www.googletagmanager.com/gtag/js?id=G-NK7DRKKFN7
75627
31167
Serve images in next-gen formats — Potential savings of 192 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://sex.ebalka.kim/img/bg.png
56599
51928.15
http://sex.ebalka.kim/contents/videos_screenshots/135000/135063/240x180/1.jpg
19030
10757.5
http://sex.ebalka.kim/contents/videos_screenshots/135000/135118/240x180/1.jpg
18263
10415.15
http://sex.ebalka.kim/contents/videos_screenshots/135000/135115/240x180/1.jpg
17302
9741.35
http://sex.ebalka.kim/contents/videos_screenshots/112000/112921/240x180/1.jpg
16426
9539.6
http://sex.ebalka.kim/contents/videos_screenshots/89000/89066/240x180/1.jpg
15916
9227.95
http://sex.ebalka.kim/contents/videos_screenshots/82000/82600/240x180/1.jpg
15522
9068.7
http://sex.ebalka.kim/contents/videos_screenshots/135000/135060/240x180/1.jpg
16174
8956.8
http://sex.ebalka.kim/contents/videos_screenshots/135000/135104/240x180/1.jpg
15134
8922
http://sex.ebalka.kim/contents/videos_screenshots/135000/135061/240x180/1.jpg
14188
8850.25
http://sex.ebalka.kim/contents/videos_screenshots/135000/135110/240x180/1.jpg
16125
8664.7
http://sex.ebalka.kim/contents/videos_screenshots/96000/96267/240x180/1.jpg
16242
8611.45
http://sex.ebalka.kim/contents/videos_screenshots/135000/135105/240x180/1.jpg
15388
8551.8
http://sex.ebalka.kim/contents/videos_screenshots/135000/135059/240x180/1.jpg
15263
8534.4
http://sex.ebalka.kim/contents/videos_screenshots/135000/135112/240x180/1.jpg
15154
8440.6
http://sex.ebalka.kim/contents/videos_screenshots/118000/118624/240x180/1.jpg
14985
8378.85
http://sex.ebalka.kim/contents/videos_screenshots/135000/135102/240x180/1.jpg
14260
8247.7
Avoid serving legacy JavaScript to modern browsers — Potential savings of 15 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)
http://sitewithg.com/sweetie/hello.min.js?id=1629881082
15835
Preload Largest Contentful Paint image — Potential savings of 630 ms
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
http://sex.ebalka.kim/contents/videos_screenshots/135000/135023/240x180/1.jpg
630
Serve static assets with an efficient cache policy — 6 resources found
Ebalka.kim 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://sex.ebalka.kim/?mode=async&action=js_stats&rand=1666088258126
0
666
http://sex.ebalka.kim/?mode=async&action=js_stats&rand=1666088257969
0
656
https://sitewithg.com/osvald/1753?n=bm8c53d&ab=true&ts=1666088258364&fg=null&mb=null&rt=false&id=1666088258363&tz=420&ps=1666088257136&action=init
0
297
http://sitewithg.com/sweetie/hello.min.js?id=1629881082
86400000
70081
http://site.yandex.net/v2.0/js/all.js
216013000
15957
http://sex.ebalka.kim/js/KernelTeamVideoSharingSystem.js?v=5.5.0
604800000
2741

Metrics

First Contentful Paint — 3.3 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 4.2 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.306
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Eliminate render-blocking resources — Potential savings of 1,230 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Ebalka.kim should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
http://sex.ebalka.kim/static/1524304640913/main.css
13369
180
http://sex.ebalka.kim/js/KernelTeamVideoSharingSystem.js?v=5.5.0
2741
330
First Contentful Paint (3G) — 6750 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
87

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of ebalka.kim. 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

`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"]`
Ebalka.kim may provide assistance to deaf or hearing-impaired users with captions on videos.

ARIA

`[aria-*]` attributes do not match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
Failing Elements

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that ebalka.kim 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.
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
Host allowlists can frequently be bypassed. Consider using CSP nonces or hashes instead, along with 'strict-dynamic' if necessary.
script-src
High
'unsafe-inline' allows the execution of unsafe in-page scripts and event handlers. Consider using CSP nonces or hashes to allow scripts individually.
script-src
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.
Name Version
jQuery
1.9.1
core-js
core-js-pure@3.9.1
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 — 58 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://ebalka.kim/
Allowed
http://sex.ebalka.kim/
Allowed
http://sex.ebalka.kim/static/1524304640913/main.css
Allowed
http://sex.ebalka.kim/js/KernelTeamVideoSharingSystem.js?v=5.5.0
Allowed
http://sex.ebalka.kim/static/1524258613548/combine.js
Allowed
http://sitewithg.com/sweetie/hello.min.js?id=1629881082
Allowed
http://sex.ebalka.kim/?mode=async&action=js_stats&rand=1666088257969
Allowed
http://sex.ebalka.kim/img/bg.png
Allowed
http://site.yandex.net/v2.0/js/all.js
Allowed
http://sex.ebalka.kim/img/logo_small_blue_new.png
Allowed
http://sex.ebalka.kim/img/nav-icon.png
Allowed
http://sex.ebalka.kim/img/search-btn.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135023/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/118000/118624/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/112000/112921/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/104000/104992/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/99000/99300/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/96000/96267/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/89000/89115/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/89000/89066/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/82000/82600/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/82000/82062/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135152/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135142/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135141/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135134/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135133/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135130/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135118/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135117/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135115/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135114/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135112/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135110/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135108/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135105/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135104/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135103/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135102/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135096/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135085/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135084/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135080/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135078/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135077/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135076/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135073/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135070/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135067/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135066/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135065/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135064/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135063/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135062/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135061/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135060/240x180/1.jpg
Allowed
http://sex.ebalka.kim/contents/videos_screenshots/135000/135059/240x180/1.jpg
Allowed
http://sex.ebalka.kim/?mode=async&action=js_stats&rand=1666088258126
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 4 vulnerabilities detected
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.
Library Version Vulnerability Count Highest Severity
4
Medium

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://sex.ebalka.kim/contents/videos_screenshots/104000/104992/240x180/1.jpg
170 x 128
240 x 180
340 x 256
http://sex.ebalka.kim/contents/videos_screenshots/112000/112921/240x180/1.jpg
170 x 128
240 x 180
340 x 256
http://sex.ebalka.kim/contents/videos_screenshots/118000/118624/240x180/1.jpg
170 x 128
240 x 180
340 x 256
http://sex.ebalka.kim/contents/videos_screenshots/135000/135023/240x180/1.jpg
170 x 128
240 x 180
340 x 256
http://sex.ebalka.kim/contents/videos_screenshots/96000/96267/240x180/1.jpg
170 x 128
240 x 180
340 x 256
http://sex.ebalka.kim/contents/videos_screenshots/99000/99300/240x180/1.jpg
170 x 128
240 x 180
340 x 256
91

SEO

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

Content Best Practices

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

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
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.

Crawling and Indexing

Links are not 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.

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 ebalka.kim. 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 ebalka.kim 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: 104.26.12.96
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

Name IP Address
Name.com, Inc. 104.18.6.161
Security

Visitor Safety

Mature Content: Yes
McAfee WebAdvisor Rating: Unknown
WOT Rating:
WOT Trustworthiness: 80/100
WOT Child Safety: 10/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: sni.cloudflaressl.com
Issued By: Cloudflare Inc ECC CA-3
Valid From: 26th June, 2022
Valid To: 25th June, 2023
Subject: CN = sni.cloudflaressl.com
O = Cloudflare, Inc.
L = San Francisco
S = US
Hash: c959965e
Issuer: CN = Cloudflare Inc ECC CA-3
O = Cloudflare, Inc.
S = US
Version: 2
Serial Number: 13807882189093393593169973130225005281
Serial Number (Hex): 0A634D271602506394C6B94417B032E1
Valid From: 26th June, 2024
Valid To: 25th June, 2024
Signature Algorithm (Short Name): ecdsa-with-SHA256
Signature Algorithm (Long Name): ecdsa-with-SHA256
Authority Key Identifier: keyid:A5:CE:37:EA:EB:B0:75:0E:94:67:88:B4:45:FA:D9:24:10:87:96:1F
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/CloudflareIncECCCA-3.crl

Full Name:
URI:http://crl4.digicert.com/CloudflareIncECCCA-3.crl

Certificate Policies: Policy: 2.23.140.1.2.2
CPS: http://www.digicert.com/CPS

Authority Information Access: OCSP - URI:http://ocsp.digicert.com
CA Issuers - URI:http://cacerts.digicert.com/CloudflareIncECCCA-3.crt

SCT List: 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 : Jun 26 19:25:34.054 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:AB:BC:96:64:49:D6:0D:0C:27:F6:FE:
4B:F9:E7:DB:1D:E0:AE:DF:62:CA:C5:BB:7C:C5:56:3F:
3E:14:10:DB:22:02:21:00:9B:2A:36:9C:D4:E8:FF:34:
D6:45:0C:D3:D3:11:2E:37:C5:9B:DF:19:A5:17:E6:6E:
EC:BB:F3:90:3E:FC:17:45
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 35:CF:19:1B:BF:B1:6C:57:BF:0F:AD:4C:6D:42:CB:BB:
B6:27:20:26:51:EA:3F:E1:2A:EF:A8:03:C3:3B:D6:4C
Timestamp : Jun 26 19:25:34.059 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:98:DA:52:2B:6D:4B:71:88:62:AA:5B:
35:90:4D:96:52:12:55:3D:5F:43:4C:D8:4C:7A:C5:6E:
E3:1F:24:C2:35:02:20:6E:15:72:F5:CF:9B:8B:A6:B1:
10:08:92:5B:4F:06:54:5D:D2:60:93:A7:CB:06:02:0A:
43:69:9B:A8:59:C0:67
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : B3:73:77:07:E1:84:50:F8:63:86:D6:05:A9:DC:11:09:
4A:79:2D:B1:67:0C:0B:87:DC:F0:03:0E:79:36:A5:9A
Timestamp : Jun 26 19:25:34.104 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:B6:EF:03:CF:A2:31:16:3D:E5:37:19:
BC:CD:41:71:F8:59:DF:52:EA:35:07:42:9C:EA:5B:2C:
1A:AA:E7:E7:80:02:21:00:AD:45:D6:BF:B0:44:34:C3:
96:D2:36:4B:6E:81:4A:77:F4:70:79:26:4B:94:3A:43:
88:78:1F:30:86:95:99:DE
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:ebalka.kim
DNS:sni.cloudflaressl.com
DNS:*.ebalka.kim
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 403 Forbidden
Date: 18th October, 2022
Content-Type: text/html; charset=UTF-8
Cache-Control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Expires: 1st January, 1970
Server: cloudflare
Connection: close
CF-Chl-Bypass: 1
Referer-Policy: same-origin
Permissions-Policy: accelerometer=(),autoplay=(),camera=(),clipboard-read=(),clipboard-write=(),fullscreen=(),geolocation=(),gyroscope=(),hid=(),interest-cohort=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=()
X-Frame-Options: SAMEORIGIN
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=aJHKtg6ZD4ccjQkexOf6SiY6Tj0ut%2FanoL6NZZqHiQFunascMysBTp9oYAy8IxAjKXGnQVMsRKfw5t3CBCSRXNLOqGeTVJX%2FY7z1zYcYR7JIty0q%2BrCzRMAp%2FNI%3D"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
CF-RAY: 75c085e44ed8e760-EWR

Whois Lookup

Created: 25th June, 2022
Changed: 30th June, 2022
Expires: 25th June, 2023
Registrar: Name.com, Inc.
Status: clientTransferProhibited
Nameservers: mary.ns.cloudflare.com
pete.ns.cloudflare.com
Owner Name: REDACTED FOR PRIVACY
Owner Organization: Domain Protection Services, Inc.
Owner Street: REDACTED FOR PRIVACY
Owner Post Code: REDACTED FOR PRIVACY
Owner City: REDACTED FOR PRIVACY
Owner State: CO
Owner Country: US
Owner Phone: REDACTED FOR PRIVACY
Owner Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Post Code: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Post Code: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Full Whois: Domain Name: ebalka.kim
Registry Domain ID: 6dd6425bd8f04c03b34db311367a190c-DONUTS
Registrar WHOIS Server: whois.name.com
Registrar URL: http://www.name.com
Updated Date: 2022-06-30T19:30:10Z
Creation Date: 2022-06-25T19:29:47Z
Registry Expiry Date: 2023-06-25T19:29:47Z
Registrar: Name.com, Inc.
Registrar IANA ID: 625
Registrar Abuse Contact Email: abuse@name.com
Registrar Abuse Contact Phone: +1.7203101849
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: Domain Protection Services, Inc.
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: CO
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: US
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: mary.ns.cloudflare.com
Name Server: pete.ns.cloudflare.com
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2022-10-18T10:17:15Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

Terms of Use: Donuts Inc. provides this Whois service for information purposes, and to assist persons in obtaining information about or related to a domain name registration record. Donuts does not guarantee its accuracy. Users accessing the Donuts Whois service agree to use the data only for lawful purposes, and under no circumstances may this data be used to: a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the registrar's own existing customers and b) enable high volume, automated, electronic processes that send queries or data to the systems of Donuts or any ICANN-accredited registrar, except as reasonably necessary to register domain names or modify existing registrations. When using the Donuts Whois service, please consider the following: The Whois service is not a replacement for standard EPP commands to the SRS service. Whois is not considered authoritative for registered domain objects. The Whois service may be scheduled for downtime during production or OT&E maintenance periods. Queries to the Whois services are throttled. If too many queries are received from a single IP address within a specified time, the service will begin to reject further queries for a period of time to prevent disruption of Whois service access. Abuse of the Whois system through data mining is mitigated by detecting and limiting bulk query access from single sources. Where applicable, the presence of a [Non-Public Data] tag indicates that such data is not made publicly available due to applicable data privacy laws or requirements. Should you wish to contact the registrant, please refer to the Whois records available through the registrar URL listed above. Access to non-public data may be provided, upon request, where it can be reasonably confirmed that the requester holds a specific legitimate interest and a proper legal basis for accessing the withheld data. Access to this data can be requested by submitting a request via the form found at https://donuts.domains/about/policies/whois-layered-access/ Donuts Inc. reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.

Nameservers

Name IP Address
mary.ns.cloudflare.com 173.245.58.134
pete.ns.cloudflare.com 172.64.33.136
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
$12,591 USD 2/5
0/5
0/5
0/5

Sites hosted on the same IP address