3 sec in total
63 ms
1.9 sec
971 ms
Click here to check amazing Einstein content for United States. Otherwise, check out these important facts you probably never knew about einstein.com
Learn how artificial intelligence can turn your customer data into business insights with powerful Salesforce Einstein ai software.
Visit einstein.comWe analyzed Einstein.com page load time and found that the first response time was 63 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
einstein.com performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value8.1 s
2/100
25%
Value9.7 s
10/100
10%
Value6,850 ms
0/100
30%
Value0.245
51/100
15%
Value20.7 s
2/100
10%
63 ms
455 ms
151 ms
261 ms
271 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Einstein.com, 81% (46 requests) were made to Salesforce.com and 5% (3 requests) were made to A.sfdcstatic.com. The less responsive or slowest element that took the longest time to load (725 ms) relates to the external source Salesforce.com.
Page size can be reduced by 296.8 kB (49%)
611.2 kB
314.4 kB
In fact, the total size of Einstein.com main page is 611.2 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. 80% 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 280.5 kB which makes up the majority of the site volume.
Potential reduce by 105.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 31.8 kB, which is 26% 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 105.2 kB or 86% of the original size.
Potential reduce by 0 B
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. Einstein images are well optimized though.
Potential reduce by 134.4 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 134.4 kB or 48% of the original size.
Potential reduce by 57.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. Einstein.com needs all CSS files to be minified and compressed as it can save up to 57.2 kB or 39% of the original size.
Number of requests can be reduced by 38 (78%)
49
11
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Einstein. 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 8 to 1 for CSS and as a result speed up the page load time.
einstein.com
63 ms
455 ms
otSDKStub.js
151 ms
17965891249
261 ms
evergage.min.js
271 ms
sfdc_jquery.min.d6ea05d15a13f90cbddc2a00c4eb5f05.js
135 ms
all.bundle.e867c2dc6805b5f7c7a5.css
206 ms
clientlibs_analytics_top.min.0bc67465bdc7b020028dd0e1b94193f1.js
215 ms
clientlibs_onetrust.min.d956db948796236838bf4abf44338802.js
216 ms
webpack-style-manifest-productListComponent-js.bundle.5ebdc406ea0f6ddb5f43.css
180 ms
sfdc-liveChat.bundle.e867c2dc6805b5f7c7a5.css
162 ms
clientlibs_onetrust.min.3d140fee194f8daaced56601194a905d.css
160 ms
modern.min.3a0ad4c7614495b1cae264dfcb9b9813.js
179 ms
webpack-style-manifest-scrollableTabsComponent-js.bundle.5ebdc406ea0f6ddb5f43.css
386 ms
webpack-style-manifest-blockquoteComponent-js.bundle.5ebdc406ea0f6ddb5f43.css
372 ms
clientlibs_www_tags.min.1b6dbce218e03b78c31afe6479e1dcca.js
358 ms
webpack-style-manifest-tileSystemComponent-js.bundle.5ebdc406ea0f6ddb5f43.css
362 ms
kernel.min.015ac4f9d569ca6cc01b4c370c725560.js
356 ms
clientlibs_hgf_aab889b8.js
358 ms
webpack-style-manifest-metricComponent-js.bundle.5ebdc406ea0f6ddb5f43.css
355 ms
vendors~scriptloader.bundle.5ebdc406ea0f6ddb5f43.js
352 ms
clientlibs_analytics_bottom.min.570cadea1df7439553ca74f27014e244.js
357 ms
clientlibs_evergage.min.93d25246841f4d9f30b4589ef0f08b08.js
353 ms
scriptloader.bundle.5ebdc406ea0f6ddb5f43.js
350 ms
vendors~scriptloader~utils.bundle.5ebdc406ea0f6ddb5f43.js
343 ms
utils.bundle.5ebdc406ea0f6ddb5f43.js
340 ms
742a15b9-6aa4-4c2f-99c1-ad4ca220cf96.json
269 ms
shared.min.d8eee0685f08a5253a1d753a2619a08f.js
240 ms
vendors~utils~webpack-script-manifest-SfdcWwwBaseCnc-js~webpack-script-manifest-commonlyUsed-js~webp~8dbeef75.bundle.5ebdc406ea0f6ddb5f43.js
230 ms
ip.json
450 ms
gtm.js
495 ms
location
332 ms
NCPYV-VGJPP-N4J93-8HN3B-8B6S3
442 ms
g
557 ms
g
725 ms
spacer.gif
254 ms
salesforce-cloud-logo-sm.png
253 ms
einstein-overview-jumbotron-v11.png
499 ms
jumbotron-mobile.png
378 ms
SalesforceSans-Regular.woff
184 ms
otBannerSdk.js
150 ms
webpack-script-manifest-linkedData-js.bundle.5ebdc406ea0f6ddb5f43.js
98 ms
vendors~webpack-script-manifest-SfdcWwwBaseCnc-js~webpack-script-manifest-commonlyUsed-js.bundle.5ebdc406ea0f6ddb5f43.js
101 ms
vendors~webpack-script-manifest-SfdcWwwBaseCnc-js~webpack-script-manifest-commonlyUsed-js~webpack-sc~8ab15162.bundle.5ebdc406ea0f6ddb5f43.js
93 ms
webpack-script-manifest-commonlyUsed-js.bundle.5ebdc406ea0f6ddb5f43.js
91 ms
webpack-script-manifest-commonlyUsed-js~webpack-script-manifest-globalNavConsolidated-js~webpack-scr~8e1c6a65.bundle.5ebdc406ea0f6ddb5f43.js
89 ms
vendors~webpack-script-manifest-scrollableTabsComponent-js.bundle.5ebdc406ea0f6ddb5f43.js
89 ms
webpack-script-manifest-tileSystemComponent-js.bundle.5ebdc406ea0f6ddb5f43.js
92 ms
webpack-script-manifest-scrollableTabsComponent-js.bundle.5ebdc406ea0f6ddb5f43.js
244 ms
webpack-script-manifest-liveChat-js.bundle.5ebdc406ea0f6ddb5f43.js
82 ms
webpack-script-manifest-formContainerV2-js~webpack-script-manifest-liveChat-js.bundle.5ebdc406ea0f6ddb5f43.js
84 ms
vendors~webpack-script-manifest-liveChat-js.bundle.5ebdc406ea0f6ddb5f43.js
77 ms
AvantGarde-Demi.woff
75 ms
SalesforceSans-Bold.woff
71 ms
salesforce-icons.woff
71 ms
SalesforceSans-Light.woff
71 ms
gtm.js
95 ms
einstein.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
einstein.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
einstein.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 Einstein.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 Einstein.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.
einstein.com
Open Graph data is detected on the main page of Einstein. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: