salesforce.com website review

About 1.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.1 s faster on a phone.

Google Tag Manager costs a phone 2.9 s of main-thread work and 2.1 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

sfdcstatic.com costs a phone 1.9 s of main-thread work and 1.7 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

A phone's processor spends 16.2 s on main-thread work while loading, 10.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

13 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.

Your mobile performance score is 32. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

The page has 7,829 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

36 files are served with short cache lifetimes, so returning visitors download them again (7.3 MB).

8 third-party services load with your homepage (Google Tag Manager, sfdcstatic.com and Impact Radius and others), adding 4.1 MB and 5.3 s of main-thread time.

20 long tasks block the main thread while loading, the longest for 1.3 s. During a long task the page ignores taps.

About 102 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

12 images could be 262 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

42 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 300 ms faster on a phone.

Polyfills for old browsers add 30 KiB JavaScript that modern phones do not need.

6 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 23.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Get started with the #1 AI CRM”.

Visually, the page fills in at 19.9 s (Speed Index). Good is under 3.4 s.

Scripts block taps and scrolling for 5.9 s in total while the page loads. Good is under 200 ms.

The page becomes fully interactive after 44.1 s. Good is under 3.8 s.

Real visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 348 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 3.5 s to 4.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

The first text or image appears after 2.4 s on a phone. Good is under 1.8 s.

3 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 501 ms to 487 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 15.4 MB in 438 requests on a phone: images 9.2 MB (133), scripts 4.6 MB (142) and media 668 KiB (2). Under 2 MB keeps phones on slow connections fast.

5 images are downloaded at several times the size a phone draws them, for example resources-tab1-trailhead-community.png at 1,200 px wide, shown at 358 px. Resized copies would save about 505 KiB.

6 images (1.5 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

8 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 4.37 g of CO₂e: 524.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

48 images have no alt text, which hurts accessibility and image search.

Headings skip levels (h2 → h6, h2 → h6 and h2 → h6), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (2 elements).

Your title is only 25 characters: “Salesforce: The #1 AI CRM”. Between 30 and 65 characters leaves room to say what you do and for whom.

7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 574 pages on salesforce.com and 72 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.salesforce.com/agentforce/operations, whose canonical is https://www.salesforce.com/agentforce/regrello. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.salesforce.com/agentforce/operations, https://www.salesforce.com/agentforce/customer-stories, https://www.salesforce.com/agentforce/use-cases, https://www.salesforce.com/agentforce/pricing, https://www.salesforce.com/sales and https://www.salesforce.com/sales/cloud and 1 other took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 199 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://id.rlcdn.com/464526.gif.

4 errors were logged to the browser console while the page loaded, for example “Refused to get unsafe header "X-OneTrust-IsBot"”.

Large scripts ship without source maps.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 1,374 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Reddit Pixel and 1 more (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 35 cookies, 3 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 51 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.