The world of static site generators has come a long way, but what sets PRSS apart from others is its unique configuration-free and managed build process.
We've been working tirelessly to refine the build process over the years, ensuring that your site loads optimally every time. In our pursuit for perfection, we experimented with loading theme resources via Content Delivery Networks (CDNs) like JsDelivr and Unpkg to speed up load times.
While this approach is successful in some aspects, we encountered issues with responsiveness using Unpkg. To address these concerns, we've made significant changes to the build process. Our latest update now loads theme assets directly within the editor and saves them as local site assets.
This change has several benefits:
- No need to call up CDNs for theme CSS and JS
- Improved load times and responsiveness
- A more streamlined and efficient build process
The result is a faster, more reliable, and user-friendly experience for creators like you.
What resources are loaded in a PRSS site?
Here's some key components that are present in a built PRSS site:
- Google Fonts
- PRSS UI assets. These are assets common to all themes.
- client.js (client-side JS for PRSS blocks. Blocks are SSR rendered so client.js is needed for things like opening an accordion or a gallery item)
- blocks.css (Styles for PRSS blocks)
- Theme assets
- theme.css
- client.js (themes are also SSR rendered, so client.js is used for things like opening a dropdown or handling dark mode),
- Site assets. These are defined if you've set global JS or CSS in your Site Settings.
- index.css
- index.js
- Inline styles or JS
- These are the scripts or styles the user has set at the page level
As you can see, there's quite a bit of assets. But this is the sweet spot to provide a fast loading experience (~1s) that is not too barebones.
For added insights into the loading of your site, we recommend GTMetrics. You can check out our report for this post here.
