IPRIMO.JP 婚約指輪,結婚指輪などのブライダルリング専門店I-PRIMO(アイプリモ)

iprimo.jp Website Information

Daily Unique Visits: 2,198

Daily Page Views: 6,594

Income Per Day: $20

Estimated Value: $7,200

This website is located in Japan and is using following IP address 219.99.164.190. See the complete list of popular websites hosted in Japan.

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

Website iprimo.jp is using the following name servers:

  • dns-c.iij.ad.jp
  • dns-b.iij.ad.jp

and is probably hosted by FUTURE Future Spirits Co.,Ltd., JP. See the full list of other websites hosted by FUTURE Future Spirits Co.,Ltd., JP.

The highest website iprimo.jp position in Alexa rank database was 21749 and the lowest rank position was 971266. Current position of iprimo.jp in Alexa rank database is 489303.

Desktop speed score of iprimo.jp (62/100) is better than the results of 38.44% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of iprimo.jp (95/100) is better than the results of 39.69% of other sites and means that the page is mobile-friendly.

Mobile speed score of iprimo.jp (45/100) is better than the results of 25.64% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Advertisement

iprimo.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.


iprimo.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] IPRIMO.JP

[登録者名] プリモ・ジャパン 株式会社
[Registrant] Primo Japan Inc.

[Name Server] ns013-7avbmc8tm0tnd8v9.7.d-53.info
[Name Server] ns013-7avbmc8tm0tnd8v9.7.d-53.jp
[Name Server] ns013-7avbmc8tm0tnd8v9.7.d-53.net
[Signing Key] 48918 13 2 (
87D3AA6F1E52F9A7CD468DE99631F013
60EE04ABF0675A4AFC5D231BDB5EBD42 )

[登録年月日] 2003/04/16
[有効期限] 2025/04/30
[状態] Active
[最終更新] 2024/05/01 01:05:04 (JST)

Contact Information: [公開連絡窓口]
[名前] プリモ・ジャパン 株式会社
[Name] Primo Japan Inc.
[Email] postmaster@primojapan.co.jp
[Web Page]
[郵便番号] 104-0061
[住所] 東京都中央区 銀座 5-12-5
白鶴ビルディング 4F
[Postal Address] Tokyo
Chuo-ku
HAKUTSURU Bldg. 4F, 5-12-5 Ginza
[電話番号] 03-6226-6261
[FAX番号] 03-6226-6269

iprimo.jp server information

Servers Location

iprimo.jp desktop page speed rank

Last tested: 2018-12-09


Desktop Speed Bad
62/100

iprimo.jp Desktop Speed Test Quick Summary


priority - 32Optimize images

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

Optimize the following images to reduce their size by 314.5KiB (55% reduction).

Compressing https://image.iprimo.jp/assets_2017/img/index_v2/main_01.jpg could save 123.6KiB (75% reduction).
Compressing https://image.iprimo.jp/assets_2017/img/index_v2/main_06.jpg could save 88.5KiB (50% reduction).
Compressing https://image.iprimo.jp/assets_2017/img/index/instaPic02.jpg could save 30.7KiB (67% reduction).
Compressing https://image.iprimo.jp/assets_2017/img/index/instaPic03.jpg could save 23.2KiB (66% reduction).
Compressing https://image.iprimo.jp/assets_2017/img/index_v2/main_05.jpg could save 18.8KiB (28% reduction).
Compressing https://image.iprimo.jp/assets_2017/img/index/instaPic01.jpg could save 17.1KiB (70% reduction).
Compressing https://image.iprimo.jp/assets_2017/img/index_v2/filter.png could save 6.2KiB (30% reduction).
Compressing https://image.iprimo.jp/assets_2017/img/index/link03.jpg could save 3.2KiB (17% reduction).
Compressing https://image.iprimo.jp/assets_2017/img/index/link02.jpg could save 2.9KiB (18% reduction).
Compressing https://image.iprimo.jp/assets_2017/img/common/instaIcon2.png could save 159B (24% reduction).
Compressing https://image.iprimo.jp/assets_2017/img/common/instaIcon.png could save 155B (23% reduction).

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

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

Optimize CSS Delivery of the following:

https://www.iprimo.jp/assets_2017/css/common.css?ver=1
https://fast.fonts.net/t/1.css?apiType=css&project…4a47-b69c-0cf361b4f823
https://fonts.googleapis.com/css?family=Noto+Serif…00,600&subset=japanese
https://www.iprimo.jp/assets_2017/css/head.css?ver=1
https://www.iprimo.jp/assets_2017/css/foot.css?ver=1
https://www.iprimo.jp/assets_2017/css/slick.css?ver=1
https://www.iprimo.jp/assets_2017/css/index-v2.css?ver=1
https://www.iprimo.jp/assets_new/css/ipcheck_modal.css?ver=1

priority - 9Avoid 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://iprimo.jp/
https://iprimo.jp/
https://www.iprimo.jp/

priority - 6Leverage 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://b92.yahoo.co.jp/js/s_retargeting.js (expiration not specified)
https://st.nex8.net/js/nexRt.js (expiration not specified)
https://s.yimg.jp/images/listing/tool/cv/conversion.js (9.5 minutes)
https://d.line-scdn.net/n/line_tag/public/release/v1/lt.js (13.8 minutes)
https://js.fout.jp/segmentation.js (14.8 minutes)
https://www.googletagmanager.com/gtag/js?id=AW-961632427 (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/611324…2723?v=2.8.34&r=stable (20 minutes)
https://connect.facebook.net/signals/config/611383…3977?v=2.8.34&r=stable (20 minutes)
https://www.googleadservices.com/pagead/conversion.js (60 minutes)
https://www.googleadservices.com/pagead/conversion_async.js (60 minutes)
https://stats.g.doubleclick.net/dc.js (2 hours)
https://cs.nakanohito.jp/b3/bi.js (3 hours)
https://s.yjtag.jp/tag.js (4 hours)

priority - 3Reduce server response time

In our test, your server responded in 0.32 seconds.

priority - 1Minify 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 10.1KiB (19% reduction).

Minifying https://www.iprimo.jp/js/s_code.js could save 8KiB (19% reduction) after compression.
Minifying https://www.iprimo.jp/js/ppc_primo.js could save 624B (51% reduction) after compression.
Minifying https://d-track.send.microad.jp/js/blade_track_jp.js could save 584B (15% reduction).
Minifying https://js.fout.jp/segmentation.js could save 348B (15% reduction) after compression.
Minifying https://s.btstatic.com/lib/a28ef273b989a01a969138e174704ef6b30f800e.js?v=2 could save 284B (22% reduction) after compression.
Minifying https://www.iprimo.jp/assets_2017/js/common.js?ver=1 could save 242B (13% reduction) after compression.

priority - 0Enable 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 3KiB (62% reduction).

Compressing https://d-track.send.microad.jp/js/blade_track_jp.js could save 2.7KiB (66% reduction).
Compressing https://cdn.adnwif.smt.docomo.ne.jp/scripts/retarg…g/retargeting.js?15443 could save 252B (38% reduction).

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 1.5KiB (35% reduction).

Minifying https://www.iprimo.jp/assets_new/css/ipcheck_modal.css?ver=1 could save 1.3KiB (47% reduction) after compression.
Minifying https://www.iprimo.jp/assets_2017/css/foot.css?ver=1 could save 153B (11% 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.5KiB (14% reduction).

Minifying https://www.iprimo.jp/ could save 1,008B (13% reduction) after compression.
Minifying https://js.fout.jp/beacon.html?from=dmp could save 499B (15% reduction) after compression.

iprimo.jp Desktop Resource Breakdown

Total Resources250
Number of Hosts72
Static Resources81
JavaScript Resources51
CSS Resources9

iprimo.jp mobile page speed rank

Last tested: 2018-12-09


Mobile Speed Bad
45/100

iprimo.jp Mobile Speed Test Quick Summary


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

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

Optimize CSS Delivery of the following:

https://www.iprimo.jp/smt/assets_2017/css/common.css?ver=1
https://fast.fonts.net/t/1.css?apiType=css&project…4a47-b69c-0cf361b4f823
https://fonts.googleapis.com/css?family=Noto+Serif…00,600&subset=japanese
https://www.iprimo.jp/smt/assets_2017/css/slick.css?ver=1
https://www.iprimo.jp/smt/assets_2017/css/index-v2.css?ver=1
https://www.iprimo.jp/smt/assets_new/css/ipcheck_modal.css?ver=1

priority - 40Optimize images

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

Optimize the following images to reduce their size by 393.4KiB (55% reduction).

Compressing https://image.iprimo.jp/smt/assets_2017/img/index_v2/main201807_0.jpg could save 118.9KiB (71% reduction).
Compressing https://image.iprimo.jp/smt/assets_2017/img/index_v2/banner_tvcm2.jpg could save 94.1KiB (69% reduction).
Compressing https://image.iprimo.jp/smt/assets_2017/img/index_v2/main20181022.jpg could save 77.3KiB (51% reduction).
Compressing https://image.iprimo.jp/smt/assets_2017/img/index_v2/banner_about.jpg could save 42.6KiB (63% reduction).
Compressing https://image.iprimo.jp/smt/assets_2017/img/index_v2/banner_service.jpg could save 33.4KiB (61% reduction).
Compressing https://image.iprimo.jp/smt/assets_2017/img/index_v2/main20180901.jpg could save 17.5KiB (22% reduction).
Compressing https://image.iprimo.jp/smt/assets_2017/img/index/link03.jpg could save 4KiB (15% reduction).
Compressing https://image.iprimo.jp/smt/assets_2017/img/common/footInsta.jpg could save 2KiB (21% reduction).
Compressing https://image.iprimo.jp/smt/assets_2017/img/common/gMenuIcon10.png could save 1.7KiB (26% reduction).
Compressing https://image.iprimo.jp/smt/assets_2017/img/common/footFacebook.jpg could save 1.6KiB (12% reduction).
Compressing https://image.iprimo.jp/smt/assets_2017/img/common/instaIcon.png could save 193B (22% reduction).

priority - 10Avoid 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://iprimo.jp/
https://iprimo.jp/
https://iprimo.jp/smt/

priority - 8Leverage 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://b92.yahoo.co.jp/js/s_retargeting.js (expiration not specified)
https://s.yimg.jp/images/listing/tool/cv/conversion.js (9 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/611324…2723?v=2.8.34&r=stable (20 minutes)
https://connect.facebook.net/signals/config/611383…3977?v=2.8.34&r=stable (20 minutes)
https://js.fout.jp/segmentation.js (21.8 minutes)
https://js.fout.jp/prefs.js (26.6 minutes)
https://www.googleadservices.com/pagead/conversion.js (60 minutes)
https://www.googleadservices.com/pagead/conversion_async.js (60 minutes)
https://stats.g.doubleclick.net/dc.js (2 hours)
https://s.yjtag.jp/tag.js (4 hours)

priority - 4Reduce server response time

In our test, your server responded in 0.49 seconds.

priority - 1Minify 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 9.9KiB (20% reduction).

Minifying https://iprimo.jp/js/s_code.js could save 8KiB (19% reduction) after compression.
Minifying https://iprimo.jp/js/ppc_primo.js could save 624B (51% reduction) after compression.
Minifying https://d-track.send.microad.jp/js/blade_track_jp.js could save 584B (15% reduction).
Minifying https://js.fout.jp/segmentation.js could save 348B (15% reduction) after compression.
Minifying https://www.iprimo.jp/smt/assets_2017/js/common.js?ver=1 could save 331B (16% reduction) after compression.

priority - 0Enable 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 3KiB (62% reduction).

Compressing https://d-track.send.microad.jp/js/blade_track_jp.js could save 2.7KiB (66% reduction).
Compressing https://cdn.adnwif.smt.docomo.ne.jp/scripts/retarg…g/retargeting.js?15443 could save 252B (38% reduction).

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.2KiB (25% reduction).

Minifying https://www.iprimo.jp/smt/assets_new/css/ipcheck_modal.css?ver=1 could save 1.3KiB (47% reduction) after compression.
Minifying https://www.iprimo.jp/smt/assets_2017/css/common.css?ver=1 could save 875B (14% 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 2KiB (15% reduction).

Minifying https://iprimo.jp/smt/ could save 1.5KiB (16% reduction) after compression.
Minifying https://js.fout.jp/beacon.html?from=dmp could save 499B (15% reduction) after compression.

iprimo.jp Mobile Resource Breakdown

Total Resources185
Number of Hosts34
Static Resources67
JavaScript Resources34
CSS Resources7

iprimo.jp mobile page usability

Last tested: 2018-12-09


Mobile Usability Good
95/100

iprimo.jp Mobile Usability Test Quick Summary


priority - 3Configure the viewport

Your page specifies a fixed-width mobile viewport. Consider using a responsive viewport to allow your page to render properly on all devices.

priority - 1Size 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="/smt/marriage/rings/">結婚指輪</a> is close to 1 other tap targets.

The tap target <a href="/smt/aboutipri…e.html#_anc_02" class="_link_membership">アフターサービス&amp;会員サービス</a> and 5 others are close to other tap targets.

The tap target <a href="https://www.ip…index.php?fn=1" class="img-reserve-by-web">簡単1分 WEBでご来店予約</a> and 1 others are close to other tap targets.

The tap target <a href="/smt/shop/">Shops店舗のご案内</a> is close to 3 other tap targets.

The tap target <li id="slick-slide00" class="">1</li> and 2 others are close to other tap targets.

The tap target <button type="button">1</button> and 1 others are close to other tap targets.

The tap target <button type="button">2</button> is close to 1 other tap targets.

The tap target <a href="/smt/engagement/rings/">Engagement Ring婚約指輪</a> and 1 others are close to other tap targets.

iprimo.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: 6 Column: 1 - 49
"...)</title> <meta http-equiv="Content-Language" content="ja"> <meta..."

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

Line: 7 Column: 1 - 65
"...ent="ja"> <meta http-equiv="Content-Script-Type" content="text/javascript"> <meta..."

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

Line: 8 Column: 1 - 57
"...ascript"> <meta http-equiv="Content-Style-Type" content="text/css"> <!--[..."

An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.

Line: 113 Column: 9 - 57
"...> <img src="/assets_2017/img/index_v2/main_04.jpg"> ..." Line: 122 Column: 9 - 57
"...> <img src="/assets_2017/img/index_v2/main_01.jpg"> ..."

Element “dl” is missing a required child element.

Line: 407 Column: 19 - 22
"... <dd> ..."

The “frameborder” attribute on the “iframe” element is obsolete. Use CSS instead.

Line: 606 Column: 3 - 139
"...script> <iframe src="//b.yjtag.jp/iframe?c=pCtwSuc,DAxxIyV" width="1" height="1" frameborder="0" scrolling="no" marginheight="0" marginwidth="0"></ifra..."

The “scrolling” attribute on the “iframe” element is obsolete. Use CSS instead.

Line: 606 Column: 3 - 139
"...script> <iframe src="//b.yjtag.jp/iframe?c=pCtwSuc,DAxxIyV" width="1" height="1" frameborder="0" scrolling="no" marginheight="0" marginwidth="0"></ifra..."

The “marginheight” attribute on the “iframe” element is obsolete. Use CSS instead.

Line: 606 Column: 3 - 139
"...script> <iframe src="//b.yjtag.jp/iframe?c=pCtwSuc,DAxxIyV" width="1" height="1" frameborder="0" scrolling="no" marginheight="0" marginwidth="0"></ifra..."

The “marginwidth” attribute on the “iframe” element is obsolete. Use CSS instead.

Line: 606 Column: 3 - 139
"...script> <iframe src="//b.yjtag.jp/iframe?c=pCtwSuc,DAxxIyV" width="1" height="1" frameborder="0" scrolling="no" marginheight="0" marginwidth="0"></ifra..."

Element “style” not allowed as child of element “body” in this context. (Suppressing further errors from this subtree.)

Line: 628 Column: 1 - 23
"...27.5. --> <style type="text/css"> .bnr_..."

End tag “p” seen, but there were open elements.

Line: 651 Column: 288 - 291
"...alt="閉じる"></p> </div..."

Unclosed element “span”.

Line: 651 Column: 162 - 214
"...JECT"></a><span class="bnr_top_floating_close" title="バナーを閉じる"><img s..."

Warnings

The document is not mappable to XML 1.0 due to two consecutive hyphens in a comment.

Line: 125 Column: - 16
"... <!-- /.mv--slide --> <..." Line: 127 Column: - 40
"...lass="idx-sld--inner"> ..." Line: 131 Column: - 16
"... <!-- /.mv--slide --> <..." Line: 133 Column: - 29
"...lass="idx-sld--inner"> ..." Line: 134 Column: - 30
"...lass="idx-sld--box"> ..." Line: 135 Column: - 31
"...lass="idx-sld--title">SAMPLE2 ..." Line: 136 Column: - 30
"...lass="idx-sld--txt">リンクなし</p> ..." Line: 141 Column: - 16
"... <!-- /.mv--slide --> </d..." Line: 160 Column: - 22
"...-- /.idx-main--card --> <d..." Line: 173 Column: - 22
"...-- /.idx-main--card --> </di..." Line: 188 Column: - 22
"...-- /.idx-main--card --> <d..." Line: 201 Column: - 22
"...-- /.idx-main--card --> </di..." Line: 216 Column: - 22
"...-- /.idx-main--card --> <d..." Line: 221 Column: - 22
"...-- /.idx-main--card --> </di..." Line: 236 Column: - 22
"...-- /.idx-main--card --> <d..." Line: 249 Column: - 22
"...-- /.idx-main--card --> </di..."

The “language” attribute on the “script” element is obsolete. You can safely omit it.

Line: 612 Column: 1 - 53
"...e.com --> <script language="JavaScript" type="text/javascript"><!-- /..."

iprimo.jp similar domains

Similar domains:
www.iprimo.com
www.iprimo.net
www.iprimo.org
www.iprimo.info
www.iprimo.biz
www.iprimo.us
www.iprimo.mobi
www.primo.jp
www.iprimo.jp
www.uprimo.jp
www.iuprimo.jp
www.uiprimo.jp
www.jprimo.jp
www.ijprimo.jp
www.jiprimo.jp
www.kprimo.jp
www.ikprimo.jp
www.kiprimo.jp
www.oprimo.jp
www.ioprimo.jp
www.oiprimo.jp
www.irimo.jp
www.iorimo.jp
www.iporimo.jp
www.ilrimo.jp
www.iplrimo.jp
www.ilprimo.jp
www.ipimo.jp
www.ipeimo.jp
www.ipreimo.jp
www.iperimo.jp
www.ipdimo.jp
www.iprdimo.jp
www.ipdrimo.jp
www.ipfimo.jp
www.iprfimo.jp
www.ipfrimo.jp
www.iptimo.jp
www.iprtimo.jp
www.iptrimo.jp
www.iprmo.jp
www.iprumo.jp
www.ipriumo.jp
www.ipruimo.jp
www.iprjmo.jp
www.iprijmo.jp
www.iprjimo.jp
www.iprkmo.jp
www.iprikmo.jp
www.iprkimo.jp
www.ipromo.jp
www.ipriomo.jp
www.iproimo.jp
www.iprio.jp
www.iprino.jp
www.iprimno.jp
www.iprinmo.jp
www.iprijo.jp
www.iprimjo.jp
www.ipriko.jp
www.iprimko.jp
www.iprim.jp
www.iprimi.jp
www.iprimoi.jp
www.iprimio.jp
www.iprimk.jp
www.iprimok.jp
www.ipriml.jp
www.iprimol.jp
www.iprimlo.jp
www.iprimp.jp
www.iprimop.jp
www.iprimpo.jp

iprimo.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.


iprimo.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.