Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
In Puppeteer, use elementHandle.isVisible() to check a handle’s current state, page.waitForSelector(selector, { visible: true }) to wait for a matching element to appear, or a locator action such as page.locator(selector).click() when you intend to interact with it. These APIs have different visibility and readiness criteria, so choose based on whether you need a boolean, a wait, or an action.
Choose the API for the question you need to answer
| Need | Puppeteer API | What it does | Important distinction |
|---|---|---|---|
| Check a handle now | elementHandle.isVisible() |
Returns a boolean for the handle’s current state, using the method’s documented visibility criteria. | It does not wait for a future change. |
| Wait for a selector to appear visibly | page.waitForSelector(selector, { visible: true }) |
Waits for a matching element to be present and pass the wait option’s visibility check. | It can time out, and its documented CSS checks are worded differently from isVisible(). |
| Interact when ready | page.locator(selector).click() or another locator action |
Waits for the locator’s relevant action preconditions, then performs the action. | Prefer this when the real goal is clicking, typing, or filling rather than reporting visibility. |
“Visible” here means visible according to the selected Puppeteer API’s criteria. It does not by itself prove that an element is unobstructed, legible, or guaranteed to receive a user click.
Check the current visibility of an existing handle
If code has already obtained an ElementHandle, call isVisible() and await its boolean result:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
const visible = await elementHandle.isVisible();
console.log(visible); // true or falsePuppeteer documents this method as checking computed styles, a non-empty bounding client rect, and that the element’s visibility value is neither hidden nor collapse. See the ElementHandle.isVisible() API reference.
#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
This is an immediate state query. If a script reveals the element later, calling isVisible() before that change will not wait for it. Use a wait API when the state is expected to change asynchronously.
Wait for a matching selector to become visible
Use page.waitForSelector() when the element may not yet exist or may initially be hidden:
const element = await page.waitForSelector('.target', { visible: true });
if (!element) {
throw new Error('The selector did not resolve to an element');
}
// Use the element here, then dispose of the handle when finished.
await element.dispose();The visible: true option waits for a matching element to be present and checks that its computed display is not none and its visibility is not hidden. It is not the same phrasing or precisely the same documented test as ElementHandle.isVisible(). Consult the waitForSelector API reference for options and timeout behavior.
If no qualifying match appears before the timeout, the wait rejects with a timeout error. The cited API reference lists 30 seconds as the default timeout; it can be configured through page timeout settings or on the call, depending on the Puppeteer version in use. Check the reference for the version installed in your project.
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
waitForSelector() is a lower-level API that can return an element handle. Dispose of handles you no longer need, especially in repeated capture or automation loops, to avoid retaining remote objects longer than necessary.
Use a locator when the next step is an interaction
If you intend to click a button or fill a field, express that action directly with a locator:
await page.locator('.target').click();Puppeteer recommends locators for selecting and interacting with page elements. Locator actions automatically wait for relevant readiness conditions. The interactions guide documents checks that include viewport presence and visibility, and a stable bounding box across two animation frames; actions such as clicking and filling also have action-specific conditions, such as being enabled where relevant. See the Puppeteer page interactions guide.
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 glitchesThis is usually more reliable than checking visibility, then separately clicking: between two separate operations, the page can change. Let the locator handle the action’s readiness checks when the goal is an action, not a standalone visibility result.
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.
Wait for locator visibility without acting
When the code needs to wait for a locator’s state but should not click or type, the interactions guide shows waiting on a locator:
await page.locator('.loading').wait();Locator visibility can be configured. The API defines visibility options as 'hidden', 'visible', or null. Check the VisibilityOption API reference for the installed version and the locator method’s options.
Plain browser JavaScript: inspect the state you actually mean
In page-side JavaScript, there is no single universal “visible” test that answers every practical question. You can inspect relevant browser state directly, but treat the result as a check for those particular conditions—not a guarantee of unobstructed interaction. For Puppeteer automation, the documented APIs above provide defined checks and waits.
For example, this browser-side helper checks whether an element exists, is not hidden by the common CSS display or visibility properties, and has a non-empty client rect:
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
function isVisible(element) {
if (!element) return false;
const style = getComputedStyle(element);
const hasBox = element.getBoundingClientRect().width > 0 &&
element.getBoundingClientRect().height > 0;
return style.display !== 'none' &&
style.visibility !== 'hidden' &&
style.visibility !== 'collapse' &&
hasBox;
}
const visible = isVisible(document.querySelector('.target'));
console.log(visible);This helper is a custom approximation for a browser page, not a replacement for a Puppeteer method’s documented semantics. It does not establish that the element is in the viewport, not covered by another element, or clickable. A page can also change immediately after the check. If you need to wait for a state change in browser-side code, use an appropriate observer or polling strategy with a bounded timeout; if using Puppeteer, prefer its wait or locator APIs.
Common failure modes and fixes
- The wait times out: Confirm the selector matches the page’s actual DOM, that navigation has reached the expected state, and that the element is not permanently hidden. Increase the timeout only when the page legitimately needs longer; do not mask a selector or page-state bug with an unlimited wait.
isVisible()returns false but the element appears on screen: Verify that the handle refers to the intended element and inspect its computed styles and client rect. Remember that the method tests its documented conditions, not every colloquial meaning of visible.- The selector matches more than one element: Make the selector more specific or use the locator selection methods appropriate to the page. A wait concerns a matching element; broad selectors can make the intended target unclear.
- The element becomes visible after the check: A boolean query is only a snapshot. Replace it with
waitForSelector(..., { visible: true })or an appropriate locator wait. - The element passes a visibility check but click fails: Use a locator click so Puppeteer waits for action readiness. Visibility alone does not promise that another element is not covering the target or that the target will remain ready through the action.
- Memory use grows during a long-running script: Dispose of element handles returned by lower-level APIs when no longer needed, and avoid accumulating handles in loops.
- Behavior differs from an online example: Puppeteer API details can change between versions. Check the official API page for the version used by your project; the reviewed documentation pages span versions 25.8.0 to 25.12.0.
Performance, reliability, and timeout choices
A direct isVisible() query is suitable when code already has a handle and needs its present status. A wait adds time intentionally because it waits for the page to reach a condition. A locator action is a better fit for robust interaction because it couples readiness checks with the operation.
Keep waits bounded. Use a timeout appropriate to the page and task, and handle timeout rejection explicitly when the expected result is optional. Avoid repeated tight polling when a Puppeteer wait can express the required state. For dynamic pages, run the wait after the navigation or event that is expected to produce the element, and use a selector that identifies the intended element rather than a broad page-wide match.
Free tools Windows power users keep installed
One-click scans. No signup required.
Or skip the browser setup
If the goal is a screenshot rather than testing or interacting with the element, a screenshot API can avoid setting up and maintaining browser automation. ScreenshotNeo is a website screenshot API and MCP server for developers. Its clean-shot workflow accepts cookie or consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each of those steps can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers report the page verdict and billing status.
For an image capture, make one GET request. See the ScreenshotNeo API documentation for parameters and output options:
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.
curl -G "https://api.screenshotneo.com/v1/shot"
-d access_key=YOUR_API_KEY
--data-urlencode url=https://stripe.com
-o shot.webpThe API can return PNG, JPEG, WebP, or PDF. It also supports full-page capture with lazy images loaded, CSS-selector element capture, device and viewport settings, custom CSS or JavaScript, waits, and other capture controls. Its MCP server offers take_screenshot, get_page_info, and capture_pdf for AI agents using Claude, Cursor, or another MCP client. 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: 1,000 screenshots a month, no card required.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Frequently Asked Questions
Does Puppeteer’s visible check guarantee that a user can click the element?
No. It reports visibility or readiness according to the chosen API’s criteria; it does not establish that the target is unobstructed or guaranteed to receive a click.
Can I use `waitForSelector` just to check visibility?
Yes. It waits for a visible matching element and returns a handle when it resolves. Dispose of the handle when you no longer need it.
What should I use if I only need to take a screenshot?
A screenshot API can capture a page without writing a Puppeteer visibility check. ScreenshotNeo provides a GET screenshot endpoint and an MCP server; its capture options and billing behavior are described above.
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.
Recommended Free Tools
