As with other Lovely emails this is strong typographically and has good hierarchy. Its easy to browse and to read. The point of the email is clear.
Imagery suggesting security or helping me understand the importance of this email would be helpful. In addition an opportunity to read more might be a good next step. The action item seems to be to “go to Lovely”, but that doesn’t seem like the best choice. Its hard to have emails like this and not freak people out or hurt your brand, but its also important to clearly communicate the importance of an issue like this.
They could use a little more padding on top and bottom in my pick opinion as well.
Here’s how Lovely's emails render in the most popular email clients. Are yours rendering as designed? Find out with a free trial of Litmus.
Looks aren’t everything. Does this email follow key accessibility best practices? Our friends at Litmus ran the test.
Table roles should be clearly defined. This helps screen readers determine how to interpret the table.
Larger paragraphs of text should be left-justified to improve readability for some readers.
Email headings should be well structured. This will help screen readers easily navigate content.
Specifying "alt text" for these images helps screen readers describe the image.
Without a [lang] attribute, screen readers will assume the email is in the default language the subscriber chose when setting up their screen reader. If your email is not in that user’s language, the screen reader may not accurately transcribe your message.
Emails should have a "meta content-type" and defined character set.