Speed Optimizer

1 · Installation

Two ways to install — via Composer or by uploading the app folder. Both end with the same Magento CLI steps.

System requirements

• Magento 2.3.x / 2.4.x installed and working
• PHP, MySQL/MariaDB and web server meeting Magento 2 system requirements
• SSH access to run Magento CLI commands

Method 1 — Install via Composer (recommended)

1. Open a terminal in your Magento 2 root directory and require the package:

   composer require magepow/speedoptimizer

2. Run the Magento setup upgrade:

   php bin/magento setup:upgrade

3. Deploy static content (production mode):

   php bin/magento setup:static-content:deploy -f

4. Flush the cache:

   php bin/magento cache:flush

Method 2 — Manual install (upload app folder)

1. Download the extension package and unzip it. Upload the app folder to your Magento 2 root so it merges with the existing app directory.
2. Run the following commands from the Magento 2 root:

   php bin/magento setup:upgrade
   php bin/magento setup:static-content:deploy -f
   php bin/magento cache:flush

3. Log out of the Admin panel and log back in to refresh access permissions, then clear the cache under System > Cache Management.

2 · Configuration & Usage

All settings live in the Magento Admin panel. Screenshots below match the default Admin theme.

1. General Configuration

Enable/Disable module

To Enable/DisableMagepow Speed Optimizer Extension: Go to Admin Panel > Stores > Settings > Configuration > Magepow > Speed Optimizer. Then, select Yes to Enable module/ No to Disable the module.

General Configuration

• Preloading Body: Set Yes to use Preloading body site. If not, set No.
• Loading Body placeholder: Upload icon/image to placeholder when loaing wesbite body. After set yes and upload icon/image.

• Preloading Images: Set Yes to use preloading images.
• Exclude Image class: Enter the class of images that you don't want to be applied lazy load such as top banner, header...
• Loading Image placehoder: Upload the icon/image to display preloading images. For example, after set Preloading Images to Yes and Upload Icon/Image, we will have:

• Placeholder images: Set Yes to create placeholder for all loading images. This case will help you keep the website layout (frame) while the images have not loaded completely.
• Regex Block: Enter the place that you want to use lazy load from that place to footer by using id or class of block. For example, this will be good for people want to keep the first content such as slider, header... not effected by Lazy load.
• Lazyload Images Response Ajax: Set Yes to apply Lazy load for Response Ajax. If not, set No.
• Minify Html: Set Yes to minify HTML files and Javascript files.
• Defer Javascripts: Move JavaScript to page bottom, a script that will not run until after the page has loaded.
• Scripts and Style Sheets: This field is for who want to customize the lazy load, use particular scripts or style.
• After config you need login ssh after go to root magento and run 10 commands line below:

		php bin/magento deploy:mode:set production
		php bin/magento config:set dev/css/minify_files 1
		php bin/magento config:set dev/css/merge_css_files 1
		php bin/magento config:set dev/js/minify_files 1
		php bin/magento config:set dev/js/merge_files 0
		php bin/magento config:set dev/js/enable_js_bundling 1
		rm -rf pub/static/frontend/* && rm -rf var/view_preprocessed
		php bin/magento setup:static-content:deploy -f
		php bin/magento cache:enable
		php bin/magento cache:flush
	

2. Result

Results after using Speed Optimizer Extension

1.1 Speed Test on gtmetrix.com

2.2 Speed Test on Google PageSpeed Insights

3 · Support

Found a bug or need customization? Contact us — we usually reply within 24–48 hours.

Need help?

• Ticket support: support.magepow.com — we reply within 24–48 hours (usually much faster). Please include your Magento version, extension version and screenshots/error messages.
• Documentation: docs.magepow.com
• Video tutorials: Magepow on YouTube

Bug reports

If you find a bug, please report it via the ticket system with steps to reproduce, expected vs. actual behavior, and any relevant logs (var/log/system.log, var/log/exception.log).