TOMIKAN.JP Website Information

tomikan.jp Website Information

Daily Unique Visits: 870

Daily Page Views: 1,740

Income Per Day: $5

Estimated Value: $1,200

tomikan.jp is registered under .JP top-level domain. Please check other sites in .JP zone.

No name server records were found.

and is probably hosted by CPI-NET KDDI Web Communications Inc., JP. See the full list of other websites hosted by CPI-NET KDDI Web Communications Inc., JP.

The highest website tomikan.jp position in Alexa rank database was 51406 and the lowest rank position was 998073. Current position of tomikan.jp in Alexa rank database is 824084.

Desktop speed score of tomikan.jp (19/100) shows that the page desktop performance can be improved.

Mobile usability score of tomikan.jp (99/100) means that the page is mobile-friendly.

Mobile speed score of tomikan.jp (23/100) shows that the landing page performance on mobile devices is poor and can be improved.

Advertisement

tomikan.jp Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.


tomikan.jp whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.


[ JPRS database provides information on network administration. Its use is ]
[ restricted to network administration purposes. For further information, ]
[ use 'whois -h whois.jprs.jp help'. To suppress Japanese output, add'/e' ]
[ at the end of command, e.g. 'whois -h whois.jprs.jp xxx/e'. ]
Domain Information: [ドメイン情報]
[Domain Name] TOMIKAN.JP

[登録者名] 東御市観光協会
[Registrant] Tomi City Tourist Association

[Name Server] ns6.cpi.ad.jp
[Name Server] ns7.cpi.ad.jp
[Signing Key]

[登録年月日] 2016/05/16
[有効期限] 2024/05/31
[状態] Active
[最終更新] 2023/06/01 01:05:07 (JST)

Contact Information: [公開連絡窓口]
[名前] さくらインターネット
[Name] SAKURA internet Inc.
[Email] nic-staff@sakura.ad.jp
[Web Page]
[郵便番号] 530-0001
[住所] 大阪府大阪市
北区梅田1丁目12番12号
東京建物梅田ビル11階
[Postal Address] Osaka
Osaka
11F,1-12-12,Umeda,Kita-ku
[電話番号] 06-6476-8790
[FAX番号]

tomikan.jp server information

Servers Location

tomikan.jp desktop page speed rank

Last tested: 2017-12-19


Desktop Speed Bad
19/100

tomikan.jp Desktop Speed Test Quick Summary


priority - 185Enable compression

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

Enable compression for the following resources to reduce their transfer size by 1.8MiB (77% reduction).

Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/bg_02.svg could save 520.3KiB (77% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/logo_bg.svg could save 489KiB (77% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/bg_03.svg could save 205.4KiB (76% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/news_icon_01.svg could save 154.2KiB (79% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/app_arrow.svg could save 147.3KiB (76% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/news_icon_02.svg could save 141.5KiB (79% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/bg_01.svg could save 117.4KiB (76% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/logo.svg could save 31.8KiB (73% reduction).

priority - 166Optimize images

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

Optimize the following images to reduce their size by 1.6MiB (73% reduction).

Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/mv_04.jpg could save 570.1KiB (77% reduction).
Compressing and resizing http://tomikan.jp/cms/wp-content/themes/tomicity/img/tumb_04.jpg could save 183.9KiB (95% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/mv_06.jpg could save 156.9KiB (59% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/nousan_banner_sp.jpg could save 120.6KiB (75% reduction).
Compressing and resizing http://tomikan.jp/cms/wp-content/themes/tomicity/img/top/bn_wine.png could save 97.9KiB (65% reduction).
Compressing and resizing http://tomikan.jp/cms/wp-content/themes/tomicity/img/top/raiden_tumb.png could save 96.3KiB (70% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/nousan_banner.jpg could save 57.1KiB (74% reduction).
Compressing and resizing http://tomikan.jp/cms/wp-content/themes/tomicity/img/city_tomi.jpg could save 56.9KiB (89% reduction).
Compressing and resizing http://tomikan.jp/cms/wp-content/themes/tomicity/img/tumb_06.jpg could save 45.2KiB (86% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/sanbanner.jpg could save 39.9KiB (71% reduction).
Compressing and resizing http://tomikan.jp/cms/wp-content/themes/tomicity/img/kotohira_bn.png could save 36KiB (70% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/takamine.jpg could save 30.1KiB (61% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/IPD.jpg could save 24.4KiB (63% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/Mimaki_bn01.jpg could save 19.7KiB (60% reduction).
Compressing and resizing http://tomikan.jp/cms/wp-content/themes/tomicity/img/top/bn_tomi-koyo.png could save 19.2KiB (70% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/pr_06.jpg could save 7KiB (63% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/pr_07.jpg could save 6.4KiB (68% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/pr_09.jpg could save 6.4KiB (65% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/pr_01.jpg could save 6.2KiB (63% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/pr_02.jpg could save 5.5KiB (60% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/pr_10.jpg could save 5.5KiB (65% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/pr_08.jpg could save 5.2KiB (65% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/pr_04.jpg could save 5.2KiB (66% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/pr_03.jpg could save 5.1KiB (61% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/pr_05.jpg could save 3.5KiB (60% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/app_01.jpg could save 3.1KiB (68% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/app_02.jpg could save 2.7KiB (64% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/reco_title_bg.png could save 1.1KiB (25% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/reco_title_bg02.png could save 1.1KiB (24% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/pagetop.png could save 1KiB (18% reduction).

priority - 9Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://tomikan.jp/cms/wp-content/themes/tomicity/img/app_arrow.svg (expiration not specified)
http://tomikan.jp/cms/wp-content/themes/tomicity/img/bg_01.svg (expiration not specified)
http://tomikan.jp/cms/wp-content/themes/tomicity/img/bg_02.svg (expiration not specified)
http://tomikan.jp/cms/wp-content/themes/tomicity/img/bg_03.svg (expiration not specified)
http://tomikan.jp/cms/wp-content/themes/tomicity/img/logo.svg (expiration not specified)
http://tomikan.jp/cms/wp-content/themes/tomicity/img/logo_bg.svg (expiration not specified)
http://tomikan.jp/cms/wp-content/themes/tomicity/img/news_icon_01.svg (expiration not specified)
http://tomikan.jp/cms/wp-content/themes/tomicity/img/news_icon_02.svg (expiration not specified)
http://maps.google.com/maps/api/js?libraries=geome…&language=ja&ver=4.5.1 (30 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
http://tomikan.jp/cms/wp-content/plugins/contact-f…s/styles.css?ver=4.3.3 (12 hours)
http://tomikan.jp/cms/wp-content/plugins/contact-f…ddon.min.css?ver=4.5.1 (12 hours)
http://tomikan.jp/cms/wp-content/plugins/contact-f…s/styles.css?ver=4.4.2 (12 hours)
http://tomikan.jp/cms/wp-content/plugins/wp-google…frontend.css?ver=4.5.1 (12 hours)
http://tomikan.jp/cms/wp-content/themes/tomicity/css/base.css (12 hours)
http://tomikan.jp/cms/wp-content/themes/tomicity/css/common.css (12 hours)
http://tomikan.jp/cms/wp-content/themes/tomicity/css/component.css (12 hours)
http://tomikan.jp/cms/wp-content/themes/tomicity/css/slider-pro.css (12 hours)

priority - 3Reduce server response time

priority - 2Minify JavaScript

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

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

Minifying http://tomikan.jp/cms/wp-content/themes/tomicity/js/jquery.sliderPro.js could save 17.6KiB (48% reduction) after compression.
Minifying http://tomikan.jp/cms/wp-content/plugins/contact-f…s/scripts.js?ver=4.3.3 could save 642B (40% reduction) after compression.
Minifying http://tomikan.jp/cms/wp-content/themes/tomicity/js/jquery.dlmenu.js could save 576B (29% reduction) after compression.
Minifying http://tomikan.jp/cms/wp-content/plugins/wp-google…s/js/maps.js?ver=4.5.1 could save 449B (11% reduction) after compression.
Minifying http://tomikan.jp/cms/wp-content/plugins/contact-f…derAccess.js?ver=4.5.1 could save 377B (33% reduction) after compression.
Minifying http://tomikan.jp/cms/wp-content/plugins/contact-f…s/scripts.js?ver=4.4.2 could save 322B (11% reduction) after compression.
Minifying http://tomikan.jp/cms/wp-content/themes/tomicity/js/common.js could save 280B (36% reduction) after compression.
Minifying http://tomikan.jp/cms/wp-includes/js/jquery/ui/mouse.min.js?ver=1.11.4 could save 116B (12% reduction) after compression.
Minifying http://ajax.googleapis.com/ajax/libs/jqueryui/1.11…r-ja.min.js?ver=1.11.4 could save 101B (20% reduction) after compression.

priority - 0Minify CSS

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

Minify CSS for the following resources to reduce their size by 2.8KiB (26% reduction).

Minifying http://tomikan.jp/cms/wp-content/themes/tomicity/css/common.css could save 1.5KiB (28% reduction) after compression.
Minifying http://tomikan.jp/cms/wp-content/themes/tomicity/css/component.css could save 459B (21% reduction) after compression.
Minifying http://tomikan.jp/cms/wp-content/themes/tomicity/css/base.css could save 430B (45% reduction) after compression.
Minifying http://tomikan.jp/cms/wp-content/themes/tomicity/css/slider-pro.css could save 401B (20% reduction) after compression.
Minifying http://tomikan.jp/cms/wp-content/plugins/contact-f…ddon.min.css?ver=4.5.1 could save 109B (33% reduction) after compression.

priority - 0Minify HTML

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

Minify HTML for the following resources to reduce their size by 1.7KiB (17% reduction).

Minifying http://tomikan.jp/ could save 1.7KiB (17% reduction) after compression.

tomikan.jp Desktop Resource Breakdown

Total Resources94
Number of Hosts6
Static Resources90
JavaScript Resources27
CSS Resources10

tomikan.jp mobile page speed rank

Last tested: 2017-12-19


Mobile Speed Bad
23/100

tomikan.jp Mobile Speed Test Quick Summary


priority - 135Enable compression

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

Enable compression for the following resources to reduce their transfer size by 1.3MiB (77% reduction).

Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/bg_02.svg could save 520.3KiB (77% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/bg_03.svg could save 205.4KiB (76% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/news_icon_01.svg could save 154.2KiB (79% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/app_arrow.svg could save 147.3KiB (76% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/news_icon_02.svg could save 141.5KiB (79% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/bg_01.svg could save 117.4KiB (76% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/logo.svg could save 31.8KiB (73% reduction).

priority - 134Optimize images

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

Optimize the following images to reduce their size by 1.3MiB (70% reduction).

Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/mv_04.jpg could save 570.1KiB (77% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/mv_06.jpg could save 156.9KiB (59% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/tumb_04.jpg could save 156.4KiB (81% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/nousan_banner_sp.jpg could save 120.6KiB (75% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/nousan_banner.jpg could save 57.1KiB (74% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/sanbanner.jpg could save 39.9KiB (71% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/city_tomi.jpg could save 36.5KiB (57% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/takamine.jpg could save 30.1KiB (61% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/tumb_06.jpg could save 29.9KiB (57% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/IPD.jpg could save 24.4KiB (63% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/Mimaki_bn01.jpg could save 19.7KiB (60% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/pr_06.jpg could save 7KiB (63% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/pr_07.jpg could save 6.4KiB (68% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/pr_09.jpg could save 6.4KiB (65% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/pr_01.jpg could save 6.2KiB (63% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/pr_02.jpg could save 5.5KiB (60% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/pr_10.jpg could save 5.5KiB (65% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/pr_08.jpg could save 5.2KiB (65% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/pr_04.jpg could save 5.2KiB (66% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/pr_03.jpg could save 5.1KiB (61% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/pr_05.jpg could save 3.5KiB (60% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/top/bn_tomi-koyo.png could save 3.4KiB (13% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/app_01.jpg could save 3.1KiB (68% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/app_02.jpg could save 2.7KiB (64% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/reco_title_bg.png could save 1.1KiB (25% reduction).
Compressing http://tomikan.jp/cms/wp-content/themes/tomicity/img/pagetop.png could save 1KiB (18% reduction).

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

Your page has 5 blocking script resources and 9 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

http://tomikan.jp/cms/wp-content/themes/tomicity/js/modernizr.custom.js
http://tomikan.jp/cms/wp-includes/js/jquery/jquery.js?ver=1.12.3
http://tomikan.jp/cms/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.0
http://maps.google.com/maps/api/js?libraries=geome…&language=ja&ver=4.5.1
http://tomikan.jp/cms/wp-content/plugins/wp-google…s/js/maps.js?ver=4.5.1

Optimize CSS Delivery of the following:

http://tomikan.jp/cms/wp-content/themes/tomicity/css/slider-pro.css
http://tomikan.jp/cms/wp-content/themes/tomicity/css/common.css
http://tomikan.jp/cms/wp-content/themes/tomicity/css/base.css
http://tomikan.jp/cms/wp-content/themes/tomicity/css/component.css
http://tomikan.jp/cms/wp-content/plugins/contact-f…s/styles.css?ver=4.4.2
http://ajax.googleapis.com/ajax/libs/jqueryui/1.11…-ui.min.css?ver=1.11.4
http://tomikan.jp/cms/wp-content/plugins/contact-f…ddon.min.css?ver=4.5.1
http://tomikan.jp/cms/wp-content/plugins/contact-f…s/styles.css?ver=4.3.3
http://tomikan.jp/cms/wp-content/plugins/wp-google…frontend.css?ver=4.5.1

priority - 12Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://tomikan.jp/cms/wp-content/themes/tomicity/img/app_arrow.svg (expiration not specified)
http://tomikan.jp/cms/wp-content/themes/tomicity/img/bg_01.svg (expiration not specified)
http://tomikan.jp/cms/wp-content/themes/tomicity/img/bg_02.svg (expiration not specified)
http://tomikan.jp/cms/wp-content/themes/tomicity/img/bg_03.svg (expiration not specified)
http://tomikan.jp/cms/wp-content/themes/tomicity/img/logo.svg (expiration not specified)
http://tomikan.jp/cms/wp-content/themes/tomicity/img/news_icon_01.svg (expiration not specified)
http://tomikan.jp/cms/wp-content/themes/tomicity/img/news_icon_02.svg (expiration not specified)
http://maps.google.com/maps/api/js?libraries=geome…&language=ja&ver=4.5.1 (30 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
http://tomikan.jp/cms/wp-content/plugins/contact-f…s/styles.css?ver=4.3.3 (12 hours)
http://tomikan.jp/cms/wp-content/plugins/contact-f…ddon.min.css?ver=4.5.1 (12 hours)
http://tomikan.jp/cms/wp-content/plugins/contact-f…s/styles.css?ver=4.4.2 (12 hours)
http://tomikan.jp/cms/wp-content/plugins/wp-google…frontend.css?ver=4.5.1 (12 hours)
http://tomikan.jp/cms/wp-content/themes/tomicity/css/base.css (12 hours)
http://tomikan.jp/cms/wp-content/themes/tomicity/css/common.css (12 hours)
http://tomikan.jp/cms/wp-content/themes/tomicity/css/component.css (12 hours)
http://tomikan.jp/cms/wp-content/themes/tomicity/css/slider-pro.css (12 hours)

priority - 4Reduce server response time

priority - 2Minify JavaScript

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

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

Minifying http://tomikan.jp/cms/wp-content/themes/tomicity/js/jquery.sliderPro.js could save 17.6KiB (48% reduction) after compression.
Minifying http://tomikan.jp/cms/wp-content/plugins/contact-f…s/scripts.js?ver=4.3.3 could save 642B (40% reduction) after compression.
Minifying http://tomikan.jp/cms/wp-content/themes/tomicity/js/jquery.dlmenu.js could save 576B (29% reduction) after compression.
Minifying http://tomikan.jp/cms/wp-content/plugins/wp-google…s/js/maps.js?ver=4.5.1 could save 449B (11% reduction) after compression.
Minifying http://tomikan.jp/cms/wp-content/plugins/contact-f…derAccess.js?ver=4.5.1 could save 377B (33% reduction) after compression.
Minifying http://tomikan.jp/cms/wp-content/plugins/contact-f…s/scripts.js?ver=4.4.2 could save 322B (11% reduction) after compression.
Minifying http://tomikan.jp/cms/wp-content/themes/tomicity/js/common.js could save 280B (36% reduction) after compression.
Minifying http://tomikan.jp/cms/wp-includes/js/jquery/ui/mouse.min.js?ver=1.11.4 could save 116B (12% reduction) after compression.
Minifying http://ajax.googleapis.com/ajax/libs/jqueryui/1.11…r-ja.min.js?ver=1.11.4 could save 101B (20% reduction) after compression.

priority - 0Minify CSS

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

Minify CSS for the following resources to reduce their size by 2.8KiB (26% reduction).

Minifying http://tomikan.jp/cms/wp-content/themes/tomicity/css/common.css could save 1.5KiB (28% reduction) after compression.
Minifying http://tomikan.jp/cms/wp-content/themes/tomicity/css/component.css could save 459B (21% reduction) after compression.
Minifying http://tomikan.jp/cms/wp-content/themes/tomicity/css/base.css could save 430B (45% reduction) after compression.
Minifying http://tomikan.jp/cms/wp-content/themes/tomicity/css/slider-pro.css could save 401B (20% reduction) after compression.
Minifying http://tomikan.jp/cms/wp-content/plugins/contact-f…ddon.min.css?ver=4.5.1 could save 109B (33% reduction) after compression.

priority - 0Minify HTML

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

Minify HTML for the following resources to reduce their size by 1.7KiB (17% reduction).

Minifying http://tomikan.jp/ could save 1.7KiB (17% reduction) after compression.

tomikan.jp Mobile Resource Breakdown

Total Resources93
Number of Hosts6
Static Resources88
JavaScript Resources27
CSS Resources10

tomikan.jp mobile page usability

Last tested: 2017-12-19


Mobile Usability Good
99/100

tomikan.jp Mobile Usability Test Quick Summary


priority - 0Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="http://tomikan.jp/genre/eat">食べる</a> is close to 2 other tap targets.

The tap target <div class="sp-arrow sp-previous-arrow"> and 1 others are close to other tap targets.

The tap target <div class="sp-arrow sp-next-arrow"> is close to 1 other tap targets.

The tap target <a href="http://tomikan…2%b3%e3%83%b3/">イベント情報…夜空のフォトコンテスト開催】</a> is close to 1 other tap targets.

tomikan.jp HTML validation

Errors

Using the “meta” element to specify the document-wide default language is obsolete. Consider specifying the language on the root element instead.

Line: 4 Column: 1 - 51
"..."> <head> <meta http-equiv="Content-Language" content="ja" /> <meta..."

Bad value “Content-Style-Type” for attribute “http-equiv” on element “meta”.

Line: 6 Column: 1 - 59
"...utf-8" /> <meta http-equiv="Content-Style-Type" content="text/css" /> <meta..."

Bad value “Content-Script-Type” for attribute “http-equiv” on element “meta”.

Line: 7 Column: 1 - 67
"...t/css" /> <meta http-equiv="Content-Script-Type" content="text/javascript" /> <lin..."

Bad value “https://api.w.org/” for attribute “rel” on element “link”: The string “https://api.w.org/” is not a registered keyword.

Line: 68 Column: 1 - 67
"...</script> <link rel='https://api.w.org/' href='http://tomikan.jp/wp-json/' /> <link..."

“script” element between “head” and “body”.

Line: 74 Column: 1 - 8
"...> </head> <script> (fu..."

Cannot recover after last error. Any further errors will be ignored.

Line: 74 Column: 1 - 8
"...> </head> <script> (fu..."

Warnings

Consider avoiding viewport values that prevent users from resizing documents.

Line: 10 Column: 1 - 108
"...n.ico" /> <meta name="viewport" content="width=device-width, user-scalable=yes, maximum-scale=1.0, minimum-scale=1.0"> <meta..."

tomikan.jp similar domains

Similar domains:
www.tomikan.com
www.tomikan.net
www.tomikan.org
www.tomikan.info
www.tomikan.biz
www.tomikan.us
www.tomikan.mobi
www.omikan.jp
www.tomikan.jp
www.romikan.jp
www.tromikan.jp
www.rtomikan.jp
www.fomikan.jp
www.tfomikan.jp
www.ftomikan.jp
www.gomikan.jp
www.tgomikan.jp
www.gtomikan.jp
www.yomikan.jp
www.tyomikan.jp
www.ytomikan.jp
www.tmikan.jp
www.timikan.jp
www.toimikan.jp
www.tiomikan.jp
www.tkmikan.jp
www.tokmikan.jp
www.tkomikan.jp
www.tlmikan.jp
www.tolmikan.jp
www.tlomikan.jp
www.tpmikan.jp
www.topmikan.jp
www.tpomikan.jp
www.toikan.jp
www.tonikan.jp
www.tomnikan.jp
www.tonmikan.jp
www.tojikan.jp
www.tomjikan.jp
www.tojmikan.jp
www.tokikan.jp
www.tomkikan.jp
www.tomkan.jp
www.tomukan.jp
www.tomiukan.jp
www.tomuikan.jp
www.tomjkan.jp
www.tomijkan.jp
www.tomkkan.jp
www.tomikkan.jp
www.tomokan.jp
www.tomiokan.jp
www.tomoikan.jp
www.tomian.jp
www.tomijan.jp
www.tomikjan.jp
www.tomiian.jp
www.tomikian.jp
www.tomiikan.jp
www.tomiman.jp
www.tomikman.jp
www.tomimkan.jp
www.tomilan.jp
www.tomiklan.jp
www.tomilkan.jp
www.tomioan.jp
www.tomikoan.jp
www.tomikn.jp
www.tomikqn.jp
www.tomikaqn.jp
www.tomikqan.jp
www.tomikwn.jp
www.tomikawn.jp
www.tomikwan.jp
www.tomiksn.jp
www.tomikasn.jp
www.tomiksan.jp
www.tomikzn.jp
www.tomikazn.jp
www.tomikzan.jp
www.tomika.jp
www.tomikab.jp
www.tomikanb.jp
www.tomikabn.jp
www.tomikah.jp
www.tomikanh.jp
www.tomikahn.jp
www.tomikaj.jp
www.tomikanj.jp
www.tomikajn.jp
www.tomikam.jp
www.tomikanm.jp
www.tomikamn.jp

tomikan.jp Ping

Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.


tomikan.jp TRACEROUTE

Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.