andresugai Update
After noticing a very high page load time on several pages on the site, I used the Code Profiler diagnostic tool to identify the plugins and themes that were contributing the most to the load time.
Initially, the profiler showed that the WP Offload Media plugin was consuming an excessive amount of time (approximately 4 seconds), which was the main factor in the slowness of the pages.
To diagnose the specific cause of this high consumption by WP Offload Media, I performed isolation tests of plugins and settings. I temporarily disabled other plugins and adjusted the WP Offload Media settings, running Code Profiler after each change.
The results of the isolation tests were very revealing:
Test 1 (Original Condition): With TagDiv Composer enabled and WP Offload Media enabled and configured to rewrite URLs to S3/CDN, WP Offload Media had an execution time of approximately 4 seconds. (See Screenshot 1: Original Condition)
Test 2: By disabling the TagDiv Composer plugin, the execution time of WP Offload Media dropped dramatically to around 0.06-0.15 seconds, a normal and acceptable time. (See Screenshot 2: TagDiv Composer Disabled)
Test 3 (Crucial Result): I kept TagDiv Composer enabled, but adjusted the WP Offload Media settings to disable URL rewriting (“Copy files also to Amazon S3” and “Rewrite Media URLs” options disabled). In this condition, with WP Offload Media still ON but not interacting with S3/CDN for rewriting, the execution time of WP Offload Media was approximately 0.22 seconds. (See Screenshot 3: WP Offload Media Active, S3/CDN Disabled, TagDiv Composer Active)
Based on these results, the conclusion is that the high CPU consumption and execution time by WP Offload Media (the 4 seconds) occurs specifically when the TagDiv Composer plugin is active AND WP Offload Media is configured to intercept and rewrite media URLs to Amazon S3/CDN. When S3 URL rewriting is disabled in WP Offload Media, even with the plugin active and TagDiv Composer active, the execution time of WP Offload Media returns to normal.
This strongly suggests that there is a conflict or inefficient interaction between WP Offload Media’s URL rewriting logic (when pointing to S3/CDN) and TagDiv Composer’s page processing. Unfortunately, disabling TagDiv Composer is not a viable solution, as it is critical to the structure and layout of my site built with your theme.
I was wondering if you have any knowledge of this specific compatibility issue or performance conflict when using TagDiv Composer/Newspaper Theme in conjunction with S3 media offload plugins that rewrite URLs (such as WP Offload Media). Is there a recommended setting within the theme or Composer, a specific plugin/theme version, or a workaround that can be applied to resolve this conflict and allow both plugins to work optimally together?
I greatly appreciate your attention, support, and any guidance you can provide in resolving this critical performance issue for my site.
Thanks for your help!
Hi aminier86,
After disabling the backup option the loading time remains high. It doesn’t seem to have had an impact in my case :\
Hi aminier86, how are you?
I also tried to downgrade but it didn’t work. The hosting CPU consumption remained high and the page loading time was still compromised.
andresugai Hi Anamaria, how are you?
These are my settings, despite making the suggested changes the graph did not change and the loading time and CPU consumption remain high.
Hi, aminier86. Yes, i’m using Version: 12.7.1.
