Loading

Time To First Byte (TTFB) best practices for the B2C Commerce platform

Publiseringsdato: Aug 26, 2025
Beskrivelse

What does Time To First Byte (TTFB) mean? 

Time To First Byte (TTFB) describes the time the web-server needs to deliver the first byte to the client. Time is measured between the point in time where the server receives the http-request until the first byte (the first 8 bit) are received by the client or client browser (depending on the method of measurement).

 

Note: Measurements should always be taken in a stable environment. Mobile devices do not offer stable data connections and the network stability is no tool to produce representative numbers.

Løsning

Troubleshooting TTFB first steps: 

 

If you are behind the eCDN and Minification/Compression is turned on

In this case TTFB is not a relevant factor to measure because the method for measuring TTFB on e.g. webpagetest.org is not usable for TTFB behind a Content Delivery Network (CDN) like the embedded CDN used in the B2C Commerce platform because of the compression that is used for the minification. The overall site loading speed will be faster but the TTFB will be longer. For more information, please read this blog post.

Pipeline Profiler 

The Pipeline Profiler displays a high-level view of response times per script, such as hits, total time for a page to be generated, and average time. Use the Pipeline Profiler to identify the most expensive pipeline or controllers, and the most expensive component within that pipeline or controller. Drill down into script data within a pipeline or controller to identify expensive scripts running on the storefront.

  1. Use Pipeline Profiler by going Administration > Operations > Pipeline Profiler in Business Manager. 
  2. Also check the Script Data link in the Browse Captured Script Data section to see which scripts take the longest time. This way you will find out where improvements are needed. 

Note: In addition, pipeline performance can additionally be checked via the Technical Dashboard in Reports & Dashboards. Our general recommendation is an average response time <= 400 ms and a cache hit ratio above 70%. To help with this, please work with your development team and/or integration partner to achieve better numbers and review the material below:

 

Other troubleshooting

Please walk through First Steps to take when your Salesforce B2C Commerce site is slow to troubleshoot site slowness. 

 

If you did all the troubleshooting above but TTFB is still high:

Please contact Commerce Cloud Support with your findings from the steps above and include the following information so we can investigate: 

  1. HAR-file containing: 
    • Ray ID 
    • dwsid (session ID)
    • timestamp 
    • How to retrieve a HAR-file can be found here. 
  2. Describe your test setup and with which tools you tested the TTFB.
  3. What kind of internet connection did you use? 
  4. Please also see Gathering Details for B2C Commerce Cloud Support Cases.

 

Knowledge-artikkelnummer

000391229

 
Laster
Salesforce Help | Article