Common Pagespeed Questions
Welcome to our guide on Common Pagespeed Questions. In this article, we will address some common questions and provide insights into various aspects of website speed optimization as measured by Pagespeed tools. Let's dive right in!
Rendering process: To display a website, numerous web elements such as images, buttons, links, etc., need to be positioned correctly according to the theme's configuration. This process is known as rendering and involves fetching data, building the web page layout, and placing components. This process can consume a substantial amount of time, accounting for about 40%-60% of the total page load. The result is HTML content sent back to the browser.
First requests: usually, the initial requests to the system trigger the rendering engine to generate the HTML content.
Caching for speed: To reduce server load and improve speed, ShopBase temporarily caches HTML content within the system. Subsequent requests can then read the pre-built HTML content and return it promptly to the browser.
Impact of traffic: Running ads or having high traffic can significantly speed up loading times because the system fetches HTML from the cache.
Reduce initial server response time: in the initial requests, you may encounter the Reduce initial server response time item in Pagespeed results. However, as more requests are made, the system can deliver data faster through caching.
CDN optimization: ShopBase use Cloudflare as a Content Delivery Network (CDN) to expedite the delivery of static content (images, JavaScript, CSS files, etc.) to the browser.
Automatic image optimization: as content passes through Cloudflare CDN, images are automatically optimized in terms of format and file size. For instance, an image may be converted from PNG to Webp format, and its file size may be reduced. These optimized images are temporarily cached in the Cloudflare system.
Caching mechanism: initially, the Cloudflare system may request information from ShopBase to fetch the file and return it to the browser. Cloudflare also optimizes images for subsequent deliveries, ensuring the best format, quality, and size for the browser.
"Serve images in next-gen formats" warning: initially, all requests to an image link will trigger the Pagespeed tool to report Serve images in next-gen formats This warning disappears as images are automatically converted to the correct format.
Pagespeed index: The pagespeed index is an important metric, but in some cases, like the checkout page, a good user experience (UX) is crucial. For example, a fast-loading checkout page allows buyers to enter their information immediately, enhancing their experience.
Checkout page optimization: ShopBase's checkout page has been optimized for quick loading. Input forms appear almost instantly, and other components like the order summary and product information load shortly after. Ongoing efforts are made to further improve loading speed.
Results can vary significantly between the first test (without caching) and subsequent tests with caching. Frequent access to a URL allows the web page to load much faster due to caching mechanisms in place.
Website Builder: ShopBase is actively working on improving loading speed for the Website Builder. Various issues are being addressed with a priority on the Website Builder.
Checkout page: the checkout page will be improved for all themes and the entire Website Builder system to ensure a fast and smooth experience.
We hope this guide has provided you with valuable insights into common Pagespeed questions. If you have further inquiries or require assistance with optimization, please don't hesitate to reach out to our support team.
1. Why does it take a long time to load the website for the first time? What is the meaning of "Reduce initial server response time" in Pagespeed results?
Rendering process: To display a website, numerous web elements such as images, buttons, links, etc., need to be positioned correctly according to the theme's configuration. This process is known as rendering and involves fetching data, building the web page layout, and placing components. This process can consume a substantial amount of time, accounting for about 40%-60% of the total page load. The result is HTML content sent back to the browser.
First requests: usually, the initial requests to the system trigger the rendering engine to generate the HTML content.
Caching for speed: To reduce server load and improve speed, ShopBase temporarily caches HTML content within the system. Subsequent requests can then read the pre-built HTML content and return it promptly to the browser.
Impact of traffic: Running ads or having high traffic can significantly speed up loading times because the system fetches HTML from the cache.
Reduce initial server response time: in the initial requests, you may encounter the Reduce initial server response time item in Pagespeed results. However, as more requests are made, the system can deliver data faster through caching.
2. What does "Serve images in next-gen formats" mean in the results?
CDN optimization: ShopBase use Cloudflare as a Content Delivery Network (CDN) to expedite the delivery of static content (images, JavaScript, CSS files, etc.) to the browser.
Automatic image optimization: as content passes through Cloudflare CDN, images are automatically optimized in terms of format and file size. For instance, an image may be converted from PNG to Webp format, and its file size may be reduced. These optimized images are temporarily cached in the Cloudflare system.
Caching mechanism: initially, the Cloudflare system may request information from ShopBase to fetch the file and return it to the browser. Cloudflare also optimizes images for subsequent deliveries, ensuring the best format, quality, and size for the browser.
"Serve images in next-gen formats" warning: initially, all requests to an image link will trigger the Pagespeed tool to report Serve images in next-gen formats This warning disappears as images are automatically converted to the correct format.
3. Which metrics are important?
Pagespeed index: The pagespeed index is an important metric, but in some cases, like the checkout page, a good user experience (UX) is crucial. For example, a fast-loading checkout page allows buyers to enter their information immediately, enhancing their experience.
Checkout page optimization: ShopBase's checkout page has been optimized for quick loading. Input forms appear almost instantly, and other components like the order summary and product information load shortly after. Ongoing efforts are made to further improve loading speed.
4. Why are the results inconsistent between runs?
Results can vary significantly between the first test (without caching) and subsequent tests with caching. Frequent access to a URL allows the web page to load much faster due to caching mechanisms in place.
5. For which themes has the page speed been improved?
Website Builder: ShopBase is actively working on improving loading speed for the Website Builder. Various issues are being addressed with a priority on the Website Builder.
Checkout page: the checkout page will be improved for all themes and the entire Website Builder system to ensure a fast and smooth experience.
We hope this guide has provided you with valuable insights into common Pagespeed questions. If you have further inquiries or require assistance with optimization, please don't hesitate to reach out to our support team.
Updated on: 12/10/2023
Thank you!