What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
In an Applitools Eyes Playwright test, set fully: true in eyes.check() to capture a full-page checkpoint. Then compare it with the approved baseline, choosing capture mode and comparison settings to match how the page behaves and what visual changes matter.
Set up a full-page checkpoint in Playwright
Applitools’ Playwright integration uses a test fixture from @applitools/eyes-playwright/fixture. The key full-page option is fully: true; the example below also sets a strict match level.
As an Amazon Associate I earn from qualifying purchases.
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',
});
});
This creates a checkpoint named “Homepage” for comparison with its baseline. The integration guide documents this full-page pattern: Applitools Playwright integration guide.
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 minuteChoose a capture mode for the page
Capture mode determines how Eyes assembles a full-page screenshot. Applitools’ Eyes Visual AI settings documentation describes CSS and scroll modes.
#1 Best Overall
| Mode | How it captures | When to try it |
|---|---|---|
| CSS (default) | Uses CSS-based full-page capture. | Recommended by Applitools for pages with fixed-position elements, such as headers or floating bars, to avoid those elements appearing repeatedly in the assembled image. |
| Scroll | Scrolls using standard JavaScript window scrolling. | Try it if the full-page result from the other mode is problematic; inspect the output to see whether it better matches the page. |
Do not assume one mode is best for every page. If a fixed element is duplicated or the assembled image otherwise looks wrong, switch to the alternative capture mode and check the resulting screenshot.
Distinguish capture problems from comparison settings
A checkpoint can be complete but still report differences you do not want to treat as failures. The match level controls how Eyes compares the checkpoint image with the baseline. The Playwright guide also documents ignored regions for dynamic content, plus floating regions and displacement handling as advanced options. Select these based on the test’s purpose rather than adding them automatically: Applitools Playwright integration guide.
Rank #2
- Use a match level that fits the test. The example uses
Strict; decide whether that sensitivity is appropriate for the page and the changes your test is intended to catch. - Ignore only genuinely variable areas. An ignored region can keep dynamic content from dominating a comparison, but it also excludes that area from the visual check.
- Consider floating regions or displacement handling only when needed. These are advanced options, not prerequisites for full-page capture.
If the screenshot itself is missing content or has faulty stitching, fix capture coverage before changing comparison sensitivity. A more permissive match level cannot restore content that was never captured.
Windows 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 reinstallOutdated 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 matchTroubleshoot missing or repeated content
Only the visible viewport appears
Check whether the page scrolls inside a nested element instead of the main document. Eyes normally attempts to scroll the body or document, but some applications use a different scrollable element. Use browser developer tools to inspect the suspected container and verify that scrolling it reveals the missing content. Then configure the appropriate scroll root for a full-window capture or check the scrollable region fully, as applicable. Do not assume body is the right scroll root for every page. See Applitools’ guidance on determining the scrollable element for a full-page screenshot.
Fixed headers or floating bars repeat
Try CSS capture mode, which Applitools recommends for fixed-position elements. If the output is still problematic, test the alternative mode and inspect the complete image rather than judging only the initial viewport. See the capture settings documentation.
Content loaded by scrolling is absent
Some pages add content only after a section enters the viewport. Applitools’ support guidance recommends scrolling to the bottom and back up before taking the full-page screenshot, giving scroll-triggered loading a chance to run. This is a troubleshooting approach, not a guarantee: application-specific loading behavior may require additional handling. See Applitools’ lazy-loading guidance.
Rank #4
The screenshot looks complete, but the comparison is noisy
First confirm that the changing area is genuinely dynamic and not a visual regression the test should catch. If it is safe to exclude, configure an ignored region; otherwise, adjust the match level only if the desired comparison policy calls for it. These settings affect how differences are judged, not how much of the page is captured.
Or skip the browser setup
For a standalone screenshot rather than a baseline comparison, ScreenshotNeo provides a website screenshot API. One GET request can return an image or PDF; its API does not replace Eyes’ baseline comparison.
Install the Python dependency with python -m pip install requests, then run:
import requests
r = requests.get(
"https://api.screenshotneo.com/v1/shot",
params={"access_key": "YOUR_API_KEY", "url": "https://example.com"},
timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)
See the ScreenshotNeo API documentation for request options and response details. Cookie banners are accepted and removed before capture, along with supported consent platforms, newsletter popups, and chat widgets; each of these steps 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. An MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents. The Free plan includes 1,000 shots a month with no card; paid plans start at $5 for 3,000 shots.
Sign up for ScreenshotNeo’s free plan to get 1,000 screenshots a month with no card.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Frequently Asked Questions
Does fully: true compare a screenshot with a baseline by itself?
It requests a full-page checkpoint in eyes.check(); the checkpoint is then evaluated within the Eyes visual testing workflow against its baseline.
Can ScreenshotNeo replace Applitools Eyes for baseline comparison?
No. ScreenshotNeo’s API returns screenshots or PDFs; the code here does not provide Eyes’ baseline comparison.
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.




