First Steps to take when your Salesforce B2C Commerce site is slow

1

Was there a Cache Clear today?

1.Check Cache Time in Business Manager

2.Check to See if replication ran as this clears cache

3.Check to See if code replication ran

1.In Production Business Manager Under Sites | Administration | Sites | Manage Sites | <Site Name> | Check cache last Invalidated time. If cache has been invalidated recently you will experience slower performance while the cache rebuilds.

2. To see if data replication ran, log into your staging instance. Navigate to Administration | Replication | Data Replication Check to see if a replication to production finished recently. If so cache will have been cleared.

3. To see if code replication ran, log into your staging instance. Navigate  to Administration | Replication | Code Replication Check to see  if a replication to production finished recently. If so cache will have  been cleared.

2

Are Jobs Running on Production?

Check for running jobs and duration

Check Indexing Configuration to see if incremental indexing was enabled

Check Job History to see if job is running much longer than usual. If so this is a tip that data may have changed significantly.

Think about large data loads such as backend changed all prices for the season / all products were touched

You can see the settings under Search Indexing module in Business Manager

3

Has New Code or Feature Been Deployed?

Check Code Version on Production

Have you thought about about meta data?

Any preferences changed?

Slowness caused by new feature / function? New cartridges / dependencies?

Check Error Logs. Is the log file size larger than yesterday? If so, download and check the error logs.

4

Are all pages slow, or are specific pages slow?

Check the most frequently requested first: Home, Search Results, Product-Detail,  and Product-Category (often driven by Search).

5

Have there been any recent changes to code, catalogs, or integrations?

If so, when (date, time) were they made?

6

Have you tried to review page response time using a tool like Firebug? Be sure to review client-side timing, versus server-side timing

Note the individual components times over the end-to-end timing  to indicate if client-side or server-side timing is the  root-cause.

7

Have you reviewed the respective pipeline response times (based on the  slow pages); comparing current vs. historical - via Analytics

8

Have you reviewed the respective pipeline caching efficiency (based on  the slow pages) - via Analytics (Technical Reports)?

Was there a recent  cache-clearing event?  How often do such events occur; e.g. each day?

9

Have you investigated the respective pipeline response times (based on  the slow pages) relative to the sequential processing steps - via  Pipeline Profiler?

Pipeline runtime includes wait-time; e.g. are there  any steps dependent on responses from external systems or services (i.e.  integrations)?

Go to Administration | Operations | Pipeline Profiler and click on Play button. You would need to hit refresh button see the result for script debugging.

10

Network Investigation

Have you run a traceroute from the IP address you are connecting to the instance from? Count the number of hops involved along with average time to use as a comparison between other locations to see if a local network issue explains the slowness.

11

Network Verification

Check out this url to see if the site is available globally:

http://www.websitepulse.com/help/tools.php

If it is up you might have a local network issue.