Dmm.Co.Jp - Info dmm.co.jp

dmm.co.jp receives about 4,096,233 unique visitors and 42,191,197 (10.30 per visitor) page views per day which should earn about $133,726.26/day from advertising revenue. Estimated site value is $97,620,199.47. According to Alexa Traffic Rank dmm.co.jp is ranked number 418 in the world and 0.0903% of global Internet users visit it. Site is hosted in Tokyo, Tokyo, 190-0031, Japan and links to network IP address 202.6.246.29. This server supports HTTPS and doesn't support HTTP/2.
Loading...

About - dmm.co.jp


Technologies used on Website

Web Servers
Apache
Tag Managers
Google Tag Manager
Analytics
SiteCatalyst

dmm.co.jp Profile

Title: 年齢認証 - FANZA
Description: 成人向けコンテンツを取り扱うアダルト総合サイト。18歳未満の方のアクセスは固くお断りいたします。
Keywords: 成人向けコンテンツを取り扱うアダルト総合サイト。スマートフォン、ケータイにも対応。
Last update was 15 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with dmm.co.jp in any way. Only publicly available statistics data are displayed.

How popular is dmm.co.jp?

4.1M daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
4,096,233
Monthly Unique Visitors:
98,309,592
Pages per Visit:
10.30
Daily Pageviews:
42,191,197
Loading...
Alexa Rank:
418 visit alexa
Alexa Reach:
0.0903%   (of global internet users)
Avg. visit duration:
08:17
Bounce rate:
33.69%
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources

Direct:
53.68%
Referral:
8.64%
Search:
27.97%
Social:
2.04%
Paid:
3.49%

Visitors by country

Users%Pageviews%Rank
Japan 89.6%93.8%33
Taiwan 3.0%1.7%302
China 2.6%0.7%3563
Hong Kong 1.5%1.5%230
Korea, Republic of 1.2%1.2%891
United States 0.7%0.3%12565

Where do visitors go on this site?

Reach%Pageviews%PerUser
dmm.co.jp
88.64%86.16%10.2
games.dmm.co.jp
19.43%3.99%2.1
accounts.dmm.co.jp
13.26%1.48%1.2
cashier.dmm.co.jp
5.11%0.87%1.8
book.dmm.co.jp
4.49%1.55%3.6
dlsoft.dmm.co.jp
3.15%1.45%4.8
pics.dmm.co.jp
2.58%1.83%7.4
agent-livechat.dmm.co.jp
1.76%1.12%6.7
dojin.dmm.co.jp
1.56%0.35%2.4
video.dmm.co.jp
1.52%0.15%1.0
livechat5.dmm.co.jp
0.73%0.07%1
special.dmm.co.jp
0.62%0.06%1.0
help.dmm.co.jp
0.61%0.19%3
point.dmm.co.jp
0.58%0.19%3
pr.dmm.co.jp
0.57%0.07%1
widget-view.dmm.co.jp
0.56%0.05%1
payment.dmm.co.jp
0.53%0.06%1
my.dmm.co.jp
0.35%0.08%2
actress.dmm.co.jp
0.25%0.06%2
OTHER
0%0.23%0

Competitive Data

SEMrush
Domain:
  dmm.co.jp
Rank:
(Rank based on keywords, cost and organic traffic)
  29,445
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  14,376
Organic Traffic:
(Number of visitors coming from top 20 search results)
  75,933
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $149.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:
  88
Page Authority:
  56
MozRank:
  6

+ How socially engaged is dmm.co.jp?

Facebook:
  13
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:
dmm.co.jp
Last Change Time:
(The last time that the site changed status.)
2020-02-25 03:10:10
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 03:10:10
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:
dmm.co.jp
Last Change Time:
(The last time that the site changed status.)
2020-02-25 03:10:10
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 dmm.co.jp can earn?

Daily Revenue:
$133,726.26
Monthly Revenue:
$4,011,787.80
Yearly Revenue:
$48,810,084.90
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
Japan 39,575,343$126,641.10
Hong Kong 632,868$2,183.39
United States 126,574$1,451.80
Taiwan 717,250$1,362.78
Korea, Republic of 506,294$1,174.60
China 295,338$912.60

How much money do dmm.co.jp lose due to Adblock?

Daily Revenue Loss:
$4,662.56
Monthly Revenue Loss:
$139,876.86
Yearly Revenue Loss:
$1,701,835.07
Daily Pageviews Blocked:
1,446,736
Monthly Pageviews Blocked:
43,402,084
Yearly Pageviews Blocked:
528,058,693
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
Japan 1,187,260$3,799.23
United States 22,783$261.32
Hong Kong 63,287$218.34
Taiwan 114,760$218.04
China 38,394$118.64
Korea, Republic of 20,252$46.98

How much is dmm.co.jp worth?

Website Value:
$97,620,199.47

+ Where is dmm.co.jp hosted?

Server IP:
202.6.246.29
ASN:
AS23620 
ISP:
DooGA Co., Ltd. 
Server Location:
Tokyo
Tokyo, 13
190-0031
Japan, JP
 

Other sites hosted on 202.6.246.29

There are no other sites hosted on this IP

+ How fast does dmm.co.jp load?

Average Load Time:
(1839 ms) 48 % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

92
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 68% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 68% 25% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 25% 6% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 6%
First Input Delay (FID)12ms 98% of loads for this page have a fast (<100ms) First Input Delay (FID) 98% 0% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 0% 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.7s 45% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 45% 47% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 47% 6% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 6%
First Input Delay (FID)17ms 98% of loads for this page have a fast (<100ms) First Input Delay (FID) 98% 0% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

Lab Data

Max Potential First Input Delay 50 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.9 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 1.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.9 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.9 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 0.9 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

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

Resource Type
RequestsTransfer Size
Total
32241 KB
Script
17210 KB
Stylesheet
417 KB
Document
25 KB
Image
45 KB
Other
53 KB
Media
00 KB
Font
00 KB
Third-party
21168 KB
Eliminate render-blocking resources - Potential savings of 490 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://www.dmm.co.jp/css/agecheck.css?1558660624
1 KB70
http://www.dmm.co.jp/css/top/pc-top.css?1570691552
2 KB110
http://www.dmm.co.jp/css/www.dmm.co.jp.top.css?1570692025
10 KB190
http://www.dmm.co.jp/js/library/jquery_1_8_3/jquery-1.8.3.min.js?1358679782
41 KB310
http://www.dmm.co.jp/js/localize_welcome.js?1461295284
2 KB110
http://www.dmm.co.jp/js/common/set_tracking.js?1472622208
1 KB110
http://www.dmm.co.jp/js/s_code_dummy.js
0 KB70
http://www.dmm.co.jp/js/mbox.js
8 KB110
https://dmm-extension.com/js/sys-support-dp.js
4 KB230
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://dmm.co.jp/
0 ms499 ms0 KB0 KB301text/html
http://www.dmm.co.jp/
499 ms933 ms5 KB10 KB200text/htmlDocument
https://navismithapis-cdn.com/css/pc/min.css?v=2.4.11
953 ms984 ms4 KB19 KB200text/cssStylesheet
http://www.dmm.co.jp/css/agecheck.css?1558660624
954 ms1275 ms1 KB2 KB200text/cssStylesheet
http://www.dmm.co.jp/css/top/pc-top.css?1570691552
954 ms1444 ms2 KB5 KB200text/cssStylesheet
http://www.dmm.co.jp/css/www.dmm.co.jp.top.css?1570692025
955 ms1275 ms10 KB39 KB200text/cssStylesheet
http://www.dmm.co.jp/js/library/jquery_1_8_3/jquery-1.8.3.min.js?1358679782
955 ms1582 ms41 KB91 KB200application/javascriptScript
http://www.dmm.co.jp/js/localize_welcome.js?1461295284
955 ms1274 ms2 KB4 KB200application/javascriptScript
http://www.dmm.co.jp/js/common/set_tracking.js?1472622208
955 ms1278 ms1 KB4 KB200application/javascriptScript
http://www.dmm.co.jp/js/s_code_dummy.js
955 ms1276 ms0 KB0 KB200application/javascriptScript
http://www.dmm.co.jp/js/mbox.js
956 ms1273 ms8 KB23 KB200application/javascriptScript
https://navismithapis-cdn.com/js/pigeon.js?v=2.4.11
956 ms1028 ms3 KB6 KB200application/javascriptScript
https://dmm-extension.com/js/sys-support-dp.js
957 ms1717 ms4 KB8 KB200application/javascriptScript
http://stats.g.doubleclick.net/dc.js
1635 ms1640 ms17 KB45 KB200text/javascriptScript
https://cdn.ravenjs.com/3.26.4/raven.min.js
1637 ms1668 ms0 KB0 KB-1Script
http://stat.i3.dmm.com/latest/js/dmm.tracking.min.js
1724 ms2074 ms6 KB17 KB200application/javascriptScript
https://www.googletagmanager.com/gtm.js?id=GTM-JLBT
1725 ms1748 ms59 KB320 KB200application/javascriptScript
http://p.dmm.co.jp/p/pf/icon/rainbow.svg
1731 ms2206 ms3 KB3 KB200image/svg+xmlImage
https://www.google-analytics.com/analytics.js
1864 ms1869 ms19 KB45 KB200text/javascriptScript
http://cdn.cxense.com/cx.js
1877 ms2102 ms24 KB101 KB200application/x-javascriptScript
https://www.google-analytics.com/plugins/ua/linkid.js
1883 ms1886 ms1 KB2 KB200text/javascriptScript
https://ampcid.google.com/v1/publisher:getClientId?key=AIzaSyA65lEHUEizIsNtlbNo-l2K18dT680nsaM
1890 ms1927 ms1 KB0 KB200application/jsonXHR
https://www.google-analytics.com/collect?v=1&_v=j82&a=1555766395&t=pageview&_s=1&dl=http%3A%2F%2Fwww.dmm.co.jp%2F&ul=en-us&de=UTF-8&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=aTBAgQAjAAQC~&jid=1929178518&gjid=359223926&cid=750499905.1589506696&tid=UA-48257133-2&_gid=1632384504.1589506696>m=2wg561JLBT&cd1=GTM-JLBT&cd2=pc&cd50=&cd59=&cd55=750499905.1589506696&z=1734642748
1957 ms1960 ms1 KB0 KB200image/gifImage
https://stats.g.doubleclick.net/r/collect?t=dc&aip=1&_r=3&v=1&_v=j82&tid=UA-48257133-2&cid=750499905.1589506696&jid=1929178518&gjid=359223926&_gid=1632384504.1589506696&_u=aTBAgQAjAAQC~&z=377589986
1957 ms1962 ms1 KB0 KB302text/html
https://www.google.com/ads/ga-audiences?v=1&aip=1&t=sr&_r=4&tid=UA-48257133-2&cid=750499905.1589506696&jid=1929178518&_v=j82&z=377589986
1963 ms1991 ms1 KB0 KB200image/gifImage
http://trac.i3.dmm.com/analytics/v0.9
2083 ms2244 ms0 KB0 KB200text/plainXHR
http://cdn.cxense.com/p1.html
2161 ms2301 ms1 KB0 KB200text/htmlDocument
http://trac.i3.dmm.com/analytics/v0.9
2246 ms2418 ms0 KB0 KB200text/plainXHR
http://cdn.cxense.com/cx.js
2314 ms2368 ms24 KB101 KB200application/x-javascriptScript
http://p1cluster.cxense.com/p1.js
2314 ms2357 ms1 KB0 KB200text/javascriptScript
http://comcluster.cxense.com/Repo/rep.gif?ver=1&typ=pgv&rnd=ka7j8wjv43zabjun&acc=0&sid=9222334054942283910&loc=http%3A%2F%2Fwww.dmm.co.jp%2F&ref=&gol=&pgn=<m=1589506696651&new=1&arf=0&tzo=420&res=800x600&dpr=1&col=24&jav=0&bln=en-US&cks=ka7j8wkoaqn593pp&ckp=ka7j8wkrc65r5avv&glb=&chs=UTF-8&wsz=1350x940&fls=0&flv=&cst=2rajvyp1pma932v3jptf0o2r7e
2384 ms2402 ms0 KB0 KB200image/gifImage
https://id.cxense.com/public/user/id?json=%7B%22identities%22%3A%5B%7B%22type%22%3A%22ckp%22%2C%22id%22%3A%22ka7j8wkrc65r5avv%22%7D%2C%7B%22type%22%3A%22lst%22%2C%22id%22%3A%222rajvyp1pma932v3jptf0o2r7e%22%7D%2C%7B%22type%22%3A%22cst%22%2C%22id%22%3A%222rajvyp1pma932v3jptf0o2r7e%22%7D%5D%2C%22siteId%22%3A%229222334054942283910%22%2C%22location%22%3A%22http%3A%2F%2Fwww.dmm.co.jp%2F%22%7D&callback=cXJsonpCBka7j8wrbzf1pevxz
2387 ms2633 ms1 KB0 KB200text/javascriptScript
Serve static assets with an efficient cache policy - 13 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://www.dmm.co.jp/js/mbox.js
0 ms8 KB
https://navismithapis-cdn.com/css/pc/min.css?v=2.4.11
0 ms4 KB
https://dmm-extension.com/js/sys-support-dp.js
0 ms4 KB
http://p.dmm.co.jp/p/pf/icon/rainbow.svg
0 ms3 KB
https://navismithapis-cdn.com/js/pigeon.js?v=2.4.11
0 ms3 KB
http://comcluster.cxense.com/Repo/rep.gif?ver=1&typ=pgv&rnd=ka7j8wjv43zabjun&acc=0&sid=9222334054942283910&loc=http%3A%2F%2Fwww.dmm.co.jp%2F&ref=&gol=&pgn=<m=1589506696651&new=1&arf=0&tzo=420&res=800x600&dpr=1&col=24&jav=0&bln=en-US&cks=ka7j8wkoaqn593pp&ckp=ka7j8wkrc65r5avv&glb=&chs=UTF-8&wsz=1350x940&fls=0&flv=&cst=2rajvyp1pma932v3jptf0o2r7e
0 ms0 KB
http://www.dmm.co.jp/js/s_code_dummy.js
0 ms0 KB
http://cdn.cxense.com/cx.js
3600000 ms24 KB
http://cdn.cxense.com/cx.js
3600000 ms24 KB
http://stat.i3.dmm.com/latest/js/dmm.tracking.min.js
3600000 ms6 KB
https://www.google-analytics.com/plugins/ua/linkid.js
3600000 ms1 KB
https://www.google-analytics.com/analytics.js
7200000 ms19 KB
http://stats.g.doubleclick.net/dc.js
7200000 ms17 KB
Minimize third-party usage - Third-party code blocked the main thread for 0 ms
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 Blocking Time
59 KB0 ms
51 KB0 ms
21 KB0 ms
18 KB0 ms
1 KB0 ms
0 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
964 ms
13 ms
1617 ms
47 ms
1671 ms
24 ms
1745 ms
85 ms
1845 ms
18 ms
1864 ms
35 ms
1904 ms
13 ms
1954 ms
30 ms
2102 ms
9 ms
2134 ms
12 ms
2170 ms
16 ms
2233 ms
13 ms
2329 ms
6 ms
2343 ms
10 ms
2399 ms
12 ms
2661 ms
6 ms
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
121 ms7 ms2 ms
http://www.dmm.co.jp/js/library/jquery_1_8_3/jquery-1.8.3.min.js?1358679782
103 ms27 ms3 ms
https://www.googletagmanager.com/gtm.js?id=GTM-JLBT
57 ms48 ms9 ms
Avoids enormous network payloads - Total size was 241 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://www.googletagmanager.com/gtm.js?id=GTM-JLBT
59 KB
http://www.dmm.co.jp/js/library/jquery_1_8_3/jquery-1.8.3.min.js?1358679782
41 KB
http://cdn.cxense.com/cx.js
24 KB
http://cdn.cxense.com/cx.js
24 KB
https://www.google-analytics.com/analytics.js
19 KB
http://stats.g.doubleclick.net/dc.js
17 KB
http://www.dmm.co.jp/css/www.dmm.co.jp.top.css?1570692025
10 KB
http://www.dmm.co.jp/js/mbox.js
8 KB
http://stat.i3.dmm.com/latest/js/dmm.tracking.min.js
6 KB
http://www.dmm.co.jp/
5 KB
Minimizes main-thread work - 0.4 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
Script Evaluation
210 ms
Style & Layout
87 ms
Other
82 ms
Script Parsing & Compilation
29 ms
Parse HTML & CSS
15 ms
Rendering
4 ms
Avoids an excessive DOM size - 34 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
34
Maximum DOM Depth
9
Maximum Child Elements
11
Avoid multiple page redirects - Potential savings of 190 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://dmm.co.jp/)
0
http://www.dmm.co.jp/
190
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 430 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

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

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. 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 - 9 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.

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

72
0-49 50-89 90-100 i

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)3.6s 68% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 37% 31% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 31% 31% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 31%
First Input Delay (FID)78ms 95% of loads for this page have a fast (<100ms) First Input Delay (FID) 95% 3% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 3% 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.9s 37% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 37% 55% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 55% 6% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 6%
First Input Delay (FID)90ms 98% of loads for this page have a fast (<100ms) First Input Delay (FID) 95% 3% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 3% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

Lab Data

Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 2.6 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 160 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 5.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Estimated Input Latency 30 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) 4887 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Total Blocking Time 330 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 5.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 5.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 Contentful Paint 2.5 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids an excessive DOM size - 34 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
34
Maximum DOM Depth
13
Maximum Child Elements
7
Avoid multiple page redirects - Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://dmm.co.jp/)
0
http://www.dmm.co.jp/
630
Keep request counts low and transfer sizes small - 32 requests • 246 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
32246 KB
Script
16220 KB
Stylesheet
413 KB
Image
56 KB
Document
25 KB
Other
53 KB
Media
00 KB
Font
00 KB
Third-party
23180 KB
Eliminate render-blocking resources - Potential savings of 670 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://www.dmm.co.jp/style/sp/common/agecheck.css?1531981876
1 KB180
http://www.dmm.co.jp/css/top/sp-top.css?1564468984
1 KB330
http://www.dmm.co.jp/style/sp/common/top.css?1574391640
6 KB480
http://www.dmm.co.jp/js/library/jquery_1_8_3/jquery-1.8.3.min.js?1358679782
41 KB930
http://www.dmm.co.jp/js/s_code_dummy.js
0 KB330
http://www.dmm.co.jp/js/mbox.js
8 KB480
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://dmm.co.jp/
0 ms504 ms0 KB0 KB301text/html
http://www.dmm.co.jp/
505 ms1158 ms4 KB9 KB200text/htmlDocument
https://navismithapis-cdn.com/css/sp/min.css?v=2.4.11
1169 ms1893 ms4 KB16 KB200text/cssStylesheet
http://www.dmm.co.jp/style/sp/common/agecheck.css?1531981876
1171 ms1507 ms1 KB2 KB200text/cssStylesheet
http://www.dmm.co.jp/css/top/sp-top.css?1564468984
1171 ms1661 ms1 KB2 KB200text/cssStylesheet
http://www.dmm.co.jp/style/sp/common/top.css?1574391640
1172 ms1699 ms6 KB31 KB200text/cssStylesheet
http://www.dmm.co.jp/js/library/jquery_1_8_3/jquery-1.8.3.min.js?1358679782
1173 ms1813 ms41 KB91 KB200application/javascriptScript
http://www.dmm.co.jp/js/s_code_dummy.js
1174 ms1489 ms0 KB0 KB200application/javascriptScript
http://www.dmm.co.jp/js/mbox.js
1174 ms1492 ms8 KB23 KB200application/javascriptScript
https://navismithapis-cdn.com/js/sp-switch.js?v=2.4.11
1174 ms1288 ms2 KB6 KB200application/javascriptScript
https://navismithapis-cdn.com/js/ajax.js?v=2.4.11
1174 ms1330 ms1 KB1 KB200application/javascriptScript
https://navismithapis-cdn.com/js/pigeon.js?v=2.4.11
1290 ms1426 ms3 KB6 KB200application/javascriptScript
http://stats.g.doubleclick.net/dc.js
1856 ms1860 ms17 KB45 KB200text/javascriptScript
http://stats.g.doubleclick.net/r/__utm.gif?utmwv=5.7.2dc&utms=1&utmn=898947932&utmhn=www.dmm.co.jp&utmcs=UTF-8&utmsr=412x660&utmvp=412x660&utmsc=24-bit&utmul=en-us&utmje=0&utmfl=-&utmhid=1390047282&utmr=-&utmp=%2F&utmht=1589506688284&utmac=UA-26842624-1&utmcc=__utma%3D125690133.1695619903.1589506688.1589506688.1589506688.1%3B%2B__utmz%3D125690133.1589506688.1.1.utmcsr%3D(direct)%7Cutmccn%3D(direct)%7Cutmcmd%3D(none)%3B&utmjid=1227795175&utmredir=3&utmu=qBAAgAAAAAAAAAAAAAAAAAAE~
1893 ms1898 ms0 KB0 KB200image/gifImage
https://cdn.ravenjs.com/3.26.4/raven.min.js
1897 ms1913 ms14 KB37 KB200application/javascriptScript
http://stat.i3.dmm.com/latest/js/dmm.tracking.min.js
1898 ms2247 ms6 KB17 KB200application/javascriptScript
https://www.googletagmanager.com/gtm.js?id=GTM-QGG2
1899 ms1923 ms58 KB324 KB200application/javascriptScript
http://p.dmm.co.jp/p/pf/icon/rainbow.svg
1906 ms2393 ms3 KB3 KB200image/svg+xmlImage
https://www.google-analytics.com/analytics.js
2037 ms2041 ms19 KB45 KB200text/javascriptScript
http://cdn.cxense.com/cx.js
2048 ms2141 ms24 KB101 KB200application/x-javascriptScript
https://www.google-analytics.com/plugins/ua/linkid.js
2053 ms2056 ms1 KB2 KB200text/javascriptScript
https://ampcid.google.com/v1/publisher:getClientId?key=AIzaSyA65lEHUEizIsNtlbNo-l2K18dT680nsaM
2059 ms2098 ms1 KB0 KB200application/jsonXHR
https://www.google-analytics.com/collect?v=1&_v=j82&a=1390047282&t=pageview&_s=1&dl=http%3A%2F%2Fwww.dmm.co.jp%2F&ul=en-us&de=UTF-8&sd=24-bit&sr=412x660&vp=412x660&je=0&_u=aTBAgQAjAAQC~&jid=1884101313&gjid=1385085481&cid=1695619903.1589506688&tid=UA-48257133-2&_gid=855037450.1589506689>m=2wg561QGG2&cd1=GTM-QGG2&cd2=sp&cd50=&cd59=&cd55=1695619903.1589506688&z=2056202663
2119 ms2132 ms1 KB0 KB200image/gifImage
https://stats.g.doubleclick.net/r/collect?t=dc&aip=1&_r=3&v=1&_v=j82&tid=UA-48257133-2&cid=1695619903.1589506688&jid=1884101313&gjid=1385085481&_gid=855037450.1589506689&_u=aTBAgQAjAAQC~&z=1359114471
2119 ms2124 ms1 KB0 KB302text/html
https://www.google.com/ads/ga-audiences?v=1&aip=1&t=sr&_r=4&tid=UA-48257133-2&cid=1695619903.1589506688&jid=1884101313&_v=j82&z=1359114471
2124 ms2133 ms1 KB0 KB200image/gifImage
http://cdn.cxense.com/p1.html
2206 ms2349 ms1 KB0 KB200text/htmlDocument
http://trac.i3.dmm.com/analytics/v0.9
2255 ms2444 ms0 KB0 KB200text/plainXHR
http://cdn.cxense.com/cx.js
2361 ms2380 ms24 KB101 KB200application/x-javascriptScript
http://p1cluster.cxense.com/p1.js
2361 ms2404 ms1 KB0 KB200text/javascriptScript
http://comcluster.cxense.com/Repo/rep.gif?ver=1&typ=pgv&rnd=ka7j8qawkw6zax7b&acc=0&sid=9222334054942283910&loc=http%3A%2F%2Fwww.dmm.co.jp%2F&ref=&gol=&pgn=<m=1589506688553&new=1&arf=0&tzo=420&res=412x660&dpr=2.625&col=24&jav=0&bln=en-US&cks=ka7j8qbqfkkyj6gg&ckp=ka7j8qbxqnamq2u9&glb=&chs=UTF-8&wsz=412x660&fls=0&flv=&cst=14vnoafu9pc5f2088qvo9ez9ze
2407 ms2452 ms0 KB0 KB200image/gifImage
https://id.cxense.com/public/user/id?json=%7B%22identities%22%3A%5B%7B%22type%22%3A%22ckp%22%2C%22id%22%3A%22ka7j8qbxqnamq2u9%22%7D%2C%7B%22type%22%3A%22lst%22%2C%22id%22%3A%2214vnoafu9pc5f2088qvo9ez9ze%22%7D%2C%7B%22type%22%3A%22cst%22%2C%22id%22%3A%2214vnoafu9pc5f2088qvo9ez9ze%22%7D%5D%2C%22siteId%22%3A%229222334054942283910%22%2C%22location%22%3A%22http%3A%2F%2Fwww.dmm.co.jp%2F%22%7D&callback=cXJsonpCBka7j8qhyqwy474as
2410 ms2476 ms1 KB0 KB200text/javascriptScript
http://trac.i3.dmm.com/analytics/v0.9
2446 ms2807 ms0 KB0 KB200text/plainXHR
Serve static assets with an efficient cache policy - 14 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://www.dmm.co.jp/js/mbox.js
0 ms8 KB
https://navismithapis-cdn.com/css/sp/min.css?v=2.4.11
0 ms4 KB
http://p.dmm.co.jp/p/pf/icon/rainbow.svg
0 ms3 KB
https://navismithapis-cdn.com/js/pigeon.js?v=2.4.11
0 ms3 KB
https://navismithapis-cdn.com/js/sp-switch.js?v=2.4.11
0 ms2 KB
https://navismithapis-cdn.com/js/ajax.js?v=2.4.11
0 ms1 KB
http://comcluster.cxense.com/Repo/rep.gif?ver=1&typ=pgv&rnd=ka7j8qawkw6zax7b&acc=0&sid=9222334054942283910&loc=http%3A%2F%2Fwww.dmm.co.jp%2F&ref=&gol=&pgn=<m=1589506688553&new=1&arf=0&tzo=420&res=412x660&dpr=2.625&col=24&jav=0&bln=en-US&cks=ka7j8qbqfkkyj6gg&ckp=ka7j8qbxqnamq2u9&glb=&chs=UTF-8&wsz=412x660&fls=0&flv=&cst=14vnoafu9pc5f2088qvo9ez9ze
0 ms0 KB
http://www.dmm.co.jp/js/s_code_dummy.js
0 ms0 KB
http://cdn.cxense.com/cx.js
3600000 ms24 KB
http://cdn.cxense.com/cx.js
3600000 ms24 KB
http://stat.i3.dmm.com/latest/js/dmm.tracking.min.js
3600000 ms6 KB
https://www.google-analytics.com/plugins/ua/linkid.js
3600000 ms1 KB
https://www.google-analytics.com/analytics.js
7200000 ms19 KB
http://stats.g.doubleclick.net/dc.js
7200000 ms17 KB
Minimize third-party usage - Third-party code blocked the main thread for 190 ms
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 Blocking Time
14 KB97 ms
18 KB55 ms
51 KB36 ms
58 KB0 ms
21 KB0 ms
1 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
1184 ms
7 ms
1843 ms
36 ms
1888 ms
29 ms
1919 ms
78 ms
2004 ms
10 ms
2016 ms
18 ms
2034 ms
32 ms
2072 ms
12 ms
2121 ms
21 ms
2168 ms
12 ms
2204 ms
22 ms
2271 ms
8 ms
2374 ms
5 ms
2408 ms
10 ms
2418 ms
7 ms
2500 ms
6 ms
JavaScript execution time - 0.8 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
http://www.dmm.co.jp/js/library/jquery_1_8_3/jquery-1.8.3.min.js?1358679782
377 ms95 ms11 ms
Other
327 ms23 ms7 ms
https://cdn.ravenjs.com/3.26.4/raven.min.js
255 ms246 ms7 ms
http://cdn.cxense.com/cx.js
186 ms168 ms18 ms
http://stats.g.doubleclick.net/dc.js
113 ms108 ms5 ms
https://www.googletagmanager.com/gtm.js?id=GTM-QGG2
69 ms34 ms35 ms
Avoids enormous network payloads - Total size was 246 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://www.googletagmanager.com/gtm.js?id=GTM-QGG2
58 KB
http://www.dmm.co.jp/js/library/jquery_1_8_3/jquery-1.8.3.min.js?1358679782
41 KB
http://cdn.cxense.com/cx.js
24 KB
http://cdn.cxense.com/cx.js
24 KB
https://www.google-analytics.com/analytics.js
19 KB
http://stats.g.doubleclick.net/dc.js
17 KB
https://cdn.ravenjs.com/3.26.4/raven.min.js
14 KB
http://www.dmm.co.jp/js/mbox.js
8 KB
http://www.dmm.co.jp/style/sp/common/top.css?1574391640
6 KB
http://stat.i3.dmm.com/latest/js/dmm.tracking.min.js
6 KB
Minimizes main-thread work - 1.5 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
Script Evaluation
839 ms
Style & Layout
278 ms
Other
244 ms
Script Parsing & Compilation
110 ms
Parse HTML & CSS
40 ms
Rendering
16 ms
Avoid chaining critical requests - 6 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.

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.

Reduce server response times (TTFB) - Root document took 650 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.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

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

Your page has 3 blocking script resources and 4 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.Remove render-blocking JavaScript:

http://www.dmm.co.jp/js/library/jquery_1_8_3/jquery-1.8.3.min.js?1358679782
http://www.dmm.co.jp/js/s_code_dummy.js
http://www.dmm.co.jp/js/mbox.js
Optimize CSS Delivery of the following:

http://www.dmm.co.jp/style/sp/common/agecheck.css?1531981876
http://www.dmm.co.jp/css/top/sp-top.css?1564468984
http://www.dmm.co.jp/style/sp/common/top.css?1574391640
https://navismithapis-cdn.com/css/sp/min.css?v=2.4.11

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://p.dmm.co.jp/p/pf/icon/rainbow.svg (expiration not specified)
http://www.dmm.co.jp/js/mbox.js (expiration not specified)
http://www.dmm.co.jp/js/s_code_dummy.js (expiration not specified)
https://www.googletagmanager.com/gtm.js?id=GTM-QGG2 (15 minutes)
http://cdn.cxense.com/cx.js (60 minutes)
http://stat.i3.dmm.com/latest/js/dmm.tracking.min.js (60 minutes)
https://www.google-***ytics.com/plugins/ua/linkid.js (60 minutes)
http://stats.g.doubleclick.net/dc.js (2 hours)
https://www.google-***ytics.com/***ytics.js (2 hours)

Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 1.9KiB (61% reduction).

Compressing http://p.dmm.co.jp/p/pf/icon/rainbow.svg could save 1.9KiB (61% reduction).

Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and *** time.

Minify JavaScript for the following resources to reduce their size by 1.8KiB (47% reduction).

Minifying https://navismithapis-cdn.com/js/pigeon.js?v=2.4.11 could save 947B (47% reduction) after compression.
Minifying https://navismithapis-cdn.com/js/sp-switch.js?v=2.4.11 could save 502B (42% reduction) after compression.
Minifying https://navismithapis-cdn.com/js/ajax.js?v=2.4.11 could save 377B (56% reduction) after compression.

Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and p*** times.

Minify HTML for the following resources to reduce their size by 360B (11% reduction).

Minifying http://www.dmm.co.jp/ could save 360B (11% reduction) after compression.
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.
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.
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.
Size tap targets appropriately
All of your page's links/buttons are large enough for a user to easily tap on a touchscreen. Learn more about sizing tap targets appropriately.
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 dmm.co.jp use compression?

dmm.co.jp use gzip compression.
Original size: 10.33 KB
Compressed size: 4.31 KB
File reduced by: 6.02 KB (58%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

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

+ SSL Checker - SSL Certificate Verify

dmm.co.jp supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: *.dmm.co.jp
Organization: DMM.com Co.,Ltd
Location: Minato-ku, Tokyo, JP
Issuer: GlobalSign Organization Validation CA - SHA256 - G2
Valid from: Jun 5 07:11:08 2018 GMT
Valid until: May 31 23:59:59 2020 GMT
Authority: Is not a CA
Keysize:
Common Name: GlobalSign Organization Validation CA - SHA256 - G2
Organization: GlobalSign nv-sa
Location: BE
Issuer: GlobalSign Root CA
Valid from: Feb 20 10:00:00 2014 GMT
Valid until: Feb 20 10:00:00 2024 GMT
Authority: Is a CA
Keysize: 2048 Bits

+ Verify HTTP/2 Support

dmm.co.jp does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Date: Fri, 15 May 2020 01:37:53 GMT
Server: Apache
Pragma: no-cache
Cache-Control: no-cache
Location: http://www.dmm.co.jp
Vary: Accept-Encoding,User-Agent
Content-Encoding: gzip
Content-Length: 20
Connection: close
Content-Type: text/html; charset=UTF-8

HTTP/1.1 200 OK
Date: Fri, 15 May 2020 01:37:53 GMT
Server: Apache
Set-Cookie: ckcy=2; expires=Sat, 15-May-2021 01:37:53 GMT; path=/; domain=dmm.co.jp
Set-Cookie: i3_ab=5022; expires=Wed, 11-Nov-2020 01:37:53 GMT; path=/; domain=dmm.co.jp
Pragma: no-cache
Cache-Control: no-cache
Vary: Accept-Encoding,User-Agent
Content-Encoding: gzip
Content-Length: 4411
Connection: close
Content-Type: text/html; charset=UTF-8

+ DNS Lookup

Type Ip Target TTL
SOA 60
Mname ns0.dmm.co.jp
Rname hostmaster.dmm.co.jp
Serial Number 2019071527
Refresh 7200
Retry 1800
Expire 1209600
Minimum TTL 0
MX secondary-mx.dmm.com 900
MX swiss.dmm.co.jp 900
TXT 900
TXT 900
TXT 900
A 157.112.85.173 30
A 202.6.246.29 30
NS ns5.dmm.co.jp 60
NS ns6.dmm.co.jp 60
NS dns-a.iij.ad.jp 60

+ Whois Lookup

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

whois lookup at whois.jprs.jp...
[ JPRS database provides information on network administration. Its use is ]
[ restricted to network administration purposes. For further information, ]
[ use 'whois -h whois.jprs.jp help'. To suppress Japanese output, add'/e' ]
[ at the end of command, e.g. 'whois -h whois.jprs.jp ***/e'. ]

Domain Information: [ドメイン情報]
a. [ドメイン名] DMM.CO.JP
e. [そしきめい] ごうどうがいしゃでぃーえむえむどっとこむ
f. [組織名] 合同会社DMM.com
g. [Organization] DMM.com LLC
k. [組織種別] 合同会社
l. [Organization Type] Limited Liability Company
m. [登録担当者] TN4***30JP
n. [技術連絡担当者] TM49224JP
p. [ネームサーバ] ns5.dmm.co.jp
p. [ネームサーバ] ns6.dmm.co.jp
p. [ネームサーバ] dns-a.iij.ad.jp
s. [署名鍵]
[状態] Connected (2020/07/31)
[登録年月日] 2006/07/10
[接続年月日] 2006/07/10
[最終更新] 2019/08/01 01:05:43 (JST)
Last update was 15 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with dmm.co.jp in any way. Only publicly available statistics data are displayed.

Recently Analyzed Sites

kursovikof.ru
1 min
kurskprof.ru
2 mins
kursk-komobr.ru
3 mins
kurs-eurocollege.ru
4 mins
swolebay.com
4 mins
kurazhdance.ru
5 mins
funtracerblog.blogspot.com
6 mins
kuponomix.com
6 mins
adi88m.blogspot.com
6 mins
kupitkan.com
7 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!
dmm.co.jp widget