You’ve been sent a redesigned website or the landing page for this year’s big campaign. Now you need to look it over and give feedback.
You want to preview your site on different screen sizes to catch layout problems your customers might hit, before you send feedback. People often open a site on a phone and later come back on different devices, such as a tablet or a computer.
The same page can look fine on larger screens and still hide a menu or cut off the main action on smaller screens.
If you have visitor data, use the most common desktop, tablet, and phone sizes from it to see which views matter most. If you don’t, start with 1920 by 1080, 820 by 1180, and 390 by 844, then preview the live page.
Those three common screen sizes match screens many people use. In Statcounter’s October 2026 worldwide tables, 1920 by 1080 was the most common desktop size. 820 by 1180 is a common page size for some iPad Air models, and 390 by 844 is a common page size for the standard-size iPhone 12, 13, and 14.
Online Website Previewer shows a live page at those sizes. Preview there, and if your visitor data listed others, write down which ones this pass could not show.
You’ll need the page address to open that live preview.
Start with a Desktop, Tablet, and Phone Size
A practical starting option is one desktop size, one tablet size, and one phone size.
This starter set is not a substitute for the site’s own visitor data, and it is not a required minimum. If you can open this site’s visitor data, check whether your visitors match those sizes.
If You Have the Site’s Visitor Data
If you have access to visitor data in Google Analytics 4 or another tool, use it when you want a closer match to this audience. Those numbers describe these visitors more closely than a worldwide chart can.
Find Screen Sizes in Google Analytics 4
- Open Reports, then Tech, then Tech details.
- In the report controls, set the main breakdown (primary dimension) to Screen resolution.
- Use Device category to look at desktop, mobile, and tablet separately.
On Tech overview, you can also use the Users by screen resolution card.
Write down the most common size in each group.
If two sizes in the same group both account for a large share of visits, note both. You may want to check that extra size on a real device or in a previewer that can show it.
Google’s help page for the Tech details report describes Screen resolution as the width and height of the screen, in pixels.
What These Analytics Numbers Actually Measure
When you look at Screen resolution in Google Analytics, you are looking at the whole display — the size recorded for that visit. A visitor can have a 1920 by 1080 monitor and keep the browser much smaller than that. The page you are reviewing follows the window, not the monitor.
A resolution printed on a device spec sheet does not necessarily describe the space the page actually uses.
A top desktop size is still useful because it tells you many visitors have a screen that large, even though it does not prove every visitor browses in a window that large. Treat it as a starting reference for the screens people own, not as proof of the space the page actually had.
A few other things can change how you use the list:
- A pair like 820 by 1180 and 1180 by 820 is often the same device turned on its side, so check both orientations when you preview the page.
- A tablet can be counted as a phone, or the other way around, so if a popular size looks surprising, check the device category before you treat it as your main phone or tablet target.
- If the site is new or has little traffic, the top of the list will jump around, so use the starting sizes above instead of waiting for more visits.
- Less common sizes can collapse into an “(other)” row, so treat that row as leftover traffic, not as a size you can preview.
If You Use a Different Analytics Tool
This Guide can’t cover every menu. If you don’t use Google Analytics 4, open your tool’s own help page for the current steps and screenshots:
- Adobe Analytics’s Monitor resolution dimension
- Matomo’s Devices report, including Screen resolution
- Mixpanel’s default properties, including Screen Width and Screen Height
- Kissmetrics’s automatically tracked properties, including KM Screen Resolution
- PostHog’s autocapture properties, including Screen Width and Screen Height
If You Do Not Have Analytics Access
You can still review the page with the starting sizes above. That is enough to begin a visual first pass, but it does not mean you have covered every size your audience uses.
If a public table shows another size with a large share, or you notice a layout problem, check that extra size in a previewer that can show it.
If you want public figures to compare against, Statcounter publishes free tables. The links open the current tables, which update over time.
The percentages below are for October 2026. You do not have to preview every row.
In October 2026, worldwide, the most common sizes were:
Desktop (Statcounter desktop table)
- 1920 by 1080: 27.82%
- 1536 by 864: 9.13%
- 800 by 600: 8.85%
- 1366 by 768: 7.48%
Mobile (Statcounter mobile table)
- 414 by 896: 12.67%
- 360 by 800: 8.57%
- 384 by 832: 7.24%
- 390 by 844: 5.33%
Tablet (Statcounter tablet table)
- 1280 by 800: 7.96%
- 800 by 1280: 7.89%
- 768 by 1024: 7.39%
- 820 by 1180: 4.71%
These figures will change. Check the tables when you review a page, and note the month they cover.
As noted above, 1280 by 800 and 800 by 1280 on that list may be the same size turned on its side.
When a Report Lists Device Models Instead of Screen Sizes
Some reports tell you which phones or tablets are common, and skip a screen-size table. Detailed charts on publisher sites such as Statista are also often behind a login.
If you already have sizes from visitor data, or you are using the starting sizes above, you can skip this.
If you only know a popular model, look up the page size a website uses on that model. That number is often smaller than the resolution printed on a spec sheet.
For the standard-size iPhone 12, 13, and 14, a common page size is 390 by 844 pixels. That does not cover every iPhone in those families. For some iPad Air models, a common page size is 820 by 1180 pixels.
A worldwide table describes a general public, so your landing page may attract a different mix of phones and screens. If you later get access to visitor data, use those numbers when they look stable.
Preview the Page at the Sizes You Chose
This pass uses the three views the previewer shows: 1920 by 1080 on desktop, 820 by 1180 on tablet, and 390 by 844 on phone. Open the live page at those widths and look at the layout.
The previewer is free and does not need an account.
- Paste the page address, then press Preview.
- Compare the desktop, tablet, and phone layouts.
- Check that the text is easy to read and that image sizes fit the screen. Try the menu and the main action, not only whether you can see them.
You can focus on one device, rotate the phone or tablet, and zoom in for a closer look. People on phones and tablets can see your site in both landscape and portrait mode, so check the layout both ways.
If your visitor data pointed to other sizes, say in your notes which ones you checked and which ones you could not match in this pass.
This is a visual check in your current browser, so use it to look at the layout. It does not automatically score the site, and it does not replace testing on real devices and in other browsers.
When You Send Your Review Notes
Tell your team or client which sizes you checked, and whether those sizes came from the site’s own visitors, from a public table, or from the three starting sizes above. That context is part of the feedback.
If something looks off, include the page address, the size and orientation, what you saw, and why it matters. Include a screenshot if you can.
For example: “I reviewed the live page at https://www.example.com/landing at desktop 1920 by 1080, tablet 820 by 1180, and phone 390 by 844, including phone and tablet landscape. I checked readability, images, the menu, and the main action. On phone in portrait at 390 by 844, the main offer button is cut off on the right, so I could not use the main action.”
