Will a Shopify Survey Slow Checkout? Placement and Testing Guide

OrderSurvey's online surveys appear after an order is placed, on the Thank you and Order status pages. Customers do not have to answer a survey to complete their order. The app does not add survey fields to the information, shipping or payment steps.

That placement keeps the survey outside the steps needed to place the order. It does not mean the survey has zero loading cost or that every store's conversion rate will stay unchanged. The block still needs to load, display clearly and save answers reliably.

This guide explains what to check before launch. See the product walkthrough, or book personal setup help if you would like us to verify the blocks with you.

Choose the page for the question you want to ask

Shopify makes Thank you and Order status UI extension blocks available on Basic and higher. UI extensions in the information, shipping and payment steps require Shopify Plus. These are different placements with different requirements. See Shopify's app availability table.

This article covers the online blocks. In-store surveys use a separate Shopify POS workflow, where staff open the survey action after the sale.

What a native extension does—and what still loads

OrderSurvey uses Shopify UI extensions for its online survey blocks. You add and position them through Shopify's checkout and accounts editor; you do not paste a survey script into your theme. Shopify documents how extension targets determine where app content appears.

The extension still runs code and makes requests to OrderSurvey to find an eligible survey and save a submission. A slow connection, an unavailable service or a configuration issue can affect that experience. Native placement alone is not evidence of a particular load time, unchanged page metrics or a guaranteed response rate.

The extension framework also does not determine all of an app's data permissions. Review the actual permissions and OrderSurvey's privacy policy. Optional customer tagging requires customer access; it is separate from displaying a basic survey.

Keep participation optional and the question useful

Start with one question tied to a decision. For example, "How did you first hear about us?" can help identify discovery sources to investigate alongside your analytics. An Other answer can reveal choices you missed.

Use a conditional follow-up when the detail matters: someone who selects a creator or podcast can name it, while other respondents finish sooner. Test both the follow-up and the route that skips it. The branch-testing checklist covers changed answers, required fields and completion paths.

A required question means a person must answer it before submitting that survey. It does not make the survey a requirement for placing an order. Customers can leave the page without responding.

If you need multiple questions, choose a step-by-step or same-page flow deliberately. Test the longest path on a phone. A shorter first screen can make the interaction easier to use, but it is not proof of faster network loading.

Verify both blocks before inviting responses

Installing OrderSurvey and enabling a survey do not place the blocks automatically. Add and save the block separately on each selected page in the active checkout configuration.

Use a development store or an approved test order for these checks. Keep the rest of the configuration stable and record the device, connection and test time.

A developer can use browser performance and network tools to compare repeated tests under the same conditions, including a slower mobile connection. Record the block's loading and submission behavior as well as the surrounding page's usability. One successful load or a single before-and-after timing is not a performance guarantee.

The editor preview helps check layout, but it does not replace an actual matching-order submission. Follow the Thank you page setup guide and Order status troubleshooting steps when a block does not appear.

Check eligibility before treating an absent survey as a speed problem

An enabled survey can remain hidden because its page, audience, schedule, rules or response allowance do not match the current request. Use the app's setup diagnostics to distinguish those conditions from a loading issue.

Online audience settings include All orders, First orders only and Repeat orders only. Additional rules can use order total, item quantity, products or variants, shipping country and currency when the required data is available. First- or repeat-order targeting stays hidden when the order context cannot establish eligibility.

Customer-tag targeting is unavailable on these checkout blocks. Adding a customer tag after a response is a separate permission-dependent feature. See the targeting guide before adding conditions.

Measure the experience without overclaiming the result

Track successful display and saved responses separately. A visible survey is not a completed response, and missing display evidence is not by itself proof of a rendering failure. When calculating a response rate, state whether the denominator is eligible orders, observed displays or another measured group. The response-rate guide explains the reporting limits.

Also watch for merchant or customer reports of slow loading, confusing choices and submission errors. If store conversion changes around launch, investigate other changes in traffic, promotions and checkout configuration. A simple before-and-after comparison cannot isolate the survey's effect.

OrderSurvey's Free plan includes 100 responses per rolling 30 days. Unlimited is $24 USD/month, with unlimited responses, CSV export, webhook alerts and priority support. Use Unlimited when response volume or your reporting workflow needs it; it does not replace placement and submission testing.

Install OrderSurvey to start with one useful question, or book a 20-minute setup call. We can help you check both pages and verify that the first answer reaches your dashboard.

Frequently asked questions