Google PageSpeed doesn't measure the Loading Time!
Page Optimizations slow down the Loading Time!
LiteSpeed Guestmode is a Cheatmode!
avif Images are 30% smaller in Size as webp Images!
Quic.cloud doesn't optimize webp Images!
WordPress ThemeBuilder Themes cause HTML Overkill!
LiteSpeed SpeedMaster
It is not difficult to become a LiteSpeed Speedmaster. As a LiteSpeed Speedmaster, you are more than just an Expert for Google PageSpeed, as a LiteSpeed Speedmaster optimizes the Loading Time and not just the Display Time like PageSpeed. If you follow the Rules for Optimizing the Loading Time, you will increase the Click Rate and the Time Visitors spend on your website. Only through these Factors will you become valuable to Google and increase the Usefulness of your Website.
Speed influences the PageSpeed Score and can improve the Ranking in Search Results. However, higher Speed also influences User Behavior and reduces premature Page Bounces, meaning Users are less likely to leave your Site quickly.
Speed is not the same as Speed. Page Optimization improves the Display Time (how fast Screen is painted) but doesn't affect the loading Time (how fast Data is fetched from Server).
Google offers the Potential of a better Ranking for good Page Optimization. However, this Potential does not guarantee more Visitors. But there is a Guarantee that if a Website is slow to load, it will lose a lot of Visitors.
Page Optimization is not free. It is expensive and causes high Server Load. Page Optimization, if done by a Plugin, is executed every time a URL is requested, because Optimization doesn't change any Files but is done on-the-fly. As a Result, Optimization improves the PageSpeed Score but may actually increase the overall Load Time compared to not optimizing.
PageBuilder Themes allow Users to create Websites without HTML Knowledge but Result in bloated HTML Code. This "HTML Overkill" significantly slows down Loading Times and impacts Website Performance dramatically, even if a Page Cache is used. PageBuilder Themes present a significant Challenge for effective Page Optimization.
Do you still believe that Page Optimization will make your Site load faster?
Google PageSpeed doesn't measure the loading Time
Have you always thought that PageSpeed measured loading time? Unfortunately, this is a widespread misconception. PageSpeed cannot measure loading time and does not want to. But what does PageSpeed measure instead? PageSpeed measures display time, i.e. the time it takes to display the loaded data AFTER all the data required for display has been loaded. You may get a good score with a well-optimized page, but your page is still incredibly slow because optimization cannot improve loading time. Optimizations only improve display behavior.
Google PageSpeed assigns a Score to evaluate the Optimization. However, this Score is not assigned by a Measurement carried out by Google. Instead, the Score, or the Data required for the Score, is determined by the Google Chrome Browser of each User of this Browser, which transmits this Score Data to Google every Time a URL is requested.
Google PageSpeed does not measure the Loading Time, but the Display Time. The Loading Time only includes the Time for Loading all the Sources required for Display. However, Loading does not mean Displaying. The Display Time determines the Time it takes until the loaded Sources can be displayed after the Data has been loaded from the Server. Only the Display Time is measured and scored by PageSpeed!
Do you still believe that Page Optimization will make your Site load faster?
WordPress ThemeBuilder Themes seem to be a good solution. Without any knowledge of HTML, CSS, and JavaScript, anyone can create a theme using drag-and-drop. This not only sounds good, it is good. However, this convenience comes at a cost: a significant loss in performance. You encounter performance issues that you wouldn't have with a conventional WordPress theme. But why is this the case? The nature of every PageBuilder theme and how WordPress operates results in a massive amount of HTML code being generated to override the original HTML code of the WordPress theme. When using a PageBuilder theme, you are effectively working with two themes: the original theme and the custom PageBuilder theme.
This leads to a tremendous amount of HTML code that needs to be rendered by the browser each time a URL is requested. You don’t see the HTML code, but rendering HTML and building the Document Object Model (DOM) are the crucial processes before anything can be displayed. The less HTML code there is and the lower the nesting, the faster the browser can render the window. PageBuilder themes, however, dramatically increase both the amount of HTML code and the level of nesting! The generated HTML code from ThemeBuilder themes is equivalent to what would be required for ten websites!
JavaScript and Cascading Style Sheets (CSS) can be optimized and reduced using optimization plugins, but HTML cannot be minimized or optimized. A page cache like LiteSpeed LScache does not alter this critical situation. A page cache can only deliver the code faster, not reduce it, meaning there is no real solution—unless you forgo using a ThemeBuilder theme.
The most important thing: Google PageSpeed only indirectly rewards the amount of HTML code; it evaluates only the consequences of excessive HTML. This indirect evaluation does not provide direct evidence of what causes these consequences, even though the amount of HTML is behind most complaints.
PageBuilder themes utilize CSS frameworks like Bootstrap. CSS frameworks are libraries that provide a wide array of styles and simplify the work for designers. The layout of a website is usually custom and often requires only tailored CSS code for formatting. However, PageBuilder themes load the entire data set of the CSS framework, even though less than 10 percent of the total CSS code is actually needed. Optimization plugins can help by using Unique CSS (UCSS), but this optimization is not free, incurs additional overhead, and can negatively impact page performance, especially if a URL is not yet cached.
If you use a plugin for optimizations and if you use a PageBulier theme, then you cannot optimize what cannot be optimized! Take the current status or leave (WordPress) it.
Do you still believe that Page Optimization will make your Site load faster?
Webp is dead, long live AVIF
For many years, the webp image format was the only alternative when it came to reducing the amount of data when requesting a website, so that ideally webp images have a file size of up to 30% smaller without the image quality suffering. This has led to the webp image format being widely used and all well-known CMS providers supporting the webp format, although the webp format does not necessarily have to be supported by the respective CMS. However, the development of algorithms for compressing images does not stand still, so the avif image format has been around since 2020 and is now supported by all modern browsers. The most striking feature of this new image format is that it enables even better compression while maintaining the same image quality. While up to 30% is possible with the webp format, avif achieves a file size of up to 50% smaller compared to jp(e)g. Since avif is now fully supported by all modern browsers and devices, you are no longer dependent on the webp format.
This Website uses avif Images!
< 50% smaller filesize as jp(e)g
< 25% smaller filesize as webp
Safes up to 60% disk space
Has more options for optimization
Supported by all modern browsers since 2022
Currently unsupported by LiteSpeed Cache Plugin for WordPress and quic.cloud
avif support for LiteSpeed Cache Plugin for WordPress can be added by AWR Plugin
Page Optimization is important because it improves Display Behavior and Google rewards good Optimization, but Page Optimization does not improve Loading Time. Page Optimization only pays off if Loading Time is optimized as well, so that Visitors not only visit your Website, but also consume the Content on your Website. The Session Duration and the Click Rate set the Benchmark for whether Google classifies your Website as valuable. You cannot achieve this Benchmark with Page Optimization only. The Consequence is therefore to optimize the Display Time AND the Loading Time.
As long as the main Document isn't loaded and rendered, nothing can be displayed and Page Optimizations have no effect. Therefore a always warmed Cache is the most important Optimization to benefit from Page Optimizations.
To significantly improve Loading Time, you need a Page Cache like the server-based LiteSpeed LScache. However, a Page Cache is only as good as the Cache is always warmed up. You can warm up the Cache with the Cache Plugin's built-in Crawler, but this crawler has been highly flawed for many Years, so you will only benefit very limitedly from LiteSpeed LScache.
Bugs and Disadvantages of the LiteSpeed Cache Plugin's built-in Crawler for WordPress
Causes high Load and RAM Consumption
Needs too much time for Crawling
Has no Re-cache Option
Has no Overload Protection
Has no Cache Inventory
Can be blocked by Host Provider
Has no User friendly Error Management
Allows only Cache Warmup of all or no URLs
Due to faulty Cache Vary built-in Crawler warms up wrong Cache
Doesn't warmup the Cache of actually relevant URLs
Uses Sitemap for Crawling only, but Sitemap is used for Search Bots to index a Website
Get Maxx LiteSpeed LScache Power
Only with a warmed up Cache can Page Optimizations actually become Optimizations. A Page Cache that is not warmed up is a Waste of Resources that no one can benefit from. To get the maximum Benefits of LiteSpeed LScache, you need a Cache Warmup Crawler specially programmed for LiteSpeed LScache, which will give you the maximum Power of LScache.
Powered for
HighSpeed Cache Warmer for LiteSpeed LScache Wordpress Plugin
Multi-Threading Process Mode
Crawls up to 1,000,000 URLs within 1 hour, even on Shared Hosting
300% faster as LiteSpeed built-in Crawler
50% less Load while crawling
Dynamic Load Control
Smart Overload Protection
Post Type Selection
Auto-Adjust Configuration
Cache Vary Support for Guest Mode, Webp Replacement and Mobile View
Available as Desktop Version and Version for Command Line Interface (Cron)
Convert webp and avif Images on your own Server instead of quic.cloud
Did you know that you can convert webp and even avif Images yourself on your own Server? You don't need quic.cloud because everything you need to convert the Images is already installed on most Servers. This is especially true for Shared Hosting.
Powered for
LiteSpeed offers quic.cloud to convert Images into webp Format. This partially free Service seems to be a good Thing. However, Problems often arise because the quic.cloud Servers are regularly overloaded. There is also a Limit, so users have to switch to a paid Plan if the Limit is exceeded.
Quic.cloud converts Images into webp Format, but QC does not optimize the webp Images. This means that the File Size of the webp Images is often larger than the File size of the Original Images. As a Result, the Original Image is used rather than the supposedly better webp Image.
Free yourself from these Limitations, save a lot of Money and convert your Images on your own Server. Everything you need is already installed on most Servers. This is especially true for Shared Hosting. With the AWR Plugin you can convert all your Images on your own Server. The AWR Plugin was specially programmed for LiteSpeed and the Cache Plugin for WordPress.
webp Images are good, but avif Images are much better! The avif Image Format reduces the File Size by a further 50% compared to jp(e)g Images and does so without any loss of Quality. With the AWR Plugin you can also convert your Images to the avif Format and thereby significantly improve the loading Times.
LiteSpeed SpeedMaster
