By default, PriceFetchWP can resolve external prices as a WooCommerce product, page, or post loads.
In many cases this happens quickly, especially when a valid cached price is available. However, a new external fetch can take longer if the source website is slow, blocked, or being retrieved through a Proxy provider.
Delay Price Load allows the page to continue loading while PriceFetchWP retrieves or resolves the price separately.
This option is recommended for most sites.
– Default Behavior
When Delay Price Load is disabled:
- PriceFetchWP attempts to resolve the price during the normal page request
- A valid PriceFetchWP cached price can be used immediately
- If a new external fetch is required, the page may wait for that request to complete
- The resulting price is displayed
This can work well with fast sources, but an uncached external request may increase page-load time.
– When Delays Can Occur
A new external price request may take longer when:
- The external website responds slowly
- A Proxy provider is being used
- Browser rendering is required
- The external site is experiencing temporary problems
- No valid PriceFetchWP cached price is available
- The previous Price Cache has expired
Once PriceFetchWP has a valid cached price, it can reuse that result until the configured Price Cache expires.
When the cache expires, the next applicable request may need to perform a new external fetch.
– What Is Delay Price?
Delay Price Load allows the page to render without waiting for the external price request to finish.
Instead of holding up the initial page request, PriceFetchWP loads the price separately after the page has begun loading.
A loading indicator can be displayed while the price is being resolved.
Delay Price Load is recommended because it can improve page-load behavior and reduce problems caused by full-page caching.
– How It Works
With Delay Price Load enabled:
- The page begins loading normally
- A loading indicator may appear where the PriceFetchWP price is displayed
- PriceFetchWP sends a separate request for the price
- The normal PriceFetchWP Price Cache is checked
- If a valid cached price exists, that result can be reused
- If no valid cached price exists, PriceFetchWP performs the required external fetch
- The displayed price updates when the request completes
Delay Price Load does not disable or bypass PriceFetchWP’s own Price Cache.
– Benefits
• Faster Initial Page Loading
The page does not have to wait for a slow external price request before it can continue rendering.
This is especially useful when a new external fetch is required.
• Better User Experience
Visitors can begin viewing the page while PriceFetchWP resolves the price separately.
If needed, a loading indicator provides feedback until the price becomes available.
• Helps With Full-Page Caching
Delay Price Load can help prevent a page cache, hosting cache, or CDN from locking an older price directly into a cached copy of the page.
Because the PriceFetchWP price is requested separately after the page begins loading, a cached page can still request the current PriceFetchWP result.
PriceFetchWP’s own Price Cache still applies to that delayed request.
• Useful for Slow or Protected Sites
Delay Price Load is particularly useful when:
- External websites respond slowly
- A Proxy provider is required
- Browser rendering is involved
- Request times vary between fetches
Using Delay Price Load together with an appropriate Price Cache can help reduce how often those slower external requests are required.
– When to Use Delay Price
Delay Price Load is recommended for most sites.
It is particularly useful when:
- Your site uses full-page caching
- Your site uses a CDN
- External sources respond slowly
- You use PhantomJSCloud or Scrapfly
- You want pages to render without waiting for an uncached external fetch
- Price fetch times vary between requests
– When Not to Use It
You may prefer to disable Delay Price Load if you specifically need the price to be resolved as part of the initial server-rendered page response.
Keep in mind that if a new external fetch is required, the normal page request may then need to wait for that external request to complete.
– What Users Will See With Delay Price
When enabled:
- The page begins loading normally
- A selected loading indicator may appear
- PriceFetchWP resolves the price separately
- The displayed price updates when the request completes
If a valid PriceFetchWP cached price already exists, the delayed request can usually be completed without performing another external fetch.
The appearance of the loading indicator can be customized under Loader Settings.
– Delay Price Load and Price Cache
Delay Price Load and Price Cache perform different jobs.
Delay Price Load controls when the displayed price is loaded into the page.
Price Cache controls how long PriceFetchWP can reuse a previously retrieved price before another external fetch is required.
For example:
Cached page loads
↓
Delay Price Load sends separate request
↓
PriceFetchWP checks Price Cache
↓
Cached price available?
↓
YES → return cached price
NO → perform external fetchThis allows Delay Price Load to help with page or CDN caching while still benefiting from PriceFetchWP’s own caching system.
For more information, see: Price Cache
– Common Questions
• Why does the price appear after the page loads?
Because Delay Price Load is enabled.
The page begins rendering first, and the price fetch runs while the page starts loading.
• Does Delay Price Load always make a new external request?
No. The delayed request still checks the normal PriceFetchWP Price Cache first.
If a valid cached price is available, PriceFetchWP can return that result without fetching the external website again.
• Does Delay Price Load bypass my page cache or CDN?
It can help prevent a cached page from locking an older PriceFetchWP price into the page.
The page itself may still be served from cache, but PriceFetchWP requests the displayed price separately after the page begins loading.
• Does Delay Price Load bypass the PriceFetchWP Price Cache?
No. PriceFetchWP’s own Price Cache still applies normally.
Next Steps ───
Now that you understand page load behavior, continue to: