Nobody.Jp - Info nobody.jp

nobody.jp receives about 12,725 unique visitors and 21,633 (1.70 per visitor) page views per day which should earn about $51.85/day from advertising revenue. Estimated site value is $37,924.56. According to Alexa Traffic Rank nobody.jp is ranked number 101,541 in the world and 0.00075% of global Internet users visit it. Site is hosted in Japan and links to network IP address 112.140.42.26. This server supports HTTPS and HTTP/2.

About - nobody.jp

nobody.jpドメインであなただけのホームページを作ってみませんか?『NINJA TOOLS』なら無料であなたのホームページを作ることができます。しかもケータイ対応だし、容量無制限だし。
Edit Site Info

Technologies used on Website

Web Servers
OpenResty
Nginx
Reverse Proxy
Nginx
Programming Languages
Lua

nobody.jp Profile

Title: nobody.jp | 忍者ホームページ - 忍者ツールズ
Keywords: nobody.jp,無料ホームページ,ホームページ,ホムペ,NINJA TOOLS
Last update was 8 days ago
loader
This can take up to 60 seconds. Please wait...

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

How popular is nobody.jp?

12.7K daily visitors
Daily Unique Visitors:
12,725
Monthly Unique Visitors:
381,750
Pages per Visit:
1.70
Daily Pageviews:
21,633
Alexa Rank:
101,541 visit alexa
Alexa Reach:
0.00075%   (of global internet users)
Avg. visit duration:
03:55
Bounce rate:
88.98%
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources

Direct:
18.67%
Referral:
43.58%
Search:
36.51%
Social:
1.24%
Paid:
0%

Visitors by country

Users%Pageviews%Rank
Japan 78.9%74.9%11486

Where do visitors go on this site?

Reach%Pageviews%PerUser
baseballmonster.nobody.jp
58.54%55.58%1
OTHER
0%44.42%0

+ Competitive Data

SEMrush
Domain:
  nobody.jp
Rank:
(Rank based on keywords, cost and organic traffic)
  976,652
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  1,995
Organic Traffic:
(Number of visitors coming from top 20 search results)
  739
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $1.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:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is nobody.jp?

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

+ Ad Experience Report

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

Desktop summary

Root domain:
nobody.jp
Region:
(The Ad Standard region to which this site has been assigned.)
Pending
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.)
Not reviewed


Mobile summary

Region:
(The Ad Standard region to which this site has been assigned.)
Pending
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.)
Not reviewed

+ Abusive Experience Report

Root domain:
nobody.jp
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.)
Not reviewed

+ How much nobody.jp can earn?

Daily Revenue:
$51.85
Monthly Revenue:
$1,555.50
Yearly Revenue:
$18,925.25
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
Japan 16,203$51.85

How much money do nobody.jp lose due to Adblock?

Daily Revenue Loss:
$1.56
Monthly Revenue Loss:
$46.66
Yearly Revenue Loss:
$567.76
Daily Pageviews Blocked:
486
Monthly Pageviews Blocked:
14,583
Yearly Pageviews Blocked:
177,424
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
Japan 486$1.56

How much is nobody.jp worth?

Website Value:
$37,924.56

+ Where is nobody.jp hosted?

Server IP:
112.140.42.26
ASN:
AS23637 
ISP:
Equinix Jpapan Enterprise K.K. 
Server Location:

Japan, JP
 

Other sites hosted on 112.140.42.26

+ How fast does nobody.jp load?

Average Load Time:
(208 ms) 99 % 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 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.

Origin Data

All pages served from this origin have an 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.

Lab Data

Speed Index 0.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.3 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.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 0.3 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 0.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids enormous network payloads - Total size was 56 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://nobody.jp/btn_make.jpg
15 KB
http://v2st.shinobi.jp/asumi/arms/1.17.46
10 KB
http://x9.shinobi.jp/fire?cid=453134574&v=1.1.0.a0368610078aceb7672f6eec96c60b52
10 KB
http://v2st.shinobi.jp/asumi/resource/248
4 KB
http://x7.namekuji.jp/ufo/112276400
3 KB
http://nobody.jp/logo.gif
1 KB
http://nobody.jp/
1 KB
http://nobody.jp/style.css
1 KB
http://st.shinobi.jp/img/services/admaxdsp/static/javascripts/trac.js
1 KB
https://sync.im-apps.net/imid/set?cid=10338&tid=sid&uid=e573fe44-62dc-4ad3-832c-417af653b158
1 KB
Minimizes main-thread work - 0.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Other
70 ms
Style & Layout
59 ms
Script Evaluation
58 ms
Parse HTML & CSS
11 ms
Script Parsing & Compilation
9 ms
Rendering
4 ms
Avoids an excessive DOM size - 33 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
33
Maximum DOM Depth
6
Maximum Child Elements
11
Keep request counts low and transfer sizes small - 32 requests • 56 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
3256 KB
Script
1329 KB
Image
1122 KB
Other
63 KB
Document
11 KB
Stylesheet
11 KB
Media
00 KB
Font
00 KB
Third-party
2838 KB
Eliminate render-blocking resources - Potential savings of 40 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://nobody.jp/style.css
1 KB70
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://nobody.jp/
0 ms164 ms1 KB2 KB200text/htmlDocument
http://nobody.jp/style.css
187 ms354 ms1 KB2 KB200text/cssStylesheet
http://nobody.jp/logo.gif
187 ms347 ms1 KB1 KB200image/gifImage
http://nobody.jp/btn_make.jpg
188 ms681 ms15 KB14 KB200image/jpegImage
http://x7.namekuji.jp/ufo/112276400
189 ms507 ms3 KB7 KB200application/x-javascriptScript
http://x7.namekuji.jp/Zen?1122764NaaabaaabaaaaaaaaaaaaaabeuaxcayJ00__B
515 ms678 ms0 KB0 KB200application/x-javascriptScript
http://asumi.shinobi.jp/encount
516 ms685 ms0 KB0 KB200text/plainScript
http://st.shinobi.jp/img/services/admaxdsp/static/javascripts/trac.js
518 ms838 ms1 KB1 KB200application/javascriptScript
http://asumi.shinobi.jp/assault?f=102
518 ms836 ms0 KB0 KB200application/javascriptScript
http://asumi.shinobi.jp/assault?f=233
519 ms834 ms0 KB0 KB200application/javascriptScript
http://v2st.shinobi.jp/asumi/arms/1.17.46
689 ms866 ms10 KB43 KB200application/javascriptScript
http://sync.shinobi.jp/v2/sync/ne?r=http%3A%2F%2Fadm.shinobi.jp%2Fchikayo%2Fcookiesync%3Fuid%3D
841 ms1164 ms1 KB0 KB302
http://sync.shinobi.jp/v2/sync/ne?r=http%3A%2F%2Fasumi.shinobi.jp%2Fsync%3Fid%3D
873 ms1040 ms0 KB0 KB302
http://asumi.shinobi.jp/fire?f=102
876 ms1145 ms1 KB1 KB200application/javascriptScript
http://asumi.shinobi.jp/sync?id=9dfec950-8aef-4cc4-8e79-e5f4b6a49cd5
1040 ms1208 ms0 KB0 KB200image/gifImage
http://asumi.shinobi.jp/track?r=348&a=pick&_=1570862576175
1157 ms1321 ms0 KB0 KB200image/gifImage
http://v2st.shinobi.jp/asumi/resource/248
1157 ms1364 ms4 KB3 KB200image/gifImage
http://asumi.shinobi.jp/track?r=348&a=imp&_=1570862576177
1157 ms1317 ms0 KB0 KB200image/gifImage
http://asumi.shinobi.jp/track?r=348&a=view&_=1570862576180
1158 ms1322 ms0 KB0 KB200image/gifImage
http://asumi.shinobi.jp/fire?f=233
1162 ms1328 ms0 KB0 KB200application/javascriptScript
http://adm.shinobi.jp/chikayo/cookiesync?uid=e573fe44-62dc-4ad3-832c-417af653b158
1164 ms1480 ms0 KB0 KB200image/gifImage
http://x9.shinobi.jp/ufo/453134574
1334 ms1650 ms0 KB0 KB302text/html
http://x9.shinobi.jp/fire?cid=453134574&v=1.1.0.a0368610078aceb7672f6eec96c60b52
1651 ms1972 ms10 KB24 KB200application/javascriptScript
http://sync.shinobi.jp/v2/sync/control
1986 ms2151 ms1 KB0 KB200text/javascriptScript
http://sync.shinobi.jp/v2/sync/ne?t=js&r=http%3A%2F%2Fx9.shinobi.jp%2Ftrack%3Fcid%3D453134574%26ref%3D%26time%3D1570862577016%26x9uid%3Dd8430bc5-9d4a-4d54-9240-07240ca11095%26picked%3D%257B%2522453134574-174%2522%253A%257B%257D%257D%26callback%3D__chikayo__.callback.C_1570862577011_8002%26uid%3D
1992 ms2154 ms1 KB0 KB302
http://sync.shinobi.jp/v2/sync/multi?1570862577178
2154 ms2470 ms1 KB0 KB200text/javascriptScript
http://x9.shinobi.jp/track?cid=453134574&ref=&time=1570862577016&x9uid=d8430bc5-9d4a-4d54-9240-07240ca11095&picked=%7B%22453134574-174%22%3A%7B%7D%7D&callback=__chikayo__.callback.C_1570862577011_8002&uid=e573fe44-62dc-4ad3-832c-417af653b158
2155 ms2316 ms0 KB0 KB200application/javascriptScript
http://sync.shinobi.jp/v2/sync/multi/1001?1570862577497
2474 ms2637 ms0 KB0 KB302
http://sync.shinobi.jp/v2/sync/multi/1762?1570862577497
2474 ms2654 ms0 KB0 KB302
http://sync.shinobi.jp/v2/sync/multi/2736?1570862577497
2474 ms2802 ms0 KB0 KB200image/gifImage
https://adm.shinobi.jp/chikayo/cookiesync?uid=e573fe44-62dc-4ad3-832c-417af653b158
2637 ms2799 ms0 KB0 KB200image/gifImage
https://sync.im-apps.net/imid/set?cid=10338&tid=sid&uid=e573fe44-62dc-4ad3-832c-417af653b158
2654 ms3306 ms1 KB0 KB200image/gifImage
Uses efficient cache policy on static assets - 21 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://nobody.jp/btn_make.jpg
0 ms15 KB
http://x7.namekuji.jp/ufo/112276400
0 ms3 KB
http://nobody.jp/logo.gif
0 ms1 KB
http://nobody.jp/style.css
0 ms1 KB
http://asumi.shinobi.jp/fire?f=102
0 ms1 KB
http://x7.namekuji.jp/Zen?1122764NaaabaaabaaaaaaaaaaaaaabeuaxcayJ00__B
0 ms0 KB
http://asumi.shinobi.jp/assault?f=102
0 ms0 KB
http://asumi.shinobi.jp/assault?f=233
0 ms0 KB
http://asumi.shinobi.jp/sync?id=9dfec950-8aef-4cc4-8e79-e5f4b6a49cd5
0 ms0 KB
http://adm.shinobi.jp/chikayo/cookiesync?uid=e573fe44-62dc-4ad3-832c-417af653b158
0 ms0 KB
https://adm.shinobi.jp/chikayo/cookiesync?uid=e573fe44-62dc-4ad3-832c-417af653b158
0 ms0 KB
http://x9.shinobi.jp/track?cid=453134574&ref=&time=1570862577016&x9uid=d8430bc5-9d4a-4d54-9240-07240ca11095&picked=%7B%22453134574-174%22%3A%7B%7D%7D&callback=__chikayo__.callback.C_1570862577011_8002&uid=e573fe44-62dc-4ad3-832c-417af653b158
0 ms0 KB
http://asumi.shinobi.jp/encount
0 ms0 KB
http://asumi.shinobi.jp/track?r=348&a=imp&_=1570862576177
0 ms0 KB
http://asumi.shinobi.jp/track?r=348&a=pick&_=1570862576175
0 ms0 KB
http://asumi.shinobi.jp/track?r=348&a=view&_=1570862576180
0 ms0 KB
http://asumi.shinobi.jp/fire?f=233
0 ms0 KB
http://sync.shinobi.jp/v2/sync/multi/2736?1570862577497
0 ms0 KB
http://st.shinobi.jp/img/services/admaxdsp/static/javascripts/trac.js
259200000 ms1 KB
http://v2st.shinobi.jp/asumi/arms/1.17.46
2592000000 ms10 KB
http://v2st.shinobi.jp/asumi/resource/248
2592000000 ms4 KB
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
1 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
196 ms
17 ms
215 ms
5 ms
385 ms
59 ms
538 ms
12 ms
1176 ms
12 ms
1358 ms
6 ms
2003 ms
19 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
144 ms4 ms1 ms
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 - 4 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 160 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.


Page Speed (Google PageSpeed Insights) - Mobile

82
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a 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.

Origin Data

All pages served from this origin have an 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.

Lab Data

Max Potential First Input Delay 100 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 6.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Estimated Input Latency 20 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 130 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
First Contentful Paint (3G) 1560 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Speed Index 2.3 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 0.8 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.8 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.

Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://nobody.jp/
0 ms343 ms1 KB2 KB200text/htmlDocument
http://nobody.jp/style.css
357 ms570 ms1 KB2 KB200text/cssStylesheet
http://nobody.jp/logo.gif
358 ms1041 ms1 KB1 KB200image/gifImage
http://nobody.jp/btn_make.jpg
358 ms792 ms15 KB14 KB200image/jpegImage
http://x7.namekuji.jp/ufo/112276400
359 ms695 ms2 KB3 KB200application/x-javascriptScript
http://x7.namekuji.jp/Zen?1122764Naaabaaabaaaaaaaaaaaaaaapwazkayo00__B
701 ms1231 ms0 KB0 KB200application/x-javascriptScript
http://asumi.shinobi.jp/encount
702 ms1021 ms0 KB0 KB200text/plainScript
http://asumi.shinobi.jp/fire?f=439
703 ms1020 ms2 KB7 KB200application/javascriptScript
http://v2st.shinobi.jp/asumi/arms/1.17.46
1023 ms1202 ms10 KB43 KB200application/javascriptScript
http://sync.shinobi.jp/v2/sync/ne?r=http%3A%2F%2Fasumi.shinobi.jp%2Fsync%3Fid%3D
1209 ms1537 ms1 KB0 KB302
http://static.criteo.net/js/ld/publishertag.js
1220 ms1243 ms27 KB86 KB200text/javascriptScript
http://asumi.shinobi.jp/track?r=1822&a=pick&_=1570862567183
1223 ms1383 ms0 KB0 KB200image/gifImage
http://asumi.shinobi.jp/track?r=1822&a=imp&_=1570862567187
1224 ms1538 ms0 KB0 KB200image/gifImage
http://asumi.shinobi.jp/track?r=1822&a=view&_=1570862567188
1224 ms1551 ms0 KB0 KB200image/gifImage
https://bidder.criteo.com/cdb?ptv=74&profileId=184&cb=16492488092
1273 ms1292 ms0 KB0 KB204text/plainXHR
https://static.criteo.net/images/pixel.gif?ch=1
1308 ms1325 ms0 KB0 KB200image/gifImage
https://static.criteo.net/images/pixel.gif?ch=2
1308 ms1325 ms0 KB0 KB200image/gifImage
http://j.microad.net/js/compass.js
1322 ms1579 ms0 KB0 KB302
http://asumi.shinobi.jp/track?r=1822&a=passback&_=1570862567276
1326 ms1650 ms0 KB0 KB200image/gifImage
http://asumi.shinobi.jp/track?r=3083&a=pick&_=1570862567277
1326 ms1487 ms0 KB0 KB200image/gifImage
http://asumi.shinobi.jp/track?r=3083&a=imp&_=1570862567289
1326 ms1647 ms0 KB0 KB200image/gifImage
http://asumi.shinobi.jp/track?r=3083&a=view&_=1570862567290
1326 ms1700 ms0 KB0 KB200image/gifImage
http://asumi.shinobi.jp/sync?id=ec9f8eda-b066-4d12-a20e-1d31a1876234
1538 ms1734 ms0 KB0 KB200image/gifImage
http://jgl.microad.net/js/compass.js
1579 ms1654 ms19 KB82 KB200application/javascriptScript
https://cache.send.microadinc.com/js/cookie_loader.html
1677 ms2331 ms1 KB2 KB200text/htmlDocument
https://s-rtb.send.microadinc.com/ad?spot=bba23cb10c8a5d84060ca8f0d1d04008&cb=microadCompass.AdRequestor.callback&url=http%3A%2F%2Fnobody.jp%2F&referrer=http%3A%2F%2Fnobody.jp%2F&cbt=4c31ad157b10cc016dbeb490da
1677 ms2356 ms2 KB2 KB200text/javascriptScript
https://gum.criteo.com/sync?c=46&r=2&j=handleData
2344 ms2361 ms0 KB0 KB200text/javascriptScript
http://microad-d.openx.net/mw/1.0/jstag
2374 ms2498 ms17 KB47 KB200text/javascriptScript
https://ssp.send.microadinc.com/ic?ep=4XaF16A4vl4BBf2BN7HMhIoLRUKhfLIhVZxvAO_kkA16IVhs3AMRwHv6PvrMF9Emi3DEYrpFea2w1oEMHr4i_5wOjHKaPM02r9VxSWQHAQQ6kh73XZNNHx743GvTGC2RvAaNwP520uflQ9hnwizId-vUwYnUx8kIJr4m74GbzyXM
2376 ms3045 ms0 KB0 KB200image/gifImage
http://aid.send.microad.jp/g/pc/asr
2376 ms2701 ms1 KB0 KB200image/gifImage
http://microad-d.openx.net/mw/1.0/acj?ai=106b692b-7399-4fbf-becb-332494096261&o=7861007874&callback=OX_7861007874&ju=http%3A//nobody.jp/&jr=&auid=540838448&dims=&adxy=&res=412x660x24&plg=pm&ch=UTF-8&tz=420&ws=0x0&ifr=1&tws=981x1570&vmt=1&mt=1
2517 ms2595 ms1 KB0 KB302
http://microad-d.openx.net/mw/1.0/acj?cc=1&ai=106b692b-7399-4fbf-becb-332494096261&o=7861007874&callback=OX_7861007874&ju=http%3A//nobody.jp/&jr=&auid=540838448&dims=&adxy=&res=412x660x24&plg=pm&ch=UTF-8&tz=420&ws=0x0&ifr=1&tws=981x1570&vmt=1&mt=1
2596 ms2666 ms2 KB1 KB200application/jsonScript
https://js.ad-stir.com/js/adstir.js
2682 ms2766 ms21 KB79 KB200text/javascriptScript
http://ad.ad-stir.com/ad?app_id=MEDIA-576942b8&ad_spot_no=6&locale=en&ut=1570862568833&topframe=0&origin=http%3A%2F%2Fnobody.jp%2F&sw=412&sh=660&dpr=2.625&novideo=0&topurl=1&callback=AdstirCB8816379860A5312259186
2776 ms2945 ms0 KB0 KB200application/jsonScript
http://us-u.openx.net/w/1.0/pd?plm=10&ph=464022e2-4b47-43d2-8758-dcad4ae1fd07
2953 ms3027 ms1 KB1 KB200text/htmlDocument
http://pixel.advertising.com/ups/55981/sync?_origin=1&gdpr=0&uid=e404b588-3eb1-02a1-20cd-6b0a6e9f5f27
3039 ms3076 ms0 KB0 KB302
http://pixel-sync.sitescout.com/dmp/pixelSync?nid=4&gdpr=0
3039 ms3173 ms0 KB0 KB302
https://rtb.openx.net/sync/dds
3040 ms3080 ms1 KB0 KB302
http://rtb.openx.net/sync/yahoo?gdpr=0
3040 ms3080 ms1 KB0 KB302
http://sync.mathtag.com/sync/img?mt_exid=5&redir=http%3A%2F%2Fus-u.openx.net%2Fw%2F1.0%2Fsd%3Fid%3D536872786%26val%3D%5BMM_UUID%5D
3040 ms3108 ms1 KB0 KB302image/gif
https://ad.turn.com/r/cs?pid=9&gdpr=0
3040 ms3058 ms0 KB0 KB302
https://sync-tm.everesttech.net/upi/pid/ny75r2x0?redir=https%3A%2F%2Fus-u.openx.net%2Fw%2F1.0%2Fsd%3Fid%3D537148856%26val%3D%24%7BTM_USER_ID%7D
3040 ms3059 ms1 KB0 KB302
http://pr-bh.ybp.yahoo.com/sync/openx/5e075045-7677-aaa1-423d-bcf5066b6607?gdpr=0
3041 ms3102 ms0 KB0 KB200image/gifImage
http://match.adsrvr.org/track/cmf/openx?oxid=cac03601-e6db-38e8-73ea-aa00f93cab4e&gdpr=0
3041 ms3211 ms1 KB0 KB302text/html
https://cm.g.doubleclick.net/pixel?google_nid=openx&google_cm&google_sc
3041 ms3057 ms1 KB0 KB302text/html
https://cm.g.doubleclick.net/pixel?google_nid=openx&google_cm=&google_sc=&google_tc=
3057 ms3064 ms1 KB0 KB302text/html
https://us-u.openx.net/w/1.0/sd?id=537073061&val=3530140700691563208&gdpr=0&gdpr_consent=
3059 ms3132 ms0 KB0 KB200image/gifImage
https://sync-tm.everesttech.net/ct/upi/pid/ny75r2x0?redir=https%3A%2F%2Fus-u.openx.net%2Fw%2F1.0%2Fsd%3Fid%3D537148856%26val%3D%24%7BTM_USER_ID%7D&_test=XaF16QAAAH2qokzT
3059 ms3076 ms0 KB0 KB302
https://us-u.openx.net/w/1.0/sd?id=537072991&val=CAESEO9PuvI1dn6E5mB6eSZ22SY&google_cver=1
3065 ms3143 ms0 KB0 KB200image/gifImage
http://pixel.advertising.com/ups/55981/sync?_origin=1&gdpr=0&uid=e404b588-3eb1-02a1-20cd-6b0a6e9f5f27&verify=true
3076 ms3095 ms0 KB0 KB302
https://us-u.openx.net/w/1.0/sd?id=537148856&val=XaF16QAAAH2qokzT&_test=XaF16QAAAH2qokzT
3076 ms3154 ms0 KB0 KB200image/gifImage
https://cm.g.doubleclick.net/pixel?google_nid=open&google_hm=FZa8PU9dgcaVnua3KiWR9A==&ox_sc=1&ox_init=1
3080 ms3090 ms1 KB0 KB302text/html
https://ads.yahoo.com/cms/v1?nwid=10001117459&eid=b83c9f9b-235f-00df-3758-4b822cadd7ac&sigv=1&esig=1~08bdad24184475912e0fb509bf15aa7719c53732&gdpr=0
3081 ms3142 ms1 KB0 KB302
https://rtb.openx.net/sync/dds?ox_sc=1&ox_init=1
3090 ms3129 ms0 KB0 KB200image/gifImage
http://ups.analytics.yahoo.com/ups/55981/sync?_origin=1&gdpr=0&uid=e404b588-3eb1-02a1-20cd-6b0a6e9f5f27&apid=UP81aeda28-ecbb-11e9-b795-0a2b93bf66fc
3095 ms3128 ms0 KB0 KB302
http://sync.mathtag.com/sync/img?mt_exid=5&redir=http%3A%2F%2Fus-u.openx.net%2Fw%2F1.0%2Fsd%3Fid%3D536872786%26val%3D%5BMM_UUID%5D&mm_bnc&mm_bct&UUID=c8715da1-6e45-4900-bf5d-b7c159cb0075
3108 ms3150 ms1 KB0 KB302image/gif
http://ups.analytics.yahoo.com/ups/55981/sync?_origin=1&gdpr=0&uid=e404b588-3eb1-02a1-20cd-6b0a6e9f5f27&apid=UP81aeda28-ecbb-11e9-b795-0a2b93bf66fc&verify=true
3128 ms3159 ms1 KB0 KB204text/plainImage
https://cookiex.ngd.yahoo.com/ack?xid=X8oYC8SPv4bha_nHL.BHZNaC&eid=b83c9f9b-235f-00df-3758-4b822cadd7ac&gdpr=0
3142 ms3310 ms1 KB0 KB200Image
http://us-u.openx.net/w/1.0/sd?id=536872786&val=c8715da1-6e45-4900-bf5d-b7c159cb0075
3150 ms3225 ms0 KB0 KB200image/gifImage
http://pixel-sync.sitescout.com/dmp/pixelSync?cookieQ=1&nid=4&gdpr=0
3173 ms3335 ms1 KB0 KB302
http://match.adsrvr.org/track/cmb/openx?oxid=cac03601-e6db-38e8-73ea-aa00f93cab4e&gdpr=0
3211 ms3380 ms1 KB0 KB302text/html
http://us-u.openx.net/w/1.0/sd?id=537072977&val=41cb3964-76a8-4bf1-8c92-557b566eb16b
3335 ms3411 ms0 KB0 KB200image/gifImage
http://us-u.openx.net/w/1.0/sd?id=537072971&val=3f956e7a-3217-40b0-8d3b-bbc2cfb10f57&ttd_puid=cac03601-e6db-38e8-73ea-aa00f93cab4e
3380 ms3456 ms1 KB0 KB200image/gifImage
https://gum.criteo.com/syncframe?topUrl=nobody.jp
3473 ms3494 ms5 KB11 KB200text/htmlDocument
https://gum.criteo.com/sid/json?origin=publishertag&domain=nobody.jp&topUrl=nobody.jp&lwid=b8edda17-2ad4-4d35-a3ed-609831bae98a&pm=2&cw=1
3511 ms3529 ms1 KB0 KB200application/jsonFetch
Serve static assets with an efficient cache policy - 24 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://nobody.jp/btn_make.jpg
0 ms15 KB
http://asumi.shinobi.jp/fire?f=439
0 ms2 KB
https://s-rtb.send.microadinc.com/ad?spot=bba23cb10c8a5d84060ca8f0d1d04008&cb=microadCompass.AdRequestor.callback&url=http%3A%2F%2Fnobody.jp%2F&referrer=http%3A%2F%2Fnobody.jp%2F&cbt=4c31ad157b10cc016dbeb490da
0 ms2 KB
http://x7.namekuji.jp/ufo/112276400
0 ms2 KB
http://nobody.jp/logo.gif
0 ms1 KB
http://nobody.jp/style.css
0 ms1 KB
https://cookiex.ngd.yahoo.com/ack?xid=X8oYC8SPv4bha_nHL.BHZNaC&eid=b83c9f9b-235f-00df-3758-4b822cadd7ac&gdpr=0
0 ms1 KB
http://aid.send.microad.jp/g/pc/asr
0 ms1 KB
http://x7.namekuji.jp/Zen?1122764Naaabaaabaaaaaaaaaaaaaaapwazkayo00__B
0 ms0 KB
https://ssp.send.microadinc.com/ic?ep=4XaF16A4vl4BBf2BN7HMhIoLRUKhfLIhVZxvAO_kkA16IVhs3AMRwHv6PvrMF9Emi3DEYrpFea2w1oEMHr4i_5wOjHKaPM02r9VxSWQHAQQ6kh73XZNNHx743GvTGC2RvAaNwP520uflQ9hnwizId-vUwYnUx8kIJr4m74GbzyXM
0 ms0 KB
http://asumi.shinobi.jp/sync?id=ec9f8eda-b066-4d12-a20e-1d31a1876234
0 ms0 KB
http://asumi.shinobi.jp/encount
0 ms0 KB
http://asumi.shinobi.jp/track?r=1822&a=imp&_=1570862567187
0 ms0 KB
http://asumi.shinobi.jp/track?r=1822&a=passback&_=1570862567276
0 ms0 KB
http://asumi.shinobi.jp/track?r=1822&a=pick&_=1570862567183
0 ms0 KB
http://asumi.shinobi.jp/track?r=1822&a=view&_=1570862567188
0 ms0 KB
http://asumi.shinobi.jp/track?r=3083&a=imp&_=1570862567289
0 ms0 KB
http://asumi.shinobi.jp/track?r=3083&a=pick&_=1570862567277
0 ms0 KB
http://asumi.shinobi.jp/track?r=3083&a=view&_=1570862567290
0 ms0 KB
https://js.ad-stir.com/js/adstir.js
3600000 ms21 KB
http://microad-d.openx.net/mw/1.0/jstag
3600000 ms17 KB
http://static.criteo.net/js/ld/publishertag.js
86400000 ms27 KB
http://jgl.microad.net/js/compass.js
381595000 ms19 KB
http://v2st.shinobi.jp/asumi/arms/1.17.46
2592000000 ms10 KB
Third-Party usage - Third-party code blocked the main thread for 40 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
33 KB39 ms
25 KB2 ms
3 KB0 ms
3 KB0 ms
1 KB0 ms
1 KB0 ms
1 KB0 ms
1 KB0 ms
1 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
377 ms
10 ms
603 ms
56 ms
727 ms
8 ms
1246 ms
10 ms
1279 ms
25 ms
1325 ms
16 ms
1341 ms
17 ms
1690 ms
20 ms
2365 ms
7 ms
2388 ms
21 ms
2533 ms
17 ms
2699 ms
16 ms
2801 ms
6 ms
2977 ms
6 ms
3061 ms
7 ms
3489 ms
14 ms
3527 ms
6 ms
3570 ms
5 ms
JavaScript execution time - 0.6 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
859 ms95 ms13 ms
http://static.criteo.net/js/ld/publishertag.js
211 ms196 ms12 ms
http://v2st.shinobi.jp/asumi/arms/1.17.46
83 ms50 ms20 ms
http://microad-d.openx.net/mw/1.0/jstag
80 ms74 ms5 ms
https://s-rtb.send.microadinc.com/ad?spot=bba23cb10c8a5d84060ca8f0d1d04008&cb=microadCompass.AdRequestor.callback&url=http%3A%2F%2Fnobody.jp%2F&referrer=http%3A%2F%2Fnobody.jp%2F&cbt=4c31ad157b10cc016dbeb490da
76 ms60 ms7 ms
http://microad-d.openx.net/mw/1.0/acj?cc=1&ai=106b692b-7399-4fbf-becb-332494096261&o=7861007874&callback=OX_7861007874&ju=http%3A//nobody.jp/&jr=&auid=540838448&dims=&adxy=&res=412x660x24&plg=pm&ch=UTF-8&tz=420&ws=0x0&ifr=1&tws=981x1570&vmt=1&mt=1
59 ms49 ms4 ms
Avoids enormous network payloads - Total size was 151 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://static.criteo.net/js/ld/publishertag.js
27 KB
https://js.ad-stir.com/js/adstir.js
21 KB
http://jgl.microad.net/js/compass.js
19 KB
http://microad-d.openx.net/mw/1.0/jstag
17 KB
http://nobody.jp/btn_make.jpg
15 KB
http://v2st.shinobi.jp/asumi/arms/1.17.46
10 KB
https://gum.criteo.com/syncframe?topUrl=nobody.jp
5 KB
http://asumi.shinobi.jp/fire?f=439
2 KB
https://s-rtb.send.microadinc.com/ad?spot=bba23cb10c8a5d84060ca8f0d1d04008&cb=microadCompass.AdRequestor.callback&url=http%3A%2F%2Fnobody.jp%2F&referrer=http%3A%2F%2Fnobody.jp%2F&cbt=4c31ad157b10cc016dbeb490da
2 KB
http://microad-d.openx.net/mw/1.0/acj?cc=1&ai=106b692b-7399-4fbf-becb-332494096261&o=7861007874&callback=OX_7861007874&ju=http%3A//nobody.jp/&jr=&auid=540838448&dims=&adxy=&res=412x660x24&plg=pm&ch=UTF-8&tz=420&ws=0x0&ifr=1&tws=981x1570&vmt=1&mt=1
2 KB
Minimizes main-thread work - 1.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Script Evaluation
677 ms
Other
447 ms
Style & Layout
246 ms
Script Parsing & Compilation
94 ms
Parse HTML & CSS
80 ms
Rendering
23 ms
Garbage Collection
3 ms
Avoids an excessive DOM size - 32 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
32
Maximum DOM Depth
5
Maximum Child Elements
12
Keep request counts low and transfer sizes small - 65 requests • 151 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
65151 KB
Script
13104 KB
Image
2424 KB
Other
2313 KB
Document
49 KB
Stylesheet
11 KB
Media
00 KB
Font
00 KB
Third-party
61133 KB
Eliminate render-blocking resources - Potential savings of 70 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://nobody.jp/style.css
1 KB180
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 - 3 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 340 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Configure the viewport

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

Configure a viewport for this page.

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://nobody.jp/style.css

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://aid.send.microad.jp/g/pc/asr (expiration not specified)
http://asumi.shinobi.jp/encount (expiration not specified)
http://nobody.jp/btn_make.jpg (expiration not specified)
http://nobody.jp/logo.gif (expiration not specified)
http://nobody.jp/style.css (expiration not specified)
http://x7.namekuji.jp/ufo/112276400 (expiration not specified)
http://microad-d.openx.net/mw/1.0/jstag (60 minutes)
https://js.ad-stir.com/js/adstir.js (60 minutes)

Use legible font sizes

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

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

「無名の人」とは? renders only 5 pixels tall (12 CSS pixels) .
例文:あー彼、無名の人だから呼ばなくていいよ。 and 1 others render only 5 pixels tall (12 CSS pixels) .
忍者ツールズの『忍者ホームペ…ができます。しかも無料です。 renders only 5 pixels tall (12 CSS pixels) .

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 4.5KiB (57% reduction).

Compressing https://image6.pubmatic.com/AdServer/PugMaster?kdntuid=1&rnd=14881141&p=157492&s=0&a=0&ptask=ALL&np=0&fp=0&mpc=0&spug=1&coppa=0&gdpr=0&gdpr_consent=&sec=1 could save 2.2KiB (67% reduction).
Compressing https://s-rtb.send.microadinc.com/ad?spot=bba23cb10c8a5d84060ca8f0d1d04008&cb=microadCompass.AdRequestor.callback&url=http%3A%2F%2Fnobody.jp%2F&referrer=http%3A%2F%2Fnobody.jp%2F&cbt=210af30afc4092016dbeb46b2f could save 1.1KiB (51% reduction).
Compressing http://microad-d.openx.net/mw/1.0/acj?cc=1&ai=a3d2397b-89b0-4175-896d-3ea1f2b0960f&o=1488114113&callback=OX_1488114113&ju=http%3A//nobody.jp/&jr=&auid=540838448&dims=&adxy=&res=412x732x24&plg=pm&ch=UTF-8&tz=420&ws=320x100&ifr=1&tws=981x1742&vmt=1&mt=1 could save 688B (51% reduction).
Compressing http://us-u.openx.net/w/1.0/pd?plm=10&ph=464022e2-4b47-43d2-8758-dcad4ae1fd07 could save 445B (47% reduction).

Optimize images

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

Optimize the following images to reduce their size by 3.6KiB (26% reduction).

Compressing http://nobody.jp/btn_make.jpg could save 3.6KiB (26% reduction).

Minify CSS

Compacting CSS code can save many bytes of data and speed up download and p*** times.

Minify CSS for the following resources to reduce their size by 247B (29% reduction).

Minifying http://nobody.jp/style.css could save 247B (29% reduction) after compression.

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 230B (18% reduction).

Minifying http://microad-d.openx.net/mw/1.0/acj?cc=1&ai=a3d2397b-89b0-4175-896d-3ea1f2b0960f&o=1488114113&callback=OX_1488114113&ju=http%3A//nobody.jp/&jr=&auid=540838448&dims=&adxy=&res=412x732x24&plg=pm&ch=UTF-8&tz=420&ws=320x100&ifr=1&tws=981x1742&vmt=1&mt=1 could save 230B (18% reduction).
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
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.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does nobody.jp use compression?

nobody.jp use gzip compression.
Original size: 1.97 KB
Compressed size: 1014 B
File reduced by: 1003 B (49%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  67
Vendor reliability:
  67
Privacy:
  67
Child safety:
  81

+ SSL Checker - SSL Certificate Verify

nobody.jp supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: *.nobody.jp
Organization:
Location:
Issuer: Let's Encrypt Authority X3
Valid from: Sep 27 01:13:26 2019 GMT
Valid until: Dec 26 01:13:26 2019 GMT
Authority:
Keysize:

+ Verify HTTP/2 Support

nobody.jp supports HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Server: openresty
Date: Sat, 12 Oct 2019 06:42:30 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: keep-alive
Content-Encoding: gzip

+ DNS Lookup

Currently Not Available

+ 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: [ドメイン情報]
[Domain Name] NOBODY.JP

[登録者名] 忍者ツールズ株式会社
[Registrant] Ninja Tools Inc.

[Name Server] ns01.idcfcloud.com
[Name Server] ns02.idcfcloud.com
[Name Server] ns03.idcfcloud.com
[Signing Key]

[登録年月日] 2010/01/25
[有効期限] 2020/01/31
[状態] Active
[最終更新] 2019/10/10 17:29:03 (JST)

Contact Information: [公開連絡窓口]
[名前] Whois情報公開代行サービス by お名前.com
[Name] Whois Privacy Protection Service by onamae.com
[Email] email
[Web Page]
[郵便番号] 150-8512
[住所] 東京都渋谷区
桜丘町 26-1
セルリアンタワー 11階
[Postal Address] Shibuya-ku
26-1 Sakuragaoka-cho
Cerulean Tower 11F
[電話番号] +81.354562560
[FAX番号]
Last update was 8 days ago
loader
This can take up to 60 seconds. Please wait...

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

Recently Analyzed Sites

wr-games.com
19 secs
btcoince.com
44 secs
tow-anime.ga
1 min
webspaceinvader.com
2 mins
sharensplit.com
3 mins
***mhub.com
3 mins
webiartsolutions.com
3 mins
manifestacionmagicapdf.com
3 mins
fwci.biz
4 mins
tvextra.altervista.org
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!
nobody.jp widget