Skip to content
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

Update configuration.md #2067

Merged
merged 3 commits into from
Jun 4, 2018
Merged

Update configuration.md #2067

merged 3 commits into from
Jun 4, 2018

Conversation

neeta-wagento
Copy link
Contributor

This PR is a: Typo Error and remove extra will occurance

  • New topic
  • Content fix or rewrite
  • Bug fix or improvement

Summary

When this pull request is merged, it will...

Additional information

@magento-engcom-team magento-engcom-team added Partner: Wagento PR created by Wagento partner partners-contribution PR created by Magento partner labels Jun 4, 2018
@@ -53,7 +53,7 @@ To improve the storefront responsiveness of your Magento instance, go to the Adm
| Javascript Settings | Enable JavaScript Bundling | Yes |
| Template Settings | Minify HTML | Yes |

When you activate the **Enable Javascript Bundling** option, you allow Magento to merge all JS resources into one or a set of bundles that are loaded in storefront pages. Bundling JS results in fewer requests to the server, which improves page performance. It also helps the browser cache JS resources on the first call and reuse it for all further browsing. This option also brings lazy evaluation, as all JS is loaded as text. It initiates analysis and evaluation of code only after specific actions are triggered on the page. However, this setting is not recommended for stores where the first page load time is extremely critical, because all JS content will will be loaded on the first call.
When you activate the **Enable Javascript Bundling** option, you allow Magento to merge all JS resources into one or a set of bundles that are loaded in storefront pages. Bundling JS results in fewer requests to the server, which improves page performance. It also helps the browser cache JS resources on the first call and reuses it for all further browsing. This option also brings lazy evaluation, as all JS is loaded as text. It initiates analysis and evaluation of code only after specific actions are triggered on the page. However, this setting is not recommended for stores where the first page load time is extremely critical, because all JS content will be loaded on the first call.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It also helps the browser cache JS resources on the first call and reuses it reuse them for all further browsing.

@jeff-matthews jeff-matthews self-assigned this Jun 4, 2018
@jeff-matthews jeff-matthews added the Editorial Typo and grammar fixes or minor rewrites to correct inaccuracies label Jun 4, 2018
@jeff-matthews jeff-matthews merged commit f328429 into magento:develop Jun 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Editorial Typo and grammar fixes or minor rewrites to correct inaccuracies Partner: Wagento PR created by Wagento partner partners-contribution PR created by Magento partner
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants