johan
37e5497923
Drop the redundant documentation/marketing/ nesting inherited from the plugin repos, so files sit at marketing/<plugin>/<page>.md. These paths become raw URLs pasted into Elementor pages and ACF fields, so they are much cheaper to change now than once sites reference them. Fixes the four cross-plugin links for their new depth, and corrects the README, which still pointed at the abandoned per-repo documentation/ folders instead of this repo. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
20 lines
1.3 KiB
Markdown
Executable File
20 lines
1.3 KiB
Markdown
Executable File
# Preloading
|
|
|
|
Stop waiting for the browser to discover what it needs — tell it in advance.
|
|
|
|
## The problem it solves
|
|
|
|
Browsers work through a page's resources largely as they discover them, request by request. That discovery process itself takes time, and for the resources that matter most to how fast a page *feels* — your hero image, your web fonts, the third-party services your theme relies on — that delay is pure waste.
|
|
|
|
There's a second, quieter problem too: the very first visitor to a freshly published page pays the full "build this page from scratch" cost, because nothing has been cached yet.
|
|
|
|
## How it helps
|
|
|
|
Dotjuice Pagespeed tells the browser exactly what to prioritise: your designated hero image loads with maximum urgency, key web fonts are preloaded before they're needed, and connections to services you actually use (analytics, fonts, embeds) are opened in advance rather than discovered mid-page.
|
|
|
|
On the server side, the moment you hit publish, the plugin quietly visits the new page itself in the background — so by the time a real visitor arrives, the cache is already warm. And with one click, you can do the same for your entire site at once.
|
|
|
|
## The result
|
|
|
|
Your most important image and fonts, prioritised instead of left to chance — and a cache that's always warm before a real visitor needs it.
|