Symptom:
When working with your email or landing page template, you notice that the template does not load, or loads very slowly. You also notice that your template in normal view appears to be blank.
When attempting to 'Save' or 'Save As' your template, the browser spins indefinitely.
Potential Causes and Resolutions:
- Large images are causing your template to load slowly.
Templates with large images can cause your template to perform poorly. If your template contains numerous large images, then your browser may require more time to load your template.
To resolve, you can try reducing the size of your images. It is recommended that images be no larger than 500 KB in size-- some web standards even recommend under 200 KB. - You have scripts (e.g. JavaScript) within the code of your email templates.
If your email template contain scripts that execute programing, your browser may be attempting to execute them in your browser, which could cause delays.
To resolve, it is recommended that executable scripts be removed from your email templates.
Here's why: Emails that contain scripts are considered huge spam flags by many spam filters. If you send an email an email with scripts, you can potentially be flagged as a spammer who is trying to embed malicious code and be identified as a "phisher".
Note - You may not necessarily need to remove scripts from a landing page. Web pages are treated differently than emails and it is common for a web page to have one or more scripts running on it. - You are using the Grammarly online tool or browser extension.
Grammarly is an online grammar and spell checker tool. It can also be installed into a browser through an add-on or extension.
Grammarly has been known to inject a large amount of its code into a user's active browser page that it is scanning. This code is subsequently inserted into your templates code by the browser. When this happens, your browser will take longer to display your template because it is busy loading all of the Grammarly code.
If the template loads, users will find extra code in their templates and the code will reference Grammarly. Here are examples of what you might see:
.gr_-editor {
overflow-y: auto;
height: 100%;
position: fixed;
width: 100%;
top: 0;
left: 0;
font-family: Arial;
color: #000;
background: rgba(0,0,0,0.7) !important;
z-index: 2147483647;
display: none;
transition: opacity 0.3s ease-in;
transform: translateZ(0);
background: rgba(0,0,0,0.5) !important;
will-change: opacity;
}
.gr_-editor.gr-_show {
display: block !important;
}
.gr_-editor .gr-_dialog-content {
background: #fff !important;
position: fixed;
z-index: 2147483647;
border: 0;
box-shadow: 0 10px 50px 0px rgba(0,0,0,0.6);
}
To resolve, users should remove the Grammarly code from their email template-- this will allow you to be able to see and work on the template. For future templates, users may need to temporarily disable Grammarly when working on their email templates. Otherwise, the Grammarly code will be inserted into your template each time Grammarly is used.