Tokyosex.Com - Info
tokyosex.com receives about 5 unique visitors and 5 (1.00 per visitor) page views per day which should earn about $0.04/day from advertising revenue. Estimated site value is $17.50. According to Alexa Traffic Rank tokyosex.com is ranked number 22,788,821 in the world and 1.0E-6% of global Internet users visit it. Site is hosted in New York, NY, 10004, United States and links to network IP address 126.96.36.199.
How popular is tokyosex.com?
- Daily Unique Visitors:
- Monthly Unique Visitors:
- Daily Pageviews:
- 5 (1.00 per visitor)
- Alexa Rank:
- 22,788,821 visit alexa
- Alexa Reach:
- 1.0E-6% (Percent of global Internet users)
Visitors by countryCurrently Not Available
Where do visitors go on this site?Currently Not Available
- Organic Keywords:
- Organic Traffic:
- Organic Cost:
- Adwords Keywords:
- Adwords Traffic:
- Adwords Cost:
- Domain Authority:
- Page Authority:
- Total Sites Linking In (Alexa):
- Total Backlinks:
- Follow Links:
- Nofollow Links:
- Referring Domains:
- Referring IPs:
How socially engaged is tokyosex.com?
- Google +:
How much tokyosex.com can earn?
- Website Value:
- Daily Revenue:
- Monthly Revenue:
- Yearly Revenue:
Where is tokyosex.com hosted?
- Server IP:
- Dosarrest Internet Security LTD
- Server Location:
- New York
Other sites hosted on 188.8.131.52There are no other sites hosted on this IP
How fast does tokyosex.com load?
- Average Load Time:
- (2086 ms) 53 % of sites are slower
Page Speed (Google PageSpeed Insights)
Leverage browser cachingSetting 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://184.108.40.206/banners/***/***.jpg(expiration not specified)
http://tokyo***.com/css/caffluid-original.css(expiration not specified)
http://tokyo***.com/css/salesbanner.css(expiration not specified)
http://tokyo***.com/images/fluid/page-bg.png(expiration not specified)
Configure the viewportYour page specifies a fixed-width mobile viewport. Consider using a responsive viewport to allow your page to render properly on all devices.
Configuring a viewport specifying width=device-width instead of width=480 will allow your page to adapt for devices of various widths. This may require additional work if the styling on your page relies on a fixed-width layout.
Optimize imagesProperly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 9.1KiB (30% reduction).
http://220.127.116.11/banners/***/***.jpgcould save 7.3KiB (28% reduction).
http://tokyo***.com/images/fluid/page-bg.pngcould save 1.8KiB (47% reduction).
Minify HTML for the following resources to reduce their size by 777B (20% reduction).
http://tokyo***.com/search_caf.php?uid=tokyo***586f4b3dd2fbb1.29340139&src=fluidoldbg&abp=1could save 777B (20% reduction) after compression.
Minify CSSCompacting 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 689B (24% reduction).
http://tokyo***.com/css/caffluid-original.csscould save 689B (24% reduction) after compression.
Prioritize visible contentYou have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size content to viewportThe contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Size tap targets appropriatelyAll 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.
Avoid pluginsYour 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.
Use legible font sizesThe text on your page is legible. Learn more about using legible font sizes.
Reduce server response timeYour server responded quickly. Learn more about server response time optimization.
Avoid landing page redirectsYour page has no redirects. Learn more about avoiding landing page redirects.
Google Safe Browsing
- Vendor reliability:
- Child safety:
Site Categories (dmoz)Currently Not Available
What sites are related to tokyosex.com?
HTTP/1.1 200 OK
Date: Fri, 06 Jan 2017 07:46:02 GMT
P3P: CP="NON DSP COR ADMa OUR IND UNI COM NAV INT"
DNS LookupCurrently Not Available
- Domain Created:
- Domain Age:
- 18 years 10 months 17 days