155chan.Gr - Info 155chan.gr

155chan.gr receives about 9,072 unique visitors and 9,072 (1.00 per visitor) page views per day which should earn about $76.90/day from advertising revenue. Estimated site value is $56,138.09. According to Alexa Traffic Rank 155chan.gr is ranked number 349,163 in the world and 0.0002% of global Internet users visit it. Site is hosted in Amsterdam, North Holland, 1091, Belize and links to network IP address 198.144.121.148. This server supports HTTPS and doesn't support HTTP/2.

About - 155chan.gr


Technologies used on Website

Web Servers
Nginx
Reverse proxies
Nginx

155chan.gr Profile

Title: 155chan.gr 2.0 — Chan pedo community
Description: This is a default index page for a new domain.
Last update was 2 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with 155chan.gr in any way. Only publicly available statistics data are displayed.

How popular is 155chan.gr?

9.1K daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
9,072
Monthly Unique Visitors:
217,728
Pages per Visit:
1.00
Daily Pageviews:
9,072
Alexa Rank:
349,163 visit alexa
Alexa Reach:
0.0002%   (of global internet users)
Avg. visit duration:
08:16
Bounce rate:
51.46%
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources

Direct:
57.09%
Referral:
41.15%
Search:
0.64%
Social:
0.46%
Paid:
0.65%

Visitors by country

Users%Pageviews%Rank
United States 75.9%73.9%158933

Where do visitors go on this site?

Reach%Pageviews%PerUser
155chan.gr
100.00%100.00%1

Competitive Data

SEMrush
Domain:
  155chan.gr
Rank:
(Rank based on keywords, cost and organic traffic)
  34,680
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  0
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
  0
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
  0
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)
  $0.00

+ Moz Data

Domain Authority:
  27
Page Authority:
  35
MozRank:
  4

+ How socially engaged is 155chan.gr?

Facebook:
  0
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
155chan.gr
Last Change Time:
(The last time that the site changed status.)
2018-12-04 00:18:43
Region:
(The Ad Standard region to which this site has been assigned.)
B
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Passing


Mobile summary

Last Change Time:
(The last time that the site changed status.)
2018-12-04 00:18:44
Region:
(The Ad Standard region to which this site has been assigned.)
B
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Passing

+ Abusive Experience Report

Root domain:
155chan.gr
Last Change Time:
(The last time that the site changed status.)
2018-12-04 00:18:44
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Passing

+ How much 155chan.gr can earn?

Daily Revenue:
$76.90
Monthly Revenue:
$2,307.00
Yearly Revenue:
$28,068.50
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
United States 6,704$76.90

How much money do 155chan.gr lose due to Adblock?

Daily Revenue Loss:
$13.84
Monthly Revenue Loss:
$415.25
Yearly Revenue Loss:
$5,052.15
Daily Pageviews Blocked:
1,207
Monthly Pageviews Blocked:
36,203
Yearly Pageviews Blocked:
440,466
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
United States 1,207$13.84

How much is 155chan.gr worth?

Website Value:
$56,138.09

+ Where is 155chan.gr hosted?

Server IP:
198.144.121.148
ASN:
AS206264 
ISP:
Amarutu Technology Ltd 
Server Location:
Amsterdam
North Holland, NH
1091
Belize, BZ
 

Other sites hosted on 198.144.121.148

+ How fast does 155chan.gr load?

Average Load Time:
(7730 ms) 2 % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

100
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a AVERAGE speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

First Contentful Paint (FCP)1.3s 65% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 65% 26% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 26% 8% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 8%
First Input Delay (FID)34ms 97% of loads for this page have a fast (<100ms) First Input Delay (FID) 97% 1% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 1% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

Origin Data

All pages served from this origin have an AVERAGE speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

First Contentful Paint (FCP)1.3s 65% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 65% 26% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 26% 8% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 8%
First Input Delay (FID)34ms 97% of loads for this page have a fast (<100ms) First Input Delay (FID) 97% 1% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 1% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

Lab Data

First Meaningful Paint 0.4 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 0.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Minimize third-party usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Speed Index 0.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.4 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.4 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Keep request counts low and transfer sizes small - 9 requests • 22 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
922 KB
Image
416 KB
Document
13 KB
Script
12 KB
Other
31 KB
Stylesheet
00 KB
Media
00 KB
Font
00 KB
Third-party
819 KB
Eliminate render-blocking resources - Potential savings of 180 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
http://cdn.popcash.net/pop.150218.js
2 KB190
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://155chan.gr/
0 ms527 ms3 KB6 KB200text/htmlDocument
http://cdn.popcash.net/pop.150218.js
544 ms574 ms2 KB3 KB200application/javascriptScript
https://i.postimg.cc/BvrL37dy/amf.jpg
544 ms731 ms2 KB2 KB200image/jpegImage
https://teenlist.top/button.png
544 ms609 ms7 KB7 KB200image/pngImage
https://ls-girls.biz/topsite/button.php?u=155chan
579 ms683 ms0 KB0 KB302text/html
https://18top.link/button.php?u=155chan
579 ms1583 ms0 KB0 KB302text/html
https://dcba.popcash.net/znWaa3gu
578 ms645 ms0 KB0 KB204text/plainXHR
https://ls-girls.biz/topsite/images/button.png
684 ms1068 ms2 KB2 KB200image/pngImage
http://18top.link/images/button.png
1583 ms1861 ms5 KB5 KB200image/pngImage
Uses efficient cache policy on static assets - 2 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://cdn.popcash.net/pop.150218.js
2592000000 ms2 KB
http://18top.link/images/button.png
5184000000 ms5 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
550 ms
11 ms
596 ms
6 ms
602 ms
17 ms
667 ms
5 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
55 ms3 ms1 ms
Avoids enormous network payloads - Total size was 22 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://teenlist.top/button.png
7 KB
http://18top.link/images/button.png
5 KB
http://155chan.gr/
3 KB
https://ls-girls.biz/topsite/images/button.png
2 KB
https://i.postimg.cc/BvrL37dy/amf.jpg
2 KB
http://cdn.popcash.net/pop.150218.js
2 KB
https://ls-girls.biz/topsite/button.php?u=155chan
0 KB
https://18top.link/button.php?u=155chan
0 KB
https://dcba.popcash.net/znWaa3gu
0 KB
Minimizes main-thread work - 0.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Other
26 ms
Style & Layout
16 ms
Script Evaluation
9 ms
Rendering
6 ms
Parse HTML & CSS
3 ms
Script Parsing & Compilation
2 ms
Avoids an excessive DOM size - 68 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
68
Maximum DOM Depth
5
Maximum Child Elements
18
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 530 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Serve images in next-gen formats
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

Avoid chaining critical requests - 1 chain found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.


Page Speed (Google PageSpeed Insights) - Mobile

100
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a AVERAGE speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

First Contentful Paint (FCP)1.1s 65% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 72% 23% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 23% 4% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 4%
First Input Delay (FID)276ms 1% of loads for this page have a fast (<100ms) First Input Delay (FID) 1% 96% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 96% 2% of loads for this page have a slow (>300ms) First Input Delay (FID) 2%

Origin Data

All pages served from this origin have an AVERAGE speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

First Contentful Paint (FCP)1.1s 72% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 72% 23% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 23% 4% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 4%
First Input Delay (FID)276ms 97% of loads for this page have a fast (<100ms) First Input Delay (FID) 1% 96% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 96% 2% of loads for this page have a slow (>300ms) First Input Delay (FID) 2%

Lab Data

First Meaningful Paint 1.3 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 1.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Minimize third-party usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
First Contentful Paint (3G) 2460 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Speed Index 1.5 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.3 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 1.3 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Keep request counts low and transfer sizes small - 9 requests • 22 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
922 KB
Image
416 KB
Document
13 KB
Script
12 KB
Other
31 KB
Stylesheet
00 KB
Media
00 KB
Font
00 KB
Third-party
819 KB
Eliminate render-blocking resources - Potential savings of 630 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
http://cdn.popcash.net/pop.150218.js
2 KB630
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://155chan.gr/
0 ms595 ms3 KB6 KB200text/htmlDocument
http://cdn.popcash.net/pop.150218.js
609 ms647 ms2 KB3 KB200application/javascriptScript
https://i.postimg.cc/BvrL37dy/amf.jpg
610 ms673 ms2 KB2 KB200image/jpegImage
https://teenlist.top/button.png
610 ms706 ms7 KB7 KB200image/pngImage
https://ls-girls.biz/topsite/button.php?u=155chan
650 ms1072 ms0 KB0 KB302text/html
https://18top.link/button.php?u=155chan
650 ms1724 ms0 KB0 KB302text/html
https://dcba.popcash.net/znWaa3gu
650 ms755 ms0 KB0 KB204text/plainXHR
https://ls-girls.biz/topsite/images/button.png
1072 ms1564 ms2 KB2 KB200image/pngImage
http://18top.link/images/button.png
1724 ms2010 ms5 KB5 KB200image/pngImage
Uses efficient cache policy on static assets - 2 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://cdn.popcash.net/pop.150218.js
2592000000 ms2 KB
http://18top.link/images/button.png
5184000000 ms5 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
618 ms
10 ms
673 ms
8 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
155 ms8 ms4 ms
Avoids enormous network payloads - Total size was 22 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://teenlist.top/button.png
7 KB
http://18top.link/images/button.png
5 KB
http://155chan.gr/
3 KB
https://ls-girls.biz/topsite/images/button.png
2 KB
https://i.postimg.cc/BvrL37dy/amf.jpg
2 KB
http://cdn.popcash.net/pop.150218.js
2 KB
https://ls-girls.biz/topsite/button.php?u=155chan
0 KB
https://18top.link/button.php?u=155chan
0 KB
https://dcba.popcash.net/znWaa3gu
0 KB
Minimizes main-thread work - 0.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Other
87 ms
Style & Layout
27 ms
Script Evaluation
25 ms
Rendering
22 ms
Parse HTML & CSS
8 ms
Script Parsing & Compilation
6 ms
Avoids an excessive DOM size - 68 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
68
Maximum DOM Depth
5
Maximum Child Elements
18
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 600 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Serve images in next-gen formats
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

Avoid chaining critical requests - 1 chain found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

While the chan…uth ***uality. renders only 6 pixels tall (15 CSS pixels) .
Onion Center S…h (onion site) and 27 others render only 6 pixels tall (15 CSS pixels) .
Topiclink&#39;s al…gem or three. and 21 others render only 6 pixels tall (15 CSS pixels) .
and possibly have you v&amp; and 2 others render only 6 pixels tall (15 CSS pixels) .
If we missed a…&quot;dot&quot; symbols) and 9 others render only 6 pixels tall (15 CSS pixels) .

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking script resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Remove render-blocking JavaScript:

http://cdn.popcash.net/pop.150218.js

Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="http://jwzzevn…r75aybyd.onion">MyLove (onion site)</a> and 21 others are close to other tap targets .

Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

Configure a viewport for this page.

Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 638B (19% reduction).

Compressing https://i.postimg.cc/BvrL37dy/amf.jpg could save 409B (25% reduction).
Compressing https://ls-girls.biz/topsite/images/button.png could save 229B (14% reduction).
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Enable compression
You have compression enabled. Learn more about enabling compression.
Leverage browser caching
You have enabled browser caching. Learn more about browser caching recommendations.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Minify CSS
Your CSS is minified. Learn more about minifying CSS.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does 155chan.gr use compression?

155chan.gr use gzip compression.
Original size: 5.93 KB
Compressed size: 2.81 KB
File reduced by: 3.11 KB (52%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  19
Vendor reliability:
  19
Privacy:
  19
Child safety:
  n/a

+ SSL Checker - SSL Certificate Verify

155chan.gr supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: 155chan.gr
Organization:
Location:
Issuer: Let's Encrypt Authority X3
Valid from: Mar 31 03:34:24 2020 GMT
Valid until: Jun 29 03:34:24 2020 GMT
Authority:
Keysize:

+ Verify HTTP/2 Support

155chan.gr does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Server: nginx
Date: Thu, 02 Apr 2020 09:24:50 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: keep-alive
Keep-Alive: timeout=60
Vary: Accept-Encoding
Last-Modified: Thu, 26 Mar 2020 17:12:38 GMT
ETag: W/"17b5-5a1c517792d80"
Content-Encoding: gzip

+ DNS Lookup

Type Ip Target TTL
A 198.144.121.148 3600
SOA 3600
Mname ns1.hostaqua.net
Rname root.155chan.gr
Serial Number 2019111801
Refresh 7200
Retry 3600
Expire 1209600
Minimum TTL 0
TXT 3600
MX mail.155chan.gr 3600
NS ns2.hotdomains.site 3580
NS ns1.hotdomains.site 3580

+ Whois Lookup

Domain Created:
0000-00-00
Domain Age:
 
WhoIs:
 

Currently Not Available
Last update was 2 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with 155chan.gr in any way. Only publicly available statistics data are displayed.

Recently Analyzed Sites

comerz.ru
8 secs
tvlovertv.tk
13 secs
infobrus.ru
30 secs
skypaybd.com
1 min
bridgwatermasjid.com
1 min
glassmedia.ca
1 min
gclubtheone.com
2 mins
bridgendbites.com
2 mins
briannaauto.parts
3 mins
***-shopi.ru
4 mins
WHAT WE RECOMMEND:
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!

BrowserExtension

Install HypeStat extension in your browser to see statistics and technologies used with one click.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
155chan.gr widget