# 16 minute build using hugo + lunrjs

**URL:** <https://answers.netlify.com/t/16-minute-build-using-hugo-lunrjs/2769>\
**Category:** Support\
**Tags:** building, performance, hugo\
**Created:** [August 15, 2019, 7:24pm UTC](https://answers.netlify.com/t/16-minute-build-using-hugo-lunrjs/2769 "2019-08-15T19:24:43Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jacebenson](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/jacebenson/32/1254_2.png) [@jacebenson](https://answers.netlify.com/u/jacebenson)\
**Post date:** [August 15, 2019, 7:24pm UTC](https://answers.netlify.com/t/16-minute-build-using-hugo-lunrjs/2769/1 "2019-08-15T19:24:43Z")

</div>

I’m trying to keep some documentation on a system I work on. However, I fear the build time might be too long. I looked at the topics here about doing things to take advantage of the cdn. However I’m not even sure where to start to lower this time.

Build link: [Netlify App](https://app.netlify.com/sites/determined-curran-f6ceac/deploys/5d55ab02ca99670008850128)

---

<div class="post-metadata">

**Author:** ![fool](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/fool/32/37_2.png) [@fool](https://answers.netlify.com/u/fool)\
**Post date:** [August 18, 2019, 2:44am UTC](https://answers.netlify.com/t/16-minute-build-using-hugo-lunrjs/2769/2 "2019-08-18T02:44:58Z")

</div>

Howdy! I think this is the main article you need to read and act on:

> [@\[Support Guide\] Making the most of Netlify's CDN cache](https://answers.netlify.com/t/common-issue-making-the-most-of-netlifys-cdn-cache/127):
>
> Last reviewed by Netlify Support - August, 2023 Our CDN derives much of its efficiency from files whose checksums don’t change between deploys. For instance, in a blog, you usually write or update one article in one file, while the rest of the content remains unchanged. In this typical use case, we don’t need to re-upload and re-process these files, since our CDN already has them stored - no checksums have changed except the one file. This also means that your visitors’ browsers don’t need to …

It is about the size of your site, but really, the size of what changes with each build is what matters most.

LEt me know if it’s not obvious after reading that how to tell what changes. Fixing that thing could be easier or harder, but figuring it out is step 1 🙂

---

<div class="post-metadata">

**Author:** ![jacebenson](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/jacebenson/32/1254_2.png) [@jacebenson](https://answers.netlify.com/u/jacebenson)\
**Post date:** [August 19, 2019, 1:53am UTC](https://answers.netlify.com/t/16-minute-build-using-hugo-lunrjs/2769/3 "2019-08-19T01:53:16Z")

</div>

I kept thinking about it on and off. Each page gets teh whole “index” if you will of the links. I’ll have to rethink how that happens as, that is making the pages change each time.

---

<div class="post-metadata">

**Author:** ![jacebenson](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/jacebenson/32/1254_2.png) [@jacebenson](https://answers.netlify.com/u/jacebenson)\
**Post date:** [August 20, 2019, 9:36pm UTC](https://answers.netlify.com/t/16-minute-build-using-hugo-lunrjs/2769/4 "2019-08-20T21:36:44Z")

</div>

So I rewrote how the “sidebar” is built.  
Before every page had a link to every other page.  
Also every page had a “modified” meta tag of when it was built.  
Those could be handy but not at the cost of netlify re-uploading each file uniquely every time.

 ![ScreenShot-2019-Aug-20-435-PM](https://global.discourse-cdn.com/netlify/original/2X/5/5f3362525e8ea6acbbe6e994b68996e0f57d5533.png)