← Load Test Directory

Overview

Modern web pages often serve a mix of dynamic and static content. While dynamic content, such as database-driven content, is the primary source of load, static content (like images, stylesheets, and JavaScript) can also influence server performance. While it's common for LoadForge tests to exclude these static assets, testing them can offer a comprehensive view of a site's performance.

Example: Load Testing Static Content

In the example provided, we illustrate a test that requests an index page followed by requests for a CSS file, a JS file, and an image. Notice the image request; it has a custom weight @task(4). This weight ensures that the image is requested four times more frequently than other assets, simulating a scenario where a page might have multiple images compared to other static content.

Test Script

from locust import HttpUser, task, between

class QuickstartUser(HttpUser):
    # Defines the wait time between tasks
    wait_time = between(5, 9)

    # This task fetches the index page and its associated JS and CSS files
    @task(1)
    def index_page(self):
        self.client.get("/")
        self.client.get("/app.js")
        self.client.get("/app.css")

    # This task emulates loading an image and is set to run 4 times as frequently
    @task(4)
    def image_selection(self):
        self.client.get("/images/logo.jpg")

---

By including static content in your tests, you ensure that your server's full capacity—across both dynamic and static content—is measured, helping you prepare for real-world scenarios.