What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Good website images start with the job they need to do: explain something, decorate a page, act as a control, or convey complex information. From there, choose a crop and format that suit the actual display slot, provide meaningful text alternatives, and deliver responsive dimensions without slowing the page. There is no universally best image format or export setting; the right choice depends on the image, browser support, and the visual quality the page needs.
Start by deciding what the image is for
Before opening an image editor, identify the image’s role in the page. It may communicate information, add atmosphere without carrying meaning, function as a link or button, contain text, or present a complex graphic such as a chart. That role determines how to crop and export it, and what alternative text the page needs.
- Informational: The image contributes meaning that is not fully available in nearby text. Preserve the relevant subject and provide a concise text alternative.
- Decorative: The image adds visual polish but does not add information. In HTML, use
alt=""so assistive technology can skip it. - Functional: The image is the visible content of a link or control. Describe the action or destination, rather than listing visual details that do not explain its function.
- Text or complex data: If an image contains essential wording or a detailed chart, make its content available as text too. A short alt attribute alone may not communicate a complex graphic completely.
W3C’s Web Content Accessibility Guidelines 2.2, Success Criterion 1.1.1 (2023), requires text alternatives for non-text content except for specified exceptions. Its accessibility guidance also emphasizes that the right alternative depends on the image’s purpose. Decide this before exporting: a crop that removes the meaningful subject cannot be repaired by writing better alt text.
Design and crop for the space where the image will appear
Make the image for its actual component, not for an abstract idea of “website size.” A wide hero, a square card, and a narrow mobile banner have different aspect ratios and focal points. Start with the likely rendered dimensions and the content that must remain visible. Keep faces, product details, labels, and other important subjects inside a safe area so a tighter crop does not cut them off.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →For a layout that uses several widths, export a small set of useful intrinsic sizes rather than one oversized image for every screen. Include explicit width and height attributes, or otherwise establish the image’s aspect ratio, so the browser can reserve space before the file loads. This helps avoid layout movement while the page is rendering. Google Search Central recommends responsive image markup such as srcset or picture, with a fallback src, and dimensions or an aspect ratio.
#1 Best Overall
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
When mobile needs a genuinely different composition, use art direction: offer a mobile crop and a desktop crop rather than shrinking a desktop composition until its subject becomes tiny. Check each crop at the size it will actually render, especially where the image contains a product, text, or a focal subject near the edge.
Choose an image format by content, not by a universal rule
WebP and AVIF are useful options for many photographic and raster images because they generally compress more efficiently than older formats. The result depends on the source, encoder, settings, and acceptable visual loss; one format is not always the right choice. Compare the output at the size it will be displayed and inspect details, not just the file extension or file size.
| Image type or need | Practical starting point | What to check |
|---|---|---|
| Photographs and many raster images | Try WebP or AVIF. | Inspect fine texture, edges, gradients, and color for compression artifacts at the rendered size. |
| Screenshots, diagrams, logos, or line art | Use a lossless export when artifacts would harm clarity. | Check small text, thin lines, transparency, and crisp edges. |
| Compatibility fallback | Keep an appropriate JPEG or PNG fallback when needed. | Verify that the fallback has the right crop, dimensions, and appearance; it should not be a mismatched or missing asset. |
MDN advises preferring WebP or AVIF for raster images in general, while Google also documents WebP. Treat that as a starting point rather than a guarantee about every image or audience. Avoid choosing quality settings from a generic percentage claim: compression and visible quality vary by image and encoder.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallUse semantic, responsive HTML
Use an <img> element for content images. It makes the image available to assistive technology and crawlers, and provides a place for alternative text and intrinsic dimensions. Use <picture> when selecting a format or art-directed crop, while keeping an <img> with a usable fallback source.
This example offers AVIF and WebP, then a JPEG fallback. The sizes value says the image may occupy the viewport width; adjust it to match the actual layout rather than copying it blindly.
<picture>
<source type="image/avif"
srcset="hero-480.avif 480w, hero-960.avif 960w"
sizes="100vw">
<source type="image/webp"
srcset="hero-480.webp 480w, hero-960.webp 960w"
sizes="100vw">
<img src="hero-960.jpg"
srcset="hero-480.jpg 480w, hero-960.jpg 960w"
sizes="100vw" width="960" height="540"
alt="Descriptive, purpose-focused alternative text">
</picture>Replace the sample filenames with real files you have exported. Make each candidate in a srcset a version of the same intended image and crop; use <picture> sources for format choices or distinct art direction. If a hero image has a different mobile crop, use a media condition on an appropriate <source> and keep the <img> fallback. Do not use CSS background images for content that needs to be discoverable as an image; reserve backgrounds for decoration.
Rank #3
Write alt text that communicates purpose
Alt text should be concise, specific to the page context, and useful to someone who cannot see the image. The same photograph may need different alternatives in different contexts: a product page may need the item and relevant feature, while an article about composition may need to describe the framing. Google Search Central calls alt text the most important image metadata; W3C advises putting the most important information first.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors- For a meaningful image, describe the information or purpose a reader needs from it.
- For a linked image, describe where the link goes or what it does.
- For a purely decorative image, use an empty value,
alt="", rather than a caption-like description. - For a detailed chart, provide the data or explanation in surrounding text; do not expect a short alt value to carry every detail.
Do not stuff keywords into the alternative. If a phrase is useful to a person understanding the image, include it naturally; if it is present only to influence search ranking, leave it out. Text embedded in an image also deserves a separate check: confirm it remains readable at the rendered size and that essential wording is available as text outside the bitmap where appropriate.
Load images without undermining speed or layout stability
Do not lazy-load the above-the-fold image that is likely to become the page’s Largest Contentful Paint (LCP) element. Lazy-load images that are below the fold so they can wait until they are needed. Serve dimensions close to the displayed size, provide dimensions or an aspect ratio, and use stable image URLs so browsers and crawlers can reuse cached assets.
Rank #4
- Brand: Wiley
- Set of 2 Volumes
- A handy two-book set that uniquely combines related technologies Highly visual format and accessible language makes these books highly effective learning tools Perfect for beginning web designers and front-end developers
Google’s “good” Core Web Vitals targets are LCP at or below 2.5 seconds, Interaction to Next Paint (INP) below 200 milliseconds, and Cumulative Layout Shift (CLS) below 0.1. These are page-level targets, not promises that changing image format alone will meet them. Images are one part of the page’s performance; measure on a slow connection and on real mobile layouts rather than assuming a desktop preview tells the whole story.
Check accessibility, fidelity, and repeatability before publishing
A repeatable export and QA process catches problems that a quick visual glance misses. For each image, verify that the intended source, crop, fallback, dimensions, and alt text are all connected correctly in the page.
- Preview each crop at its rendered size. Check the desktop and mobile layouts, focal point, sharpness, and any text or fine detail.
- Inspect compressed versions. Compare WebP or AVIF with the lossless or fallback candidate. Look for artifacts that matter for this content.
- Test the page without seeing images. Check whether the text alternatives preserve information and whether the page still makes sense.
- Check with assistive technology or an accessibility audit. Confirm decorative images are skipped and meaningful or functional images have relevant alternatives.
- Review loading and layout behavior. Confirm the likely LCP image is not lazy-loaded, below-the-fold images can be deferred, and reserved image space prevents avoidable shifts.
- Recheck after edits. If a crop or image purpose changes, revisit the alt text, responsive candidates, and any explanatory text nearby.
Common image problems and fixes
- The page downloads a large image for a small slot: Add responsive candidates with accurate widths and a
sizesvalue that reflects the layout; export versions closer to likely display sizes. - The subject is cut off on mobile: Create an art-directed mobile crop and verify the subject stays in a safe area at the actual narrow layout.
- A logo, chart, or screenshot looks damaged: Compare a lossless export or less aggressive compression. The smallest file is not useful if it obscures information.
- The page shifts when an image loads: Supply width and height or reserve the correct aspect ratio so the browser knows how much space to allocate.
- A decorative image is announced unnecessarily: Use
alt=""for an image that adds no information or function. - A meaningful image has no useful alternative: Replace a filename or generic label with a context-aware description; for complex data, add the full explanation in text.
- A new format fails to display: Check the source type and file path, then retain a suitable
<img>fallback and test that fallback directly. - Text in the image is unreadable: Use a sharper or larger export, reconsider the crop, and provide essential wording as actual page text as well.
Or skip the browser setup
If a website image is a capture of an existing live page—for example, a reference image for documentation or a preview—you can request a screenshot directly instead of setting up a browser capture flow. This makes a screenshot of a page; it does not design or compose a new illustration. ScreenshotNeo is a website screenshot API and MCP server from Yorker Media. Its API accepts one GET request and can return PNG, JPEG, WebP, or PDF. See the ScreenshotNeo API documentation.
For a direct command-line capture, save a WebP response as shot.webp:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpPython version:
import requests
r = requests.get(
"https://api.screenshotneo.com/v1/shot",
params={"access_key": "YOUR_API_KEY", "url": "https://example.com"},
timeout=90,
)
open("shot.webp", "wb").write(r.content)Node.js version using the built-in fetch API:
const q = new URLSearchParams({
access_key: 'YOUR_API_KEY',
url: 'https://example.com'
});
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
Replace YOUR_API_KEY with your API key and https://example.com with the page to capture. The Node.js example shows the request; to save its response as a file, consume the response body using the file-writing approach appropriate for your Node.js runtime. ScreenshotNeo accepts cookie banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each cleanup step can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers report the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 shots. Use the ScreenshotNeo website for product details, then sign up for 1,000 free screenshots a month with no card.
FAQ
Can a screenshot replace accessible page content?
No. A screenshot is a bitmap of the page, not a substitute for the page’s selectable text, controls, or accessible structure. If you publish a capture as an image, give it an appropriate alternative and keep the underlying information available in text when readers need it.
Should I put the same image in an HTML image element and a CSS background?
Usually not for the same content. Use a semantic image element for content that should be discoverable or have an alternative text; use CSS backgrounds for decorative treatment.
Frequently Asked Questions
Can a screenshot replace accessible page content?
No. A screenshot is a bitmap of the page, not a substitute for selectable text, controls, or accessible structure. Give a published capture an appropriate alternative and keep necessary information available as text.
Should I put the same image in an HTML image element and a CSS background?
Usually not for the same content. Use a semantic image element for content that should be discoverable or have an alternative text; use CSS backgrounds for decoration.
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.
