Answers.Body: <p>17 seconds from pressing &quot;Submit&quot; to the thank-you page is still obscenely high.  My only client who comes close to this has maybe 80 extensions installed.  My guess is you have something going on already that's exacerbated by Stripe.</p>
  <p>While it's not the easiest solution, doing an <a href="https://xdebug.org/docs/profiler" rel="nofollow noreferrer">xdebug profiling session</a> would be really helpful here.  E.g. I once found a bug in the token processor that made contact creation take a long time - and when I added an extension with custom tokens, the problem got even worse.  Something comparable may be happening here.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-09-01T20:34:47.897Z
Answers.Text: I tested my client with 80+ extensions with Stripe 6.5 and they returned in 11 seconds, FWIW.
Answers.UserDisplayName: Jon G - Megaphone Tech
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-09-21T20:50:07.540Z
Answers.Text: The commonality thus far is large db size + Wordpress + Stripe. What CMS are they on?
Answers.UserDisplayName: Andy Burns
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-09-21T23:19:09.557Z
Answers.Text: Drupal 8, about a quarter million contacts.  Also using Redis, which is a good idea if you have a large db
Answers.UserDisplayName: Jon G - Megaphone Tech
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-09-01T18:38:21.440Z
Answers.LastActivityDate: 2020-09-01T18:38:21.440Z
Answers.UserDisplayName: Jon G - Megaphone Tech
Body: <p>Our contribution pages are not as fast as I would expect. What is the expected time people see to submit a CiviContribute page out of the box? Up until recently, it was reliably within 20-25s using Stripe which was at the outer limits of my expectations but serviceable.</p>
  <p>Now contributions take from 30-35s. The increase seems to have occurred within the last month.</p>
  <p>The factors I can see that are affecting submissions are:</p>
  <ul>
  <li>USPS standardization</li>
  <li>Google geocoding</li>
  <li>Deduping to a large database</li>
  <li>Stripe</li>
  <li>Cividesk Normalize</li>
  </ul>
  <p>We also experience a cookies error intermittently after submitting a donation.</p>
  <p><a href="https://i.sstatic.net/xbj80.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/xbj80.png" alt="enter image description here" /></a></p>
  <p>In other words, the donor does not get to the thank you page but gets the following error. The donation does succeed. This issue has persisted for a long-time. We have not seen any pattern for when it occurs. I would estimate that it occurs 10-20% of the time.</p>
  <p>This is related: <a href="https://lab.civicrm.org/dev/core/-/issues/517" rel="nofollow noreferrer">https://lab.civicrm.org/dev/core/-/issues/517</a> and says using PHP 7.2 resolved, but we are already on 7.2.</p>
  <h1>Testing</h1>
  <ul>
  <li>CiviCRM 5.28.3</li>
  <li>Processors: Stripe 6.4.2 / PayPal Standard / Authorize.net</li>
  <li>Browser: Chrome</li>
  </ul>
  <p>Baseline time to submission: Using Stripe with USPS standardization, CiviDesk Normalize, Geocoding: 32 seconds.</p>
  <p>Test 1 - Stripe: Disable Cividesk Normalize and USPS standardization: 35s</p>
  <p>Test 2 - Stripe: Above and disabled Google Geocoding + Geofill: 29s</p>
  <p>Test 3 - Authorize.net and enabled above extensions: 23s</p>
  <p>Test 4 - Authorize.net and disabled above extensions: 23s</p>
  <p>Test 5 - PayPal Standard and enabled above extensions: 17s</p>
  <p>Test 6 - PayPal Standard and disabled above extensions: 17s</p>
  <p>So it appears to be related to Stripe.</p>
  <p>For reference civicrm.org runs Stripe and donating there it took 7s to confirmation page and 9s to submit.</p>
  <p><strong>Update: The common factors of the slowness is WP + large database + Stripe.</strong></p>
  <p>Ref: <a href="https://lab.civicrm.org/extensions/stripe/-/issues/246" rel="nofollow noreferrer">https://lab.civicrm.org/extensions/stripe/-/issues/246</a></p>
  
Tags: <civicontribute><payment-processor><stripe>
Title: Contribution Page Time to Submit
ThreadText: # Contribution Page Time to Submit
  
  (Asked by: username_0 on 2020-09-01)
  
  Our contribution pages are not as fast as I would expect. What is the expected time people see to submit a CiviContribute page out of the box? Up until recently, it was reliably within 20-25s using Stripe which was at the outer limits of my expectations but serviceable.
  
  Now contributions take from 30-35s. The increase seems to have occurred within the last month.
  
  The factors I can see that are affecting submissions are:
  
  * USPS standardization
  * Google geocoding
  * Deduping to a large database
  * Stripe
  * Cividesk Normalize
  
  We also experience a cookies error intermittently after submitting a donation.
  
  [![enter image description here](https://i.sstatic.net/xbj80.png)](https://i.sstatic.net/xbj80.png)
  
  In other words, the donor does not get to the thank you page but gets the following error. The donation does succeed. This issue has persisted for a long-time. We have not seen any pattern for when it occurs. I would estimate that it occurs 10-20% of the time.
  
  This is related: <https://lab.civicrm.org/dev/core/-/issues/517> and says using PHP 7.2 resolved, but we are already on 7.2.
  
  # Testing
  
  * CiviCRM 5.28.3
  * Processors: Stripe 6.4.2 / PayPal Standard / Authorize.net
  * Browser: Chrome
  
  Baseline time to submission: Using Stripe with USPS standardization, CiviDesk Normalize, Geocoding: 32 seconds.
  
  Test 1 - Stripe: Disable Cividesk Normalize and USPS standardization: 35s
  
  Test 2 - Stripe: Above and disabled Google Geocoding + Geofill: 29s
  
  Test 3 - Authorize.net and enabled above extensions: 23s
  
  Test 4 - Authorize.net and disabled above extensions: 23s
  
  Test 5 - PayPal Standard and enabled above extensions: 17s
  
  Test 6 - PayPal Standard and disabled above extensions: 17s
  
  So it appears to be related to Stripe.
  
  For reference civicrm.org runs Stripe and donating there it took 7s to confirmation page and 9s to submit.
  
  **Update: The common factors of the slowness is WP + large database + Stripe.**
  
  Ref: <https://lab.civicrm.org/extensions/stripe/-/issues/246>
  
  **Tags:** civicontribute, payment-processor, stripe
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2020-09-01. Score: 2
  
  17 seconds from pressing "Submit" to the thank-you page is still obscenely high. My only client who comes close to this has maybe 80 extensions installed. My guess is you have something going on already that's exacerbated by Stripe.
  
  While it's not the easiest solution, doing an [xdebug profiling session](https://xdebug.org/docs/profiler) would be really helpful here. E.g. I once found a bug in the token processor that made contact creation take a long time - and when I added an extension with custom tokens, the problem got even worse. Something comparable may be happening here.
  
  > **Comments:**
  > **username_1**: I tested my client with 80+ extensions with Stripe 6.5 and they returned in 11 seconds, FWIW.  
  > **username_0**: The commonality thus far is large db size + Wordpress + Stripe. What CMS are they on?  
  > **username_1**: Drupal 8, about a quarter million contacts.  Also using Redis, which is a good idea if you have a large db  
  
  ---
  
  