joaopeixoto
posted this
03 December 2022
nicepage.css is to big!
This file should be the size that reflects the website needs. not ALL css that can be used.
It's a lazzy work from nicepage and it's not that hard to make it right. while building the export file, just perform a check the css is used in all the website files and add the css requests while performing that check to a new .css file. that file should be the exported one. not the generic all in one.
--------------()
This is inserted with google analytics in the begining of the code. it should be added in the bottom of the file to improve website download time. Also with cookie policy this should be only enabled after the confirm button.
Fonts!
PageSeed Insights tells me that I can save more than half a second using this:
font improvement
How do I "Add the &display=swap parameter to the end of your Google Fonts URL:"
How do I show my text BEFORE google fonts are downloaded using nicepage?
This should be really easy to do to nicepage.
Async:
problem with chained requests
How can I insert Async critical requests in Nicepage?
Or improve this chanied requests using Nicepage if Async is not possible? (that should be)
Stop adding stuff. Improve what you have already (that is great, thats why I bought Nicepage).
I'm from C Language, so I'm used to optimize code. It makes me sad seeing a great product beeing lazzy in some trivial aspects.
Ofc this is not what the client will see, only what the programmer will. This could be a seller point for your product, because your selling this also to programmers that likes to give a better experience to their clients and proud of the work done.
Right now I've more that +96 score in 3 of my sites, and I will only be happy when I get 100 ;)
1. nicepage.css is to big!
This file should be the size that reflects the website needs. not ALL css that can be used.
It's a lazzy work from nicepage and it's not that hard to make it right. while building the export file, just perform a check the css is used in all the website files and add the css requests while performing that check to a new .css file. that file should be the exported one. not the generic all in one.
2. --------------()
This is inserted with google analytics in the begining of the code. it should be added in the bottom of the file to improve website download time. Also with cookie policy this should be only enabled after the confirm button.
3. Fonts!
PageSeed Insights tells me that I can save more than half a second using this:
[font improvement][1]
How do I "Add the &display=swap parameter to the end of your Google Fonts URL:"
How do I show my text BEFORE google fonts are downloaded using nicepage?
This should be really easy to do to nicepage.
4. Async:
[problem with chained requests][2]
How can I insert Async critical requests in Nicepage?
Or improve this chanied requests using Nicepage if Async is not possible? (that should be)
[1]: https://developer.chrome.com/docs/lighthouse/performance/font-display/?utm_source=lighthouse&utm_medium=lr
[2]: https://developer.chrome.com/docs/lighthouse/performance/critical-request-chains/?utm_source=lighthouse&utm_medium=lr
Stop adding stuff. Improve what you have already (that is great, thats why I bought Nicepage).
I'm from C Language, so I'm used to optimize code. It makes me sad seeing a great product beeing lazzy in some trivial aspects.
Ofc this is not what the client will see, only what the programmer will. This could be a seller point for your product, because your selling this also to programmers that likes to give a better experience to their clients and proud of the work done.
Right now I've more that +96 score in 3 of my sites, and I will only be happy when I get 100 ;)
Last edited 03 December 2022 by joaopeixoto
Vote to pay developers attention to this features or issue.
