Gisèle Wendl

<p><strong>IndexReloaded</strong> is the ultimate performance plugin, specially designed to tackle slow loading times on your website on both desktop and mobile platforms. This plugin addresses Google PageSpeed Insights issues and significantly improves Core Web Vitals.</p>
<p>This plugin offers a range of features designed to optimize your website’s speed:</p>
<ul>
<li><strong>Resolve Render-Blocking Issues:</strong> Address render-blocking CSS and JavaScript issues to streamline loading.</li>
<li><strong>Enhancing Critical Rendering Path:</strong> Automatically generate critical CSS for above-the-fold content to improve the critical rendering path.</li>
<li><strong>Minification:</strong> Reduce load size by minifying JavaScript, and CSS files.</li>
<li><strong>Resource Bundling:</strong> Combine inline/external JavaScript and inline/external CSS to reduce server requests.</li>
<li><strong>Deferred Loading:</strong> Prioritize content rendering by deferring CSS and JavaScript loading.</li>
<li><strong>Cache Leveraging:</strong> Utilize server-side object-cache for improved performance.</li>
<li><strong>Host external CSS or JS locally:</strong> For improved performance hosting external CSS and JS on your server is a big help.</li>
</ul>
<p>This plugin is your go-to solution for reducing slow loading times, improving SEO and boosting website speed, making it an essential tool for performance optimization and SEO.</p>
<h3>Why Choose IndexReloaded?</h3>
<p>Are you looking to improve your website’s performance? IndexReloaded excels in core web vitals. IndexReloaded represents our expertise gained from optimizing the performance of plenty of websites on mobile devices. We believe you could well find a similar, user-friendly, all-in-one solution for boosting the performance your website. But we do not believe that you find similar honesty and better price-performance relation in similar products.</p>
<p>Benefit from our suite of unique features designed to turbocharge your site’s loading speed. From innovative critical CSS generation for above-the-fold content to implementation of tagged page caching, we ensure lightning-fast load times that improve critical performance metrics such as Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), and more.</p>
<h3>Before You Install</h3>
<p>Our statistics indicate that the plugin improves the speed of 4 out of 5 websites. However, certain theme and plugin combinations, especially those related to caching and optimization, may lead to compatibility issues. Therefore, our plugin might not suit every website. To preview how IndexReloaded could benefit your site, there’s a simple tool that allows you to test it before installing it. <strong>We highly recommend</strong> that you visit <a href="https://pagespeed.web.dev/" rel="nofollow ugc">PageSpeed Insights</a> and run a test of your website beforehand. Please note: To accurately test your site on PageSpeed Insights, it’s crucial to temporarily disable any optimizing plugins. This test requires raw data to apply its own optimization.</p>
<h3>Features</h3>
<h4>Licencing</h4>
<p>The free version, run without licence key has everything enabled apart form CCSS (critical CSS) creation. On our website TocToc Internetmanagement (https://www.toctoc.ch/en/getindexloaded) we offer a free licence key valid for one site and one month – which allows to run a full version of the plugin before you decide if it’s worth around 30 CHF a year (for 3 websites).</p>
<p>IndexReloaded offers 3 different licences:<br />
– <strong>Free</strong>: suitable for testing IndexReloaded for one month,<br />
– <strong>Standard</strong>: enables CCSS on 3 sites for a year,<br />
– <strong>Developer</strong>: enables CCSS on 12 sites for a year</p>
<p>Privacy information: The free version of IndexReloaded does not any connection to third party websites, like ours – toctoc.ch. The licenced version connects to our website toctoc.ch for licence validation, the connection is strictly restraint to this purpose and does not send data outside the scope of licence validation to toctoc.ch.</p>
<h4>IndexReloaded Backend</h4>
<p>The backend is divided in two menu items, the “Overview” and the “Settings”.</p>
<p>For correct basic operation of IndexReloaded it will be necessary to identify JavaScript which IndexReloaded should exclude for its operations like regrouping, compression and defered loading). In some cases also CSS must get excluded.<br />
We supply an experience-based database that helps to indentify recommended excludes and – if some are found – adds them to the IndexReloaded Excludes list for your site – based on theme, plugins and elements found in your pages.<br />
This experience-based database is distributed along every release of IndexReloaded and licenced users can download a fresh copy of the experience-based database from our site in the backend of Indexreloaded in Overview->Recommended excludes</p>
<h4>IndexReloaded Overview</h4>
<p>In “Overview” we first focus on the basic operation of the plugin and on the challenge we have to solve to make it work properly.<br />
After this we have 3 tabs where the overall state of the plugin is displayed. You see if it is active and see the licencing state.</p>
<p>In tab “CSS and JS files” you see information on the css and js files produced by indexreloaded. With the “Delete files”-button you can remove all files on disk and force IndexReloaded to recreate the files.<br />
Tab “Licence key” informs on the used licence and its validity.<br />
Tab “Exclude list”, shows the proposed excludes for your settings “CSS and JS processing” setting “Exclude list” and delivers informations for the reasons why the excludes are recommended. These information come from the experience-based database.</p>
<h4>The experience-based database</h4>
<p>As we are on release 1.1.1. and this is valid for all subsequent versions, the experience behind the experience-based database <em>must still grow</em>. It is important to us to get your feedback on excludes you find in your site and which are not part yet of our experience-based database. So please send us your finds, along with plugins or themes concerned, to our moderated e-mail address knowledgebase@toctoc.ch</p>
<h4>IndexReloaded Settings</h4>
<p>IndexReloaded organizes its settings into groups for general settings, settings related to CSS and JS processing, to Critical CSS, HTML-cleanup, preloading and monitoring.</p>
<h4>General settings</h4>
<p>Within General settings, you can add a licence-key and setup some basic behaviors of the plugin, like where to store css and js-files, days generated files stay on disk and more. With setting “Activation” you activate or desactivate the enire frontend processing of IndexReloaded.</p>
<h4>CSS and JS processing</h4>
<p>The first part of these settings concern what IndexReloaded processes regarding CSS and JavaScript. You can turn off everything, turn off CSS or JavaScript-processing individually.<br />
As the core setting, the “Exclude list” allows to identify JavaScript and CSS that must be left intact by IndexReloaded. It’s a core setting because here you can make all possible errors disappear by add correct identifiers.<br />
The identifiers in this comma-separated list can be for example the id of a script or part of a filename, for inline JavaScript even parts of the code may be used as identifier.<br />
Setting “Force new files” is handy when developing the “Excludes list”, alternatively one could delete all files in “Overview”.<br />
With “Production mode” all 3 URL-Parameters we can pass along the request form the frontend, will be disabled.<br />
With “Load last JS file asynchronous” one can either defer or not defer the JavaScript-files created by IndexReloaded.<br />
Even after he grouping of JS by IndexReloaded some JavaScript will remain in HTML. Setting “Defer remaining JS after processing” defers this JavaScript. This is important for the (final) elimination of renderblocking elements.<br />
You got a ‘jquery not found’-errormessage after enabling “Defer remaining JS after processing”? Setting “Do not defer Jquery” allows to exclude jquery from deferal.<br />
The “CSS compression” setting enables or disables minimizing CSS files. By reducing CSS size, the plugin significantly improves page load times.<br />
The “Minify JS” setting enables or disables optimizing website performance by reducing JavaScript file sizes. This feature uses a third-party JavaScript minification tool, run on your site. By enabling Minify JS you reduce JavaScript size, optimize script delivery and boost web page efficiency.<br />
Setting “Minify exclude list” allow to identify JS that must not be minified, if ever this would be needed.</p>
<h4>Critical CSS</h4>
<p>This feature of the IndexReloaded significantly improves page loading speed by focusing on critical aspects of optimization. Above-the-fold Critical CSS adds up to non-blocking JavaScripts to streamline the critical path for fast rendering of essential content. Setting “enable folding” will split the grouped CSS to inline critical CSS and to deferred (asynchronously lazy load) non-essential CSS for improved performance. In addition, if some CSS-part found in original HTML does not sort out any critical CSS, this CSS may be dropped with setting “Remove CSS from CSS below if it doesn’t sort out CCSS”.<br />
Critical CSS is based on the HTML as it is displayed on the client around 2 seconds after page load. With this the urge to specify “Tags to keep above the fold” (or classes or Ids to keep above the fold) is very rare.</p>
<h4>Preloading</h4>
<p>This setting within IndexReloaded focuses on optimizing website load times by proactively preloading critical resources. This feature allows to force preloads of essential assets, such as fonts, scripts, or CSS files that are required for the initial page rendering process. By fetching these key requests ahead of time, it significantly improves page speed.<br />
However as these settings apply to every page of the site use preloading prudently. Apart from font-preloads, a preload will only show up if the filename is present in the HTML of the page.</p>
<h4>HTML Cleanup</h4>
<p>The settings here allow to remove parts of the HTML which are often considered as useless. Note that setting “Remove HTML-comments and generator meta” leaves intact comments by ko.js.<br />
But most HTML clean up is done automatically. For fonts loaded over Google it uses the “swap” mode for web fonts to ensure that a fallback font is displayed immediately, preventing a flash of invisible text (FOIT). Additionally, it optimizes the loading of Google Fonts, ensuring that content remains visible during the font-loading process.<br />
Also it makes sure that all images have alt, width and height attributes.</p>
<h3>Uninstallation</h3>
<p>When you delete the plugin, it will automatically keep all settings. During this process, the directory containing optimized files will be removed and possible cache entries in the database will get deleted. Please note that uninstalling the plugin will not remove the settings of the plugin.</p>
<h3>Feedback, Bug Reports, and Logging Possible Issues</h3>
<p>If you have any questions, suggestions, or encounter issues related to site speed optimization, we encourage you to contact us at contactindexreloaded@toctoc.ch. Whether you’re a user, developer, or tester, your feedback is essential to improving our services.</p>
<p>To facilitate troubleshooting, IndexReloaded offers error logging capabilities. If you encounter any problems, you can help us in resolving them by providing us with the relevant error log file. Your assistance will help us improve your experience with IndexReloaded.</p>


IndexReloaded

Get warp 10 for page speed performance with IndexReloaded: Minify CSS and JS, defer CSS and JS, clean up HTML, generate critical CSS and more!

Automattic

Weston Ruter

rtCamp

Google

Pascal Birchler

Joshua Wold

Alain Schlesser

Piotr Delawski

Alberto Medina

Pierre Gordon

Lovekesh Kumar

<p><a href="https://developers.google.com/search/docs/guides/page-experience" rel="nofollow ugc">Page Experience</a> (PX) is a set of ranking signals—including <a href="https://web.dev/vitals/#core-web-vitals" rel="nofollow ugc">Core Web Vitals</a> (CWV)—measuring the user experience of interacting with a web page. AMP is a powerful tool which applies many optimizations and best practices automatically on your site, making it easier for you to achieve good page experience for your visitors. The official AMP Plugin, supported by the AMP team, makes it easy to bring the power of AMP to your WordPress site, seamlessly integrating with the normal publishing flow and allowing the use of existing themes and plugins.</p>
<p><iframe loading="lazy" title="AMP for WordPress: The official AMP plugin for WordPress" width="750" height="422" src="https://www.youtube.com/embed/s52JNMT59s8?list=PLXTOW_XMsIDRGRr5QDffrvND8Qh1RndFb" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe></p>
<p>For more videos like this, check out the ongoing <a href="https://www.youtube.com/playlist?list=PLXTOW_XMsIDRGRr5QDffrvND8Qh1RndFb" rel="nofollow ugc">AMP for WordPress video series</a>.</p>
<p>The plugin’s key features include:</p>
<ol>
<li><strong>Automate the process of generating AMP-valid markup as much as possible</strong>, letting users follow the standard workflows they are used to in WordPress.</li>
<li><strong>Provide effective validation tools</strong> to help users deal with AMP incompatibilities when they happen, including mechanisms for <strong>identifying</strong>, <strong>contextualizing</strong>, and <strong>resolving issues caused by validation errors</strong>.</li>
<li><strong>Provide development support</strong> to make it easier for WordPress developers to build AMP-compatible ecosystem components and build websites and solutions with AMP-compatibility built-in.</li>
<li><strong>Support the serving of AMP pages</strong> to make it easier for site owners to take advantage of mobile redirection, AMP-to-AMP linking, and generation of optimized AMP by default (via PHP port of AMP Optimizer).</li>
<li><strong>Provide a turnkey solution</strong> for segments of WordPress creators to be able to go from zero to publishing AMP pages in no time, regardless of technical expertise or availability of resources.</li>
</ol>
<p>The official AMP plugin for WordPress is a powerful tool that helps you build user-first WordPress sites, that is, sites that are fast, beautiful, secure, engaging, and accessible. A user-first site will deliver experiences that delight your users and therefore will increase user engagement and the success of your site. And, contrary to the popular belief of being only for mobile sites (it doesn’t stand for Accelerated <em>Mobile</em> Pages anymore!), AMP is a fully responsive web component framework, which means that you can provide AMP experiences for your users on both mobile and desktop devices.</p>
<h4>AMP Plugin Audience: Everyone</h4>
<p>This plugin can be used by both developers and non-developer users:</p>
<ul>
<li>If you are a developer or tech savvy user, you can take advantage of advanced developer tools provided by the AMP plugin to fix validation issues your site may have and reach full AMP compatibility.</li>
<li>If you are not a developer or tech savvy user, or you just simply don’t want to deal with validation issues and tackling development tasks, the AMP plugin allows you to assemble fully AMP-compatible sites with different configurations taking advantage of AMP-compatible components. The plugin helps you to deal with validation issues by removing invalid AMP markup in cases where it is possible, or altogether suppressing AMP-incompatible plugins on AMP pages.</li>
</ul>
<p>The bottom line is that regardless of your technical expertise, the AMP plugin can be useful to you.</p>
<h4>Template Modes</h4>
<p>The official AMP plugin enables site owners to serve AMP to their users in different ways, which are referred to as template modes: Standard, Transitional, and Reader. The differences between them are in terms of the number of themes used (one or two), and the number of versions of the site (non-AMP, AMP). Each template mode brings its own value proposition and serves the needs of different scenarios in the large and diverse WordPress ecosystem. And in all cases, the AMP plugin provides as much support as possible in terms of automating the generation of AMP pages, as well as keeping the option chosen AMP valid. In a nutshell, the available template modes are the following:</p>
<p><strong>Standard Mode</strong>: This template mode is the ideal, as there is only one theme for serving requests and a single version of your site: the AMP version. Besides enabling all of your site to be AMP-first, this has the added benefit of reducing development and maintenance costs. This mode is the best choice for sites where the theme and plugins used in the site are fully AMP-compatible. It's also a good option if some components are not AMP-compatible but the site owner has the resources or the know-how to fix them. See our <a href="https://amp-wp.org/showcases/?template_mode=standard" rel="nofollow ugc">showcase</a> of sites using Standard mode.</p>
<p><strong>Transitional Mode</strong>: In this mode there is also a single theme used, but there can be two versions of each page: AMP and non-AMP. The active theme is used for serving the AMP and non-AMP versions of a given URL. This mode is a good choice if the site uses a theme that is not fully AMP compatible, but the functional differences between the AMP and non-AMP pages are acceptable (due to graceful degradation). In this case, users accessing the site from mobile devices can get the AMP version and get an optimized experience which also retains the look and feel of the non-AMP version. Check out our <a href="https://amp-wp.org/showcases/?template_mode=transitional" rel="nofollow ugc">showcase</a> of sites using Transitional mode.</p>
<p><strong>Reader Mode</strong>: In this mode there are two different themes, one for AMP pages and another for non-AMP pages, and therefore there are also two versions of the site. This mode may be selected when the site is using an AMP-incompatible theme, but the level of incompatibilities is significant without graceful degradation. It’s also a good choice if you are not technically savvy (or simply do not want to deal with the incompatibilities) and therefore want simplified and robust workflows that allow you to take advantage of AMP with minimal effort.</p>
<p>Different modes would be recommended in different scenarios, depending on the specifics of your site and your role. As you configure the plugin, it will suggest the mode that might be best for you based on its assessment of the theme and plugins used on your site. And, independently of the mode used, you have the option of serving all or only a portion of your site as AMP. This gives you all the flexibility you need to get started enabling AMP on your site progressively.</p>
<h4>AMP Ecosystem</h4>
<p>It is possible today to assemble great looking user-first sites powered by the AMP plugin by picking and choosing themes and plugins from a growing AMP-compatible ecosystem. In this context, the AMP plugin acts as an orchestrator of the overall AMP content creation and publishing process; it serves as a validator and enforcer making it easier to not only get to AMP experiences, but to maintain them with confidence.</p>
<p>Many popular theme and plugin developers have taken efforts to support the official AMP plugin. If you are using a theme like Astra or Newspack, or if you are using plugins like Yoast or WP Forms — they will work out of the box! You can see the <a href="https://amp-wp.org/ecosystem/" rel="nofollow ugc">growing list</a> of tested themes and plugins.</p>
<h4>AMP Development</h4>
<p>Although there is a growing ecosystem of AMP-compatible WordPress components, there is still a ways to go before majority AMP compatibility in the ecosystem. If you are a developer, or you have the resources to pursue development projects, you may want in some cases to develop custom plugin or theme to serve your specific needs. The official AMP plugin can be of great help to you by providing powerful and effective developer tools that shed light into the AMP development process as it is done in WordPress. This includes mechanisms for detailing the root causes of validation issues, the contextual space to understand them properly, and methods to deal with them during the process of achieving full AMP compatibility. Read more about <a href="https://amp-wp.org/documentation/getting-started/developer-tools/" rel="nofollow ugc">Developer Tools</a>.</p>
<h4>Getting Started</h4>
<p>To learn more about the plugin and start leveraging its capabilities to power your AMP publishing workflow, check <a href="https://amp-wp.org/" rel="nofollow ugc">the official AMP plugin product site</a>.</p>
<p>If you are a developer, we encourage you to <a href="https://github.com/ampproject/amp-wp" rel="nofollow ugc">follow along</a> or <a href="https://github.com/ampproject/amp-wp/wiki/Contributing" rel="nofollow ugc">contribute</a> to the development of this plugin on GitHub.</p>
<p>We have put up a comprehensive <a href="https://amp-wp.org/documentation/frequently-asked-questions/" rel="nofollow ugc">FAQ page</a> and extensive documentation to help you start as smoothly as possible.</p>
<p>But if you need some help, we are right here to support you in the plugin’s <a href="https://wordpress.org/support/plugin/amp/" rel="ugc">support forum</a>, as well as through <a href="https://github.com/ampproject/amp-wp/issues" rel="nofollow ugc">GitHub issues</a> (for technical bugs and feature requests). And our thriving <a href="https://amp-wp.org/ecosystem/amp-experts/" rel="nofollow ugc">AMP Expert ecosystem</a> has indie freelancers to enterprise grade agencies in case you need commercial support!</p>


It's best AMP plugin for WP. With good support team

Best AMP plugin for WP

Memory usage jumped from 5% to 91% when this plugin was activated.

Killed Php Memory

Excellent tool.


I tried it when AMP was a "must have" but it’s just adding problems to your site. All the work you make on your site to give a good experience for your users is broken by AMP rendering. SEO is worst and the product helps only Google to make money on your work. Don’t install it, choose a light theme and put your effort on the theme.


Bad Experience

An easier path to great Page Experience for everyone. Powered by AMP.

IndexReloaded vs AMP