84.2 sec in total
292 ms
67.5 sec
16.3 sec
Click here to check amazing Force content for United States. Otherwise, check out these important facts you probably never knew about force.com
Personalize every experience along the customer journey with the Customer 360. Unify marketing, sales, service, commerce, and IT on the world's #1 CRM.
Visit force.comWe analyzed Force.com page load time and found that the first response time was 292 ms and then it took 83.9 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
force.com performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value21.9 s
0/100
25%
Value19.4 s
0/100
10%
Value20,660 ms
0/100
30%
Value0.123
84/100
15%
Value32.5 s
0/100
10%
292 ms
1024 ms
3950 ms
3162 ms
4299 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Force.com, 24% (23 requests) were made to C2.sfdcstatic.com and 16% (15 requests) were made to C1.sfdcstatic.com. The less responsive or slowest element that took the longest time to load (17.8 sec) relates to the external source T.co.
Page size can be reduced by 2.3 MB (63%)
3.6 MB
1.3 MB
In fact, the total size of Force.com main page is 3.6 MB. 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. Javascripts take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 373.2 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 96.1 kB, which is 23% 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 373.2 kB or 90% of the original size.
Potential reduce by 18.7 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. Force images are well optimized though.
Potential reduce by 1.4 MB
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 1.4 MB or 68% of the original size.
Potential reduce by 525.2 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. Force.com needs all CSS files to be minified and compressed as it can save up to 525.2 kB or 86% of the original size.
Number of requests can be reduced by 66 (75%)
88
22
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Force. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 41 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
force.com
292 ms
1024 ms
jquery.min.d311399a202bbfe8f6b94a4546a2a025.js
3950 ms
utils.min.3010ac293e9c3ee5e4d05561c6e817b9.js
3162 ms
granite.min.b14676fa47cce8b31155c6be3da9e810.js
4299 ms
jquery.min.d7c42e4a257b8b9fe38d1c53dd20d01a.js
4361 ms
modern.min.7b2eea6898007731c2ec2232f96726c7.js
4362 ms
clientlibs_analytics_top.min.0b855f66fc64f3d45c8e2dab7820f50d.js
3275 ms
clientlibs_target_mbox.min.a9511707130c4ab21a1e0980a2c00ff4.js
3760 ms
clientlibs_target.min.d3361a6371d57734a92c480aea90a69f.js
5317 ms
util.min.1635d0ebcdfe3d94bc77738938b9688e.js
3721 ms
init.min.39d4e72a0860bf570742093e197a1609.js
3721 ms
satelliteLib-eb844e404d0d734b7f9841b393b34585463d72b4.js
5277 ms
clientlibs_base.min.22dbf0c1f969063dbb2ea2d9bcec0e2d.css
3720 ms
clientlibs_framework.min.b3e7e4fd744d0b879a70986bac723def.css
3715 ms
clientlibs_base.min.3cb4842ace5dee3543cc2f2cb5c5400c.css
4206 ms
clientlibs_newrelic.min.7d40a47fc3896687c6fefb3070d0259f.js
5230 ms
shared.min.382b2b1228aed143f42df767d3f1d3de.js
5289 ms
kernel.min.4c82f83ebcf6ed4a6ee4836c155f341d.js
5287 ms
clientlibs_analytics_bottom.min.1236b5c1e29c26e66f7a96024610d48d.js
5206 ms
clientlibs_base.min.6a46789d2f8dbc07d02d07ca3b016137.js
5205 ms
clientlibs_yall.min.ded48a3646073cb853f8f12e703c27ab.js
5206 ms
clientlibs_base.min.8f90c63b6aba389d20ff826cbca3096b.js
5147 ms
clientlibs_mouseflow.min.c7ed116971b905e9db1529b89b3480d6.js
5205 ms
token.json
1219 ms
ip.json
1242 ms
target.js
1191 ms
id
820 ms
rd
444 ms
id
216 ms
ajax
2001 ms
salesforce-logo.png
325 ms
salesforce-logo-cloud.png
66 ms
spacer.gif
560 ms
resource-force-com-security-benefit.jpg
726 ms
resource-force-com-lightning-benefit.jpg
471 ms
rxr05acqt.js
1119 ms
cse.js
1516 ms
SalesforceSans-Regular.woff
356 ms
controltag.js.1c86c30cac854ccdacab6e3099f5b9ee
1546 ms
jsapi
4053 ms
opinionlab-white.gif
2674 ms
salesforce-icons.ttf
2557 ms
SalesforceSans-Thin.woff
1811 ms
SalesforceSans-Bold.woff
1784 ms
SalesforceSans-Light.woff
1783 ms
proxy.3d2100fd7107262ecb55ce6847f01fa5.html
1030 ms
default+en.css
745 ms
default.css
551 ms
default+en.I.js
3992 ms
optout_check
1446 ms
get
864 ms
pixel
1394 ms
adsct
16478 ms
adsct
17802 ms
15332 ms
satellite-57eda13564746d28e2004335.js
680 ms
pnapi_integration.min.js
584 ms
satellite-5809971b64746d4cc800708e.js
1636 ms
satellite-58815a2564746d6199003201.js
1719 ms
pixel
3937 ms
pixel
13381 ms
pixel
14392 ms
pixel
13379 ms
analytics.js
16252 ms
livechat-waterfall-agent.html
13251 ms
get
12880 ms
ga360.js
11454 ms
activity;src=2382028;type=sales555;cat=retar915;ord=8882343654986.47
13165 ms
logo-salesforce.svg
8206 ms
icon-login-astro@2x.png
8205 ms
map_number.jsonp
5843 ms
trailhead-app-building-force.jpg
2004 ms
hero-force-com.jpg
2004 ms
3904 ms
tr
3586 ms
tr
3586 ms
pixel
2004 ms
2384 ms
2646 ms
s75730217203963
1928 ms
male-1-large@2x.jpg
1927 ms
out
1569 ms
1071772740
1550 ms
tr
1079 ms
1929 ms
2004 ms
pixel
3474 ms
collect
2379 ms
collect
2378 ms
id
841 ms
ga-audiences
228 ms
in
225 ms
nr-768.min.js
10436 ms
async-ads.js
10051 ms
googlelogo_grey_46x15dp.png
9985 ms
force.com accessibility score
force.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
force.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Force.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Force.com 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.
force.com
Open Graph data is detected on the main page of Force. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: