On Nginx servers, Apache .htaccess rules cannot serve HTML cache by themselves. When W3Speedster detects Nginx, it provides a ready-made nginx.conf snippet so cached HTML can be served from the site root.

How to Access

• Open W3Speedster Dashboard → HTML Cache and enable HTML Caching.
• If Nginx is detected, the tab shows a notice with the exact nginx.conf content to create in your WordPress root.
• Include that file in your Nginx server block, for example: include /path/to/site/nginx.conf;
• Test and reload Nginx with nginx -t && nginx -s reload, or use your host panel.
• Open the homepage while logged out so a cache file can be created, then reload the HTML Cache tab to confirm the status.

Status messages

• Nginx cache is working — the homepage response matched the cached HTML file.
• Nginx cache rules found — rules are present, but no homepage cache file exists yet.
• Nginx cache is not serving yet — rules and a cache file exist, but Nginx is still not returning that file. Check the include and reload Nginx.

Notes

• This is the Nginx equivalent of serving HTML cache files through rewrite rules.
• When Ignore query parameters is enabled, Nginx cache rules also ignore the query string for lookups.

The post Nginx Cache Support appeared first on W3Speedster.

When Optimize with AI is enabled, the URL table shows Desktop and Mobile status, the last update time, and actions for each page. Filters and pagination are stored in the page URL, so a refresh keeps the same view.

Functionality:

• Rows Per Page — show 10, 20, 50, or 100 rows at a time.
• Status — filter by All, Queued, In-progress, Optimized, or Not Optimized.
• URL — type part of a URL and click Filter to narrow the list.

Status meanings

• Queued — waiting for the next crawl slot.
• In-progress — critical CSS or cache work is running, including cloud sync.
• Optimized — desktop and mobile work for that URL is complete.
• Not Optimized — the page failed or was marked not optimized on purpose.

How to Access

• Open W3Speedster Dashboard → Optimize with AI.
• Use the filter row above the URL table.

The post Status Filters & Table appeared first on W3Speedster.

Bulk Actions let you update several Optimize with AI URLs at once. Select rows with the checkboxes (or Check all), choose an action, then click Apply.

Available actions

• Re-optimize — clears local HTML cache and critical CSS files for the selected URLs, sets them to Queued, and starts crawling them now (limited by Pages per Minute).
• Queue for next run — clears those files and sets status to Queued without crawling immediately. Pages are picked up on the next Optimize with AI cycle.
• Mark as not optimized — sets status to Not Optimized so W3Speedster stops retrying until you queue or re-optimize them again.

How to Access

• Open W3Speedster Dashboard → Optimize with AI.
• Select one or more rows, choose a bulk action, then click Apply.

Benefits

• Fix failed pages without resetting the whole site.
• Delay heavy crawls when the server is busy.
• Keep the queue accurate instead of waiting on false timeouts.

The post Bulk Actions appeared first on W3Speedster.

Ignore query parameters tells HTML cache to look up pages without the query string. For example, /product/?srsltid=abc and /?utm_source=google can use the same cache files as /product/ and /.

Functionality:

• Applies to HTML cache delivery through .htaccess, PHP/advanced-cache, and Nginx (nginx.conf).
• Overrides Enable caching page with GET parameters while it is on. W3Speedster will not use a separate cache file per query string for lookup.
• On a cache miss, the original query string still reaches WordPress; only the cache path ignores it.
• Off by default. Enabling it does not rewrite existing rules until you save, and it does not flush the HTML cache.
• Not the same as Remove query parameters, which strips version strings such as ?ver= from CSS and JavaScript file URLs for browser and CDN caching.

When to enable

• Tracking parameters such as srsltid, gclid, fbclid, and utm_* that should not create extra HTML cache files.
• Sites that cache pages with GET parameters but want one shared cache for marketing variants of the same URL.

How to Access

• Open W3Speedster Dashboard → HTML Cache.
• Enable Ignore query parameters (under Enable caching page with GET parameters).
• Save changes.

The post Ignore query parameters appeared first on W3Speedster.

Pages per Minute sets how many queued pages Optimize with AI may start crawling in one minute. In the admin UI the field is labeled Pages per Minutes. The maximum value is 20. Use a lower value on smaller servers and a higher value on stronger hosts.

Why We Need It

• Large sites need a steady optimization pace, not an all-at-once burst.
• Too many pages at once can overload the server; too few makes the job take longer than necessary.
• This setting lets you match optimization speed to your hosting capacity.

Problems Without It

• Without a limit, crawls can spike CPU and memory usage.
• Without enough throughput, finishing the full URL list can take much longer.
• Every host is different, so a fixed pace for all sites is not practical.

Solutions with Pages per Minute

• If Pages per Minute is empty, W3Speedster can fall back to the Preload Page Caching per Minute value.
• Set a value from 1 to 20 on the Optimize with AI tab, then click Save.
• Only pages that successfully start crawling move from Queued to In-progress. Remaining pages stay Queued for the next minute.
• Pages already In-progress keep syncing optimization status and are not limited by this setting for status checks.
• If a page stays In-progress for about 60 seconds with no local work started and no cloud job, it returns to Queued automatically.

How to Access

• Open W3Speedster Dashboard → Optimize with AI.
• Set Pages per Minutes (max 20) and click Save.

Benefits

• Protects the server while optimization runs.
• Lets powerful hosts finish large sites faster when you raise the limit.
• Keeps the queue predictable: new crawls start only when a slot is available.

The post Pages Per Minute appeared first on W3Speedster.

Optimize with AI automates the main performance tasks for your site. It crawls your pages, then generates critical CSS, optimizes images, and builds HTML cache so you do not have to manage each step manually.

Why We Need It

• Critical CSS, image optimization, and cache creation take time when done by hand and are easy to miss on some pages.
• Each page can be optimized for its own layout, which keeps performance more consistent across the site.
• When content changes, AI can pick up new or updated pages so optimization stays current.
• Faster pages improve user experience and can support better SEO results.

Problems Without AI Optimization

• Manual runs often skip critical CSS, cache, or image work on some URLs.
• Pages missing from the sitemap, or added later, may stay unoptimized until they are crawled.
• Resetting and regenerating optimizations becomes slow and error-prone without automation.
• Uneven settings across pages lead to uneven performance.

Solutions with Optimize with AI

• Crawling Through Sitemap
  • AI reads the sitemap to find site URLs.
  • URLs are processed in controlled batches so the server is not overloaded.
• Generating Critical CSS
  • Page-specific critical CSS is generated for each URL.
  • Above-the-fold content can render sooner, which improves perceived speed.
• Image Optimization and Cache Creation
  • Images are optimized automatically where those options are enabled.
  • HTML cache files are created so repeat visits load faster.
• Handling Missing URLs
  • If a URL is not in the sitemap, critical CSS can still be created the first time that page is crawled.
• Reset and Rescan
  • Use Reset when you want a clean rebuild.
  • Previous critical CSS is cleared, then the sitemap is scanned again and optimizations are regenerated.
• Automatic Safeguards
  • Optimize with AI depends on related options such as critical CSS, image optimization, and caching.
  • If required options are turned off, Optimize with AI turns itself off so it does not run in an incomplete state.

Benefits

• Faster load times with less manual work.
• Optimizations that stay updated as the site changes.
• More consistent performance across pages and devices.

The post Enable AI Optimization appeared first on W3Speedster.

After integrating W3Speedster into your Core PHP application, it’s recommended to conduct a baseline performance test to assess the immediate optimization impact.

Step 1: Run a Default Settings Test

• Complete the W3Speedster integration into your Core PHP project.
• Measure the application’s performance metrics before enabling any optimization (e.g., using tools like Lighthouse, GTmetrix, or WebPageTest).
• Enable Recommended Default Settings from the W3Speedster configuration panel.
• Re-run the performance test after enabling the default settings.
• This helps you benchmark the default optimization benefits and understand W3Speedster’s initial performance gains for your Core PHP environment.

Step 2: Optional Advanced Testing (For Technical Users)

For developers familiar with web performance, asset loading behavior, and server-side rendering, W3Speedster allows deeper optimization through manual tuning.

You can enhance performance further by:

• Utilizing diagnostic tools such as:
  • GTmetrix
  • Pingdom Tools
  • Google PageSpeed Insights
• Analyzing reports to identify bottlenecks in your Core PHP application’s:
  • Route-level response times
  • Asset loading sequences
  • Render-blocking resources
  • Server-to-client delivery delays
• Applying tool-specific recommendations in combination with W3Speedster’s advanced settings to align optimization with your app’s structure, such as:
  • Delaying non-critical scripts
  • Deferring or inlining CSS
  • Optimizing database queries and eager loading
  • Fine-tuning routing logic and file includes
• This step is ideal for projects where performance is mission-critical or for applications with custom frontend stacks or real-time interaction layers.

Step 3: Interpreting Performance Test Results

To get accurate and consistent results, follow these best practices:

• Stick to one testing tool for consistency (e.g., only GTmetrix).
• Run three consecutive tests on the same tool.
• Take the average of the three results for a more reliable benchmark.

Are there any recommended settings for W3Speedster?

Yes, W3Speedster provides a set of pre-configured recommended defaults—designed as a “fast track” to achieving a(Way to 90+ on Google PSI) and similar performance benchmarks.

However, optimal results may vary based on the unique architecture of your Core PHP application, including:

• Frontend stack (e.g., raw HTML/CSS/JS, jQuery, or custom frameworks)
• Third-party packages or custom modules
• Hosting environment (shared, VPS, managed cloud, etc.)
• Content structure, such as: (e.g., Asset-heavy dashboards, Image/media-driven layouts, API-intensive workflows)

Features That Work Automatically

Some of W3Speedster’s most impactful features are designed to be plug-and-play. Simply enable them, and they handle the rest automatically in the background:

• CSS Minification
  • Reduces file size by removing unnecessary characters (whitespace, comments) from your stylesheets.
  • Improves load time without altering the appearance of your site.
• JS Minification
  • Strips down JavaScript files to their essential code only.
  • Reduces execution time and enhances overall performance.
• WebP Support
  • Automatically converts and serves images in WebP format, which is lighter and faster than JPG or PNG.
  • No manual conversion or theme changes needed.

These automated settings are safe and effective across most Core PHP setups, requiring no advanced technical expertise. They are designed to deliver noticeable performance improvements out-of-the-box, making them ideal for developers seeking quick optimization without deep configuration.

Best Practice: Gradual Testing & Enablement

To ensure a stable and effective optimization process when integrating W3Speedster into your Core PHP application, follow these steps:

• Begin with the recommended default settings to quickly achieve performance improvements aligned with Way to 90+ on Google PSI
• Incrementally enable advanced features, such as:
  • Custom Code
  • Exclusion
  • Integration hooks with PHP packages
• Use performance tools (like PageSpeed Insights, GTmetrix, or Pingdom) after each change.
• If a feature causes rendering issues, disable it immediately and retest.

Automated Features (No Manual Configuration Required)

The following features in W3Speedster are fully automated once enabled, requiring no further setup:

• HTML Caching – Speeds up repeat visits by caching the HTML output.
• WebP Support – Automatically serves images in WebP format if the browser supports it.
• Image Quality Control – Optimizes images without visible quality loss.
• Lazy Loading – Defers off-screen images and iframes for faster initial load.
• CSS Minification – Removes unnecessary characters from CSS files.
• JS Minification – Shrinks JavaScript files for faster execution.
• Combining Inline & 3rd-Party Scripts – Reduces HTTP requests by merging JavaScript code.
• Combining Google Fonts – Merges multiple font requests into one to reduce loading time.

These features work silently in the background to improve performance without manual adjustments.

Settings Pane Structure

Use this section to locate specific settings in the W3Speedster dashboard:

HTML Cache Tab

• HTML Caching – Enable/disable full-page cache.
• Minify HTML – Remove whitespace and comments from HTML output.
• Cache Preload – Automatically preloads cache for faster first loads.
• Leverage Browser Cache – Instruct browsers to cache static assets.
• Gzip Compression – Compress site files for faster delivery.
• Query Parameter Handling – Control how query strings are cached
• URL Exclusion – Exclude specific URLs from being cached.
• Cache Path – Customize the directory path for storing cache files.

General Tab

• License Key – Enter your valid W3Speedster license.
• INP Issues – Tools and fixes to improve Interaction to Next Paint (INP) scores.

CDN Tab

• CDN URL – Add your Content Delivery Network (CDN) URL.
• CDN Exclusion – Specify which files or paths to exclude from CDN.

CSS Tab

• CSS Minification – Reduce size of CSS files.
• Combine Google Fonts – Merge font requests into fewer HTTP calls.
• Critical CSS – Generate and inline above-the-fold CSS.
• CLS Fixes – Tools to minimize Cumulative Layout Shift.

JavaScript Tab

• JavaScript Minification – Compress JavaScript files.
• Combine JavaScript – Merge scripts into a single file to reduce load time.
• Load JS via URL – Add custom JavaScript file URLs to be loaded.

Exclusion Tab

• Exclude JS/CSS/Images/Pages – Prevent specific resources from being optimized or cached.
• Preload Resources – Prioritize key files for faster loading.
• Lazy Load Exclusion – Define elements to skip lazy loading.
• Custom Code Injection – Add your own:
  • CSS Code
  • JavaScript Code

Cache Tab

• HTML Cache
• CSS/JS Cache
• Critical CSS Cache

Manage and clear caches individually for precise control.

Image Settings Tab

• Image Optimization – Automates image compression.
• Image Size Adjustment – Resize large images to optimal dimensions.
• Lazy Loading – Enabled by default.
• WebP Support – Converts images to WebP format.
• Image Quality Control – Adjusts image quality threshold.

Hooks Tab

• Predefined PHP Functions – Integrate custom logic using available hooks.

Web Vitals Log Tab

• Core Web Vitals Log – Tracks real-time metrics related to:
  • LCP (Largest Contentful Paint)
  • CLS (Cumulative Layout Shift)
  • INP (Interaction to Next Paint)

The post Getting Started with W3Speedster appeared first on W3Speedster.

1. Access the W3Speedster Admin Panel

• Open your browser and go to the W3Speedster login URL:
  https://your-site-domain.com/?admin=1&page=w3_speedster
• You will see the W3Speedster login interface.

2. Log in Using Default Credentials

• Default Email: admin@example.com
• Default Password: Admin@1234

These credentials are provided only for first-time access. It is strongly recommended to update them immediately after login to secure your panel.

3. Update Admin Profile Information

After logging in:

• Click on the “Hi, Admin” at the top-right corner of the dashboard
• select settings dropdown
• Update the following details:
  • Name
  • Email
  • Password
• Once saved, these new details will become your permanent login credentials. Ensure your email is valid, as it will be used for password recovery.

4. Configure SMTP for Password Recovery

In case you forget your password, W3Speedster provides a secure email-based recovery system. To enable this feature:

• Navigate to the SMTP Configuration section under settings in the admin panel.
• Enter all required SMTP details:
  • SMTP Host
  • SMTP Name
  • SMTP Username
  • SMTP Password
  • SMTP Port
  • SMTP From
• After entering the configuration, change the status from Inactive to Active.

Enabling SMTP ensures that the system can send a password reset link to your registered email address whenever “Forgot Password” is triggered.

Benefits of SMTP Configuration

• Enables secure password reset via email.
• Ensures critical alerts and notifications are delivered successfully.
• Enhances reliability of user communication within the system.

The post Accessing W3Speedster appeared first on W3Speedster.

1. Backup Your Project (Optional but Recommended)

• Before making any changes, it’s good practice to back up your CorePHP project and database.
• This ensures rollback capability in case anything breaks unexpectedly after the removal.

2. Revert all configuration(Recommended)

• Go To Image optimization tab > click on “Restore original” button to revert all the original images in your current directory
• Disable all the active settings inside w3speedster panel like HTML Caching, Image optimization

3. Identify W3Speedster Files

W3Speedster in CorePHP generally consists of:

• /w3speedster/ directory in the root folder
• header_opt.php and footer_opt.php files
• Include statements within your PHP pages like:
  <?php include_once($_SERVER[‘DOCUMENT_ROOT’] .”/header_opt.php”); ?>

  <?php include_once($_SERVER[‘DOCUMENT_ROOT’] .”/footer_opt.php”); ?>

4. Remove Include Statements from Your PHP Files

Open all PHP pages where W3Speedster was integrated (commonly the main layout files or page templates) and:

• Delete or comment out the following lines:
  <?php include_once($_SERVER[‘DOCUMENT_ROOT’] .”/header_opt.php”); ?>

  <?php include_once($_SERVER[‘DOCUMENT_ROOT’] .”/footer_opt.php”); ?>

• Save each file after removing the reference.

5. Delete W3Speedster Files and Folders

Using FTP or your hosting file manager:

• Navigate to the root directory of your project.
• Delete the following:
  • The entire w3speedster/ directory
  • header_opt.php
  • footer_opt.php

These files are no longer needed once include references are removed.

6. Clear Optimized Assets (Optional)

If W3Speedster previously generated optimized static files (e.g., cached HTML, minified CSS/JS), you may choose to:

• Manually delete /cache/w3-cache, /critical-css/, /w3-webp/ or similar directories generated by W3Speedster, if applicable.
• Clear any references in .htaccess (if didn’t reverted).

7. Final Verification

To confirm successful uninstallation:

• Reload your site in the browser.
• Use browser DevTools (F12) → Network Tab to ensure no requests are routed through W3Speedster scripts or caching layers.
• Check for the absence of WebP conversions, lazy loading, or CDN rewrites that were previously added by W3Speedster.

Important Notes

• This uninstallation process does not affect your actual content—only the optimization layer added by W3Speedster..
• If you’re switching to a different optimization solution, ensure that residual cached data from W3Speedster is completely cleared to prevent conflicts.

The post Uninstalling W3Speedster appeared first on W3Speedster.