One platform for the web — load, API, DEM, uptime, all on the same timeline.
LoadGen runs the web stack as one engine — Playwright-based load on Core agents, visual API testing flows, SessionSight DEM, and uptime checks. Three vendors collapse into one timeline.
New Load Profile
Select a technology to create a new load profile
Select Technology
Choose the connection technology for your new load profile. Each technology has its own guided wizard.
Citrix Enhanced
Modern Citrix connection using StoreFront, NetScaler Gateway, or Web Interface. Supports multiple authentication methods.
VDI Technologies
Citrix Enhanced — StoreFront / Gateway
Citrix Basic — Direct ICA connection
RDP — Remote Desktop Protocol
Azure Virtual Desktop — Azure Virtual Desktop
Omnissa Horizon — Omnissa Horizon
Web & Automation
Web Testing — Browser automation
Core — Command-line execution
Special Modes
Local Client — Local VDI client
vWorkspace — Dell vWorkspace
The Problem
The web is full-stack. Your testing tool isn’t.
Real-user experience on the web is the overlap of API, frontend, third-party, and infrastructure. Tools that test only one of those leave the rest as guesswork.
HTTP-only load tests miss what users actually feel.
A 200 OK doesn’t describe a SPA hydration stall, a third-party script regression, or a checkout drop-off. Synthetic green covers real red.
API tests, load tests, and DEM live in three vendors.
Three contracts, three dashboards, three timelines. The user issue is in the seam where none of them looked.
Uptime and load tests rarely share a contract.
Uptime says "endpoint up." Load test says "p95 fine." Neither tells you that conversion is collapsing on the 14th step.
How LoadGen handles Web
Capture · Replay · Test · Monitor.
Four motions, every one running on the same Playwright engine — across heatmaps, journeys, API flows, load tests, and uptime checks.
Capture
SessionSight records real sessions across web, SPA, and multi-page apps. Heatmaps, journeys, and replay — image or DOM mode.
Replay
Visual API testing flows author validation logic against the same target — OpenAPI / Swagger import, environment variables, OAuth2 / Bearer auth.
Test
Generic wizard with native Web technology runs Playwright-based scenarios on Core agents (port 4850) — same engine as your monitoring profiles.
Monitor
Uptime checks (HTTP, REST, JSON-validated) and continuous E2E monitoring keep the loop closed between releases.
Live · SessionSight Heatmaps
See the click. See the rage. Test it next release.
Heatmaps and journeys live on the same canvas as the load test. Real friction informs the next API flow; the next API flow blocks the next regression at the gate.
Outcomes · before / after
Three vendors → one timeline. Real friction → real fixes.
Drawn from teams that consolidated their web testing + DEM + uptime onto LoadGen for one release cycle.
Before
4 days
After
2 hrs
Before
Day 3
After
Live
Before
3
After
1
Before
12 %
After
0.8 %
Web → Platform
Five features. One web stack.
Web isn’t a feature — it’s the way these five compose into a single capture-test-monitor loop.
- /config/load-profiles/new/web— Generic wizard · Web
- /api-testing/flows— Visual API flows
- /sessionsight/dashboard— Heatmaps · journeys · replay
- /uptime/checks— HTTP / REST / JSON checks
- /monitoring/profiles— Continuous web UX validation
Load Profile Wizard
Generic wizard with native Web technology — Playwright-based, multi-page and SPA aware.
/features/load-profile-wizard
API Flows
Visual API validation with 28+ specialized node types. OpenAPI / Swagger import. Reusable auth profiles.
/features/flow-editor
SessionSight
Heatmaps, journeys, and session replay — image or DOM mode. Multi-page and SPA support out of the box.
/products/sessionsight
Uptime
HTTP, REST, SQL, and Azure Function status checks. JSONPath validation. SLA-grade incident tracking.
/products/uptime
Alerting
When p95 climbs or a journey drops, the right channel pages — email, webhook, SMS, WhatsApp, Teams, Slack.
/features/alerting
Replace three web tools with one engine.
Capture your first session this afternoon. Author the API flow it implies. Run it as the gate stage on tomorrow’s release.
