cody.flanagan
posted this
18 November 2022
Oversized images are usually the biggest problem in terms of page load speed.
Typically, the 2nd biggest problem is "Code Bloat". Unnecessarily heavy CSS files.
As you can see when publishing a site, there is a CSS file for every single page rather than 1 optimized CSS file for all pages. What this means in terms of load speed (which is increasingly important as a Google ranking factor) is that you must request a new CSS file for every single page.
Many of these CSS files have the exact same CSS as in the previous page but because of NP architecture, that CSS must be requested and redownloaded again even if that CSS has already been loaded from a different file. Not efficient.
If you dig into Page Speed Insights, it will tell you how to use the chrome inspector to see the CSS. Inspector will ALSO show you what CSS is unused on each page, requiring users to download an unnecessarily large file.
While it is possible to manually delete unused CSS, the next time you publish the page, it also republishes the original "bloated" CSS.
SUGGESTION!
For those of us who want fast-loading pages and are willing to go to these lengths, it would be an excellent idea if NP would allow me to "lock" the CSS pages so it doesn't overwrite when publishing changes.
The only other possibility is to manually replace bloated CSS with streamlined files. Of course, you must remember that a single change to any page will require you to insure your streamlined CSS files have those changes. It's a management nightmare.
For those of you interested in this, I just found a site called Unused-CSS.com that will help you determine what CSS you can strip out - Manually. https://unused-css.com/dashboard
Ideally, Nicepage would be able to do this.. or at the very least have one primary CSS file that contains CSS for all pages and would remove redundant CSS entries.
Final Word
You may find it interesting to note that for the FIRST TIME EVER, Google analytics now has reports specifically about core web vitals - most important of these is page speed. What this means is that we now have a new ranking factor to consider other than on-page and off-page SEO.
If you'd like to know more about this (and you absolutely should), check out my blog post on this topic for a high level overview. https://irazor.io/blog/the-importance-of-page-speed.html
Oversized images are usually the biggest problem in terms of page load speed.
Typically, the 2nd biggest problem is "Code Bloat". Unnecessarily heavy CSS files.
As you can see when publishing a site, there is a CSS file for every single page rather than 1 optimized CSS file for all pages. What this means in terms of load speed (which is increasingly important as a Google ranking factor) is that you must request a new CSS file for every single page.
Many of these CSS files have the exact same CSS as in the previous page but because of NP architecture, that CSS must be requested and redownloaded again even if that CSS has already been loaded from a different file. Not efficient.
If you dig into Page Speed Insights, it will tell you how to use the chrome inspector to see the CSS. Inspector will ALSO show you what CSS is unused on each page, requiring users to download an unnecessarily large file.
While it is possible to manually delete unused CSS, the next time you publish the page, it also republishes the original "bloated" CSS.
**SUGGESTION!**
For those of us who want fast-loading pages and are willing to go to these lengths, it would be an excellent idea if NP would allow me to "lock" the CSS pages so it doesn't overwrite when publishing changes.
The only other possibility is to manually replace bloated CSS with streamlined files. Of course, you must remember that a single change to any page will require you to insure your streamlined CSS files have those changes. It's a management nightmare.
For those of you interested in this, I just found a site called Unused-CSS.com that will help you determine what CSS you can strip out - Manually. https://unused-css.com/dashboard
Ideally, Nicepage would be able to do this.. or at the very least have one primary CSS file that contains CSS for all pages and would remove redundant CSS entries.
**Final Word**
You may find it interesting to note that for the FIRST TIME EVER, Google analytics now has reports specifically about core web vitals - most important of these is page speed. What this means is that we now have a new ranking factor to consider other than on-page and off-page SEO.
If you'd like to know more about this (and you absolutely should), check out my blog post on this topic for a high level overview. https://irazor.io/blog/the-importance-of-page-speed.html
