Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsTo load test a website with Apache JMeter, model real user journeys in a Test Plan, generate concurrency with a Thread Group, send requests through HTTP Request samplers, validate responses with assertions, and run the finished .jmx plan from the command line. Use the GUI to build and debug; use non-GUI (CLI) mode for the measured run. Judge the result against service targets you define for your own environment—JMeter has no universal pass/fail latency or user-count threshold.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
This guide takes you from scenario design through reporting, including browser-journey recording, pacing, data variation, injector sizing, distributed execution, and the failure modes that can make a test look better or worse than the site really is.
As an Amazon Associate I earn from qualifying purchases.
Recommended Free Tools
What a JMeter website load test measures
JMeter is primarily an HTTP-level load generator. A JMeter thread represents a virtual user that executes the samplers and controllers in your plan. It does not reproduce every activity of a full browser, such as painting pixels or running all client-side code, unless those effects are represented by requests you explicitly send. That makes JMeter well suited to web pages, APIs, login flows, searches, checkouts, and other server-facing journeys, while requiring care when a result depends on browser rendering or client-only JavaScript.
Each virtual user follows the plan independently. The number of threads therefore expresses concurrency, not a guaranteed number of requests per second. Response speed, loops, timers, and the journey itself determine the resulting request rate. A plan that omits pacing can produce a burst of back-to-back requests unlike human use and can exhaust the injector before it stresses the target.
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
A useful plan usually contains these building blocks:
| Element | Role in the test |
|---|---|
| Test Plan | Top-level container for the scenario and its configuration. |
| Thread Group | Defines virtual-user count, ramp-up, loops, and optional duration. |
| HTTP Request samplers | Send page, API, form, or other HTTP/HTTPS requests. |
| HTTP Request Defaults | Centralize a shared protocol, host, and port so samplers need only their paths and action-specific settings. |
| Cookie Manager | Maintains cookies per thread so sessions behave more like browser sessions. |
| Header Manager and CSV Data Set Config | Supply required headers and vary users, credentials, search terms, or other input data. |
| Timers | Pause between samplers to model user pacing. |
| Assertions | Check status, text, JSON, or business markers rather than trusting transport success alone. |
| Listeners and saved results | Display or persist samples for debugging, analysis, and the generated report. |
Define the scenario and acceptance criteria first
Do not start by choosing an arbitrary thread count. First describe what users do and what “acceptable” means for this site, version, and environment. Obtain authorization from the site owner and agree on a test window; an unannounced high-volume run can be mistaken for an attack.
Choose representative journeys
List the actions that matter to the service, such as opening a landing page, searching, signing in, viewing an item, submitting a form, or completing checkout. Record the order, required inputs, authentication state, and expected response for each action. If several journeys have different business importance, represent them as separate thread groups or controllers with an explicit mix rather than silently giving every request equal weight.
Define measurable success conditions
Write targets for the particular environment under test. Common dimensions are response-time percentiles, throughput, error percentage, assertion-failure percentage, and behavior during ramp-up, steady state, and ramp-down. Also state the test duration, arrival profile, excluded resources, and any maintenance or monitoring limits. Apache’s JMeter guidance does not publish a universal website-user count, latency target, or pass/fail number, so these values must come from your service objectives and capacity plan.
- Specify which responses count as transport errors and which count as business failures.
- Decide whether redirects, cached responses, or expected validation errors are acceptable for each sampler.
- Identify the steady-state interval that will be compared with your targets; do not judge a run solely by its startup ramp.
- Record the application build, database state, feature flags, and test data assumptions.
Build the JMeter test plan
1. Create the Thread Group
- Open JMeter and choose Test Plan in the tree.
- Use Add > Threads (Users) > Thread Group.
- Set Number of Threads (users) to the concurrency required by your scenario.
- Set Ramp-up period (seconds) so threads start progressively rather than in one burst.
- Choose a loop count, or enable a duration and scheduler when the test should run for a fixed time.
Every thread executes the plan independently. A ten-thread group with a 100-second ramp-up starts successive threads 10 seconds apart, a pattern Apache uses to illustrate gradual startup. Adjust the interval to match the intended arrival profile and to prevent a coordinated spike.
2. Centralize connection settings
Right-click the Thread Group (or an appropriate controller) and add Config Element > HTTP Request Defaults. Enter the common protocol, server name or IP, and port. Leave path and method details to individual samplers. Centralizing these fields lets you move the same plan between staging and production-like environments by changing one configuration element instead of every request.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
Add Config Element > HTTP Cookie Manager for web sessions. Without it, cookies are not handled as a browser would be, so login state and server-side sessions can be wrong. Add a HTTP Header Manager when the application requires headers such as an API content type or correlation identifier. Use CSV Data Set Config when each virtual user needs a different account, token, search term, or other data value; keep credentials in a controlled test-data file rather than hard-coding one account into every thread.
3. Add HTTP Request samplers
Right-click the Thread Group and choose Add > Sampler > HTTP Request for each page or API action. Set the method, path, parameters, body, and any action-specific headers. Give samplers business names such as Search products or Submit checkout, not opaque recorder-generated labels. Clear naming makes failures intelligible in reports.
Use controllers when a journey has branches or optional work. For example, a login controller can precede a search controller, while a transaction controller can group the requests that form one business operation. Keep the sequence understandable; a plan that is technically executable but impossible to audit will be difficult to trust.
4. Add pacing and data variation
Choose Add > Timer under the scope where a delay belongs. Timers pause before samplers. They are essential when a human would read a page, type, or move between actions; without them, a thread immediately issues the next request and can create an unrealistic request rate. Use a consistent, documented delay model for the scenario and note whether any think time is fixed or varied.
Free tools Windows power users keep installed
One-click scans. No signup required.
Parameterize values that should differ between users or iterations. Verify that the supplied rows in a CSV file are sufficient for the planned concurrency and duration, and decide what happens when the file reaches end-of-file. Reusing one account for hundreds of threads can trigger application throttling or lockouts unrelated to normal capacity.
Record a browser journey—or author it manually
When recording helps
The HTTP(S) Test Script Recorder can capture a complicated sequence quickly, especially when you do not yet know every request made by a page. Configure the browser to use the recorder’s listening address and port shown by JMeter, perform the journey with test data, then stop recording and inspect the resulting plan.
Rank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
Filter before measuring
Recording captures more than the business actions you care about. Apply recorder filters and then review the plan to remove irrelevant image, stylesheet, JavaScript, font, analytics, and other embedded-resource requests when including them would clutter the test or distort the intended workload. Excluding a resource is a modeling decision: include it only when the capacity question specifically concerns that resource or the request volume is part of the user behavior you need to reproduce.
Clean and parameterize the recording
- Rename samplers by business action and group related requests.
- Delete duplicate navigations, recorder noise, and requests outside the chosen journey.
- Replace recorded account details, tokens, IDs, and search terms with variables or CSV data.
- Check redirects, hidden form fields, CSRF values, and dynamic identifiers.
- Add a Cookie Manager and required headers if the recording did not already model them correctly.
- Run the cleaned journey with one or a few threads before adding load.
Manual authoring is often faster for a small API or a stable set of endpoints. Recording should accelerate discovery, not replace review; an unedited recording is rarely an appropriate production load plan.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Model realistic load
| Control | What it changes | Question to answer |
|---|---|---|
| Number of threads | Maximum concurrent virtual users in that group. | How many users should be active at once? |
| Ramp-up period | How quickly those threads begin. | Should traffic arrive gradually, in stages, or as a burst? |
| Loop count | How many times each thread repeats its journey. | Is the workload iteration-based or time-based? |
| Duration/scheduler | How long threads continue running. | How long must the system sustain the load? |
| Timers | Delay between actions and resulting request rate. | What pause would a real user have? |
| Data mix | Variation in accounts, paths, and payloads. | Does the test exercise the same cache and database patterns as real traffic? |
Size the thread count against both the target’s expected concurrency and the injector’s ability to schedule threads, open connections, encrypt traffic, and store results. If the injector cannot keep up, increasing threads may measure the load generator rather than the website. Very short response times combined with an overloaded injector can also create coordinated-omission effects: the generator fails to send work at the intended times, making the target appear healthier than it is.
Use a staged plan when you need to locate a capacity boundary: establish a baseline, increase load in controlled steps, hold each step long enough to observe behavior, and stop if error rates or resource alarms make further traffic unsafe. Keep the arrival profile and hold periods identical when comparing builds.
Validate transport and business correctness
An HTTP 200 response proves only that the server returned a response with that status. It does not prove that the expected account is logged in, that a search returned results, or that checkout completed. Add assertions under each sampler or transaction to check the conditions that matter.
Useful assertion checks
- Expected status codes or acceptable status ranges for the action.
- Required text, titles, identifiers, or business markers in the response.
- JSON fields, values, and schema fragments for API responses.
- Presence of a success token and absence of an error message.
- Correlation values extracted from one response and supplied to the next request.
Keep assertions specific enough to catch an error page that happens to return a successful transport status, but stable enough not to fail on harmless presentation changes. JMeter records assertion failures as errors in its results and reports, so include them in the pass/fail calculation rather than looking only at network exceptions.
Rank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
Debug in the GUI without contaminating the load run
Use GUI mode to assemble the tree, inspect variables, and run a small smoke test. The View Results Tree listener is valuable for examining request and response details while debugging. It is expensive to keep enabled during a substantial run because rendering and retaining every response consumes injector resources. Remove it or disable heavy listeners before measuring.
Start with one thread and one iteration, then a small number of threads. Confirm DNS, TLS, authentication, cookies, redirects, dynamic values, assertions, and cleanup behavior. Check the application and infrastructure logs at the same time so a JMeter error can be matched to a server-side event. Only after the journey is correct should you test concurrency.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Run the measured test from the command line
Apache’s guidance is explicit: "Don’t run load test using GUI mode !" Save the plan and execute it in non-GUI mode so the injector spends resources on generating traffic rather than rendering results.
A typical run that saves samples and creates an HTML dashboard is:
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows 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 reinstalljmeter -n -t website-load.jmx -l results.jtl -e -o report -j jmeter.logHere, -n selects non-GUI mode, -t names the saved plan, -l writes result data, -e creates the report after execution, -o selects an empty output directory for that report, and -j writes the JMeter log. JMeter can write CSV or XML result formats; choose the format required by your analysis workflow and keep the raw file unchanged.
For repeatable runs, keep the .jmx file, properties, CSV data, JMeter version, Java version, command line, injector details, and environment configuration together with the result artifacts. If you override variables from the shell, record the exact overrides; JMeter properties can be supplied with -Jname=value and referenced in a plan with the appropriate property expression.
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
Prepare and scale the load injector
Before increasing concurrency, monitor the injector’s CPU, memory, network throughput, open sockets, disk space, and Java heap. A saturated injector produces misleading latency and throughput. Use a dedicated machine where possible, avoid desktop listeners, and ensure the operating system and Java runtime are supported by the JMeter version you use.
Distributed execution
If one injector cannot generate the required workload, use JMeter’s distributed mode. Start JMeter in server mode on remote engines, verify that the client can reach them, and control those engines from a client. A command-line client can target named engines with the remote-server option, for example:
jmeter -n -t website-load.jmx -R engine1,engine2 -l results.jtl -e -o reportAlternatively, run multiple CLI instances and combine their result files during analysis. In either design, synchronize the plan, properties, data files, JMeter and Java versions, clocks, network routes, and certificates across engines. Confirm that the aggregate traffic is representative of the user geography and that the test network itself is not the bottleneck.
Distributed testing multiplies traffic; it does not automatically make a test realistic. Document which engine generated which portion of the load, and verify that the target can distinguish test traffic if operational monitoring or cleanup requires it.
Analyze results and decide whether the site passed
Open the generated HTML report or analyze the saved result file with your reporting system. Examine at least:
- Response-time distributions, including the percentiles selected in your service objective.
- Throughput over time and whether it remained stable during the steady-state interval.
- Error percentage, transport failures, timeouts, and connection failures.
- Assertion failures separated from protocol errors.
- Behavior as load ramps up, holds, and ramps down.
- Injector resource usage and target-side CPU, memory, database, queue, and dependency metrics.
Compare those observations with the criteria defined before the run. A run passes only when the agreed response-time, throughput, error, and business-correctness conditions are met for the specified duration and environment. A low average latency cannot compensate for a failing high percentile or a checkout assertion failure. Conversely, a deliberately excluded static resource should not be counted as a failure unless the test objective included it.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Report enough context for another engineer to interpret the result: test date, application build, JMeter and Java versions, thread and ramp-up settings, loop or duration settings, timer strategy, data mix, excluded requests, injector topology, target environment, monitoring evidence, and any aborted interval. Preserve the raw results so a summary chart can be checked against the original samples.
Quick Recap
Troubleshoot misleading or failed runs
| Symptom | Likely cause | Action |
|---|---|---|
| Latency rises while injector CPU or heap is saturated | The generator is the bottleneck. | Disable heavy listeners, reduce retained results, tune or enlarge the injector, then repeat. |
| Many requests fail immediately at startup | Ramp-up is too abrupt, or connection and authentication setup is synchronized. | Lengthen ramp-up, stagger groups, and inspect server and injector logs. |
| Every user appears to share one session | Cookies or credentials are not separated per thread. | Use Cookie Manager and unique test data; verify variables in a low-load run. |
| HTTP status is successful but the journey is broken | No business assertion, or a server error page uses a successful status. | Add content, JSON, and success-marker assertions. |
| Results show an implausibly high request rate | Timers are missing, loops are wrong, or embedded resources were unintentionally included. | Inspect the request tree, add realistic pacing, and document resource filters. |
| Only some distributed engines fail | Version, data, network, certificate, clock, or firewall differences. | Compare engine configuration and run a small remote smoke test before load. |
| Report output is empty or cannot be regenerated | The output directory was not empty or the run did not save samples. | Use a new empty report directory, confirm the result path, and inspect the JMeter log. |
Reproducibility checklist
- Authorized target, test window, and rollback or stop conditions.
- Named journeys, user mix, test data source, and data-reset procedure.
- Thread counts, ramp-up, loops or duration, timers, controllers, and resource exclusions.
- Assertions and the exact success criteria used for the verdict.
- JMeter plan, properties, CSV files, command line, JMeter version, and Java version.
- Injector CPU, memory, network, heap, and distributed-engine topology.
- Target build, environment, monitoring dashboards, and relevant server logs.
- Raw result files, generated report, timestamps, and notes about anomalies or aborted intervals.
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.
