Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →In an Applitools Eyes Playwright test, pass fully: true to eyes.check() to compare the full page with its baseline. Then choose a capture mode that fits the page’s scrolling behavior, and configure comparison options such as match level or ignored regions for the visual test you intend to run.
Set up a full-page checkpoint in Playwright
Applitools’ Playwright integration guide uses the test fixture from @applitools/eyes-playwright/fixture. Its full-page example navigates to a page and calls eyes.check() with fully: true and a strict match level:
import { test } from '@applitools/eyes-playwright/fixture';
test('Visual test using eyes.check()', async ({ page, eyes }) => {
await page.goto('https://example.com');
await eyes.check('Homepage', {
fully: true,
matchLevel: 'Strict',
});
});Replace the example URL and checkpoint name with the page and stable label used in your test. The fully setting requests full-page capture; the matchLevel setting controls how Eyes compares the checkpoint image with its baseline. Applitools’ Playwright integration guide also documents ignored and floating regions and displacement handling. Use those options when the page or test purpose calls for them, rather than adding them by default.
Choose a full-page capture mode
Applitools’ settings documentation calls the setting that determines how a full-page capture is defined the “Screenshot Capture Mode.” CSS mode is the default and is recommended for pages with fixed-position elements, such as a fixed header or floating bar, so they do not appear repeatedly in the assembled image. Scroll mode uses standard JavaScript window scrolling. If the full-page result is wrong, try the alternative capture mode and inspect the new image.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →#1 Best Overall
Changing capture mode addresses how the full-page image is assembled; it does not decide how sensitive the baseline comparison should be. See Applitools’ Eyes Visual AI settings documentation for the capture-mode details.
Diagnose missing or incomplete page content
Only the visible viewport appears
A page may scroll inside a nested container instead of the main document. Eyes normally attempts to scroll the body or document, so a different scroll root may be needed. Use browser developer tools to inspect the element suspected of scrolling and test its scroll behavior. Then configure the appropriate scroll root for a full-window capture, or check the scrollable region fully. Do not assume that body is the scroll root on every site. Applitools explains this issue in its guide to determining the scrollable element for a full-page screenshot.
Rank #2
Lazy-loaded sections are absent
Some pages add content only after scrolling reaches it. That can change the page height during capture or leave lower sections unloaded. Applitools’ documented troubleshooting approach is to scroll to the bottom and back up before taking the full-page screenshot, giving scroll-triggered loading a chance to occur. This is an approach to try, not a guarantee for every application’s loading logic. See Applitools’ guidance on screenshots missing content due to lazy loading.
The page is complete, but the comparison flags differences
Separate capture coverage from comparison policy. First inspect the checkpoint image to verify that the expected page content was captured. If it was, consider whether the selected match level suits the test and whether genuinely variable areas should be ignored. An ignored region prevents that area from driving the comparison; it should not be used to conceal a change the test is meant to catch. Applitools’ integration guide documents matchLevel and ignoreRegions as checkpoint options.
Compare capture approaches by the failure you see
| Page or symptom | What to check | Next step |
|---|---|---|
| Fixed header or floating bar repeats in the stitched image | Capture mode | Try CSS mode, which Applitools recommends for fixed-position items. |
| Only part of a long page is captured | Whether the main document or a nested element scrolls | Identify the actual scrollable element and configure the relevant scroll root or region. |
| Lower sections appear only after scrolling | Scroll-triggered or lazy loading | Try scrolling to the bottom and back up before capture. |
| Image contains the expected content but reports visual differences | Comparison sensitivity and dynamic content | Review match level and whether specific dynamic regions should be ignored. |
Or skip the browser setup
If you need a screenshot rather than an Applitools baseline comparison, ScreenshotNeo offers a one-request screenshot API. Its clean-shot processing accepts cookie or consent banners like a visitor 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 are not billed, and response headers report the page verdict and billing status. Its MCP server includes screenshot tools for AI agents.
For a one-call capture, use the cURL example below. Replace the target URL and API key with your own. See the ScreenshotNeo API documentation for supported options and response details.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpThe free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots. Sign up for ScreenshotNeo’s free plan to try it.
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.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minute
