Guest
5 speed tests / 24 hours
1 fixed website; no manual replacement
Set up a test, understand the evidence and manage your workspace.
No matching guides. Try another search or contact support.
Free reports show desktop speed summaries. Premium adds detailed measurements and waterfalls. Business adds technical evidence, repair guidance and captured browser images when available.
Enter a public HTTP or HTTPS URL on the homepage. Free and guest tests use desktop; paid plans also offer mobile. Open the live report to follow progress. No ownership verification is required for speed testing. Create an account to keep access to guest results.
Add the website under Websites. Publish its DNS TXT token or download the verification file and upload it to the website root. Verification is required for load, security and functional QA.
Choose a verified endpoint, GET or JSON POST, concurrency or request rate, duration and a standard or stepped profile. Advanced request checks remain available. Review the settings and queue the test.
Choose configuration checks, bounded probes or penetration testing. Penetration testing attacks the selected GET or JSON POST endpoint, optionally using encrypted test-session headers. Findings include confidence, requests sent per rule and repairs. Stored-XSS checks need explicit test-record consent. DOM-fragment checks run in penetration mode. Stored XSS, CSRF and role checks run when their dedicated sessions and application workflows are configured. Package advisory matching needs an exact inventory. Checks are bounded and report their actual execution status.
Functional QA visits up to five same-origin pages and checks expected text, HTTP status, JavaScript exceptions and failed resources. It inventories links and forms without submitting them. Login and purchase automation are not included.
Network conditions, browser work, third-party resources and the target itself can vary. Paid accounts can run three sequential audits and inspect the median-score run alongside the variation.
Speed and Structure grades summarize different evidence. Inspect timings, resources, filmstrip and charts according to your plan. Business Issues & fixes explains supported findings; missing evidence is labelled, never invented.
Paid users can configure checks for verified websites and choose email or Telegram notifications. Repeated failures open an incident and recovery sends an update. Configure alert destinations and use the test-notification control.
Free includes summary JSON/HTML downloads and print-to-PDF. Premium and Business include their permitted report details and email delivery to a verified account address when configured. Reports are private to their owner and administrators. Open Support to discuss testing, billing or account issues.
Contact support →Available processing capacity can reduce admitted load. Queue priority does not interrupt a running job. Compare the same URL, device and workload; cache state and third-party resources can change results. Keep the normal delivery path when measuring visitor experience.
Open My servers in the Business workspace. Enter the address, sign-in method and server identity key. Request setup, then follow administrator approval and installation progress. Only the assigned account can select the server for tests.
Follow the server setup guide →Finish its active tests, expand Connection details & removal, and confirm removal. LoadVM cleans up its inventoried components before deleting the saved connection and credentials. Shared prerequisites remain. Unreachable or older untracked installations require review.
Follow the server setup guide →Open Databases and save a connection using a dedicated read-only account. Discovery starts automatically and the list refreshes when it finishes. It includes only names accessible to that account. MySQL, PostgreSQL and SQL Server are supported.
Choose a discovered database and a table-read, connection-churn or custom SELECT workload. Increase clients gradually. Compare operation rate, latency, failures, optional engine counters and after-test connectivity. These read tests do not cover every InnoDB crash, write contention or recovery scenario.
Business connects an approved sender and receiver, then chooses Mbps, a total MB cap and a time limit. The report shows actual payload rate and receiver-confirmed volume. A single path test does not establish dedicated bandwidth or aggregate multiple ports.
Sign in with supported configured methods, reset your password and choose light or dark appearance. Prices and paid checkout depend on the published offer and payment configuration. An access upgrade does not itself prove a payment succeeded.
Plans & billing →Business users can choose an approved server under Execution server when starting a penetration test. The test runs on that server; first use may take longer while missing testing components are prepared. The selected website still needs ownership verification and permission to test. Free memory and available resources determine whether a scan can finish.
The test did not receive the application details needed for that check. Open Browser, role and vulnerability checks in the security setup:
Public DOM-fragment and TLS checks run automatically in penetration mode. A tested marker that did not execute is a negative result for that particular check, not proof that every XSS path is safe. Historical reports retain the checks actually run; start a new test after completing setup.
Requested mode gradually attempts your chosen client count. Automatic mode first reduces it to an estimate based on the testing server’s resources. Peak connections shows what the database actually accepted at the same time. A short run, connection limits, errors or resource protection can prevent the requested count being reached.
Clients are not operations per second. Query time, connection setup and the pause between operations determine throughput. Database tests let you change that pause; zero means continuous operations. Customer servers accept your chosen client count independently of hosted plan ceilings, but their physical capacity still limits the test. Administrators can adjust hosted limits under Control room → LoadVM testing servers.
Open Plans & billing to pay by card through Stripe and review your subscription. An upgrade uses a prorated adjustment for the remaining paid period, shown before you confirm. A downgrade or cancellation takes effect when the current paid period ends. You retain access until then; scheduling a downgrade does not refund unused days.
Use Manage billing for saved payment methods and invoices. Payment confirmation may take a short time to reach your account. Do not submit another payment while confirmation is pending. Contact support if the paid plan does not appear.
Open Plans & billing →5 speed tests / 24 hours
1 fixed website; no manual replacement
10 speed tests / 6 hours
3 websites; replace after 15 days
50 speed tests / 24 hours
7 websites; replace after 24 hours
25 load tests / 24 hours
Speed tests: no plan quota
Unlimited websites; replace anytime
Load tests: no plan quota
Usage windows start with the first accepted test. Replacement waits start when each website is added. Domain ceilings survive account cleanup. Guest sessions expire after 24 hours. Resource limits still apply.
Yes. Enter a public HTTP or HTTPS page URL to run a guest speed test. Guest allowances are shared per domain and the window starts with the first accepted test. See Pricing for the current limits. Create an account to keep access to reports.
Load and security tests require a DNS TXT record or a verification file on the target website. The service checks ownership again before testing. Speed tests do not require verification.
No. Business tests assess selected endpoints and configured browser workflows. DOM-fragment checks run in penetration mode. Stored XSS, CSRF and role checks need dedicated sessions and approved application actions. Review each execution status and its evidence; unconfigured checks are not passes and no scan provides exhaustive coverage.
A bounded test shows performance at the chosen workload. It cannot establish a universal maximum-user count. Response sizes, request frequency, application behavior and generator capacity all matter.
Free includes summary JSON, HTML and print-to-PDF downloads. Premium and Business export their permitted report details and can email reports to their verified account address when email delivery is enabled.
Business can add servers using an SSH key or password, subject to administrator approval. Network tests measure a transfer between approved servers; database tests use a dedicated read-only account.
Guest workspaces expire 24 hours after creation. Cleanup removes expired guest reports after active tests finish. Closing a browser ends normal guest-session access, although browser session restoration may retain it until expiry. Create an email account before expiry to keep the same workspace and reports. Domain usage limits survive guest cleanup.
Business includes captured images, filmstrips and live browser previews. Free and Premium retain their permitted measurements without browser images. A report may contain fewer images when the page produces fewer captured frames. LoadVM displays available evidence without inventing missing frames.
Mobile and desktop are different measurement profiles. Mobile includes simulated network and CPU constraints, plus a mobile viewport. A low mobile score does not mean the test itself ran incorrectly. Compare the same URL, profile and cache conditions; look at LCP, blocking time and the affected resources before choosing a fix.
The filmstrip is the captured browser loading sequence. Simulated timing estimates and screenshot timestamps represent different measurements. Repeat tests for consistency; a single score is not a capacity guarantee.
Click the service badge for current availability and maintenance notices. A delayed status check means the browser could not refresh the status data; it does not prove your website is down. Monitoring alerts concern your configured websites separately.
Use Support for account questions or the public contact form for guest enquiries. Your support conversation stays with your account. Avoid including passwords or secret keys.
Read the report error before retrying. Check the URL and public access. A login page, blocked request, redirect or outage can prevent testing. If it keeps failing, send the test ID to support.
Check the DNS record or verification file against the instructions for your website. DNS changes may take time. The file must be publicly accessible. Keep your verification proof in place after approval.
Keep your normal website setup to measure what visitors experience. Cached and uncached requests can have different timings. Compare the same URL and device profile under similar conditions.
Check your plan and service status. Some features need a verified website, an approved server or a completed connection. A paid plan does not override a temporarily disabled service.
Open Dashboard → Websites and add your domain. Complete domain verification, then open AI Growth → Websites & brands. Choose that website, enter your business name and select Save website.
Tracking is optional. Enter one customer question per line, add competitor names if useful, then choose an available AI service, language, country and frequency. Save the schedule. Run check now collects answers; it does not submit your website for ranking.
For WordPress, open Connections. Enter your site URL, WordPress username and an application password created in WordPress → Users → Profile. Connect, then open WordPress posts → Write a new post. Manual publishing does not require an AI provider.
For outreach, connect your email service with its API key, verified sender and business address. Add a recipient, write and save a message, review it, then approve and send or schedule. For posts, save your draft before approving and publishing. Check Activity for delivery errors.
Business penetration tests include a bounded DOM fragment execution check and, for HTTPS, protocol and cipher offers. Use the configuration box for the workflows below. Combine sections in one JSON object. Sessions and workflow data are encrypted; use dedicated accounts and disposable staging records.
Supply two different sessions. The owner must see a distinctive marker in the protected test record. The restricted account must be signed in, as established by its session page, and must not have access to that record. Only the selected GET operation is tested.
{
"roles": {
"path": "/test-records/owner-only",
"expected_text": "DISPOSABLE_OWNER_RECORD",
"owner_headers": {"Cookie": "session=OWNER_TEST_SESSION"},
"restricted_headers": {"Cookie": "session=RESTRICTED_TEST_SESSION"},
"session_path": "/test-account",
"session_text": "RESTRICTED_ACCOUNT_SIGNED_IN"
}
}Use JSON POST endpoints that create and delete disposable records. The create response must contain a top-level record ID. The view page is opened in a separate browser context. The test marker does not extract data. Enable the workflow permission checkbox. Cleanup failures require inspection before retrying.
{
"stored": {
"create": {"path": "/staging-notes", "body": {"text": "{{probe}}"}},
"id_field": "id",
"view_path": "/staging-notes/{{id}}",
"cleanup": {"path": "/staging-notes/{{id}}/delete", "body": {"id": "{{id}}"}}
}
}Supply the test account Cookie or Authorization header in the session fields. Arbitrary click sequences, login refresh and every possible rendering context are not covered.
Use URL-encoded POST endpoints with a readable state check and cleanup action. Copy the test session cookie attributes accurately; changing SameSite or Secure changes what is being tested. The runner checks anonymous access, a same-origin reference action and an opaque-origin HTML form. It reports confirmation only when the expected state changes. Do not include passwords or anti-CSRF tokens in the action fields.
{
"csrf": {
"cookies": [{"name": "session", "value": "TEST_SESSION", "sameSite": "Lax", "secure": true, "httpOnly": true}],
"action": {"path": "/staging-preference", "body": {"value": "{{marker}}"}},
"verify_path": "/staging-preference",
"cleanup": {"path": "/staging-preference/reset", "body": {"value": "{{marker}}"}}
}
}The verify endpoint must return HTTP success and include the marker only after the action succeeds. The workflow permission checkbox is required. Other cross-site origins and actions need separate tests.
Provide exact installed versions, up to 20 packages. Approve the inventory-sharing checkbox: package names and versions are sent to the public advisory lookup service. A version match is not proof of exploitation; vendor backports and configuration affect applicability.
{
"dom": true,
"tls": true,
"packages": [{"ecosystem": "npm", "name": "YOUR_PACKAGE", "version": "EXACT_VERSION"}]
}Supported ecosystems: npm, PyPI, Packagist, Maven, Go, RubyGems, crates.io and NuGet. TLS tests are bounded to protocols and cipher offers supported by the testing runtime. Failed handshakes may reflect network or client limitations. No scan can guarantee exhaustive CVE coverage.