![]() This can be done by defining the absolute or relative path to the images and optionally the pixel density descriptors (e.g. The srcset attribute allows image sources to be defined. This offers browsers the ability to display a specific image when a rule is met. The srcset, sizes, and media attributes allow the and elements to be extended by offering the browser additional information, such as different image sources as well as different display sizes and media conditions. What are the srcset, sizes, and media attributes? As you may recall from our Image CDN article, images take up 51% of the average web page size, which means serving scaled images is critical to reduce your web page sizes. This is advantageous because of the significant performance improvements that can be gained. ![]() ![]() Instead of taking a single image and only making it responsive with CSS, which is then delivered to all devices, you can deliver completely different images based on the requesting device. This allows you to further optimize your image delivery to improve the overall performance of your website or application. But once you're using Campaign, you'll likely never want to go back to anything else, as the content/editing approach & experience is just so great.Responsive image techniques, such as the srcset, sizes, and media HTML attributes, allow different scaled images to be delivered based on the size and resolution of the accessing device. Given the list size you're talking about, you'll definitely want to spend more time on the performance optimisation than most would normally need to do, do some extensive testing, and just be aware of this during your development. With caching, this can be significantly improved but we have had some issues with stale previews etc when doing this, so don't feel we have things quite right yet. (Without any performance optimisation/caching, using MJML based templates, and using a $20 Vultr VPS, it's about 10+ hours to send to the list. That is of course inherent to the Campaign approach of using Craft templates and your server. We have about 10000 on our list, use Postmark as our ESP (they are brilliant - best SAAS I've ever used!) - but the sending does take a fair while and place a noticeable amount of load on the server during that time. Indeed, with those, often you might want to slow things down and stagger delivery to prevent the inevitable server hit from all those folks clicking on your links etc., when you do a send out. If you're used to Mailchimp or similar, you'll know the entire thing sends in the blink of any eye with those services - even to massive lists. My only caveat to raise is with the sending performance side of things. ![]() And the more you send, the more you save! The cost is dramatically cheaper than any service based alternative. Things like MJML or similar can greatly help ease that development of course. ![]() Of course the developer has to do a bunch of work on email templates (ergh!) - to get the quality of content delivery to similar levels to what you get out of the box with a service. The approach is just superb - being able to edit in the CMS, and use existing content, is revelatory vs. Campaign is an excellent plugin, and Ben a truly excellent and supportive developer. ![]()
0 Comments
Leave a Reply. |