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.

Practice

1. What is the main purpose of a before_request hook in Flask?

easy

A. To run code before every request to prepare or check something

B. To define the main route of the application

C. To handle errors after a request is processed

D. To send the final response to the client

Solution

1. Step 1: Understand the role of before_request

   The before_request hook runs before each request to prepare data or check conditions.

2. Step 2: Compare with other options

   Defining routes, handling errors, or sending responses happen elsewhere, not in before_request.

3. Final Answer:

   To run code before every request to prepare or check something -> Option A

4. Quick Check:

   before_request runs before request = C [OK]

Hint: before_request runs code before each request [OK]

Common Mistakes:

• Confusing before_request with route handlers
• Thinking it handles errors or sends responses
• Assuming it runs after the request

2. Which of the following is the correct way to register a before_request hook in Flask that does not short-circuit the request?

easy

A. @app.before_request\nclass BeforeHook: pass

B. @app.before_request()\ndef before(): pass

C. @app.before_request\ndef before(): return 'Hello'

D. @app.before_request\ndef before(): pass

Solution

1. Step 1: Recall the decorator syntax

   The before_request decorator is used without parentheses: @app.before_request.

2. Step 2: Check function definition

   The hook must be a function, not a class, and must not return a response to continue to the route.

3. Final Answer:

   @app.before_request\ndef before(): pass -> Option D

4. Quick Check:

   Decorator without () and function = D [OK]

Hint: Use @app.before_request without parentheses [OK]

Common Mistakes:

• Adding parentheses after @app.before_request
• Defining a class instead of a function
• Returning a value when not needed

3. Given this Flask code, what will be the output when accessing /?

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

@app.before_request
def check():
    return redirect('/login')

@app.route('/')
def home():
    return 'Home Page'

@app.route('/login')
def login():
    return 'Login Page'

medium

A. Home Page

B. Login Page

C. Redirect loop error

D. 404 Not Found

Solution

1. Step 1: Analyze the before_request hook

   The check function unconditionally returns a redirect to /login for every request.

2. Step 2: Determine the final response

   Request to / redirects to /login, but /login also triggers before_request which redirects again, causing an infinite loop.

3. Final Answer:

   Redirect loop error -> Option C

4. Quick Check:

   Always redirect to /login = C [OK]

Hint: Unconditional return in before_request causes loop [OK]

Common Mistakes:

• Expecting 'Login Page' without considering loop
• Thinking before_request does not run on /login
• Ignoring that every request triggers the hook

4. What is wrong with this Flask code snippet?

from flask import Flask
app = Flask(__name__)

@app.before_request
def before():
    print('Before request')
    return None

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

medium

A. before_request must return a response always

B. Nothing is wrong; code works fine

C. Printing inside before_request is not allowed

D. Returning None in before_request causes an error

Solution

1. Step 1: Understand return behavior in before_request

   Returning None means no response is sent, so Flask continues to route handler.

2. Step 2: Check if printing is allowed

   Printing is allowed and useful for debugging; it does not cause errors.

3. Final Answer:

   Nothing is wrong; code works fine -> Option B

4. Quick Check:

   None return means continue normal route = A [OK]

Hint: Return None or nothing to continue request normally [OK]

Common Mistakes:

• Thinking return None causes error
• Believing before_request must always return response
• Assuming print statements break Flask hooks

5. You want to use a before_request hook to block access to all routes except /login unless a user is logged in. Which code snippet correctly implements this?

hard

A. from flask import request, redirect, session
@app.before_request
def block():
if request.path != '/login' and not session.get('user'):
return redirect('/login')

B. from flask import request, redirect
@app.before_request
def block():
if request.path == '/login':
return redirect('/login')

C. from flask import session
@app.before_request
def block():
if not session.get('user'):
return 'Access Denied'

D. from flask import request
@app.before_request
def block():
if request.path == '/login' or session.get('user'):
return redirect('/login')

Solution

1. Step 1: Identify the condition to block access

   We want to redirect to /login if the path is not /login and user is not logged in.

2. Step 2: Check each option logic

   from flask import request, redirect, session @app.before_request def block(): if request.path != '/login' and not session.get('user'): return redirect('/login') correctly checks path and session, redirecting only when needed. Others either redirect wrongly or deny access without redirect.

3. Final Answer:

   from flask import request, redirect, session @app.before_request def block(): if request.path != '/login' and not session.get('user'): return redirect('/login') -> Option A

4. Quick Check:

   Check path and session, redirect if not logged in = A [OK]

Hint: Check path and session, redirect if not logged in [OK]

Common Mistakes:

• Redirecting /login to itself causing loop
• Not checking path before redirect
• Returning string instead of redirect response