1v1lol.com

1v1lol.com is SSL secured

Free website and domain report on 1v1lol.com

Last Updated: 15th November, 2024
Overview

Snoop Summary for 1v1lol.com

This is a free and comprehensive report about 1v1lol.com. Our records indicate that 1v1lol.com is privately registered by Dynadot Privacy Service. If 1v1lol.com was to be sold it would possibly be worth $574 USD (based on the daily revenue potential of the website over a 24 month period). 1v1lol.com receives an estimated 271 unique visitors every day - a decent amount of traffic! This report was last updated 15th November, 2024.

About 1v1lol.com

Site Preview: 1v1lol.com 1v1lol.com
Title:
Description:
Keywords and Tags: parked domain, pups
Related Terms: 1v1lol
Fav Icon:
Age: Over 4 years old
Domain Created: 12th December, 2019
Domain Updated: 8th July, 2021
Domain Expires: 12th December, 2030
Review

Snoop Score

1/5

Valuation

$574 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 5,152,466
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: 271
Monthly Visitors: 8,248
Yearly Visitors: 98,915
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $24 USD
Yearly Revenue: $282 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: 1v1lol.com 10
Domain Name: 1v1lol 6
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 77
Performance 95
Accessibility 78
Best Practices 92
SEO 100
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
95

Performance

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

Metrics

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

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://1v1lol.com/
http/1.1
0
161.24600009061
1505
839
200
text/html
Document
http://1v1lol.com/js/parking.2.102.0.js
http/1.1
168.32399996929
259.80299990624
22612
69011
200
application/javascript
Script
http://1v1lol.com/_fd
http/1.1
274.29699990898
462.81799999997
2570
3925
200
text/html
Fetch
https://www.google.com/adsense/domains/caf.js
h2
275.63400007784
289.62699999101
54651
147826
200
text/javascript
Script
http://1v1lol.com/px.gif?ch=1&rn=10.29941227471633
http/1.1
277.49800006859
420.84000003524
421
42
200
image/gif
Image
http://1v1lol.com/px.gif?ch=2&rn=10.29941227471633
http/1.1
277.854999993
454.21399991028
421
42
200
image/gif
Image
https://partner.googleadservices.com/gampad/cookie.js?domain=1v1lol.com&client=dp-bodis30_3ph&product=SAS&callback=__sasCookie
h2
473.98600005545
478.93700003624
881
360
200
text/javascript
Script
https://www.google.com/afs/ads?psid=3872471141&pcsa=false&channel=pid-bodis-gcontrol102%2Cpid-bodis-gcontrol97%2Cpid-bodis-gcontrol317%2Cpid-bodis-gcontrol152%2Cpid-bodis-gcontrol471&client=dp-bodis30_3ph&r=m&hl=en&rpbu=http%3A%2F%2F1v1lol.com%3Fcaf%26&max_radlink_len=60&type=3&uiopt=false&swp=as-drid-2640601439763898&oe=UTF-8&ie=UTF-8&fexp=21404%2C17301113%2C17301114%2C17301115&format=r3&nocache=9761674669396286&num=0&output=afd_ads&domain_name=1v1lol.com&v=3&bsl=8&pac=0&u_his=2&u_tz=-480&dt=1674669396287&u_w=800&u_h=600&biw=1350&bih=940&psw=1334&psh=76&frm=0&cl=502576190&uio=-&cont=rs&jsid=caf&jsv=502576190&rurl=http%3A%2F%2F1v1lol.com%2F&adbw=master-1%3A1334
h2
489.56999997608
577.50599994324
2510
5734
200
text/html
Document
https://www.google.com/adsense/domains/caf.js?pac=0
h2
587.23800000735
605.1570000127
54509
147759
200
text/javascript
Script
https://fonts.googleapis.com/css?family=Michroma&display=swap
h2
627.72099999711
633.69200006127
1087
396
200
text/css
Stylesheet
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%2302198b
h2
644.60300002247
651.09100006521
1072
391
200
image/svg+xml
Image
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
h2
644.94700008072
648.52200006135
1194
444
200
image/svg+xml
Image
https://fonts.gstatic.com/s/michroma/v16/PN_zRfy9qWD8fEagAPg9pTn5_PDb.woff2
h2
665.03200004809
668.98899991065
10819
9892
200
font/woff2
Font
http://www.google-analytics.com/analytics.js
http/1.1
669.43800006993
674.67199987732
20542
50234
200
text/javascript
Script
http://1v1lol.com/_tr
http/1.1
698.12399987131
805.41299981996
565
2
200
text/html
Fetch
https://www.google-analytics.com/j/collect?v=1&_v=j99&a=785429793&t=pageview&_s=1&dl=http%3A%2F%2F1v1lol.com%2F&dp=%2F&ul=en-us&de=UTF-8&dt=1v1lol.com&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAEABAAAAACACI~&jid=1112080311&gjid=1934585407&cid=63359566.1674669397&tid=UA-106537103-1&_gid=1036403741.1674669397&_r=1&_slc=1&z=1010162097
h2
732.48000000603
737.79499996454
492
2
200
text/plain
XHR
https://www.google.com/afs/gen_204?client=dp-bodis30_3ph&output=uds_ads_only&zx=csmhle1s745j&aqid=VG3RY9-FFYnTtOUP7quzoAE&psid=3872471141&pbt=bs&adbx=425&adby=65.8125&adbh=500&adbw=500&adbah=150%2C150%2C184&adbn=master-1&eawp=partner-dp-bodis30_3ph&errv=502576190&csala=10%7C0%7C104%7C34%7C45&lle=0&llm=1000&ifv=1&usr=1
h2
2171.1309999228
2187.2139999177
1160
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-bodis30_3ph&output=uds_ads_only&zx=gpz66bo8y4mj&aqid=VG3RY9-FFYnTtOUP7quzoAE&psid=3872471141&pbt=bv&adbx=425&adby=65.8125&adbh=500&adbw=500&adbah=150%2C150%2C184&adbn=master-1&eawp=partner-dp-bodis30_3ph&errv=502576190&csala=10%7C0%7C104%7C34%7C45&lle=0&llm=1000&ifv=1&usr=1
h2
2672.1059998963
2688.5299999267
682
0
204
text/html
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
166.101
9.075
266.576
12.569
302.269
6.39
466.169
26.543
581.472
6.782
617.809
28.958
668.218
31.454
699.799
6.949
714.361
19.592
13991.943
6.9
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. 1v1lol.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. 1v1lol.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. 1v1lol.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. 1v1lol.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. 1v1lol.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. 1v1lol.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 — Potential savings of 63 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.google.com/adsense/domains/caf.js
54651
33091
https://www.google.com/adsense/domains/caf.js?pac=0
54509
31721
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 160 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://1v1lol.com/
162.235
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. 1v1lol.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. 1v1lol.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 — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
http://1v1lol.com/js/parking.2.102.0.js
144
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 174 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.google.com/adsense/domains/caf.js
54651
https://www.google.com/adsense/domains/caf.js?pac=0
54509
http://1v1lol.com/js/parking.2.102.0.js
22612
http://www.google-analytics.com/analytics.js
20542
https://fonts.gstatic.com/s/michroma/v16/PN_zRfy9qWD8fEagAPg9pTn5_PDb.woff2
10819
http://1v1lol.com/_fd
2570
https://www.google.com/afs/ads?psid=3872471141&pcsa=false&channel=pid-bodis-gcontrol102%2Cpid-bodis-gcontrol97%2Cpid-bodis-gcontrol317%2Cpid-bodis-gcontrol152%2Cpid-bodis-gcontrol471&client=dp-bodis30_3ph&r=m&hl=en&rpbu=http%3A%2F%2F1v1lol.com%3Fcaf%26&max_radlink_len=60&type=3&uiopt=false&swp=as-drid-2640601439763898&oe=UTF-8&ie=UTF-8&fexp=21404%2C17301113%2C17301114%2C17301115&format=r3&nocache=9761674669396286&num=0&output=afd_ads&domain_name=1v1lol.com&v=3&bsl=8&pac=0&u_his=2&u_tz=-480&dt=1674669396287&u_w=800&u_h=600&biw=1350&bih=940&psw=1334&psh=76&frm=0&cl=502576190&uio=-&cont=rs&jsid=caf&jsv=502576190&rurl=http%3A%2F%2F1v1lol.com%2F&adbw=master-1%3A1334
2510
http://1v1lol.com/
1505
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
1194
https://www.google.com/afs/gen_204?client=dp-bodis30_3ph&output=uds_ads_only&zx=csmhle1s745j&aqid=VG3RY9-FFYnTtOUP7quzoAE&psid=3872471141&pbt=bs&adbx=425&adby=65.8125&adbh=500&adbw=500&adbah=150%2C150%2C184&adbn=master-1&eawp=partner-dp-bodis30_3ph&errv=502576190&csala=10%7C0%7C104%7C34%7C45&lle=0&llm=1000&ifv=1&usr=1
1160
Uses efficient cache policy on static assets — 3 resources found
1v1lol.com 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://www.google-analytics.com/analytics.js
7200000
20542
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
82800000
1194
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%2302198b
82800000
1072
Avoids an excessive DOM size — 19 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
19
Maximum DOM Depth
7
Maximum Child Elements
6
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. 1v1lol.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.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.google.com/adsense/domains/caf.js?pac=0
72.817
48.492
2.635
http://1v1lol.com/js/parking.2.102.0.js
67.44
62.094
1.115
Minimizes main-thread work — 0.2 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
140.795
Other
57.038
Style & Layout
15.816
Script Parsing & Compilation
10.117
Parse HTML & CSS
6.353
Rendering
5.541
Garbage Collection
2.206
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 — 18 requests • 174 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
18
177693
Script
5
153195
Font
1
10819
Image
6
4950
Document
2
4015
Other
3
3627
Stylesheet
1
1087
Media
0
0
Third-party
12
149599
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)
113512
0
21034
0
11906
0
881
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 3 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.01587962962963
0.0055926380368098
0.0050073619631902
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 1v1lol.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.

Metrics

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

Audits

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

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of 1v1lol.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.
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 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"]`
1v1lol.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

Names and labels

`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Failing Elements

Internationalization and localization

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

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 1v1lol.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 — 7 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://1v1lol.com/
Allowed
http://1v1lol.com/js/parking.2.102.0.js
Allowed
http://1v1lol.com/_fd
Allowed
http://1v1lol.com/px.gif?ch=1&rn=10.29941227471633
Allowed
http://1v1lol.com/px.gif?ch=2&rn=10.29941227471633
Allowed
http://www.google-analytics.com/analytics.js
Allowed
http://1v1lol.com/_tr
Allowed
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for 1v1lol.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 1v1lol.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 1v1lol.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 1v1lol.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) 76
Performance 74
Accessibility 85
Best Practices 92
SEO 100
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
74

Performance

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

Metrics

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).
Cumulative Layout Shift — 0.033
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

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://1v1lol.com/
http/1.1
0
85.820999927819
1505
839
200
text/html
Document
http://1v1lol.com/js/parking.2.102.0.js
http/1.1
95.856999978423
169.27499999292
22612
69011
200
application/javascript
Script
http://1v1lol.com/_fd
http/1.1
189.17599995621
372.6659999229
2570
3925
200
text/html
Fetch
https://www.google.com/adsense/domains/caf.js
h2
190.37999992725
202.68200000282
54520
147793
200
text/javascript
Script
http://1v1lol.com/px.gif?ch=1&rn=5.563621689040176
http/1.1
192.44799995795
266.08699990902
421
42
200
image/gif
Image
http://1v1lol.com/px.gif?ch=2&rn=5.563621689040176
http/1.1
192.76899995748
279.31699994951
421
42
200
image/gif
Image
https://partner.googleadservices.com/gampad/cookie.js?domain=1v1lol.com&client=dp-bodis30_3ph&product=SAS&callback=__sasCookie
h2
383.39199998882
389.28199990187
882
360
200
text/javascript
Script
https://www.google.com/afs/ads?psid=3872471141&pcsa=false&channel=pid-bodis-gcontrol102%2Cpid-bodis-gcontrol97%2Cpid-bodis-gcontrol317%2Cpid-bodis-gcontrol152%2Cpid-bodis-gcontrol471&client=dp-bodis30_3ph&r=m&hl=en&rpbu=http%3A%2F%2F1v1lol.com%3Fcaf%26&max_radlink_len=60&type=3&uiopt=false&swp=as-drid-2640601439763898&oe=UTF-8&ie=UTF-8&fexp=21404&format=r3&nocache=1231674669444900&num=0&output=afd_ads&domain_name=1v1lol.com&v=3&bsl=8&pac=0&u_his=2&u_tz=-480&dt=1674669444902&u_w=360&u_h=640&biw=360&bih=640&psw=344&psh=76&frm=0&cl=502576190&uio=-&cont=rs&jsid=caf&jsv=502576190&rurl=http%3A%2F%2F1v1lol.com%2F&adbw=master-1%3A344
h2
399.65399994981
492.20699991565
2644
5814
200
text/html
Document
https://www.google.com/adsense/domains/caf.js?pac=0
h2
506.3679999439
525.23799997289
54517
147766
200
text/javascript
Script
https://fonts.googleapis.com/css?family=Michroma&display=swap
h2
552.94899991713
558.97599994205
1087
396
200
text/css
Stylesheet
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%2302198b
h2
574.09199990798
579.28399997763
1188
391
200
image/svg+xml
Image
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
h2
574.3229999207
578.77399993595
1194
444
200
image/svg+xml
Image
https://fonts.gstatic.com/s/michroma/v16/PN_zRfy9qWD8fEagAPg9pTn5_PDb.woff2
h2
595.52999993321
599.81799998786
10818
9892
200
font/woff2
Font
http://www.google-analytics.com/analytics.js
http/1.1
607.55399998743
613.19999990519
20542
50234
200
text/javascript
Script
http://1v1lol.com/_tr
http/1.1
628.22499999311
735.24099995848
550
2
200
text/html
Fetch
https://www.google-analytics.com/j/collect?v=1&_v=j99&a=1488181243&t=pageview&_s=1&dl=http%3A%2F%2F1v1lol.com%2F&dp=%2F&ul=en-us&de=UTF-8&dt=1v1lol.com&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=IEBAAEABAAAAACACI~&jid=2111662130&gjid=203230547&cid=432745512.1674669445&tid=UA-106537103-1&_gid=1018012892.1674669445&_r=1&_slc=1&z=1423890237
h2
666.52799991425
673.85999998078
608
2
200
text/plain
XHR
https://www.google.com/afs/gen_204?client=dp-bodis30_3ph&output=uds_ads_only&zx=37ntydrdef5x&aqid=hG3RY7z-OuWOtOUP26WhoAs&psid=3872471141&pbt=bs&adbx=0&adby=65.8125&adbh=568&adbw=360&adbah=184%2C218%2C150&adbn=master-1&eawp=partner-dp-bodis30_3ph&errv=502576190&csala=10%7C0%7C114%7C39%7C59&lle=0&llm=1000&ifv=1&usr=1
h2
2109.5159999095
2130.960999988
893
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-bodis30_3ph&output=uds_ads_only&zx=u5mucghhpnpr&aqid=hG3RY7z-OuWOtOUP26WhoAs&psid=3872471141&pbt=bv&adbx=0&adby=65.8125&adbh=568&adbw=360&adbah=184%2C218%2C150&adbn=master-1&eawp=partner-dp-bodis30_3ph&errv=502576190&csala=10%7C0%7C114%7C39%7C59&lle=0&llm=1000&ifv=1&usr=1
h2
2610.3230000008
2626.7049999442
531
0
204
text/html
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
90.735
9.736
177.594
16.852
219.061
8.339
376.082
26.937
498.014
9.884
540.276
35.395
576.757
5.065
605.778
24.022
629.976
7.974
643.584
24.66
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. 1v1lol.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. 1v1lol.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. 1v1lol.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. 1v1lol.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. 1v1lol.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. 1v1lol.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
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 90 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://1v1lol.com/
86.807
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. 1v1lol.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. 1v1lol.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 — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
http://1v1lol.com/js/parking.2.102.0.js
144
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 173 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.google.com/adsense/domains/caf.js
54520
https://www.google.com/adsense/domains/caf.js?pac=0
54517
http://1v1lol.com/js/parking.2.102.0.js
22612
http://www.google-analytics.com/analytics.js
20542
https://fonts.gstatic.com/s/michroma/v16/PN_zRfy9qWD8fEagAPg9pTn5_PDb.woff2
10818
https://www.google.com/afs/ads?psid=3872471141&pcsa=false&channel=pid-bodis-gcontrol102%2Cpid-bodis-gcontrol97%2Cpid-bodis-gcontrol317%2Cpid-bodis-gcontrol152%2Cpid-bodis-gcontrol471&client=dp-bodis30_3ph&r=m&hl=en&rpbu=http%3A%2F%2F1v1lol.com%3Fcaf%26&max_radlink_len=60&type=3&uiopt=false&swp=as-drid-2640601439763898&oe=UTF-8&ie=UTF-8&fexp=21404&format=r3&nocache=1231674669444900&num=0&output=afd_ads&domain_name=1v1lol.com&v=3&bsl=8&pac=0&u_his=2&u_tz=-480&dt=1674669444902&u_w=360&u_h=640&biw=360&bih=640&psw=344&psh=76&frm=0&cl=502576190&uio=-&cont=rs&jsid=caf&jsv=502576190&rurl=http%3A%2F%2F1v1lol.com%2F&adbw=master-1%3A344
2644
http://1v1lol.com/_fd
2570
http://1v1lol.com/
1505
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
1194
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%2302198b
1188
Uses efficient cache policy on static assets — 3 resources found
1v1lol.com 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://www.google-analytics.com/analytics.js
7200000
20542
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
82800000
1194
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%2302198b
82800000
1188
Avoids an excessive DOM size — 19 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
19
Maximum DOM Depth
7
Maximum Child Elements
6
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. 1v1lol.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.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)
https://www.google.com/adsense/domains/caf.js?pac=0
265.488
197.108
11.568
http://1v1lol.com/js/parking.2.102.0.js
256.712
241.144
7.08
https://www.google.com/afs/ads?psid=3872471141&pcsa=false&channel=pid-bodis-gcontrol102%2Cpid-bodis-gcontrol97%2Cpid-bodis-gcontrol317%2Cpid-bodis-gcontrol152%2Cpid-bodis-gcontrol471&client=dp-bodis30_3ph&r=m&hl=en&rpbu=http%3A%2F%2F1v1lol.com%3Fcaf%26&max_radlink_len=60&type=3&uiopt=false&swp=as-drid-2640601439763898&oe=UTF-8&ie=UTF-8&fexp=21404&format=r3&nocache=1231674669444900&num=0&output=afd_ads&domain_name=1v1lol.com&v=3&bsl=8&pac=0&u_his=2&u_tz=-480&dt=1674669444902&u_w=360&u_h=640&biw=360&bih=640&psw=344&psh=76&frm=0&cl=502576190&uio=-&cont=rs&jsid=caf&jsv=502576190&rurl=http%3A%2F%2F1v1lol.com%2F&adbw=master-1%3A344
119.292
10.416
7.76
Unattributable
110.812
1.988
0
http://www.google-analytics.com/analytics.js
103.392
94.684
5.06
https://www.google.com/adsense/domains/caf.js
85.016
54.756
11.504
http://1v1lol.com/
77.692
7.452
5.956
Minimizes main-thread work — 1.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
610.84
Other
235.528
Style & Layout
75.424
Script Parsing & Compilation
49.244
Parse HTML & CSS
27.68
Rendering
26.968
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 — 18 requests • 173 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
18
177503
Script
5
153073
Font
1
10818
Image
6
4648
Document
2
4149
Other
3
3728
Stylesheet
1
1087
Media
0
0
Third-party
12
149424
Minimize third-party usage — Third-party code blocked the main thread for 90 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)
113105
51.224
21150
41.34
11905
0
882
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.03349609375
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 — 5 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.google.com/adsense/domains/caf.js?pac=0
3007
142
http://www.google-analytics.com/analytics.js
3187
99
http://1v1lol.com/js/parking.2.102.0.js
2161
96
http://1v1lol.com/js/parking.2.102.0.js
960
67
http://1v1lol.com/js/parking.2.102.0.js
2107
54
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 1v1lol.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.

Metrics

Time to Interactive — 4.0 s
The time taken for the page to become fully interactive.
Speed Index — 4.0 s
The time taken for the page contents to be visibly populated.

Other

Reduce unused JavaScript — Potential savings of 63 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.google.com/adsense/domains/caf.js
54520
33019
https://www.google.com/adsense/domains/caf.js?pac=0
54517
31715

Metrics

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

Audits

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

Other

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

Accessibility

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

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

Names and labels

`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Failing Elements

Internationalization and localization

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

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 1v1lol.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 — 7 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://1v1lol.com/
Allowed
http://1v1lol.com/js/parking.2.102.0.js
Allowed
http://1v1lol.com/_fd
Allowed
http://1v1lol.com/px.gif?ch=1&rn=5.563621689040176
Allowed
http://1v1lol.com/px.gif?ch=2&rn=5.563621689040176
Allowed
http://www.google-analytics.com/analytics.js
Allowed
http://1v1lol.com/_tr
Allowed
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for 1v1lol.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 1v1lol.com on mobile screens.
Document uses legible font sizes — 75.26% 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
.privacy
16.49%
11px
.si133
8.25%
10px
75.26%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

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

Crawling and Indexing

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

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
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 1v1lol.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 1v1lol.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: 199.59.243.227
Continent:
Country:
Region:
City:
Longitude:
Latitude:
Currencies:
Languages:

Web Hosting Provider

Name IP Address
Bodis, LLC
Registration

Domain Registrant

Private Registration: Yes
Name: REDACTED FOR PRIVACY
Organization: Dynadot Privacy Service
Country: US
City: San Mateo
State: California
Post Code: 94401
Email:
Phone: +1.6505854708
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
DYNADOT LLC 104.16.152.132
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Unknown
WOT Rating:
WOT Trustworthiness:
WOT Child Safety:
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: 1v1lol.com
Issued By: E5
Valid From: 29th October, 2024
Valid To: 27th January, 2025
Subject: CN = 1v1lol.com
Hash: eb5c5bd7
Issuer: CN = E5
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x0419505B48F6570158E4BA52E14D6F672E69
Serial Number (Hex): 0419505B48F6570158E4BA52E14D6F672E69
Valid From: 29th October, 2024
Valid To: 27th January, 2024
Signature Algorithm (Short Name): ecdsa-with-SHA384
Signature Algorithm (Long Name): ecdsa-with-SHA384
Authority Key Identifier: keyid:9F:2B:5F:CF:3C:21:4F:9D:04:B7:ED:2B:2C:C4:C6:70:8B:D2:D7:0D
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1

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

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
Timestamp : Oct 29 12:34:05.068 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:30:37:A2:49:A4:6C:4F:50:6F:1E:C3:CE:
53:B7:32:F3:73:22:38:AC:EF:55:03:BA:20:C2:71:1B:
73:D7:9F:FC:02:20:2F:A4:07:7A:28:D8:8A:47:6A:00:
84:CA:06:D3:F5:50:98:D5:13:4A:D6:FB:27:1A:B2:53:
5F:FA:C2:7B:FB:93
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : E0:92:B3:FC:0C:1D:C8:E7:68:36:1F:DE:61:B9:96:4D:
0A:52:78:19:8A:72:D6:72:C4:B0:4D:A5:6D:6F:54:04
Timestamp : Oct 29 12:34:05.110 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:65:6D:B0:2A:37:F3:55:43:1D:A4:FB:D9:
36:7B:EB:BD:10:8F:EA:C1:F6:57:12:C7:AE:54:24:53:
33:7F:17:58:02:20:16:0C:D7:33:4F:D7:80:F0:CF:81:
1C:38:9D:BF:C0:E7:88:13:9D:D0:14:BF:84:A3:CF:D6:
75:35:F8:E2:BE:E7
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:1v1lol.com
DNS:*.1v1lol.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
1v1lol.com. 199.59.243.227 IN 10800

NS Records

Host Nameserver Class TTL
1v1lol.com. ns2.bodis.com. IN 600
1v1lol.com. ns1.bodis.com. IN 600

SOA Records

Domain Name Primary NS Responsible Email TTL
1v1lol.com. ns1.bodis.com. dnsadmin.bodis.com. 10800

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
date: 15th November, 2024
content-type: text/html; charset=utf-8
cache-control: no-store, max-age=0
content-length: 1078
x-request-id: f49b87c9-a863-4e60-9680-f48d5cbda6d9
accept-ch: sec-ch-prefers-color-scheme
critical-ch: sec-ch-prefers-color-scheme
vary: sec-ch-prefers-color-scheme
x-adblock-key: MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBANDrp2lz7AOmADaN8tA50LsWcjLFyQFcb/P2Txc58oYOeILb3vBw7J6f4pamkAQVSQuqYsKx3YzdUHCvbVZvFUsCAwEAAQ==_kmjYDy311SUE3jt7MzDEBV/oVajHQb7XNT2NJ504u6SfPBuHcuhpC8+mFkS6tNG7eCunfSv+m8kGW6LMMLrl8A==
set-cookie: *

Whois Lookup

Created: 12th December, 2019
Changed: 8th July, 2021
Expires: 12th December, 2030
Registrar: DYNADOT LLC
Status: clientTransferProhibited
Nameservers: ns1.bodis.com
ns2.bodis.com
Owner Name: REDACTED FOR PRIVACY
Owner Organization: Super Privacy Service LTD c/o Dynadot
Owner Street: PO Box 701
Owner Post Code: 94401
Owner City: San Mateo
Owner State: California
Owner Country: US
Owner Phone: +1.6505854708
Owner Email: https://www.dynadot.com/domain/contact-request?domain=1v1lol.com
Admin Name: REDACTED FOR PRIVACY
Admin Organization: Super Privacy Service LTD c/o Dynadot
Admin Street: PO Box 701
Admin Post Code: 94401
Admin City: San Mateo
Admin State: California
Admin Country: US
Admin Phone: +1.6505854708
Admin Email: https://www.dynadot.com/domain/contact-request?domain=1v1lol.com
Tech Name: REDACTED FOR PRIVACY
Tech Organization: Super Privacy Service LTD c/o Dynadot
Tech Street: PO Box 701
Tech Post Code: 94401
Tech City: San Mateo
Tech State: California
Tech Country: US
Tech Phone: +1.6505854708
Tech Email: https://www.dynadot.com/domain/contact-request?domain=1v1lol.com
Full Whois: Domain Name: 1V1LOL.COM
Registry Domain ID: 2466213831_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.dynadot.com
Registrar URL: http://www.dynadot.com
Updated Date: 2021-07-08T10:39:38.0Z
Creation Date: 2019-12-12T07:56:04.0Z
Registrar Registration Expiration Date: 2030-12-12T07:56:04.0Z
Registrar: DYNADOT LLC
Registrar IANA ID: 472
Registrar Abuse Contact Email: abuse@dynadot.com
Registrar Abuse Contact Phone: +1.6502620100
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID:
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: Super Privacy Service LTD c/o Dynadot
Registrant Street: PO Box 701
Registrant Street:
Registrant City: San Mateo
Registrant State/Province: California
Registrant Postal Code: 94401
Registrant Country: US
Registrant Phone: +1.6505854708
Registrant Email: https://www.dynadot.com/domain/contact-request?domain=1v1lol.com
Registry Admin ID:
Admin Name: REDACTED FOR PRIVACY
Admin Organization: Super Privacy Service LTD c/o Dynadot
Admin Street: PO Box 701
Admin Street:
Admin City: San Mateo
Admin State/Province: California
Admin Postal Code: 94401
Admin Country: US
Admin Phone: +1.6505854708
Admin Email: https://www.dynadot.com/domain/contact-request?domain=1v1lol.com
Registry Tech ID:
Tech Name: REDACTED FOR PRIVACY
Tech Organization: Super Privacy Service LTD c/o Dynadot
Tech Street: PO Box 701
Tech Street:
Tech City: San Mateo
Tech State/Province: California
Tech Postal Code: 94401
Tech Country: US
Tech Phone: +1.6505854708
Tech Email: https://www.dynadot.com/domain/contact-request?domain=1v1lol.com
Name Server: ns1.bodis.com
Name Server: ns2.bodis.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2021-07-08 03:39:38 -0700 <<<

Nameservers

Name IP Address
ns1.bodis.com 199.59.243.110
ns2.bodis.com 34.48.46.38
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
$1,256 USD 1/5
$418 USD 1/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
$464 USD 1/5
$905 USD 2/5
0/5
$1,851 USD 2/5