Skip to content
docs

LoadFocus Onboarding

Welcome to LoadFocus. This onboarding guide walks you through everything you need to do on day one: creating your account, inviting your team, and running your first tests across each service in your plan.

1. Create your LoadFocus account

Section titled “1. Create your LoadFocus account”

The first account you create becomes the team owner and is tied to billing. Use a long-lived business email (for example ops@yourcompany.com) rather than a personal address.

Sign up here:

https://loadfocus.com/signup?plan=load_free

This link creates an account on the free Load Testing plan. The other services have their own plans and limits, listed on the Pricing page.

2. Invite your team

Section titled “2. Invite your team”

LoadFocus is built around teams. Tests, monitors, reports, and integrations all live inside a team, so the next step is to add your colleagues.

Open the teams console:

https://teams.loadfocus.com

From there you can:

  • Create a team.
  • Invite members by email and assign them a role and the services they can use.
  • Review the invitations you have sent.

Team seats depend on your plan, and the Free plan includes none. Full reference: Teams and Members guide.

3. Get started with Load Testing

Section titled “3. Get started with Load Testing”

LoadFocus has three load testing engines on the same dashboard, and every plan, including Free, can run all three (the limits differ by plan). Pick the one that matches your stack.

3.1 Load Testing for Websites and APIs (HTTP)

Section titled “3.1 Load Testing for Websites and APIs (HTTP)”

The fastest path: paste a URL, choose virtual users and duration, and run a cloud load test from multiple geographic regions.

Use this when you want to load test a website, a single API endpoint, or a short multi-step user flow without writing a script.

3.2 Load Testing with JMeter

Section titled “3.2 Load Testing with JMeter”

Bring your existing .jmx test plans to LoadFocus and run them at scale from the cloud, with no JMeter master/slave infrastructure to maintain.

Use this when your team already has JMeter expertise or pre-built test plans you want to reuse.

3.3 Load Testing with k6

Section titled “3.3 Load Testing with k6”

Run k6 JavaScript test scripts from the LoadFocus cloud and view the results in the same dashboard as the other engines.

Use this when you prefer modern, code-based load tests written in JavaScript and want goals, thresholds, and scenarios as code.

4. Get started with Page Speed Monitoring

Section titled “4. Get started with Page Speed Monitoring”

Page Speed Monitoring runs scheduled Lighthouse-based checks on your pages and tracks Performance, SEO, Best Practices, and other audit scores over time, so you can catch regressions when you ship new features.

The Free plan allows 1 test a day and 1 a month. Paid plans raise those limits and add hourly, 6-hour and 12-hour schedules and sitemap import.

A good first setup:

  1. Add your most important page (home, pricing, or top landing page).
  2. Add alert channels (email, Slack, or Microsoft Teams).
  3. Schedule the monitor. Hourly, 6-hour and 12-hour schedules need a paid plan; 24-hour and longer schedules are available on every plan.
  4. Add alerts on the metrics you care about (Performance score, SEO score, etc.) so you hear about regressions without checking the dashboard.

5. Get started with API Monitoring

Section titled “5. Get started with API Monitoring”

API Monitoring runs scheduled uptime and functional checks against your API endpoints from multiple locations worldwide and alerts you when an assertion breaks (response status, body content, headers, or response time).

A good first setup:

  1. Add your most critical API endpoint (login, checkout, or a health endpoint).
  2. Add assertions for status code, response body, and response time.
  3. Set the check frequency. The shortest interval depends on your plan: 5 minutes on Free, 1 minute on Starter and 30 seconds on Professional (browser checks run at most every 5 minutes). Use a longer interval for staging.
  4. Pick the locations that match where your customers are.
  5. Wire alerts into the channel your on-call team actually watches (email, Slack, Microsoft Teams).

6. Where to go next

Section titled “6. Where to go next”

If anything in this guide is unclear, use the support widget on loadfocus.com.