Process request and process response in Django - Performance & Optimization

Performance: Process request and process response

MEDIUM IMPACT

This affects how quickly the server handles incoming requests and sends back responses, impacting page load speed and interaction responsiveness.

Handling HTTP requests and responses in Django middleware

Django

import asyncio

def middleware(get_response):
    async def middleware_func(request):
        # Offload heavy task asynchronously
        asyncio.create_task(do_heavy_task_async())
        response = await get_response(request)
        # Lightweight response modification
        response.content = fast_modification(response.content)
        return response
    return middleware_func

Asynchronous processing avoids blocking the main request thread, speeding up response time.

📈 Performance GainReduces blocking time by 80%, improving LCP and INP

Handling HTTP requests and responses in Django middleware

Django

def middleware(get_response):
    def middleware_func(request):
        # Heavy synchronous processing before response
        do_heavy_task()
        response = get_response(request)
        # Modifying response with expensive operations
        response.content = expensive_modification(response.content)
        return response
    return middleware_func

Heavy synchronous tasks block the request processing, delaying response and increasing server time.

📉 Performance CostBlocks rendering for 100+ ms per request, increasing LCP and INP

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Synchronous heavy processing in middleware	N/A (server-side)	N/A	Delays browser paint start	[X] Bad
Asynchronous lightweight processing in middleware	N/A (server-side)	N/A	Faster browser paint start	[OK] Good

Rendering Pipeline

The request is received by Django, processed through middleware and views, then the response is constructed and sent back. Slow processing delays the server response, impacting browser rendering start.

→Request Processing

→Response Construction

→Network Transfer

⚠️ BottleneckSynchronous blocking operations during request or response processing

Core Web Vital Affected

LCP, INP

This affects how quickly the server handles incoming requests and sends back responses, impacting page load speed and interaction responsiveness.

Optimization Tips

1Avoid heavy synchronous tasks during request processing to reduce server delay.

2Use asynchronous operations to offload expensive work outside the main request cycle.

3Keep response modifications lightweight to speed up response delivery.

Performance Quiz - 3 Questions

What impact does synchronous heavy processing in Django request handling have on page load?

A Reduces network latency

B Improves browser rendering speed

C Increases server response time, delaying LCP

D Has no impact on performance

DevTools: Network

How to check: Open DevTools, go to Network tab, reload page, and check the Time column for server response time.

What to look for: Look for long 'Waiting (TTFB)' times indicating slow server processing affecting LCP.

Practice

1. What does the request object in a Django view primarily contain?

easy

A. Information sent by the user, like form data and headers

B. The HTML template to render

C. The final content sent back to the user

D. Database connection details

Solution

1. Step 1: Understand the role of the request object

   The request object holds all data sent by the user, such as form inputs, cookies, and headers.

2. Step 2: Differentiate request from response

   The response object is what the server sends back, not the request.

3. Final Answer:

   Information sent by the user, like form data and headers -> Option A

4. Quick Check:

   Request = User data [OK]

Hint: Request holds user input; response sends output [OK]

Common Mistakes:

• Confusing request with response
• Thinking request contains templates
• Assuming request holds server data

2. Which of the following is the correct way to return a simple text response in a Django view?

easy

A. return HttpResponse('Hello World')

B. return render('Hello World')

C. return JsonResponse('Hello World')

D. return redirect('Hello World')

Solution

1. Step 1: Identify the correct response class for text

   HttpResponse is used to send plain text or HTML content back to the user.

2. Step 2: Check other options

   render is for templates, JsonResponse for JSON data, redirect for URL redirects.

3. Final Answer:

   return HttpResponse('Hello World') -> Option A

4. Quick Check:

   Text response uses HttpResponse [OK]

Hint: Use HttpResponse for plain text output [OK]

Common Mistakes:

• Using render without a template
• Using JsonResponse for plain text
• Confusing redirect with response content

3. Given this Django view code, what will be the output when accessed?

from django.http import JsonResponse

def my_view(request):
    data = {'name': 'Alice', 'age': 30}
    return JsonResponse(data)

medium

A. name=Alice&age=30

B. {'name': 'Alice', 'age': 30}

C. {"name": "Alice", "age": 30}

D. An error because JsonResponse needs a string

Solution

1. Step 1: Understand JsonResponse output format

   JsonResponse converts the Python dictionary into a JSON string with double quotes.

2. Step 2: Check the output format

   The output is a JSON string: {"name": "Alice", "age": 30} with double quotes, not Python dict syntax.

3. Final Answer:

   {"name": "Alice", "age": 30} -> Option C

4. Quick Check:

   JsonResponse outputs JSON string [OK]

Hint: JsonResponse outputs JSON with double quotes [OK]

Common Mistakes:

• Expecting Python dict syntax in output
• Confusing URL query string with JSON
• Thinking JsonResponse needs string input

4. What is wrong with this Django view code?

from django.http import HttpResponse

def bad_view(request):
    response = HttpResponse('Hello')
    response.status_code = '404'
    return response

medium

A. HttpResponse cannot have status_code set manually

B. status_code must be an integer, not a string

C. Missing return statement

D. HttpResponse requires a JSON object

Solution

1. Step 1: Check the status_code assignment

   Status codes must be integers like 404, not strings like '404'.

2. Step 2: Confirm HttpResponse usage

   HttpResponse allows setting status_code manually but it must be int.

3. Final Answer:

   status_code must be an integer, not a string -> Option B

4. Quick Check:

   status_code = int, not string [OK]

Hint: status_code must be int, not string [OK]

Common Mistakes:

• Using string for status_code
• Thinking HttpResponse forbids status_code
• Forgetting to return response

5. You want to create a Django view that processes a POST request with JSON data and returns a JSON response with a message and the original data. Which code snippet correctly handles this?

hard

A. def view(request):
data = request.GET
return JsonResponse({'message': 'Received', 'data': data})

B. def view(request):
data = request.POST
return HttpResponse({'message': 'Received', 'data': data})

C. def view(request):
data = request.body
return JsonResponse(data)

D. def view(request):
data = json.loads(request.body)
return JsonResponse({'message': 'Received', 'data': data})

Solution

1. Step 1: Parse JSON from POST request body

   request.body contains raw bytes; json.loads converts it to a Python dict.

2. Step 2: Return JsonResponse with message and data

   JsonResponse correctly serializes the Python dict to JSON for response.

3. Step 3: Check other options

   def view(request): data = request.POST return HttpResponse({'message': 'Received', 'data': data}) wrongly uses HttpResponse with dict, def view(request): data = request.GET return JsonResponse({'message': 'Received', 'data': data}) uses GET instead of POST, def view(request): data = request.body return JsonResponse(data) returns raw bytes without parsing.

4. Final Answer:

   def view(request): data = json.loads(request.body) return JsonResponse({'message': 'Received', 'data': data}) -> Option D

5. Quick Check:

   Parse JSON body, respond with JsonResponse [OK]

Hint: Parse JSON from request.body, respond with JsonResponse [OK]

Common Mistakes:

• Using request.POST for JSON body
• Returning dict in HttpResponse
• Not parsing JSON before response