General Questions & off load

Hi @lutzryan,
Let me answer your questions point by point:

1. Offloading images to Optimole CDN server has nothing to do with reducing your SQL queries. It is mostly helpful where you have to pay high storage cost to your webhost when you have a large media library. When you offload your images to Optimole server, your images will be automatically synced to Optimole server reducing your web host server storage cost. You can also revert the changes if you wish to rollback. Read more about that here: https://docs.optimole.com/article/1323-cloud-library-browsing#rollback
2. When using Optimole plugin, you do not need to optimize the images on your end as the entire image optimization and future ready file format delivery is taken care of Optimole. So, you Optimole will take your images, optimize them and then serve them in a future ready file format like WebP and AVIF.
3. You can use Perfmatter for your script and other optimization, it’s a great plugin.
4. For page caching, I’ll recommend you to use Super Page Cache for Cloudflare plugin, especially if you have a website where user’s don’t have to login to read your content. This way your pages will be cached in Cloudflare CDN and will be served through there. This is way better than having some server level page caching. In this way you won’t need the litespeed caching plugin as perfmatters will handle script, style and other optimizations, the above plugin will handle page caching at CDN level and then lastly Optimole will handle image optimization.
5. I’m not sure if offloading images to Optimole cloud will stop WordPress from generating all these different image sizes or not, I’ve asked internally and as soon as I have an update will let you know about that.
6. One of the main concern for your website is that as you are not using the WordPress default folder structure like /wp-content/uploads/2023/06, I will suggest you to try things out with a smaller number of dataset before doing the full switch. After you enable offloading images, by default it will only offload new images and not old images unless you sync them. So, better you try out with a few images and check if everything works as expected or not. Then make the switch.

I’ll also recommend you to watch this short video to see how the offloading feature works:

Hope this helps. ??

Hi @lutzryan,
I’ve already confirmed this with the team that when you have enabled the offloading images to Optimole Cloud, Optimole, WordPress won’t be creating multiple image sizes. Instead just the primary image will be offloaded to Optimole Cloud and then optimole will auto resize them as needed without the need for WordPress conventional multiple image creation process.

Hello @isaumya and thank you for your responses

You and I had corresponded prior about Super page cache and I really like the concept and had spent alot of time installing it.

The problem I was running into with Superpage was the instagram feed plugin was not updating new posts. You said “to use a system that uses JavaScript to dynamically fetch the insta images after the page load.” Can you tell me what system that would be?
—

As it relates to my current database disconnect issues. I think it relates to devowl.io plugin real physical media, real category management, real media library causing the issue. And the plugin creator isnt helpful to identify where the problem lies.

So, I had now deleted the 11000 extra images that the plugin did not delete, as advertised. This stopped me getting the frequent API and database unavailable warning in wordpress admin. And seems to have decreased my sql issues pressure.

My installation shows 4000 images in wordpress Admin, thus I estimate about 15000 on my server. And then there are likely another 5000 orphaned images on my server.

Im not worried about the image size on my server and space being taken up.

I thought that moving to optimole offloading may remove the stress from the server when Im working in WP admin, given the volume of images.

Are you telling me that this is not the case?

Hi @lutzryan,

The problem I was running into with Superpage was the instagram feed plugin was not updating new posts. You said “to use a system that uses JavaScript to dynamically fetch the insta images after the page load.” Can you tell me what system that would be?

I don’t know how your instagram feed plugin is loading the posts, but is a page is cached in CDN then it won’t request the server for generating the page HTML. So, in that case if you have a insta feed plugin that uses JavaScript which asynchronously make ajax request to fetch the latest content then it won’t interfere with page cache.

I thought that moving to optimole offloading may remove the stress from the server when Im working in WP admin, given the volume of images.

That is truw, when you are ofloading the images to Optimole, the WP is not wasting resouces to create 100 different version of the same image, instead just the primary image gets uploaded to Optimole, and then it dynamically serves all images sizes from the primary image. This will reduce your server resource usage significantly while speeding up your front end and back end.

Id like to use superpage on an upcoming project because it was faster on ttfb internationally(and prob in other ways).

How Specifically would I go about punching holes in the cache, so that these plugins can function and update.

The main concern is the Insta feed plugin documentation is Smash balloon and here is a page on my current site. The images are served via the instgram CDN, it seems.

—
Images
Regarding the images and my current installation. Are you suggesting offloading images will only be a benefit during the uploading process? My biggest concern is dealing with media library, and trying to make it as fast as possible to navigate. And that is where Ive been having problems with datbase and API errors. So please let me know if Im barking up the wrong tree by assessing offloading.

Images and PHP ?
ALSO on the images, Im hoping to be able to use this plugin called justified image grid (or something like it).
However I cant figure out how to get these images served through optimole, or If I need to.

I like the image quality that this is shipping, however it looks as it may be a bunch of PHP calls. And Im concerned this may start being a problem if the traffic increases.

xzib.com/wp-content/plugins/justified-image-grid/timthumb.php?src=https%3A%2F%2Fxzib.com%2Fart%2Faf%2Fdesign-miami%2F2022%2Fsavannah-college-of-art-and-design-at-design-miami-2022-1-scaled.jpeg&h=1500&w=1125&q=34&f=.jpeg

• This reply was modified 1 year, 5 months ago by RL.

Hi @lutzryan,

1. The instagram feed plugin you are using, it is not asynchronously fetching the data from insta, instead it’s loading the content in your server and then showing it via PHP. So, you cannot use a long term cache solution like Cloudflare page cache. You have to use the cache mechanism you are currently using.
2. The plugin you have mentioned, Justified Image Grid, it is not taking advantage of Optimole but instead creating all the thumbnails onit’s own using PHP – this causes increase in server resource as well as execution time. If the plugin would have supported Optimole cloud, instead of generating all these thumbnails using PHP it can just directly fetch them from Optimole. Unfortunately in this case you need to contact the plugin dev asking them to support Optimole so that the plugin doesn’t create these image sizes on it’s own.

Hey @isaumya

Im still trying to get this image issue resolved and emailed Firsh at Justifiedimagegrid but he is often very slow to respond.

Im seeing web traffic has stopped per Google analytics. Google search console, high fail rate on server connectivity 28% and robot.txt at 8% and the files causing the problem seem to be JIG images.

I really like the extensive design control Justified Image grid allows. Is this plugin able to be engineered to handle 10-50 images that could be 1mb a piece? Or do you have a recommendation to use with optimole?

I modified these settings below and set “block External Leechers” to False. Not sure if this is part of the problem.

<?php
	define ('BLOCK_EXTERNAL_LEECHERS', false); // Hotlinking protection
	define ('ALLOW_ALL_EXTERNAL_SITES', true); // Ability to load images from anywhere (Facebook, Flickr, Instagram, RSS etc.)
	define ('MAX_WIDTH', 2000);
	define ('MAX_HEIGHT', 2000);
	// Exception list to blocking external leechers (hotlinking sites) be explicit about the full hosts
	$ALLOWED_HOTLINKERS = array(
		'SAME_HOST', // SAME_HOST allows child sites (subdomains for WMPL, CDN) e.g. en.example.com or cdn.example.co.uk
		'xzib.com', // allow example.com NOT subdomain.example.com or www.example.com
	//	'*xzib.com', // allow subdomain.example.com and also example.com and www.example.com
	 // '*.xzib.com', //  allow www.example.com NOT example.com
		'*googleusercontent.com' // Google's cached view
	);
?>

Hi @lutzryan,
If you use multiple images in your website with multiple image sizes, then Optimole would be the best thing for you. Cause the way Optimole works is basically once you upload the primary image (let’s say 2000px X 1333px) and you have 10 different add_image_size() inside the theme and plugin, which basically tells WP core to create all these image sizes from the primary image that has been uploaded.

Optimole will stop that, and instead only upload the primary image that you have uploaded to the Optimole cloud. From there Optimole will use URL params to resize and optimize the image on the cloud and serve the images, saving your server resource and storage cost. Screenshot: https://i.imgur.com/DAMDMjn.jpeg

But your justified-image-grid plugin is generating the image thumbnail on it’s own without using native WP option, which is causing the issue I guess.