🎉 Celebrate with 10% OFF on All Products! Use Code: GFEX10 Or Buy Any 2+ Items for 30% OFF with Code: GFEX30!
Guides & Tutorials November 1, 2026

Why Is My Gravity Forms Submission Slow? How to Find the Step That Takes the Time

GravityExtra
Why Is My Gravity Forms Submission Slow? How to Find the Step That Takes the Time

A visitor fills in your form, presses Submit, and waits. The spinner turns for two seconds, then four, sometimes longer. Some visitors press the button again and you get a duplicate entry; others close the tab and you never hear from them. When you test the form yourself, it feels slow too, but nothing is broken: the entry is saved, the e-mails arrive, the CRM gets its contact. So where does the time go?

This guide explains what actually happens after a visitor presses Submit on a Gravity Forms form, why the usual speed tools cannot see it, and how to find the one step that is slow instead of guessing. It uses the Gravity Forms Form Speed Profiler & Optimizer add-on, which times every step of a submission and shows the result as a waterfall.

What happens after a visitor presses Submit

A Gravity Forms submission is not one action but a chain of steps that run one after the other on your server, while the visitor waits for the confirmation:

  • WordPress starts up: WordPress, your theme and every active plugin load, as on any page request.
  • Validation: every field is checked. Other plugins can add their own checks here, such as spam filters, address lookups or e-mail verification, and some of those call an outside service.
  • The entry is saved to the database, and the spam check runs.
  • Feeds run: each feed add-on sends the entry where it needs to go, such as a CRM, a mailing list, a spreadsheet or a webhook. Payment add-ons charge the card. Each of these usually waits for an outside service to answer.
  • Notifications are sent: each notification builds its e-mail and hands it to your mail system, and the visitor waits until the mail server has accepted it.
  • The confirmation is built, other plugins run their after-submission code, and the page is sent back.

The total time is the sum of all of these. If one feed waits three seconds for a slow CRM, or one notification waits for a slow mail server, the whole submission takes that much longer. And because every step looks the same from the outside, a spinner, you cannot tell which one it is.

Why the usual tools do not find it

Page-speed tools and browser measurements are built to measure how quickly a page and its files load: images, scripts, style sheets, fonts. They are excellent for that, but a submission’s slow part happens on the server, after the request has been sent and before the answer comes back. To a page-speed tool, it is one long wait with nothing inside it.

Gravity Forms has a logging feature that writes down what happens during a submission. It is the right tool for finding errors, and every developer who supports Gravity Forms knows it. But it is a raw text log, without a timing breakdown, and it does not tell you which plugin’s code took the time. Reading timestamps line by line across a long log, for several submissions, is slow work, and code from other plugins that hooks into Gravity Forms does not write to that log at all.

So most people guess. They switch plugins off one by one, or change the mail set-up and hope, or blame the hosting. Sometimes the guess is right. Often it costs an afternoon and changes nothing, because the slow step was somewhere else.

Measure instead: profile the submission

The Form Speed Profiler add-on measures each step of real submissions. In Forms → Speed Profiler you choose a form (or any form), how many of the next submissions to profile and after how many minutes to stop. Then you send the form yourself, or simply wait for your visitors. The rule switches itself off after the number of submissions or the time limit, so you cannot forget it.

For each profiled submission the add-on records the time of every phase, from start-up to page output, and inside them every step: each feed add-on, each notification with its mail sending, payment steps, and every callback that other plugins attached to Gravity Forms, with the name of the plugin it belongs to and the number of database queries it ran. Multi-page forms are covered too: moving to the next page is profiled as a page change, and a submission that fails validation is recorded as such.

The waterfall of one profiled submission: server time, slowest step, and each phase with its feed add-ons, notifications and hooked code, the plugin they belong to, their time and a timeline bar
One submission, step by step. The slow notification and the slow feed add-on stand out, each with the plugin behind it.

The result is a waterfall: a timeline of the request with the slowest step at the top of the summary. In the example above, a dental practice’s registration form took a little over two seconds on the server. Almost one second of that was a single notification, “Office copy”, waiting for the mail server; six tenths of a second were one feed add-on sending the entry to a records system; and a small piece of code from a practice-management bridge plugin added another fifteen hundredths. Everything else together was a fraction of a second. Without the waterfall, that is three different things to suspect and no way to tell them apart.

The usual culprits, and what helps

After profiling a few submissions, open the Report tab. It averages the profiles, lists the slowest steps and the time per plugin, and turns the numbers into suggestions. These are the findings that come up most often.

A slow notification

If a notification takes most of a second or more, the time is almost always spent handing the e-mail to the mail server. A mail connection that is slow to answer, or a notification that sends several e-mails one after the other, adds up quickly. Check your mail sending set-up first. Gravity Forms can also send notifications in the background, so the visitor does not wait for them; a developer can switch this on with a single filter. And check whether every notification is needed for every submission: notification conditions can skip the ones that are not.

A slow feed add-on

A feed that sends data to a CRM, a mailing list or a webhook waits for that service to answer. If the service is slow, every submission is slow. Many feed add-ons can process their feeds in the background instead, so the visitor gets the confirmation straight away and the data follows a moment later. Feed conditions help too, so a feed only runs for the submissions that need it.

A slow payment step

Charging a card means waiting for the payment service, and there is not much to change about that. But it is a good reason to keep everything else on a payment form quick, so the total stays reasonable.

Code from another plugin

Plugins often attach their own code to Gravity Forms: to copy entries somewhere, to check addresses, to add tracking. The waterfall names each one, the hook it uses and the plugin it belongs to. If one of them is slow, check its settings, or contact its author with the numbers: “your callback on gform_after_submission takes 1.2 seconds per submission” is a much better support request than “my form is slow”.

Slow validation

When the validation phase is slow, look at the steps under it. A spam check or an address check that calls an outside service is the most common cause, especially when the service is far away or overloaded.

Many database queries

The waterfall shows the number of queries per step. A step that runs hundreds of queries per submission is worth a closer look by a developer, and with SAVEQUERIES enabled the add-on also shows how much time those queries took.

The report across profiled submissions: average and slowest server time, suggestions in plain words, the slowest steps with average and slowest times, and the time per plugin
The report averages the profiles, lists the slowest steps and suggests where to look.

Making the form page itself lighter

The submission is one half of how fast a form feels; the other half is how quickly the page with the form appears and becomes usable. Here the add-on offers four switches per form, all optional and off by default:

  • Load the captcha on first interaction. Captcha scripts are often the heaviest thing on a form page. With this switch the captcha loads when the visitor first focuses, clicks, types or taps in the form, not with the page. A visitor who presses Submit first still gets a working form: the captcha loads, then the form is sent.
  • Render long choice lists on focus. A country drop-down can hold two hundred and fifty choices. The page is sent with only the first and selected choice, and the full list is filled in when the visitor opens the field. What is submitted does not change.
  • Skip rendering until the form is near the screen. For a form further down a long page, the browser may skip laying it out and painting it until the visitor scrolls near it.
  • Defer Gravity Forms scripts where safe. The add-on asks WordPress to load the Gravity Forms scripts with “defer”. WordPress itself decides which scripts can safely be deferred and keeps the others as they are.

Every page is different, so the add-on lets you measure instead of hoping. Measure page weight loads the form preview with the switches off and on in a hidden frame in your browser and compares what is loaded before the first interaction: size, requests, elements on the page, the choices rendered and the scripts waiting for the first interaction.

The Speed Profiler tab of a form: four optional front-end switches and the page-weight readout comparing the form preview without and with the switches
The optional front-end switches of a form and the page-weight readout, measured in your own browser.

How this differs from the tools you may already use

It helps to be clear about which tool answers which question. Our Form Health add-on checks the configuration of your forms for mistakes, such as a notification with no valid recipient or logic that points to a deleted field. Feed Health catches feeds that failed and lets you retry them. Failed Submissions shows submissions that failed validation and whether the visitor gave up. Test Mode lets you try a form on the live site without side effects, and our SMTP add-on makes sure your e-mail is delivered. None of them measures time.

Gravity Forms logging records what happens, but without a timing breakdown per step and plugin. Page-speed plugins and browser tools measure page assets, not the steps of a submission. The Speed Profiler fills exactly that gap: it measures the submission on the server, step by step, and names the plugin behind each step.

Safe to use on a live site

A profiler that slows the site down or leaks data would defeat its purpose, so the add-on is built to stay out of the way:

  • Nothing is timed when the profiler is off. The add-on only reads one small setting to see whether a profiling rule is running. In our tests, submissions with the profiler off took the same time as with the add-on deactivated, within the normal variation between runs.
  • It does not change your submissions. Callbacks receive the same data, return the same results and run in the same order; e-mails, feeds and confirmations are the same with and without profiling.
  • No form data is stored. A profile holds timings and the names of hooks, callbacks, feeds, notifications and plugins, never what a visitor typed. Profiles are capped and deleted automatically after a number of days.
  • Admin-only. The profiler, the reports and the switches need the Gravity Forms settings capability. Visitors never see anything.
  • No outside service. Everything runs on your own server.

Getting started

If your forms feel slow after Submit, measuring takes a few minutes: install the add-on, start a profiling rule for the form, send it a couple of times, and open the waterfall. The setup guide explains every phase, the report, the suggestions and the front-end switches in detail. The add-on works with Gravity Forms 2.9 and newer.

Stop guessing which plugin to blame. Get Gravity Forms Form Speed Profiler & Optimizer and see exactly which step of your form takes the time.

0
0
Your Cart
Your cart is emptyReturn to Shop
🔥 FREQUENTLY BOUGHT TOGETHER
Complete Combo & Save 40%!
ITEM IN YOUR CART
Gravity Forms Klaviyo Add-on
$39.00/yr
+
🎁 RECOMMENDED ADD-ON SAVE 40% OFF
Original Price: $39.00/yr
Bundle Special Price: $23.40/yr