Reading Browser Test Pages Without Over-Reading Them
You open a free browser test page inside one of your profiles. Some values look odd. Now what?
Mostly: calm down. A test page is a mirror. It reads a few values your browser exposes and prints them back. It doesn't know your use case, and it has no say in how any real site treats you.
This guide is about using such pages for one narrow job: confirming that the settings you chose for a profile are the settings the browser reports. It isn't a guide to scoring well on anything. If you run a multi-account browser for ad verification workflows, QA across regions or automation of your own accounts, that narrow job is usually all you need.
Know what you're looking at
Test pages come from third parties. We don't control what they list or how they define each value, and they can change without notice. So don't take a summary of their rows from us or from anyone else. Open the page, read the labels, and look up what each value means in the browser's own documentation (MDN is a good start for properties like navigator.languages or navigator.plugins).
Two habits help:
- Treat every row as a question, not a grade. "This reports X" is a fact. "X is bad" is somebody's opinion.
- Compare against a profile you opened by hand. If the hand-opened one and the scripted one differ, the difference is the lead.
Step 1: Compare what you configured with what is reported
Each JustBrowser profile carries its own settings: timezone, languages, screen, WebGL values and a proxy. Write down what you set, load a test page, and check the reported values against your list. A mismatch between a value you set and the value reported is a real finding. A red label you don't understand isn't, yet.
Common sources of mismatch in your own setup:
- Timezone and proxy. If the proxy's exit IP geolocates to London and the profile's timezone says New York, that's an inconsistency in your configuration. Fix the profile or the proxy. Each profile has its own timezone, so your system clock isn't the thing to adjust.
- Languages. Match the language list to the locale you intend the profile to have.
- Hardware identity. A WebGL renderer should be plausible for the operating system the profile presents. If you edited values one at a time, start again from a coherent combination instead.
Step 2: Check how the profile was launched
Most surprises in scripted work come from launch method, not from the profile.
Headless by default. POST /profiles/{id}/start starts headless unless you send {"headless": false} as JSON. A headless session has no real window, so its screen and viewport follow headless defaults, and window-size values can differ from a headed session. In short: headless isn't headed. If a session needs a real window, ask for one.
The right browser. navigator.webdriver returns false in a JustBrowser profile. If you're seeing true, you're probably attached to a different browser than you think, such as a stock Chromium started by your own framework. Check which cdp_url you connected to.
The right engine. Chrome profiles run JustBrowser's own Chromium; Firefox profiles run a real Firefox engine. Chrome-specific objects will naturally look different on a Firefox profile. That's expected, not a fault.
Step 3: Connect to the profile properly
When you drive a profile over CDP, a few habits avoid self-inflicted differences:
- Start the profile through the local REST API and use the returned
cdp_url. The API is local, bound to 127.0.0.1. - Use
contexts[0]and its first page. Don't callnew_context(), which creates an incognito context outside the profile. - End the session with
POST /profiles/{id}/stop.browser.close()only disconnects; the profile keeps running. - In Selenium, pin ChromeDriver to the core's current major version, or Selenium Manager will fetch a driver for your machine's own Chrome and the attach will fail.
The local API docs list every operation, with an anchor per endpoint.
Step 4: Use more than one tool, and keep your expectations small
One test page reads a few values. Other third-party pages show more detail about what a browser exposes. Use them only to inspect your own configuration, and read what they show rather than any score. If you want background on those surfaces, the audio, font and hardware fingerprinting breakdown covers the fundamentals.
Keep in mind what none of them can do. They can't tell you how a particular site will behave. Sites also look at traffic and behaviour, and some limit automated access in their terms. Read those terms for any site you automate; if a site says no to automation, a tidy test page doesn't change that.
When a value still looks wrong
Work down this list:
- Is the profile headless when you wanted headed?
- Are you attached to the browser you think you are?
- Does the value match what you configured in the profile?
- Does the proxy's location agree with the timezone and languages?
If all four check out and a value still surprises you, look the value up in the browser's documentation before assuming anything is broken. Plenty of odd-looking values are simply how a browser behaves in that mode.
FAQ
Is a test page a good measure of how a website will treat my profile?
No. A test page reads a handful of values from your browser and prints them. A real website sees far more, including network traits and behaviour, and makes its own decisions. Use a test page to check that your own profile settings came through as you configured them.
Why does my scripted profile look different from the one I opened by hand?
Check whether it launched headless. JustBrowser's local API starts a profile headless unless the request body says {"headless": false}, and a headless session has no real window, so its screen and viewport follow headless defaults.
Should I trust a summary of what a test page checks, including this one?
No. Test pages are run by third parties and change without notice. Open the page, read what it lists, and check the project's own documentation for what each value means.
What should I check first when a value looks wrong?
Start with the launch. Confirm the profile ran headed if you needed a window, that you are attached to the browser you think you are, and that the value matches what you configured in the profile.
Try JustBrowser
A multi-account browser for teams, built on a custom Chromium engine with native C++ integration (not an extension), patched on every upstream release. 40+ identity parameters per profile, plus a local REST API and CDP for Playwright, Puppeteer, Selenium. 7-day free trial, card required — then $9.99/month or $99.99/year, unlimited profiles, free team seats.
Get started → · How it differs from Multilogin / GoLogin / AdsPower
Ready to manage multiple accounts?
Seven days free, then $9.99/month — one plan, everything included.