I see that the "screen resolution" is smaller than the "browser size" in MANY cases. How is that possible?
Some of these entries look a bit fishy. Any ideas what's going on? Is there a bug in Google Analytics?
Webmasters Stack Exchange is a question and answer site for webmasters. It only takes a minute to sign up.
Sign up to join this communityI see that the "screen resolution" is smaller than the "browser size" in MANY cases. How is that possible?
Some of these entries look a bit fishy. Any ideas what's going on? Is there a bug in Google Analytics?
I've tried for the last couple of days to unveil the mystery around how the Browser Size dimension in Google Analytics is computed, and couldn't find an authoritative source yet.
In my own observations of GA data, across different GA accounts, targeting wildly different websites, Browser Size is capped at 2610x1610 top. And I don't know why. Of course that is so wrong that makes me wonder what Browser Size represents, actually.
Anyway, back to the question
How can Screen Resolution be smaller than Browser Size in Google Analytics?
The viewport width is directly innerWidth
, which can be increased or decreased by zooming out or in, respectively.
For example, lest's start from a browser window which is 1000px wide at 100% zoom.
innerWidth
becomes 2000px wideinnerWidth
becomes 500px wideIn Google Chrome, a maximised browser window spans all the available screen width, thus (at 100% zoom and with a devicePixelRatio
of 1) innerWidth
happens to be equal to the screen width. At other zoom levels, innerWidth
can be bigger or smaller, depending on the zoom level.
It would have been great if Browser Size had been innerWidth
.
Utter speculation, but I'm new here and want to help:
I think the resolution that the browser tells the website to render at is different from the actual screen-resolution of the phone. Especially with the 800x600 case I can see how that could increase user experience.