collectstatic for production in Django - Performance & Optimization

Performance: collectstatic for production

MEDIUM IMPACT

This affects page load speed by optimizing how static files are served in production.

Serving static files efficiently in production

Django

Run `python manage.py collectstatic` to gather all static files into a single directory, then serve them via a dedicated web server or CDN.

Static files are served quickly and efficiently by optimized servers, reducing load time and server load.

📈 Performance GainImproves LCP by reducing static asset load time; offloads CPU from Django app server.

Serving static files efficiently in production

Django

Serving static files directly from Django during production without running collectstatic.

Django's development server is not optimized for static file delivery, causing slow load times and blocking rendering.

📉 Performance CostBlocks rendering for hundreds of milliseconds per request; increases server CPU load.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Serving static files via Django dev server without collectstatic	N/A	N/A	High due to slow asset load	[X] Bad
Serving static files after running collectstatic via CDN or web server	N/A	N/A	Low due to fast asset delivery	[OK] Good

Rendering Pipeline

Static files collected by collectstatic are served by fast web servers or CDNs, bypassing Django's slower development server, speeding up the critical rendering path.

→Network Request

→Resource Load

→Paint

⚠️ BottleneckNetwork Request and Resource Load when static files are served inefficiently

Core Web Vital Affected

LCP

This affects page load speed by optimizing how static files are served in production.

Optimization Tips

1Always run collectstatic before deploying to production.

2Serve static files from a dedicated web server or CDN, not Django's dev server.

3Check static asset load times in DevTools Network panel to ensure fast delivery.

Performance Quiz - 3 Questions

Why should you run collectstatic before deploying a Django app to production?

A To automatically update the database schema

B To minify Python code for faster execution

C To gather all static files into one location for efficient serving

D To enable debug mode for better error messages

DevTools: Network

How to check: Open DevTools, go to Network tab, reload the page, and filter by static assets like CSS, JS, and images.

What to look for: Look for long load times or large file sizes on static assets indicating inefficient serving; fast load times indicate good performance.

Practice

1. What is the main purpose of running collectstatic in a Django project before deployment?

easy

A. To gather all static files into one folder for easy serving in production

B. To compile Python code into bytecode

C. To migrate database changes

D. To start the Django development server

Solution

1. Step 1: Understand what collectstatic does

   The collectstatic command collects all static files from apps and places them into a single directory.

2. Step 2: Recognize its role in production

   This makes it easier for the web server to serve static files efficiently in production environments.

3. Final Answer:

   To gather all static files into one folder for easy serving in production -> Option A

4. Quick Check:

   collectstatic gathers static files [OK]

Hint: Remember: collectstatic collects static files for production [OK]

Common Mistakes:

• Confusing collectstatic with database migrations
• Thinking collectstatic runs the server
• Assuming collectstatic compiles Python code

2. Which setting must be defined in settings.py to specify where collectstatic will gather static files?

easy

A. STATIC_ROOT

B. MEDIA_ROOT

C. STATIC_URL

D. STATICFILES_DIRS

Solution

1. Step 1: Identify the setting for static file collection

   STATIC_ROOT tells Django the directory where collected static files will be placed.

2. Step 2: Differentiate from other static settings

   STATIC_URL is the URL prefix, MEDIA_ROOT is for user-uploaded files, and STATICFILES_DIRS lists additional static file locations.

3. Final Answer:

   STATIC_ROOT -> Option A

4. Quick Check:

   STATIC_ROOT sets collection folder [OK]

Hint: STATIC_ROOT is the folder for collected static files [OK]

Common Mistakes:

• Confusing STATIC_ROOT with STATIC_URL
• Using MEDIA_ROOT for static files
• Thinking STATICFILES_DIRS is the collection folder

3. Given the following settings.py snippet:

STATIC_URL = '/static/'
STATIC_ROOT = '/var/www/example.com/static/'
STATICFILES_DIRS = ['/home/user/project/assets']

What happens when you run python manage.py collectstatic?

medium

A. Static files are deleted from /var/www/example.com/static/

B. Static files remain in /home/user/project/assets and are not copied

C. Static files from assets and app static folders are copied to /var/www/example.com/static/

D. An error occurs because STATIC_URL is not a valid path

Solution

1. Step 1: Understand the role of STATICFILES_DIRS and STATIC_ROOT

   STATICFILES_DIRS lists extra folders with static files, and STATIC_ROOT is the destination for collected files.

2. Step 2: What collectstatic does

   Running collectstatic copies all static files from app static folders and STATICFILES_DIRS into STATIC_ROOT.

3. Final Answer:

   Static files from assets and app static folders are copied to /var/www/example.com/static/ -> Option C

4. Quick Check:

   collectstatic copies files to STATIC_ROOT [OK]

Hint: collectstatic copies all static files to STATIC_ROOT [OK]

Common Mistakes:

• Thinking STATIC_URL affects file copying
• Believing files stay in source folders
• Assuming collectstatic deletes files

4. You run python manage.py collectstatic but get an error: Permission denied for the STATIC_ROOT directory. What is the best way to fix this?

medium

A. Remove the STATIC_ROOT setting from settings.py

B. Change permissions of the STATIC_ROOT folder to allow write access

C. Run collectstatic without any arguments

D. Delete all static files from your apps

Solution

1. Step 1: Understand the error cause

   The Permission denied error means Django cannot write files to the STATIC_ROOT folder due to OS permissions.

2. Step 2: Fix permissions

   Changing the folder permissions to allow write access for the user running the command resolves this issue.

3. Final Answer:

   Change permissions of the STATIC_ROOT folder to allow write access -> Option B

4. Quick Check:

   Fix permissions to allow writing [OK]

Hint: Fix folder permissions to allow writing [OK]

Common Mistakes:

• Removing STATIC_ROOT disables static collection
• Running collectstatic without fixing permissions
• Deleting static files unnecessarily

5. You want to deploy your Django project to production. Your settings.py has:

STATIC_URL = '/static/'
STATIC_ROOT = '/var/www/example.com/static/'
STATICFILES_DIRS = ['/home/user/project/assets']

After running collectstatic, you notice some static files are missing from /var/www/example.com/static/. What could be a reason and how to fix it?

hard

A. Static files are not copied if DEBUG is True; set DEBUG to False

B. You forgot to set STATIC_URL to the correct path

C. You need to run python manage.py migrate before collectstatic

D. Some static files are inside app folders but not declared in STATICFILES_DIRS; add app static folders or check AppConfig

Solution

1. Step 1: Understand where static files come from

   Django collects static files from app static folders and STATICFILES_DIRS. If files are missing, they might be in app folders not properly recognized.

2. Step 2: Fix by ensuring app static folders are included

   Check that apps have static folders and are correctly configured. Adding missing folders to STATICFILES_DIRS or verifying app configs helps.

3. Final Answer:

   Some static files are inside app folders but not declared in STATICFILES_DIRS; add app static folders or check AppConfig -> Option D

4. Quick Check:

   Missing files often mean missing source folders [OK]

Hint: Check all static source folders are included [OK]

Common Mistakes:

• Thinking STATIC_URL affects file copying
• Running migrate instead of collectstatic
• Assuming DEBUG controls static file copying