Q:Request a Quote & Hide Price
Meets our highest standards for performance, design, and integration. Learn moreOpens in new window
Reviews (648)
We started using this app around September 2025, and initially, it worked well for our needs. The setup was smooth, and the core “Request a Quote” functionality is useful, especially for B2B operations.
However, over time we noticed a decline in our site performance and conversion rate. After thorough investigation (including multiple tests using Chrome DevTools), we found that the app generates a very high number of repeated GraphQL (API) requests on product and collection pages. In some cases, this resulted in hundreds of requests per page load, which significantly slowed down the site.
We worked closely with the support team, and while they were responsive and tried to assist, they ultimately confirmed that this behavior is tied to the app’s current architecture and cannot be further optimized at this time.
Because of the impact on performance and conversions, we made the decision to disable the app on our store.
To be fair, the app itself is functional and the support team is helpful. But for stores that are sensitive to performance and conversion rates, this is a serious concern.
We may consider using the app again in the future if improvements are made.
For anyone considering installing this app: please test carefully on your store. If your site speed and conversion rate are critical, use with caution and monitor performance closely.
Hi there, Kaylee here, Customer Support Team Lead.
Thank you for the detailed review and for acknowledging that the app is functional and our support team was responsive.
I’m truly sorry for the performance and conversion impact you experienced. We understand how critical site speed is, and we appreciate you sharing your investigation and the context around the repeated requests you observed.
One additional note we’d like to share: in our recent speed tests on your store, even with our app not embedded on the theme, the baseline performance score is already quite low. Because of that, it’s difficult to make a fair “before vs. after” comparison or isolate the app’s impact without testing under the same conditions as when the app was enabled.
If you’re open to it, we’d really like to run a controlled re-test with you (same rules/configuration as before) so we can compare results accurately and share the findings with our product team.
Thank you again, we’d really value the chance to work with you on this.
