Dcard.tw - Info 
Domain Summary
What is the traffic rank for Dcard.tw?
• Dcard.tw ranks 392 globally on Alexa.
What percent of global Internet users visit Dcard.tw?
• 0.0185% of global Internet users visit Dcard.tw
How many people visit Dcard.tw each day?
• Dcard.tw receives approximately 0.9M visitors and 2,854,674 page impressions per day.
Which countries does Dcard.tw receive most of its visitors from?
• Dcard.tw is mostly visited by people located in Taiwan,Japan,Hong Kong.
How much Dcard.tw can earn?
• Dcard.tw should earn about $5,724.88/day from advertising revenue.
What is Dcard.tw estimated value?
• Estimated value of Dcard.tw is $4,179,188.77.
What IP addresses does Dcard.tw resolve to?
• Dcard.tw resolves to the IP addresses 104.16.204.58.
Where are Dcard.tw servers located in?
• Dcard.tw has servers located in San Francisco, CA, 94107, United States.
About - dcard.tw

What technologies does dcard.tw use?
dcard.tw Profile
Title: Dcard
Description: 廣受年輕人喜愛的 Dcard 是台灣最大的匿名交流平台,舉凡時事話題、感情心情、吃喝玩樂、學習工作等,都有卡友陪你聊!
Keywords: {{og.description}}
Description: 廣受年輕人喜愛的 Dcard 是台灣最大的匿名交流平台,舉凡時事話題、感情心情、吃喝玩樂、學習工作等,都有卡友陪你聊!
Keywords: {{og.description}}
Last update was 23 days ago

This can take up to 60 seconds. Please wait...

This can take up to 60 seconds. Please wait...
*HypeStat.com is not linking to, promoting or affiliated with dcard.tw in any way. Only publicly available statistics data are displayed.
dcard.tw Traffic Summary
0.9M daily visitors
Is this your site?
Verify your site's metrics.
Verify your site's metrics.
- Daily Unique Visitors:
- 912,036
- Monthly Visits:
- 28,729,134
- Pages per Visitor:
- 3.13
- Daily Pageviews:
- 2,854,674
- Monthly Visits (SEMrush):
- 37,066,270
- Monthly Unique Visitors (SEMrush):
- 11,849,031
- Monthly Visits (SimilarWeb):
- 23,293,755
- Alexa Rank:
- 392
- Alexa Reach:
- 0.0185% (of global internet users)
- Avg. visit duration:
- 11:32
- Bounce rate:
- 63.32%
Traffic sources
- Direct:
- 38.78%
- Referral:
- 6.31%
- Search:
- 52.25%
- Social:
- 2.67%
- Paid:
- 0%
Visitors by country
- Users%Pageviews%Rank
- Taiwan 91.7%95.0%13
- Japan 4.9%3.0%10927
- Hong Kong 1.9%0.7%126
- United States 0.5%0.7%10523
- Australia %-3158
- Canada %-6982
- China %-21219
- Germany %-12639
- Ireland %-1355
- Korea, Republic of %-14279
- Macao %-130
- Malaysia %-526
- Singapore %-1304
- United Kingdom %-6446
- Viet Nam %-7958
Where do visitors go on dcard.tw?
- Reach%Pageviews%PerUser
- dcard.tw
- 99.56%99.58%6.2
- imgur.dcard.tw
- 0.32%0.10%2
- ec-report.dcard.tw
- 0.17%0.06%2
- OTHER
- 0%0.26%0
Competitive Data
- Domain:
- dcard.tw
- Rank:
(Rank based on keywords, cost and organic traffic) - 20,506
- Organic Keywords:
(Number of keywords in top 20 Google SERP) - 150,150
- Organic Traffic:
(Number of visitors coming from top 20 search results) - 129,764
- Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords) - $215.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
Backlinks Report
- Total Sites Linking In (Alexa):
- 3,025
- Total Backlinks:
- 2,528
- Follow Links:
- 1,175
- Nofollow Links:
- 1,352
- Referring Domains:
- 258
- Referring IPs:
- 269
- Authority Domain Score:
- 43
Backlinks by country
- Domains
- United States 195
- Japan 16
- France 14
- Germany 8
- Korea, Republic of 7
Backlinks by TLDs
- TLD Distribution
- Domains
- .com
- 90
- .in
- 53
- .net
- 27
- .edu
- 0
- .gov
- 0
Search Engine Indexes
- Google Index:
- 5,460,000
- Bing Index:
- 979,000
- Yahoo Index:
- 946,000
+ Moz Data
- Domain Authority:
- 58
- Page Authority:
- 42
- MozRank:
- 4
+ How much would dcard.tw make?
- Daily Revenue:
- $5,724.88
- Monthly Revenue:
- $171,746.40
- Yearly Revenue:
- $2,089,581.20
Daily earning by country
- PageviewsEarning
- Taiwan 2,711,940$5,152.69
- Japan 85,640$274.05
- United States 19,983$229.20
- Hong Kong 19,983$68.94
- Australia 0$0.00
- Canada 0$0.00
- China 0$0.00
- Germany 0$0.00
- Ireland 0$0.00
- Korea, Republic of 0$0.00
- Macao 0$0.00
- Malaysia 0$0.00
- Singapore 0$0.00
- United Kingdom 0$0.00
- Viet Nam 0$0.00
How much money does dcard.tw lose due to Adblock?
- Daily Revenue Loss:
- $880.80
- Monthly Revenue Loss:
- $26,424.05
- Yearly Revenue Loss:
- $321,492.61
- Daily Pageviews Blocked:
- 442,075
- Monthly Pageviews Blocked:
- 13,262,244
- Yearly Pageviews Blocked:
- 161,357,308
Daily revenue loss by country
- BlockedLost Money
- Taiwan 433,910$824.43
- United States 3,597$41.26
- Japan 2,569$8.22
- Hong Kong 1,998$6.89
- Australia 0$0.00
- Canada 0$0.00
- China 0$0.00
- Germany 0$0.00
- Ireland 0$0.00
- Korea, Republic of 0$0.00
- Macao 0$0.00
- Malaysia 0$0.00
- Singapore 0$0.00
- United Kingdom 0$0.00
- Viet Nam 0$0.00
How much is dcard.tw worth?
- Website Value:
- $4,179,188.77
+ Ad Experience Report
Summary of the ad experience rating of a site for a specific platform.
Desktop summary
- Root domain:
- dcard.tw
- Last Change Time:
(The last time that the site changed status.) - 2020-02-25 00:49:47
- Region:
(The Ad Standard region to which this site has been assigned.) - C
- 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.) - 2020-02-25 00:49:47
- Region:
(The Ad Standard region to which this site has been assigned.) - C
- 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:
- dcard.tw
- Last Change Time:
(The last time that the site changed status.) - 2020-02-25 00:49:47
- 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
+ Where is dcard.tw hosted?
- Server IP:
- 104.16.204.58
- ASN:
- AS13335
- ISP:
- Cloudflare Inc
- Server Location:
- San Francisco
CA
94107
United States, US
Other sites hosted on 104.16.204.58
There are no other sites hosted on this IP+ How fast does dcard.tw load?
- Average Load Time:
- (1128 ms) 71 % of sites are slower
Page Speed (Google PageSpeed Insights) - Desktop
Field Data
Over the last 30 days, the field data shows that this page has a SLOW 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)2.5s
First Input Delay (FID)741ms
Origin Data
All pages served from this origin have an SLOW 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)2.4s
First Input Delay (FID)479ms
Lab Data
First Contentful Paint 1.0 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
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.
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 1.1 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 1,060 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
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 10.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time 3,770 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Estimated Input Latency 600 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.
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 4.9 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 8.2 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
Page Speed (Google PageSpeed Insights) - Mobile
Field Data
Over the last 30 days, the field data shows that this page has a SLOW 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)2.0s
First Input Delay (FID)522ms
Origin Data
All pages served from this origin have an SLOW 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)2.1s
First Input Delay (FID)728ms
Lab Data
JavaScript execution time
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Speed Index 10.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 10.6 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
Minimizes main-thread work
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
First Contentful Paint 2.3 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Diagnostics
Collection of useful page vitals.
Collection of useful page vitals.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 9.3 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 2,100 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
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 12.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
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.
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.
Tasks
Lists the toplevel main thread tasks that executed during page load.
Lists the toplevel main thread tasks that executed during page load.
Estimated Input Latency 650 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.
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 3,720 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
First Contentful Paint (3G) 4378 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
+ Does dcard.tw use compression?
dcard.tw use br compression.
Original size: 449.75 KB
Compressed size: 56.37 KB
File reduced by: 393.39 KB (87%)
Compressed size: 56.37 KB
File reduced by: 393.39 KB (87%)
+ Google Safe Browsing
+ SSL Checker - SSL Certificate Verify
dcard.tw supports HTTPS

Verifying SSL Support. Please wait...
Common Name: Cloudflare Inc ECC CA-3
Organization: Cloudflare, Inc.
Location: US
Issuer: Baltimore CyberTrust Root
Valid from: Jan 27 12:48:08 2020 GMT
Valid until: Dec 31 23:59:59 2024 GMT
Authority: Is a CA
Keysize: 576 Bits
Organization: Cloudflare, Inc.
Location: US
Issuer: Baltimore CyberTrust Root
Valid from: Jan 27 12:48:08 2020 GMT
Valid until: Dec 31 23:59:59 2024 GMT
Authority: Is a CA
Keysize: 576 Bits
+ Verify HTTP/2 Support
dcard.tw supports HTTP/2

Verifying HTTP/2.0 Support. Please wait...
+ Http Header
Date: Fri, 29 Apr 2022 12:26:02 GMT
Transfer-Encoding: chunked
Connection: keep-alive
Cache-Control: max-age=3600
Expires: Fri, 29 Apr 2022 13:26:02 GMT
Location: https://www.dcard.tw/
Set-Cookie: __cf_bm=5Gn68NO0MfIQpjOYCgBo4P7S00e4yvzYJSLESYe2BCM-1651235162-0-AfdI0ODiWToYC/sWN2/ERMCf9+V5BZ9WwYipmr5X4Fp/8Q1dCEJkqTR4lwF6J7OXEW5r0hJ+thwSPyZCus0jx9E=; path=/; expires=Fri, 29-Apr-22 12:56:02 GMT; domain=.dcard.tw; HttpOnly; SameSite=None
Vary: Accept-Encoding
X-Content-Type-Options: nosniff
Server: cloudflare
CF-RAY: 70380612d8792bd4-ORD
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400
HTTP/2 302
date: Fri, 29 Apr 2022 12:26:02 GMT
cache-control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
expires: Thu, 01 Jan 1970 00:00:01 GMT
location: /f
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
set-cookie: __cf_bm=3W6nBBBvyLQvGGn3WcSbOwYjrP_noST3Bth8ek5KzXo-1651235162-0-Afocko1rnRqXESnK1yjknZlMlj4eCMnqBF/0IGOBM2zo4VlZeLvoqK3faXbftUM6c7ykj08vC+TU7evm6nE2JVI=; path=/; expires=Fri, 29-Apr-22 12:56:02 GMT; domain=.dcard.tw; HttpOnly; Secure; SameSite=None
vary: Accept-Encoding
strict-transport-security: max-age=15552000; includeSubDomains; preload
x-content-type-options: nosniff
server: cloudflare
cf-ray: 70380613eedb629f-ORD
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400
HTTP/2 200
date: Fri, 29 Apr 2022 12:26:02 GMT
content-type: text/html; charset=utf-8
dc-trace-id: 74246ad77340729c199e303da742199b
vary: Accept-Encoding
x-frame-options: DENY
cache-control: public, max-age=0, s-maxage=1200
via: 1.1 google
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400
cf-cache-status: HIT
age: 204
last-modified: Fri, 29 Apr 2022 12:22:38 GMT
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
set-cookie: __cf_bm=hq2iG2x8EBEufg8uvvEplu0vhmscz3CSAnSoOTbCwyU-1651235162-0-ASX8Zve9oi4jktHRp2nyZhx0B35SyXM4aqiU+ZtRtvxaFFxKezpZgVrBsbShvwHnHGZvo4H4P8ZmDMCGJ65yeNM=; path=/; expires=Fri, 29-Apr-22 12:56:02 GMT; domain=.dcard.tw; HttpOnly; Secure; SameSite=None
strict-transport-security: max-age=15552000; includeSubDomains; preload
x-content-type-options: nosniff
server: cloudflare
cf-ray: 703806141f2d629f-ORD
content-encoding: br
+ DNS Lookup
Type | Ip | Target | TTL |
HINFO | 3600 | ||
A | 104.16.204.58 | 293 | |
A | 104.16.105.87 | 293 | |
NS | hal.ns.cloudflare.com | 3593 | |
NS | lola.ns.cloudflare.com | 3593 |
+ Whois Lookup
- WhoIs: