Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Vytis

    (@bvytis)

    Hi @nazrinn,

    Thank you for using Optimole and I’m sorry to hear about this issue.

    Have you excluded SVG images as shown in this image – https://vertis.d.pr/uaJzET ?

    If you added it this way, have you cleared cache not only from Optimole but your caching plugins if you have any?

    Let us know if the issue persists, thanks!

    Thread Starter Nazrinn

    (@nazrinn)

    Hello Vytis,

    Yes I did. I flushed the cache of both my plugins multiple times and looked at the SVGs is my incognito browser, but there was no change.

    Because I was under time pressure, I simply reuploaded the images on my server. It fixed the problem, but I’d be ready to test it again on my staging environment after the site goes live, if you wish.
    Because they are so small, however, I wonder if it’s actually worth the trouble of synchronizing my SVG files using Optimole’s CDN.

    They’re around 20kb at most, and I feel like the DNS lookup time might not be worth it. Is there a way to exclude them from the CDN like I exclude them from optimization? What should I do?

    • This reply was modified 3 years, 10 months ago by Nazrinn.
    Plugin Support Vytis

    (@bvytis)

    Hi @nazrinn,

    You’re right, SVGs are tiny files, and optimizing them doesn’t reduce the file size a lot.
    Sometimes this happens when minimizing SVGs (some tags might be dropped that are not SVG compatible) resulting in broken SVGs.

    If you exclude SVGs by extension in the Optimole’s settings – original links should be back (not served via Optimole).

    If this doesn’t happen please contact us directly via https://optimole.com/#contact so we can check your website further.

    Thanks!

    Thread Starter Nazrinn

    (@nazrinn)

    I reuploaded my SVG after I excluded them. Now it’s alright. Their original link is back too, so it’s all peachy.

    If I still have problems with this in the future, I’ll let you know.

    At that point, why not exclude SVGs by default? To me it only made (all of them) look noticeably worse.

    Plugin Support Vytis

    (@bvytis)

    Hi @nazrinn,

    Great, happy to hear that it worked, thanks for the update!

    It depends on the SVGs and not all the files get broken when optimized so we leave the opportunity for users to decide whether they want to process SVGs or not.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Rollback SVG optimization (cache issue?)’ is closed to new replies.