SANSAN.COM Business Card-based Contact Management for Companies | Sansan


sansan.com website information.

sansan.com domain name is registered by .COM top-level domain registry. See the other sites registred in .COM domain zone.

No name server records were found.

and probably website sansan.com 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 sansan.com position was 3245 (in the world). The lowest Alexa rank position was 996489. Now website sansan.com ranked in Alexa database as number 248753 (in the world).

Website sansan.com Desktop speed measurement score (58/100) is better than the results of 33.06% of other sites shows that the page desktop performance can be improved.

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

Mobile speed measurement score of sansan.com (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

DateRankChange
Mar-28-2024 248,753-10,385
Mar-27-2024 238,3685,117
Mar-26-2024 243,485-7,122
Mar-25-2024 236,3634,080
Mar-24-2024 240,443-22,032
Mar-23-2024 218,41112,510
Mar-22-2024 230,921-12,543

Advertisement

sansan.com 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.



sansan.com 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.


Domain Name: SANSAN.COM
Registry Domain ID: 85419078_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.discount-domain.com
Registrar URL: http://gmo.jp
Updated Date: 2021-03-24T15:22:04Z
Creation Date: 2002-04-09T18:06:49Z
Registry Expiry Date: 2022-04-09T18:06:49Z
Registrar: GMO Internet, Inc. d/b/a Onamae.com
Registrar IANA ID: 49
Registrar Abuse Contact Email: abuse@gmo.jp
Registrar Abuse Contact Phone: +81.337709199
Domain Status: ok https://icann.org/epp#ok
Name Server: NS-1295.AWSDNS-33.ORG
Name Server: NS-1982.AWSDNS-55.CO.UK
Name Server: NS-241.AWSDNS-30.COM
Name Server: NS-623.AWSDNS-13.NET
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2021-04-26T22:18:43Z

sansan.com server information

Servers Location

IP Address
Country
Region
City

sansan.com desktop page speed rank

Last tested: 2019-12-11


Desktop Speed Bad
58/100

sansan.com Desktop Speed Test Quick Summary


priority - 31 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 303.7KiB (32% reduction).

Compressing https://www.sansan.com/common/img/home/img_device.svg could save 250.6KiB (28% reduction).
Compressing https://www.sansan.com/sg/wp/wp-includes/css/dist/…tyle.min.css?ver=5.0.7 could save 20.9KiB (83% reduction).
Compressing https://www.sansan.com/common/css/styles.css?date=201912110303 could save 11.3KiB (76% reduction).
Compressing https://www.sansan.com/sg/ could save 9.3KiB (67% reduction).
Compressing https://www.sansan.com/common/js/pages/home.js could save 2.9KiB (77% reduction).
Compressing https://www.sansan.com/common/js/common.js could save 2.3KiB (61% reduction).
Compressing https://www.sansan.com/common/img/common/sansan_logo.svg could save 2.1KiB (65% reduction).
Compressing https://www.sansan.com/common/css/pages/home.css?date=201912110303 could save 1.6KiB (68% reduction).
Compressing https://www.sansan.com/common/js/modernizr.custom.svg.js could save 760B (48% reduction).
Compressing https://www.sansan.com/sg/wp/wp-content/plugins/wo…/css/wpp.css?ver=4.2.2 could save 686B (56% reduction).
Compressing https://www.sansan.com/sg/wp/wp-includes/js/wp-embed.min.js?ver=5.0.7 could save 650B (47% reduction).
Compressing https://www.sansan.com/sg/wp/wp-content/plugins/wo…4.2.0.min.js?ver=4.2.2 could save 566B (50% reduction).

priority - 16 Optimize images

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

Optimize the following images to reduce their size by 157.3KiB (38% reduction).

Compressing https://www.sansan.com/common/img/common/bg_mv_01.png could save 51.1KiB (40% reduction).
Compressing https://www.sansan.com/common/img/home/bg_card_en.png could save 48KiB (34% reduction).
Compressing https://www.sansan.com/common/img/common/bg_mv_02.png could save 41KiB (46% reduction).
Compressing https://www.sansan.com/common/img/home/img_intro_02.png could save 1.7KiB (28% reduction).
Compressing https://www.sansan.com/common/img/common/logo_jppost.png could save 1.7KiB (34% reduction).
Compressing https://www.sansan.com/common/img/common/logo_toyota.png could save 1.6KiB (23% reduction).
Compressing and resizing https://www.sansan.com/common/img/common/icon_lang_change.png could save 1.4KiB (63% reduction).
Compressing https://www.sansan.com/common/img/common/logo_zendesk.png could save 1.4KiB (34% reduction).
Compressing https://www.sansan.com/common/img/common/logo_voice_lenovo.png could save 1.3KiB (26% reduction).
Compressing and resizing https://www.sansan.com/common/img/common/icon_footer_sns_youtube.png could save 1.2KiB (75% reduction).
Compressing https://www.sansan.com/common/img/home/img_intro_03.png could save 1.1KiB (32% reduction).
Compressing https://www.sansan.com/common/img/common/logo_sap.png could save 1,015B (23% reduction).
Compressing and resizing https://www.sansan.com/common/img/common/icon_footer_sns_twitter.png could save 976B (72% reduction).
Compressing https://www.sansan.com/common/img/common/logo_seven.png could save 888B (23% reduction).
Compressing https://www.sansan.com/common/img/common/logo_konica.png could save 881B (19% reduction).
Compressing and resizing https://www.sansan.com/common/img/common/icon_footer_sns_linkedin.png could save 625B (72% reduction).
Compressing https://www.sansan.com/common/img/common/logo_avnet.png could save 580B (40% reduction).
Compressing https://www.sansan.com/common/img/home/img_intro_01.png could save 532B (19% reduction).
Compressing and resizing https://www.sansan.com/common/img/common/icon_footer_sns_facebook.png could save 340B (65% reduction).

priority - 14 Reduce server response time

In our test, your server responded in 1.6 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 - 8 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking script resources and 5 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://www.sansan.com/sg/wp/wp-content/plugins/wo…4.2.0.min.js?ver=4.2.2

Optimize CSS Delivery of the following:

https://www.sansan.com/sg/wp/wp-includes/css/dist/…tyle.min.css?ver=5.0.7
https://www.sansan.com/sg/wp/wp-content/plugins/wo…/css/wpp.css?ver=4.2.2
https://fonts.googleapis.com/css?family=Lato:100,1…400i,700,700i,900,900i
https://www.sansan.com/common/css/styles.css?date=201912110303
https://www.sansan.com/common/css/pages/home.css?date=201912110303

priority - 5 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://munchkin.marketo.net/munchkin.js (expiration not specified)
https://js.hs-scripts.com/4907834.js (60 seconds)
https://js.hs-analytics.net/analytics/1576076400000/4907834.js (5 minutes)
https://js.usemessages.com/conversations-embed.js (10 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-P7H5WWT (15 minutes)
https://amplify.outbrain.com/cp/obtp.js (20 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/277276…4587?v=2.9.14&r=stable (20 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://cs.nakanohito.jp/b3/bi.js (3 hours)

priority - 3 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://sansan.com/
https://www.sansan.com/
https://www.sansan.com/sg/

priority - 1 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 5.7KiB (32% reduction).

Minifying https://www.sansan.com/common/css/styles.css?date=201912110303 could save 4.3KiB (30% reduction).
Minifying https://www.sansan.com/sg/wp/wp-content/plugins/wo…/css/wpp.css?ver=4.2.2 could save 853B (70% reduction).
Minifying https://www.sansan.com/common/css/pages/home.css?date=201912110303 could save 615B (25% reduction).

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 2.9KiB (21% reduction).

Minifying https://www.sansan.com/sg/ could save 2.9KiB (21% reduction).

priority - 0 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 2.9KiB (36% reduction).

Minifying https://www.sansan.com/common/js/pages/home.js could save 1.5KiB (39% reduction).
Minifying https://www.sansan.com/common/js/common.js could save 1.2KiB (35% reduction).
Minifying https://munchkin.marketo.net/munchkin.js could save 148B (20% reduction) after compression.

sansan.com Desktop Resources

Total Resources70
Number of Hosts27
Static Resources47
JavaScript Resources19
CSS Resources5

sansan.com Desktop Resource Breakdown

sansan.com mobile page speed rank

Last tested: 2019-12-14


Mobile Speed Bad
46/100

sansan.com Mobile Speed Test Quick Summary


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

Compressing https://www.sansan.com/common/img/home/img_device.svg could save 250.6KiB (28% reduction).
Compressing https://www.sansan.com/sg/sp/wp/wp-includes/css/di…tyle.min.css?ver=5.0.8 could save 20.9KiB (83% reduction).
Compressing https://www.sansan.com/sp/common/css/styles.css?date=201912140700 could save 12.9KiB (76% reduction).
Compressing https://www.sansan.com/sg/sp/ could save 10.6KiB (69% reduction).
Compressing https://www.sansan.com/sp/common/js/jquery.easing.1.3.js could save 6KiB (75% reduction).
Compressing https://www.sansan.com/sp/common/js/common.js?v=160920 could save 3.1KiB (66% reduction).
Compressing https://www.sansan.com/sp/common/css/pages/home.css?date=201912140700 could save 2.8KiB (71% reduction).
Compressing https://www.sansan.com/common/img/common/sansan_logo.svg could save 2.1KiB (65% reduction).
Compressing https://www.sansan.com/sp/common/js/jquery.lazyload.min.js could save 2KiB (61% reduction).
Compressing https://www.sansan.com/sp/common/css/idangerous.swiper.css could save 1.1KiB (74% reduction).
Compressing https://www.sansan.com/sp/common/js/modernizr.custom.svg.js could save 760B (48% reduction).
Compressing https://www.sansan.com/sg/sp/wp/wp-content/plugins…/css/wpp.css?ver=4.2.2 could save 686B (56% reduction).
Compressing https://www.sansan.com/sg/sp/wp/wp-includes/js/wp-embed.min.js?ver=5.0.8 could save 650B (47% reduction).
Compressing https://www.sansan.com/sg/sp/wp/wp-content/plugins…4.2.0.min.js?ver=4.2.2 could save 566B (50% reduction).
Compressing https://www.sansan.com/sp/common/js/home.js could save 299B (41% reduction).
Compressing https://www.sansan.com/sp/common/js/jquery.easingscroll.js could save 163B (37% reduction).

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

Your page has 1 blocking script resources and 6 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://www.sansan.com/sg/sp/wp/wp-content/plugins…4.2.0.min.js?ver=4.2.2

Optimize CSS Delivery of the following:

https://www.sansan.com/sg/sp/wp/wp-includes/css/di…tyle.min.css?ver=5.0.8
https://www.sansan.com/sg/sp/wp/wp-content/plugins…/css/wpp.css?ver=4.2.2
https://fonts.googleapis.com/css?family=Roboto:100…00italic,700,700italic
https://www.sansan.com/sp/common/css/styles.css?date=201912140700
https://www.sansan.com/sp/common/css/idangerous.swiper.css
https://www.sansan.com/sp/common/css/pages/home.css?date=201912140700

priority - 22 Reduce server response time

In our test, your server responded in 1.7 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 - 19 Avoid landing page redirects

Your page has 3 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://sansan.com/
https://www.sansan.com/
https://www.sansan.com/sp/
https://www.sansan.com/sg/sp/

priority - 15 Optimize images

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

Optimize the following images to reduce their size by 149.8KiB (38% reduction).

Compressing https://www.sansan.com/sp/common/img/common/bg_mv_01.png could save 51.1KiB (40% reduction).
Compressing https://www.sansan.com/common/img/home/bg_card_en.png could save 48KiB (34% reduction).
Compressing https://www.sansan.com/sp/common/img/common/bg_mv_02.png could save 41KiB (46% reduction).
Compressing https://www.sansan.com/common/img/home/img_intro_02.png could save 1.7KiB (28% reduction).
Compressing https://www.sansan.com/sp/common/img/home/logo_img_jp_post.png could save 1.7KiB (34% reduction).
Compressing https://www.sansan.com/common/img/common/logo_voice_lenovo.png could save 1.3KiB (26% reduction).
Compressing https://www.sansan.com/common/img/home/img_intro_03.png could save 1.1KiB (32% reduction).
Compressing https://www.sansan.com/sp/common/img/home/logo_img_zendesk.png could save 776B (29% reduction).
Compressing https://www.sansan.com/sp/common/img/home/logo_img_avnet.png could save 565B (44% reduction).
Compressing https://www.sansan.com/common/img/home/img_intro_01.png could save 532B (19% reduction).
Compressing https://www.sansan.com/common/img/common/icon_footer_sns_youtube.png could save 474B (31% reduction).
Compressing https://www.sansan.com/common/img/common/icon_footer_sns_twitter.png could save 443B (34% reduction).
Compressing https://www.sansan.com/common/img/common/icon_lang_change.png could save 431B (19% reduction).
Compressing https://www.sansan.com/common/img/common/icon_footer_sns_linkedin.png could save 331B (39% reduction).
Compressing https://www.sansan.com/common/img/common/icon_footer_sns_facebook.png could save 235B (46% reduction).

priority - 7 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://munchkin.marketo.net/munchkin.js (expiration not specified)
https://js.hs-scripts.com/4907834.js (60 seconds)
https://js.hs-analytics.net/analytics/1576306800000/4907834.js (5 minutes)
https://js.usemessages.com/conversations-embed.js (10 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-P7H5WWT (15 minutes)
https://amplify.outbrain.com/cp/obtp.js (20 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/277276…4587?v=2.9.15&r=stable (20 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://cs.nakanohito.jp/b3/bi.js (3 hours)

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

Minifying https://www.sansan.com/sp/common/js/jquery.easing.1.3.js could save 4.4KiB (55% reduction).
Minifying https://www.sansan.com/sp/common/js/common.js?v=160920 could save 1.5KiB (33% reduction).
Minifying https://www.sansan.com/sp/common/js/home.js could save 737B (100% reduction).
Minifying https://www.sansan.com/sp/common/js/jquery.easingscroll.js could save 152B (35% reduction).
Minifying https://munchkin.marketo.net/munchkin.js could save 148B (20% reduction) after compression.
Minifying https://js.hs-scripts.com/4907834.js could save 104B (22% reduction) after compression.

priority - 1 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 6.7KiB (31% reduction).

Minifying https://www.sansan.com/sp/common/css/styles.css?date=201912140700 could save 4.3KiB (26% reduction).
Minifying https://www.sansan.com/sp/common/css/pages/home.css?date=201912140700 could save 1.6KiB (41% reduction).
Minifying https://www.sansan.com/sg/sp/wp/wp-content/plugins…/css/wpp.css?ver=4.2.2 could save 853B (70% reduction).

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 3.1KiB (21% reduction).

Minifying https://www.sansan.com/sg/sp/ could save 3.1KiB (21% reduction).

sansan.com Mobile Resources

Total Resources74
Number of Hosts27
Static Resources51
JavaScript Resources22
CSS Resources6

sansan.com Mobile Resource Breakdown

sansan.com mobile page usability

Last tested: 2019-12-14


Mobile Usability Good
100/100

sansan.com similar domains

Similar domains:
www.sansan.com
www.sansan.net
www.sansan.org
www.sansan.info
www.sansan.biz
www.sansan.us
www.sansan.mobi
www.ansan.com
www.sansan.com
www.wansan.com
www.swansan.com
www.wsansan.com
www.eansan.com
www.seansan.com
www.esansan.com
www.dansan.com
www.sdansan.com
www.dsansan.com
www.zansan.com
www.szansan.com
www.zsansan.com
www.xansan.com
www.sxansan.com
www.xsansan.com
www.aansan.com
www.saansan.com
www.asansan.com
www.snsan.com
www.sqnsan.com
www.saqnsan.com
www.sqansan.com
www.swnsan.com
www.sawnsan.com
www.ssnsan.com
www.sasnsan.com
www.ssansan.com
www.sznsan.com
www.saznsan.com
www.sasan.com
www.sabsan.com
www.sanbsan.com
www.sabnsan.com
www.sahsan.com
www.sanhsan.com
www.sahnsan.com
www.sajsan.com
www.sanjsan.com
www.sajnsan.com
www.samsan.com
www.sanmsan.com
www.samnsan.com
www.sanan.com
www.sanwan.com
www.sanswan.com
www.sanwsan.com
www.sanean.com
www.sansean.com
www.sanesan.com
www.sandan.com
www.sansdan.com
www.sandsan.com
www.sanzan.com
www.sanszan.com
www.sanzsan.com
www.sanxan.com
www.sansxan.com
www.sanxsan.com
www.sanaan.com
www.sansaan.com
www.sanasan.com
www.sansn.com
www.sansqn.com
www.sansaqn.com
www.sansqan.com
www.sanswn.com
www.sansawn.com
www.sanssn.com
www.sansasn.com
www.sanssan.com
www.sanszn.com
www.sansazn.com
www.sansa.com
www.sansab.com
www.sansanb.com
www.sansabn.com
www.sansah.com
www.sansanh.com
www.sansahn.com
www.sansaj.com
www.sansanj.com
www.sansajn.com
www.sansam.com
www.sansanm.com
www.sansamn.com
www.sansan.con

sansan.com 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.


sansan.com 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.