Mobile Product Page Above the Fold: What a 390 px Screen Needs
What must be visible on a mobile product page above the fold at 390 px: image, name, price, reviews, and buy path, with a checklist table to audit yours.
mobile product page above the foldmobile product page designsticky add to cart mobilemobile ecommerce checklistabove the fold mobile
On a 390 px wide phone screen, the first view of a product page should show the product image, the product name, the price, a review summary, and either the add to cart button or a clear path to it. Everything else, including long descriptions, badges, and cross sells, can wait until the shopper scrolls.
What does "above the fold" mean on a 390 px screen?
Above the fold on mobile is whatever a shopper sees on load before touching the screen. On a 390 px wide phone, that is a strip about 390 CSS pixels wide and, once the browser's address bar and toolbar take their share, noticeably shorter than the device's full screen height.
390 px is the CSS viewport width of several recent iPhone models, such as the iPhone 13 and iPhone 14, which makes it a practical design target. Their screen is 844 CSS px tall, but Safari's interface uses part of it, and the visible area changes as the toolbar collapses on scroll. Design for the smaller visible height on first load, not the full 844 px.
The fold is not a wall. Shoppers do scroll on phones. The point of the first view is different: it has to confirm they are on the right product, show what it costs, and make the next step obvious. If any of those is missing, many shoppers never scroll far enough to find it. Our post on scroll map analysis covers how to see where shoppers actually stop.
What must be visible before scrolling?
Five things must be visible on first load: the main product image, the product name, the price, a review summary, and a path to purchase. Use this checklist to audit your own page at 390 px.
Element
Priority
What good looks like at 390 px
Main product image
Must
Shows the product clearly, takes no more than about half the visible height, swipeable for more photos
Product name
Must
Two lines at most, readable without zooming
Price
Must
Next to or right under the name, including any sale price and the original price
Review summary
Must
Stars plus count on one line, tappable to jump to reviews
Add to cart button or sticky bar
Must
Visible on load, or a sticky bar appears as soon as the shopper scrolls
Variant selector (size, color)
Should
At least the first row of options visible, or the selected option named
Delivery or stock line
Should
One short line such as "In stock, ships today"
Image count indicator
Should
Dots or "1 of 6" so shoppers know they can swipe
Header and announcement bar
Keep small
Combined height kept low, no stacked promo bars
Description, specs, cross sells
Can wait
Below the buy area, in sections or tabs
What can wait below the fold?
Anything that helps a shopper who is already interested can wait. That covers the full description, size guides, ingredient lists, shipping and returns details, full reviews, "complete the look" sections, and brand story blocks.
The common mistake is not putting too little above the fold. It is putting the wrong things there. A cookie banner, a newsletter popup, a two line promo bar, and a large logo header can together use a big share of the first screen before the shopper sees the product. Every one of those deserves scrutiny:
Cookie banners: Use a compact bottom bar instead of a full screen modal where your consent rules allow it.
Popups: Delay email popups until the shopper has scrolled or spent time on the page, never on first load.
Announcement bars: Keep one, with one short message. Rotating bars add motion that pulls the eye.
Breadcrumbs: On mobile, they often use a full line for little value. Shorten or hide them.
How do you fit everything into the first screen?
Fit it by reclaiming height from the header and image, then tightening the text block under the image. Follow these steps in order, checking the page at 390 px after each one.
Shrink the header. Reduce the logo height and combine menu, search, and cart icons into a single slim row.
Set the image ratio. A square or slightly portrait image usually works. Very tall portrait images can push the price off the first screen.
Shorten the product name. Move secondary details such as material or pack size into a subtitle or the description.
Put price and rating on tight lines. Place the stars and count on one line, then the price, without large gaps between them.
Bring the button up or make it sticky. If variant selection pushes the button down, add a sticky add to cart bar that appears on scroll.
Remove first load interruptions. Delay popups and make the cookie banner compact.
Recheck on a real phone. Emulators are close, but browser bars and font rendering differ on real devices.
Should you use a sticky add to cart bar on mobile?
Use a sticky add to cart bar when the main button sits below the first screen or disappears as the shopper scrolls through photos and details. It keeps the next step one tap away at every scroll position.
EyeCaptain
Conversions Booster
Your checkout is leaking revenue
35% of cart abandonments are caused by fixable UX issues. Our audit reveals trust gaps, hidden costs, and checkout friction points.
Keep the bar slim: price on one side, button on the other, and optionally the selected variant. If a size must be chosen first, tapping the bar should scroll to the selector or open it in a sheet, not throw an error. Make the button easy to hit; Apple's Human Interface Guidelines recommend tap targets of at least 44 by 44 points, and WCAG 2.2 sets a minimum target size of 24 by 24 CSS pixels. For where thumbs reach comfortably, see our guide to thumb zone design.
What does a good first screen look like in practice?
Here is a worked example for a hypothetical running shoe store. On a 390 px phone, the current product page shows, from top to bottom: a two line promo bar, a tall header with a centered logo, breadcrumbs, a portrait product photo that fills most of the screen, and the start of the product name. The price, rating, and button are all below the first screen. A newsletter popup also opens after two seconds.
The revised first screen looks like this:
One line promo bar: "Free returns for 60 days."
A slim header with a smaller logo, search, and cart icons on one row. Breadcrumbs removed on mobile.
A square main photo with "1 of 8" in the corner, so shoppers know they can swipe.
"Trail Runner 4, Men's" on one line, then "4.5 stars, 1,204 reviews" on the next.
"$129" with "In stock, ships today" beside it.
The first row of size buttons, and a sticky "Add to cart, $129" bar that appears once the shopper scrolls.
The popup moves to trigger after the shopper scrolls past the reviews. Nothing was removed from the page; the order and sizes changed so the buying essentials fit the first screen.
How do you check your page at 390 px?
Check it in your browser's device emulator at 390 by 844, then on a real phone, and then with a tool that captures the page as a new visitor sees it. Each step catches different problems.
In Chrome DevTools, open device mode and choose a 390 px wide device. Load the page with cache disabled so you see popups and banners as a first time visitor would. Take a screenshot of only the visible area, not the full page, and check each row of the checklist table.
Also check speed and stability, because a fast first screen matters as much as a well arranged one. On product pages the main image is often the Largest Contentful Paint element, and Google's Core Web Vitals threshold for a good LCP is 2.5 seconds. If the price or button jumps when images or fonts load, that is layout shift, which our post on layout shifts and conversions covers in detail.
A free CRO audit on EyeCaptain opens the page on a real mobile viewport and flags what competes with the buy button on the first screen.
Key takeaways
Design for the visible area of a 390 px phone after browser bars, not the full screen height.
Image, name, price, review summary, and a path to purchase must appear before scrolling.
Reclaim space from headers, promo bars, breadcrumbs, and popups before shrinking the product image.
Use a slim sticky add to cart bar when the main button sits below the first screen.
Frequently asked questions
What screen size should I design mobile product pages for?
Design for a range rather than one device, but 390 px wide is a practical baseline because several recent iPhones use it. Also check 360 px for smaller Android phones and around 430 px for large phones. The layout should hold up across that range, with the price and buying path still visible on first load at the smallest width.
Does the add to cart button need to be above the fold on mobile?
Not always, but a path to purchase does. If the product needs a size or color choice, the button can sit just below the selector, as long as a sticky add to cart bar appears when the shopper scrolls. What matters is that shoppers never have to hunt for the next step.
How tall should the product image be on mobile?
Tall enough to show the product clearly, but not so tall that it pushes the name and price off the first screen. A square image is a safe default at 390 px wide. If you use portrait images for fashion, check that the price still appears before scrolling, and add an image count indicator so shoppers swipe.
Do popups hurt mobile product pages?
Popups that cover the page on first load block the product at the moment shoppers decide whether to stay. Google's search guidelines also warn against intrusive interstitials on mobile. If you collect emails, trigger the popup after scrolling or time on page, keep it easy to close, and never show it before the product loads.
How do I see what my mobile page looks like to a first time visitor?
Open the page in a private browser window on a phone so cookies and past consent choices do not hide banners or popups. In Chrome DevTools, use device mode with cache disabled. Screenshot only the visible area, then compare it against a checklist of image, name, price, rating, and button.
Enjoyed this article?
One short email a week with practical CRO and UX tips
No spam. Unsubscribe anytime.
Find what stops your visitors from converting
EyeCaptain is an AI-powered CRO & UX audit tool that automatically scans your pages, identifies UX issues, and gives you actionable optimization suggestions to increase conversions. Try it for free, no card, no commitment.