web116.jp website information.
web116.jp domain name is registered by .JP top-level domain registry. See the other sites registred in .JP domain zone.
Following name servers are specified for web116.jp domain:
- ns2.nttcom.ne.jp
- pdsDkz03.aincs.ne.jp
and probably website web116.jp is hosted by LINODE-AP Linode, LLC, US web hosting company. Check the complete list of other most popular websites hosted by LINODE-AP Linode, LLC, US hosting company.
According to Alexa traffic rank the highest website web116.jp position was 6633 (in the world). The lowest Alexa rank position was 581556. Now website web116.jp ranked in Alexa database as number 216435 (in the world).
Website web116.jp Desktop speed measurement score (66/100) is better than the results of 44.37% of other sites shows that the page desktop performance can be improved.
web116.jp Mobile usability score (99/100) is better than the results of 79.46% of other sites and means that the page is mobile-friendly.
Mobile speed measurement score of web116.jp (46/100) is better than the results of 27.13% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Weekly Rank Report
| Date | Rank | Change |
|---|---|---|
| Nov-17-2024 | 216,435 | 4,705 |
| Nov-16-2024 | 221,140 | -772 |
| Nov-15-2024 | 220,368 | -2,557 |
| Nov-14-2024 | 217,811 | 1,701 |
| Nov-13-2024 | 219,512 | 0 |
| Nov-12-2024 | 219,512 | 0 |
| Nov-11-2024 | 219,512 | 0 |
Advertisement
web116.jp 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.
web116.jp 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.
web116.jp server information
web116.jp desktop page speed rank
Last tested: 2018-05-04
Desktop Speed
Medium
66/100
web116.jp Desktop Speed Test Quick Summary
priority - 22 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 211.4KiB (71% reduction).
Compressing http://web116.jp/shared/js/jquery.js could save 59.8KiB (64% reduction).
Compressing http://web116.jp/shared/css/common.css could save 28.8KiB (82% reduction).
Compressing http://web116.jp/shared/js/user_misc.js could save 23KiB (80% reduction).
Compressing http://web116.jp/ could save 17.2KiB (73% reduction).
Compressing http://web116.jp/shared/css/sub-contents.css could save 12.7KiB (87% reduction).
Compressing http://web116.jp/shared/css/global-navi.css could save 8.7KiB (85% reduction).
Compressing http://web116.jp/shared/js/jquery.exfixed-latest.js could save 7.9KiB (70% reduction).
Compressing http://web116.jp/shared/js/facet/thickbox.js could save 7.8KiB (68% reduction).
Compressing http://web116.jp/shared/css/content_top.css could save 7.5KiB (76% reduction).
Compressing http://web116.jp/shared/css/layout.css could save 7.2KiB (73% reduction).
Compressing http://search.ntt-east.co.jp/bizasp/js/accela_suggest2.js could save 4.1KiB (64% reduction).
Compressing http://search.ntt-east.co.jp/bizasp/js/accela_suggest.js could save 4KiB (64% reduction).
Compressing http://web116.jp/shared/js/facet/thickbox.css could save 3.2KiB (74% reduction).
Compressing http://web116.jp/shared/css/base.css could save 2.9KiB (62% reduction).
Compressing http://web116.jp/shared/js/common_pc.js could save 2.6KiB (77% reduction).
Compressing http://web116.jp/shared/js/focus/iepngfix.js could save 2.5KiB (58% reduction).
Compressing http://web116.jp/shared/css/focus/slide.css could save 2.1KiB (74% reduction).
Compressing http://web116.jp/shared/js/focus/setting.js could save 1.7KiB (61% reduction).
Compressing http://web116.jp/shared/js/focus/sliding.js could save 1.7KiB (65% reduction).
Compressing http://web116.jp/shared/css/head.css could save 1.4KiB (61% reduction).
Compressing http://web116.jp/shared/js/focus/cloning.js could save 1.1KiB (67% reduction).
Compressing http://web116.jp/shared/css/focus/reset.css could save 1.1KiB (54% reduction).
Compressing http://web116.jp/shared/images/focus/top/sites.xml could save 884B (63% reduction).
Compressing http://web116.jp/shared/js/placeholder.js could save 528B (68% reduction).
Compressing http://web116.jp/shared/css/foot.css could save 486B (50% reduction).
Compressing http://web116.jp/shared/css/bottom-content.css could save 255B (48% reduction).
Compressing http://web116.jp/shared/css/import.css could save 198B (44% reduction).
Compressing http://web116.jp/shared/css/common.css could save 28.8KiB (82% reduction).
Compressing http://web116.jp/shared/js/user_misc.js could save 23KiB (80% reduction).
Compressing http://web116.jp/ could save 17.2KiB (73% reduction).
Compressing http://web116.jp/shared/css/sub-contents.css could save 12.7KiB (87% reduction).
Compressing http://web116.jp/shared/css/global-navi.css could save 8.7KiB (85% reduction).
Compressing http://web116.jp/shared/js/jquery.exfixed-latest.js could save 7.9KiB (70% reduction).
Compressing http://web116.jp/shared/js/facet/thickbox.js could save 7.8KiB (68% reduction).
Compressing http://web116.jp/shared/css/content_top.css could save 7.5KiB (76% reduction).
Compressing http://web116.jp/shared/css/layout.css could save 7.2KiB (73% reduction).
Compressing http://search.ntt-east.co.jp/bizasp/js/accela_suggest2.js could save 4.1KiB (64% reduction).
Compressing http://search.ntt-east.co.jp/bizasp/js/accela_suggest.js could save 4KiB (64% reduction).
Compressing http://web116.jp/shared/js/facet/thickbox.css could save 3.2KiB (74% reduction).
Compressing http://web116.jp/shared/css/base.css could save 2.9KiB (62% reduction).
Compressing http://web116.jp/shared/js/common_pc.js could save 2.6KiB (77% reduction).
Compressing http://web116.jp/shared/js/focus/iepngfix.js could save 2.5KiB (58% reduction).
Compressing http://web116.jp/shared/css/focus/slide.css could save 2.1KiB (74% reduction).
Compressing http://web116.jp/shared/js/focus/setting.js could save 1.7KiB (61% reduction).
Compressing http://web116.jp/shared/js/focus/sliding.js could save 1.7KiB (65% reduction).
Compressing http://web116.jp/shared/css/head.css could save 1.4KiB (61% reduction).
Compressing http://web116.jp/shared/js/focus/cloning.js could save 1.1KiB (67% reduction).
Compressing http://web116.jp/shared/css/focus/reset.css could save 1.1KiB (54% reduction).
Compressing http://web116.jp/shared/images/focus/top/sites.xml could save 884B (63% reduction).
Compressing http://web116.jp/shared/js/placeholder.js could save 528B (68% reduction).
Compressing http://web116.jp/shared/css/foot.css could save 486B (50% reduction).
Compressing http://web116.jp/shared/css/bottom-content.css could save 255B (48% reduction).
Compressing http://web116.jp/shared/css/import.css could save 198B (44% reduction).
priority - 14 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 7 blocking script resources and 13 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.
Remove render-blocking JavaScript:
http://web116.jp/shared/js/common_pc.js
http://web116.jp/shared/js/jquery.js
http://web116.jp/shared/js/user_misc.js
http://web116.jp/shared/js/facet/thickbox.js
http://web116.jp/shared/js/jquery.exfixed-latest.js
http://web116.jp/shared/js/focus/cloning.js
http://search.ntt-east.co.jp/bizasp/js/accela_suggest2.js
http://web116.jp/shared/js/jquery.js
http://web116.jp/shared/js/user_misc.js
http://web116.jp/shared/js/facet/thickbox.js
http://web116.jp/shared/js/jquery.exfixed-latest.js
http://web116.jp/shared/js/focus/cloning.js
http://search.ntt-east.co.jp/bizasp/js/accela_suggest2.js
Optimize CSS Delivery of the following:
http://web116.jp/shared/css/import.css
http://web116.jp/shared/css/layout.css
http://web116.jp/shared/css/base.css
http://web116.jp/shared/css/head.css
http://web116.jp/shared/css/global-navi.css
http://web116.jp/shared/css/sub-contents.css
http://web116.jp/shared/css/bottom-content.css
http://web116.jp/shared/css/foot.css
http://web116.jp/shared/css/common.css
http://web116.jp/shared/js/facet/thickbox.css
http://web116.jp/shared/css/content_top.css
http://web116.jp/shared/css/focus/reset.css
http://web116.jp/shared/css/focus/slide.css
http://web116.jp/shared/css/layout.css
http://web116.jp/shared/css/base.css
http://web116.jp/shared/css/head.css
http://web116.jp/shared/css/global-navi.css
http://web116.jp/shared/css/sub-contents.css
http://web116.jp/shared/css/bottom-content.css
http://web116.jp/shared/css/foot.css
http://web116.jp/shared/css/common.css
http://web116.jp/shared/js/facet/thickbox.css
http://web116.jp/shared/css/content_top.css
http://web116.jp/shared/css/focus/reset.css
http://web116.jp/shared/css/focus/slide.css
priority - 10 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 95.2KiB (28% reduction).
Compressing http://web116.jp/shared/images/focus/top/img_05.png could save 31.9KiB (35% reduction).
Compressing http://web116.jp/shared/images/focus/top/img_main.png could save 19.9KiB (26% reduction).
Compressing http://web116.jp/shared/images/focus/top/img_03.png could save 19.6KiB (25% reduction).
Compressing http://web116.jp/shared/images/global_navi/gnavi_index.gif could save 2.8KiB (31% reduction).
Compressing http://web116.jp/shared/images/focus/top/tmb_08.png could save 1.5KiB (23% reduction).
Compressing http://web116.jp/shared/images/global_navi/gnavi_bg.gif could save 1.5KiB (85% reduction).
Compressing http://web116.jp/ced/images/top/ind_bg_h2.gif could save 1.4KiB (75% reduction).
Compressing http://web116.jp/images/top/tit_kiki.gif could save 1.2KiB (28% reduction).
Compressing http://web116.jp/shared/images/focus/top/tmb_10.png could save 1.1KiB (12% reduction).
Compressing http://web116.jp/shared/images/focus/top/tmb_03.png could save 1.1KiB (23% reduction).
Compressing http://web116.jp/images/top/tit_payment.gif could save 1KiB (23% reduction).
Compressing http://web116.jp/images/top/title01.jpg could save 1KiB (24% reduction).
Compressing http://web116.jp/images/top/ind_bg_h2.gif could save 1,004B (53% reduction).
Compressing http://web116.jp/shared/images/focus/top/tmb_05.png could save 920B (12% reduction).
Compressing http://web116.jp/shared/images/focus/tmb_off.png could save 831B (72% reduction).
Compressing http://web116.jp/shared/images/subcont/bg_boxbot.gif could save 739B (70% reduction).
Compressing http://web116.jp/images/top/tit_phone.gif could save 679B (17% reduction).
Compressing http://web116.jp/shared/images/focus/img_off.png could save 676B (34% reduction).
Compressing http://web116.jp/shared/images/head/header_serch_btn.gif could save 676B (54% reduction).
Compressing http://web116.jp/shared/images/head/header_serch_btn.gif could save 676B (54% reduction).
Compressing http://web116.jp/images/top/title03.jpg could save 674B (24% reduction).
Compressing http://web116.jp/images/top/top_intro_2024ikou.gif could save 624B (17% reduction).
Compressing http://web116.jp/shared/images/focus/top/tmb_04.png could save 573B (11% reduction).
Compressing http://web116.jp/images/top/top_intro_toiawase.gif could save 556B (18% reduction).
Compressing http://web116.jp/shared/images/head/header_logo_116_def.gif could save 543B (19% reduction).
Compressing http://web116.jp/images/top/tit2_faq.gif could save 478B (27% reduction).
Compressing http://web116.jp/images/top/tit2_support.gif could save 444B (25% reduction).
Compressing http://web116.jp/images/top/tit2_if.gif could save 419B (21% reduction).
Compressing http://web116.jp/shared/images/focus/arrow.png could save 415B (15% reduction).
Compressing http://web116.jp/images/top/title02.jpg could save 341B (22% reduction).
Compressing http://web116.jp/shared/images/head/header_logo_ntt.gif could save 199B (12% reduction).
Compressing http://web116.jp/shared/images/subcont/rtit_site.gif could save 101B (11% reduction).
Compressing http://web116.jp/shared/images/focus/top/img_main.png could save 19.9KiB (26% reduction).
Compressing http://web116.jp/shared/images/focus/top/img_03.png could save 19.6KiB (25% reduction).
Compressing http://web116.jp/shared/images/global_navi/gnavi_index.gif could save 2.8KiB (31% reduction).
Compressing http://web116.jp/shared/images/focus/top/tmb_08.png could save 1.5KiB (23% reduction).
Compressing http://web116.jp/shared/images/global_navi/gnavi_bg.gif could save 1.5KiB (85% reduction).
Compressing http://web116.jp/ced/images/top/ind_bg_h2.gif could save 1.4KiB (75% reduction).
Compressing http://web116.jp/images/top/tit_kiki.gif could save 1.2KiB (28% reduction).
Compressing http://web116.jp/shared/images/focus/top/tmb_10.png could save 1.1KiB (12% reduction).
Compressing http://web116.jp/shared/images/focus/top/tmb_03.png could save 1.1KiB (23% reduction).
Compressing http://web116.jp/images/top/tit_payment.gif could save 1KiB (23% reduction).
Compressing http://web116.jp/images/top/title01.jpg could save 1KiB (24% reduction).
Compressing http://web116.jp/images/top/ind_bg_h2.gif could save 1,004B (53% reduction).
Compressing http://web116.jp/shared/images/focus/top/tmb_05.png could save 920B (12% reduction).
Compressing http://web116.jp/shared/images/focus/tmb_off.png could save 831B (72% reduction).
Compressing http://web116.jp/shared/images/subcont/bg_boxbot.gif could save 739B (70% reduction).
Compressing http://web116.jp/images/top/tit_phone.gif could save 679B (17% reduction).
Compressing http://web116.jp/shared/images/focus/img_off.png could save 676B (34% reduction).
Compressing http://web116.jp/shared/images/head/header_serch_btn.gif could save 676B (54% reduction).
Compressing http://web116.jp/shared/images/head/header_serch_btn.gif could save 676B (54% reduction).
Compressing http://web116.jp/images/top/title03.jpg could save 674B (24% reduction).
Compressing http://web116.jp/images/top/top_intro_2024ikou.gif could save 624B (17% reduction).
Compressing http://web116.jp/shared/images/focus/top/tmb_04.png could save 573B (11% reduction).
Compressing http://web116.jp/images/top/top_intro_toiawase.gif could save 556B (18% reduction).
Compressing http://web116.jp/shared/images/head/header_logo_116_def.gif could save 543B (19% reduction).
Compressing http://web116.jp/images/top/tit2_faq.gif could save 478B (27% reduction).
Compressing http://web116.jp/images/top/tit2_support.gif could save 444B (25% reduction).
Compressing http://web116.jp/images/top/tit2_if.gif could save 419B (21% reduction).
Compressing http://web116.jp/shared/images/focus/arrow.png could save 415B (15% reduction).
Compressing http://web116.jp/images/top/title02.jpg could save 341B (22% reduction).
Compressing http://web116.jp/shared/images/head/header_logo_ntt.gif could save 199B (12% reduction).
Compressing http://web116.jp/shared/images/subcont/rtit_site.gif could save 101B (11% reduction).
priority - 3 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 28.9KiB (30% reduction).
Minifying http://web116.jp/shared/css/common.css could save 10.7KiB (31% reduction).
Minifying http://web116.jp/shared/css/sub-contents.css could save 4.2KiB (29% reduction).
Minifying http://web116.jp/shared/css/layout.css could save 2.9KiB (30% reduction).
Minifying http://web116.jp/shared/css/content_top.css could save 2.8KiB (29% reduction).
Minifying http://web116.jp/shared/css/global-navi.css could save 2.1KiB (21% reduction).
Minifying http://web116.jp/shared/js/facet/thickbox.css could save 1.6KiB (38% reduction).
Minifying http://web116.jp/shared/css/focus/reset.css could save 1.5KiB (76% reduction).
Minifying http://web116.jp/shared/css/base.css could save 1.5KiB (32% reduction).
Minifying http://web116.jp/shared/css/focus/slide.css could save 750B (27% reduction).
Minifying http://web116.jp/shared/css/head.css could save 386B (17% reduction).
Minifying http://web116.jp/shared/css/foot.css could save 277B (29% reduction).
Minifying http://web116.jp/shared/css/import.css could save 195B (43% reduction).
Minifying http://web116.jp/shared/css/sub-contents.css could save 4.2KiB (29% reduction).
Minifying http://web116.jp/shared/css/layout.css could save 2.9KiB (30% reduction).
Minifying http://web116.jp/shared/css/content_top.css could save 2.8KiB (29% reduction).
Minifying http://web116.jp/shared/css/global-navi.css could save 2.1KiB (21% reduction).
Minifying http://web116.jp/shared/js/facet/thickbox.css could save 1.6KiB (38% reduction).
Minifying http://web116.jp/shared/css/focus/reset.css could save 1.5KiB (76% reduction).
Minifying http://web116.jp/shared/css/base.css could save 1.5KiB (32% reduction).
Minifying http://web116.jp/shared/css/focus/slide.css could save 750B (27% reduction).
Minifying http://web116.jp/shared/css/head.css could save 386B (17% reduction).
Minifying http://web116.jp/shared/css/foot.css could save 277B (29% reduction).
Minifying http://web116.jp/shared/css/import.css could save 195B (43% reduction).
priority - 2 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 24.1KiB (36% reduction).
Minifying http://web116.jp/shared/js/user_misc.js could save 11.2KiB (40% reduction).
Minifying http://web116.jp/shared/js/jquery.exfixed-latest.js could save 3.4KiB (31% reduction).
Minifying http://web116.jp/shared/js/facet/thickbox.js could save 3.2KiB (29% reduction).
Minifying http://web116.jp/shared/js/focus/iepngfix.js could save 1.7KiB (40% reduction).
Minifying http://web116.jp/shared/js/focus/setting.js could save 1.2KiB (44% reduction).
Minifying http://web116.jp/shared/js/common_pc.js could save 1.2KiB (35% reduction).
Minifying http://web116.jp/shared/js/focus/sliding.js could save 1.1KiB (45% reduction).
Minifying http://web116.jp/shared/js/focus/cloning.js could save 792B (46% reduction).
Minifying http://web116.jp/shared/js/placeholder.js could save 169B (22% reduction).
Minifying http://web116.jp/shared/js/jquery.exfixed-latest.js could save 3.4KiB (31% reduction).
Minifying http://web116.jp/shared/js/facet/thickbox.js could save 3.2KiB (29% reduction).
Minifying http://web116.jp/shared/js/focus/iepngfix.js could save 1.7KiB (40% reduction).
Minifying http://web116.jp/shared/js/focus/setting.js could save 1.2KiB (44% reduction).
Minifying http://web116.jp/shared/js/common_pc.js could save 1.2KiB (35% reduction).
Minifying http://web116.jp/shared/js/focus/sliding.js could save 1.1KiB (45% reduction).
Minifying http://web116.jp/shared/js/focus/cloning.js could save 792B (46% reduction).
Minifying http://web116.jp/shared/js/placeholder.js could save 169B (22% reduction).
priority - 0 Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
http://www.google-analytics.com/analytics.js (2 hours)
priority - 0 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 3KiB (13% reduction).
Minifying http://web116.jp/ could save 3KiB (13% reduction).
web116.jp Desktop Resources
| Total Resources | 79 |
| Number of Hosts | 3 |
| Static Resources | 3 |
| JavaScript Resources | 13 |
| CSS Resources | 13 |
web116.jp Desktop Resource Breakdown
web116.jp mobile page speed rank
Last tested: 2019-12-09
Mobile Speed
Bad
46/100
web116.jp Mobile Speed Test Quick Summary
priority - 64 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 8 blocking script resources and 3 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.
Remove render-blocking JavaScript:
https://web116.jp/shared/js/common_sp.js
https://web116.jp/s/common/js/jquery.min.js
https://web116.jp/s/common/js/load.js
https://web116.jp/s/common/js/jquery.flickslide.js
https://web116.jp/shared/js/user_misc.js
https://web116.jp/shared/js/facet/thickbox.js
https://web116.jp/shared/js/jquery.exfixed-latest.js
https://web116.jp/s/common/js/run.js
https://web116.jp/s/common/js/jquery.min.js
https://web116.jp/s/common/js/load.js
https://web116.jp/s/common/js/jquery.flickslide.js
https://web116.jp/shared/js/user_misc.js
https://web116.jp/shared/js/facet/thickbox.js
https://web116.jp/shared/js/jquery.exfixed-latest.js
https://web116.jp/s/common/js/run.js
Optimize CSS Delivery of the following:
https://web116.jp/s/common/css/core.css
https://web116.jp/s/common/css/component.css
https://web116.jp/s/common/css/widget.css
https://web116.jp/s/common/css/component.css
https://web116.jp/s/common/css/widget.css
priority - 21 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 201.4KiB (46% reduction).
Compressing https://web116.jp/s/images/focus/top/top_bnr_slide_06.jpg could save 42.3KiB (51% reduction).
Compressing https://web116.jp/s/images/focus/top/top_bnr_slide_03.jpg could save 42KiB (51% reduction).
Compressing https://web116.jp/s/images/focus/top/top_bnr_slide_04.jpg could save 35.9KiB (48% reduction).
Compressing https://web116.jp/s/images/focus/top/top_bnr_slide_05.jpg could save 34.7KiB (59% reduction).
Compressing https://web116.jp/s/images/focus/top/top_bnr_slide_08.jpg could save 31.8KiB (49% reduction).
Compressing https://web116.jp/s/images/focus/top/top_bnr_slide_02.jpg could save 5.6KiB (16% reduction).
Compressing https://web116.jp/s/images/pickup/pick_hikari.png could save 2.8KiB (31% reduction).
Compressing https://web116.jp/s/images/pickup/pick_0036.png could save 2.6KiB (32% reduction).
Compressing https://web116.jp/s/images/pickup/pick_credit.png could save 2.2KiB (16% reduction).
Compressing https://web116.jp/s/common/images/icons.png could save 874B (15% reduction).
Compressing https://web116.jp/s/common/images/icons_high.png could save 761B (11% reduction).
Compressing https://web116.jp/s/images/focus/top/top_bnr_slide_03.jpg could save 42KiB (51% reduction).
Compressing https://web116.jp/s/images/focus/top/top_bnr_slide_04.jpg could save 35.9KiB (48% reduction).
Compressing https://web116.jp/s/images/focus/top/top_bnr_slide_05.jpg could save 34.7KiB (59% reduction).
Compressing https://web116.jp/s/images/focus/top/top_bnr_slide_08.jpg could save 31.8KiB (49% reduction).
Compressing https://web116.jp/s/images/focus/top/top_bnr_slide_02.jpg could save 5.6KiB (16% reduction).
Compressing https://web116.jp/s/images/pickup/pick_hikari.png could save 2.8KiB (31% reduction).
Compressing https://web116.jp/s/images/pickup/pick_0036.png could save 2.6KiB (32% reduction).
Compressing https://web116.jp/s/images/pickup/pick_credit.png could save 2.2KiB (16% reduction).
Compressing https://web116.jp/s/common/images/icons.png could save 874B (15% reduction).
Compressing https://web116.jp/s/common/images/icons_high.png could save 761B (11% reduction).
priority - 13 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 130.4KiB (69% reduction).
Compressing https://web116.jp/s/common/js/jquery.min.js could save 59.8KiB (64% reduction).
Compressing https://web116.jp/shared/js/user_misc.js could save 23.3KiB (80% reduction).
Compressing https://web116.jp/s/common/css/component.css could save 8.5KiB (82% reduction).
Compressing https://web116.jp/shared/js/jquery.exfixed-latest.js could save 7.9KiB (70% reduction).
Compressing https://web116.jp/s/index.html could save 7.9KiB (73% reduction).
Compressing https://web116.jp/shared/js/facet/thickbox.js could save 7.8KiB (68% reduction).
Compressing https://web116.jp/s/common/js/jquery.flickslide.js could save 5.7KiB (72% reduction).
Compressing https://web116.jp/s/common/css/widget.css could save 2.9KiB (72% reduction).
Compressing https://web116.jp/s/common/css/core.css could save 2.8KiB (70% reduction).
Compressing https://web116.jp/shared/js/common_sp.js could save 2.4KiB (77% reduction).
Compressing https://web116.jp/s/common/js/run.js could save 1.3KiB (67% reduction).
Compressing https://web116.jp/s/common/js/load.js could save 158B (47% reduction).
Compressing https://web116.jp/shared/js/user_misc.js could save 23.3KiB (80% reduction).
Compressing https://web116.jp/s/common/css/component.css could save 8.5KiB (82% reduction).
Compressing https://web116.jp/shared/js/jquery.exfixed-latest.js could save 7.9KiB (70% reduction).
Compressing https://web116.jp/s/index.html could save 7.9KiB (73% reduction).
Compressing https://web116.jp/shared/js/facet/thickbox.js could save 7.8KiB (68% reduction).
Compressing https://web116.jp/s/common/js/jquery.flickslide.js could save 5.7KiB (72% reduction).
Compressing https://web116.jp/s/common/css/widget.css could save 2.9KiB (72% reduction).
Compressing https://web116.jp/s/common/css/core.css could save 2.8KiB (70% reduction).
Compressing https://web116.jp/shared/js/common_sp.js could save 2.4KiB (77% reduction).
Compressing https://web116.jp/s/common/js/run.js could save 1.3KiB (67% reduction).
Compressing https://web116.jp/s/common/js/load.js could save 158B (47% reduction).
priority - 12 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://s.yjtag.jp/tag.js (expiration not specified)
https://s.yimg.jp/images/listing/tool/cv/conversion.js (10 minutes)
https://s.yimg.jp/images/listing/tool/cv/ytag.js (10 minutes)
https://www.googletagmanager.com/gtag/js?id=AW-699485346 (15 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-M2K5BPH&l=dataLayer (15 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-M6GNB7L&l=dataLayer (15 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-NW2R359&l=dataLayer (15 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-TD73K2F (15 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-TPBRHJZ&l=dataLayer (15 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-TR6WFLF&l=dataLayer (15 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-TSR3LCG&l=dataLayer (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/942411…9923?v=2.9.14&r=stable (20 minutes)
https://adcdn.goo.ne.jp/images/pix/uvqqgowbzf.js (45.8 minutes)
https://www.googleadservices.com/pagead/conversion_async.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://s.yimg.jp/images/listing/tool/cv/conversion.js (10 minutes)
https://s.yimg.jp/images/listing/tool/cv/ytag.js (10 minutes)
https://www.googletagmanager.com/gtag/js?id=AW-699485346 (15 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-M2K5BPH&l=dataLayer (15 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-M6GNB7L&l=dataLayer (15 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-NW2R359&l=dataLayer (15 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-TD73K2F (15 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-TPBRHJZ&l=dataLayer (15 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-TR6WFLF&l=dataLayer (15 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-TSR3LCG&l=dataLayer (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/942411…9923?v=2.9.14&r=stable (20 minutes)
https://adcdn.goo.ne.jp/images/pix/uvqqgowbzf.js (45.8 minutes)
https://www.googleadservices.com/pagead/conversion_async.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
priority - 10 Avoid landing page redirects
Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.
Avoid landing page redirects for the following chain of redirected URLs.
http://web116.jp/
https://web116.jp/
https://web116.jp/s/index.html
https://web116.jp/
https://web116.jp/s/index.html
priority - 8 Prioritize visible content
Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
Only about 64% of the final above-the-fold content could be rendered with the full HTML response.
Click to see the screenshot with only the HTML response:
priority - 2 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 20.3KiB (36% reduction).
Minifying https://web116.jp/shared/js/user_misc.js could save 11.4KiB (40% reduction).
Minifying https://web116.jp/shared/js/jquery.exfixed-latest.js could save 3.4KiB (31% reduction).
Minifying https://web116.jp/shared/js/facet/thickbox.js could save 3.2KiB (29% reduction).
Minifying https://web116.jp/s/common/js/run.js could save 1.1KiB (53% reduction).
Minifying https://web116.jp/shared/js/common_sp.js could save 1KiB (32% reduction).
Minifying https://web116.jp/s/common/js/load.js could save 179B (52% reduction).
Minifying https://web116.jp/shared/js/jquery.exfixed-latest.js could save 3.4KiB (31% reduction).
Minifying https://web116.jp/shared/js/facet/thickbox.js could save 3.2KiB (29% reduction).
Minifying https://web116.jp/s/common/js/run.js could save 1.1KiB (53% reduction).
Minifying https://web116.jp/shared/js/common_sp.js could save 1KiB (32% reduction).
Minifying https://web116.jp/s/common/js/load.js could save 179B (52% reduction).
priority - 0 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 4.8KiB (27% reduction).
Minifying https://web116.jp/s/common/css/component.css could save 2.4KiB (24% reduction).
Minifying https://web116.jp/s/common/css/core.css could save 1.5KiB (38% reduction).
Minifying https://web116.jp/s/common/css/widget.css could save 977B (25% reduction).
Minifying https://web116.jp/s/common/css/core.css could save 1.5KiB (38% reduction).
Minifying https://web116.jp/s/common/css/widget.css could save 977B (25% reduction).
web116.jp Mobile Resources
| Total Resources | 85 |
| Number of Hosts | 26 |
| Static Resources | 19 |
| JavaScript Resources | 39 |
| CSS Resources | 3 |
web116.jp Mobile Resource Breakdown
web116.jp mobile page usability
Last tested: 2019-12-09
Mobile Usability
Good
99/100
web116.jp Mobile Usability Test Quick Summary
priority - 0 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="/term/index.html">サイトのご利用条件(PC)</a> and 1 others are close to other tap targets.web116.jp similar domains
Similar domains:
www.web116.com
www.web116.net
www.web116.org
www.web116.info
www.web116.biz
www.web116.us
www.web116.mobi
www.eb116.jp
www.web116.jp
www.qeb116.jp
www.wqeb116.jp
www.qweb116.jp
www.aeb116.jp
www.waeb116.jp
www.aweb116.jp
www.seb116.jp
www.wseb116.jp
www.sweb116.jp
www.eeb116.jp
www.weeb116.jp
www.eweb116.jp
www.wb116.jp
www.wwb116.jp
www.wewb116.jp
www.wweb116.jp
www.wsb116.jp
www.wesb116.jp
www.wdb116.jp
www.wedb116.jp
www.wdeb116.jp
www.wrb116.jp
www.werb116.jp
www.wreb116.jp
www.we116.jp
www.wev116.jp
www.webv116.jp
www.wevb116.jp
www.weg116.jp
www.webg116.jp
www.wegb116.jp
www.weh116.jp
www.webh116.jp
www.wehb116.jp
www.wen116.jp
www.webn116.jp
www.wenb116.jp
www.web16.jp
www.web11.jp
www.web116.net
www.web116.org
www.web116.info
www.web116.biz
www.web116.us
www.web116.mobi
www.eb116.jp
www.web116.jp
www.qeb116.jp
www.wqeb116.jp
www.qweb116.jp
www.aeb116.jp
www.waeb116.jp
www.aweb116.jp
www.seb116.jp
www.wseb116.jp
www.sweb116.jp
www.eeb116.jp
www.weeb116.jp
www.eweb116.jp
www.wb116.jp
www.wwb116.jp
www.wewb116.jp
www.wweb116.jp
www.wsb116.jp
www.wesb116.jp
www.wdb116.jp
www.wedb116.jp
www.wdeb116.jp
www.wrb116.jp
www.werb116.jp
www.wreb116.jp
www.we116.jp
www.wev116.jp
www.webv116.jp
www.wevb116.jp
www.weg116.jp
www.webg116.jp
www.wegb116.jp
www.weh116.jp
www.webh116.jp
www.wehb116.jp
www.wen116.jp
www.webn116.jp
www.wenb116.jp
www.web16.jp
www.web11.jp
web116.jp 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.
web116.jp 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.