At its core, Quicklink is a silent observer, that works in three simple steps:
Observation: Quicklink keeps an eye on which links are currently visible on the webpage as a user scrolls.
Proactive: Quicklink proactively fetches the content for links it sees that matches specific criteria. It does this quietly in the background, choosing moments when it won’t slow down the user’s current activities.
Ready: By the time a user decides to click on a link, Quicklink has already fetched the content for that link. The result? Pages load significantly faster, almost as if Quicklink knew where the user would click next, but really, it’s just been preparing all along.
What it looks like
Behind the scenes, you can see Quicklink initiating the fetching of content, from links that match the criteria. Quicklink for Blocs is designed out of the box to take a balanced approach.
It’s a no-brainer and in the pocket.
If you haven’t been utilizing Quicklink until now, you’ve been missing out significantly. Previously, integrating it was a cumbersome process, but now it has been simplified to a tickbox.
This runs the script locally, so no issue. If it was running through a CDN connecting to an external source that might be different. I’ve been using QuickLink for years and it makes web pages a whole lot faster to load in a way that Google approves. This bric simply makes it easier to install and configure.
Thanks Alan (@KBConcepts), I appreciate that. A few more things coming out the pipeline soon. I am most excited about one in particular. It should add some much requested abilities.
