You only need iphone to make cache for Apple based mobile phones available, but why do you vary cache for Apple mobile devices? webp images? Then, this rule is also wrong. Newer version of MAC OS X supports webp images, so you must vary OS version in UA.
first, webp images must support
web browser Safari, not
MAC OS X!
second. nothing matter exist or not support of webp images in new versions of Safari because current version of Journal theme always provide to Safari jpg and png images (not webp)
When will you start learning, that it doesn't make sense trying to make cache for bots available?
First, this rule is completely wrong. Second, there are hundreds of bots and almost every bot has different user agent. Third, this rule prevents cache for Google, Bingbot and other popular bots/search engines.
first, I NOT interested in in other "hundreds of bots", I logged of requests to site during 6 month and choose most often bots!
second, really "
prevents cache for Google, Bingbot and other popular bots/search engines"!?!?!?!?!
are you sure?
because:
-
Desktop Google bot is
Code:
Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)
-
Desktop Bing bot is
Code:
Mozilla/5.0 (compatible; bingbot/2.0; +http://www.bing.com/bingbot.htm)
-
Desktop Yandex bot is
Code:
Mozilla/5.0 (compatible; YandexBot/3.0; +http://yandex.com/bots)
third, rule for desktop bots is very-very-very right and
work!
I previously says to you that build cache for bots make sense because:
1. Google Search Console give best results for more effective urls
2. rewrite rules
prevent from errors in Mobile bots parts of GSC like "small fonts", "wider screen", "elements close to each others"
May I help you to make up 100,000 requests per hour?
this is
really FAKE!!!!!!!!!!!!
because only
simple text pages can build fast!
simple text pages without:
- images
- internal js
- external js (google shopping, analytics, tag manager) and webfonts (google fonts)
in real conditions, REAL web page of products for full build(load) and save to disk for really generated cache of page - require 2-4 seconds!!!!!!
this is from 450 to 1800 pages per hour.