Before_request hooks in Flask - Performance & Optimization

Performance: Before_request hooks

MEDIUM IMPACT

This affects server response time and perceived page load speed by running code before each request is processed.

Running code before every HTTP request in a Flask app

Flask

from flask import Flask, g
app = Flask(__name__)

@app.before_request
def lightweight_task():
    g.data = 'ready'

@app.route('/')
def index():
    return g.data

The before_request hook does minimal work, avoiding blocking and allowing fast response.

📈 Performance GainResponse time is near instant, improving LCP and user experience.

Running code before every HTTP request in a Flask app

Flask

from flask import Flask, g
app = Flask(__name__)

@app.before_request
def heavy_task():
    # Simulate heavy computation or blocking IO
    import time
    time.sleep(2)  # blocks request handling
    g.data = 'done'

@app.route('/')
def index():
    return g.data

The before_request hook blocks every request for 2 seconds, delaying response and increasing load time.

📉 Performance CostBlocks server response for 2 seconds per request, increasing LCP significantly.

Performance Comparison

Pattern	Server Delay	Blocking Operations	Impact on LCP	Verdict
Heavy blocking code in before_request	High (2+ seconds)	Yes (sleep or blocking IO)	Severe delay	[X] Bad
Minimal setup in before_request	Low (milliseconds)	No	Fast response	[OK] Good

Rendering Pipeline

Before_request hooks run on the server before the response is generated and sent to the browser. Heavy or blocking operations here delay the server response, which delays the browser's ability to start rendering the page.

→Server Processing

→Network Transfer

→Browser Rendering

⚠️ BottleneckServer Processing stage is most expensive if before_request hooks do heavy work.

Core Web Vital Affected

LCP

This affects server response time and perceived page load speed by running code before each request is processed.

Optimization Tips

1Avoid blocking or heavy computations in before_request hooks.

2Use before_request hooks only for quick setup or checks.

3Offload heavy tasks to background jobs or async processes.

Performance Quiz - 3 Questions

What is the main performance risk of doing heavy work in a Flask before_request hook?

A It causes the browser to skip rendering the page.

B It delays the server response, increasing page load time.

C It increases the size of the HTML sent to the browser.

D It reduces the number of HTTP requests the browser makes.

DevTools: Network

How to check: Open DevTools, go to Network tab, reload the page, and check the Time to First Byte (TTFB) for the request.

What to look for: A high TTFB indicates server-side delay likely caused by heavy before_request hooks.