Picostrap Keeps Getting Better: Local Fonts, Performance Improvements, and Automatic Updates

Found the right font? You can now bring it home without manually downloading files, writing font-face rules, and wiring everything together.

On WordPress 7.0 or later, choose a supported font in Picostrap’s typography picker, click Host locally, wait for the import and Sass compilation, then Publish. Picostrap imports the files into the WordPress Font Library, enables the family, and switches that selection to local hosting.

Your visitors then load those font files from your own site. Body text and headings remain independent: use hosted fonts for either role, or both.

Need your own files, italics, or additional language subsets? Add or manage fonts opens the native Font Library from the picker. A unified font-loading preview also makes it easier to see which declarations your site is producing.

Some of the most useful work doesn’t need a new button. We revisited how Picostrap handles WordPress’s frontend extras and how the theme’s stylesheet is requested.

Emoji cleanup now covers modern WordPress hooks. We updated the removal of automatic emoji scripts and styles, alongside the existing cleanup of discovery markup and the automatic post-embed script. Normal content embeds and the REST API remain available.

CSS preload now matches the stylesheet URL and version. That helps the browser reuse the intended request. We also removed the blanket preload of the full Gutenberg block stylesheet, allowing modern WordPress to load block styles as needed, and stopped sending theme CSS preload hints for responses that don’t render it.

They’re small corrections with a practical purpose: avoid unnecessary frontend work and make resource loading more deliberate. The result on a particular site still depends on its content, plugins, hosting, and cache. Measure the finished site with your own content and interactions in place.

Picostrap Options has become a clearer place to manage the theme. The reorganized workspace puts design actions, frontend settings, inspection tools, and maintenance within easy reach.

Open the Customizer, recompile Sass, inspect the saved stylesheet, install the starter child theme, or export your theme settings and menus. Related optimization switches are grouped together, using the same settings as the Customizer.

The interface follows WordPress’s light admin styling, with an optional dark mode remembered in your browser. That preference belongs to the tools workspace; the visitor-facing dark-mode switch remains a separate choice.

The overview shows your saved theme CSS and Bootstrap JavaScript sizes, gzip estimates, and a delivery check for HTTP compression. You can see what the theme produces and check how your server delivers it. The panel doesn’t turn on server compression itself.

Analyze homepage previews how much of the saved stylesheet a rendered homepage needs. Running the preview doesn’t change your settings.

There’s also an experimental, opt-in page-specific CSS reduction. It retains matching rules inline and includes a fallback that can restore the complete stylesheet when dynamic content needs it. Plugin stylesheets are separate.

A smaller candidate isn’t automatically a faster visit: cached external CSS can be reused between pages. Try the preview, then test navigation, forms, galleries, and repeat visits before deciding whether the feature suits your project.

The new tools build on the reasons we made Picostrap in the first place: direct access to your design system, readable source, and a workflow you can make your own. These are established favourites, still central to the theme.