Skip to content

[AssetMapper] Shortening "Optimizing Performance" #19625

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Mar 4, 2024
Merged

[AssetMapper] Shortening "Optimizing Performance" #19625

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions frontend/asset_mapper.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -635,8 +635,7 @@ which will automatically do most of these things for you:
- **Compress your assets**: Your web server should compress (e.g. using gzip)
your assets (JavaScript, CSS, images) before sending them to the browser. This
is automatically enabled in Caddy and can be activated in Nginx and Apache.
Or, proxy your site through a service like Cloudflare, which will
automatically compress your assets for you. In Cloudflare, you can also
In Cloudflare, you can also
enable `auto minify`_ to further compress your assets (e.g. removing
whitespace and comments from JavaScript and CSS files).

Expand All @@ -658,7 +657,7 @@ Performance: Understanding Preloading

Automatic preloading of JavaScript files was introduced in Symfony 6.4.

One issue that LightHouse may report is:
One issue that Lighthouse may report is:

Avoid Chaining Critical Requests

Expand Down