8.5 sec in total
2.9 sec
5.1 sec
442 ms
Welcome to appexchange.salesforce.com homepage info - get ready to check App Exchange Salesforce best content for United States right away, or after learning these important things about appexchange.salesforce.com
The AppExchange is the business app store from Salesforce. Our business app store features thousands of enterprise and small business applications for all functions of business: sales, email, marketin...
Visit appexchange.salesforce.comWe analyzed Appexchange.salesforce.com page load time and found that the first response time was 2.9 sec and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
appexchange.salesforce.com performance score
name
value
score
weighting
Value2.2 s
78/100
10%
Value5.9 s
14/100
25%
Value4.2 s
77/100
10%
Value2,070 ms
7/100
30%
Value1.327
0/100
15%
Value7.7 s
45/100
10%
2889 ms
19 ms
101 ms
28 ms
29 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 81% of them (87 requests) were addressed to the original Appexchange.salesforce.com, 6% (6 requests) were made to D.adroll.com and 5% (5 requests) were made to Graph.facebook.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Appexchange.salesforce.com.
Page size can be reduced by 716.8 kB (42%)
1.7 MB
1.0 MB
In fact, the total size of Appexchange.salesforce.com main page is 1.7 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. 65% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 374.1 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 89.3 kB, which is 19% 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 374.1 kB or 78% of the original size.
Potential reduce by 195.8 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. Obviously, App Exchange Salesforce needs image optimization as it can save up to 195.8 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 146.8 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 146.8 kB or 66% of the original size.
Number of requests can be reduced by 14 (15%)
95
81
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of App Exchange 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 10 to 1 for JavaScripts and as a result speed up the page load time.
appexchange.salesforce.com
2889 ms
stub.js
19 ms
3_3_3.Finalorg.ajax4jsf.javascript.AjaxScript
101 ms
SfdcCore.js
28 ms
picklist.js
29 ms
VFState.js
27 ms
styleAppex.css
34 ms
styleComty1.css
32 ms
styleComty2.css
36 ms
appxheadCombined.js
35 ms
pixel
178 ms
pixel
196 ms
pixel
197 ms
appex-logo.png
58 ms
sprite-icons.png
63 ms
p1200x1.gif
59 ms
p.gif
60 ms
listing-bar.png
61 ms
servlet.FileDownload
115 ms
rating-stars.png
63 ms
sprite-large.png
63 ms
servlet.FileDownload
133 ms
servlet.FileDownload
107 ms
servlet.FileDownload
212 ms
servlet.FileDownload
217 ms
servlet.FileDownload
226 ms
servlet.FileDownload
268 ms
servlet.FileDownload
296 ms
servlet.FileDownload
299 ms
servlet.FileDownload
358 ms
servlet.FileDownload
317 ms
servlet.FileDownload
320 ms
servlet.FileDownload
371 ms
servlet.FileDownload
434 ms
servlet.FileDownload
396 ms
servlet.FileDownload
412 ms
servlet.FileDownload
421 ms
servlet.FileDownload
494 ms
servlet.FileDownload
1061 ms
servlet.FileDownload
497 ms
servlet.FileDownload
2164 ms
servlet.FileDownload
625 ms
servlet.FileDownload
646 ms
servlet.FileDownload
1058 ms
SalesforceSans-Regular.woff
497 ms
SalesforceSans-Bold.woff
476 ms
appxBodyCombined.js
476 ms
omniture_appexchange.js
574 ms
servlet.FileDownload
1010 ms
servlet.FileDownload
1009 ms
servlet.FileDownload
1008 ms
servlet.FileDownload
1007 ms
SalesforceSans-Light.woff
1005 ms
servlet.FileDownload
959 ms
servlet.FileDownload
954 ms
servlet.FileDownload
938 ms
servlet.FileDownload
935 ms
servlet.FileDownload
920 ms
servlet.FileDownload
909 ms
servlet.FileDownload
861 ms
servlet.FileDownload
911 ms
servlet.FileDownload
974 ms
servlet.FileDownload
909 ms
servlet.FileDownload
854 ms
servlet.FileDownload
853 ms
pixel
925 ms
loading.gif
516 ms
loading-mini.gif
514 ms
loading-small.gif
524 ms
loading-small-white.gif
521 ms
loading-medium.gif
527 ms
loading-save-mini.gif
528 ms
loading-save-small.gif
548 ms
graph.facebook.com
287 ms
graph.facebook.com
460 ms
graph.facebook.com
478 ms
graph.facebook.com
478 ms
graph.facebook.com
480 ms
elqCfg.min.js
145 ms
113 ms
CB4N2L52HBA6JEK64P3DY5
102 ms
seg
105 ms
CB4N2L52HBA6JEK64P3DY5
107 ms
servlet.FileDownload
313 ms
servlet.FileDownload
296 ms
servlet.FileDownload
241 ms
servlet.FileDownload
264 ms
servlet.FileDownload
345 ms
servlet.FileDownload
377 ms
servlet.FileDownload
582 ms
servlet.FileDownload
428 ms
servlet.FileDownload
453 ms
servlet.FileDownload
587 ms
servlet.FileDownload
749 ms
servlet.FileDownload
759 ms
footer-graph-1.png
506 ms
footer-graph-2.png
515 ms
out
10 ms
60 ms
pixel
51 ms
pixel
40 ms
s75857901917770
10 ms
in
4 ms
in
5 ms
insight.min.js
27 ms
17 ms
l
30 ms
appexchange.salesforce.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
appexchange.salesforce.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
appexchange.salesforce.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Appexchange.salesforce.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Appexchange.salesforce.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.
appexchange.salesforce.com
Open Graph description is not detected on the main page of App Exchange 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: