Fixing Slow Redirects on Linkly
Some features on Linkly necessarily slow down redirection performance, as third-party tags take time to run in the user's browser.
Disabling these features will significantly increase the redirect speed.
What features slow down redirects?
Linkly features that involve firing javascript tags when a user clicks a link will inject a 0.5 second delay before the user is redirected.
These features are:
- Google Analytics
- Meta Pixel
- X Tailored Audiences
- Retargeting/remarketing tags
- Custom Social Media Previews
Disabling these features will mean redirects are server-side 302 redirects and near instantaneous.
Why do javascript tags slow down redirects?
These features require us to show a blank interstitial page when the user clicks on a link, so that the tags that make these features work can be fired.
The blank page is shown for 0.5 seconds to give the tags enough time to call back to their respective services (e.g. Google Analytics, Meta Pixel), before the user is finally redirected.
Frequently Asked Questions
How much slower are redirects with tracking tags?
Redirects with JavaScript tags enabled take approximately 0.5 seconds longer than standard server-side redirects.
Can I use Google Tag Manager instead to avoid the delay?
Yes. Using Google Tag Manager on your destination page instead of Linkly's built-in tracking avoids the redirect delay while still allowing you to fire tracking pixels.
Do custom social previews also cause delays?
Yes. Custom social previews require an interstitial page to display OpenGraph metadata, which adds a small delay before redirecting.
Is 0.5 seconds noticeable to users?
Most users won't notice a half-second delay. However, if speed is critical for your use case, consider using server-side tracking or moving your pixels to the destination page.