Email verification pattern in Flask - Performance & Optimization

Performance: Email verification pattern

MEDIUM IMPACT

This pattern affects page load speed and interaction responsiveness during user registration and verification steps.

Verifying user email during registration without blocking UI

Flask

from flask import Flask, request, jsonify
from threading import Thread
app = Flask(__name__)

def send_verification_email_async(email):
    # simulate sending email
    import time
    time.sleep(5)
    print(f'Verification email sent to {email}')

@app.route('/register', methods=['POST'])
def register():
    email = request.form['email']
    Thread(target=send_verification_email_async, args=(email,)).start()
    return jsonify({'message': 'Registration complete, verification email sent asynchronously'})

Sends email in background thread, allowing immediate HTTP response and smooth UI interaction.

📈 Performance GainNon-blocking request, reduces user wait time by 5 seconds, improves INP significantly.

Verifying user email during registration without blocking UI

Flask

from flask import Flask, request
import time
app = Flask(__name__)

@app.route('/register', methods=['POST'])
def register():
    email = request.form['email']
    # Simulate sending email synchronously
    send_verification_email(email)  # blocks request until done
    return 'Registration complete, check your email!'

def send_verification_email(email):
    time.sleep(5)  # simulate delay
    print(f'Verification email sent to {email}')

Sends verification email synchronously, blocking the HTTP request and delaying response to user.

📉 Performance CostBlocks rendering and response for 5 seconds, causing poor INP and user frustration.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Synchronous email sending	Minimal	N/A	Blocks paint until response	[X] Bad
Asynchronous email sending	Minimal	N/A	Immediate paint and interaction	[OK] Good

Rendering Pipeline

Synchronous email sending blocks server response, delaying browser rendering and interaction readiness. Asynchronous sending frees server to respond immediately, allowing browser to paint and become interactive faster.

→Network

→JavaScript Execution

→Rendering

⚠️ BottleneckNetwork and server processing blocking response

Core Web Vital Affected

INP

This pattern affects page load speed and interaction responsiveness during user registration and verification steps.

Optimization Tips

1Never block HTTP responses with long-running tasks like sending emails.

2Use background threads or task queues to handle email sending asynchronously.

3Test user interaction speed with DevTools Performance panel to catch blocking tasks.

Performance Quiz - 3 Questions

What is the main performance problem with sending verification emails synchronously during registration?

A It increases CSS paint time

B It blocks the server response, delaying page interaction

C It causes layout shifts on the page

D It reduces image loading speed

DevTools: Performance

How to check: Record a performance profile while submitting registration form; look for long tasks blocking main thread and delayed Time to Interactive.

What to look for: Long blocking tasks during request and delayed user interaction readiness indicate synchronous blocking.

Practice

1. What is the main purpose of email verification in a Flask application?

easy

A. To store user data securely in the database

B. To confirm that the user owns the provided email address

C. To speed up the login process

D. To encrypt the user's password

Solution

1. Step 1: Understand email verification purpose

   Email verification is used to confirm that the user actually owns the email they provided during signup.

2. Step 2: Differentiate from other security tasks

   Encrypting passwords and speeding login are different tasks unrelated to email verification.

3. Final Answer:

   To confirm that the user owns the provided email address -> Option B

4. Quick Check:

   Email verification = Confirm ownership [OK]

Hint: Email verification confirms user email ownership [OK]

Common Mistakes:

• Confusing email verification with password encryption
• Thinking it speeds up login
• Assuming it stores data securely

2. Which Flask library is commonly used to create timed tokens for email verification?

easy

A. flask_sqlalchemy

B. flask_login

C. itsdangerous

D. flask_mail

Solution

1. Step 1: Identify token generation library

   The itsdangerous library provides URLSafeTimedSerializer to create timed tokens.

2. Step 2: Differentiate from other Flask extensions

   flask_sqlalchemy manages databases, flask_login handles user sessions, and flask_mail sends emails but does not create tokens.

3. Final Answer:

   itsdangerous -> Option C

4. Quick Check:

   Token creation = itsdangerous [OK]

Hint: Use itsdangerous for timed token creation [OK]

Common Mistakes:

• Choosing flask_mail for token creation
• Confusing flask_login with token generation
• Selecting flask_sqlalchemy incorrectly

3. Given this Flask code snippet, what will verify_token(token) return if the token is expired?

from itsdangerous import URLSafeTimedSerializer, SignatureExpired

serializer = URLSafeTimedSerializer('secret-key')

def verify_token(token):
    try:
        email = serializer.loads(token, max_age=3600)
        return email
    except SignatureExpired:
        return None

medium

A. Returns None

B. Raises a SignatureExpired exception

C. The email string inside the token

D. Returns an empty string

Solution

1. Step 1: Understand token verification logic

   The function tries to load the token with a max age of 3600 seconds (1 hour).

2. Step 2: Handle expired token exception

   If the token is expired, it raises SignatureExpired, which is caught and returns None.

3. Final Answer:

   Returns None -> Option A

4. Quick Check:

   Expired token returns None [OK]

Hint: Expired tokens return None in try-except block [OK]

Common Mistakes:

• Expecting exception to propagate
• Assuming it returns empty string
• Thinking it returns the email anyway

4. Identify the error in this Flask email verification token generation code:

from itsdangerous import URLSafeTimedSerializer

serializer = URLSafeTimedSerializer('secret-key')

def generate_token(email):
    token = serializer.dumps(email)
    return token

# Later verification
email = serializer.loads(token, max_age=3600)

medium

A. Token variable is undefined at verification

B. Missing secret key in serializer initialization

C. max_age parameter is invalid in loads()

D. Using dumps() instead of loads() to verify

Solution

1. Step 1: Check token generation and usage

   The token is generated inside generate_token but not stored or passed outside.

2. Step 2: Verify token usage scope

   At verification, token is used but not defined in that scope, causing a NameError.

3. Final Answer:

   Token variable is undefined at verification -> Option A

4. Quick Check:

   Undefined token variable causes error [OK]

Hint: Ensure token variable is defined before verification [OK]

Common Mistakes:

• Ignoring variable scope for token
• Thinking secret key is missing
• Misusing max_age parameter

5. You want to implement email verification in Flask so that users receive a link with a token that expires after 24 hours. Which approach correctly combines token creation, sending email, and verification?

hard

A. Generate token without secret key, send email, verify token ignoring expiration

B. Store plain email in database, send email without token, verify by matching email only

C. Send token as plain text in email body, verify token with max_age=3600

D. Generate token with URLSafeTimedSerializer, send email with token link, verify token with max_age=86400

Solution

1. Step 1: Create token with expiration

   Use URLSafeTimedSerializer with a secret key to generate a token that expires after 86400 seconds (24 hours).

2. Step 2: Send email with token link and verify properly

   Send the token inside a URL link in the email. Verify the token using loads() with max_age=86400 to enforce expiration.

3. Final Answer:

   Generate token with URLSafeTimedSerializer, send email with token link, verify token with max_age=86400 -> Option D

4. Quick Check:

   Token creation + email + 24h expiry = Generate token with URLSafeTimedSerializer, send email with token link, verify token with max_age=86400 [OK]

Hint: Use max_age=86400 for 24h token expiry [OK]

Common Mistakes:

• Not using tokens in email links
• Ignoring token expiration
• Sending tokens without secret key