What Frame Manages
Frame manages advanced performance settings such as caching, CDN delivery, and other platform-level optimizations.
Caching helps store temporary copies of site content so pages can load faster.
CDN delivery helps serve files such as images, scripts, stylesheets, and fonts from server locations closer to the visitor.
Because Frame is a managed platform, these settings should not be changed manually by editors.
What Editors Can Do
Editors can help keep pages fast by making smart content choices in the Frame editor.
Recommended practices include:
Use properly sized images
Avoid uploading large original camera files
Limit video embeds
Limit third-party embeds
Keep page layouts simple
Remove unused or duplicate content
Preview pages before publishing
What Editors Should Not Change
Editors should not try to manage advanced performance settings unless instructed by Frame support.
Do not:
Install caching plugins
Install CDN plugins
Change DNS settings for performance
Edit theme or site code
Add custom performance scripts
Change hosting or server settings
These settings are managed by Frame to protect site stability and consistency.
When to Contact Frame Support
Contact Frame support if:
A page is loading unusually slowly
Images are not loading correctly
Recent updates are not appearing after publishing
A caching or CDN issue is suspected
A third-party script needs to be added
A page needs advanced performance help
When contacting support, include the page URL, a short description of the issue, and any recent changes made to the page.
What Is Caching?
Caching helps your Frame site load faster by storing temporary copies of site content.
Instead of loading everything from scratch every time someone visits a page, cached content can be delivered more quickly. This can help pages feel faster for visitors and reduce extra load on the site.
Simple Example
Imagine your homepage has images, text, styles, and layout files.
Without caching, the site may need to load everything again each time someone visits.
With caching, some of that content can be stored temporarily and reused, so the page loads faster.
Why Changes May Not Appear Right Away
Sometimes caching can cause recent updates to take a little time to appear. This does not always mean the update failed.
For example, if you update an image, button, or page section, you may still see an older version for a short time because a cached version is being shown.
What Editors Should Do
If you recently made a change and do not see it right away:
Refresh the page
Check the page in a private or incognito window
Try viewing the page on another device
Wait a short amount of time and check again
If the update still does not appear, contact Frame support.
What Editors Should Not Do
Do not install caching plugins or change advanced caching settings. Frame manages caching at the platform level.
Changing caching settings manually can cause display issues or conflicts with the managed platform.
What Is a CDN?
A CDN, or Content Delivery Network, helps your Frame site deliver files faster by using a network of servers.
These files can include:
Images
Stylesheets
Scripts
Fonts
Other static site files
Instead of every visitor loading those files directly from one main server, a CDN can deliver cached copies from a server location closer to the visitor.
Simple Example
Imagine your Frame site has a large homepage banner image.
Someone in Washington, Florida, and Mexico all visit the site.
Without a CDN, each visitor may need to load that image from the main site server.
With a CDN, the image can be delivered from a server location closer to each visitor.
In simple terms:
Without a CDN:
Visitor → Main site server → Image loads
With a CDN:
Visitor → Nearby CDN server → Image loads faster
A CDN is like having multiple local stores instead of one central warehouse. Visitors can receive common site files from a closer location instead of waiting for everything to come from the original server.
CDN Usage on Frame
Frame manages CDN delivery at the platform level. Editors do not need to set up a CDN manually.
Do not:
Install CDN plugins
Set up AWS, Cloudflare, or other CDN services
Change DNS settings for CDN purposes
Modify server settings
Frame handles CDN delivery for you.
What Editors Should Know
A CDN can help site files load faster, but it does not fix every performance issue.
If a page has too many large images, video embeds, or third-party tools, it can still load slowly. Editors should still keep pages clean and lightweight.
How Editors Can Keep Pages Fast
Frame manages many performance settings automatically, but editors still play an important role in keeping pages fast and easy to use.
The way a page is built can affect how quickly it loads. Large images, too many videos, heavy embeds, and long page layouts can slow things down.
Use Properly Sized Images
Images are one of the most common reasons a page becomes slow.
Before uploading images to Frame:
Use images that are large enough to look clear, but not larger than necessary
Avoid uploading original camera files when a smaller web version will work
Use JPG or WebP for most photos
Use PNG only when transparency or sharp graphic detail is needed
Avoid placing too many large images on one page
Remove duplicate or unnecessary images
For most page content, an image does not need to be several thousand pixels wide unless it is being used as a large hero image or full-width background.
Be Careful With Large Background Images
Large background images can make a page look nice, but they can also make the page heavier.
Use them carefully on:
Homepages
Hero sections
Landing pages
Full-width sections
A single strong image is usually better than several large background images on the same page.
Limit Video Embeds
Videos can slow down a page, especially when several are embedded at once.
Recommended practices:
Only embed videos that are necessary
Avoid placing several videos on one page
Use a button or thumbnail link when a full embed is not needed
Keep video-heavy content on a dedicated page
For example, instead of embedding five videos on a homepage, use one featured video and link to the rest.
Limit Third-Party Embeds
Third-party embeds can add extra loading time to a page.
Examples include:
Maps
Calendars
Social media feeds
Forms
Chat widgets
Tracking scripts
Before adding an embed, ask:
Does this need to appear directly on the page?
Could this be linked instead?
Does it need to appear on every page?
Will this slow down the visitor experience?
If a third-party script or advanced embed is needed, contact Frame support.
Keep Page Layouts Simple
Large pages with too many sections, images, columns, embeds, or animations can feel slower for visitors.
To keep pages easier to load:
Use only the sections you need
Keep homepage content focused
Avoid repeating image-heavy sections
Move long content into separate pages
Use buttons and links to guide visitors to more details
A clean page is usually faster, easier to read, and easier to maintain.
Avoid Copying Messy Content
Copying content directly from another website, document, or page builder can sometimes bring unwanted formatting with it.
To keep pages clean:
Paste as plain text when possible
Reapply headings, buttons, and formatting inside Frame
Avoid copying entire layouts from outside sources
Preview the page after pasting content
Optimizing Images for Frame
Images help make your Frame site look polished, but large image files can slow pages down.
Before uploading an image, make sure it is the right size and format for the page.
Recommended Image Practices
Use these guidelines when adding images to Frame:
Use JPG or WebP for most photos
Use PNG when transparency is needed
Avoid uploading original camera files
Avoid using images that are much larger than needed
Compress images before uploading when possible
Remove duplicate or unused images from the page
When Large Images Are Okay
A larger image may be needed for:
Homepage hero sections
Full-width banners
Large background images
Featured landing pages
Even then, the image should still be optimized for web use.
When Smaller Images Are Better
Smaller images are usually better for:
Staff photos
Blog posts
Ministry cards
Event previews
Inline page images
Thumbnails
These images do not need to be extremely large to look good on the page.
Image Checklist
Before publishing, check that:
Images look clear
Images are not larger than necessary
The page does not have too many large images
Duplicate images have been removed
The page has been previewed on desktop and mobile
Limiting Embeds and Third-Party Content
Embeds and third-party content can be useful, but they can also slow down a page if too many are added.
Examples of third-party content include:
YouTube videos
Google Maps
Social media feeds
Calendars
Forms
Chat widgets
Tracking scripts
Why Embeds Can Affect Performance
When you add an embed, the page may need to load content from another service. This can add extra files, scripts, or loading time.
One embed may be fine, but several embeds on the same page can make the page feel slower.
Best Practices
Use embeds only when they are needed.
Recommended practices:
Use one featured video instead of several videos
Link to extra videos instead of embedding all of them
Use a button link when a full embed is not necessary
Keep maps, calendars, and feeds limited to the pages where they are needed
Avoid placing heavy embeds on the homepage unless necessary
When to Contact Frame Support
Contact Frame support if:
An embed is not loading correctly
A page became slower after adding an embed
A tool needs to appear across the whole site
Frame support can help make sure third-party tools are added safely and do not create unnecessary performance issues.