Skip to content
DocsSearch the docsEnglishBack to siteOpen console

Tech report

Browser, operating system, device category and model, outdated versions and real page speed for your visitors. The screen to open before you decide to support — or drop — a browser, and the screen that misleads you if you do not know how coarse its buckets are.

Where the screen is#

In the console menu, under the Reports group, choose Tech. The route is /tech. The page heading is Tech overview and it holds these blocks:

Block What it shows
Overview three headline tiles: Users, Sessions, Views
Users by device category a share bar of desktop / mobile / tablet, with each category's share and user count beneath
Users by browser a bar chart of browsers
Browser and Operating system two tables with Value, Users, Sessions
Device models & screen sizes models with their maker, and screen sizes
Outdated browsers & operating systems the share of users on an outdated version and the version tables
Page speed (Web Vitals) LCP, INP and CLS in Google's colours, and tables by device, operator, connection type and page
Tech: browser, operating system and device.
Tech: browser, operating system and device.

The Download CSV link sits under the Browser table and — contrary to what you would expect — does not export just browsers. That is covered below.

The buckets are deliberately coarse#

This is the most important thing to know about the screen. AdPix does not run the user-agent string through a heavyweight parser; it looks for a handful of known tokens and drops each hit into one of a few buckets. The result is a short, stable list you can compare over time, rather than a hundred rows of half-percent versions.

Dimension Possible values
Browser Edge · Chrome · Firefox · Safari · Other
Operating system Windows · macOS · Android · iOS · Linux · Other
Device category mobile · tablet · desktop

The order the tokens are tested in is part of the behaviour, with several concrete consequences:

  • Edge is tested before Chrome, otherwise every Edge visit would land under Chrome.
  • Chromium-based browsers — Brave, Opera, Vivaldi, Yandex — all become Chrome. Their user-agent string carries the Chrome token, and that is what AdPix sees.
  • On iOS every browser lands under Safari. Chrome and Firefox on an iPhone use Apple's engine and their strings carry the Safari token; their own product tokens are not on the test list.
  • Android tablets fall into mobile. The mobile test runs first and includes the Android token, so any Android device — phone or tablet — counts as mobile. In practice tablet almost always means iPad. The Device models table does tell an iPad apart: it is listed as an iPad even in desktop mode, where it sends a Mac user agent and is recognised by Safari on an iPad-shaped screen.
Do not assume another tool draws the same lines

If you are comparing mobile share, Safari share or the size of "Other" against Google Analytics or anything else, read that tool's definition before concluding anything. A gap on this screen is usually a difference in bucketing, not in collection. For the other reasons numbers diverge, see Numbers don't match GA4.

Each table returns at most 50 rows and drops rows whose value is empty — an event that carried no user agent at all. Given the short value lists above, that cap is never actually reached for browser or operating system.

The new sections: device models, versions and page speed#

The three sections at the bottom of the page come from a fuller user-agent parse and from speed measured in the browser. Those inputs were never stored before, so all three collect from the day the updated tracking code is live on your website, and each says Collecting since that date (Jalali in the Persian console). Until then it shows "No data yet"; earlier visits never appear in these sections.

Device models & screen sizes#

  • Device models: the most-used models with their Maker, users and sessions — for example Samsung / Galaxy A54. A model code without a known trade name is shown as the raw code.
  • Screen sizes: screen width×height and users per size, for responsive-design decisions.
iPhones have no model

Apple devices report only "iPhone" or "iPad" in the user agent, so their exact model can't be reported.

Outdated browsers & operating systems#

The big number at the top is the share of users who came on an outdated browser or operating system. The two version tables — Operating system and Browsers — list each version with its users, and outdated versions carry an Outdated badge. Outdated means:

Outdated when
Android below 10
iOS below 15
Windows below 10
Safari below 15
Chrome, Edge, Samsung Internet, Firefox more than 12 versions behind the latest

If the share is high, test the website on those versions before you rely on a new CSS or JavaScript feature.

Version not reported

Some browsers no longer put the real operating-system version in their user agent. Chrome and Samsung Internet on Android send the same fixed placeholder for every phone, and every browser reports macOS as 10.15. Where the browser offers it, AdPix reads the real version and the phone model from the browser's client hints (Chrome, Edge, Samsung Internet, Opera). Where it cannot — Safari, Firefox, or a visitor who declined marketing cookies on a website with a consent banner — the row says version not reported instead of a version that would be wrong. On an iPhone, Safari 26 and later keep an iOS 18 number in the user agent; there AdPix uses Safari's own version, which always matches the iOS version.

In the Browsers table, iOS WebView and Android WebView are pages opened inside an app (Instagram, Telegram and the like), not in the browser itself.

Page speed (Web Vitals)#

AdPix measures how fast pages really load in your users' browsers — not in a lab. Four cards at the top show Google's core metrics and the server's response time:

Metric What it measures Good Needs improvement Poor
LCP — main content load when the largest part of the page appears up to 2.5 s up to 4 s above
INP — response to interaction how slowly the page answers a click or tap up to 200 ms up to 500 ms above
CLS — layout shift content jumping around while loading up to 0.1 up to 0.25 above
TTFB — server response time until the server sends the first byte up to 0.8 s up to 1.8 s above

Each card is the 75th percentile: 75% of page loads were this fast or faster (Google's own measure). The badge next to it gives its rating, and the bar beneath it splits loads into good, needs improvement and poor.

The table below repeats the four metrics for one breakdown at a time. Switch it with the tabs above the table: Operator (the default), Page, Device and Connection (4G, 3G…). Each cell is coloured by its rating, as in the legend under the table, and the column header carries the unit: LCP and TTFB in seconds, INP in milliseconds. Use it to find the page or operator the slowness comes from.

  • Speed is measured only with the user's statistics consent.
  • Each page load sends one measurement that is never counted as a page view or an event and never counts toward the monthly page-view quota.
  • The measuring script loads separately after the first page view and adds nothing to the base data stream.

The three headline numbers#

The usual definitions, and exactly the same numbers you see on the Demographics report:

Tile Definition
Users distinct visitor identifiers seen in the selected range
Sessions distinct sessions; an event with no session is not counted
Views page_view events only

"User" here also means a distinct browser, not a distinct person. Someone arriving on desktop Chrome and mobile Safari fills two rows in the browser table and counts as two users in the headline. That is why you should not sum the user column across rows — these tables exist to be read as proportions.

Sessions is the second column, and often the more useful one

Both tables carry sessions alongside users. When one browser's sessions-per-user ratio sits noticeably below the rest, that usually points at something breaking in that browser — not at its users being less interested.

What never reaches this screen#

  • Bots. User agents recognised as crawlers are separated out before reporting, which is why no search-engine crawler appears in your list.
  • Test traffic and the internal IP blocks you listed under Admin → Website details → Traffic filtering.
  • Server-side events have no browser; their tech values are only populated when your server-to-server call passes the visitor's user-agent string in context.

Comparing with a previous period#

Turn Compare on in the date-range picker and all three headline tiles gain a percentage change — green with ▲, red with ▼ — against the same numbers over the second window.

The charts and both tables always reflect the primary range. To see how one browser's share moved between two periods, pull the first range and export it, then the second. The comparison modes are covered in Date ranges and comparison.

CSV export#

This page's export is a cross-tab, not a copy of the browser table: each row is one combination of browser, operating system and device category, with the user count for that combination — up to 5,000 rows, over the range and website selected on screen.

That is exactly what combination questions need: "how many are on Safari on mobile?", "what share of Firefox is on Windows?" — questions the two independent on-screen tables cannot answer.

There is no sessions column in this file, only users. And as with every CSV export here, column order is not guaranteed — resolve columns from the header row, not by position. If the range holds no rows, the file comes back completely empty.

Frequently asked questions#

Why aren't Brave and Opera in the list?

Both are Chromium-based and their user-agent string carries the Chrome token, which is what AdPix classifies on — so both land under Chrome. That is deliberate: the list stays short and stable over time instead of splintering into dozens of sub-percent names.

Why is my mobile share different from Google Analytics?

Because the bucket boundaries differ. In AdPix any user agent carrying the Android token counts as mobile, including Android tablets. A tool that separates tablets puts the same traffic in a different bucket.

What does Other mean in the browser column?

Any browser whose user-agent string carries none of the four known tokens — Edge, Chrome, Firefox, Safari. In-app browsers, Android's stock browser and unusual clients typically collect here.

Why don't the user columns add up across tables?

One visitor can appear on two browsers or two operating systems within the same range and is counted in each matching row. Every table is counted independently — read the proportions, do not sum the columns.

Why are page speed and device models empty for past months?

Those sections are built from inputs that were not stored before this release. Data starts on the day the updated tracking code went live on the website, and that date is shown above each section.

Build with the APIUnderstand where revenue comes from.
Was this page helpful?