<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: daeun.eth</title>
    <description>The latest articles on DEV Community by daeun.eth (@daa3230).</description>
    <link>https://dev.to/daa3230</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3356122%2F68aed845-ed71-42ab-9b55-577e76397cfb.jpg</url>
      <title>DEV Community: daeun.eth</title>
      <link>https://dev.to/daa3230</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/daa3230"/>
    <language>en</language>
    <item>
      <title>How can I make my frontend run quicker</title>
      <dc:creator>daeun.eth</dc:creator>
      <pubDate>Sun, 27 Jul 2025 16:33:40 +0000</pubDate>
      <link>https://dev.to/daa3230/how-can-i-make-my-frontend-runs-quicker-6dh</link>
      <guid>https://dev.to/daa3230/how-can-i-make-my-frontend-runs-quicker-6dh</guid>
      <description>&lt;p&gt;When we try to improve user experience for a website, good design and nice flow definitely matter. &lt;/p&gt;

&lt;p&gt;But what else should be also taken into account? &lt;br&gt;
Yes! It's performance!&lt;/p&gt;

&lt;p&gt;Even if we use the awarded design for our website, if any actions on the web take 10 seconds to load not many people would use the website. &lt;/p&gt;

&lt;p&gt;Then let's discuss how to improve web performance.&lt;br&gt;
The followings are what helped me (and my team) to improve performance on our web app. &lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Use code bundler, use code bundler wisely!&lt;br&gt;
Now days, when you create an app with framework like next or nuxt, bundlers are also set-up as default. But wait a second, what is bundler? To use it smart put in small research about tools you are using.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Lazy loading&lt;br&gt;
This is very simple and nice way to improve initial loading time.&lt;br&gt;
When you first load the page, we load all related code from server. &lt;br&gt;
What about the components that wouldn't be rendered now? Do we also load them? Normally yes, unless you are using &lt;code&gt;lazy loading&lt;/code&gt;.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;API call bundling / caching&lt;br&gt;
Making multiple API calls often is worse than making a single bundled api calls due to waiting time, server loads, less http request overhead. And having proper &lt;code&gt;caching&lt;/code&gt; logic also helps to make &lt;code&gt;less&lt;/code&gt; requests to server.&lt;br&gt;
But we need to make sure these aren't always THE ANSWER.&lt;br&gt;
Maybe we want to get the result for &lt;code&gt;main api call&lt;/code&gt; to render this data to user first!&lt;br&gt;
Accidentally showing stale data to user could be fatal error!&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Image Compression&lt;br&gt;
Using compressed images on the right places can help improving data fetching speed.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;load low-quality images for small thumbnails&lt;/li&gt;
&lt;li&gt;compress before image upload (or before returning image from BE)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Then happy coding everyone! &lt;br&gt;
If you want to learn more/detailed knowledge for the topic, I also recommend to read: &lt;a href="https://www.freecodecamp.org/news/the-front-end-performance-optimization-handbook/" rel="noopener noreferrer"&gt;https://www.freecodecamp.org/news/the-front-end-performance-optimization-handbook/&lt;/a&gt; and apply it to your very own projects!&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
