tucker501
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Shortcode in Pagebuilder opens as Greyed outiMaginem Pagebuilder r6
Thank you for taking the time to give a work around. I purchased this plugin at 3.5.5, so not sure how to download an older version. I’ll try going to their download site, but not sure I will have access to older versions.
I’m assuming that the older version didn’t break anything you had done, only allowed the proper font to be shown. The sizing of the font that IS shown is not exactly correct either. Wish it wouldn’t take so long for them to issue a fix for something as big as implementing the incorrect font. I may end up looking at another slider as I don’t have a ton of time invested in the project.
Thank you again.
Forum: Plugins
In reply to: [Health Check & Troubleshooting] Plugin stuck on “Results are still loading…”I have the exact same issue and I don’t have Jetpack as a plugin. I do have a caching program that does a form of memcache. Haven’t tried turning that off because I need the mem-casching more than health check.
This started immediately after new WordPress version was installed.
Any solutions noted?
- This reply was modified 4 years, 6 months ago by tucker501.
Forum: Plugins
In reply to: [LiteSpeed Cache] JS MinifyAfter clearing my browser cache, I see far fewer, but some still are there:
Minifying https://mdavis.photos/wp-content/themes/kreativa/js/tilt.jquery.js could save 1009B (35% reduction) after compression. See optimized version.
Minifying https://mdavis.photos/wp-includes/js/jquery/jquery.js could save 68B (1% reduction) after compression. See optimized version.
Minifying https://player.vimeo.com/api/player.js could save 63B (2% reduction) after compression. See optimized version.
Minifying https://mdavis.photos/wp-content/litespeed/cssjs/d88e4.js could save 34B (2% reduction) after compression. See optimized version.
Minifying https://mdavis.photos/wp-content/litespeed/cssjs/d8f74.js could save 14B (1% reduction) after compression. See optimized version.
Minifying https://mdavis.photos/wp-content/litespeed/cssjs/ae31f.js could save 10B (1% reduction) after compression. See optimized version.
Minifying https://mdavis.photos/wp-content/litespeed/cssjs/9a3ce.js could save 5B (1% reduction) after compression. See optimized version.
Minifying https://mdavis.photos/wp-content/litespeed/cssjs/6d24d.js could save 4B (1% reduction) after compression. See optimized version.
Minifying https://mdavis.photos/wp-content/litespeed/cssjs/ae385.js could save 4B (1% reduction) after compression. See optimized version.Forum: Plugins
In reply to: [LiteSpeed Cache] Load Js deferred breaks only ONE pageJS Combine is set to OFF!
Forum: Plugins
In reply to: [LiteSpeed Cache] Load Js deferred breaks only ONE pageThank you for such a fast response. Ultra fast response.
I’m not sure I understand your answer. I think what you are saying is that before I can find the files to exclude, I need to disable js combine/minify.
Because you have such a very reasonable paid service, I think I will just submit a paid ticket to get you to do this for me.
Again, thank you for your response.
Regards,
MikeI now understand. It only optimized the thumbnail, NOT the full sized image. I totally understand this now.
So, here’s my next pre-sales question. Since this is a photography site I don’t want to notice ANY changes in photo quality. Can I ask the pro version to just optimize 5 images instead of all of mine, in case I don’t like the results? Easy to put back 5 images, but not so easy to put back 300.
Secondly, I use a CDN provided by my hosting site. How will it work to use your CDN as well?
Michael- This reply was modified 4 years, 9 months ago by tucker501.
Thank you for taking the time to respond, especially to someone only using the free version.
My test was with new images, not originally uploaded images. When I uploaded the new image, I did see that the plug-in indicated a “savings” in optimization. Then I turned off the optimization of new images from the plug-in settings and put an identical image (different name) in the media library. I noticed that the plug-in, rightfully so, did not indicate that an optimization had occurred. This is what I expected since I had turned off optimize new images. Then I looked at both images on a live website page using the page inspector. Both images, the optimized one and the non-optimized one, was listed as same size in the browser element inspector.
I’m thinking I’m not doing this correctly.