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 minuteWindows 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 reinstallIf Percy cannot find or load a page, first verify that the snapshot URL is correct, uses http or https, and can be reached from Percy’s rendering environment—not just from your laptop. If the page requires authentication, configure access for the capture. Then identify whether the failure is page loading, asset retrieval, or snapshot upload; each points to a different fix.
Identify which part of the Percy job failed
“Cannot find a page” can describe several different failures. Check the failed build’s classification and Network logs before changing settings: the classification helps locate the failing stage, while the logs show which requests failed.
As an Amazon Associate I earn from qualifying purchases.
| Symptom | Likely layer | First checks |
|---|---|---|
| Percy cannot load the snapshot page | Page loading or reachability | Validate the URL, check that Percy can reach it, and configure required authentication. |
| The snapshot URL is rejected or the snapshot will not upload | URL format or upload path | Use an http or https URL; check network stability and retry. |
| The page renders, but the visual snapshot is incomplete | Asset discovery | Check asset URLs, allowed hostnames, authentication, reachability, and timeout settings. |
| Requests fail but the source is unclear | Diagnostics | Review the build classification and Percy Network logs. |
Percy’s failure-type guide distinguishes page-load problems from asset failures; its snapshot upload troubleshooting covers upload-specific failures.
Check the snapshot URL and how Percy receives it
Validate the complete URL
Make sure the URL has the correct scheme, host, port, and path, and that a browser can navigate to it. Percy’s upload guidance says snapshot URLs should start with http or https; it gives about:blank as an invalid example. A typo or a URL that resolves only in your local environment can prevent Percy from capturing the intended page.
#1 Best Overall
Check the snapshot target source
Percy CLI can receive targets from a snapshot file, a static directory, or a sitemap URL. If you use a snapshot file, each entry needs a URL a browser can navigate to. For local or static paths, verify the configured base URL and how the path resolves. See the Percy CLI guide for the supported target sources.
Verify Percy can reach and access the page
A page that loads in your own browser may still be unavailable to Percy’s renderers—for example, if it is local or otherwise inaccessible from Percy’s environment. For a Page Load Timeout classification, BrowserStack recommends confirming that Percy can reach the URL and that any required authentication is configured.
Rank #2
- Check that the page is reachable from the environment Percy uses, not only from your workstation.
- If the page is protected, provide the authentication Percy needs to load it.
- Confirm that redirects lead to a reachable destination and do not require an interactive sign-in that Percy cannot complete.
For a Page Load Timeout, use the specific checks in BrowserStack’s build failure types guide before changing unrelated capture settings.
When the page loads but the screenshot is incomplete
A successful page load does not guarantee that every image, stylesheet, script, font, or other resource loaded. If the page appears but parts are missing, investigate those asset requests separately from the page URL.
- Verify each failing asset URL and confirm its host is reachable.
- Check whether the asset host is included in the allowed hostnames configuration.
- Configure authentication if an asset endpoint is protected.
- Review network logs for failed requests and consider whether the network-idle timeout is appropriate for the page.
Percy documents allowed hostnames and a network-idle timeout among the relevant configuration checks. Its failure guide recommends checking asset reachability, URL correctness, authentication, and logs.
When capture worked but the snapshot did not upload
An upload failure is not proof that Percy could not find the page. If capture completed but upload failed, check network stability and retry. If the problem persists, investigate the runner’s network path to Percy rather than changing the page URL without evidence.
Use the upload-specific steps in Percy’s snapshot upload troubleshooting. Compare the failure classification with the upload error to establish whether the issue occurred before or after capture.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Use Percy Network logs to locate the failing request
Percy Network logs show request statuses and include the URL, timestamp, and device-configuration context. Find the failed request and determine whether it is the page itself, an asset, or part of the upload path. That distinction narrows the fix and avoids treating every failure as a missing page.
- Open the failed Percy build and note its failure classification.
- Open the build’s Network logs.
- Find the failed request and inspect its URL and status.
- Use the request context to decide whether to fix the page URL, access, an asset host, or the runner’s network path.
See BrowserStack’s guide to viewing Network logs for the log details.
Or skip the browser setup
If you need a screenshot of a public page outside a Percy visual-test workflow, ScreenshotNeo can return an image or PDF from one GET request. It is not a Percy configuration fix, but it can be a simpler way to capture a URL without setting up a browser runner.
cURL example (see the ScreenshotNeo documentation):
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo removes cookie/consent banners, newsletter popups, and chat widgets before capture. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed. Its MCP server lets AI agents take screenshots, and the Free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. Sign up for ScreenshotNeo’s free plan.
If you meant Google cannot find the page
Search indexing is separate from Percy’s ability to load a snapshot URL. For indexing questions, Google Search Console directs site owners to URL Inspection to investigate why a page might not be indexed; links and sitemaps can also help Google discover pages. See Google Search Console’s help on the video indexing report.
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.
