It takes too long to build and deploy my GitHub Actions. How can I speed it up?

Having large artifact file sizes can result in long building and deployment times with GitHub Actions. We recommend the methods below to reduce the file sizes:

Migrate static resource files to KurocoFiles

KurocoFiles is a function that enables you to upload and update files from the admin panel. Migrating static resource files (such as images) to KurocoFiles can help reduce the total size of your source files. Also, KurocoFiles uploads are cached in our CDN and can be served at higher speeds.

More information:

• User guide: Files
• Reference: Dynamic conversion of images

Reduce the HTML file size

For statically generated sites, you can reduce the artifact file sizes by reducing the HTML file size.

Import SVG sprites as files

If icons are displayed using SVG sprites, with the SVG code contained in the HTML source, this code will be included in all the pages generated during the build process, causing the page sizes to become bloated. You can reduce the HTML file size by loading the SVG code as svg-sprite.svg. For example:

<svg>
    <use xlink:href="/assets/svg/sprite.svg#icon-foo"></use>
</svg>

Display page contents asynchronously

For static websites, as the total number of pages on the site increases, so does the number of files generated during the build. If the subsequent pages after a list page are static, you can reduce the number of pages generated by displaying them asynchronously using Axios.