A responsive website hero needs more than a wide image: it needs a crop that works on small screens, HTML text that stays accessible, dimensions that reserve space, and an image file sized for the visitor’s display. A useful starting point is a 16:9 source—1920×1080 is the U.S. National Science Foundation’s preferred full-size hero—but the image’s focal point and delivery matter as much as its original dimensions.
What size should a website hero image be?
Start with a wide, crop-safe source image. The National Science Foundation recommends a width-to-height ratio of at least 1.7:1 for a hero and identifies 1920×1080 (16:9) as its preferred full-size image. It also lists 1366×768 (16:9) as an alternative with less detail. These are useful source-image benchmarks, not a promise that one file will look right at every viewport.
Plan the image around the narrowest important screen. A desktop-wide image displayed with cover on a phone loses content at its sides; a subject placed near an edge may disappear, and a subject behind the headline or call-to-action may become hard to see. Keep the essential subject and visual cues away from the edges and from areas where text will sit. If the subject must remain fully visible, create a separate mobile crop rather than relying on automatic cropping.
A hero should work as visual atmosphere, not as a poster containing information the page needs to communicate. The NSF puts it plainly: “Text in an image, except for pure decoration, creates accessibility issues.” Keep headlines, supporting copy, and buttons in HTML.
#1 Best Overall
- CRISP CLARITY: This 23.8″ Philips V line monitor delivers crisp Full HD 1920x1080 visuals. Enjoy movies, shows and videos with remarkable detail
- INCREDIBLE CONTRAST: The VA panel produces brighter whites and deeper blacks. You get true-to-life images and more gradients with 16.7 million colors
- THE PERFECT VIEW: The 178/178 degree extra wide viewing angle prevents the shifting of colors when viewed from an offset angle, so you always get consistent colors
- WORK SEAMLESSLY: This sleek monitor is virtually bezel-free on three sides, so the screen looks even bigger for the viewer. This minimalistic design also allows for seamless multi-monitor setups that enhance your workflow and boost productivity
- A BETTER READING EXPERIENCE: For busy office workers, EasyRead mode provides a more paper-like experience for when viewing lengthy documents
Choose between a background image and an img element
Use an HTML <img> when the image conveys content that needs an appropriate text alternative, or when you want the browser to select among responsive image files. Use a CSS background when the image is decorative and the content can stand without it. A background is convenient for layering HTML over a hero, but its URL can be harder for the browser to discover early, and it does not provide an alt attribute.
| Approach | Best fit | Trade-off |
|---|---|---|
Responsive <img> or <picture> |
Meaningful imagery, responsive file selection, and an explicit text alternative | Requires image markup and sensible alt text; cropping still needs deliberate sizing and positioning |
| CSS background | Decorative atmosphere behind HTML content | No alt text; can be discovered later than an image in the document, and responsive variants take extra CSS or markup |
With either approach, distinguish between filling a box and showing the entire image. object-fit: cover keeps the image’s proportions while cropping it to fill an <img> box. object-fit: contain shows the whole image but may leave empty space. For a background, the comparable common setting is background-size: cover. Use object-position or background-position to move the crop toward the focal subject.
Build responsive image markup
For a content-bearing hero, provide intrinsic width and height on the fallback image, then offer multiple widths with srcset and sizes. The browser uses those hints to choose a suitable file for the rendered width and screen density. Adjust sizes to the actual component width; do not use 100vw blindly if the hero is inside a constrained container.
<picture>
<source type="image/avif"
srcset="hero-480.avif 480w, hero-960.avif 960w, hero-1920.avif 1920w"
sizes="100vw">
<source type="image/webp"
srcset="hero-480.webp 480w, hero-960.webp 960w, hero-1920.webp 1920w"
sizes="100vw">
<img src="hero-960.jpg"
srcset="hero-480.jpg 480w, hero-960.jpg 960w, hero-1920.jpg 1920w"
sizes="100vw"
width="1920" height="1080"
alt="Descriptive subject of the hero image"
fetchpriority="high"
class="hero-image">
</picture>.hero-image {
display: block;
inline-size: 100%;
block-size: auto;
aspect-ratio: 16 / 9;
object-fit: cover;
object-position: center;
}
.hero {
position: relative;
overflow: hidden;
}
.hero-copy {
position: absolute;
inset: auto auto 2rem 2rem;
z-index: 1;
}The example assumes a full-viewport-width hero. For a container capped at 72rem, for example, describe that layout in sizes with a matching media condition instead of claiming the image will occupy the full viewport at every width. A width-descriptor srcset without sizes makes the browser assume 100vw, which can lead to an unnecessarily large download.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesUse <picture> when you need format switching or art direction, such as a different mobile composition. Keep a usable src fallback: Google Search Central recommends a fallback because not every browser or crawler necessarily understands responsive image attributes. AVIF or WebP can reduce image bytes when your delivery setup supports them, with JPEG or PNG as a fallback where appropriate.
Rank #2
- CRISP CLARITY: This 22 inch class (21.5″ viewable) Philips V line monitor delivers crisp Full HD 1920x1080 visuals. Enjoy movies, shows and videos with remarkable detail
- 100HZ FAST REFRESH RATE: 100Hz brings your favorite movies and video games to life. Stream, binge, and play effortlessly
- SMOOTH ACTION WITH ADAPTIVE-SYNC: Adaptive-Sync technology ensures fluid action sequences and rapid response time. Every frame will be rendered smoothly with crystal clarity and without stutter
- INCREDIBLE CONTRAST: The VA panel produces brighter whites and deeper blacks. You get true-to-life images and more gradients with 16.7 million colors
- THE PERFECT VIEW: The 178/178 degree extra wide viewing angle prevents the shifting of colors when viewed from an offset angle, so you always get consistent colors
Keep the hero from hurting LCP or layout stability
A visible hero image can be the page’s Largest Contentful Paint (LCP) element, so loading it late can delay the main visual response. Do not lazy-load a hero image above the fold. web.dev’s guidance is direct: “For a hero image above the fold, don’t use loading.” If a framework applies lazy loading automatically, ensure the visible hero is eager or uses the browser’s default loading behavior.
Consider fetchpriority="high" only for the image that is genuinely the page’s critical LCP resource. High priority is not free: prioritizing one request means other requests may receive less priority. Do not mark every image or responsive variant as high priority.
For a critical CSS background, a preload may help when the image URL is known and the browser would otherwise discover it late. Avoid preloading every responsive variant or format. Over-preloading can trigger downloads the page does not need and harm performance rather than improve it.
Free tools Windows power users keep installed
One-click scans. No signup required.
Reserve the image’s space before it loads. Explicit image dimensions let the browser infer its ratio and allocate layout space early; a CSS aspect-ratio can also express the intended shape. Without reserved space, the image may push text and controls down after loading, creating layout shift. Keep CSS dimensions consistent with the image and intended layout so the ratio does not distort.
Make the crop and text accessible
Keep the headline, supporting text, and CTA as HTML. That makes them selectable, zoomable, localizable, and readable when the image crop changes. WCAG 2.2 Success Criterion 1.4.9 limits images of text to decoration or cases where a particular presentation is essential. Do not put words, logos that carry meaning, or instructions into the hero bitmap as a substitute for page content.
Rank #3
- Clear visuals. Fluid motion: A 144Hz refresh rate and 1ms MPRT deliver smooth, tear‑free motion across work, gaming, and streaming for clearer, more fluid viewing.
- Eye comfort: TÜV Rheinland 3‑star* certification reduces harmful blue light while preserving stunning color quality without compromise. *TÜV Rheinland 3-star eye comfort certification.
- Wide viewing angle: Get consistent views across a wide 178° /178° viewing angle.
- In-Plane Switching (IPS): See excellent color accuracy and consistency across wide viewing angles with In-plane Switching (IPS) technology.
- Ultra-thin bezels: Maximize your viewing experience with thin bezels.
For an informative <img>, write concise alt text describing the subject and its relevance. Do not repeat the visible headline in the alt text. For a purely decorative image, use alt="" if it is an HTML image, or use CSS background imagery. A CSS background has no alt text; make sure it is not the only way the page communicates a meaningful fact.
Text over an image must remain legible across the image’s responsive crops. Test contrast where the text actually falls, not just over the desktop mockup. A gradient or solid backing can help, but verify it does not obscure the subject or CTA. Keep the focal subject out of the copy area, and use a different mobile art direction when repositioning alone cannot preserve both subject and text.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Test the hero at real viewport sizes and zoom
A desktop preview is not enough. W3C Technique C37 describes checking image fit at 400% zoom, and WCAG 2.2 Reflow (1.4.10) targets content that can be presented at a 320 CSS-pixel equivalent width without two-dimensional scrolling, subject to documented exceptions. Check that the hero neither forces horizontal scrolling nor conceals controls as the viewport narrows.
- Wide desktop: confirm the main subject, headline, and CTA have clear space and the crop does not feel accidental.
- Narrow phone: inspect the actual crop and verify the subject remains visible. Switch to a mobile-specific source if it does not.
- High-density phone: check that the chosen source remains crisp without shipping the largest file unnecessarily.
- Zoom and reflow: test at 400% zoom and around a 320 CSS-pixel equivalent width; verify no horizontal overflow and that text and controls remain usable.
- Keyboard and assistive technology: move focus through hero controls and confirm focus indicators are visible against the image; check that informative imagery has suitable alt text and decorative imagery is ignored.
- Slow connection: observe whether the hero reserves space, arrives promptly, and avoids a jump in surrounding content.
Inspect the selected image file as well as the visual result. The browser may pick an unexpectedly large candidate if the sizes description is wrong. Google Chrome’s modern web guidance notes that images commonly make up the largest page payload and calls for format negotiation, responsive sizing, and layout stabilization.
Troubleshooting common hero-image problems
The subject disappears on mobile
Cause: a wide source is being cropped to fill a tall or narrow box, often with its focal point centered in the wrong place.
Fix: adjust object-position or background-position first. If that cannot retain the subject without colliding with copy, use art direction with a dedicated mobile crop through <picture>.
Rank #4
- CURVED FOR ENHANCED ENGAGEMENT: An immersive viewing experience with a curved monitor that wraps more closely around your field of vision; It creates a wider view, enhancing depth perception and minimizing peripheral distraction
- SMOOTH PERFORMANCE FOR SEAMLESS CONTENT: Stay in the action when playing games, watching videos, or working on creative projects; The 100Hz refresh rate reduces lag and motion blur so you don't miss a thing in fast-paced moments¹
- MORE GAMING POWER: Gain the edge with optimizable game settings; Color and image contrast can be adjusted to see scenes more vividly and spot enemies hiding in the dark; Game Mode adjusts any game to fill the screen so you can view every detail²
- KEEP IT EASY ON THE EYES: Care for your eyes and stay comfortable, even during long sessions; Advanced eye comfort technology certified by TÜV reduces eye strain by minimizing blue light and reducing irritating screen flicker²
- INCREASED VERSATILITY: Connect to more; Plug devices straight into your monitor for increased flexibility, making your computing environment even more convenient
The image looks stretched or distorted
Cause: both dimensions are being forced without preserving the image ratio, or the intended ratio does not match the asset.
Fix: use block-size: auto for an image that should retain its natural shape, or set a deliberate container aspect-ratio and use object-fit: cover when cropping is acceptable.
The page jumps when the image loads
Cause: the browser did not know the image’s dimensions or reserved component ratio in advance.
Fix: add the correct intrinsic width and height attributes to the fallback <img>, or reserve the slot with CSS aspect-ratio.
The hero image is downloaded too late
Cause: the above-the-fold image is lazy-loaded, or a critical image is hidden in CSS and discovered late.
Fix: remove lazy loading from the visible hero. Consider a selective high fetch priority for the true LCP image; for a critical CSS background, consider a preload only when its URL is known.
Mobile visitors receive an oversized file
Cause: only one large asset is offered, or sizes inaccurately describes the rendered width.
Fix: generate several image widths, connect them with width-descriptor srcset, and set sizes to the real responsive layout. Use modern formats with fallbacks if supported by your delivery stack.
Text becomes hard to read over the image
Cause: the crop changes the background behind the copy, or the image has competing detail and contrast.
Fix: move the focal point away from the text, provide a contrast-preserving overlay or backing, and retest on the narrow crop. Keep all actual copy in HTML.
Best Value
- 【INTEGRATED SPEAKERS】Whether you're at work or in the midst of an intense gaming session, our built-in speakers provide rich and seamless audio, all while keeping your desk clutter-free.
- 【EASY ON THE EYES】 Protect your eyes and enhance your comfort with Blue-Light Shift technology. This feature reduces harmful blue light emissions from your screen, helping to alleviate eye strain during long hours of use and promoting healthier viewing habits.
- 【WIDEN YOUR PERSPECTIVE】Our sleek minimal bezel design ensures undivided attention. The nearly bezel-free display seamlessly connects in a dual monitor arrangement, delivering an unobstructed view that lets you focus on more at once, completely distraction-free.
Or skip the browser setup
If you need a screenshot to inspect how a hero renders on a page, ScreenshotNeo provides a screenshot API and MCP server for developers. A one-call capture can help check the page without building a browser-capture flow:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo documentation for request options and use your own target URL. The service accepts cookie/consent banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers identify the page verdict and billing status. AI agents can use its MCP server tools, including take_screenshot, get_page_info, and capture_pdf. The Free plan includes 1,000 shots per month without a card; paid plans start at $5 for 3,000 shots. Sign up for ScreenshotNeo’s free plan.
Set a repeatable hero-image workflow
- Choose the image and focal point. Start with a wide, crop-safe composition, and decide whether the mobile crop needs its own source.
- Keep meaning in the page. Put the headline and CTA in HTML; decide whether the image is informative or decorative and provide alt treatment accordingly.
- Generate responsive files. Provide suitable widths and modern formats with a fallback, then wire them into
srcset,sizes, and, when needed,picture. - Reserve layout space. Include intrinsic dimensions and use a consistent aspect ratio so content does not jump.
- Prioritize the visible hero. Do not lazy-load it; use high fetch priority or preload only when the image is genuinely critical.
- Validate the actual page. Test narrow and wide viewports, zoom, keyboard focus, contrast, slow loading, crop behavior, and the image candidate selected by the browser.
Frequently Asked Questions
Should every hero image have alt text?
No. Informative HTML images need concise alt text; purely decorative images should use empty alt text or be implemented as CSS backgrounds.
Is 1920×1080 mandatory for a hero image?
No. It is the NSF’s preferred full-size recommendation, not a universal requirement. Match source widths and crops to the component and visitors’ viewports.
Can I use lazy loading for a hero below the fold?
Yes. The restriction applies to a hero image above the fold; below-the-fold images are appropriate candidates for lazy loading.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
