Free fit check · public metadata only

Name the three flows
that must keep working.

Share public URLs and expected visible results. Do not send credentials, private source, customer data, or payment information.

The paid baseline, if it fits

One customer-controlled public website.
Up to three agreed user flows and twelve checkpoints.
Chromium at 1440 × 1000 and 390 × 844.
Python pytest/Playwright with a small page-object layer.
Three clean runs, JUnit XML, failure screenshots, a short issue ledger, README, and one correction pass.

Inspect the executed LazyTravel proof →

Check the site

Review first: nothing is sent while you fill in the form or choose “Review request.” Do not include passwords, access tokens, private URLs, personal data, or confidential source text.

Contact email Used only to reply to this fit check.

Public site URL and your role State the public domain and how you are authorized to request tests for it.

Up to three priority flows For each flow, list the starting URL, short action sequence, and visible result that means it passed.

Repository and CI environment Optional. Python version, repository host, and CI provider if the tests should enter an existing repository.

Known failures or unstable dependencies Optional. Note consent banners, third-party APIs, animations, or intermittent behavior.

Preferred delivery and deadline For example: pull request to a named repository, or a source archive; include the practical deadline.

Other constraints

I control this site or am authorized to request testing of its public flows, and I will not send credentials or private data at this stage. I understand that the fixed USD 250 baseline covers one public website, up to three agreed flows and twelve checkpoints, Chromium at 1440 × 1000 and 390 × 844, and one correction pass. Login, private staging, CAPTCHA or MFA bypass, destructive or payment actions, cross-browser coverage, site fixes, certification, deployment, and ongoing maintenance are excluded.

Return to the offer

Review before sending

Check the exact request below. Nothing has been sent.

I reviewed the request above and want to make “Send fit check” available.

Choose how to continue. “Send fit check” encrypts the reviewed request for private review. You can also prepare it in your email app or copy it.

Open in email

What happens next

I check whether the public flows are stable, non-destructive, and small enough for the fixed baseline.
If they fit, both sides accept the exact written scope, delivery, cancellation, and refund terms.
A Stripe payment request follows scope acceptance. Marketplace clients keep contract and payment on that marketplace.
No credentials or private customer data are needed for this offer.

Name the three flowsthat must keep working.

The paid baseline, if it fits

Check the site

Review before sending

What happens next

Name the three flows
that must keep working.