Performance

Promptless WP loads only the styles and scripts a page’s sections need, sizes and prioritises section images, and preloads the hero image. The rest of a page’s speed depends on things you control: the images you upload, your host and your page cache.

What Promptless WP does on every page

What	How it works
Styles per section type	Each section type has its own stylesheet. A page loads a shared base stylesheet plus the stylesheets for the section types on that page, and nothing for the rest. Pages without Promptless sections do not load the section stylesheets at all.
No duplicated styles	Post Grid, Product Grid and Map build on the Features styles. They load the Features stylesheet once, as a dependency, instead of each carrying a copy of it. A page with Features and a grid loads the Features rules once.
Scripts only when used	The gallery lightbox, the Post Grid filter, maps, the video lightbox, modals, carousels and scrolling logo strips each load their script only on pages that use them.
Hero image preload	When the first section on a page is a Hero with a background or featured image, the page’s <head> tells the browser to fetch that image first, at high priority. For a featured image it names the same size the page will display, so the image is not downloaded twice.
Image sizes and lazy loading	Section images from the Media Library are sent with their smaller sizes and their dimensions, so a phone downloads a phone-sized file and the page does not jump as images arrive. The first section’s hero image loads immediately; images further down load as the visitor scrolls.
Maps and video embeds	Map and video embeds are loaded lazily, and a Map section can be set to load only when the visitor clicks it. See Map sections.
Cache-safe updates	Each stylesheet’s address changes when the file changes, so after a plugin update visitors and CDNs get the new file rather than a stale cached copy.

Note

If an image optimiser such as EWWW rewrites images into WebP <picture> elements, Promptless WP skips the hero featured-image preload, because the preload would fetch the original file that the page no longer shows. Background-image preloads are unaffected.

How it is measured

Before release, Promptless WP’s demo pages are measured with Lighthouse, the tool behind Google PageSpeed Insights, on a simulated slow mobile connection. Each page must meet Google’s Core Web Vitals “good” thresholds:

Measure	Threshold
Largest Contentful Paint (the main image or heading appears)	2.5 seconds
Cumulative Layout Shift (the page jumps while loading)	0.1
Total Blocking Time (the page is slow to respond)	200 ms
First Contentful Paint (something appears)	1.8 seconds

These are lab measurements of the plugin’s own pages. They show that the plugin’s output is fast; your site’s numbers also depend on your images, host and other plugins. To check a page on your site, run it through PageSpeed Insights and read the mobile result.

What you control

Images

Images are the most common reason a Promptless page misses the thresholds.

• Upload through the Media Library. Promptless WP can only send smaller sizes for images WordPress knows about. An image pasted as an external URL is sent at full size.
• Resize before uploading. A hero background rarely needs to be wider than 1920 pixels. Very large photos make WordPress’s generated sizes larger too.
• Use a modern format. WordPress accepts WebP uploads, and image-optimisation plugins can convert your existing library. WebP files are usually much smaller than JPEG at the same quality.
• Keep the first section light. The hero image is what visitors wait for. A text-only hero, or a smaller hero image, is the quickest win on a slow page.

Hosting response time

Nothing on the page can start until your server answers. PageSpeed Insights reports this as server response time. If it is slow on every page, including pages without Promptless sections, the fix is at the host: a faster plan, a current PHP version, or an object cache.

Page caching

A page cache stores the finished page so the server does not rebuild it for every visitor. Promptless pages are ordinary WordPress pages and work with page-cache plugins and host caches. After you save a page, your cache plugin or host decides when visitors see the new version; if an edit does not appear, clear the page cache there.

Promptless WP’s own Cache Management screen (Promptless WP → Cache Management) is not a page cache. Its Clear AI Cache button clears saved AI responses only; it has no effect on page speed or on what visitors see. See Plugin Settings.

Limits and common problems

• The mobile score is low but desktop is fine. Usually the hero image. Check its file size and format first, then your server response time.
• PageSpeed Insights names “render-blocking resources”. Stylesheets from the theme and every plugin are counted together. Check which files it lists; Promptless WP’s are the ones under ai-section-builder-modern/build/.
• Visitors see an old version of a page. A page cache or CDN is serving a stored copy. Clear it in your cache plugin or host panel.
• Scores vary between runs. Lighthouse results move by a few hundred milliseconds from one run to the next. Run a page two or three times before acting on one number.

Related pages

• Working with WordPress Themes — How Promptless WP pages sit inside any WordPress theme, the three display modes, and when the Promptless theme's own templates are used.
• Plugin Settings — Every Promptless WP screen in wp-admin, what each option changes, and where the settings that are not in wp-admin live.
• Troubleshooting — What to do when sections do not show, edits do not appear, the editor will not open, or a Promptless WP feature stops working.