4chan.Org - Info 4chan.org

4chan.org receives about 923,016 unique visitors and 6,119,599 (6.63 per visitor) page views per day which should earn about $44,233.87/day from advertising revenue. Estimated site value is $33,429,365.20. According to Alexa Traffic Rank 4chan.org is ranked number 805 in the world and 0.0544% of global Internet users visit it. Site is hosted in San Francisco, CA, 94107, United States and links to network IP address 104.17.136.89. This server supports HTTPS and HTTP/2.
Loading...

About - 4chan.org

Covers Japanese culture, interests and creativity with an x-rated section providing ***, *** and GIF animations.
Edit Site Info

Technologies used on Website

CDN
CloudFlare
Analytics
Google Analytics

4chan.org Profile

Title: 4chan
Keywords: imageboard,image board,forum,bbs,anonymous,chan,anime,manga,ecchi,***,video games,english,japan
Last update was 13 days ago
loader
This can take up to 60 seconds. Please wait...

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

How popular is 4chan.org?

0.9M daily visitors
Daily Unique Visitors:
923,016
Monthly Unique Visitors:
27,690,480
Pages per Visit:
6.63
Daily Pageviews:
6,119,599
Loading...
Alexa Rank:
805 visit alexa
Alexa Reach:
0.0544%   (of global internet users)
Avg. visit duration:
15:30
Bounce rate:
29.36%
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources

Direct:
53.61%
Referral:
22.58%
Search:
21.33%
Social:
2.48%
Paid:
0%

Visitors by country

Users%Pageviews%Rank
United States 43.5%40.7%420
United Kingdom 8.7%8.2%200
Germany 5.9%7.7%531
Canada 5.6%5.9%367
Norway 4.0%5.8%93
Denmark 2.8%3.1%97
Australia 2.6%2.7%551
Netherlands 2.5%2.4%255
Sweden 2.4%1.9%201
Italy 2.4%2.4%984
France 2.3%1.5%1463
Spain 2.3%2.5%877
Poland 1.8%2.9%678
Brazil 1.5%2.3%2395
Ireland 1.0%1.0%320
Belgium 0.9%0.9%634
Mexico 0.9%0.6%2315
Romania 0.7%0.9%724
Austria 0.6%0.5%1030
Portugal 0.5%0.4%778

Where do visitors go on this site?

Reach%Pageviews%PerUser
boards.4chan.org
84.93%84.18%6.56
4chan.org
48.15%7.77%1.07
is2.4chan.org
11.93%7.88%4.4
sys.4chan.org
0.89%0.15%1.1
OTHER
0%0.03%0

+ Competitive Data

SEMrush
Domain:
  4chan.org
Rank:
(Rank based on keywords, cost and organic traffic)
  2,259
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  49,506
Organic Traffic:
(Number of visitors coming from top 20 search results)
  1,325,986
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $415,584.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

On October 30 SEMrush is hosting first of a kind 24-hour online conference for marketers around the globe — Global Marketing Day. The event is designed for marketers to learn from the most successful in the field. Speakers from Google, Walt Disney, Adobe, BBC, WeWork, and many more will share real cases, tools and insights, so attendees can find out more about marketing in a day than many do by slaving over books for months. This unique experience is absolutely free!
Sign up & watch for free >>

+ Moz Data

Domain Authority:
  87
Page Authority:
  64
MozRank:
  6

+ How socially engaged is 4chan.org?

Facebook:
  33
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:
4chan.org
Last Change Time:
(The last time that the site changed status.)
2018-06-22 04:08:24
Region:
(The Ad Standard region to which this site has been assigned.)
A
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-06-21 07:02:23
Region:
(The Ad Standard region to which this site has been assigned.)
A,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:
4chan.org
Last Change Time:
(The last time that the site changed status.)
2018-06-22 04:08:24
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 4chan.org can earn?

Daily Revenue:
$44,233.87
Monthly Revenue:
$1,327,016.10
Yearly Revenue:
$16,145,362.55
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
United States 2,490,677$28,568.06
United Kingdom 501,807$3,126.26
Canada 361,056$2,531.00
Germany 471,209$2,275.94
Norway 354,937$1,881.16
Australia 165,229$1,244.18
Netherlands 146,870$747.57
Denmark 189,708$728.48
Sweden 116,272$618.57
Italy 146,870$512.58
France 91,794$431.43
Poland 177,468$321.22
Ireland 61,196$303.53
Belgium 55,076$271.53
Brazil 140,751$249.13
Spain 152,990$169.82
Austria 30,598$99.44
Romania 55,076$64.99
Portugal 24,478$53.36
Mexico 36,718$35.62

How much money do 4chan.org lose due to Adblock?

Daily Revenue Loss:
$8,535.39
Monthly Revenue Loss:
$256,061.60
Yearly Revenue Loss:
$3,115,416.10
Daily Pageviews Blocked:
1,154,095
Monthly Pageviews Blocked:
34,622,855
Yearly Pageviews Blocked:
421,244,739
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
United States 448,322$5,142.25
Germany 136,651$660.02
Canada 90,264$632.75
United Kingdom 80,289$500.20
Norway 70,987$376.23
Australia 33,046$248.84
Denmark 47,427$182.12
Sweden 32,556$173.20
Netherlands 24,968$127.09
Ireland 23,866$118.38
Poland 58,565$106.00
Italy 24,968$87.14
France 10,097$47.46
Belgium 6,609$32.58
Spain 29,068$32.27
Austria 7,955$25.86
Brazil 8,445$14.95
Romania 11,566$13.65
Portugal 5,140$11.21
Mexico 3,305$3.21

How much is 4chan.org worth?

Website Value:
$33,429,365.20

+ Where is 4chan.org hosted?

Server IP:
104.17.136.89
ASN:
AS13335 
ISP:
Cloudflare Inc 
Server Location:
San Francisco
CA
94107
United States, US
 

Other sites hosted on 104.17.136.89

There are no other sites hosted on this IP

+ How fast does 4chan.org load?

Average Load Time:
(1078 ms) 76 % 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.4s 81% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 81% 14% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 14% 3% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 3%
First Input Delay (FID)7ms 98% of loads for this page have a fast (<50ms) First Input Delay (FID) 98% 0% of loads for this page have an average (50ms ~ 250ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>250ms) 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.4s 81% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 81% 14% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 14% 3% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 3%
First Input Delay (FID)7ms 98% of loads for this page have a fast (<50ms) First Input Delay (FID) 98% 0% of loads for this page have an average 50ms ~ 250ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>250ms) 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.
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.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 0.4 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 - 16 requests • 140 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
16140 KB
Image
11112 KB
Script
321 KB
Document
14 KB
Stylesheet
12 KB
Media
00 KB
Font
00 KB
Other
00 KB
Third-party
15136 KB
Eliminate render-blocking resources - Potential savings of 170 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://s.4cdn.org/css/frontpage.12.css
2 KB190
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://4chan.org/
0 ms115 ms4 KB13 KB200text/htmlDocument
http://s.4cdn.org/css/frontpage.12.css
125 ms160 ms2 KB6 KB200text/cssStylesheet
http://s.4cdn.org/image/fp/logo-transparent.png
126 ms155 ms12 KB18 KB403text/htmlImage
http://pl15117602.pvclouds.com/0d81380df517f9c5e0e6d7e4573b0244/invoke.js
126 ms227 ms0 KB0 KB403text/htmlScript
http://i.4cdn.org/jp/1569856014397s.jpg
164 ms222 ms12 KB18 KB403text/htmlImage
http://i.4cdn.org/fa/1570245603913s.jpg
164 ms223 ms12 KB18 KB403text/htmlImage
http://i.4cdn.org/v/1570409592322s.jpg
164 ms224 ms12 KB18 KB403text/htmlImage
http://i.4cdn.org/x/1570257644569s.jpg
164 ms221 ms12 KB18 KB403text/htmlImage
http://i.4cdn.org/a/1570372251876s.jpg
164 ms221 ms12 KB18 KB403text/htmlImage
http://i.4cdn.org/vp/1570188944516s.jpg
164 ms220 ms12 KB18 KB403text/htmlImage
http://i.4cdn.org/lgbt/1570402605077s.jpg
165 ms225 ms12 KB18 KB403text/htmlImage
http://i.4cdn.org/mu/1570391955835s.jpg
165 ms226 ms12 KB18 KB403text/htmlImage
http://s.4cdn.org/js/frontpage.min.7.js
156 ms179 ms3 KB6 KB200application/x-javascriptScript
http://www.google-analytics.com/analytics.js
165 ms170 ms18 KB43 KB200text/javascriptScript
http://s.4cdn.org/image/fp/fade.png
169 ms193 ms1 KB0 KB200image/pngImage
http://s.4cdn.org/image/fp/icon-close-red.png
171 ms197 ms1 KB0 KB200image/pngImage
Uses efficient cache policy on static assets - 1 resource found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://www.google-analytics.com/analytics.js
7200000 ms18 KB
Third-Party Usage - 1 Third-Party Found
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.

Third-Party
SizeMain Thread Time
18 KB24 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
137 ms
6 ms
181 ms
6 ms
187 ms
50 ms
247 ms
8 ms
261 ms
25 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
95 ms3 ms1 ms
Avoids enormous network payloads - Total size was 140 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://www.google-analytics.com/analytics.js
18 KB
http://i.4cdn.org/jp/1569856014397s.jpg
12 KB
http://i.4cdn.org/lgbt/1570402605077s.jpg
12 KB
http://i.4cdn.org/mu/1570391955835s.jpg
12 KB
http://i.4cdn.org/fa/1570245603913s.jpg
12 KB
http://i.4cdn.org/vp/1570188944516s.jpg
12 KB
http://i.4cdn.org/x/1570257644569s.jpg
12 KB
http://s.4cdn.org/image/fp/logo-transparent.png
12 KB
http://i.4cdn.org/a/1570372251876s.jpg
12 KB
http://i.4cdn.org/v/1570409592322s.jpg
12 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.

Category
Time Spent
Style & Layout
46 ms
Script Evaluation
28 ms
Other
25 ms
Rendering
13 ms
Parse HTML & CSS
8 ms
Script Parsing & Compilation
3 ms
Avoids an excessive DOM size - 289 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can 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
289
Maximum DOM Depth
10
Maximum Child Elements
14
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 120 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.

Minimize Critical Requests Depth - 2 chains 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.9s 81% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 62% 32% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 32% 5% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 5%
First Input Delay (FID)29ms 97% of loads for this page have a fast (<50ms) First Input Delay (FID) 97% 1% of loads for this page have an average (50ms ~ 250ms) First Input Delay (FID) 1% 0% of loads for this page have a slow (>250ms) 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.9s 62% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 62% 32% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 32% 5% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 5%
First Input Delay (FID)29ms 98% of loads for this page have a fast (<50ms) First Input Delay (FID) 97% 1% of loads for this page have an average 50ms ~ 250ms) First Input Delay (FID) 1% 0% of loads for this page have a slow (>250ms) First Input Delay (FID) 0%

Lab Data

Speed Index 1.3 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.7 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.
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 130 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 2.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time 40 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
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.
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.

Screenshot Thumbnails

This is what the load of your site looked like.

JavaScript execution time - 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.

URL
Total CPU TimeScript EvaluationScript Parse
Other
565 ms17 ms4 ms
http://www.google-analytics.com/analytics.js
128 ms119 ms9 ms
Avoids enormous network payloads - Total size was 140 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://www.google-analytics.com/analytics.js
18 KB
http://i.4cdn.org/vg/1570375958430s.jpg
12 KB
http://i.4cdn.org/mu/1570400587943s.jpg
12 KB
http://i.4cdn.org/co/1570302647459s.jpg
12 KB
http://i.4cdn.org/toy/1570247673811s.jpg
12 KB
http://i.4cdn.org/his/1570395783645s.jpg
12 KB
http://i.4cdn.org/k/1570402191378s.jpg
12 KB
http://i.4cdn.org/m/1570369161882s.jpg
12 KB
http://i.4cdn.org/v/1570409244739s.jpg
12 KB
http://s.4cdn.org/image/fp/logo-transparent.png
12 KB
Minimizes main-thread work - 0.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Style & Layout
314 ms
Script Evaluation
153 ms
Other
141 ms
Rendering
53 ms
Parse HTML & CSS
36 ms
Script Parsing & Compilation
19 ms
Avoids an excessive DOM size - 293 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can 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
293
Maximum DOM Depth
10
Maximum Child Elements
14
Keep request counts low and transfer sizes small - 16 requests • 140 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
16140 KB
Image
11112 KB
Script
321 KB
Document
14 KB
Stylesheet
12 KB
Media
00 KB
Font
00 KB
Other
00 KB
Third-party
15136 KB
Eliminate render-blocking resources - Potential savings of 470 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://s.4cdn.org/css/frontpage.12.css
2 KB630
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://4chan.org/
0 ms172 ms4 KB14 KB200text/htmlDocument
http://s.4cdn.org/css/frontpage.12.css
188 ms222 ms2 KB6 KB200text/cssStylesheet
http://s.4cdn.org/image/fp/logo-transparent.png
188 ms309 ms12 KB18 KB403text/htmlImage
http://pl15117602.pvclouds.com/0d81380df517f9c5e0e6d7e4573b0244/invoke.js
189 ms322 ms0 KB0 KB403text/htmlScript
http://i.4cdn.org/v/1570409244739s.jpg
227 ms316 ms12 KB18 KB403text/htmlImage
http://i.4cdn.org/co/1570302647459s.jpg
228 ms313 ms12 KB18 KB403text/htmlImage
http://i.4cdn.org/k/1570402191378s.jpg
228 ms312 ms12 KB18 KB403text/htmlImage
http://i.4cdn.org/his/1570395783645s.jpg
228 ms315 ms12 KB18 KB403text/htmlImage
http://i.4cdn.org/m/1570369161882s.jpg
228 ms316 ms12 KB18 KB403text/htmlImage
http://i.4cdn.org/mu/1570400587943s.jpg
228 ms314 ms12 KB18 KB403text/htmlImage
http://i.4cdn.org/vg/1570375958430s.jpg
229 ms318 ms12 KB18 KB403text/htmlImage
http://i.4cdn.org/toy/1570247673811s.jpg
229 ms317 ms12 KB18 KB403text/htmlImage
http://s.4cdn.org/js/frontpage.min.7.js
227 ms248 ms3 KB6 KB200application/x-javascriptScript
http://www.google-analytics.com/analytics.js
229 ms237 ms18 KB43 KB200text/javascriptScript
http://s.4cdn.org/image/fp/fade.png
232 ms276 ms1 KB0 KB200image/pngImage
http://s.4cdn.org/image/fp/icon-close-red.png
233 ms289 ms1 KB0 KB200image/pngImage
Uses efficient cache policy on static assets - 1 resource found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://www.google-analytics.com/analytics.js
7200000 ms18 KB
Third-Party Usage - 1 Third-Party Found
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.

Third-Party
SizeMain Thread Time
18 KB128 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
218 ms
10 ms
230 ms
5 ms
268 ms
6 ms
273 ms
78 ms
366 ms
11 ms
379 ms
6 ms
385 ms
5 ms
391 ms
33 ms
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.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. 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.

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.

Minimize Critical Requests Depth - 2 chains 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.

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

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

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

Your page has 1 blocking CSS 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.Optimize CSS Delivery of the following:

http://s.4cdn.org/css/frontpage.12.css

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="//boards.4channel.org/a/" class="boardlink">Anime &amp; Manga</a> and 62 others are close to other tap targets .

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://www.google-***ytics.com/***ytics.js (2 hours)
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.
Configure the viewport
Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.
Enable compression
You have compression enabled. Learn more about enabling compression.
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.
Optimize images
Your images are optimized. Learn more about optimizing images.
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.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does 4chan.org use compression?

4chan.org use gzip compression.
Original size: 13.3 KB
Compressed size: 3.39 KB
File reduced by: 9.92 KB (74%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  86
Vendor reliability:
  86
Privacy:
  86
Child safety:
  12

+ SSL Checker - SSL Certificate Verify

4chan.org supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: COMODO ECC Certification Authority
Organization: COMODO CA Limited
Location: Salford, Greater Manchester, GB
Issuer: AddTrust External CA Root
Valid from: May 30 10:48:38 2000 GMT
Valid until: May 30 10:48:38 2020 GMT
Authority: Is a CA
Keysize: 832 Bits

+ Verify HTTP/2 Support

4chan.org supports HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Internet/Chats and Forums

+ Http Header

Date: Mon, 07 Oct 2019 01:45:35 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: keep-alive
Set-Cookie: __cfduid=deef983d7fe98fe5d5636ff7ec3bd3b0c1570412735; expires=Tue, 06-Oct-20 01:45:35 GMT; path=/; domain=.4chan.org; HttpOnly
Cache-Control: public, max-age=120, s-maxage=120
Vary: Cookie,Accept-Encoding
X-Frame-Options: SAMEORIGIN
CF-Cache-Status: DYNAMIC
Server: cloudflare
CF-RAY: 521c324dfc4bc653-MSP
Content-Encoding: gzip

+ DNS Lookup

Type Ip Target TTL
HINFO 3600
NS rick.ns.cloudflare.com 3600
NS rita.ns.cloudflare.com 3600

+ Whois Lookup

Domain Created:
2004-02-14
Domain Age:
15 years 7 months 21 days  
WhoIs:
 

whois lookup at whois.pir.org...
Domain Name: 4CHAN.ORG
Registry Domain ID: D103979195-LROR
Registrar WHOIS Server: whois.cloudflare.com
Registrar URL: http://www.cloudflare.com
Updated Date: 2015-11-03T00:20:14Z
Creation Date: 2004-02-14T15:46:26Z
Registry Expiry Date: 2023-02-14T15:46:26Z
Registrar Registration Expiration Date:
Registrar: CloudFlare, Inc.
Registrar IANA ID: 1910
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1.6503198930
Reseller:
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Registrant Organization: 4chan community support LLC
Registrant State/Province: CA
Registrant Country: US
Name Server: RICK.NS.CLOUDFLARE.COM
Name Server: RITA.NS.CLOUDFLARE.COM
DNSSEC: signedDelegation
URL of the ICANN Whois Inaccuracy Complaint Form https://www.icann.org/wicf/)
>>> Last update of WHOIS database: 2019-10-07T01:44:52Z <<<

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

Access to Public Interest Registry WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the Public Interest Registry registry database. The data in this record is provided by Public Interest Registry for informational purposes only, and Public Interest Registry does not guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no cir***stances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Afilias except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Public Interest Registry reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.

The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Last update was 13 days ago
loader
This can take up to 60 seconds. Please wait...

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

Recently Analyzed Sites

maac4kids.org
24 secs
***et***e.com
38 secs
luxtaxi.rs
2 mins
lucacleveland.com
2 mins
lowtherloudspeakers.com
3 mins
date-me.com
3 mins
problogbooster.com
4 mins
lovasut.hu
4 mins
freehack.tools
4 mins
***-***www.******x.com
4 mins

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!
4chan.org widget