8 best practices that will improve your front-end efficiency

front-end efficiency
It is obvious that web applications are growing in popularity. What can be done so  everyone can fully enjoy their benefits without any damage to website performance and accessibility? It is actually a matter of just a few improvements.
In web apps, data is exchanged via API and its presentation and editing is done browser-side. User experience is smoother  due to lack of pages overloading and better interaction with particular elements, e.g. via animated redirections and clicks.
Greater benefits unfortunately come with greater hardware and software requirements, however. How can front-end performance be improved? Here’s 8 best practices we adhere to at Unity Group:

Front-end efficiency tip #1: Choose the right browser

If you would like to use new web technologies, you should first decide which browsers you want to support. According to GS Statscounter findings on the most frequently used browsers, Internet Explorer is steadily losing popularity, especially versions older than 11. Until recently, older versions of IE were much more popular among users, which prevented the implementation of new solutions, or, at the very least, required using additional (dedicated) styles and scripts which had a detrimental effect on performance.

Currently, the most popular browsers are Google Chrome and Mozilla Firefox, both of which come with automatic updates. New browsers support new standards, enabling them to function faster and more efficiently.

Front-end efficiency tip #2: Load images in appropriate sizes

Pictures used in dedicated applications have the same resolution in which they will be displayed in HTML, which is not really problematic. Problems arise when we take the RWD approach to web design. In such cases, it is necessary to have a few different resolutions handy, depending on the site’s breakpoints, and automatically load only the image that fits best to the current size of the browser window.

Front-end efficiency tip #3: Load CSS and JS in the right order

Delays in loading CSS slow down rendering, which makes for a terrible user experience. To avoid that, CSS files should be loaded first, therefore it is best to add them in the website’s header (<head/>). It is a good idea to place CSS files in the same domain as the website, which removes the waiting times involved with DNS searching. JavaScript files, on the other hand, should be moved to the very end of the page and placed just before the <body/> tag. Scripts are not loaded asynchronously, if they are placed at the end, the user will think that the page loaded faster.

Front-end efficiency tip #4: Reduce requests to a minimum

It is common practice to use many JS plug-ins, as well as several style files. In order to reduce the amount of request sent to the server, a good solution is to combine such files. To that end, you can use ready-made tools such as Grunt, Gulp or WebPack, which can help you quickly process combined files by e.g. minimising them. Therefore, you only need one tool to simultaneously reduce the number of requests and the size of CSS and JS files. If the site also contains many icons, it is also a good idea to prepare their font, svg or at least CSS sprite versions, which can also be achieved using the above-mentioned tools.

Front-end efficiency tip #5: Careful with linking and redirections

Correct linking to resources is another important element which influences site load times. When attaching a file, ensure that the file is free of errors and that opening it does not redirect you to another domain. Such redirections extend file load times, which in turn makes the entire site slower. The same applies to linking to files which do not exist. The browser requests the file and waits for a response whenever the site is opened, even if the resource in question was not saved.

Front-end efficiency tip #6: Use cookies responsibly

If you want to store information, remember that it is a good idea to reduce the amount and size of cookies as much as possible, as they are sent to the server inside headers. For browser-side data storage, it is a good idea to use Local Storage, in which you can store much more information than in cookie files.

Front-end efficiency tip #7: Consider server-side improvements

To speed up the load times and save on data transfer, the first thing that should be done is to turn on lossless GZIP compression on your server. You can also move your static files to CDN, which will reduce the load on the main server and prevent unnecessary cookies from being sent in headers, which will also have a positive effect on the load times. Implementing HTTP/2 is also something that is worth considering.

Front-end efficiency tip #8: Pay attention to performance tests

There are numerous online tools which can help you to improve performance, provide a summary of information about the website’s elements or display statistics. The most popular tools of this kind include Page Speed, Y-Slow and Web Page Test. In addition to external online applications, you can also make use of Chrome’s DevTools. The tools allow for much quicker and easier website performance testing.

Web application performance is key – it is website speed and loading times that make users want to continue browsing. Thanks to new web technologies, available tools and compatibility with new browsers, we are able to build simple, functional and, most importantly, fast websites which can be run on many devices.


Karol is a Webmaster at Unity Group. In the web industry since 2009, he’s participated in development of the biggest online stores and B2B solutions in Poland. He continually strives to expand his knowledge of modern web design & development, he’s also an avid consumer of tech world news.


Questions? Don't hesitate to drop us a line - we're here to help.

Fields marked with an * are required