by
Tony Hayes
4.7 (3 reviews)
Teleporter
Seamless fading page loading transitions via the Browser History API.
Teleporter ranks #39,782 among WordPress.org plugins with 10+ active installations, a 4.7/5 rating from 3 reviews, and was last updated Jun 2, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Tested up to WP 6.9.9 (Current: 7.1.2)
v1.1.5
Current Version v1.1.5
Updated 3 months ago
Last Update on 02 Jun, 2026
Refreshed 12 hours ago
Last Refreshed on
Top 50% by installs
Rank
#39,782
+977 this week
Active Installs
10+
—
No change
KW Avg Position
100.8
2.8 worse
Downloads
3.7K
+2 today
Support Resolved
0%
—
No change
Rating
94%
Review 4.7 out of 5
4.7
(3 reviews)
Next Milestone 20
10+
20+
26,520
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 8 more installs to reach 20+
Rank Changes
Current
#39,782
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
4.7
3 reviews
Overall
94%
5
2
(67%)
4
1
(33%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.1.5
- Last Updated
- Jun 02, 2026
- Requires WP
- 4.0.0+
- Tested Up To
- 6.9.9
- PHP Version
- N/A
- Author
- Tony Hayes
Support & Rating
- Rating
- ★ ★ ★ ★ ★ 4.7
- Reviews
- 3
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade Now
Frequently Asked Questions
Common questions about Teleporter
Once you have activated the plugin, any internal links on your site will automatically be loaded via page transitions. Visit the plugin settings page to modify the default plugin behaviour.
Teleporter loads new content in iframes within the existing window, then uses the Browser History API to keep track of the content that is loaded. It then monitors the onpopstate event so that browser forward and back buttons continue to load the desired content, with the added ability to fade between them.
Any standard <a> link on the page that:
This is a comprehensive attempt to match and transition between internal links only. (If you think there is something missing here please open a Github issue.)
As of 1.0.4, Teleporter will also handle dynamic link content. That is, links added to the page later. Simply specify the classes of these links on the plugin settings page, and they are then handled with click event delegation (instead of being directly adding to the a link.) So for example, if you have a mobile menu that creates links upon expanding it with a .mobile-link class, you can add mobile-link in the plugin settings. When the mobile menu link is clicked, Teleporter will transition the page as normal. This makes it possible to use Teleporter with frontend builder or frameworks that add their content with javascript. Similarly, if there are links that you wish to force to not transition for some reason, you can use the setting for ignore link classes in the same way. And, if you need to use selectors other than classes for these links, you can use the filters teleporter_dynamic_selectors and teleporter_ignore_selectors to add those respectively also.
As of 1.0.8, Teleporter includes a setting where you can specify pages (by slug or ID) to always refresh when clicked they are clicked through to. This means that if a page already has been loaded in a Teleporter page session, and is switched away from, when it is switched back to, it is reloaded instead of simply switched back to. Intended for use with cart or checkout pages. For example, if a customer visits their cart, then navigates away and adds another product, then switches back to the cart, the cart should be refreshed to show the new contents. Note if there are other non-page URLS (eg. archives) where you want to force refresh also you can set the teleporter_refresh filter to true for that condition.
Prior to 1.1.2, page loads that reach the timeout threshhold are simply transitioned to anyway. Since 1.1.2, the option was added to prompt the user (via dialog modal) to View, Retry or Cancel when the page is taking too long to load. As of 1.1.3, the HTTP response for the URL navigated to is checked via header fetch, and thus the user can also be optionally prompted in the case of page not found (404) or other page load errors.
No. Unlike similar plugins or libraries that use AJAX to retrieve new content and swap it on the current page, Teleporter uses iframes. This may seem a little counter-intuitive since iframes have been around forever and AJAX would seem to be the modern tool for the job. However, loading page content in an iframe means that any scripts loaded within that iframe are correctly loaded by the browser without fail. Using AJAX, there is a risk that the scripts in the current page and the new page are different, which could cause breakage as the new page's scripts are not initialized along with the content, and AJAX page transitioning does not (and cannot) address this issue.
If the page transitions are not working at all, it is likely you have another plugin causing a javascript error. This would prevent Teleporter from loading. Check you javascript console by right-clicking and selecting "Inspect" or "Inspect Element" then choose the "Console" tab from within the developer box. Javascript errors will be shown in red. You can try deactivating the plugin causing the error to see if this resolves the issue and if so report it to the plugin author. If the error is from Teleporter itself, please report it in the Plugin Support forum or via Github Issues
You can run Teleporter in debug mode by appending ?teleporter-debug=1 to any URL on your site. This will load the unminified version of the script and output extra messages to the browser javascript debug console (see previous question.) If you make changes to the development script teleporter.dev.js for testing purposes, you can reprocess that file into minified and unminified versions and debug simultaneously with ?teleporter-minify=1&teleporter-debug=1