• Resolved imtino

    (@imtino)


    I already have the cache locally setting on. I am having issue with optimizing those images. Is that something I can fix?

    Report from Pagespeed:

    Optimize images
    Properly formatting and compressing images can save many bytes of data.
    Optimize the following images to reduce their size by 10.2KiB (12% reduction).
Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Author Optimizing Matters

    (@optimizingmatters)

    LYTE just downloads the thumbnails as is from youtube and stores them without any opitmization. but some image optimizing plugins allow you to add directories that contain to-be-optimized images, so if you have one of those you could add wp-content/cache/lyteThumbs/ and automatically optimize the local thumbnails?

    hope this helps,
    frank

    Thread Starter imtino

    (@imtino)

    Awesome. Thank you.

    By the way, do you know any good lazy load plugin for images that work well with Autoptimize and LYTE? Any recommendations?

    Thread Starter imtino

    (@imtino)

    How long does those images stay in the wp-content/cache/lyteThumbs/ directory? Can I manually optimized and upload it back in?

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    well, LYTE’s images are loaded after DomContentLoaded + 750ms or at document load time (whichever comes first), so lazy-loading them would not yield a lot of performance-advantage.

    with regards to lazyloading; I might add it to AO proper in 2.5 (it’s on my wishlist anyway), but until that happens you could try https://www.ads-software.com/plugins/rocket-lazy-load/ (haven’t tried it myself yet though)?

    frank

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    How long does those images stay in the wp-content/cache/lyteThumbs/ directory?

    until they are removed by someone (or something; wp super cache in some cases clears wp-content/cache entirely)

    Can I manually optimized and upload it back in?

    yes, that should work. just be sure to keep the filename identical ??

    Thread Starter imtino

    (@imtino)

    Wow, can wait for AO 2.5 with lazy load. I prefer to wait for it then to add another plugin on my WordPress install. Plus, if it built-in then there’s no conflict.

    Thanks again. You’re the best!

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    can wait for AO 2.5 with lazy load.

    you *could* wait, but 2.4 is yet to be released and work on 2.5 has not even started yet, I don’t have an ETA, but I’m pretty sure it won’t be released before end of this year/ early next year ??

    Thread Starter imtino

    (@imtino)

    That does sound like a long wait. Maybe I will have to rethink it. hehe

    By the way, AO already doing amazing job. I can’t imagine what else you can improve but of course there’s also room for improvement. I hope AO remain clean, lightweight and no bloat.

    I love AO. All my WordPress has it installed.

    I’ve dropped a lot of useful plugins over the years because they have became more and more bloated.

    I am on my next dropped Yoast SEO, too many stuff on that plugin.

    On the subject of Lazy Load, what’s your opinion on the SEO affect of it? I’ve read so many opinions. I think Google is smart enough now but what you do think?

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    well, you can read all about -and how to test- 2.4 here.

    2.5 might have lazy load, might have automated critical CSS injection (based on https://www.ads-software.com/plugins/autoptimize-criticalcss/), might have HTTP/2 push, … lots to pick from ??

    Thread Starter imtino

    (@imtino)

    Looking good. I will test it out.

    As for 2.5, I am all for it. HTTP/2 not much matter because I did that through server side already. Lazy load and automated critical CSS is a much have, will makes life so much easier.

    • This reply was modified 6 years, 8 months ago by imtino.
Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Optimize Image’ is closed to new replies.