Django Improvements — Frontend Optimizations (Part 3) | by Esther Vaati | Aug, 2022

Tips to speed up your applications

Photo by Austin Distel on Unsplash

In the last two parts of this series on improving performance in your Django applications, we focused on database and code optimizations. In part 3, we will focus on ways to improve the frontend speed of our Django applications by using the following:

  • Minification
  • Put JavaScript files at the bottom of the page
  • HTTP performance
  • Caching
  • CDN systems

The first step in any site optimization process is to get a benchmark of the speed of your Django website. Google PageSpeed Insights is the right tool to measure website performance. It reveals a website’s health by providing insights into how the website performs on mobile and desktop devices and will give you a performance score based on the following metrics:

  • First contentful paint
  • Time to interactive
  • Speed index
  • Total blocking time
  • Largest contentful paint
  • Cumulative layout shift

Google PageSpeed Insights also gives you recommendations for making your website faster. For example, the image below shows the diagnostics of a site running on Django and how to improve it.

0*r2JJRH 6Os0LOwWS

Once you have this data, you can optimize your website for speed using the methods discussed below.

Static files in Django include CSS, JavaScript files, and images. These files are stored in the static folder in your Django application. Your Django application knows how to search for them by having the following configurations in

STATIC_URL = 'static/'STATIC_ROOT = os.path.join(BASE_DIR, 'static')
os.path.join(BASE_DIR, "templates/static"),

If the static files are too large, your Django application will take more time to load. And this will be frustrating to your customers.

Minification compresses static files by removing unnecessary space, comments, and long variable names and ensures pages take less space and load as fast as possible.

Consider the following CSS file mystyle.css:

Once the above file is minified, it looks like this:


The original file takes seven lines and contains additional white space, while the minified version takes only two lines.

Minification of JavaScript files also works the same as CSS files. For example, consider the following code from Django documentation which obtains a token in an AJAX POST request.

Once minified, it looks like this:

Django Compressor is used to minify CSS and JavaScript files in Django templates. It works by combining and minifying the files into a single cached file.

To use the Django compressor, the first step is to install it via pip:

pip install django_compressor

Once installed, add it to the list of installed apps in


Next, add the Django compressor’s configurations in the file.

Add static STATICFILES_FINDERS as shown below:




Lastly, add the load compress tag in the template files which need to be compressed. For example, to compress CSS files, do the following:

{% load compress %}
{% compress css %}
<link rel="stylesheet" href="/static/css/main.css" type="text/css" charset="utf-8">
{% endcompress %}

For JavaScript files, use the compress js tag like this:

{% load compress %}
{% compress js %}
<script src="/static/js/main.js" type="text/javascript" charset="utf-8"></script>
{% endcompress %}

django-compressor will compress all the CSS and JS files after running the Python compress command and store them in a cached file. The compressor will also change the template file to reference the cached file, which will now look like this:

<script src="/static/CACHE/js/main.js"  type="text/javascript"  charset="utf-8"></script>

Another way to increase page performance is to place JavaScript scripts at the bottom of the page. The content will load first, especially on slow connections, and users won’t have to wait.

Large images on your site consume lots of bandwidth and increase load time. Image optimization involves making images an optimal size and dimensions without affecting the image quality, so they load faster and make your Django application faster.

Sometimes you have no control over images’ size and dimensions submitted by users, primarily if your application supports image uploads; these images need to be optimized. An excellent way to compress images is by using the Pillow library. Pillow can convert images to the same format and compress them adequately before being saved in your application.

Here is how to compress an image using the Pillow library before an image is saved:

Page redirects is a process where the page requested is redirected to another resource for loading; instead of the page performing a request to a single page, it performs multiple requests. Page redirects result in additional time to load a page, hence sluggish sites.

Django provides the Django Gzip middleware, which you can use to compress content and make it smaller. To enable this middleware in your Django application, add it to the list of middleware in as shown below:

“django.middleware.gzip.GZipMiddleware “

Gzip middleware should be used with caution because it is susceptible to attacks.

Cached files are served from a cache, which means that when a user submits a request, it first checks in the cache, and if the page is present in the cache, it is served from the cache. If the requested page is not in the cache, it is first fetched, cached for future use, and served to the user.

Django’s default caching backend is LocMemCache and is set up by adding it as a backend in the file.

'default': {
'BACKEND': 'django.core.cache.backends.locmem.LocMemCache',
'LOCATION': 'unique-snowflake',

LocMemCache is, however, unsuitable for production because it’s not memory efficient.

Django supports caching in views. Suppose you have a view that serves a URL that doesn’t change often. It makes sense to cache it to avoid retrieving the page for every user who requests it. Caching in Django views is done by applying the @cache_page decorator on the view, as shown below:

from django.views.decorators.cache import cache_page@cache_page(60*60*24)
def index_view(request):

60x60x24 means the view will be cached for 24 hours.

The URL for the home_view above looks like this:

urlpatterns = [
path('app/index', index_view),

When the URL /app/index/ is requested, it will be cached, and subsequent requests will use the cache.

Template caching is another way of improving page speeds.

Template caching is possible for content that changes often. Django provides fragment caching, ensuring that only certain parts of a template are cached and the rest of the dynamic content is left uncached. To add this setting to your Django project, you need to put the cache tag at the top of your template and specify the content block you wish to cache as follows:

{% load cache%}{% cache header %}
<title class = "title">{{object.title}}</title>
{% end cache%}

This setting above will create a cache fragment with the name “header” and cache it forever. If you only need to cache the template for a certain period, specify the cache timeout in seconds as shown below:

{% load cache %}{% cache 500 header %}
<!-- …….
Header content here -->

{% end cache%}

CDN services are an excellent way to increase the page load speeds of your Django application. CDN (Content delivery network ) is a set of servers spread across different locations to serve content and ensure a quick delivery. For example, suppose your Django application is hosted by a server in the USA, and users are located worldwide.

With a CDN, the client in China will be connected to the CDN server closest to their geographical location and one which offers the least latency. CDN systems perform well by using a load balancer, ensuring that client requests are forwarded to the closest CDN servers, providing maximum efficiency. A CDN works by having cached copies of the static files in different CDN locations, making it faster for users to access the content.

As shown in the “Minification” section above, Django stores your static files in one folder specified by the STATIC_ROOT setting.”

When you deploy your Django application, having your static files on the same server as your Django application is not optimal. With a CDN, it does not need to fetch them from far away but from a nearby location hence faster responses. Some of the most popular CDN services you can use in your Django application include Akamai, Amazon CloudFront, Cloudflare, Fastly, and Google Cloud CDN, among others.

Django has the django-storages package, which can store and server static files from a CDN server. Django storages supports popular backends such as Amazon S3, Google Cloud, Digital ocean, and more.

The first step is to install django-storages via pip:

pip install django-storages

Next, add storages to the list of installed apps in


If you decide to use Amazon S3, you must create an account. Amazon S3 offers file storage, and data is stored in buckets.

To upload your static files to an S3 bucket, add the following in your

STATICFILES_STORAGE = 'storages.backends.s3boto3.S3StaticStorage'

To use Amazon S3 and its cloud front service as a CDN, create a bucket on AWS S3 and set the AWS credentials in your Django project in like so:

AWS_ACCESS_KEY_ID = 'your-access-key'
AWS_SECRET_ACCESS_KEY = 'your-secret-key'

Lastly, set the STATIC URL to serve static files from the CDN custom domain.


Many factors contribute to the overall performance of your Django application, such as database, middleware, and views. Sentry’s code-level application performance monitoring allows you to spot slow-performing HTTP operations and the time taken by every page transaction.

To follow along, set up your Sentry account and create a Django project as shown below:

0* fLLU6GfyVv1dfi5

The next step is to install Sentry’s SDK via pip:

pip install --upgrade sentry-sdk

Next, open and add the Sentry SDK as shown below:

Navigate to the Sentry dashboard (Performance > Frontend) and “Frontend”:

0*zFZt3W Y3AmakTMQ

Navigate to the bottom to view transaction metrics. You should see something like this:

0*19etv8ABulf iyfp

From the data above, TPM shows the average number of transactions per minute. Other metrics include:

  • p50: 50% of transactions are above the time set on the p50 threshold. For example, if the P50 threshold is set to 10 milliseconds, then 50% of transactions exceeded that threshold, and it takes longer than ten milliseconds.
  • p75: 25% of transactions are above the time set on the p75 threshold
  • p95: 5% of transactions are above the time set on the p95 threshold

When you expand each transaction, you have more details about how each part of a request affects the overall response time:

The diagram above gives an overview of how each request performs and what causes it to be slow, allowing you to fix it quickly. From the configurations, we set a trace parameter (traces_sample_rate=1.0) which sends every transaction to Sentry (you should choose a sample rate that you’re comfortable with — Sentry’s docs provide details on how to decide); this enables you to gain insights into what part of your Django application is negatively impacting its overall performance.

This tutorial has covered frontend optimizations you can consider for speeding up your Django application. We’ll wrap this series up in part 4, where we’ll focus on caching optimizations.

News Credit

%d bloggers like this: