While integrating a Content Delivery Network (CDN) significantly enhances performance by offloading static resources, not all paths in a Joomla—should be served via CDN. Certain directories and dynamic endpoints must always be served from the origin server to maintain functional integrity and prevent unexpected issues.

W3Speedster addresses this requirement with a flexible Path Exclusion feature.

Why We Need It

• Preserve Core CMS Functionality: Joomla-specific directories (e.g., /libraries/, /administrator/, /templates/system/) contain essential files. Serving them via a CDN can result in:
  • Version mismatches
  • Failed asset resolution
  • Malfunctioning module rendering or backend errors
• Avoid Extension & Plugin Conflicts: Joomla components, modules, and plugins often require direct file access or serve AJAX endpoints. Excluding such paths ensures proper operation without CDN interference.
• Prevent Caching of Dynamic or Sensitive Logic: Some Joomla paths include:
  • CSRF token-protected URLs
  • Login/authentication modules
  • Real-time module updates or admin AJAX calls

These must not be cached or routed via CDN to prevent security breaches or UI malfunctions.

How It Works in W3Speedster

1. Path Exclusion Field
   • Located under: W3Speedster > CDN Settings > Exclude Paths
   • You can enter relative paths that should bypass the CDN rewriting logic.
2. Example Pattern Configuration: /libraries/, /administrator/, /templates/, /media/system/js/, /modules/mod_ajax/, /api/
   • All files under these directories will not be served via CDN
   • Instead, they will be loaded directly from the origin (e.g., https://www.example.com/administrator/index.php)
3. Matching Logic: W3Speedster uses string pattern matching (not regex) to determine if a URL should be excluded. Ensure each path begins with a forward slash (/) and ends with one if targeting directories.

Benefits

• Maintains Extension Compatibility – Ensures that dynamic components, real-time modules, and backend admin features work seamlessly.
• Preserves CMS Integrity – Prevents broken template behavior, script errors, or failed admin/API interactions.
• Simplifies Debugging – Keeps CDN logic separate from core functionality, allowing easier issue isolation.
• Enhances Security – Prevents CDN caching of login URLs, session-based responses, or tokenized endpoints.

Note: Avoid excluding too many paths unnecessarily, as it limits CDN benefits. Only exclude paths essential for functionality or security.

Verification Tip

After applying exclusions:

• Inspect the page source (Ctrl+U) to confirm that excluded paths are loading from the origin URL.
• Use tools like PageSpeed Insights or DevTools Network Tab to ensure CDN is applied selectively.

The post Exclude path from cdn appeared first on W3Speedster.

Key Features of W3Speedster

• CDN Integration
  • Easily integrate any Content Delivery Network (CDN) to reduce latency and improve global load times.
• HTML Caching
  • Generates static HTML versions of pages for faster delivery to users.
• Image Optimization
  • Automatically compresses images and allows adjustment of image quality settings.
• Lazy Loading
  • Delays the loading of below-the-fold images and iframes until the user scrolls near them.
• WebP Support
  • Converts and serves modern WebP images for better compression and faster loading.
• CSS Minification
  • Removes unnecessary whitespace, comments, and formatting from CSS files to reduce size.
• JavaScript Minification
  • Minifies JavaScript files to improve script execution time and reduce load size.
• Defer Parsing of JavaScript
  • Delay loading of non-critical JavaScript to prioritize visible content and improve LCP (Largest Contentful Paint).
• Serve Scaled Images
  • Ensures images are appropriately resized and scaled to match their display dimensions.
• Avoid CSS @import
  • Rewrites or inlines styles to avoid performance penalties caused by @import usage.
• Flexible Exclusion Options
  • Selectively exclude specific CSS, JS, pages, images, or URLs from optimization rules.
• Google Fonts Optimization
  • Combines and optimizes font delivery to reduce additional HTTP requests and FOUT (Flash of Unstyled Text).
• Delay JavaScript Execution
  • Allows you to delay non-essential JavaScript (e.g., third-party scripts) until after user interaction.

Advanced Use Case Support

W3Speedster is engineered to function effectively in advanced Joomla use cases, including:

• Full compatibility with Joomla templating systems, custom templates, and layout overrides.
• Works seamlessly with Joomla eCommerce extensions, multilingual and multisite configurations, and user group access controls.
• Offers granular configuration of: Page-level HTML caching and purging, Exclusions for administrator pages, AJAX endpoints, or dynamically generated URLs.

The post What exactly does W3Speedster do? appeared first on W3Speedster.

After integrating W3Speedster into your Joomla 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 Joomla application.
• Measure the application’s performance metrics before enabling any optimization (e.g., using tools like Lighthouse, GTmetrix, or Joomla Debug System).
• 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 Joomla 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 Joomla 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 middleware and route caching
• 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 Joomla application, including:

• Frontend stack (e.g., Joomla templates, JavaScript frameworks, or custom frontend extension
• Third-party extensions or custom plugins/modules
• Hosting environment (shared, VPS, managed cloud, etc.)
• Content structure, such as: (e.g., media-heavy articles, image galleries, component-based layouts, API-driven features)

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 Joomla 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 Joomla website, 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 Joomla Extensions
• 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.

Feature:

The Change Logs functionality in W3Speedster provides a detailed audit trail of all configuration changes made within the plugin. It tracks which user performed what action, along with timestamps, ensuring complete transparency and accountability over optimization settings.

Why We Need It

• Accountability: Tracks individual user actions, helping teams identify who made specific changes.
• Audit History: Maintains a chronological log of all configuration updates, reversals, or resets.
• Error Tracing: Helps pinpoint the source of performance issues caused by misconfiguration.
• Team Collaboration: Facilitates multi-user workflows by providing visibility into each contributor’s activities.
• Security Monitoring: Detects unauthorized or unexpected changes that could impact performance or stability.

How It Works in W3Speedster

• Automated Logging: Every time a user saves, updates, or resets a configuration within the W3Speedster dashboard, an entry is automatically recorded.
• Detailed Entries:
  • User identification (username or user ID)
  • Type of action (e.g., enabled minification, disabled cache)
  • Date and time stamp
  • Affected setting(s)
• Accessible Interface: View logs directly from the W3Speedster dashboard under the “Change Logs” section for quick reference.

Benefits

• Improves transparency for developers and site owners.
• Speeds up troubleshooting by allowing rollback to prior configurations based on tracked changes.
• Enhances team workflows, especially in multi-admin environments.
• Increases trust by providing visibility into all modifications made in the optimization settings.

How to Access

• Navigate to the W3Speedster Dashboard admin.
• Click on the “Change Logs” tab or section.
• Browse the chronological list of actions, filter by date or user, and review detailed activity logs.

Best Practices

• Review logs periodically to ensure no unauthorized or accidental changes have been made.
• Use logs during debugging to correlate changes with performance regressions or improvements.
• Maintain least-privilege access—only allow trusted users to modify plugin settings.

Summary

The Change Logs feature in W3Speedster acts as a real-time audit system, ensuring every action is recorded and reviewable. It empowers teams with visibility, supports debugging workflows, and enforces accountability across optimization efforts—critical for maintaining long-term performance and operational integrity.

The post Change Logs appeared first on W3Speedster.

The “Restore Original” button allows users to safely revert back to their original image files that were previously backed up before being replaced by optimized WebP images. This ensures that users maintain full control over their media library without permanent loss of original content.

Why We Need It

• Not all browsers or environments support WebP images perfectly; sometimes, visual or layout issues may arise.
• Website owners may later decide to:
  • Re-edit or resize the original image.
  • Stop using WebP for compatibility reasons.
  • Switch optimization tools or workflows.
• Therefore, the ability to safely and easily restore original images provides necessary flexibility and peace of mind.

How It Works in W3Speedster

This feature works only when the “Remove Original Image” option is unchecked (i.e., original images were backed up instead of deleted).

When You Click “Restore Original”:

• It locates the original image from the secure backup folder (/wp-content/uploads/w3speedster-backup/).
• Replaces the current WebP-optimized image with the original JPEG/PNG version.
• Ensures the restored file is placed correctly in the standard /uploads/ directory.
• This process is safe, non-destructive, and can be reversed again if needed.

Benefits of Keeping Original Images

• Revert-Friendly: Instantly switch back to original image files with a single click.
• Non-Permanent Optimization: Gives users the freedom to experiment with WebP optimization without long-term impact.
• Compatibility Recovery: Useful if you face theme/plugin/display issues caused by WebP rendering.
• Full Media Control: Avoids the risk of permanent file loss and allows strategic performance management.

How to Enable “Keep Original Images”

• Navigate to W3Speedster → Image Optimization tab.
• Ensure that “Remove Original Image” is unchecked (backup exists).
• Click the “Restore Original” button.
• Wait for the success message indicating restoration is complete.
• Verify that your media library and front-end now use the original image formats (e.g., .jpg, .png).

The post Restore Original appeared first on W3Speedster.

Step-by-Step Testing Procedure

• Enable options incrementally: Activate one setting at a time rather than enabling all features at once. This makes it easier to identify and isolate issues.
• Test in a non-logged-in session – After enabling each option:
  • Open your site in a browser window where you are not logged in.
  • Preferably use a private/incognito window to test.
  • This ensures you see the site as a regular visitor would, bypassing any admin-specific behavior.
• Check multiple page types – Review different types of pages on your site, such as:
  • Home page
  • Blog or archive pages
  • Product or service pages
  • Contact or form-based pages
• If you encounter a display or functionality issue
  • Disable the last setting you enabled.
  • The issue will usually be resolved immediately after doing so.

Summary

Following this structured approach allows you to:

• Maximize performance gains with W3Speedster
• Minimize the risk of breaking the layout or functionality
• Confidently identify and roll back conflicting settings

The post Best practice appeared first on W3Speedster.

• After purchasing W3Speedster, you can download the ZIP file from your W3Speedster Account Dashboard, email, or from the order received page during checkout.
• To download it from my account, navigate to: My Account (login required).
• Locate the most recently purchased order and click Download.

Safari Users – Important Notice

Safari may automatically unzip .zip files upon download, which prevents you from uploading the plugin.

How to Disable Automatic Unzipping in Safari

• Open Safari.
• Go to Safari > Settings (or Preferences, depending on your macOS version).
• Under the General tab:
  • Uncheck the option: “Open ‘safe’ files after downloading.”
• This ensures that the plugin file remains in .zip format after downloading, which is required for installation.
• Now you can download the zip file normally and proceed with the installation.

The post Download W3Speedster appeared first on W3Speedster.

The Exclude JavaScript from Optimization feature in W3Speedster offers developers precise control over which JavaScript elements, both tags and inline scripts—should bypass optimization routines such as lazy loading or minification. This ensures that critical functionality, user interface behaviors, and third-party integrations remain unaffected by performance enhancements.

Why We Need It

• Ensure Functional Reliability
  • Prevent critical JavaScript files and inline logic from being delayed or reordered.
  • Maintain stable and predictable behavior across all devices and user sessions.
• Support Script Dependencies: Many scripts require strict loading sequences or DOM availability. Excluding them prevents initialization errors.
• Protect Time-Sensitive Code: Tracking tools, API handlers, UI initializers, and third-party services often need synchronous execution during the initial page load.

Problems Without Exclusion

• Core Script Failures: Lazy loading may defer essential JavaScript (e.g., navigation, modals, or UI logic), causing broken functionality.
• Delayed Third-Party Integrations: Services like Google Analytics, Facebook Pixel, Stripe, or CAPTCHA systems may fail if their scripts load late or out of order.
• Visual & Interaction Glitches: UI elements relying on animation, layout calculation, or live updates may behave inconsistently.
• Loss of Event-Driven Behavior: Inline scripts tied to user actions or page-load events may not execute when needed, impacting UX and tracking accuracy.

W3Speedster’s Solution

W3Speedster resolves these issues with a dual mechanism for JavaScript exclusion:

1. Exclude JavaScript Tags
   • Script Identification – You can define:
     • Full external URLs (https://example.com/js/main.js)
     • File names (jquery.js, custom-interaction.js)
     • Script tag identifiers or unique substrings in the script path.
   • Bypass Lazy Load & Minification – Marked scripts are excluded from:
     • Lazy loading deferral
     • Minification and merging
     • Async or defer manipulations
   • Ideal Use Cases
     • Core UI libraries (jquery.js, main.js)
     • Payment SDKs (Stripe, Razorpay)
     • Real-time modules (WebSockets, chat scripts)
     • E-commerce components (cart logic, session validators)
2. Exclude Inline JavaScript
   • Pattern-Based Filtering – Specify unique:
     • Text patterns (e.g., gtag, fbq, initializeSlider)
     • script tag IDs (id=”initMenu”)
     • Keywords that match logic-critical functions
   • Immediate Execution – Matching inline scripts:
     • Execute as part of the original HTML load
     • Are not affected by lazy loading or other deferral logic
   • Ideal Use Cases
     • Tracking scripts: <script>gtag(‘config’, ‘UA-XXXXX’);</script>
     • Marketing pixels: <script>fbq(‘track’, ‘PageView’);</script>
     • UI initializers: <script>initializeSlider();</script>

Best Practices

• Use precise and unique identifiers to avoid over-exclusion or unintended matches.
• Keep the exclusion list minimal—only essential scripts should bypass optimization.
• Regularly audit excluded scripts to ensure relevance as your site evolves.
• Verify third-party requirements, especially those that mandate synchronous script loading.

Summary

The Exclude JavaScript from Optimization feature in W3Speedster provides advanced control over the execution of both external and inline JavaScript. By selectively excluding mission-critical scripts from lazy load and other optimizations, developers can ensure seamless functionality without sacrificing overall performance. This balanced approach enhances site stability, supports third-party integrations, and upholds a high standard of user experience across all environments.

The post Exclude Javascript From LazyLoad appeared first on W3Speedster.

Localize Google Fonts is a powerful feature in W3Speedster that downloads and serves Google Fonts directly from your own server instead of fetching them from Google’s Content Delivery Network (CDN). This approach reduces external dependencies, enhances privacy and security, and improves overall website performance by allowing better control over font delivery.

Why We Need It

• Improves loading speed by reducing DNS lookups and external network delays.
• Enhances privacy and regulatory compliance by avoiding user data transmission to third-party servers.
• Increases reliability by eliminating dependence on Google’s servers, preventing font loading issues caused by downtime or network blocks.
• Provides better cache control through font versioning on your server.
• Boosts SEO and Core Web Vitals by ensuring faster, more reliable font loading and improved user experience.

Problems Without Localizing Google Fonts

• External font requests cause additional DNS and connection overhead, delaying page loads.
• Font loading may fail due to blocking of Google services in certain corporate networks or regions.
• Limited cache control since fonts are cached according to Google’s policies, not site-specific needs.
• Mixed content issues arise if fonts are served over HTTP on HTTPS sites, triggering security warnings.

How W3Speedster Solves These Problems

• Automatically downloads required Google Fonts and serves them locally from your server environment.
• Rewrites Google Fonts URLs in CSS files to local paths, ensuring seamless integration without manual adjustments.
• Integrates smoothly to your website by hooking into font enqueue or CSS generation processes.
• Eliminates the need to contact third-party servers for font delivery, improving privacy compliance.
• Enables faster font delivery using your server’s caching and CDN infrastructure, reducing load times and increasing reliability.
• Removes external dependencies, making your site more self-contained and resistant to third-party outages or blocks.

Benefits

• Faster font rendering and improved page load speed.
• Enhanced user privacy and compliance with GDPR and similar regulations.
• Increased site reliability and reduced risk of font loading failures.
• Full control over caching policies and font versioning.
• Avoidance of mixed content warnings on HTTPS sites.
• Compatibility with all major PHP frameworks, ensuring consistent behavior across platforms.

How to Configure

• Access your W3Speedster settings.
• Navigate to the CSS optimiztion.
• Enable the Localize Google Fonts option by toggling it ON.
• Save changes to apply the configuration.
• Clear any existing caches if applicable to ensure the new settings take effect immediately.

The post Localize Google Fonts appeared first on W3Speedster.

This feature gives you the control to permanently delete original images after converting them to WebP format, which is a more efficient, lightweight format for the web. It is designed to help users save server storage while delivering optimized images for faster page load times.

Why We Need It

• Image size is a major contributor to slow website performance, especially on media-heavy websites (e.g., blogs, portfolios, WooCommerce stores).
• While WebP is highly optimized and typically 25–35% smaller than JPEG/PNG equivalents, storing both original and WebP versions consumes unnecessary storage.
• For websites on shared hosting or those with limited disk space, reducing redundant storage is essential.
• This feature ensures maximum space efficiency by eliminating unused original files.

How It Works in W3Speedster

W3Speedster provides two distinct behaviors based on the state of the checkbox for “Remove Original Image”:

When Enabled:

• The original image (e.g., .jpg, .png) is permanently deleted after its WebP version is created.
• Only the WebP file remains in the image directory.
• This action is irreversible — the original image cannot be recovered once removed.

When Disabled (Checkbox Unchecked):

• The original image is retained and moved to a secure backup folder (w3-backup-images).
• The WebP version is served from the main uploads folder.
• You can revert back to the original images at any time by restoring from the backup in just one click.

Benefits of Removing Original Images

• Reduced Storage Usage: Frees up server space by deleting original media files.
• Improved Load Speed: WebP images load faster due to reduced size, improving performance metrics.
• Flexible Reversion (when disabled): Original images are preserved in case you want to disable WebP delivery in the future.
• Automated Workflow: No manual handling of file deletion or storage—W3Speedster manages it.

How to Enable “Remove Original Images”

• Navigate to W3Speedster → Image Optimization tab.
• Find the option labeled “Remove Original Image”.
• Enable permanent removal of original images after WebP conversion.
• Warning: Enabling this will delete the original files permanently and cannot be undone.
• Alternatively, leave it unchecked to keep a backup of original images and serve only WebP from the main directory.

The post Remove Original Images appeared first on W3Speedster.