Support » Plugin: EWWW Image Optimizer » cookie issue

  • Resolved anand99

    (@anand99)


    gtmetrix points in cookie free domain has gone down ,below are the list shown by gtmetrix to be corrected
    /wp-content/ewww/lazy/placeholder-673×449.png
    /wp-content/ewww/lazy/placeholder-1024×683.png
    wp-content/ewww/lazy/placeholder-673×448.png
    /ewww/lazy/placeholder-671×449.png
    /ewww/lazy/placeholder-1500×375.png

    The page I need help with: [log in to see the link]

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author nosilver4u

    (@nosilver4u)

    I don’t see any lazy loader there, and I was guessing you had a CDN to prevent getting dinged for cookie-free domain, but that doesn’t seem to be the case. At least, the only CDN I see is shortpixel’s, and only half the images come from there, the rest still use your local domain–which is highly unlikely to be cookie-free, but correct me if I’m missing something!

    At any rate, if you were using a CDN, please let us know which plugin you were using to do the CDN rewriting, as I’m looking into applying one of the stock WP filters for our lazy load placeholders in a future release. So any information you can provide on your use case would be helpful.

    Alternatively, you can use our CDN, which allows you to use our lazy loader AND use a cookie-free domain: https://ewww.io/easy/

    Thread Starter anand99

    (@anand99)

    Iam using short pixel cdn provided by autoptmize , they are also providing with free webp conversion and also using front ene proxy cloud fare for the entire site and is your cdn free like short pixel given by autoptmize plugin

    • This reply was modified 3 years, 7 months ago by anand99.
    Plugin Author nosilver4u

    (@nosilver4u)

    Yeah, I can see you are using ShortPixel’s CDN, but that isn’t covering all your images. In other words, you have a lot more images using cookie-laden domains than just the few created by our lazy loader (which I fully intend to fix).

    Our CDN is not free, and neither is the ShortPixel one, unless you have a very tiny site. You get 500 credits for their service (don’t ask me how that works, read their docs), and once your site uses those, you have to signup for one of their plans. At least that is what their docs say: https://help.shortpixel.com/article/93-i-want-to-start-using-autoptimize-with-shortpixel-image-optimization-cdn

    Thread Starter anand99

    (@anand99)

    Ok, Please fix it

    Thread Starter anand99

    (@anand99)

    i have tried different types of configuration
    1. auto webp and lazy enabled
    here i got gtmetrix value
    totalpage size -1.42mb,
    but requests went to 90,
    but not serving scaled up pictures of proper size,
    Use cookie-free domains was 25,

    second configuration
    auto webp and lazy disabled
    but ewwww lazy load without enabled
    google speed test for mobile -13 to 15,
    google speed test for desktop -33 to 36,
    here i got gtmetrix value
    totalpage size -1.48mb,
    but requests went to 55,
    but are serving scaled up pictures of proper size,
    Use cookie-free domains is 0,
    google speed test for mobile -9-10,
    google speed test for desktop -33-50,
    in both cases auto html has been disabled and cloudfare html through w3tc is enabled

    here what should i prefer in one case html request is high but page memory is high and cookie point is better but no scaled images and in second case it is just the opposite , also your view on google page speed and why it is fluctuating

    Plugin Author nosilver4u

    (@nosilver4u)

    ShortPixel’s CDN already does WebP, so don’t bother with anything in EWWW IO for that.

    Really, your images are fine now, but it’s all the other stuff that is loading like garbage, and Google doesn’t really have a metric that tells you that anymore.

    If you look at a waterfall view of your site, like this: https://gtmetrix.com/reports/www.jackbite.com/Yc3PmHtL

    You will see that the images from cdn.shortpixel.ai are quick, but every request that goes directly to http://www.jackbite.com takes 1-2 seconds. Which leads to one of your next questions, “why is it fluctuating?”

    Sometimes, it’s because Google’s testing servers are busier and don’t load things as quickly, sometimes it’s because your server is busier and isn’t loading things as quickly.
    In your case, it is your server that is being slow, because we see the same results on GTmetrix and when I use the Chrome dev console (Network tab).
    What’s the fix? Unfortunately, the only way to fix a slow webhost is caching or a new webhost. You may be able to boost things by using Cloudflare, as they will deliver JS/CSS. ShortPixel does not deliver anything but images (unlike our Easy IO CDN), so you’re still stuck on the JS, CSS, etc.

    Addendum: chasing a score is a good way to waste hours of your time. Making your site faster is a good thing though, so focus on what will actually improve your speed regardless of the scores.

    • This reply was modified 3 years, 7 months ago by nosilver4u.
    Plugin Author nosilver4u

    (@nosilver4u)

    With the release of 5.7 (coming soon), the lazy load placeholders will be rewritten properly by Autoptimize in conjunction with AO’s image optimization option.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘cookie issue’ is closed to new replies.