tokyo-hot.com

tokyo-hot.com is SSL secured

Free website and domain report on tokyo-hot.com

Last Updated: 8th September, 2023 Update Now
Overview

Snoop Summary for tokyo-hot.com

This is a free and comprehensive report about tokyo-hot.com. The domain tokyo-hot.com is currently hosted on a server located in United States with the IP address 66.79.166.244, where USD is the local currency and the local language is English. Our records indicate that tokyo-hot.com is privately registered by Domains By Proxy, LLC. Tokyo-hot.com is expected to earn an estimated $40 USD per day from advertising revenue. The sale of tokyo-hot.com would possibly be worth $29,458 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Tokyo-hot.com receives an estimated 9,539 unique visitors every day - a huge amount of traffic! This report was last updated 8th September, 2023.

About tokyo-hot.com

Site Preview:
Title: TOKYO-HOT.COM M ֊}o CIWi
Description: 陵辱、輪姦、中出しがコンセプトの無修正オリジナル徹底陵辱動画を配信しいてる東京熱(TOKYOHOT)はアダルトコンテンツを含みますので、18歳未満の方はご利用できません。
Keywords and Tags: adult content, hot, popular, pornography, tokyo, tokyo hot, tokyo hot av, tokyo hot blog, tokyo hot com, tokyo hot n0803, tokyo hot n0978, www tokyo hot com, 動画, 子宮 画像 館, 年齢確認, 東京熱, 無修正, 陵辱, 餌食 牝 中井 杏奈
Related Terms: oploverz tokyo ghoul, tokyo giants, tokyo marui, tokyo subway, tokyo wards, tokyo xxxtube
Fav Icon:
Age: Over 20 years old
Domain Created: 7th May, 2003
Domain Updated: 8th May, 2022
Domain Expires: 7th May, 2024
Review

Snoop Score

3/5 (Great!)

Valuation

$29,458 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 46,757
Alexa Reach: 0.0014%
SEMrush Rank (US): 161,276
SEMrush Authority Score: 64
Moz Domain Authority: 0
Moz Page Authority: 0

Rank By Country

Country Alexa Rank
China Flag China 13,789
Indonesia Flag Indonesia 33,685
Japan Flag Japan 6,777
Singapore Flag Singapore 22,913
Taiwan, Province Of China Flag Taiwan, Province Of China 9,592
United States Flag United States 87,143

Organic vs Paid (Google Ads)

Organic Paid
Keywords: 379 0
Traffic: 9,791 0
Cost: $3,743 USD $0 USD
Traffic

Visitors

Daily Visitors: 9,539
Monthly Visitors: 290,337
Yearly Visitors: 3,481,735
Note: All visitors figures are estimates.

Visitors By Country

Country Visitors (Unique) Percentage
China Flag China Daily: 3,730
Monthly: 113,522
Yearly: 1,361,358
39.1%
Indonesia Flag Indonesia Daily: 134
Monthly: 4,065
Yearly: 48,744
1.4%
Japan Flag Japan Daily: 3,577
Monthly: 108,876
Yearly: 1,305,651
37.5%
Other Daily: 954
Monthly: 29,034
Yearly: 348,174
10%
Singapore Flag Singapore Daily: 76
Monthly: 2,323
Yearly: 27,854
0.8%
Taiwan, Province Of China Flag Taiwan, Province Of China Daily: 506
Monthly: 15,388
Yearly: 184,532
5.3%
United States Flag United States Daily: 572
Monthly: 17,420
Yearly: 208,904
6%
Note: All visitors figures are estimates.
Revenue

Revenue

Daily Revenue: $40 USD
Monthly Revenue: $1,228 USD
Yearly Revenue: $14,724 USD
Note: All revenue figures are estimates.

Revenue By Country

Country Revenue Percentage
China Flag China Daily: $9 USD
Monthly: $262 USD
Yearly: $3,148 USD
21.4%
Indonesia Flag Indonesia Daily: $0 USD
Monthly: $6 USD
Yearly: $74 USD
0.5%
Japan Flag Japan Daily: $4 USD
Monthly: $120 USD
Yearly: $1,441 USD
9.8%
Other Daily: $0 USD
Monthly: $0 USD
Yearly: $0 USD
<0.1%
Singapore Flag Singapore Daily: $0 USD
Monthly: $1 USD
Yearly: $13 USD
0.1%
Taiwan, Province Of China Flag Taiwan, Province Of China Daily: $0 USD
Monthly: $3 USD
Yearly: $34 USD
0.2%
United States Flag United States Daily: $27 USD
Monthly: $835 USD
Yearly: $10,014 USD
68%
Note: All revenue figures are estimates.
SEO

Backlinks Analysis (SEMrush)

Backlinks: 1,299,282
Referring Domains: 2,504
Referring IPs: 1,922
Tokyo-hot.com has 1,299,282 backlinks according to SEMrush. 99% of these backlinks are "dofollow" (follow) links which allow the flow of link equity to pass through, which may improve tokyo-hot.com's search engine rankings. Other links are treated as 'hints' by search engines and may also pass link equity, depending on what search engines decide in each case.
100% of tokyo-hot.com's backlinks are text and image links, which are ideal for SEO. Other backlink types may be unrecognized or ignored by search engines.

Top New Follow Links

1
Source: https://erohika.com/archives/64751
Target: https://my.tokyo-hot.com/product/k1377/

2
Source: http://rom.jpg4.info/tokyohot+%E9%BB%92%E6%9C%A8%E7%9C%9F%E7%94%B1%E7%BE%8E/pic1.html
Target: https://my.cdn.tokyo-hot.com/media/cast/6082/thumbnail.jpg

3
Source: http://rom.jpg4.info/tokyohot+%E9%BB%92%E6%9C%A8%E7%9C%9F%E7%94%B1%E7%BE%8E/pic1.html
Target: http://www.tokyo-hot.com/womb/contents/w0379_mayumi_kuroki/w0379_mayumi_kuroki_2.jpg

4
Source: http://661w222w.com/
Target: https://blog.tokyo-hot.com/cat21/post-1294.html

5
Source: http://661w222w.com/
Target: https://blog.tokyo-hot.com/top/top-430.html

Top Ranking Keywords (US)

1
Keyword: tokyo hot
Ranked Page: https://www.tokyo-hot.com/

2
Keyword: tokyo hot com
Ranked Page: https://www.tokyo-hot.com/

3
Keyword: www tokyo hot com
Ranked Page: https://www.tokyo-hot.com/

4
Keyword: 子宮 画像 館
Ranked Page: http://www.tokyo-hot.com/womb/

5
Keyword: tokyo hot av
Ranked Page: https://www.tokyo-hot.com/

Domain Analysis

Value Length
Domain: tokyo-hot.com 13
Domain Name: tokyo-hot 9
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 1.99 seconds
Load Time Comparison: Faster than 34% of sites

PageSpeed Insights

Avg. (All Categories) 66
Performance 83
Accessibility 54
Best Practices 83
SEO 90
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://my.tokyo-hot.com/
Updated: 7th March, 2023

2.91 seconds
First Contentful Paint (FCP)
50%
28%
22%

0.00 seconds
First Input Delay (FID)
99%
0%
1%

83

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for tokyo-hot.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Time to Interactive — 1.6 s
The time taken for the page to become fully interactive.
Total Blocking Time — 130 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Properly size images
Images can slow down the page's load time. Tokyo-hot.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Tokyo-hot.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Tokyo-hot.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Tokyo-hot.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 11 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Tokyo-hot.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://blog.tokyo-hot.com/static/styles.css
12392
11582
Efficiently encode images — Potential savings of 335 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://my.cdn.tokyo-hot.com/static/images/agetop5.jpg
530211
342586
Serve images in next-gen formats — Potential savings of 433 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://my.cdn.tokyo-hot.com/static/images/agetop5.jpg
530211
443586.35
Enable text compression — Potential savings of 9 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://blog.tokyo-hot.com/static/styles.css
12159
9086
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Tokyo-hot.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://tokyo-hot.com/
190
https://my.tokyo-hot.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Tokyo-hot.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 757 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://my.cdn.tokyo-hot.com/static/images/agetop5.jpg
530578
https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.9.2/jquery-ui.min.js
54009
https://cdnjs.cloudflare.com/ajax/libs/jquery-tools/1.2.7/jquery.tools.min.js
44827
https://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.3/jquery.min.js
30850
https://www.google-analytics.com/analytics.js
20594
https://my.cdn.tokyo-hot.com/static/js/flowplayer.min.js?2022042101
12697
https://blog.tokyo-hot.com/static/styles.css
12392
https://my.cdn.tokyo-hot.com/static/js/slick.min.js?2017122102
10688
https://my.cdn.tokyo-hot.com/static/css/style.css
10086
https://my.cdn.tokyo-hot.com/static/images/logo_s.png
8916
Avoids an excessive DOM size — 74 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
74
Maximum DOM Depth
8
Maximum Child Elements
7
Avoid chaining critical requests — 15 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Tokyo-hot.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.5 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
Unattributable
251.166
1.907
0
https://my.tokyo-hot.com/
244.5
25.433
2.246
https://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.3/jquery.min.js
180.498
167.825
3.19
https://www.google-analytics.com/analytics.js
169.341
163.683
1.523
https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.9.2/jquery-ui.min.js
101.064
92.058
5.791
https://cdnjs.cloudflare.com/ajax/libs/bxslider/4.2.5/jquery.bxslider.min.js
67.084
66.425
0.659
Minimizes main-thread work — 1.1 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
555.815
Other
362.931
Style & Layout
108.592
Parse HTML & CSS
20.296
Script Parsing & Compilation
19.728
Rendering
6.498
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 26 requests • 757 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
26
774880
Image
6
548140
Script
12
193868
Stylesheet
4
27966
Document
1
3577
Other
3
1329
Media
0
0
Font
0
0
Third-party
10
166764
Minimize third-party usage — Third-party code blocked the main thread for 240 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
145098
124.951
21095
111.808
571
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 8 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.google-analytics.com/analytics.js
1464
164
https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.9.2/jquery-ui.min.js
1089
105
https://my.tokyo-hot.com/
420
104
https://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.3/jquery.min.js
794
90
Unattributable
524
76
Unattributable
310
73
Unattributable
240
70
https://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.3/jquery.min.js
1034
55
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of tokyo-hot.com on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Audits

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://tokyo-hot.com/
http/1.1
0
297.3639999982
257
0
301
text/html
https://my.tokyo-hot.com/
http/1.1
297.78599995188
1195.1569998637
3577
8060
200
text/html
Document
https://my.cdn.tokyo-hot.com/static/css/style.css
h2
1211.188999936
1598.6750000156
10086
43567
200
text/css
Stylesheet
https://my.cdn.tokyo-hot.com/static/css/movie.css
h2
1213.2409999613
1598.2579998672
4164
22067
200
text/css
Stylesheet
https://my.cdn.tokyo-hot.com/static/css/colorbox.css
h2
1213.3990000002
1596.9359998126
1324
3218
200
text/css
Stylesheet
https://blog.tokyo-hot.com/static/styles.css
http/1.1
1214.2560000066
2004.3389999773
12392
12159
200
text/css
Stylesheet
https://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.3/jquery.min.js
h2
1216.3289999589
1403.6139999516
30850
93636
200
application/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.9.2/jquery-ui.min.js
h2
1216.541999951
1399.9220000114
54009
237802
200
application/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/jquery-tools/1.2.7/jquery.tools.min.js
h2
1216.7479998898
1401.2019999791
44827
142002
200
application/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/jquery.colorbox/1.6.3/jquery.colorbox-min.js
h2
1293.987999903
1317.7549999673
5216
11924
200
application/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/jquery-cookie/1.4.1/jquery.cookie.min.js
h2
1294.9099999387
1395.9929998964
1604
1300
200
application/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/jquery_lazyload/1.9.3/jquery.lazyload.min.js
h2
1295.0479998253
1400.6260000169
2137
3381
200
application/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/bxslider/4.2.5/jquery.bxslider.min.js
h2
1295.1630000025
1395.5589998513
6455
23631
200
application/javascript
Script
https://my.cdn.tokyo-hot.com/static/js/flowplayer.min.js?2022042101
h2
1295.2579997946
1403.0559998937
12697
34206
200
application/javascript
Script
https://my.cdn.tokyo-hot.com/static/js/jquery.sidr.min.js?2017122102
h2
1295.3659999184
1596.5020000003
1944
3673
200
application/javascript
Script
https://my.cdn.tokyo-hot.com/static/js/slick.min.js?2017122102
h2
1295.466999989
1597.6129998453
10688
42863
200
application/javascript
Script
https://my.cdn.tokyo-hot.com/static/js/share.js?2017122102
h2
1296.503999969
1496.3479998987
2847
6023
200
application/javascript
Script
https://my.cdn.tokyo-hot.com/static/images/logo_s.png
h2
1609.7740000114
1794.6319999173
8916
8486
200
image/png
Image
https://my.cdn.tokyo-hot.com/static/images/enter_en.gif
h2
1801.6419999767
1919.9999999255
2870
2445
200
image/gif
Image
https://my.cdn.tokyo-hot.com/static/images/enter_tw.gif
h2
1922.6119997911
2094.9549998622
2027
1605
200
image/gif
Image
https://my.cdn.tokyo-hot.com/static/images/enter_jp.gif
h2
2013.2859998848
2495.1090000104
2071
1649
200
image/gif
Image
https://my.cdn.tokyo-hot.com/static/images/18kin.png
h2
2100.9199998807
2214.7770000156
1678
1249
200
image/png
Image
https://www.google-analytics.com/analytics.js
h2
2309.5809998922
2317.1129999682
20594
50234
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j99&a=1106235182&t=pageview&_s=1&dl=https%3A%2F%2Fmy.tokyo-hot.com%2F&ul=en-us&de=UTF-8&dt=%E5%B9%B4%E9%BD%A2%E7%A2%BA%E8%AA%8D%20%7C%20Tokyo-Hot%20%E6%9D%B1%E4%BA%AC%E7%86%B1%20%E7%84%A1%E4%BF%AE%E6%AD%A3%E3%82%AA%E3%83%AA%E3%82%B8%E3%83%8A%E3%83%AB%E5%BE%B9%E5%BA%95%E5%87%8C%E8%BE%B1%E5%8B%95%E7%94%BB&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAAABAAAAACAAI~&jid=660489290&gjid=1399748715&cid=458603961.1678174636&tid=UA-36737673-4&_gid=1301611582.1678174636&_r=1&_slc=1&z=174556680
h2
2773.5019999091
2799.0739999805
501
4
200
text/plain
XHR
https://my.cdn.tokyo-hot.com/static/images/agetop5.jpg
h2
2797.764999792
3324.9699999578
530578
530211
200
image/jpeg
Image
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j99&tid=UA-36737673-4&cid=458603961.1678174636&jid=660489290&gjid=1399748715&_gid=1301611582.1678174636&_u=IEBAAAAAAAAAACAAI~&z=1247328892
h2
2805.8539999183
2811.1379998736
571
1
200
text/plain
XHR
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
1202.004
104.341
2008.326
89.792
2100.026
210.249
2310.292
96.331
2407.617
109.889
2520.518
75.837
2610.982
163.961
2775.299
22.653
3328.303
69.654
5322.957
72.571
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

First Contentful Paint — 1.1 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 1.8 s
The timing of the largest text or image that is painted.

Audits

Max Potential First Input Delay — 160 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 1.1 s
The time taken for the primary content of the page to be rendered.

Other

Eliminate render-blocking resources — Potential savings of 540 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Tokyo-hot.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://my.cdn.tokyo-hot.com/static/css/style.css
10086
230
https://blog.tokyo-hot.com/static/styles.css
12392
230
https://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.3/jquery.min.js
30850
270
https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.9.2/jquery-ui.min.js
54009
80
https://cdnjs.cloudflare.com/ajax/libs/jquery-tools/1.2.7/jquery.tools.min.js
44827
80
Reduce unused JavaScript — Potential savings of 76 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.9.2/jquery-ui.min.js
54009
48361
https://cdnjs.cloudflare.com/ajax/libs/jquery-tools/1.2.7/jquery.tools.min.js
44827
29170

Metrics

Speed Index — 2.4 s
The time taken for the page contents to be visibly populated.

Other

Reduce initial server response time — Root document took 900 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://my.tokyo-hot.com/
898.357
Serve static assets with an efficient cache policy — 15 resources found
Tokyo-hot.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://blog.tokyo-hot.com/static/styles.css
0
12392
https://www.google-analytics.com/analytics.js
7200000
20594
https://my.cdn.tokyo-hot.com/static/images/agetop5.jpg
86400000
530578
https://my.cdn.tokyo-hot.com/static/images/logo_s.png
86400000
8916
https://my.cdn.tokyo-hot.com/static/images/18kin.png
86400000
1678
https://my.cdn.tokyo-hot.com/static/js/flowplayer.min.js?2022042101
172800000
12697
https://my.cdn.tokyo-hot.com/static/js/slick.min.js?2017122102
172800000
10688
https://my.cdn.tokyo-hot.com/static/css/style.css
172800000
10086
https://my.cdn.tokyo-hot.com/static/css/movie.css
172800000
4164
https://my.cdn.tokyo-hot.com/static/images/enter_en.gif
172800000
2870
https://my.cdn.tokyo-hot.com/static/js/share.js?2017122102
172800000
2847
https://my.cdn.tokyo-hot.com/static/images/enter_jp.gif
172800000
2071
https://my.cdn.tokyo-hot.com/static/images/enter_tw.gif
172800000
2027
https://my.cdn.tokyo-hot.com/static/js/jquery.sidr.min.js?2017122102
172800000
1944
https://my.cdn.tokyo-hot.com/static/css/colorbox.css
172800000
1324
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://my.cdn.tokyo-hot.com/static/images/enter_en.gif
https://my.cdn.tokyo-hot.com/static/images/enter_tw.gif
https://my.cdn.tokyo-hot.com/static/images/enter_jp.gif
54

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of tokyo-hot.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tokyo-hot.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
83

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that tokyo-hot.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.7.1
jQuery Tools
@VERSION
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://tokyo-hot.com/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 6 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
6
Medium
90

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for tokyo-hot.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of tokyo-hot.com on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
22

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of tokyo-hot.com. This includes details about web app manifests.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of tokyo-hot.com on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 61
Performance 61
Accessibility 54
Best Practices 75
SEO 83
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://my.tokyo-hot.com/
Updated: 7th March, 2023

3.76 seconds
First Contentful Paint (FCP)
44%
19%
37%

0.02 seconds
First Input Delay (FID)
96%
4%
0%

61

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for tokyo-hot.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Total Blocking Time — 100 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 120 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://tokyo-hot.com/
http/1.1
0
228.15700003412
242
0
301
text/html
https://my.tokyo-hot.com/
http/1.1
228.55700005312
1299.4840000756
17357
43086
200
text/html
Document
https://my.cdn.tokyo-hot.com/static/css/style.css
h2
1314.0300000086
1348.4470000258
10089
43567
200
text/css
Stylesheet
https://my.cdn.tokyo-hot.com/static/css/movie.css
h2
1314.6440000273
1499.9390000012
4164
22067
200
text/css
Stylesheet
https://my.cdn.tokyo-hot.com/static/css/colorbox.css
h2
1315.6690000324
1349.2910000496
1327
3218
200
text/css
Stylesheet
https://blog.tokyo-hot.com/static/styles.css
http/1.1
1316.8290000176
1812.6720000291
12392
12159
200
text/css
Stylesheet
https://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.3/jquery.min.js
h2
1317.956999992
1346.4970000787
30844
93636
200
application/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.9.2/jquery-ui.min.js
h2
1318.3150000405
1344.5360000478
54001
237802
200
application/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/jquery-tools/1.2.7/jquery.tools.min.js
h2
1318.4950000141
1343.1830001064
44822
142002
200
application/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/jquery.colorbox/1.6.3/jquery.colorbox-min.js
h2
1319.2920000292
1347.5320000434
5215
11924
200
application/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/jquery-cookie/1.4.1/jquery.cookie.min.js
h2
1319.6300000418
1339.4400000107
1604
1300
200
application/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/jquery_lazyload/1.9.3/jquery.lazyload.min.js
h2
1319.9430000968
1341.1730000516
2137
3381
200
application/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/bxslider/4.2.5/jquery.bxslider.min.js
h2
1320.3530000756
1341.6410000063
6459
23631
200
application/javascript
Script
https://my.cdn.tokyo-hot.com/static/js/flowplayer.min.js?2022042101
h2
1320.7530000946
1354.5410000952
12697
34206
200
application/javascript
Script
https://my.cdn.tokyo-hot.com/static/js/jquery.sidr.min.js?2017122102
h2
1320.9830000997
1486.9860000908
1944
3673
200
application/javascript
Script
https://my.cdn.tokyo-hot.com/static/js/slick.min.js?2017122102
h2
1321.1250000168
1347.1480000298
10689
42863
200
application/javascript
Script
https://my.cdn.tokyo-hot.com/static/js/share.js?2017122102
h2
1321.423000074
1599.5180000318
2844
6023
200
application/javascript
Script
https://my.cdn.tokyo-hot.com/static/images/logo_s.png
h2
1601.7670000438
1625.6280000089
8916
8486
200
image/png
Image
https://my.cdn.tokyo-hot.com/static/images/enter_en.gif
h2
1627.521000104
1798.8970000297
2867
2445
200
image/gif
Image
https://my.cdn.tokyo-hot.com/static/images/enter_tw.gif
h2
1800.9210000746
1828.7640000926
2028
1605
200
image/gif
Image
https://my.cdn.tokyo-hot.com/static/images/enter_jp.gif
h2
1814.2490000464
1836.1380000133
2074
1649
200
image/gif
Image
https://my.cdn.tokyo-hot.com/static/images/18kin.png
h2
1886.1790000228
1908.5729999933
1678
1249
200
image/png
Image
https://www.google-analytics.com/analytics.js
h2
1888.254999998
1893.3270000853
20594
50234
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j99&a=2070273581&t=pageview&_s=1&dl=https%3A%2F%2Fmy.tokyo-hot.com%2F&ul=en-us&de=UTF-8&dt=%E5%B9%B4%E9%BD%A2%E7%A2%BA%E8%AA%8D%20%7C%20Tokyo-Hot%20%E6%9D%B1%E4%BA%AC%E7%86%B1%20%E7%84%A1%E4%BF%AE%E6%AD%A3%E3%82%AA%E3%83%AA%E3%82%B8%E3%83%8A%E3%83%AB%E5%BE%B9%E5%BA%95%E5%87%8C%E8%BE%B1%E5%8B%95%E7%94%BB&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=IEBAAAABAAAAACAAI~&jid=615075617&gjid=1066397120&cid=667226232.1678174677&tid=UA-36737673-4&_gid=1266892423.1678174677&_r=1&_slc=1&z=1471756109
h2
1959.661000059
1963.2480000146
501
4
200
text/plain
XHR
https://js-agent.newrelic.com/async-api.6bb277af-1225.min.js
h2
1961.9490000186
1976.5080000507
1860
2040
200
application/javascript
Script
https://js-agent.newrelic.com/lazy-loader.48127245-1225.min.js
h2
1962.9390001064
1977.360000019
1285
1626
200
application/javascript
Script
https://my.cdn.tokyo-hot.com/static/images/agetop4.jpg
h2
1967.401000089
2798.4590000706
597759
597392
200
image/jpeg
Image
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j99&tid=UA-36737673-4&cid=667226232.1678174677&jid=615075617&gjid=1066397120&_gid=1266892423.1678174677&_u=IEBAAAAAAAAAACAAI~&z=1533229696
h2
1977.9630000703
1982.963000075
571
1
200
text/plain
XHR
https://js-agent.newrelic.com/118.d37755e4-1225.min.js
h2
1982.3630000465
1997.1160000423
4178
8082
200
application/javascript
Script
https://js-agent.newrelic.com/page_view_event-aggregate.29613e65-1225.min.js
h2
1983.3730000537
1998.8020000746
2448
3756
200
application/javascript
Script
https://js-agent.newrelic.com/page_view_timing-aggregate.e791ce32-1225.min.js
h2
1984.0069999918
1999.1820000578
3014
5466
200
application/javascript
Script
https://js-agent.newrelic.com/metrics-aggregate.b4a54ed9-1225.min.js
h2
1984.6360000083
1999.5810000692
1495
1462
200
application/javascript
Script
https://bam.nr-data.net/1/296c359863?a=3586455&v=1225.PROD&to=YldTNRBYVxFUV0MKWVsddxQMWk0LWloYAkZFXlgCA01QDVsaVhNGRhxZDg9cFxRcUUAQDGFdQTcLXE5MUlFD&rst=2008&ck=0&s=dd4d38221f46b66e&ref=https://my.tokyo-hot.com/&ap=278&be=1338&fe=627&dc=568&perf=%7B%22timing%22:%7B%22of%22:1678174674734,%22n%22:0,%22f%22:231,%22dn%22:231,%22dne%22:231,%22c%22:231,%22ce%22:231,%22rq%22:231,%22rp%22:1303,%22rpe%22:1303,%22dl%22:1308,%22di%22:1906,%22ds%22:1906,%22de%22:1929,%22dc%22:1963,%22l%22:1963,%22le%22:1976%7D,%22navigation%22:%7B%7D%7D&fp=1919&fcp=1919&jsonp=NREUM.setToken
http/1.1
2007.7740000561
2190.3090000851
527
49
200
text/javascript
Script
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
1306.126
22.953
1329.621
26.149
1817.703
13.587
1831.328
59.781
1891.121
12.848
1905.949
23.481
1936.157
26.718
1963.163
13.982
2004.171
6.752
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Tokyo-hot.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Tokyo-hot.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Tokyo-hot.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Tokyo-hot.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Tokyo-hot.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Enable text compression — Potential savings of 9 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://blog.tokyo-hot.com/static/styles.css
12159
9086
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Tokyo-hot.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://tokyo-hot.com/
630
https://my.tokyo-hot.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Tokyo-hot.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 850 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://my.cdn.tokyo-hot.com/static/images/agetop4.jpg
597759
https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.9.2/jquery-ui.min.js
54001
https://cdnjs.cloudflare.com/ajax/libs/jquery-tools/1.2.7/jquery.tools.min.js
44822
https://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.3/jquery.min.js
30844
https://www.google-analytics.com/analytics.js
20594
https://my.tokyo-hot.com/
17357
https://my.cdn.tokyo-hot.com/static/js/flowplayer.min.js?2022042101
12697
https://blog.tokyo-hot.com/static/styles.css
12392
https://my.cdn.tokyo-hot.com/static/js/slick.min.js?2017122102
10689
https://my.cdn.tokyo-hot.com/static/css/style.css
10089
Avoids an excessive DOM size — 77 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
77
Maximum DOM Depth
8
Maximum Child Elements
7
Avoid chaining critical requests — 15 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Tokyo-hot.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.6 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://my.tokyo-hot.com/
342.344
116.744
26.956
https://cdnjs.cloudflare.com/ajax/libs/jquery-tools/1.2.7/jquery.tools.min.js
183.408
145.26
11.444
Unattributable
142.556
8.62
0
https://www.google-analytics.com/analytics.js
119.492
105.72
5.348
https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.9.2/jquery-ui.min.js
106.276
73.032
21.796
https://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.3/jquery.min.js
88.612
59.36
8.32
Minimizes main-thread work — 1.1 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
596.208
Other
261.452
Script Parsing & Compilation
88.628
Style & Layout
85.94
Parse HTML & CSS
73.748
Rendering
16.916
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 33 requests • 850 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
33
870622
Image
6
615322
Script
19
208657
Stylesheet
4
27972
Document
1
17357
Other
3
1314
Media
0
0
Font
0
0
Third-party
17
181555
Minimize third-party usage — Third-party code blocked the main thread for 70 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
21095
49.268
145082
22.096
14807
0
571
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 5 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.9.2/jquery-ui.min.js
4232
120
https://www.google-analytics.com/analytics.js
5432
107
https://my.tokyo-hot.com/
1652
105
https://my.tokyo-hot.com/
1560
92
https://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.3/jquery.min.js
2732
54
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of tokyo-hot.com on mobile screens.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

Time to Interactive — 5.1 s
The time taken for the page to become fully interactive.

Audits

First Meaningful Paint — 3.6 s
The time taken for the primary content of the page to be rendered.

Metrics

First Contentful Paint — 3.6 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 5.9 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 8.0 s
The timing of the largest text or image that is painted.

Other

Eliminate render-blocking resources — Potential savings of 1,700 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Tokyo-hot.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://my.cdn.tokyo-hot.com/static/css/style.css
10089
780
https://my.cdn.tokyo-hot.com/static/css/movie.css
4164
150
https://blog.tokyo-hot.com/static/styles.css
12392
930
https://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.3/jquery.min.js
30844
1080
https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.9.2/jquery-ui.min.js
54001
450
https://cdnjs.cloudflare.com/ajax/libs/jquery-tools/1.2.7/jquery.tools.min.js
44822
300
https://my.cdn.tokyo-hot.com/static/js/flowplayer.min.js?2022042101
12697
150
https://my.cdn.tokyo-hot.com/static/js/slick.min.js?2017122102
10689
300
Reduce unused JavaScript — Potential savings of 73 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.9.2/jquery-ui.min.js
54001
48354
https://cdnjs.cloudflare.com/ajax/libs/jquery-tools/1.2.7/jquery.tools.min.js
44822
26267
Efficiently encode images — Potential savings of 366 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://my.cdn.tokyo-hot.com/static/images/agetop4.jpg
597392
374874
Serve images in next-gen formats — Potential savings of 478 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://my.cdn.tokyo-hot.com/static/images/agetop4.jpg
597392
489883.3
Reduce initial server response time — Root document took 1,070 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://my.tokyo-hot.com/
1071.915
Serve static assets with an efficient cache policy — 22 resources found
Tokyo-hot.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://blog.tokyo-hot.com/static/styles.css
0
12392
https://bam.nr-data.net/1/296c359863?a=3586455&v=1225.PROD&to=YldTNRBYVxFUV0MKWVsddxQMWk0LWloYAkZFXlgCA01QDVsaVhNGRhxZDg9cFxRcUUAQDGFdQTcLXE5MUlFD&rst=2008&ck=0&s=dd4d38221f46b66e&ref=https://my.tokyo-hot.com/&ap=278&be=1338&fe=627&dc=568&perf=%7B%22timing%22:%7B%22of%22:1678174674734,%22n%22:0,%22f%22:231,%22dn%22:231,%22dne%22:231,%22c%22:231,%22ce%22:231,%22rq%22:231,%22rp%22:1303,%22rpe%22:1303,%22dl%22:1308,%22di%22:1906,%22ds%22:1906,%22de%22:1929,%22dc%22:1963,%22l%22:1963,%22le%22:1976%7D,%22navigation%22:%7B%7D%7D&fp=1919&fcp=1919&jsonp=NREUM.setToken
0
527
https://www.google-analytics.com/analytics.js
7200000
20594
https://js-agent.newrelic.com/118.d37755e4-1225.min.js
7200000
4178
https://js-agent.newrelic.com/page_view_timing-aggregate.e791ce32-1225.min.js
7200000
3014
https://js-agent.newrelic.com/page_view_event-aggregate.29613e65-1225.min.js
7200000
2448
https://js-agent.newrelic.com/async-api.6bb277af-1225.min.js
7200000
1860
https://js-agent.newrelic.com/metrics-aggregate.b4a54ed9-1225.min.js
7200000
1495
https://js-agent.newrelic.com/lazy-loader.48127245-1225.min.js
7200000
1285
https://my.cdn.tokyo-hot.com/static/images/agetop4.jpg
86400000
597759
https://my.cdn.tokyo-hot.com/static/images/logo_s.png
86400000
8916
https://my.cdn.tokyo-hot.com/static/images/18kin.png
86400000
1678
https://my.cdn.tokyo-hot.com/static/js/flowplayer.min.js?2022042101
172800000
12697
https://my.cdn.tokyo-hot.com/static/js/slick.min.js?2017122102
172800000
10689
https://my.cdn.tokyo-hot.com/static/css/style.css
172800000
10089
https://my.cdn.tokyo-hot.com/static/css/movie.css
172800000
4164
https://my.cdn.tokyo-hot.com/static/images/enter_en.gif
172800000
2867
https://my.cdn.tokyo-hot.com/static/js/share.js?2017122102
172800000
2844
https://my.cdn.tokyo-hot.com/static/images/enter_jp.gif
172800000
2074
https://my.cdn.tokyo-hot.com/static/images/enter_tw.gif
172800000
2028
https://my.cdn.tokyo-hot.com/static/js/jquery.sidr.min.js?2017122102
172800000
1944
https://my.cdn.tokyo-hot.com/static/css/colorbox.css
172800000
1327
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://my.cdn.tokyo-hot.com/static/images/enter_en.gif
https://my.cdn.tokyo-hot.com/static/images/enter_tw.gif
https://my.cdn.tokyo-hot.com/static/images/enter_jp.gif
Registers an `unload` listener
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Source
First Contentful Paint (3G) — 7202 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
54

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of tokyo-hot.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tokyo-hot.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
75

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that tokyo-hot.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.7.1
jQuery Tools
@VERSION
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://tokyo-hot.com/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 6 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
6
Medium

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://my.cdn.tokyo-hot.com/static/images/enter_en.gif
340 x 98
280 x 81
680 x 196
https://my.cdn.tokyo-hot.com/static/images/logo_s.png
320 x 60
354 x 66
640 x 120
83

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for tokyo-hot.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of tokyo-hot.com on mobile screens.
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

Mobile Friendly

Document doesn't use legible font sizes — 27.55% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
.warning
72.45%
11.2437px
27.55%
≥ 12px

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
30

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of tokyo-hot.com. This includes details about web app manifests.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of tokyo-hot.com on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 66.79.166.244
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
DCS Pacific Star, LLC
Registration

Domain Registrant

Private Registration: Yes
Name: Registration Private
Organization: Domains By Proxy, LLC
Country: US
City: Tempe
State: Arizona
Post Code: 85284
Email:
Phone: +1.4806242599
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
GoDaddy.com, LLC 23.6.68.27
Security

Visitor Safety

Mature Content: Yes
McAfee WebAdvisor Rating: Unknown
WOT Rating:
WOT Trustworthiness: 84/100
WOT Child Safety: 12/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: *.tokyo-hot.com
Issued By: RapidSSL TLS RSA CA G1
Valid From: 8th July, 2020
Valid To: 6th September, 2022
Subject: CN = *.tokyo-hot.com
Hash: 6c1613e3
Issuer: CN = RapidSSL TLS RSA CA G1
OU = www.digicert.com
O = DigiCert Inc
S = US
Version: 2
Serial Number: 16743427566226728499955043106603121900
Serial Number (Hex): 0C98AAB6D284ACB46649BAB56B2FBCEC
Valid From: 8th July, 2024
Valid To: 6th September, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:0C:DB:6C:82:49:0F:4A:67:0A:B8:14:EE:7A:C4:48:52:88:EB:56:38
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://cdp.rapidssl.com/RapidSSLTLSRSACAG1.crl

Certificate Policies: Policy: 2.16.840.1.114412.1.2
CPS: https://www.digicert.com/CPS
Policy: 2.23.140.1.2.1

Authority Information Access: OCSP - URI:http://status.rapidssl.com
CA Issuers - URI:http://cacerts.rapidssl.com/RapidSSLTLSRSACAG1.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 29:79:BE:F0:9E:39:39:21:F0:56:73:9F:63:A5:77:E5:
BE:57:7D:9C:60:0A:F8:F9:4D:5D:26:5C:25:5D:C7:84
Timestamp : Jul 8 18:48:21.526 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:D5:FF:68:D9:04:79:5B:FC:52:75:F7:
22:FF:5A:5C:2C:E2:73:46:35:0B:42:94:26:3C:3E:02:
81:48:8A:A2:31:02:20:60:E3:1C:31:81:7A:60:1C:33:
79:16:42:7F:81:84:A1:FA:99:35:3F:C3:8E:97:C5:F9:
9F:E3:47:ED:35:47:6F
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 22:45:45:07:59:55:24:56:96:3F:A1:2F:F1:F7:6D:86:
E0:23:26:63:AD:C0:4B:7F:5D:C6:83:5C:6E:E2:0F:02
Timestamp : Jul 8 18:48:21.574 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:41:7B:4C:17:F1:53:87:3B:47:DD:A6:27:
2C:0A:A8:EA:1D:83:E3:67:5B:F7:39:6C:70:2F:87:91:
E3:85:7E:3C:02:21:00:81:DD:AE:42:3B:99:76:72:01:
44:E6:6B:AF:9C:F7:F0:D1:45:4D:7E:3F:38:57:EA:22:
CD:D2:78:F9:6B:5D:43
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 51:A3:B0:F5:FD:01:79:9C:56:6D:B8:37:78:8F:0C:A4:
7A:CC:1B:27:CB:F7:9E:88:42:9A:0D:FE:D4:8B:05:E5
Timestamp : Jul 8 18:48:21.651 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:81:C7:F0:92:FB:05:18:9D:3A:54:1A:
FD:D0:0D:9F:B2:94:B2:41:A8:3D:62:9D:A9:E3:3E:7D:
4E:5D:39:38:61:02:20:6F:66:65:15:CF:76:B2:1C:D7:
B7:B8:E6:A7:29:C3:EE:69:49:7E:B1:2E:16:46:9C:FD:
9F:87:BF:B4:AC:F9:37
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:tokyo-hot.com
DNS:*.tokyo-hot.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
tokyo-hot.com. 66.79.166.243 IN 600
tokyo-hot.com. 66.79.166.244 IN 600

NS Records

Host Nameserver Class TTL
tokyo-hot.com. ns05.jskyservices.com. IN 3600
tokyo-hot.com. ns03.jskyservices.com. IN 3600
tokyo-hot.com. ns04.jskyservices.com. IN 3600

MX Records

Priority Host Server Class TTL
10 tokyo-hot.com. mx04.jskyservices.com. IN 1800
20 tokyo-hot.com. mx03.jskyservices.com. IN 1800

SOA Records

Domain Name Primary NS Responsible Email TTL
tokyo-hot.com. ns04.jskyservices.com. webmaster.tokyo-hot.com. 7200

TXT Records

Host Value Class TTL
tokyo-hot.com. v=spf1 IN 1200

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx
Date: 12th June, 2021
Content-Type: text/html; charset=utf-8
Content-Length: 30455
Connection: keep-alive
Vary: Accept-Language, Cookie
Content-Language: en
Set-Cookie: *

Whois Lookup

Created: 7th May, 2003
Changed: 8th May, 2022
Expires: 7th May, 2024
Registrar: GoDaddy.com, LLC
Status: clientTransferProhibited
clientUpdateProhibited
clientRenewProhibited
clientDeleteProhibited
Nameservers: ns03.jskyservices.com
ns04.jskyservices.com
ns05.jskyservices.com
Owner Name: Registration Private
Owner Organization: Domains By Proxy, LLC
Owner Street: DomainsByProxy.com
2155 E Warner Rd
Owner Post Code: 85284
Owner City: Tempe
Owner State: Arizona
Owner Country: US
Owner Phone: +1.4806242599
Owner Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=TOKYO-HOT.COM
Admin Name: Registration Private
Admin Organization: Domains By Proxy, LLC
Admin Street: DomainsByProxy.com
2155 E Warner Rd
Admin Post Code: 85284
Admin City: Tempe
Admin State: Arizona
Admin Country: US
Admin Phone: +1.4806242599
Admin Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=TOKYO-HOT.COM
Tech Name: Registration Private
Tech Organization: Domains By Proxy, LLC
Tech Street: DomainsByProxy.com
2155 E Warner Rd
Tech Post Code: 85284
Tech City: Tempe
Tech State: Arizona
Tech Country: US
Tech Phone: +1.4806242599
Tech Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=TOKYO-HOT.COM
Full Whois: Domain Name: TOKYO-HOT.COM
Registry Domain ID: 97619097_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: https://www.godaddy.com
Updated Date: 2022-05-08T09:02:54Z
Creation Date: 2003-05-07T11:16:57Z
Registrar Registration Expiration Date: 2024-05-07T11:16:57Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: abuse@godaddy.com
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Registry Registrant ID: Not Available From Registry
Registrant Name: Registration Private
Registrant Organization: Domains By Proxy, LLC
Registrant Street: DomainsByProxy.com
Registrant Street: 2155 E Warner Rd
Registrant City: Tempe
Registrant State/Province: Arizona
Registrant Postal Code: 85284
Registrant Country: US
Registrant Phone: +1.4806242599
Registrant Phone Ext:
Registrant Fax: +1.4806242598
Registrant Fax Ext:
Registrant Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=TOKYO-HOT.COM
Registry Admin ID: Not Available From Registry
Admin Name: Registration Private
Admin Organization: Domains By Proxy, LLC
Admin Street: DomainsByProxy.com
Admin Street: 2155 E Warner Rd
Admin City: Tempe
Admin State/Province: Arizona
Admin Postal Code: 85284
Admin Country: US
Admin Phone: +1.4806242599
Admin Phone Ext:
Admin Fax: +1.4806242598
Admin Fax Ext:
Admin Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=TOKYO-HOT.COM
Registry Tech ID: Not Available From Registry
Tech Name: Registration Private
Tech Organization: Domains By Proxy, LLC
Tech Street: DomainsByProxy.com
Tech Street: 2155 E Warner Rd
Tech City: Tempe
Tech State/Province: Arizona
Tech Postal Code: 85284
Tech Country: US
Tech Phone: +1.4806242599
Tech Phone Ext:
Tech Fax: +1.4806242598
Tech Fax Ext:
Tech Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=TOKYO-HOT.COM
Name Server: NS05.JSKYSERVICES.COM
Name Server: NS03.JSKYSERVICES.COM
Name Server: NS04.JSKYSERVICES.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2023-03-07T07:37:07Z <<<
For more information on Whois status codes, please visit https://icann.org/epp

TERMS OF USE: The data contained in this registrar's Whois database, while believed by the
registrar to be reliable, is provided "as is" with no guarantee or warranties regarding its
accuracy. This information is provided for the sole purpose of assisting you in obtaining
information about domain name registration records. Any use of this data for any other purpose
is expressly forbidden without the prior written permission of this registrar. By submitting
an inquiry, you agree to these terms and limitations of warranty. In particular, you agree not
to use this data to allow, enable, or otherwise support the dissemination or collection of this
data, in part or in its entirety, for any purpose, such as transmission by e-mail, telephone,
postal mail, facsimile or other means of mass unsolicited, commercial advertising or solicitations
of any kind, including spam. You further agree not to use this data to enable high volume, automated
or robotic electronic processes designed to collect or compile this data for any purpose, including
mining this data for your own personal or commercial purposes. Failure to comply with these terms
may result in termination of access to the Whois database. These terms may be subject to modification
at any time without notice.

Nameservers

Name IP Address
ns03.jskyservices.com 54.241.16.192
ns04.jskyservices.com 138.197.194.182
ns05.jskyservices.com 192.155.82.127
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
$1,231 USD 1/5
$3,249 USD 1/5
0/5
0/5
0/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5

Sites hosted on the same IP address