diff --git a/assets/images/hyperexecute/frameworks/performance_testing/10.png b/assets/images/hyperexecute/frameworks/performance_testing/10.png
deleted file mode 100644
index 0f4c3db1e..000000000
Binary files a/assets/images/hyperexecute/frameworks/performance_testing/10.png and /dev/null differ
diff --git a/assets/images/hyperexecute/frameworks/performance_testing/11.png b/assets/images/hyperexecute/frameworks/performance_testing/11.png
deleted file mode 100644
index 6016ae63f..000000000
Binary files a/assets/images/hyperexecute/frameworks/performance_testing/11.png and /dev/null differ
diff --git a/assets/images/hyperexecute/frameworks/performance_testing/7.png b/assets/images/hyperexecute/frameworks/performance_testing/7.png
deleted file mode 100644
index 6867b2700..000000000
Binary files a/assets/images/hyperexecute/frameworks/performance_testing/7.png and /dev/null differ
diff --git a/assets/images/hyperexecute/frameworks/performance_testing/8.png b/assets/images/hyperexecute/frameworks/performance_testing/8.png
deleted file mode 100644
index 4cdcec0f2..000000000
Binary files a/assets/images/hyperexecute/frameworks/performance_testing/8.png and /dev/null differ
diff --git a/assets/images/hyperexecute/frameworks/performance_testing/9.png b/assets/images/hyperexecute/frameworks/performance_testing/9.png
deleted file mode 100644
index 3c8787c83..000000000
Binary files a/assets/images/hyperexecute/frameworks/performance_testing/9.png and /dev/null differ
diff --git a/assets/images/hyperexecute/frameworks/performance_testing/error-reports.png b/assets/images/hyperexecute/frameworks/performance_testing/error-reports.png
new file mode 100644
index 000000000..621f2a4ff
Binary files /dev/null and b/assets/images/hyperexecute/frameworks/performance_testing/error-reports.png differ
diff --git a/assets/images/hyperexecute/frameworks/performance_testing/execute.gif b/assets/images/hyperexecute/frameworks/performance_testing/execute.gif
deleted file mode 100644
index 7fb7ead9f..000000000
Binary files a/assets/images/hyperexecute/frameworks/performance_testing/execute.gif and /dev/null differ
diff --git a/assets/images/hyperexecute/frameworks/performance_testing/execute.mp4 b/assets/images/hyperexecute/frameworks/performance_testing/execute.mp4
new file mode 100644
index 000000000..122140b6b
Binary files /dev/null and b/assets/images/hyperexecute/frameworks/performance_testing/execute.mp4 differ
diff --git a/assets/images/hyperexecute/frameworks/performance_testing/logs.png b/assets/images/hyperexecute/frameworks/performance_testing/logs.png
new file mode 100644
index 000000000..82b6a5819
Binary files /dev/null and b/assets/images/hyperexecute/frameworks/performance_testing/logs.png differ
diff --git a/assets/images/hyperexecute/frameworks/performance_testing/request-stats.png b/assets/images/hyperexecute/frameworks/performance_testing/request-stats.png
new file mode 100644
index 000000000..1004455d6
Binary files /dev/null and b/assets/images/hyperexecute/frameworks/performance_testing/request-stats.png differ
diff --git a/assets/images/hyperexecute/frameworks/performance_testing/setup.gif b/assets/images/hyperexecute/frameworks/performance_testing/setup.gif
deleted file mode 100644
index 6ae31342f..000000000
Binary files a/assets/images/hyperexecute/frameworks/performance_testing/setup.gif and /dev/null differ
diff --git a/assets/images/hyperexecute/frameworks/performance_testing/setup.mp4 b/assets/images/hyperexecute/frameworks/performance_testing/setup.mp4
new file mode 100644
index 000000000..2c5b109d4
Binary files /dev/null and b/assets/images/hyperexecute/frameworks/performance_testing/setup.mp4 differ
diff --git a/assets/images/hyperexecute/frameworks/performance_testing/summary-report.png b/assets/images/hyperexecute/frameworks/performance_testing/summary-report.png
new file mode 100644
index 000000000..2494a0e1e
Binary files /dev/null and b/assets/images/hyperexecute/frameworks/performance_testing/summary-report.png differ
diff --git a/assets/images/hyperexecute/frameworks/performance_testing/timeline-report.png b/assets/images/hyperexecute/frameworks/performance_testing/timeline-report.png
new file mode 100644
index 000000000..edbc9ff15
Binary files /dev/null and b/assets/images/hyperexecute/frameworks/performance_testing/timeline-report.png differ
diff --git a/docs/hyperexecute-run-jmeter-tests.md b/docs/hyperexecute-run-jmeter-tests.md
index 45487b4f3..ad581ed49 100644
--- a/docs/hyperexecute-run-jmeter-tests.md
+++ b/docs/hyperexecute-run-jmeter-tests.md
@@ -46,32 +46,41 @@ import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/co
 
 ## Prerequisites
 
-- Setup the [JMeter Test Plan](https://jmeter.apache.org/usermanual/build-web-test-plan.html) using Apache JMeter GUI.
+- Setup the [JMeter Test Plan](https://jmeter.apache.org/usermanual/build-web-test-plan.html) using Apache JMeter GUI. After setting up a Test Plan, now you need to associate your test cases and execute it as well via HyperExecute.
 
-After setting up a Test Plan, now you need to associate your test cases and execute it as well via HyperExecute.
+You can use your own project to configure and test it. For demo purposes, we are using the sample repository.
+
+:::tip Sample repo
+Download or Clone the code sample for the JMeter Performance Testing from the LambdaTest GitHub repository to run the tests on the HyperExecute.
+
+<a href="https://github.com/LambdaTest/hyperexecute-jmeter-sample" className="github__anchor"><img loading="lazy" src={require('../assets/images/icons/github.png').default} alt="Image" className="doc_img"/> View on GitHub</a>
+:::
 
 ## Step 1: Setup your JMeter Project
 
-- Go to the [HyperExecute Project's Dashboard](https://hyperexecute.lambdatest.com/hyperexecute/projects) and click on the **Setup new project** button.
-- Browse and Upload the test plans that you have created.
+- Go to the [HyperExecute Project's Dashboard](https://hyperexecute.lambdatest.com/hyperexecute/projects) and click on the **New Project** button.
+- Browse and Upload your JMeter test files to create a new performance test project.
 - Click on the **Save** button
 
-<img loading="lazy" src={require('../assets/images/hyperexecute/frameworks/performance_testing/setup.gif').default} alt="HyperExecute" className="doc_img"/>
-
-## Step 2: Execute Your Test Plans
+<video class="right-side" width="100%" controls id="vid">
+<source src={require('../assets/images/hyperexecute/frameworks/performance_testing/setup.mp4').default} type="video/mp4" />
+</video>
 
+## Step 2: Execute your Test Plans
 - Select your desired **.jmx** file and click on the **Run** button.
 - Configure the following parameters to perform the testing and click on the **Continue** button
-
   - **Total Users :** This indicates the number of users you intend to test for.
   - **Duration (min) :** This specifies the desired duration for the test.
   - **Ramp-up Time (min) :** This specifies the amount of time it should take to reach the peak test load.
   - **Total Load Distribution :** Configure the **regions** in which you want to distribute the load testing as per the % of the users.
+  - **Split CSV :** Enables splitting the input data from a CSV file among different threads or regions. This ensures organized data utilization across parallel executions.
+  - **Job Labels :** Add meaningful labels or tags to test executions for better identification and traceability in logs and reports.
+  - **Machine count :**  Specify the number of machines (or nodes) to use for parallel test execution. This parameter is essential for scaling test workloads or reducing execution time.
 
 :::info
 **Supported Regions :** HyperExecute supports the following regions for performance testing
 - West US 2 (Moses Lake, Washington)
-- East US (Richmond, Virginia)
+- East US (Richmond, Virginia) (**default**)
 - Central India (Pune, Maharashtra)
 - Southeast Asia (Singapore)
 - Brazil South (São Paulo State, Brazil)
@@ -80,7 +89,9 @@ After setting up a Test Plan, now you need to associate your test cases and exec
 
 - Click on the **Run Test** button.
 
-<img loading="lazy" src={require('../assets/images/hyperexecute/frameworks/performance_testing/execute.gif').default} alt="HyperExecute" className="doc_img"/>
+<video class="right-side" width="100%" controls id="vid">
+<source src={require('../assets/images/hyperexecute/frameworks/performance_testing/execute.mp4').default} type="video/mp4" />
+</video>
 
 ## Step 3: Analyze Your Project Performance
 
@@ -96,24 +107,24 @@ After setting up a Test Plan, now you need to associate your test cases and exec
   - **Load** and **Response Time** graph.
   - Additional details like **regions** and test duration.
   
-<img loading="lazy" src={require('../assets/images/hyperexecute/frameworks/performance_testing/7.png').default} alt="HyperExecute"  width="1920" height="868" className="doc_img"/>
+<img loading="lazy" src={require('../assets/images/hyperexecute/frameworks/performance_testing/summary-report.png').default} alt="HyperExecute"  width="1920" height="868" className="doc_img"/>
 
 ### Timeline Report
 
-<img loading="lazy" src={require('../assets/images/hyperexecute/frameworks/performance_testing/8.png').default} alt="HyperExecute"  width="1920" height="868" className="doc_img"/>
+<img loading="lazy" src={require('../assets/images/hyperexecute/frameworks/performance_testing/timeline-report.png').default} alt="HyperExecute"  width="1920" height="868" className="doc_img"/>
 
 ### Request Stats
 
 You can analyze the number of requests sent on that particular time.
 
-<img loading="lazy" src={require('../assets/images/hyperexecute/frameworks/performance_testing/9.png').default} alt="HyperExecute"  width="1920" height="868" className="doc_img"/>
+<img loading="lazy" src={require('../assets/images/hyperexecute/frameworks/performance_testing/request-stats.png').default} alt="HyperExecute"  width="1920" height="868" className="doc_img"/>
 
 ### Errors
 - Here you can check the Error Code type, Error Count, percentage of that error, and the percent of error in all the samples.
 
-<img loading="lazy" src={require('../assets/images/hyperexecute/frameworks/performance_testing/10.png').default} alt="HyperExecute"  width="1920" height="868" className="doc_img"/>
+<img loading="lazy" src={require('../assets/images/hyperexecute/frameworks/performance_testing/error-reports.png').default} alt="HyperExecute"  width="1920" height="868" className="doc_img"/>
 
 ### Logs
 - You can check the logs of your Jobs executed.
 
-<img loading="lazy" src={require('../assets/images/hyperexecute/frameworks/performance_testing/11.png').default} alt="HyperExecute"  width="1920" height="868" className="doc_img"/>
\ No newline at end of file
+<img loading="lazy" src={require('../assets/images/hyperexecute/frameworks/performance_testing/logs.png').default} alt="HyperExecute"  width="1920" height="868" className="doc_img"/>