iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
A page can look static and still send network requests. To check whether an e-commerce page is making API calls, open Chrome DevTools before reloading, then use the Network panel to inspect request types, initiators, payloads, and timing. The original observation behind “I thought this e-commerce site was making zero API requests” cannot be independently verified without its request log, site, or browser details, but the investigation can be repeated with a complete capture.
Why a page that looks static may still make requests
A storefront can display what looks like a finished page while the browser fetches scripts, images, analytics, app code, or data in the background. Some requests may be API calls; others are ordinary page resources. A visible page alone does not tell you which are happening.
That distinction matters when investigating a specific claim. Without the site address and a recorded Network log, it is not possible to say which requests occurred in the original session or what initiated them. The steps below show how to capture and attribute activity rather than assume that every request is an API call.
Capture requests from the start of a page load
- Open the page in Chrome and open DevTools. Select the Network panel before reloading.
- Reload the page while the Network panel is open. Chrome DevTools records requests while it is open; opening DevTools after the page has loaded can leave out earlier activity. The Network panel’s total reflects requests logged since DevTools opened. Chrome DevTools: Network features reference.
- If you need to follow requests across navigation, enable Preserve log in the Network panel, then repeat the navigation you want to examine.
- Review the request list and status-bar totals. Treat the total as a count for that capture, not as proof that every entry is an API request.
For repeatable comparisons, use the same page, browser conditions, and capture steps in each run. If you export or share a HAR file, check it for sensitive information such as session identifiers or personal data before sharing.
#1 Best Overall
Identify which requests are API calls and what triggered them
Start with the Network panel’s Type, Name, and Initiator columns. The type and request details help distinguish data requests from scripts, images, and other resources. The initiator can point to the script or document that caused a request; inspect it rather than guessing from a URL or filename. Chrome documents request details and columns including status, type, initiator, size, time, and waterfall in its Network panel reference.
Select a request to inspect its details. The Payload tab can show query parameters or form data, which helps establish what was sent. The timing and waterfall show when it occurred relative to other activity. A request that returns data is not automatically evidence of a defect: it may be needed by a visible storefront component or another feature.
Check whether third-party scripts contribute to the work
E-commerce pages can include third-party scripts, analytics, pixels, and app code. Shopify notes that each third-party script adds main-thread work and recommends auditing scripts, including removing unused additions. That is a performance consideration, not proof that any particular script is harmful. Shopify: Audit and remove third-party scripts.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Use a controlled block-and-compare test
- Record a baseline Network capture and note request totals and transfer information. Also inspect scripting time using the browser’s performance tools if that is part of the question.
- In DevTools, open More tools > Request conditions, then add a URL pattern for the specific domain you want to test. Chrome documents this as a way to block requests matching URL patterns. Chrome DevTools: Request conditions.
- Reload under the same conditions and compare the resulting capture with the baseline. Repeat runs if results vary, and record which domain was blocked and what changed.
- Check whether the storefront still behaves as expected. Blocking a domain is a diagnostic experiment; it does not establish that all third-party traffic is unnecessary or harmful.
Shopify’s guidance recommends inventorying script origins and comparing request, transfer, and scripting measurements when evaluating third-party scripts. Shopify: Audit and remove third-party scripts.
Rank #3
Check whether requests belong on a particular page
Expected API activity can differ by page and by the components present. Shopify recommends checking that API calls begin at an appropriate point during page loading and that requests do not appear on pages without the component that needs them. Shopify storefront performance guidance.
Compare pages with and without the relevant component, using a fresh capture for each. Use the Initiator and timing details to connect a request to its cause and place in the load sequence. A request appearing on a page that lacks the feature it serves is a reason to investigate, not by itself proof of a bug.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Investigate a possible storefront proxy before blaming it for latency
A proxy can add a network hop between the browser and Shopify, but one response header or one slow load is not enough to establish that a proxy is present or responsible for delay. Shopify recommends following the DNS/CNAME chain, comparing relevant response headers, and taking repeated time-to-first-byte (TTFB) measurements for the custom domain and the direct Shopify domain. Shopify: Storefront proxies.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problems- Follow the domain’s DNS and CNAME path to see where it resolves.
- Compare relevant response headers across the custom and direct Shopify domains.
- Repeat TTFB measurements under comparable conditions, then compare the results rather than relying on a single sample.
This helps separate a possible extra network hop from other causes of variable response time; it does not establish proxy use from a single observation.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
