Performance
Keep your site fast: what Uncoder loads, hero image priority, lazy loading, embeds, font delivery and caching plugins.
On this page
Uncoder is built to load little by default: each page gets only the styles and scripts it needs, images load lazily, and videos and maps wait until a visitor wants them. This page explains what happens automatically, which switches you can change, and how Uncoder works with caching plugins.
The speed settings are in Uncoder → Settings → Performance & fonts.


What Uncoder does automatically
- Only what the page uses. The styles and scripts of a widget load only on pages that contain it. A page without a slider never loads slider code.
- One stylesheet per page. When you save a page or template, Uncoder writes its styles into a small CSS file in your uploads folder. The Design System has its own file. Browsers cache these files, so the next page loads faster.
- Scripts wait. Uncoder's front-end script is small, loads at the end of the page and does not block the page from showing.
- Lazy images. Images load when visitors scroll near them, except the hero image (see below). Featured images and product images in post and product grids do too, and so do the Featured Image widget (with Loading on Automatic (lazy below the first section)) and images printed by a Shortcode widget, unless they are in the page's first section. An image in a shortcode's output that already says how it loads keeps that choice.
- Light embeds. The Video and Video Playlist widgets show a poster and a play button; YouTube or Vimeo loads only when the visitor clicks play (Load player on click, on by default). The Google Maps widget loads lazily, or only after a click with Load on click.
If your uploads folder is not writable, Uncoder prints the styles into each page instead of files. Settings → Tools then shows a warning. Ask your host to fix the folder permissions, because separate files load faster and can be cached.
Speed settings
| Setting | What it does |
|---|---|
| Load the hero image first | The first image in each page's first section, usually the first thing visitors see, loads right away with high priority instead of lazily. A background image there is preloaded. This improves Largest Contentful Paint, a speed score search engines use. On by default. |
| Inline small stylesheets | Prints the Design System, page CSS and widget styles directly into the page when each is smaller than 16 KB, which saves separate requests before the page can show. Larger files stay separate so browsers can cache them. Off by default. |
| Lazy-load background images | Background images of sections further down the page load only when visitors scroll near them. The first section always loads right away. On by default. |
| Load WooCommerce files only on store pages | Shown when WooCommerce is active. WooCommerce's stylesheets and cart scripts load only on the shop, product, cart, checkout and account pages, on search results, and on pages with a WooCommerce widget (the Mini Cart included), shortcode or block. Other pages, such as the home page or blog, get lighter. Order tracking (where a visitor came from) keeps working on every page. Off by default. |
Click Save changes in the bar at the bottom of the screen after changing them.
The first section is the first section of the page, and the first section of its header and of the template that shows it, such as a single post template. Footers, popups and mega menus never count as the top of the page. Their images and background images load lazily, and Load the hero image first never picks an image from them.
Inline small stylesheets helps most on sites where visitors often see only one page, such as landing pages. On sites where visitors browse many pages, separate cached files can be just as fast. Try both with a speed test. A stylesheet that points to images or fonts with a relative address stays a separate file, so those addresses keep working.
Fonts
Fonts are often the heaviest part of a page. In Settings → Performance & fonts, the Fonts & styles card has Font delivery, which decides where they come from:
| Option | What happens |
|---|---|
| Google Fonts CDN | Fonts load from Google's servers. The default. |
| Self-hosted (downloaded once, no requests to Google) | Uncoder downloads each Google font once and serves it from your site. No requests to Google, which also helps with privacy laws. |
| Do not load fonts | Uncoder loads no fonts. Use it when your theme or a font plugin already loads them. |
Uncoder loads only the fonts and weights your Design System and elements use, and text shows in a fallback font until the web font has arrived, so nothing stays invisible. A Google font the page already requests, for example for the Design System, is not requested a second time for the page or a template that uses it too.
With Self-hosted, Uncoder also preloads your Design System's body and heading fonts when they are Google fonts: the regular weight of the body font and the Heading 1 weight of the heading font, in Latin letters. The browser fetches them right away, so text shows in its own font at once instead of jumping when the font arrives. Custom fonts you uploaded are not preloaded.
Keep the number of font families low: two families (one for headings, one for text) with a few weights are plenty.
Load Uncoder styles on every page, in the same card, loads your Design System on pages that are not built with Uncoder too, so blog posts and other pages match the rest of the site. If only a few pages use Uncoder and the rest use your theme's own styles, you can turn it off to save a request on those pages.
Caching plugins
Uncoder works with page caching plugins such as WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache, WP Fastest Cache, SiteGround Optimizer and Autoptimize, and with host-level caching.
- After you publish or update a page, most caching plugins clear that page's cache on their own.
- After you change the Design System, a header, a footer or another template, many pages change at once. Clear the whole cache in your caching plugin so visitors get the new version.
- If styles look outdated, go to Settings → Tools and click Regenerate CSS, then clear the cache. See Site tools.
- A connected AI assistant can do both in one step: ask it to "clear the cache". It regenerates Uncoder's CSS and clears the cache of the plugins listed above.
Optimization plugins that combine, minify or delay CSS and JavaScript usually work too. If menus, popups, sliders or animations stop working after you turn on such an option, exclude the Uncoder plugin's files in that plugin's settings, or turn off "delay JavaScript" for them.
Tips for fast pages
- Upload images to your media library instead of linking to images on other sites, and use a sensible size: a 4000-pixel photo for a 600-pixel card slows the page down.
- Keep the first section light. It is what visitors see first. One hero image is better than a slider of five.
- Use fewer animations above the fold. Entrance animations on the hero delay what visitors see.
- Measure. Test a page with PageSpeed Insights (opens in a new tab) before and after changes.