Lazada Singapore serves a plain HTTP client 1,196 words, a canonical link and an h1 in 469,188 bytes. We measured it through residential proxies on 28 September 2026, and the headless browser that most tutorials start with returned 1,197 words for 1,841,729 bytes and 48 seconds. From a Malaysian exit the same URL served the same Singapore page with 1,193 words. Lazada proxies come down to plain HTTP on the residential Basic line, pinned to the domain's own country, and this page shows the arithmetic behind that.
The suggest box has no volume for Lazada proxies, and that tells you who is asking
Google's autocomplete in Singapore returns nothing at all for "lazada proxies" and nothing for "proxies for lazada". The demand exists under the scraper words: "lazada scraper api", "lazada product scraper", "lazada review scraper", "lazada data scraper". The results page for the head term is filled anyway, with two per-IP vendor pages, a guide on running several Lazada accounts, a residential-proxy essay, an r/internationalshopper thread about shopping proxies and three Lazada tag pages selling MTG proxy cards.
We read the two vendor pages that rank. One never mentions a Lazada URL. The other lists price intelligence, competitor monitoring, product extraction and price tracking, which is the right list, and then does not fetch a page to show what any of those return. The person typing "lazada product scraper" wants to know what the site sends back and what it costs. That is the question we can answer with numbers.
Plain HTTP returns the whole home, with canonical and h1 intact
We audited lazada.sg from a Singapore residential exit in one call that fetches twice: once as a pure HTTP client with no JavaScript, once in a headless browser.
| Fetch | Status | Bytes | Words | Canonical | h1 | Time |
|---|---|---|---|---|---|---|
| Singapore exit, plain HTTP | 200 | 469,188 | 1,196 | https://www.lazada.sg/ | present | 4.6 s |
| Singapore exit, rendered | 200 | 1,841,729 | 1,197 | https://www.lazada.sg/ | present | 48.3 s |
| Malaysia exit, plain HTTP | 200 | 469 KB class | 1,193 | https://www.lazada.sg/ | present | 7.1 s |
| Malaysia exit, rendered | 200 | 1.8 MB class | 1,198 | https://www.lazada.sg/ | present | audit 59.1 s |
The plain document already has the pieces a parser keys on: the title "Lazada Singapore | Always The Better Price & Free Shipping", the meta description, a self-referencing canonical and an h1 that reads "Best Shopping Experience Guaranteed at Lazada Singapore". The audit's diff reports no title change, no description change, no h1 that exists only after JavaScript, no canonical missing without it. One word appeared in the render. It cost 1,372,541 bytes and 44 seconds.
Two things are absent in both views and worth knowing before you build. There is no JSON-LD on the home, of any type. And the response headers say the home is served from Alibaba's edge cache with cache-control: max-age=60 and an x-swift-cachetime: 60: the document you fetch can be up to sixty seconds old. For a price monitor that polls a page every few seconds, that is the floor on freshness; polling faster than once a minute buys the same cached bytes again.
On Lazada the domain picks the market, and the exit only picks whether you get in
Lazada operates in six countries, Indonesia, Malaysia, the Philippines, Singapore, Thailand and Vietnam, according to the Lazada Group's own About page, each on its own domain; lazada.com.my, whose robots.txt we also fetched, is the Malaysian one. So we asked the obvious question: what does lazada.sg do when the request comes from Malaysia?
It serves lazada.sg. Same title, same canonical, 1,193 words against 1,196, and the three-word difference is a rotating module, not a localisation. The exit did not redirect to lazada.com.my, did not change the currency and did not change the language. That is the opposite of what we measured the same day on AliExpress, where a German exit rewrites the whole domain, and the same shape as Shopee, Lazada's neighbour in Singapore, where the exit decides only whether the page arrives at all.
The instruction that follows is simple, and it saves a common mistake. To read the Malaysian market you change the domain to lazada.com.my, and you pin a Malaysian exit because that is the country the domain expects. You do not point a Malaysian exit at lazada.sg and expect ringgit. Country on the exit and country in the hostname should agree, and the hostname is the one doing the work.
What the render costs on Lazada, and what to do with the money instead
Every fetch here went through residential proxies on the Basic line at $0.80/GB. Counting a gigabyte as 10^9 bytes:
| Fetch | Bytes | Fetches per GB | Cost per fetch | Words |
|---|---|---|---|---|
| Home, plain HTTP | 469,188 | 2,131 | $0.00038 | 1,196 |
| Home, rendered | 1,841,729 | 542 | $0.00148 | 1,197 |
The render is 3.9 times the bytes and 10 times the wall-clock for one word. At a thousand pages a day the difference is 1.37 GB, or about $1.10 a day on the Basic line and $3.16 on mobile proxies at $2.30/GB, spent on a browser the page does not need. Nothing in six fetches from two countries challenged the IP, so there is no reason to buy the more expensive network either. The whole budget goes into more pages, more often, within the sixty-second cache window.
The place a Lazada job does spend is category and search pages, which are paginated. The same rule applies: fetch them plain first, and reach for rendering only on a page whose plain response has a title and still no price. Our note on how to price monitor covers the polling cadence and the diff logic that turns these fetches into a price history.
A 221-byte robots.txt that names three OpenAI crawlers
lazada.sg/robots.txt is the whole file, and it is short enough to quote entire:
User-agent: *
Disallow: /wow/gcp/sg/member/login-signup
Disallow: /undefined/
Disallow: */undefined/$
Disallow: */undefined$
User-agent: OAI-SearchBot
Allow: /
User-agent: GPTBot
Allow: /
User-agent: ChatGPT-User
Allow: /Four disallow lines for everyone, all of them the login page and a broken-URL pattern, and then an explicit Allow: / for OpenAI's three crawlers. No crawl delay, no product or search exclusions, no sitemap line. Lazada is one of the few marketplaces we have measured that tells AI crawlers in writing that the whole site is theirs to read, which sits neatly beside the finding that its pages are complete without JavaScript. We track which platforms take that position in should I block AI crawlers.
What the file does not license is accounts. The login-signup path is the one disallowed surface, and the Lazada Seller Center, which redirected our fetch straight to its login page, and the Lazada Open Platform, the official API for sellers, both sit behind credentials. Running several buyer or seller accounts through proxies, which the second organic result for this keyword promotes, is governed by Lazada's terms and is not something we help with. Everything measured on this page was logged out and public.
Where the official data is, and when to use it instead
The Lazada Open Platform at open.lazada.com is a JavaScript application with an API documentation index, zero words of either without a browser; it is the official API for sellers reading their own catalogue and orders behind developer credentials. If you are a seller checking your own listings, that is the route and it needs no proxy at all. For everyone else, for public price and availability reads across other sellers, there is no feed, and the plain-HTTP page measured here is the surface.
That is also the honest limit of this post. There is no Lazada collector in our catalogue today. The web scraping API with engine: tls is the tool, the residential Basic line is the network, and the numbers above are what to expect per page. When a marketplace does have a collector, the difference is rows instead of bytes: on the same day AliExpress search returned 20 items with price, original price and discount in 4.5 seconds, and Amazon search does the same job with ASINs and ratings.
The setting that works on Lazada
- Network: residential, Basic line at $0.80/GB through residential proxies. Six fetches from two countries, nothing scored the IP; the cost is bytes and Basic is the cheapest byte.
- Fetch mode:
engine: tls, plain HTTP. 1,196 words, canonical and h1 from the home in 469,188 bytes and 4.6 seconds; the render adds one word for 1,841,729 bytes and 48.3 seconds. - Country: pin the exit to the domain's own market,
sgfor lazada.sg. A Malaysian exit received the identical Singapore page with 1,193 words; to read Malaysia you change the hostname to lazada.com.my and pinmy. - When the proxy is not enough: no Lazada collector exists yet. Point the web scraping API at category, search and product URLs with
engine: tls, poll no faster than the sixty-second edge cache, and render only a page whose plain fetch has a title and no price. - Failed requests are never billed, and every account gets $2 of free API usage per month, which is about 5,300 plain fetches of the Lazada home.