DIGLE.TOKYO プレイリスト共有プラットフォーム - DIGLE（ディグル）

  1. Homepage
  2. digle.tokyo

digle.tokyo website information.

digle.tokyo domain name is registered by .TOKYO top-level domain registry. See the other sites registred in .TOKYO domain zone.

No name server records were found.

and probably website digle.tokyo is hosted by WIKIMEDIA - Wikimedia Foundation Inc., US web hosting company. Check the complete list of other most popular websites hosted by WIKIMEDIA - Wikimedia Foundation Inc., US hosting company.

According to Alexa traffic rank the highest website digle.tokyo position was 9702 (in the world). The lowest Alexa rank position was 982182. Now website digle.tokyo ranked in Alexa database as number 546589 (in the world).

Website digle.tokyo Desktop speed measurement score (7/100) is better than the results of 0.97% of other sites shows that the page desktop performance can be improved.

digle.tokyo Mobile usability score (94/100) is better than the results of 36.81% of other sites and means that the page is mobile-friendly.

Mobile speed measurement score of digle.tokyo (6/100) is better than the results of 0.79% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Nov-18-2024 546,589-16,718
Nov-17-2024 529,871-327
Nov-16-2024 529,54411,905
Nov-15-2024 541,449-3,147
Nov-14-2024 538,302-2,936
Nov-13-2024 535,3660
Nov-12-2024 535,3660

Advertisement

digle.tokyo Rank History

Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.


digle.tokyo whois

WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.

digle.tokyo server information

Servers Location

IP Address
Country
Region
City

digle.tokyo desktop page speed rank

Last tested: 2018-06-24

Desktop Speed Bad
7/100

digle.tokyo Desktop Speed Test Quick Summary


priority - 389 Optimize images

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

Optimize the following images to reduce their size by 3.7MiB (89% reduction).

Compressing and resizing https://digle.tokyo/upload/digger_image/9b616a3599…19449f39ad581db63.jpeg could save 1.7MiB (99% reduction).
Compressing and resizing https://digle.tokyo/upload/digger_image/c7289f6e55…9a8141bddca30f1fb.jpeg could save 1,014.5KiB (99% reduction).
Compressing and resizing https://digle.tokyo/upload/digger_image/130ad78a9b…213686c171253955c.jpeg could save 530.9KiB (98% reduction).
Compressing https://platform-lookaside.fbsbx.com/platform/prof…&hash=AeQlXDyFgRlpoNy8 could save 284.2KiB (58% reduction).
Compressing and resizing https://digle.tokyo/upload/digger_image/ac91baea11…abb10015b86c361e5.jpeg could save 107.2KiB (95% reduction).
Compressing and resizing https://digle.tokyo/upload/digger_image/657686a63c…f8422facdd2f0b883.jpeg could save 57.6KiB (86% reduction).
Compressing and resizing https://digle.tokyo/img/jacket-1.jpg could save 26.1KiB (87% reduction).
Compressing https://pl.scdn.co/images/pl/default/b2bdce35d700a…ded849952600ddd0c78845 could save 15.3KiB (37% reduction).
Compressing https://pl.scdn.co/images/pl/default/d5c8067186a86…3a4384d96555434a8cc3df could save 7KiB (22% reduction).
Compressing https://pl.scdn.co/images/pl/default/b7fceaafb8774…2146c520e1cc8c240f2cca could save 5.9KiB (44% reduction).
Compressing https://pl.scdn.co/images/pl/default/537f122a8156e…81d659bbc91c435c2a22fe could save 5.3KiB (23% reduction).
Compressing https://profile-images.scdn.co/images/userprofile/…c9466a38784bcaa6a27d26 could save 4.6KiB (23% reduction).
Compressing https://pl.scdn.co/images/pl/default/e6d03f3da5cbf…b6ce370f4b9fb4b2ba8a37 could save 4KiB (25% reduction).
Compressing https://pl.scdn.co/images/pl/default/5fb0f131d9431…e603d4e97c87853153b754 could save 3.9KiB (40% reduction).
Compressing https://pl.scdn.co/images/pl/default/3e61ba9cb8cad…2f46f6ef42fcb2ad2573e9 could save 3.8KiB (43% reduction).
Compressing https://digle.tokyo/img/banner/fvmg.jpg could save 3.1KiB (20% reduction).
Compressing https://digle.tokyo/img/banner/fvmg-sp.jpg could save 2.8KiB (21% reduction).
Compressing https://digle.tokyo/img/banner/banner-register-login.jpg could save 2.7KiB (24% reduction).
Compressing https://digle.tokyo/img/banner/fv-sp.jpg could save 2.3KiB (17% reduction).
Compressing and resizing https://digle.tokyo/img/dammy.png could save 1.8KiB (47% reduction).
Compressing https://pl.scdn.co/images/pl/default/8193589ebf45a…e4ab0c856981e80a4502fe could save 1.1KiB (17% reduction).
Compressing https://pl.scdn.co/images/pl/default/a4c6f5defaadf…d4e12363175da5783b415e could save 1.1KiB (17% reduction).
Compressing https://scontent.xx.fbcdn.net/v/t1.0-1/p200x200/10…463a0c040a&oe=5BACFD13 could save 951B (13% reduction).
Compressing and resizing https://digle.tokyo/img/icon/arrow.png could save 527B (75% reduction).
Compressing and resizing https://digle.tokyo/img/icon/twitter.png could save 472B (40% reduction).
Compressing and resizing https://digle.tokyo/img/footer/arrow.png could save 365B (12% reduction).
Compressing and resizing https://digle.tokyo/img/icon/fb.png could save 294B (36% reduction).
Compressing https://digle.tokyo/img/icon/search.png could save 171B (18% reduction).
Compressing and resizing https://digle.tokyo/img/icon/rank-4.png could save 124B (19% reduction).
Compressing and resizing https://digle.tokyo/img/icon/rank-3.png could save 101B (16% reduction).

priority - 108 Enable compression

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

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

Compressing https://digle.tokyo/css/common.css could save 754.7KiB (90% reduction).
Compressing https://digle.tokyo/js/vendor/swiper.js could save 93.7KiB (78% reduction).
Compressing https://digle.tokyo/js/common.js could save 88.7KiB (87% reduction).
Compressing https://digle.tokyo/ could save 63.3KiB (86% reduction).
Compressing https://digle.tokyo/css/vendor/swiper.min.css could save 14.5KiB (83% reduction).
Compressing https://digle.tokyo/js/vendor/hammer.min.js could save 13.1KiB (64% reduction).
Compressing https://digle.tokyo/js/artist.js could save 6.1KiB (80% reduction).
Compressing https://digle.tokyo/js/mypage.js could save 3.2KiB (77% reduction).
Compressing https://digle.tokyo/js/vendor/imgLiquid-min.js could save 3.1KiB (62% reduction).
Compressing https://digle.tokyo/js/vendor/hiraku.min.js could save 2.5KiB (66% reduction).
Compressing https://digle.tokyo/css/vendor/hiraku.css could save 2.4KiB (74% reduction).
Compressing https://digle.tokyo/js/vendor/trunk8.js could save 2.3KiB (63% reduction).
Compressing https://digle.tokyo/css/vendor/yakuhanjp.css could save 1.9KiB (84% reduction).
Compressing https://digle.tokyo/js/vendor/ofi.min.js could save 1.8KiB (56% reduction).
Compressing https://digle.tokyo/js/vendor/jquery-ui-touch-punch.min.js could save 694B (53% reduction).
Compressing https://digle.tokyo/js/vendor/jquery.hammer.js could save 573B (58% reduction).

priority - 28 Leverage browser caching

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

Leverage browser caching for the following cacheable resources:

https://digle.tokyo/css/common.css (expiration not specified)
https://digle.tokyo/css/index.css (expiration not specified)
https://digle.tokyo/css/vendor/hiraku.css (expiration not specified)
https://digle.tokyo/css/vendor/swiper.min.css (expiration not specified)
https://digle.tokyo/css/vendor/yakuhanjp.css (expiration not specified)
https://digle.tokyo/img/banner/banner-register-login.jpg (expiration not specified)
https://digle.tokyo/img/banner/fv-sp.jpg (expiration not specified)
https://digle.tokyo/img/banner/fv.jpg (expiration not specified)
https://digle.tokyo/img/banner/fvmg-sp.jpg (expiration not specified)
https://digle.tokyo/img/banner/fvmg.jpg (expiration not specified)
https://digle.tokyo/img/banner/login-register.png (expiration not specified)
https://digle.tokyo/img/dammy.png (expiration not specified)
https://digle.tokyo/img/footer/arrow.png (expiration not specified)
https://digle.tokyo/img/footer/footer-logo.png (expiration not specified)
https://digle.tokyo/img/header/border-gradient-register.png (expiration not specified)
https://digle.tokyo/img/header/logo.png (expiration not specified)
https://digle.tokyo/img/header/search-button.png (expiration not specified)
https://digle.tokyo/img/header/sp/search-sp.png (expiration not specified)
https://digle.tokyo/img/icon/arrow.png (expiration not specified)
https://digle.tokyo/img/icon/fb.png (expiration not specified)
https://digle.tokyo/img/icon/humberger-menu.png (expiration not specified)
https://digle.tokyo/img/icon/menu-list.png (expiration not specified)
https://digle.tokyo/img/icon/next-a.png (expiration not specified)
https://digle.tokyo/img/icon/next.png (expiration not specified)
https://digle.tokyo/img/icon/play-mark.png (expiration not specified)
https://digle.tokyo/img/icon/plus-button.png (expiration not specified)
https://digle.tokyo/img/icon/prev-a.png (expiration not specified)
https://digle.tokyo/img/icon/prev.png (expiration not specified)
https://digle.tokyo/img/icon/rank-1.png (expiration not specified)
https://digle.tokyo/img/icon/rank-2.png (expiration not specified)
https://digle.tokyo/img/icon/rank-3.png (expiration not specified)
https://digle.tokyo/img/icon/rank-4.png (expiration not specified)
https://digle.tokyo/img/icon/rank-5.png (expiration not specified)
https://digle.tokyo/img/icon/search.png (expiration not specified)
https://digle.tokyo/img/icon/sp/more-link.png (expiration not specified)
https://digle.tokyo/img/icon/twitter.png (expiration not specified)
https://digle.tokyo/img/jacket-1.jpg (expiration not specified)
https://digle.tokyo/js/artist.js (expiration not specified)
https://digle.tokyo/js/common.js (expiration not specified)
https://digle.tokyo/js/mypage.js (expiration not specified)
https://digle.tokyo/js/vendor/hammer.min.js (expiration not specified)
https://digle.tokyo/js/vendor/hiraku.min.js (expiration not specified)
https://digle.tokyo/js/vendor/imgLiquid-min.js (expiration not specified)
https://digle.tokyo/js/vendor/jquery-ui-touch-punch.min.js (expiration not specified)
https://digle.tokyo/js/vendor/jquery.hammer.js (expiration not specified)
https://digle.tokyo/js/vendor/ofi.min.js (expiration not specified)
https://digle.tokyo/js/vendor/swiper.js (expiration not specified)
https://digle.tokyo/js/vendor/trunk8.js (expiration not specified)
https://digle.tokyo/upload/digger_image/130ad78a9b…213686c171253955c.jpeg (expiration not specified)
https://digle.tokyo/upload/digger_image/657686a63c…f8422facdd2f0b883.jpeg (expiration not specified)
https://digle.tokyo/upload/digger_image/9b616a3599…19449f39ad581db63.jpeg (expiration not specified)
https://digle.tokyo/upload/digger_image/ac91baea11…abb10015b86c361e5.jpeg (expiration not specified)
https://digle.tokyo/upload/digger_image/c7289f6e55…9a8141bddca30f1fb.jpeg (expiration not specified)
https://www.google.com/recaptcha/api.js (5 minutes)
https://wap.wovn.io/1.js (10 minutes)
https://www.googletagmanager.com/gtag/js?id=UA-88375672-1 (15 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 18 Minify 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 178.1KiB (22% reduction).

Minifying https://digle.tokyo/css/common.css could save 177.2KiB (22% reduction).
Minifying https://digle.tokyo/css/vendor/hiraku.css could save 544B (17% reduction).
Minifying https://digle.tokyo/css/vendor/yakuhanjp.css could save 250B (12% reduction).
Minifying https://digle.tokyo/css/index.css could save 158B (90% reduction).

priority - 13 Reduce server response time

In our test, your server responded in 1.5 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

priority - 10 Minify 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 93.8KiB (32% reduction).

Minifying https://code.jquery.com/ui/1.11.3/jquery-ui.js could save 39.9KiB (36% reduction) after compression.
Minifying https://digle.tokyo/js/common.js could save 35.7KiB (36% reduction).
Minifying https://j.wovn.io/1 could save 14.4KiB (21% reduction) after compression.
Minifying https://digle.tokyo/js/artist.js could save 2.4KiB (33% reduction).
Minifying https://digle.tokyo/js/mypage.js could save 952B (23% reduction).
Minifying https://digle.tokyo/js/vendor/jquery.hammer.js could save 344B (35% reduction).
Minifying https://digle.tokyo/js/vendor/jquery-ui-touch-punch.min.js could save 201B (16% reduction).

priority - 3 Minify HTML

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

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

Minifying https://digle.tokyo/ could save 24.8KiB (35% reduction).

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

Your page has 1 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Optimize CSS Delivery of the following:

https://digle.tokyo/css/vendor/yakuhanjp.css

digle.tokyo Desktop Resources

Total Resources92
Number of Hosts18
Static Resources75
JavaScript Resources21
CSS Resources6

digle.tokyo Desktop Resource Breakdown

digle.tokyo mobile page speed rank

Last tested: 2018-06-24

Mobile Speed Bad
6/100

digle.tokyo Mobile Speed Test Quick Summary


priority - 382 Optimize images

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

Optimize the following images to reduce their size by 3.6MiB (90% reduction).

Compressing and resizing https://digle.tokyo/upload/digger_image/9b616a3599…19449f39ad581db63.jpeg could save 1.7MiB (99% reduction).
Compressing and resizing https://digle.tokyo/upload/digger_image/c7289f6e55…9a8141bddca30f1fb.jpeg could save 1,017.1KiB (99% reduction).
Compressing and resizing https://digle.tokyo/upload/digger_image/130ad78a9b…213686c171253955c.jpeg could save 533.1KiB (99% reduction).
Compressing https://platform-lookaside.fbsbx.com/platform/prof…&hash=AeRluEnPtFP7gK_t could save 284.2KiB (58% reduction).
Compressing and resizing https://digle.tokyo/upload/digger_image/ac91baea11…abb10015b86c361e5.jpeg could save 108.8KiB (96% reduction).
Compressing https://pl.scdn.co/images/pl/default/b2bdce35d700a…ded849952600ddd0c78845 could save 15.3KiB (37% reduction).
Compressing https://pl.scdn.co/images/pl/default/d5c8067186a86…3a4384d96555434a8cc3df could save 7KiB (22% reduction).
Compressing https://pl.scdn.co/images/pl/default/b7fceaafb8774…2146c520e1cc8c240f2cca could save 5.9KiB (44% reduction).
Compressing https://pl.scdn.co/images/pl/default/537f122a8156e…81d659bbc91c435c2a22fe could save 5.3KiB (23% reduction).
Compressing https://profile-images.scdn.co/images/userprofile/…c9466a38784bcaa6a27d26 could save 4.6KiB (23% reduction).
Compressing https://pl.scdn.co/images/pl/default/e6d03f3da5cbf…b6ce370f4b9fb4b2ba8a37 could save 4KiB (25% reduction).
Compressing https://pl.scdn.co/images/pl/default/5fb0f131d9431…e603d4e97c87853153b754 could save 3.9KiB (40% reduction).
Compressing https://pl.scdn.co/images/pl/default/3e61ba9cb8cad…2f46f6ef42fcb2ad2573e9 could save 3.8KiB (43% reduction).
Compressing https://digle.tokyo/img/banner/fvmg.jpg could save 3.1KiB (20% reduction).
Compressing https://digle.tokyo/img/banner/fvmg-sp.jpg could save 2.8KiB (21% reduction).
Compressing https://digle.tokyo/img/banner/banner-register-login.jpg could save 2.7KiB (24% reduction).
Compressing https://digle.tokyo/img/banner/fv-sp.jpg could save 2.3KiB (17% reduction).
Compressing https://pl.scdn.co/images/pl/default/8193589ebf45a…e4ab0c856981e80a4502fe could save 1.1KiB (17% reduction).
Compressing https://pl.scdn.co/images/pl/default/a4c6f5defaadf…d4e12363175da5783b415e could save 1.1KiB (17% reduction).
Compressing https://scontent.xx.fbcdn.net/v/t1.0-1/p200x200/10…463a0c040a&oe=5BACFD13 could save 951B (13% reduction).
Compressing and resizing https://digle.tokyo/img/header/logo.png could save 828B (40% reduction).
Compressing https://digle.tokyo/img/icon/arrow.png could save 418B (59% reduction).
Compressing https://digle.tokyo/img/icon/search.png could save 171B (18% reduction).

priority - 108 Enable compression

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

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

Compressing https://digle.tokyo/css/common.css could save 754.7KiB (90% reduction).
Compressing https://digle.tokyo/js/vendor/swiper.js could save 93.7KiB (78% reduction).
Compressing https://digle.tokyo/js/common.js could save 88.7KiB (87% reduction).
Compressing https://digle.tokyo/ could save 63.3KiB (86% reduction).
Compressing https://digle.tokyo/css/vendor/swiper.min.css could save 14.5KiB (83% reduction).
Compressing https://digle.tokyo/js/vendor/hammer.min.js could save 13.1KiB (64% reduction).
Compressing https://digle.tokyo/js/artist.js could save 6.1KiB (80% reduction).
Compressing https://digle.tokyo/js/mypage.js could save 3.2KiB (77% reduction).
Compressing https://digle.tokyo/js/vendor/imgLiquid-min.js could save 3.1KiB (62% reduction).
Compressing https://digle.tokyo/js/vendor/hiraku.min.js could save 2.5KiB (66% reduction).
Compressing https://digle.tokyo/css/vendor/hiraku.css could save 2.4KiB (74% reduction).
Compressing https://digle.tokyo/js/vendor/trunk8.js could save 2.3KiB (63% reduction).
Compressing https://digle.tokyo/css/vendor/yakuhanjp.css could save 1.9KiB (84% reduction).
Compressing https://digle.tokyo/js/vendor/ofi.min.js could save 1.8KiB (56% reduction).
Compressing https://digle.tokyo/js/vendor/jquery-ui-touch-punch.min.js could save 694B (53% reduction).
Compressing https://digle.tokyo/js/vendor/jquery.hammer.js could save 573B (58% reduction).

priority - 42 Leverage browser caching

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

Leverage browser caching for the following cacheable resources:

https://digle.tokyo/css/common.css (expiration not specified)
https://digle.tokyo/css/index.css (expiration not specified)
https://digle.tokyo/css/vendor/hiraku.css (expiration not specified)
https://digle.tokyo/css/vendor/swiper.min.css (expiration not specified)
https://digle.tokyo/css/vendor/yakuhanjp.css (expiration not specified)
https://digle.tokyo/img/banner/banner-register-login.jpg (expiration not specified)
https://digle.tokyo/img/banner/fv-sp.jpg (expiration not specified)
https://digle.tokyo/img/banner/fv.jpg (expiration not specified)
https://digle.tokyo/img/banner/fvmg-sp.jpg (expiration not specified)
https://digle.tokyo/img/banner/fvmg.jpg (expiration not specified)
https://digle.tokyo/img/banner/login-register.png (expiration not specified)
https://digle.tokyo/img/dammy.png (expiration not specified)
https://digle.tokyo/img/footer/arrow.png (expiration not specified)
https://digle.tokyo/img/footer/footer-logo.png (expiration not specified)
https://digle.tokyo/img/header/border-gradient-register.png (expiration not specified)
https://digle.tokyo/img/header/logo.png (expiration not specified)
https://digle.tokyo/img/header/search-button.png (expiration not specified)
https://digle.tokyo/img/header/sp/search-sp.png (expiration not specified)
https://digle.tokyo/img/icon/arrow.png (expiration not specified)
https://digle.tokyo/img/icon/fb.png (expiration not specified)
https://digle.tokyo/img/icon/humberger-menu.png (expiration not specified)
https://digle.tokyo/img/icon/next-a.png (expiration not specified)
https://digle.tokyo/img/icon/next.png (expiration not specified)
https://digle.tokyo/img/icon/play-mark.png (expiration not specified)
https://digle.tokyo/img/icon/plus-button.png (expiration not specified)
https://digle.tokyo/img/icon/prev-a.png (expiration not specified)
https://digle.tokyo/img/icon/prev.png (expiration not specified)
https://digle.tokyo/img/icon/rank-1.png (expiration not specified)
https://digle.tokyo/img/icon/rank-2.png (expiration not specified)
https://digle.tokyo/img/icon/rank-3.png (expiration not specified)
https://digle.tokyo/img/icon/rank-4.png (expiration not specified)
https://digle.tokyo/img/icon/rank-5.png (expiration not specified)
https://digle.tokyo/img/icon/search.png (expiration not specified)
https://digle.tokyo/img/icon/sp/more-link.png (expiration not specified)
https://digle.tokyo/img/icon/twitter.png (expiration not specified)
https://digle.tokyo/img/jacket-1.jpg (expiration not specified)
https://digle.tokyo/js/artist.js (expiration not specified)
https://digle.tokyo/js/common.js (expiration not specified)
https://digle.tokyo/js/mypage.js (expiration not specified)
https://digle.tokyo/js/vendor/hammer.min.js (expiration not specified)
https://digle.tokyo/js/vendor/hiraku.min.js (expiration not specified)
https://digle.tokyo/js/vendor/imgLiquid-min.js (expiration not specified)
https://digle.tokyo/js/vendor/jquery-ui-touch-punch.min.js (expiration not specified)
https://digle.tokyo/js/vendor/jquery.hammer.js (expiration not specified)
https://digle.tokyo/js/vendor/ofi.min.js (expiration not specified)
https://digle.tokyo/js/vendor/swiper.js (expiration not specified)
https://digle.tokyo/js/vendor/trunk8.js (expiration not specified)
https://digle.tokyo/upload/digger_image/130ad78a9b…213686c171253955c.jpeg (expiration not specified)
https://digle.tokyo/upload/digger_image/657686a63c…f8422facdd2f0b883.jpeg (expiration not specified)
https://digle.tokyo/upload/digger_image/9b616a3599…19449f39ad581db63.jpeg (expiration not specified)
https://digle.tokyo/upload/digger_image/ac91baea11…abb10015b86c361e5.jpeg (expiration not specified)
https://digle.tokyo/upload/digger_image/c7289f6e55…9a8141bddca30f1fb.jpeg (expiration not specified)
https://www.google.com/recaptcha/api.js (5 minutes)
https://wap.wovn.io/1.js (10 minutes)
https://www.googletagmanager.com/gtag/js?id=UA-88375672-1 (15 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 20 Reduce server response time

In our test, your server responded in 1.5 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

priority - 18 Minify 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 178.1KiB (22% reduction).

Minifying https://digle.tokyo/css/common.css could save 177.2KiB (22% reduction).
Minifying https://digle.tokyo/css/vendor/hiraku.css could save 544B (17% reduction).
Minifying https://digle.tokyo/css/vendor/yakuhanjp.css could save 250B (12% reduction).
Minifying https://digle.tokyo/css/index.css could save 158B (90% reduction).

priority - 10 Minify 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 93.8KiB (32% reduction).

Minifying https://code.jquery.com/ui/1.11.3/jquery-ui.js could save 39.9KiB (36% reduction) after compression.
Minifying https://digle.tokyo/js/common.js could save 35.7KiB (36% reduction).
Minifying https://j.wovn.io/1 could save 14.4KiB (21% reduction) after compression.
Minifying https://digle.tokyo/js/artist.js could save 2.4KiB (33% reduction).
Minifying https://digle.tokyo/js/mypage.js could save 952B (23% reduction).
Minifying https://digle.tokyo/js/vendor/jquery.hammer.js could save 344B (35% reduction).
Minifying https://digle.tokyo/js/vendor/jquery-ui-touch-punch.min.js could save 201B (16% reduction).

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

Your page has 1 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Optimize CSS Delivery of the following:

https://digle.tokyo/css/vendor/yakuhanjp.css

priority - 3 Minify HTML

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

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

Minifying https://digle.tokyo/ could save 24.8KiB (35% reduction).

digle.tokyo Mobile Resources

Total Resources91
Number of Hosts18
Static Resources74
JavaScript Resources21
CSS Resources6

digle.tokyo Mobile Resource Breakdown

digle.tokyo mobile page usability

Last tested: 2018-06-24

Mobile Usability Good
94/100

digle.tokyo Mobile Usability Test Quick Summary


priority - 6 Size 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="/about/" class="p-arrow p-arro…u-pl30vw-down">ディグルについて</a> and 2 others are close to other tap targets.

The tap target <a href="https://www.fa…m/digle.tokyo/" class="u-color-text--…u-pb36vw-down">FACEBOOK</a> and 4 others are close to other tap targets.

The tap target <a href="/login/"></a> is close to 2 other tap targets.

The tap target <div class="p-firstview__s…tainer-android"></div> is close to 1 other tap targets.

The tap target <a href="/playlist/cfab…629a31452146b/"></a> and 5 others are close to other tap targets.

The tap target <div class="js-swiper-digg…tainer-android">電池を作る人/大学院生…Ayaka Sakai</div> is close to 1 other tap targets.

The tap target <a href="/login/"></a> is close to 1 other tap targets.

digle.tokyo similar domains

Similar domains:
www.digle.com
www.digle.net
www.digle.org
www.digle.info
www.digle.biz
www.digle.us
www.digle.mobi
www.igle.tokyo
www.digle.tokyo
www.xigle.tokyo
www.dxigle.tokyo
www.xdigle.tokyo
www.sigle.tokyo
www.dsigle.tokyo
www.sdigle.tokyo
www.eigle.tokyo
www.deigle.tokyo
www.edigle.tokyo
www.rigle.tokyo
www.drigle.tokyo
www.rdigle.tokyo
www.figle.tokyo
www.dfigle.tokyo
www.fdigle.tokyo
www.cigle.tokyo
www.dcigle.tokyo
www.cdigle.tokyo
www.dgle.tokyo
www.dugle.tokyo
www.diugle.tokyo
www.duigle.tokyo
www.djgle.tokyo
www.dijgle.tokyo
www.djigle.tokyo
www.dkgle.tokyo
www.dikgle.tokyo
www.dkigle.tokyo
www.dogle.tokyo
www.diogle.tokyo
www.doigle.tokyo
www.dile.tokyo
www.difle.tokyo
www.digfle.tokyo
www.difgle.tokyo
www.divle.tokyo
www.digvle.tokyo
www.divgle.tokyo
www.ditle.tokyo
www.digtle.tokyo
www.ditgle.tokyo
www.dible.tokyo
www.digble.tokyo
www.dibgle.tokyo
www.diyle.tokyo
www.digyle.tokyo
www.diygle.tokyo
www.dihle.tokyo
www.dighle.tokyo
www.dihgle.tokyo
www.dige.tokyo
www.digpe.tokyo
www.diglpe.tokyo
www.digple.tokyo
www.digoe.tokyo
www.digloe.tokyo
www.digole.tokyo
www.digke.tokyo
www.diglke.tokyo
www.digkle.tokyo
www.digl.tokyo
www.diglw.tokyo
www.diglew.tokyo
www.diglwe.tokyo
www.digls.tokyo
www.digles.tokyo
www.diglse.tokyo
www.digld.tokyo
www.digled.tokyo
www.diglde.tokyo
www.diglr.tokyo
www.digler.tokyo
www.diglre.tokyo

digle.tokyo Ping

Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.

digle.tokyo TRACEROUTE

Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.