Tools & Wizards About Us
success.salesforce.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

success.salesforce.co.jp

Salesforce ユーザ向け活用支援サイト - サクセスナレッジ

Page Load Speed

4.6 sec in total

First Response

885 ms

Resources Loaded

3.6 sec

Page Rendered

166 ms

success.salesforce.co.jp screenshot

About Website

Click here to check amazing Success Salesforce content for Japan. Otherwise, check out these important facts you probably never knew about success.salesforce.co.jp

クラウド型CRMサービス、Salesforce（セールスフォース）は企業の規模を問わず、あらゆる業種でご利用いただけます。このサイトでは、Salesforce 活用方法、ツールの定着化、セミナー情報をご紹介します。

Visit success.salesforce.co.jp

Key Findings

We analyzed Success.salesforce.co.jp page load time and found that the first response time was 885 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

success.salesforce.co.jp performance score

0

Network Requests Diagram

success.salesforce.co.jp

885 ms

successjp.salesforce.com

932 ms

sfRoot.css

324 ms

ui.tabs.css

331 ms

jquery.js

670 ms

Our browser made a total of 115 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Success.salesforce.co.jp, 35% (40 requests) were made to Successjp.salesforce.com and 29% (33 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (958 ms) relates to the external source Successjp.salesforce.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 258.1 kB (32%)

Content Size

818.8 kB

After Optimization

560.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Success.salesforce.co.jp main page is 818.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 461.8 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 24.1 kB

  • Original 31.8 kB
  • After minification 25.0 kB
  • After compression 7.8 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 6.8 kB, which is 21% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 24.1 kB or 76% of the original size.

Image Optimization

-4%

Potential reduce by 20.5 kB

  • Original 461.8 kB
  • After minification 441.4 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Success Salesforce images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 154.5 kB

  • Original 254.1 kB
  • After minification 216.8 kB
  • After compression 99.6 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 154.5 kB or 61% of the original size.

CSS Optimization

-83%

Potential reduce by 59.1 kB

  • Original 71.0 kB
  • After minification 61.3 kB
  • After compression 11.9 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Success.salesforce.co.jp needs all CSS files to be minified and compressed as it can save up to 59.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 67 (60%)

Requests Now

111

After Optimization

44

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Success Salesforce. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

success.salesforce.co.jp

success.salesforce.co.jp

885 ms

successjp.salesforce.com

successjp.salesforce.com

932 ms

sfRoot.css

sfRoot.css

324 ms

ui.tabs.css

ui.tabs.css

331 ms

jquery.js

jquery.js

670 ms

sfCommon.js

sfCommon.js

348 ms

ui.core.js

ui.core.js

539 ms

ui.tabs.pack.js

ui.tabs.pack.js

483 ms

s_code.js

s_code.js

819 ms

flexslider.css

flexslider.css

516 ms

jquery.flexslider.js

jquery.flexslider.js

553 ms

sfLayout.css

sfLayout.css

323 ms

sfTop.css

sfTop.css

365 ms

sfContent.css

sfContent.css

398 ms

s_retargeting.js

s_retargeting.js

578 ms

conversion.js

conversion.js

17 ms

switch-view.js

switch-view.js

373 ms

bodyBg.gif

bodyBg.gif

247 ms

siteID.png

siteID.png

189 ms

siteLogo2.png

siteLogo2.png

188 ms

delimiter.gif

delimiter.gif

221 ms

btnLogin.png

btnLogin.png

188 ms

crc_603x125_banner_resources.png

crc_603x125_banner_resources.png

362 ms

crc_603x125_banner_spring16.png

crc_603x125_banner_spring16.png

755 ms

bnr_userGroup.png

bnr_userGroup.png

377 ms

bnr_guide.png

bnr_guide.png

399 ms

bgTabs.gif

bgTabs.gif

360 ms

bgListFoot.gif

bgListFoot.gif

455 ms

bgListHead.gif

bgListHead.gif

720 ms

bgListCont.gif

bgListCont.gif

721 ms

dotline.gif

dotline.gif

719 ms

linkBtnR.gif

linkBtnR.gif

721 ms

linkBtnL.gif

linkBtnL.gif

753 ms

bnr_youtube.png

bnr_youtube.png

773 ms

widgets.js

widgets.js

10 ms

bgSearch.gif

bgSearch.gif

704 ms

searchBox.gif

searchBox.gif

724 ms

btnSearch.gif

btnSearch.gif

790 ms

icoTwitter.gif

icoTwitter.gif

958 ms

icoFacebook.gif

icoFacebook.gif

863 ms

icoYoutube.gif

icoYoutube.gif

840 ms

s15253977556712

s15253977556712

49 ms

56 ms

likebox.php

likebox.php

332 ms

ga.js

ga.js

55 ms

57 ms

stats

stats

567 ms

__utm.gif

__utm.gif

50 ms

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

37 ms

bgTab.gif

bgTab.gif

793 ms

bgTabEvent.gif

bgTabEvent.gif

791 ms

syndication

syndication

80 ms

351940442868293634

351940442868293634

456 ms

410ucuAGgaJ.css

410ucuAGgaJ.css

48 ms

pERLJfhzcxv.css

pERLJfhzcxv.css

40 ms

Czh0gDTFcBt.css

Czh0gDTFcBt.css

45 ms

EoarYgA68t4.css

EoarYgA68t4.css

61 ms

Ek6lpayKeeB.css

Ek6lpayKeeB.css

51 ms

5VZ003vMUZg.css

5VZ003vMUZg.css

67 ms

dAhyk4_vXRy.css

dAhyk4_vXRy.css

58 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

79 ms

FJmpeSpHpjS.js

FJmpeSpHpjS.js

78 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

104 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

101 ms

njO1TPvGzoR.js

njO1TPvGzoR.js

102 ms

1QuX41zDRrx.js

1QuX41zDRrx.js

100 ms

Oagsvfb4VWi.js

Oagsvfb4VWi.js

101 ms

LTv6ZK-5zxz.js

LTv6ZK-5zxz.js

110 ms

1FCa-btixu2.js

1FCa-btixu2.js

128 ms

IjqSyiwKeaX.js

IjqSyiwKeaX.js

127 ms

yasHAKDGNFx.js

yasHAKDGNFx.js

133 ms

n6VgtouijQL.js

n6VgtouijQL.js

139 ms

7BE0CZr3HTs.js

7BE0CZr3HTs.js

141 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

144 ms

_UYztdBNTjs.js

_UYztdBNTjs.js

144 ms

kvx5eeRG4FE.js

kvx5eeRG4FE.js

147 ms

Nn19HjwCsOL.js

Nn19HjwCsOL.js

139 ms

12662713_10153284096596078_1651774181211845541_n.png

12662713_10153284096596078_1651774181211845541_n.png

162 ms

safe_image.php

safe_image.php

230 ms

b8XhdWI9eAN.js

b8XhdWI9eAN.js

51 ms

safe_image.php

safe_image.php

98 ms

safe_image.php

safe_image.php

113 ms

10702202_10152331234416078_3494809188791885743_n.png

10702202_10152331234416078_3494809188791885743_n.png

79 ms

892_10153369090221078_3737451041363528498_n.png

892_10153369090221078_3737451041363528498_n.png

78 ms

12378651_10153360057776078_572930848_n.jpg

12378651_10153360057776078_572930848_n.jpg

84 ms

HEyyDkPknAC.png

HEyyDkPknAC.png

41 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

40 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

55 ms

QDwYpIaRyfG.png

QDwYpIaRyfG.png

49 ms

l5aPruN9xMM.png

l5aPruN9xMM.png

49 ms

K_65vAc89SX.png

K_65vAc89SX.png

84 ms

K00K-UgnsKu.png

K00K-UgnsKu.png

79 ms

VIr_vdW2.jpg

VIr_vdW2.jpg

148 ms

2757.png

2757.png

114 ms

proxy.jpg

proxy.jpg

148 ms

CdOJ116UYAAKVHV.jpg

CdOJ116UYAAKVHV.jpg

122 ms

1f338.png

1f338.png

122 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

28 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

42 ms

-0u_onqo_normal.jpg

-0u_onqo_normal.jpg

187 ms

cC-myOS__normal.jpeg

cC-myOS__normal.jpeg

56 ms

S_rnjzja_normal.jpg

S_rnjzja_normal.jpg

66 ms

53so6taE_normal.jpg

53so6taE_normal.jpg

55 ms

yQeO5gog_normal.jpg

yQeO5gog_normal.jpg

63 ms

RHVxek2Q_normal.jpg

RHVxek2Q_normal.jpg

63 ms

CdtlzA_UsAEB87H.jpg:small

CdtlzA_UsAEB87H.jpg:small

186 ms

CdoMwZ1VIAARZSP.jpg:small

CdoMwZ1VIAARZSP.jpg:small

63 ms

CdZVGvxVIAAGkzv.jpg:small

CdZVGvxVIAAGkzv.jpg:small

67 ms

default_profile_5_normal.png

default_profile_5_normal.png

50 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

14 ms

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

72 ms

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

67 ms

flexslider-icon.woff

flexslider-icon.woff

231 ms

proxy.jpg

proxy.jpg

9 ms

jot.html

jot.html

2 ms

SEO Factors

success.salesforce.co.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Success.salesforce.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Success.salesforce.co.jp main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

success.salesforce.co.jp

Open Graph description is not detected on the main page of Success Salesforce. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: