cloud.sap website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

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

• Real-user LCP: 2.6 s

  2.6 s

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

• Real-user INP: 310 ms

  310 ms

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

• Tap response (INP) got 41% slower for real visitors

  +41%

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

• Real-user FCP: 2.6 s

  2.6 s

  Real visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.

• Real-user TTFB: 1.4 s

  1.4 s

  Real visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.

• Largest content (LCP) held steady for real visitors

  +1%

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

• Page weight: 2.2 MB

  2.2 MB

  Your homepage downloads 2.2 MB on a phone, 135 KiB of it images (6%). Under 2 MB keeps phones on slow connections fast.

• About 0.6 g of CO₂ per visit

  0.61 g

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

• Banner landmark should not be contained in another landmark (1 element)

  Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• Document should not have more than one banner landmark (1 element)

  Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

  Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• Headings skip levels

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

  View sourceElements (3)

• robots.txt blocks all crawlers

  Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

• No structured data

  No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

• 59 internal links, 14 external

  The homepage links to 59 pages on cloud.sap and 14 external pages.

• No Organization structured data

  There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

• Parts of the site are closed to 6 AI crawlers

  Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

• Opted out of AI training for 1 crawler

  robots.txt blocks Applebot-Extended, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

• 2 links to non-canonical URLs

  Your homepage links to 2 pages by a URL that isn't their canonical one, for example /assetdetail/2023/11/2acb8474-977e-0010-bca6-c68f7e60039b.html, whose canonical is /videos/sap-business-technology-platform-overview-video-1023437. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  Elements (2)

• 1 page with very little text

  /assetdetail/2023/11/2acb8474-977e-0010-bca6-c68f7e60039b.html has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

• 3 pages slow to respond

  /products/technology-platform/core-platform-capabilities.html, /products/technology-platform/enterprise-content-management.html and /products/data-cloud.html took over 3 s to send their HTML from our server.

• 15 internal pages checked

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

• 3 small tap targets

  3 of 11 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

• 2 JavaScript errors while loading

  2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.

• No Content-Security-Policy

  No Content-Security-Policy header, the main browser-side defence against injected scripts.

• No clickjacking protection

  Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

• 2 redirects before the homepage

  Opening https://cloud.sap goes through 2 redirects before the homepage loads.

• No Permissions-Policy

  No Permissions-Policy header to switch off camera, microphone and location for embedded content.

• Deprecated X-XSS-Protection

  X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

• No CAA record

  sap.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

• DNSSEC is off

  sap.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

• Thin social proof

  Social proof on the homepage: “Over 33,000 customers”. Pairing it with named testimonials or customer logos makes it far more convincing.

• No analytics detected

  No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

• No form on the homepage

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

• No risk reducer

  No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

• About 1,020 words of copy

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

• No SPF record

  cloud.sap has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

• DMARC is monitor-only (p=none)

  DMARC is set to p=none, so mail pretending to be cloud.sap is still delivered. Reports are on, so moving to quarantine is the next step.

• No DKIM key on the usual selectors

  We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

• Domain receives no email

  cloud.sap has no MX record, so it receives no email. SPF -all and DMARC reject still matter: they stop others sending mail as you.

• Email authentication score: 25/100

  Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

• 7 cookies set on arrival

  7

  Opening the homepage sets 7 cookies (measured from a US location before any click).

• 3 other companies contacted

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