hlebo.com

hlebo.com is SSL secured

Free website and domain report on hlebo.com

Last Updated: 31st October, 2023 Update Now
Overview

Snoop Summary for hlebo.com

This is a free and comprehensive report about hlebo.com. Hlebo.com is hosted in United States on a server with an IP address of 104.21.77.126, where USD is the local currency and the local language is English. Our records indicate that hlebo.com is privately registered by DATA REDACTED. Hlebo.com is expected to earn an estimated $69 USD per day from advertising revenue. The sale of hlebo.com would possibly be worth $50,522 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Hlebo.com receives an estimated 16,362 unique visitors every day - a huge amount of traffic! This report was last updated 31st October, 2023.

What is hlebo.com?

Hlebo.com is an adults-only porn site where you can download, stream and watch porn online. We advise against visiting websites like hlebo.com as they contain mature and potentially unsafe content.

About hlebo.com

Site Preview:
Title: XXX Videos! Porn Videos! 3GP MP4 Mobile Sex XXX Porno Videos!
Description: XXX Videos! 3GP Porn, MP4 Porn Videos, Mobile Sex Videos, Mobile XXX, Mobile Porno! Mobile XXX Porno!
Keywords and Tags: adult content, adult movies, adults only, asian teen wank, big ass sex tape, big booty milf, bokep indo goyang, brazzers jordi, hot korean teen porn, huge tits bouncing, mature content, milf booty, mom saw my hard dick, nsfw, nude tik tok girl, passion hd asian, popular, porn, porn movies, pornography, roots xxx, www japanxxxcom, wwwsexiran, xnxx indonesia, xxx movies
Related Terms: 3gp indo, free 3gp videos, indo 3gp, see xxx, solidfiles mp4, tranny xxx videos, videos de maduras xxx, xxx forums, xxx thumbs, xxx vid
Fav Icon:
Age: Over 7 years old
Domain Created: 5th October, 2016
Domain Updated: 7th March, 2022
Domain Expires: 5th October, 2023
Review

Snoop Score

3/5 (Great!)

Valuation

$50,522 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 39,861
Alexa Reach:
SEMrush Rank (US): 16,482,942
SEMrush Authority Score:
Moz Domain Authority: 16
Moz Page Authority: 40

Organic vs Paid (Google Ads)

Organic Paid
Keywords: 18 0
Traffic: 1 0
Cost: $0 USD $0 USD
Traffic

Visitors

Daily Visitors: 16,362
Monthly Visitors: 498,018
Yearly Visitors: 5,972,256
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $69 USD
Monthly Revenue: $2,106 USD
Yearly Revenue: $25,256 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

1
Keyword: brazzers jordi
Ranked Page: https://hlebo.com/video/brazzers-brazzers-exxtra-hardcore-high-notes-scene-starring-phoenix-marie-and-jordi-el-ni-and-n

2
Keyword: big ass sex tape
Ranked Page: https://hlebo.com/video/mamacitaz-big-ass-latina-teen-andrea-flores-has-christmas-sex-on-hot-revenge-sex-tape

3
Keyword: mom saw my hard dick
Ranked Page: https://hlebo.com/video/japanese-mom-saw-my-hard-dick

4
Keyword: asian teen wank
Ranked Page: https://hlebo.com/video/asian-teen-wank-midget-cock

5
Keyword: xnxx indonesia
Ranked Page: https://hlebo.com/video/xnxx-indo

Domain Analysis

Value Length
Domain: hlebo.com 9
Domain Name: hlebo 5
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 0.57 seconds
Load Time Comparison: Faster than 93% of sites

PageSpeed Insights

Avg. (All Categories) 82
Performance 100
Accessibility 97
Best Practices 92
SEO 100
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
100

Performance

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

Metrics

First Contentful Paint — 0.4 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.4 s
The time taken for the page to become fully interactive.
Speed Index — 0.5 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 0.4 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 30 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.4 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://hlebo.com/
http/1.1
0
85.287000052631
725
0
301
text/plain
https://hlebo.com/
h2
85.686000064015
306.42600008287
12779
56725
200
text/html
Document
data
324.98800009489
325.11999993585
0
650
200
image/svg+xml
Image
https://hlebo.com/thumbs/55121.jpg
h2
344.22600013204
554.2040001601
12442
11763
200
image/jpeg
Image
https://hlebo.com/thumbs/28075.jpg
h2
344.48900003918
545.5700000748
9390
8708
200
image/jpeg
Image
https://hlebo.com/thumbs/710458.jpg
h2
344.6619999595
644.94700008072
10803
10110
200
image/jpeg
Image
https://hlebo.com/thumbs/235327.jpg
h2
345.0619999785
636.41100004315
11663
10982
200
image/jpeg
Image
https://hlebo.com/thumbs/1236389.jpg
h2
352.66100009903
773.70900008827
15470
14793
200
image/jpeg
Image
https://hlebo.com/thumbs/1049661.jpg
h2
352.83600003459
534.28700007498
8498
7818
200
image/jpeg
Image
https://hlebo.com/thumbs/71271.jpg
h2
353.02600008436
542.32700006105
7903
7219
200
image/jpeg
Image
https://hlebo.com/thumbs/78636.jpg
h2
353.38099999353
548.89199999161
11615
10934
200
image/jpeg
Image
https://hlebo.com/thumbs/25422.jpg
h2
353.66200003773
646.53100003488
16536
15857
200
image/jpeg
Image
https://hlebo.com/thumbs/34871.jpg
h2
353.95499994047
443.58299998567
10624
9934
200
image/jpeg
Image
https://counter.yadro.ru/hit?r;s800*600*24;uhttps%3A//hlebo.com/;hXXX%20Videos%21%20Porn%20Videos%21%203GP%20MP4%20Mobile%20Sex%20XXX%20Porno%20Videos%21;0.08672026276530742
http/1.1
361.5970001556
1406.8010000046
710
0
302
text/html
https://hlebo.com/thumbs/1011145.jpg
h2
411.59100015648
590.33400006592
10943
10262
200
image/jpeg
Image
https://hlebo.com/thumbs/845762.jpg
h2
411.77799995057
449.74300009198
8497
7811
200
image/jpeg
Image
https://hlebo.com/thumbs/803704.jpg
h2
411.95000009611
591.83100005612
10638
9952
200
image/jpeg
Image
https://hlebo.com/thumbs/45665.jpg
h2
412.45499998331
564.58400003612
10625
9947
200
image/jpeg
Image
https://hlebo.com/thumbs/138840.jpg
h2
412.6760000363
445.50899998285
10448
9757
200
image/jpeg
Image
https://hlebo.com/thumbs/1065323.jpg
h2
413.01300004125
563.71699995361
10679
9997
200
image/jpeg
Image
https://hlebo.com/thumbs/55557.jpg
h2
413.16900006495
564.88499999978
11563
10882
200
image/jpeg
Image
https://hlebo.com/thumbs/1024320.jpg
h2
413.57800015248
574.15500003844
10674
9992
200
image/jpeg
Image
https://hlebo.com/thumbs/798055.jpg
h2
413.99700008333
677.77700000443
14975
14298
200
image/jpeg
Image
https://hlebo.com/thumbs/45302.jpg
h2
414.25000014715
773.23299995624
7003
6321
200
image/jpeg
Image
https://hlebo.com/thumbs/963838.jpg
h2
414.74799998105
572.03799998388
12300
11625
200
image/jpeg
Image
https://hlebo.com/thumbs/1290776.jpg
h2
415.3599999845
668.74400014058
10727
10050
200
image/jpeg
Image
https://hlebo.com/thumbs/450652.jpg
h2
415.66699999385
681.74999998882
9092
8412
200
image/jpeg
Image
https://hlebo.com/thumbs/485643.jpg
h2
415.86900013499
452.91300001554
8509
7816
200
image/jpeg
Image
https://hlebo.com/thumbs/1323502.jpg
h2
416.15800000727
454.58999997936
9056
8366
200
image/jpeg
Image
https://hlebo.com/thumbs/1323501.jpg
h2
416.42000013962
452.49300007708
7536
6844
200
image/jpeg
Image
https://hlebo.com/thumbs/1323500.jpg
h2
416.66700015776
454.09699995071
11728
11043
200
image/jpeg
Image
https://hlebo.com/thumbs/1323498.jpg
h2
416.88200016506
473.10400009155
14616
13919
200
image/jpeg
Image
https://hlebo.com/thumbs/1323497.jpg
h2
417.06599993631
737.95199999586
10992
10305
200
image/jpeg
Image
https://hlebo.com/thumbs/1323496.jpg
h2
417.31599997729
454.81400005519
4941
4255
200
image/jpeg
Image
https://hlebo.com/thumbs/1323495.jpg
h2
417.62399999425
484.08300010487
5669
4979
200
image/jpeg
Image
https://hlebo.com/thumbs/1323155.jpg
h2
417.92999999598
469.61300005205
8354
7658
200
image/jpeg
Image
https://hlebo.com/thumbs/1323154.jpg
h2
418.15700009465
468.23600004427
7251
6557
200
image/jpeg
Image
https://hlebo.com/thumbs/1323153.jpg
h2
418.27300004661
456.31400006823
11042
10351
200
image/jpeg
Image
https://hlebo.com/thumbs/1323152.jpg
h2
418.99499995634
462.9460000433
12888
12194
200
image/jpeg
Image
https://hlebo.com/thumbs/1323151.jpg
h2
419.1090001259
459.54199996777
9819
9127
200
image/jpeg
Image
https://hlebo.com/thumbs/1323150.jpg
h2
419.55700004473
461.92899998277
10658
9966
200
image/jpeg
Image
https://hlebo.com/thumbs/1323149.jpg
h2
419.67299999669
667.44400002062
15118
14443
200
image/jpeg
Image
https://hlebo.com/thumbs/1323148.jpg
h2
419.90600014105
469.11099995486
11762
11073
200
image/jpeg
Image
https://hlebo.com/thumbs/1323147.jpg
h2
420.06699997
712.69700000994
9904
9228
200
image/jpeg
Image
https://hlebo.com/thumbs/1323146.jpg
h2
420.54500011727
457.14800013229
8590
7900
200
image/jpeg
Image
https://hlebo.com/thumbs/1323145.jpg
h2
420.78000004403
466.26499993727
13094
12399
200
image/jpeg
Image
https://hlebo.com/thumbs/1323144.jpg
h2
420.91600014828
703.47700011916
11741
11058
200
image/jpeg
Image
https://hlebo.com/thumbs/1323143.jpg
h2
421.06700013392
460.75900015421
11238
10550
200
image/jpeg
Image
https://hlebo.com/thumbs/1323142.jpg
h2
421.21200007387
474.43099995144
8120
7430
200
image/jpeg
Image
https://hlebo.com/thumbs/1323141.jpg
h2
421.36200005189
473.86100003496
11216
10521
200
image/jpeg
Image
https://hlebo.com/thumbs/1323140.jpg
h2
421.82700010017
668.48800005391
13252
12567
200
image/jpeg
Image
https://hlebo.com/thumbs/1323139.jpg
h2
422.63000016101
463.64900004119
6626
5935
200
image/jpeg
Image
https://hlebo.com/thumbs/50112.jpg
h2
425.87699997239
486.10000009649
7257
6576
200
image/jpeg
Image
https://hlebo.com/thumbs/215389.jpg
h2
425.98600010388
473.47800014541
11717
11026
200
image/jpeg
Image
https://hlebo.com/thumbs/366218.jpg
h2
426.67299997993
477.62300004251
12330
11636
200
image/jpeg
Image
https://hlebo.com/thumbs/34076.jpg
h2
426.89100001007
478.9940000046
10957
10259
200
image/jpeg
Image
https://hlebo.com/thumbs/833969.jpg
h2
426.97899998166
491.97400012054
7366
6674
200
image/jpeg
Image
https://hlebo.com/thumbs/32537.jpg
h2
427.07299999893
484.71300001256
5739
5054
200
image/jpeg
Image
https://hlebo.com/thumbs/35013.jpg
h2
427.14200005867
499.38799999654
9656
8971
200
image/jpeg
Image
https://hlebo.com/thumbs/25426.jpg
h2
427.27800016291
474.11000006832
5616
4919
200
image/jpeg
Image
https://counter.yadro.ru/hit?q;r;s800*600*24;uhttps%3A//hlebo.com/;hXXX%20Videos%21%20Porn%20Videos%21%203GP%20MP4%20Mobile%20Sex%20XXX%20Porno%20Videos%21;0.08672026276530742
http/1.1
1407.0989999454
2448.6380000599
528
43
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
310.389
9.477
322.938
23.179
348.328
6.407
355.984
13.005
369.324
53.787
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Hlebo.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Hlebo.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Hlebo.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Hlebo.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Hlebo.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Hlebo.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 220 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://hlebo.com/
221.734
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Hlebo.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://hlebo.com/
190
https://hlebo.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Hlebo.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://hlebo.com/thumbs/1011145.jpg
0
Avoids enormous network payloads — Total size was 578 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://hlebo.com/thumbs/25422.jpg
16536
https://hlebo.com/thumbs/1236389.jpg
15470
https://hlebo.com/thumbs/1323149.jpg
15118
https://hlebo.com/thumbs/798055.jpg
14975
https://hlebo.com/thumbs/1323498.jpg
14616
https://hlebo.com/thumbs/1323140.jpg
13252
https://hlebo.com/thumbs/1323145.jpg
13094
https://hlebo.com/thumbs/1323152.jpg
12888
https://hlebo.com/
12779
https://hlebo.com/thumbs/55121.jpg
12442
Uses efficient cache policy on static assets — 0 resources found
Hlebo.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
Avoids an excessive DOM size — 778 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
778
Maximum DOM Depth
 
8
Maximum Child Elements
24
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Hlebo.com 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.0 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://hlebo.com/
173.372
8.285
1.662
Minimizes main-thread work — 0.2 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Other
69.73
Rendering
68.308
Style & Layout
60.725
Script Evaluation
10.3
Parse HTML & CSS
6.368
Script Parsing & Compilation
1.662
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 — 60 requests • 578 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
60
592208
Image
57
577994
Document
1
12779
Other
2
1435
Stylesheet
0
0
Media
0
0
Font
0
0
Script
0
0
Third-party
2
1238
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 2 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
7.3212539765928E-5
7.3212539765928E-5
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 hlebo.com on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

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

Other

Largest Contentful Paint image was lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
97

Accessibility

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

Navigation

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

ARIA

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

Names and labels

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

Tables and lists

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

Internationalization and localization

`<html>` element has a `[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"]`
Hlebo.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

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

Manual Checks

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

Best Practices

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

Audits

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

Audits

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

Audits

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

Audits

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

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://hlebo.com/
Allowed
100

SEO

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

Content Best Practices

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

Crawling and Indexing

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

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
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 hlebo.com. 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 hlebo.com 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) 82
Performance 100
Accessibility 97
Best Practices 83
SEO 99
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://hlebo.com/
Updated: 10th January, 2023

1.33 seconds
First Contentful Paint (FCP)
83%
8%
9%

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

100

Performance

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

Metrics

First Contentful Paint — 1.2 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 1.2 s
The time taken for the page to become fully interactive.
Speed Index — 1.2 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 1.4 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 60 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 1.2 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://hlebo.com/
http/1.1
0
79.539000056684
721
0
301
text/plain
https://hlebo.com/
h2
79.87799984403
358.41999994591
12781
56725
200
text/html
Document
data
376.22700002976
376.35100004263
0
650
200
image/svg+xml
Image
https://hlebo.com/thumbs/55121.jpg
h2
396.37299999595
566.9259999413
12440
11763
200
image/jpeg
Image
https://hlebo.com/thumbs/28075.jpg
h2
396.59999986179
549.25299994648
9390
8708
200
image/jpeg
Image
https://hlebo.com/thumbs/710458.jpg
h2
397.12799992412
655.98399983719
10791
10110
200
image/jpeg
Image
https://hlebo.com/thumbs/235327.jpg
h2
397.62399997562
582.90000003763
11665
10982
200
image/jpeg
Image
https://hlebo.com/thumbs/1236389.jpg
h2
412.54900000058
692.69799999893
15468
14793
200
image/jpeg
Image
https://hlebo.com/thumbs/1049661.jpg
h2
412.87899995223
574.70300002024
8500
7818
200
image/jpeg
Image
https://hlebo.com/thumbs/71271.jpg
h2
413.06499997154
583.25899997726
7903
7219
200
image/jpeg
Image
https://hlebo.com/thumbs/78636.jpg
h2
413.94999995828
592.4080000259
11619
10934
200
image/jpeg
Image
https://hlebo.com/thumbs/25422.jpg
h2
414.06399989501
667.66999987885
16534
15857
200
image/jpeg
Image
https://hlebo.com/thumbs/34871.jpg
h2
414.23200001009
468.97899988107
10632
9934
200
image/jpeg
Image
https://hlebo.com/thumbs/1011145.jpg
h2
420.77199998312
495.79699989408
10960
10262
200
image/jpeg
Image
https://hlebo.com/thumbs/845762.jpg
h2
421.12399986945
482.61299985461
8500
7811
200
image/jpeg
Image
https://hlebo.com/thumbs/803704.jpg
h2
421.22099990956
576.26800006256
10640
9952
200
image/jpeg
Image
https://counter.yadro.ru/hit?r;s360*640*24;uhttps%3A//hlebo.com/;hXXX%20Videos%21%20Porn%20Videos%21%203GP%20MP4%20Mobile%20Sex%20XXX%20Porno%20Videos%21;0.8490907568505313
http/1.1
429.72299992107
1426.501999842
709
0
302
text/html
https://counter.yadro.ru/hit?q;r;s360*640*24;uhttps%3A//hlebo.com/;hXXX%20Videos%21%20Porn%20Videos%21%203GP%20MP4%20Mobile%20Sex%20XXX%20Porno%20Videos%21;0.8490907568505313
http/1.1
1426.9299998414
2049.7210000176
528
43
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
362.583
8.775
374.654
24.83
402.134
12.007
415.432
6.471
421.93
13.774
435.807
37.482
585.721
6.743
607.39
10.067
658.793
5.271
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Hlebo.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Hlebo.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Hlebo.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Hlebo.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Hlebo.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Hlebo.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 280 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://hlebo.com/
279.526
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Hlebo.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://hlebo.com/
630
https://hlebo.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Hlebo.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://hlebo.com/thumbs/55121.jpg
0
Avoids enormous network payloads — Total size was 156 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://hlebo.com/thumbs/25422.jpg
16534
https://hlebo.com/thumbs/1236389.jpg
15468
https://hlebo.com/
12781
https://hlebo.com/thumbs/55121.jpg
12440
https://hlebo.com/thumbs/235327.jpg
11665
https://hlebo.com/thumbs/78636.jpg
11619
https://hlebo.com/thumbs/1011145.jpg
10960
https://hlebo.com/thumbs/710458.jpg
10791
https://hlebo.com/thumbs/803704.jpg
10640
https://hlebo.com/thumbs/34871.jpg
10632
Uses efficient cache policy on static assets — 0 resources found
Hlebo.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
Avoids an excessive DOM size — 778 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
778
Maximum DOM Depth
 
8
Maximum Child Elements
24
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Hlebo.com 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.0 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://hlebo.com/
577.52
34.24
6.912
Unattributable
102.708
6.372
0
Minimizes main-thread work — 0.7 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)
Style & Layout
263.348
Other
179.184
Rendering
162.156
Script Evaluation
40.612
Parse HTML & CSS
28.016
Script Parsing & Compilation
6.912
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 — 17 requests • 156 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
17
159781
Image
14
145570
Document
1
12781
Other
2
1430
Stylesheet
0
0
Media
0
0
Font
0
0
Script
0
0
Third-party
2
1237
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 3 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://hlebo.com/
642
75
https://hlebo.com/
1184
55
https://hlebo.com/
1110
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 hlebo.com on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
First Contentful Paint (3G) — 2210 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Budgets

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

Other

Largest Contentful Paint image was lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
97

Accessibility

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

Navigation

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

ARIA

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

Names and labels

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

Tables and lists

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

Internationalization and localization

`<html>` element has a `[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"]`
Hlebo.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

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

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 hlebo.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

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

Audits

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

Audits

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

Audits

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

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://hlebo.com/
Allowed

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://hlebo.com/thumbs/28075.jpg
326 x 183
320 x 180
652 x 366
https://hlebo.com/thumbs/55121.jpg
326 x 183
320 x 180
652 x 366
99

SEO

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

Content Best Practices

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

Crawling and Indexing

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

Mobile Friendly

Tap targets are not sized appropriately — 95% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.
Tap Target Size Overlapping Target
39x24
Cum
63x24
Jav
38x24

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 hlebo.com. 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 hlebo.com 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.21.77.126
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: Yes
Name: DATA REDACTED
Organization: DATA REDACTED
Country: US
City: DATA REDACTED
State: OH
Post Code: DATA REDACTED
Email:
Phone: DATA REDACTED
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Cloudflare, Inc. 104.16.123.96
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: 14th June, 2022
Valid To: 14th 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: 15165680143231116088367589223363961605
Serial Number (Hex): 0B68CDC2A84533FDC373FDEBC3BEE305
Valid From: 14th June, 2024
Valid To: 14th 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 14 01:24:12.163 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:1C:39:1C:43:C1:EE:F8:D2:1A:13:BD:97:
5B:E4:EE:A9:3B:06:B5:F1:ED:11:55:03:61:14:E7:B7:
DF:AD:55:65:02:20:42:93:2C:A2:23:A5:A7:D5:89:6D:
C9:8D:75:65:9C:0C:B0:51:0C:6C:57:9F:2F:5E:07:1C:
C5:63:1F:9E:51:C3
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 14 01:24:12.185 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:66:7E:A0:1A:2E:39:C8:8F:37:98:33:07:
B1:3F:B9:45:D2:A7:4E:2C:92:68:1C:FC:68:9E:FC:9E:
C3:9D:E9:E6:02:20:39:BA:F6:B4:5C:4B:A4:D1:16:A5:
43:C2:D9:DC:54:B9:08:50:ED:62:98:EA:E2:02:95:59:
62:8C:EC:6B:FD:2C
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : B7:3E:FB:24:DF:9C:4D:BA:75:F2:39:C5:BA:58:F4:6C:
5D:FC:42:CF:7A:9F:35:C4:9E:1D:09:81:25:ED:B4:99
Timestamp : Jun 14 01:24:12.183 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:CB:6B:67:06:09:20:B3:66:6E:8A:EE:
CE:06:5F:35:30:45:CC:66:54:5E:4D:04:47:6C:15:64:
91:A8:A5:CF:EA:02:21:00:F1:79:B1:FA:49:77:18:EF:
C4:28:CE:1C:7D:DC:23:34:6E:2D:23:B1:94:92:D3:01:
85:CF:03:FF:FF:33:08:DA
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.hlebo.com
DNS:hlebo.com
DNS:sni.cloudflaressl.com
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 7th March, 2023
Content-Type: text/html; charset=utf-8
Cache-Control: max-age=300
Server: cloudflare
Connection: keep-alive
CF-Cache-Status: DYNAMIC
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=aS3jlT1WdcQTVqjGgJAzIHtvWzZQq1GV9ltW5wwZXKVNYjY0FevwWd%2BjGgIW441eknvTVpqY0AGrfoSH%2B8y8teXtJb2sQHeLNiVR%2BEoYJjjALMEMfFLMFbitYZg%3D"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
CF-RAY: 7a43a7a57df443fe-EWR
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

Whois Lookup

Created: 5th October, 2016
Changed: 7th March, 2022
Expires: 5th October, 2023
Registrar: Cloudflare, Inc.
Status:
Nameservers: jim.ns.cloudflare.com
zoe.ns.cloudflare.com
Owner Name: DATA REDACTED
Owner Organization: DATA REDACTED
Owner Street: DATA REDACTED
Owner Post Code: DATA REDACTED
Owner City: DATA REDACTED
Owner State: Moscow
Owner Country: RU
Owner Phone: DATA REDACTED
Owner Email: https://domaincontact.cloudflareregistrar.com/hlebo.com
Admin Name: DATA REDACTED
Admin Organization: DATA REDACTED
Admin Street: DATA REDACTED
Admin Post Code: DATA REDACTED
Admin City: DATA REDACTED
Admin State: DATA REDACTED
Admin Country: DATA REDACTED
Admin Phone: DATA REDACTED
Admin Email: https://domaincontact.cloudflareregistrar.com/hlebo.com
Tech Name: DATA REDACTED
Tech Organization: DATA REDACTED
Tech Street: DATA REDACTED
Tech Post Code: DATA REDACTED
Tech City: DATA REDACTED
Tech State: DATA REDACTED
Tech Country: DATA REDACTED
Tech Phone: DATA REDACTED
Tech Email: https://domaincontact.cloudflareregistrar.com/hlebo.com
Billing Name: DATA REDACTED
Billing Organization: DATA REDACTED
Billing Street: DATA REDACTED
Billing Post Code: DATA REDACTED
Billing City: DATA REDACTED
Billing State: DATA REDACTED
Billing Country: DATA REDACTED
Billing Phone: DATA REDACTED
Billing Fax: DATA REDACTED
Billing Email: https://domaincontact.cloudflareregistrar.com/hlebo.com
Full Whois: Domain Name: HLEBO.COM
Registry Domain ID: 2063841544_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.cloudflare.com
Registrar URL: https://www.cloudflare.com
Updated Date: 2022-03-07T05:22:41Z
Creation Date: 2016-10-05T17:26:46Z
Registrar Registration Expiration Date: 2023-10-05T17:26:46Z
Registrar: Cloudflare, Inc.
Registrar IANA ID: 1910
Domain Status: clienttransferprohibited https://icann.org/epp#clienttransferprohibited
Registry Registrant ID:
Registrant Name: DATA REDACTED
Registrant Organization: DATA REDACTED
Registrant Street: DATA REDACTED
Registrant City: DATA REDACTED
Registrant State/Province: Moscow
Registrant Postal Code: DATA REDACTED
Registrant Country: RU
Registrant Phone: DATA REDACTED
Registrant Phone Ext: DATA REDACTED
Registrant Fax: DATA REDACTED
Registrant Fax Ext: DATA REDACTED
Registrant Email: https://domaincontact.cloudflareregistrar.com/hlebo.com
Registry Admin ID:
Admin Name: DATA REDACTED
Admin Organization: DATA REDACTED
Admin Street: DATA REDACTED
Admin City: DATA REDACTED
Admin State/Province: DATA REDACTED
Admin Postal Code: DATA REDACTED
Admin Country: DATA REDACTED
Admin Phone: DATA REDACTED
Admin Phone Ext: DATA REDACTED
Admin Fax: DATA REDACTED
Admin Fax Ext: DATA REDACTED
Admin Email: https://domaincontact.cloudflareregistrar.com/hlebo.com
Registry Tech ID:
Tech Name: DATA REDACTED
Tech Organization: DATA REDACTED
Tech Street: DATA REDACTED
Tech City: DATA REDACTED
Tech State/Province: DATA REDACTED
Tech Postal Code: DATA REDACTED
Tech Country: DATA REDACTED
Tech Phone: DATA REDACTED
Tech Phone Ext: DATA REDACTED
Tech Fax: DATA REDACTED
Tech Fax Ext: DATA REDACTED
Tech Email: https://domaincontact.cloudflareregistrar.com/hlebo.com
Registry Billing ID:
Billing Name: DATA REDACTED
Billing Organization: DATA REDACTED
Billing Street: DATA REDACTED
Billing City: DATA REDACTED
Billing State/Province: DATA REDACTED
Billing Postal Code: DATA REDACTED
Billing Country: DATA REDACTED
Billing Phone: DATA REDACTED
Billing Phone Ext: DATA REDACTED
Billing Fax: DATA REDACTED
Billing Fax Ext: DATA REDACTED
Billing Email: https://domaincontact.cloudflareregistrar.com/hlebo.com
Name Server: jim.ns.cloudflare.com
Name Server: zoe.ns.cloudflare.com
DNSSEC: unsigned
Registrar Abuse Contact Email: registrar-abuse@cloudflare.com
Registrar Abuse Contact Phone: +1.4153197517
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2023-03-07T14:51:10Z <<<

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

Cloudflare provides more than 13 million domains with the tools to give their global users a faster, more secure, and more reliable internet experience.

NOTICE:

Data in the Cloudflare Registrar WHOIS database is provided to you by Cloudflare
under the terms and conditions at https://www.cloudflare.com/domain-registration-agreement/

By submitting this query, you agree to abide by these terms.

Register your domain name at https://www.cloudflare.com/registrar/

Nameservers

Name IP Address
jim.ns.cloudflare.com 173.245.59.125
zoe.ns.cloudflare.com 173.245.58.149
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
$171,526 USD 3/5

Sites hosted on the same IP address