How to Compare Mobile Website Screenshots on Airtel and Jio Networks

To compare a mobile website on Airtel and Jio, capture the same page on the same physical phone, at the same location, with the same browser, viewport, orientation, and page state. Turn off Wi-Fi and VPNs, test each live SIM separately, and repeat the runs. Save the screenshots with their conditions. This controls many causes of visual variation, but a screenshot by itself cannot prove that the carrier caused a difference or measure page speed.

For a live Airtel-versus-Jio comparison, the browser must actually load the page over each carrier’s cellular connection. A cloud screenshot API cannot recreate that carrier path: it captures from its own environment. Use a phone and DevTools for the carrier comparison; use a service such as ScreenshotNeo for repeatable, automated website captures outside that live-network test.

1. Define what you are comparing

Decide what counts as the result before you start. A screenshot comparison can answer whether two captured page states look different. It does not, alone, establish why they differ or how long the page took to load.

Question	Capture and record
Does the first visible screen differ?	Capture the same viewport after a predefined short wait, such as a fixed number of seconds after navigation starts. Record that interval.
Does the settled page differ?	Wait for the same page event or a fixed wait time, then capture the same viewport. Define “settled” consistently; dynamic pages may never become fully idle.
Are below-the-fold sections or lazy images affected?	Capture the full page only after both runs reach the same endpoint. For long pages, scrolling can trigger more content, so use the same scroll and wait procedure.
Is the question about speed?	Capture timestamps or a browser network/performance log in addition to screenshots. Do not infer a duration from the image.

Keep first-load and settled-page observations separate. A cached revisit can look different from a cold visit, so either clear the browser state before every run or label the runs as warm-cache tests. For sites that personalize by account, region, consent, or experiment assignment, use the same account and state where possible and note any remaining differences.

2. Control the handset, browser, and page

Use one physical phone for both SIM runs where possible. Record its model and operating system. If you use two phones, record both models; hardware, display, and browser differences can affect the result.
Use the same browser and browser version. Keep orientation, text size, zoom, accessibility settings, and display scaling unchanged.
Use the exact same URL, including path and query string. Start from the same page state: logged-in status, consent choice, locale, and any needed navigation steps.
Turn off Wi-Fi and VPNs. Confirm that cellular data is active for the SIM being tested. Disable automatic switching to Wi-Fi or another data SIM if the phone offers that option.
Keep the phone in the same place and orientation. Avoid moving between indoor and outdoor locations during a comparison.
Record whether the phone reports 4G or 5G for each run, plus visible signal changes. Keep 4G and 5G runs separate when you want to compare network modes.

A dual-SIM handset is optional. You can switch one SIM at a time in the same phone, or use two existing phones and report their models. One phone with sequential SIM swaps usually makes it easier to hold the handset constant.

3. Capture the live Airtel and Jio runs

Choose a quiet test location and write down the date, local time, and whether the phone is indoors or outdoors.
Load the target page on Airtel cellular data. Use the same page state and the capture endpoint you selected in advance.
Save the screenshot with a descriptive filename, for example airtel-4g-run-01-viewport.png. Keep the original image; do not resize or recompress it before comparison.
Switch cellular data to Jio, confirm Wi-Fi remains off, and load the same URL. Capture the same viewport or full-page endpoint, using the same wait rule.
Repeat several runs for each SIM. Alternate which carrier goes first when practical (Airtel, Jio, then Jio, Airtel) to reduce the chance that time-of-day or changing page content always favors one order. Repeating and alternating are practical controls, not a formal carrier-testing standard.
Compare recurring patterns across runs. A single missing image that appears in the next run may reflect a transient page or network condition rather than a stable difference.

Useful filenames include carrier, radio mode, run number, and capture type. Keep a small run log with URL, date/time, place, phone, OS/browser version, radio mode, signal notes, wait rule, cache state, and file name.

4. Capture with Chrome DevTools

Chrome DevTools device mode can set a mobile viewport and capture either the visible viewport or the full page. Its device emulation is useful for controlling viewport dimensions; it does not turn a desktop connection into an Airtel or Jio connection. For a real carrier test, use DevTools on the connected phone through remote debugging, or use the browser on the phone and capture its screen. Chrome documents viewport and full-size screenshot capture in its Device Mode guide.

Open the target page in Chrome. For desktop viewport experiments, open DevTools and enable the device toolbar.
Set a specific device or exact viewport width and height. Record the dimensions. Keep the same setting for both comparison captures.
For a viewport image, use the DevTools menu and choose Capture screenshot. For a full page, choose Capture full size screenshot.
For an actual Airtel/Jio test, ensure the page request is using the phone’s selected SIM. Device mode alone only emulates viewport and device characteristics.

For a phone-only workflow, take a native device screenshot at the agreed page state. Confirm the browser chrome is either included in both images or excluded from both. Crop only after saving originals, and apply the same crop to both.

5. Compare the images and interpret differences

Use side-by-side viewing or an image-difference tool, but inspect the original screenshots too. Anti-aliasing, animation frames, clocks, rotating ads, personalized content, and small scroll offsets can create pixel differences without a meaningful network effect.

Visual completeness: note missing images, placeholders, blank sections, or text that has not appeared.
Layout stability: note shifts, changed line wrapping, font substitutions, and elements that move between early and settled captures.
Repeatability: distinguish a pattern seen across runs from a one-off capture.
Timing: report timestamps or logs separately; do not label an image as “faster” based only on its appearance.
Scope: state the tested phone, location, date/time, radio mode, and number of runs in any conclusion.

If only one SIM shows a repeatable visual issue, investigate with browser network logs and a second location or time before calling it a carrier fault. The page’s server, CDN, dynamic content, browser cache, radio conditions, signal strength, device load, and time-dependent scripts can all contribute. A controlled screenshot comparison narrows the question; it does not isolate every cause by itself.

6. Keep simulated-network tests separate

DevTools and Lighthouse can simulate a constrained connection for repeatable development checks. Such a run is not a live Airtel or Jio measurement. If you use Lighthouse’s documented mobile throttling preset, identify it by name and record the tool version: the documented values are 150 ms latency, 1.6 Mbps download, 750 Kbps upload, and no packet loss. Google describes these as an emulated mobile profile, not as measurements of either Indian carrier. See the Lighthouse throttling documentation.

Use simulated throttling to ask, “How does this page behave under this repeatable profile?” Use live SIM runs to ask, “What did this handset receive on this operator at this place and time?” Report the two kinds of evidence in separate sections.

7. Use national and coverage data carefully

Published aggregate results provide context, not a prediction for one street, building, handset, or page. nPerf’s 2025–2026 India barometer reports overall download figures of 62.38 Mbps for Airtel and 63.43 Mbps for Jio, and web-browsing scores of 59.86% and 60.57%, respectively. These are national-period aggregates; the report also separates 5G results. They cannot tell you which SIM will load your particular page better at your test location. See the nPerf India barometer.

Coverage maps also have limits. Airtel says its displayed coverage and quality are predicted from outdoor estimates and that actual experience can vary with geography and building density. See the Airtel Open Network FAQ. TRAI drive-test reporting likewise describes results for the tested route and day/time; its methodology uses live operator SIM sessions and test handsets. See a TRAI drive-test release published by PIB. These sources reinforce why a local, time-stamped test should be described with its scope.

8. Or skip the browser setup

For repeatable captures of a page from ScreenshotNeo’s capture environment, make one API request. This is useful for monitoring the same URL and layout over time, but it does not run the request over your Airtel or Jio SIM. Use the live-phone method above for a carrier comparison. See the ScreenshotNeo API documentation.

cURL

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

Python

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)

Node.js

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const image = Buffer.from(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', image));

ScreenshotNeo removes cookie and consent banners, newsletter popups, and chat widgets before capture. Bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots, and the free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. Start with 1,000 free screenshots a month with no card.

9. Troubleshooting

Symptom	Likely cause	What to do
The two screenshots use different layouts	Viewport, orientation, text scale, zoom, browser version, or page state changed.	Match the phone and browser settings; verify dimensions and orientation before each capture.
Wi-Fi may have carried one run	Automatic Wi-Fi or data-SIM switching remained enabled.	Disable Wi-Fi and switching, confirm the active data SIM, and repeat the run.
An image or section is missing once	Transient load, lazy content, animation, or a one-off browser/network event.	Repeat the same capture endpoint and wait rule; inspect the browser network log before attributing cause.
The full-page captures have different lengths	Content loaded at different times, lazy loading was triggered differently, or the page is dynamic.	Define the endpoint, use the same scroll/wait sequence, and compare matching sections. Prefer viewport captures when full-page endpoints cannot be aligned.
Results change from run to run	Radio conditions, page content, signal, cache, or background activity changed.	Record conditions, repeat and alternate carrier order, and report the variation instead of selecting one favorable run.
DevTools throttling seems to contradict the phone	Throttling is an emulation profile, not the live operator network.	Label the simulated and live results separately; do not use the preset as an Airtel/Jio proxy.
A cloud screenshot differs from both phone captures	The cloud capture uses a different network location, device/browser environment, or page state.	Use the cloud capture for automated baseline monitoring, not for attributing the result to either local SIM.
A ScreenshotNeo request does not return an image	The key, URL, or response may be invalid or unsuccessful.	Check the API key and URL, inspect the response status and headers, and consult the API documentation.

10. Performance, reliability, and cost

For a manual local comparison, the main costs are test time, mobile data, and keeping the device conditions consistent. Several runs take longer but reduce the risk of treating a transient state as a stable pattern. Avoid running unrelated downloads or updates during the test, and preserve the original captures and log together.

For automated baseline screenshots, use a fixed URL and capture configuration, and compare results over time. ScreenshotNeo offers caching with a TTL you choose, async jobs with signed webhooks, and bulk capture for up to 100 URLs per call; these options can help with scheduled or multi-page work. Cloud captures do not establish local Airtel/Jio behavior. ScreenshotNeo pricing is Free: 1,000 shots/month; Starter: $5 for 3,000; Growth: $15 for 15,000; Pro: $39 for 60,000; Scale: $99 for 250,000; Business: $249 for 1,000,000. Yearly billing gives two months free, and every feature is available on every plan.

FAQ

Can one screenshot show which network is faster?

No. It shows rendered pixels at one capture point. Use timestamps or browser performance/network records for timing evidence.

Do I need a dual-SIM phone?

No. Sequentially switch SIMs in one phone, or use two phones and disclose their models.

Can DevTools device mode test Airtel or Jio?

It can control the emulated viewport. It tests a carrier only when the actual page request travels over that carrier’s live cellular connection.

Should I compare 4G and 5G together?

Keep radio modes distinct if the aim is to compare operators under similar conditions. Record the mode shown by the handset for every run.

Can ScreenshotNeo replace the live carrier test?

No. It is useful for repeatable website screenshots and automation from its capture environment, not for measuring a page over your phone’s Airtel or Jio connection.