Image Optimization and Content Delivery Networks (CDN)

Classic Plugins
1

Hi friends,

I am interested in adding Image Optimization to Turbo so you’ll never have to ask yourself, “Did I optimize those images?”, “What is image optimization?”, “What’s the best optimization for these types of images?”, etc. The goal of Turbo is to give you the best website performance while maintaining control and privacy all without having to think about it. As with all solutions, there are many approaches to this. I’d love to hear your thoughts

  1. Do image optimization on my server. Pros: completely private with respect to GDPR, etc. Images are served from your Domain. Cons: less effective optimization
  2. Use an image Optimization API (built by yours truly). Pros: More effective image Optimization. Images hosted from your Domain. Cons: Requires the images to be optimized by me and downloaded to your server.
  3. Automatic CDN. Pro: we upload your image to our CDN and globally distribute it for you. This ensures a high cache hit ratio fast response times. We optimize images in the cloud for you. Cons: images are not hosted on your domain. All of this is included in your subscription.

I’d love your feedback!

Thanks
Greg

1 Like
2

Hi Greg,

If Option 3 is selected, will it require us to create new/alter the links for each image in the project ?

Thanx,
Pearson

3

I’m liking the potential here.

  1. Privacy and GDPR matters. Any idea how much less optimization!
  2. Is GDPR affected? Costs more?
  3. Not on the domain would effect image search traffic and SEO is a negative way.
4

Nope, never. The idea regardless is that everything is transparent for you.

1 Like
5

No change in costs, always would be included. I’ll likely start with option 2. The optimizations in option 1 are significantly less.

Thanks all for the feedback!

6

How does option 2 affect GDPR? , maybe that’s what you meant by always included?

7

Great questions!

In either Option 1 or Option 2, images will always be hosted from your domain. GDPR does not apply here.

In Option 1, the image is optimized in your web hosting environment directly. This doesn’t work great in my preliminary testing (images were optimized, but the amount of savings could be better).

In Option 2, the image would be sent, in the background (with ZERO user information) to my API service where I 1) optimize the image and 2) return it back to your hosting environment. The user requests the image from your web hosting server as normal.

From the user’s perspective and GDPR, these 2 options are exactly the same. :slight_smile:

Thanks for the questions!

Cheers
Greg

1 Like
8

Awesome! What are the prerequisites of using TURBO? Stacks, Elements, Classic, Hand-coded, Wordpress?

9

Any solution where the visitor’s IP is shared with an external supplier, will require consent from that visitor according to GDPR. Keeping that in mind, the site’s owner will have to place all the optimised images behind a consent construction.

In theory you could list Chillidog as a data processor in your privacy policy, which would remove the requirement of consent from the visitor, but I don’t think image optimisation has ever been tested in court in the EU. Google Fonts was not allowed to be listed as a data processor in a similar case, which lead to quite a legal pothole in Germany.

Cheers,
Erwin

10

Yes, Option 1 and 2 will not violate this. No user information is processed.

2 Likes
11

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.