Wordpress, the navigator is fast enough to be unconscious

There were too many wordpress stand-alone projects across the screen, and the self-researched saas station system had a shadow of wp, which was an in-depth study。

The best point of pain for independent stations is the link to cardon in the inside of the station for 1-2 seconds, where visitors jump and the rate of exit is high. And preloading is at the core of solving the speed of navigation, allowing the browser to pre-prepared the page and achieve a click response。

Wordpress 6. 8, which directly integrates surmise rule api into its core function, perfects all of the traditional preloaded pits without complex development and zero costs for navigation to be “unsure”。

It's all dry stuff today, from core logic to configuration, validation, customization, one step at a time, and the new guy can do it, and you can speed up your wp station。

I. Traditional preloading: available, but too many pits fit wp extremely difficult

The early prefetch, prerender preloads are all short-walled in the wp ecology, and we've put a lot of holes in our exercise, and it's less than optimal。

♪ prefetch (pre-acquire): save resources, but not eggs? Wp stations are particularly dynamically inactive: static declarations alone, which cannot be triggered by behaviour such as mouse suspension, and the risk of "preloading" invalid consumption configurations being too cumbersome: each page is manually labelled, wp navigation, classification, product pages are heavily linked, maintenance load is doubled

Api: wp standardized preloader

W3c standardized arbitrator api, integrated deep into the core of wp 6. 8, is now the first option for all wp stations to do navigation optimization to directly address all the pains of traditional solutions。

In short, it's a wp station zero-cost, high-reward performance optimizer, open boxes, and flexible customization。

Iii. 2 core configuration methods: fit all wp scenes, code can be copied directly

Presumably, the api interconnected scripts, which are suitable for single page customization, and the http header, which are suitable for a single station-wide rule, can be selected as needed。

Method 1: inline script configuration (recommended, page level custom)

Directly added to the page, with precise exclusions of sensitive links (e. G., shopping carts, log-out pages), electrical and enterprise stations preferred, copying, and changing rules:

Other organiser
"prerender":
other organiser
"where":
"and":
"href metches": "*"
"not": "href masches": "/logout" ,
{ "not": {href masches": *(*)add-to-cart=*},
♪ "not": ♪ "selctor masches": ". No-prender" ♪
"not" : {"sector metches"): [rel~ =novollow"}

♪ i'm sorry ♪
♪ i'm sorry ♪
i don't know.
"prefetch":
other organiser
"urls": ["next. HTML", "next2. HTML"],
"requires": ["anonymous-client-ip-whon-cross-origin,"
"referrer policy": "no-referrer"
♪ i'm sorry ♪

♪ i'm sorry ♪I'm sorry

Method 2: http header configuration (unified site, blog / information station preferred)

Server response header with speculation-rules, using external json rule files to optimize the entire site, suitable for individualized blogs, information wp stations:

Speculation-rules: "/rules/prefetch. Json"

Note: json files need to set mimetype application/speculationrules+json, wp stations can be configured via plugins / themefactions. Php without touching the server backstage。

Iv. 3 step validation configuration: ensure effectiveness and do not waste time

The configuration will be verified, only with the chrome browser operation, and the newcomers will be able to handle it

F12 opens the developer mode, removes the "applied" label, finds the "presumed" rule book, sees the configuration set = the rules load a successfully suspended / clicked link, cuts the "network" label, sees the request header type of prefetch/prerender's request point, shows the sec-purpose: prefetch (pre-acquired)/sec-purpose: prerender = preload effective five, core knowledge point: 2 modes + 4 trigger times, matching as needed

Presumably, api has upgraded the traditional prefetch/prerender and added a trigger-time configuration to balance speed and resource consumption according to the wp site type (blog / electrician / enterprise)。