155chan.net

155chan.net is SSL secured

Free website and domain report on 155chan.net

Last Updated: 10th January, 2023 Update Now
Overview

Snoop Summary for 155chan.net

This is a free and comprehensive report about 155chan.net. The domain 155chan.net is currently hosted on a server located in Richardson, Texas in United States with the IP address 45.33.18.44, where USD is the local currency and the local language is English. Our records indicate that 155chan.net is privately registered by Privacy Protect, LLC (PrivacyProtect.org). If 155chan.net was to be sold it would possibly be worth $443 USD (based on the daily revenue potential of the website over a 24 month period). 155chan.net receives an estimated 208 unique visitors every day - a decent amount of traffic! This report was last updated 10th January, 2023.

About 155chan.net

Site Preview: 155chan.net 155chan.net
Title:
Description:
Keywords and Tags: parked domain
Related Terms: 155chan
Fav Icon:
Age: Over 10 years old
Domain Created: 22nd October, 2013
Domain Updated: 14th November, 2022
Domain Expires: 22nd October, 2023
Review

Snoop Score

1/5

Valuation

$443 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 6,290,157
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 1
Moz Page Authority: 15

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 208
Monthly Visitors: 6,331
Yearly Visitors: 75,920
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $18 USD
Yearly Revenue: $216 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: 155chan.net 11
Domain Name: 155chan 7
Extension (TLD): net 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 73
Performance 99
Accessibility 70
Best Practices 83
SEO 90
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
99

Performance

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

Metrics

First Contentful Paint — 0.7 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.7 s
The time taken for the page to become fully interactive.
Speed Index — 0.7 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 0.9 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 — 50 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.7 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://155chan.net/
http/1.1
0
511.98599999771
2192
1885
200
text/html
Document
http://155chan.net/px.js?ch=1
http/1.1
521.94400015287
702.00800010934
1091
346
200
application/javascript
Script
http://155chan.net/px.js?ch=2
http/1.1
522.30800013058
796.34600016288
1091
346
200
application/javascript
Script
http://ww3.155chan.net/
http/1.1
803.59500017948
1231.8310001865
7870
22955
200
text/html
Document
http://www.google.com/adsense/domains/caf.js
http/1.1
1240.5710001476
1254.416000098
54651
147834
200
text/javascript
Script
http://img.sedoparking.com/templates/bg/arrows.png
http/1.1
1252.6450001169
1268.8280001748
13196
12642
200
image/png
Image
https://partner.googleadservices.com/gampad/cookie.js?domain=ww3.155chan.net&client=dp-sedo80_3ph&product=SAS&callback=__sasCookie
h2
1296.1810000706
1302.3200000171
820
188
200
text/javascript
Script
https://www.google.com/afs/ads/i/iframe.html
h2
1310.1510000415
1315.9630000591
1880
1560
200
text/html
Document
https://www.google.com/afs/ads?adsafe=low&adtest=off&psid=9330244380&channel=exp-0051%2Cauxa-control-1%2C4234817&client=dp-sedo80_3ph&r=m&hl=en&type=3&uiopt=false&swp=as-drid-2339657850453450&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300953%2C17300956%2C17301063%2C17301066%2C17301094%2C17301097&format=r3%7Cs&nocache=511664731182384&num=0&output=afd_ads&domain_name=ww3.155chan.net&v=3&bsl=8&pac=0&u_his=2&u_tz=-420&dt=1664731182392&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=999&frm=0&uio=--&cont=rb-default&jsid=caf&jsv=476880816&rurl=http%3A%2F%2Fww3.155chan.net%2F&referer=http%3A%2F%2F155chan.net%2F&adbw=slave-1-1%3A300%2Cmaster-1%3A490
h2
1315.6980001368
1405.3090000525
2393
5741
200
text/html
Document
http://ww3.155chan.net/search/tsc.php?200=MzA3MzEzNjMz&21=NjcuMjA1LjEzNy4xMjc=&681=MTY2NDczMTE4MjM3YjM4MWNjNTdmNDQxNTYwM2Q5NzM2MjdjNmE3NGFh&crc=975dacd5bd2f3405e6ea323630efb32224271410&cv=1
http/1.1
1320.8830000367
1584.1520000249
200
0
200
text/html
XHR
https://www.google.com/adsense/domains/caf.js?pac=0
h2
1420.5500001553
1436.4120000973
54702
147827
200
text/javascript
Script
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
h2
1494.6050001308
1502.3910000455
1188
391
200
image/svg+xml
Image
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
h2
1494.8770001065
1507.666000165
1090
200
200
image/svg+xml
Image
https://www.google.com/afs/gen_204?client=dp-sedo80_3ph&output=uds_ads_only&zx=u3r7614grxvb&aqid=Lsg5Y8vSG5mYmgSAnZto&psid=9330244380&pbt=bs&adbx=430&adby=134.625&adbh=539&adbw=490&adbah=174%2C174%2C174&adbn=master-1&eawp=partner-dp-sedo80_3ph&errv=476880816&csala=15%7C0%7C110%7C38%7C68&lle=0&llm=1000&ifv=1&usr=1
h2
3030.9600001201
3055.588999996
713
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-sedo80_3ph&output=uds_ads_only&zx=tnjlk1xkjfgr&aqid=Lsg5Y8vSG5mYmgSAnZto&pbt=bs&adbx=525&adby=807.625&adbh=16&adbw=300&adbn=slave-1-1&eawp=partner-dp-sedo80_3ph&errv=476880816&csala=8%7C0%7C117%7C38%7C69&lle=0&llm=1000&ifv=1&usr=1
h2
3031.2950001098
3050.5340001546
713
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-sedo80_3ph&output=uds_ads_only&zx=qx1i5mw45plb&aqid=Lsg5Y8vSG5mYmgSAnZto&psid=9330244380&pbt=bv&adbx=430&adby=134.625&adbh=539&adbw=490&adbah=174%2C174%2C174&adbn=master-1&eawp=partner-dp-sedo80_3ph&errv=476880816&csala=15%7C0%7C110%7C38%7C68&lle=0&llm=1000&ifv=1&usr=1
h2
3531.7160000559
3551.9640001003
351
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-sedo80_3ph&output=uds_ads_only&zx=gk95lqfnl4oq&aqid=Lsg5Y8vSG5mYmgSAnZto&pbt=bv&adbx=525&adby=807.625&adbh=16&adbw=300&adbn=slave-1-1&eawp=partner-dp-sedo80_3ph&errv=476880816&csala=8%7C0%7C117%7C38%7C69&lle=0&llm=1000&ifv=1&usr=1
h2
3532.3250000365
3552.4730000179
351
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)
-283.189
9.979
435.429
11.312
450.486
11.379
475.523
8.494
484.057
32.956
522.154
10.705
609.344
8.41
650.586
44.666
696.668
8.282
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. 155chan.net 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. 155chan.net should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. 155chan.net should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. 155chan.net should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. 155chan.net should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. 155chan.net 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 59 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://www.google.com/adsense/domains/caf.js
54651
32926
https://www.google.com/adsense/domains/caf.js?pac=0
54702
27724
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 430 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
http://ww3.155chan.net/
429.228
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. 155chan.net should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://155chan.net/
190
http://ww3.155chan.net/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. 155chan.net 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.
Avoids enormous network payloads — Total size was 141 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?pac=0
54702
http://www.google.com/adsense/domains/caf.js
54651
http://img.sedoparking.com/templates/bg/arrows.png
13196
http://ww3.155chan.net/
7870
https://www.google.com/afs/ads?adsafe=low&adtest=off&psid=9330244380&channel=exp-0051%2Cauxa-control-1%2C4234817&client=dp-sedo80_3ph&r=m&hl=en&type=3&uiopt=false&swp=as-drid-2339657850453450&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300953%2C17300956%2C17301063%2C17301066%2C17301094%2C17301097&format=r3%7Cs&nocache=511664731182384&num=0&output=afd_ads&domain_name=ww3.155chan.net&v=3&bsl=8&pac=0&u_his=2&u_tz=-420&dt=1664731182392&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=999&frm=0&uio=--&cont=rb-default&jsid=caf&jsv=476880816&rurl=http%3A%2F%2Fww3.155chan.net%2F&referer=http%3A%2F%2F155chan.net%2F&adbw=slave-1-1%3A300%2Cmaster-1%3A490
2393
http://155chan.net/
2192
https://www.google.com/afs/ads/i/iframe.html
1880
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
1188
http://155chan.net/px.js?ch=1
1091
http://155chan.net/px.js?ch=2
1091
Uses efficient cache policy on static assets — 5 resources found
155chan.net 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://155chan.net/px.js?ch=1
0
1091
http://155chan.net/px.js?ch=2
0
1091
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
82800000
1188
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
82800000
1090
http://img.sedoparking.com/templates/bg/arrows.png
604800000
13196
Avoids an excessive DOM size — 32 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
32
Maximum DOM Depth
6
Maximum Child Elements
8
Avoid chaining critical requests
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. 155chan.net should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
http://ww3.155chan.net/
79.053
35.496
3.856
https://www.google.com/adsense/domains/caf.js?pac=0
63.16
43.877
2.21
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
106.353
Other
64.05
Style & Layout
21.34
Parse HTML & CSS
14.057
Script Parsing & Compilation
13.726
Rendering
9.775
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 • 141 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
144492
Script
5
112355
Image
7
17602
Document
4
14335
Other
1
200
Stylesheet
0
0
Media
0
0
Font
0
0
Third-party
12
132048
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)
115754
0
820
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
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
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 155chan.net 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

Preload Largest Contentful Paint image — Potential savings of 150 ms
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
http://img.sedoparking.com/templates/bg/arrows.png
150
70

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of 155chan.net. 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 `[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.

Audio and video

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

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
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.
83

Best Practices

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

Audits

Does not use HTTPS — 8 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://155chan.net/
Allowed
http://155chan.net/px.js?ch=1
Allowed
http://155chan.net/px.js?ch=2
Allowed
http://ww3.155chan.net/
Allowed
http://www.google.com/adsense/domains/caf.js
Allowed
http://img.sedoparking.com/templates/bg/arrows.png
Allowed
http://ww3.155chan.net/search/tsc.php?200=MzA3MzEzNjMz&21=NjcuMjA1LjEzNy4xMjc=&681=MTY2NDczMTE4MjM3YjM4MWNjNTdmNDQxNTYwM2Q5NzM2MjdjNmE3NGFh&crc=975dacd5bd2f3405e6ea323630efb32224271410&cv=1
Allowed
http://ww3.155chan.net/caf/?ses=Y3JlPTE2NjQ3MzExODImdGNpZD13dzMuMTU1Y2hhbi5uZXQ2MzM5YzgyZTM5ZGJkMS45MTg1Njg0MyZ0YXNrPXNlYXJjaCZkb21haW49MTU1Y2hhbi5uZXQmYV9pZD0zJnNlc3Npb249NmctQmhVeVEyV1BXbTF1b2hrQmM=
Allowed with warning

Audits

Issues were logged in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.
Issue type
Mixed content
90

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for 155chan.net. 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 155chan.net 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.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Crawling and Indexing

Page is 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.
Blocking Directive Source

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 155chan.net. 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 155chan.net on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 69
Performance 65
Accessibility 85
Best Practices 92
SEO 75
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
65

Performance

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

Metrics

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

Other

Properly size images
Images can slow down the page's load time. 155chan.net should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. 155chan.net should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. 155chan.net should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. 155chan.net should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. 155chan.net 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 140 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
http://www6.155chan.net/?template=ARROW_3&tdfs=1&s_token=1664731200.0336410000&uuid=1664731200.0336410000&term=Free%20Movie%20Streaming&term=Live%20Person%20Chat%20System&term=Elite%20Dating%20Services&searchbox=0&showDomain=0&backfill=0
144.427
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. 155chan.net 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 21 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://img1.wsimg.com/parking-lander/static/js/2.5940ae1c.chunk.js
21054
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 316 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://img1.wsimg.com/parking-lander/static/js/2.5940ae1c.chunk.js
136156
https://img1.wsimg.com/parking-lander/static/js/main.4e219663.chunk.js
58816
https://www.google.com/adsense/domains/caf.js
54853
https://www.google.com/adsense/domains/caf.js?pac=2
54847
http://www6.155chan.net/?template=ARROW_3&tdfs=1&s_token=1664731200.0336410000&uuid=1664731200.0336410000&term=Free%20Movie%20Streaming&term=Live%20Person%20Chat%20System&term=Elite%20Dating%20Services&searchbox=0&showDomain=0&backfill=0
3278
https://www.google.com/afs/ads?adsafe=low&adtest=off&psid=3767353295&pcsa=false&channel=08231&domain_name=155chan.net&client=dp-namemedia08_3ph&r=m&terms=Free%20Movie%20Streaming%2CLive%20Person%20Chat%20System%2CElite%20Dating%20Services&type=3&swp=as-drid-2235535430585190&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002%2C17300953%2C17300956%2C17301068%2C17301071%2C17301094%2C17301097&format=r3&nocache=5051664731200968&num=0&output=afd_ads&v=3&bsl=8&pac=2&u_his=2&u_tz=-420&dt=1664731200970&u_w=360&u_h=640&biw=360&bih=640&psw=360&psh=245&frm=0&uio=-&cont=relatedLinks&jsid=caf&jsv=476880816&rurl=http%3A%2F%2Fwww6.155chan.net%2F%3Ftemplate%3DARROW_3%26tdfs%3D1%26s_token%3D1664731200.0336410000%26uuid%3D1664731200.0336410000%26term%3DFree%2520Movie%2520Streaming%26term%3DLive%2520Person%2520Chat%2520System%26term%3DElite%2520Dating%2520Services%26searchbox%3D0%26showDomain%3D0%26backfill%3D0&referer=http%3A%2F%2F155chan.net%2F&adbw=master-1%3A360
2473
http://155chan.net/
2191
https://api.aws.parking.godaddy.com/v1/domains/domain?domain=www6.155chan.net&portfolioId=
1574
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
1188
http://155chan.net/px.js?ch=2
1091
Uses efficient cache policy on static assets — 4 resources found
155chan.net 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://155chan.net/px.js?ch=2
0
1091
http://155chan.net/px.js?ch=1
0
628
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
82800000
1188
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
82800000
1090
Avoids an excessive DOM size — 24 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
24
Maximum DOM Depth
8
Maximum Child Elements
5
Avoid chaining critical requests
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. 155chan.net 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 — 1.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://img1.wsimg.com/parking-lander/static/js/main.4e219663.chunk.js
411.06
392.016
15.92
Unattributable
266.108
98.232
1.072
https://www.google.com/adsense/domains/caf.js?pac=2
224.248
170.88
10.928
http://www6.155chan.net/?template=ARROW_3&tdfs=1&s_token=1664731200.0336410000&uuid=1664731200.0336410000&term=Free%20Movie%20Streaming&term=Live%20Person%20Chat%20System&term=Elite%20Dating%20Services&searchbox=0&showDomain=0&backfill=0
211.86
22.752
20.532
https://img1.wsimg.com/parking-lander/static/js/2.5940ae1c.chunk.js
152.208
101.86
25.96
https://www.google.com/adsense/domains/caf.js
139.068
122.448
9.92
https://www.google.com/afs/ads?adsafe=low&adtest=off&psid=3767353295&pcsa=false&channel=08231&domain_name=155chan.net&client=dp-namemedia08_3ph&r=m&terms=Free%20Movie%20Streaming%2CLive%20Person%20Chat%20System%2CElite%20Dating%20Services&type=3&swp=as-drid-2235535430585190&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002%2C17300953%2C17300956%2C17301068%2C17301071%2C17301094%2C17301097&format=r3&nocache=5051664731200968&num=0&output=afd_ads&v=3&bsl=8&pac=2&u_his=2&u_tz=-420&dt=1664731200970&u_w=360&u_h=640&biw=360&bih=640&psw=360&psh=245&frm=0&uio=-&cont=relatedLinks&jsid=caf&jsv=476880816&rurl=http%3A%2F%2Fwww6.155chan.net%2F%3Ftemplate%3DARROW_3%26tdfs%3D1%26s_token%3D1664731200.0336410000%26uuid%3D1664731200.0336410000%26term%3DFree%2520Movie%2520Streaming%26term%3DLive%2520Person%2520Chat%2520System%26term%3DElite%2520Dating%2520Services%26searchbox%3D0%26showDomain%3D0%26backfill%3D0&referer=http%3A%2F%2F155chan.net%2F&adbw=master-1%3A360
69.784
8.4
6.588
Minimizes main-thread work — 1.5 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
931.148
Other
271.716
Script Parsing & Compilation
93.824
Rendering
67.04
Style & Layout
65.008
Parse HTML & CSS
46.3
Garbage Collection
23.224
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 — 21 requests • 316 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
21
323579
Script
7
307214
Document
3
7942
Other
7
5129
Image
4
3294
Stylesheet
0
0
Media
0
0
Font
0
0
Third-party
16
315324
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.0525146484375
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 — 4 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://img1.wsimg.com/parking-lander/static/js/main.4e219663.chunk.js
4170
415
https://www.google.com/adsense/domains/caf.js?pac=2
4920
160
Unattributable
3720
78
https://img1.wsimg.com/parking-lander/static/js/2.5940ae1c.chunk.js
3798
58
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 155chan.net on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

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

Audits

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://155chan.net/
http/1.1
0
621.5960001573
2191
1885
200
text/html
Document
http://155chan.net/px.js?ch=1
http/1.1
634.79700009339
858.68300008588
628
346
200
application/javascript
Script
http://155chan.net/px.js?ch=2
http/1.1
635.11599996127
862.03499999829
1091
346
200
application/javascript
Script
http://ww8.155chan.net/
http/1.1
868.16100007854
1211.3370001316
1067
0
302
text/html
http://www6.155chan.net/?template=ARROW_3&tdfs=1&s_token=1664731200.0336410000&uuid=1664731200.0336410000&term=Free%20Movie%20Streaming&term=Live%20Person%20Chat%20System&term=Elite%20Dating%20Services&searchbox=0&showDomain=0&backfill=0
http/1.1
1211.7749999743
1355.2139999811
3278
2551
200
text/html
Document
https://www.google.com/adsense/domains/caf.js
h2
1369.8740000837
1385.2350001689
54853
148027
200
text/javascript
Script
https://img1.wsimg.com/parking-lander/static/js/2.5940ae1c.chunk.js
h2
1370.0540000573
1413.647999987
136156
428909
200
application/javascript
Script
https://img1.wsimg.com/parking-lander/static/js/main.4e219663.chunk.js
h2
1370.1760000549
1420.4820001032
58816
280078
200
application/javascript
Script
https://api.aws.parking.godaddy.com/v1/domains/domain?domain=www6.155chan.net&portfolioId=
h2
1563.5930001736
1595.2950001229
722
0
200
Preflight
https://api.aws.parking.godaddy.com/v1/domains/domain?domain=www6.155chan.net&portfolioId=
h2
1595.8849999588
1617.7870000247
1574
884
200
application/json
Fetch
https://partner.googleadservices.com/gampad/cookie.js?domain=www6.155chan.net&client=dp-namemedia08_3ph&product=SAS&callback=__sasCookie
h2
1651.5170000494
1657.9220001586
823
188
200
text/javascript
Script
https://www.google.com/afs/ads?adsafe=low&adtest=off&psid=3767353295&pcsa=false&channel=08231&domain_name=155chan.net&client=dp-namemedia08_3ph&r=m&terms=Free%20Movie%20Streaming%2CLive%20Person%20Chat%20System%2CElite%20Dating%20Services&type=3&swp=as-drid-2235535430585190&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002%2C17300953%2C17300956%2C17301068%2C17301071%2C17301094%2C17301097&format=r3&nocache=5051664731200968&num=0&output=afd_ads&v=3&bsl=8&pac=2&u_his=2&u_tz=-420&dt=1664731200970&u_w=360&u_h=640&biw=360&bih=640&psw=360&psh=245&frm=0&uio=-&cont=relatedLinks&jsid=caf&jsv=476880816&rurl=http%3A%2F%2Fwww6.155chan.net%2F%3Ftemplate%3DARROW_3%26tdfs%3D1%26s_token%3D1664731200.0336410000%26uuid%3D1664731200.0336410000%26term%3DFree%2520Movie%2520Streaming%26term%3DLive%2520Person%2520Chat%2520System%26term%3DElite%2520Dating%2520Services%26searchbox%3D0%26showDomain%3D0%26backfill%3D0&referer=http%3A%2F%2F155chan.net%2F&adbw=master-1%3A360
h2
1668.543000007
1757.4410000816
2473
6475
200
text/html
Document
https://www.google.com/adsense/domains/caf.js?pac=2
h2
1772.0350001473
1786.7060001008
54847
148020
200
text/javascript
Script
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
h2
1838.1990001071
1844.9310001452
1188
391
200
image/svg+xml
Image
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
h2
1838.3600001689
1845.4540001694
1090
200
200
image/svg+xml
Image
https://api.aws.parking.godaddy.com/v1/parkingEvents
h2
1849.4220001157
1869.8899999727
619
0
200
text/plain
Preflight
https://postback.trafficmotor.com/sn/
http/1.1
1849.9140001368
2172.5500000175
383
0
200
text/html
Preflight
https://api.aws.parking.godaddy.com/v1/parkingEvents
h2
1870.3560000286
1902.689000126
539
0
200
text/plain
Fetch
https://postback.trafficmotor.com/sn/
http/1.1
2173.2020000927
2509.5820000861
225
3
200
application/json
Fetch
https://www.google.com/afs/gen_204?client=dp-namemedia08_3ph&output=uds_ads_only&zx=qzb70890x6ez&aqid=Qcg5Y52OAtK4mwSD4bvYCA&psid=3767353295&pbt=bs&adbx=0&adby=182&adbh=478&adbw=360&adbah=152%2C152%2C152&adbn=master-1&eawp=partner-dp-namemedia08_3ph&errv=476880816&csala=12%7C0%7C116%7C30%7C74&lle=0&llm=1000&ifv=1&usr=1
h2
3388.6120000388
3409.4120000955
689
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-namemedia08_3ph&output=uds_ads_only&zx=7lg5mhcwb0ie&aqid=Qcg5Y52OAtK4mwSD4bvYCA&psid=3767353295&pbt=bv&adbx=0&adby=182&adbh=478&adbw=360&adbah=152%2C152%2C152&adbn=master-1&eawp=partner-dp-namemedia08_3ph&errv=476880816&csala=12%7C0%7C116%7C30%7C74&lle=0&llm=1000&ifv=1&usr=1
h2
3889.4490001258
3911.2460000906
327
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)
-239.529
11.637
494.501
11.643
530.702
12.258
552.818
12.446
585.788
8.568
594.397
103.823
754.716
19.58
774.685
29.121
895.478
7.79
905.034
5.884
933.494
40.12
974.833
8.951
983.823
6.642
2516.509
5.213
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

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

Other

Eliminate render-blocking resources — Potential savings of 450 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. 155chan.net should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://www.google.com/adsense/domains/caf.js
54853
1230

Metrics

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

Audits

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

Other

Reduce unused JavaScript — Potential savings of 176 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://img1.wsimg.com/parking-lander/static/js/2.5940ae1c.chunk.js
136156
66182
https://img1.wsimg.com/parking-lander/static/js/main.4e219663.chunk.js
58816
49030
https://www.google.com/adsense/domains/caf.js
54853
33137
https://www.google.com/adsense/domains/caf.js?pac=2
54847
31928
Avoid multiple page redirects — Potential savings of 1,260 ms
Redirects can cause additional delays before the page can begin loading. 155chan.net should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://155chan.net/
630
http://ww8.155chan.net/
630
http://www6.155chan.net/?template=ARROW_3&tdfs=1&s_token=1664731200.0336410000&uuid=1664731200.0336410000&term=Free%20Movie%20Streaming&term=Live%20Person%20Chat%20System&term=Elite%20Dating%20Services&searchbox=0&showDomain=0&backfill=0
0
Reduce the impact of third-party code — Third-party code blocked the main thread for 430 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)
198426
374.652
113189
56.388
823
0
First Contentful Paint (3G) — 8635 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 155chan.net. 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.
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 `[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"]`
155chan.net may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

Document doesn't have 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.
Failing Elements
`<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

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 155chan.net 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.
Name Version
React
core-js
core-js-global@3.25.1
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://img1.wsimg.com/parking-lander/static/js/main.4e219663.chunk.js
https://img1.wsimg.com/parking-lander/static/js/main.4e219663.chunk.js.map
https://img1.wsimg.com/parking-lander/static/js/2.5940ae1c.chunk.js
https://img1.wsimg.com/parking-lander/static/js/2.5940ae1c.chunk.js.map
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 5 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://155chan.net/
Allowed
http://155chan.net/px.js?ch=1
Allowed
http://155chan.net/px.js?ch=2
Allowed
http://ww8.155chan.net/
Allowed
http://www6.155chan.net/?template=ARROW_3&tdfs=1&s_token=1664731200.0336410000&uuid=1664731200.0336410000&term=Free%20Movie%20Streaming&term=Live%20Person%20Chat%20System&term=Elite%20Dating%20Services&searchbox=0&showDomain=0&backfill=0
Allowed
75

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for 155chan.net. 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 155chan.net on mobile screens.
Document uses legible font sizes — 73.62% 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
.footerLine
26.38%
11px
73.62%
≥ 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.

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.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

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.

Content Best Practices

Document doesn't have 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.
Failing Elements
Document does not have 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.

Crawling and Indexing

Page is 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.
Blocking Directive Source

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 155chan.net. 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 155chan.net 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: 45.33.18.44
Continent: North America
Country: United States
United States Flag
Region: Texas
City: Richardson
Longitude: -96.7028
Latitude: 32.9473
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Linode
Registration

Domain Registrant

Private Registration: Yes
Name: Domain Admin
Organization: Privacy Protect, LLC (PrivacyProtect.org)
Country: US
City: Burlington
State: MA
Post Code: 01803
Email: contact@privacyprotect.org
Phone: +1.8022274003
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
PDR Ltd. d/b/a PublicDomainRegistry.com 104.17.176.154
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: 155chan.net
Issued By: R3
Valid From: 14th November, 2022
Valid To: 12th February, 2023
Subject: CN = 155chan.net
Hash: 63d2332d
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x03761A1907E3C2455EE2F05F4F48A0464B37
Serial Number (Hex): 03761A1907E3C2455EE2F05F4F48A0464B37
Valid From: 14th November, 2024
Valid To: 12th February, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org

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

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 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 : Nov 15 00:08:30.935 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:B7:19:13:72:9F:12:4B:53:F6:35:47:
B3:D6:80:60:DC:24:BD:2D:FC:74:93:F8:39:EC:8C:46:
FB:6B:95:10:28:02:20:15:39:DE:4D:32:B2:AD:B8:51:
A6:20:9B:E1:34:1C:A8:FD:67:1F:4C:B8:67:9E:DF:6F:
B8:5B:6C:81:53:DC:B4
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 : Nov 15 00:08:31.262 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:C1:7B:FA:05:68:8D:19:5E:82:78:DF:
34:44:7F:4A:61:24:A5:B4:3E:F6:EF:06:11:23:EE:14:
9E:E6:40:87:DF:02:21:00:93:D1:89:AA:41:7D:54:3F:
28:B7:E7:74:F9:5C:B3:DA:D9:34:F6:10:F6:F2:1C:39:
54:26:1A:59:B8:B0:51:42
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:155chan.net
DNS:*.155chan.net
Technical

DNS Lookup

A Records

Host IP Address Class TTL
155chan.net. 64.190.62.22 IN 600

NS Records

Host Nameserver Class TTL
155chan.net. ns1.sedoparking.com. IN 21600
155chan.net. ns2.sedoparking.com. IN 21600

MX Records

Priority Host Server Class TTL
0 155chan.net. localhost. IN 3600

SOA Records

Domain Name Primary NS Responsible Email TTL
155chan.net. ns1.sedoparking.com. hostmaster.sedo.de. 600

TXT Records

Host Value Class TTL
155chan.net. v=spf1 IN 3600

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
server: openresty/1.13.6.1
date: 10th January, 2023
content-type: application/octet-stream
content-length: 0
connection: close

Whois Lookup

Created: 22nd October, 2013
Changed: 14th November, 2022
Expires: 22nd October, 2023
Registrar: PDR Ltd. d/b/a PublicDomainRegistry.com
Status: clientTransferProhibited
Nameservers: ns1.mytrafficmanagement.com
ns2.mytrafficmanagement.com
Owner Name: Domain Admin
Owner Organization: Privacy Protect, LLC (PrivacyProtect.org)
Owner Street: 10 Corporate Drive
Owner Post Code: 01803
Owner City: Burlington
Owner State: MA
Owner Country: US
Owner Phone: +1.8022274003
Owner Email: contact@privacyprotect.org
Admin Name: Domain Admin
Admin Organization: Privacy Protect, LLC (PrivacyProtect.org)
Admin Street: 10 Corporate Drive
Admin Post Code: 01803
Admin City: Burlington
Admin State: MA
Admin Country: US
Admin Phone: +1.8022274003
Admin Email: contact@privacyprotect.org
Tech Name: Domain Admin
Tech Organization: Privacy Protect, LLC (PrivacyProtect.org)
Tech Street: 10 Corporate Drive
Tech Post Code: 01803
Tech City: Burlington
Tech State: MA
Tech Country: US
Tech Phone: +1.8022274003
Tech Email: contact@privacyprotect.org
Full Whois: Domain Name: 155CHAN.NET
Registry Domain ID: 1831990729_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois.publicdomainregistry.com
Registrar URL: www.publicdomainregistry.com
Updated Date: 2022-11-14T16:52:23Z
Creation Date: 2013-10-22T00:35:03Z
Registrar Registration Expiration Date: 2023-10-22T00:35:03Z
Registrar: PDR Ltd. d/b/a PublicDomainRegistry.com
Registrar IANA ID: 303
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: Not Available From Registry
Registrant Name: Domain Admin
Registrant Organization: Privacy Protect, LLC (PrivacyProtect.org)
Registrant Street: 10 Corporate Drive
Registrant City: Burlington
Registrant State/Province: MA
Registrant Postal Code: 01803
Registrant Country: US
Registrant Phone: +1.8022274003
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: contact@privacyprotect.org
Registry Admin ID: Not Available From Registry
Admin Name: Domain Admin
Admin Organization: Privacy Protect, LLC (PrivacyProtect.org)
Admin Street: 10 Corporate Drive
Admin City: Burlington
Admin State/Province: MA
Admin Postal Code: 01803
Admin Country: US
Admin Phone: +1.8022274003
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: contact@privacyprotect.org
Registry Tech ID: Not Available From Registry
Tech Name: Domain Admin
Tech Organization: Privacy Protect, LLC (PrivacyProtect.org)
Tech Street: 10 Corporate Drive
Tech City: Burlington
Tech State/Province: MA
Tech Postal Code: 01803
Tech Country: US
Tech Phone: +1.8022274003
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: contact@privacyprotect.org
Name Server: ns1.mytrafficmanagement.com
Name Server: ns2.mytrafficmanagement.com
DNSSEC: Unsigned
Registrar Abuse Contact Email: abuse-contact@publicdomainregistry.com
Registrar Abuse Contact Phone: +1.2013775952
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2023-01-10T03:32:36Z <<<

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

Registration Service Provided By: WQRM HOLDINGS INC

PRIVACYPROTECT.ORG is providing privacy protection services to this domain name to
protect the owner from spam and phishing attacks. PrivacyProtect.org is not
responsible for any of the activities associated with this domain name. If you wish
to report any abuse concerning the usage of this domain name, you may do so at
http://privacyprotect.org/contact. We have a stringent abuse policy and any
complaint will be actioned within a short period of time.

The data in this whois database is provided to you for information purposes
only, that is, to assist you in obtaining information about or related to a
domain name registration record. We make this information available "as is",
and do not guarantee its accuracy. By submitting a whois query, you agree
that you will use this data only for lawful purposes and that, under no
circumstances will you use this data to:
(1) enable high volume, automated, electronic processes that stress or load
this whois database system providing you this information; or
(2) allow, enable, or otherwise support the transmission of mass unsolicited,
commercial advertising or solicitations via direct mail, electronic mail, or
by telephone.
The compilation, repackaging, dissemination or other use of this data is
expressly prohibited without prior written consent from us. The Registrar of
record is PDR Ltd. d/b/a PublicDomainRegistry.com.
We reserve the right to modify these terms at any time.
By submitting this query, you agree to abide by these terms.


Nameservers

Name IP Address
ns1.mytrafficmanagement.com 52.223.41.32
ns2.mytrafficmanagement.com 35.71.129.26
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
$570 USD 1/5
0/5
$22 USD 1/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
0/5
$1,033 USD 1/5
0/5
0/5
0/5