-
Notifications
You must be signed in to change notification settings - Fork 12
Editing Pages: Performance Improvement #209
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Editing Pages: Performance Improvement #209
Conversation
✅ Deploy Preview for axelerant-engg-handbook ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
| Compressed CSS/JS refers to the technique of reducing the size and optimizing the performance of CSS/JavaScript files. A website can load more quickly, use less bandwidth, and put less strain on the server by compressing its CSS and JS. By minimizing the size of the CSS/JS files and the amount of HTTP requests, compressed CSS/JS helps make a website faster and more effective. | ||
|
|
||
| Furthermore, Compressed CSS/JS can make the CSS/JS code more challenging for others to interpret and edit, which can be helpful for defending intellectual property. It is advised to preserve a copy of the original CSS/JS files for development since compressed CSS/JS might also make debugging more difficult. | ||
| Compressed CSS and JavaScript refer to techniques that reduce the size of these files, optimizing website performance. Compression leads to faster load times, reduced bandwidth usage, and less server strain by minimizing file size and HTTP requests. Additionally, compressed code can be more challenging to interpret, which may protect intellectual property. However, it’s advisable to keep original files for development, as compressed versions can complicate debugging. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Additionally, compressed code can be more challenging to interpret, which may protect intellectual property.
This is not really a benefit because these can be easily reversed. Let's drop this.
However, it’s advisable to keep original files for development, as compressed versions can complicate debugging.
Let's talk about source maps. Just a mention; no need to go in-depth.
| Compressed CSS/JavaScript refer to techniques that reduce the size of CSS and JavaScript files, optimizing website performance. Compression leads to faster load times, reduced bandwidth usage, and less server strain by minimizing file size and HTTP requests. | ||
|
|
||
| Furthermore, Compressed CSS/JS can make the CSS/JS code more challenging for others to interpret and edit, which can be helpful for defending intellectual property. It is advised to preserve a copy of the original CSS/JS files for development since compressed CSS/JS might also make debugging more difficult. | ||
| Additionally, using source maps allows developers to retain original, uncompressed code during development, making debugging more manageable even when deploying compressed versions to production. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
using source maps allows developers to retain original, uncompressed code during development
this is for debugging, not development. Developers have access to the actual source code during development in any case. Please read up on source maps and then rephrase this entire sentence.
No description provided.