History back is pretty slow sometimes

When I go back in history by tapping on the back button in the top left corner the app reacts immediately.
When I use the Android back button, which performs a


the app is sometimes slower and takes sometimes a second and more, even on the same page.

Is there any way to speed this up?

1 Like


What is slow? the effect? the process? the execution?

I would say it’s the time until the animation of the closing page starts.

1 Like

try disable animation

Do you have more code in backbutton handler that can cause this?

Also, probably not related but


must be


No, this is the only code in the handler.

I just found out that the delay seems to become longer, the more the page is scrolled down.

Let’s say I have a list of 30 items. When I push on the back button at the top of the page, it closes much faster than when I am at the bottom of the page

1 Like

And if you do it with usual <a class=“link back”> do you see such regression?

1 Like

I checked that for a few pages and even on the very long pages the normal <a class=“link back”> button works very fast.

I did some more measurements and the animations seem to be the reason. As soon as I disable them everything is very fast on any page. Are there any ways to speed up the animations?

Edit: No, and there it is back again… so the animation can not be the reason.

Which one is faster, whats the default you compare ? IOS ? or the browser ?

To be honest I can’t imagine what is happening because usual back link calls same router.back() method. Maybe the issue on Cordova side and it produces the delay of backbutton event? Try to put in backbutton event handler something different instead of router.back, for example, try to call alert there app.dialog.alert and see will it still have that delay?

What happens to the events of the closing page? Will they be destroyed automatically?

Logging only the backbutton event seems to be pretty fast as well. It starts slowing down as soon as I use the router.back() call.

If you assingned them manually, for example like $(...).on(...) then they won’t be destroyed automatically

Good to know, maybe this is somehow related as there are a lot of manually assigned events on these pages. Is there any F7 way to remove all events on a page?


is throwing an error:

Uncaught TypeError: Cannot read property 'split' of undefined
at Dom7.off (framework7.min.js:12)

I have a similiar problem. There is no issue when I move forward through pages. But the problem comes up when I move back through some pages. I attached a screenshot about page async event. There is a timetable that shows async event’s start and end times. Please attention rayon page’s load and back load times. When I click the back button, I wait 4 seconds to see the rayon page.

Here is rayon page’s async event codes:

    name: 'rayon',
    path: '/rayon/:mid/',
    async: function (routeTo, routeFrom, resolve, reject) {
        if (!isConnectToInternet()) return;
        var router = this;
        var app = router.app;
        var marketid = routeTo.params.mid;
        var apptoken = user.getAppToken();
        var mobiletoken = user.getMobileToken();
        console.log("rayon async started at: "+Date());
            success: function (data, status, xhr){
                console.log("rayon async stoped at: "+Date());
                if (data.result=="1"){
                        { componentUrl: './pages/rayon.html' },
                        { context: {data: data} }
            error: function (xhr, status){
                var error_message=status;
                if (statusErrorMap.hasOwnProperty(status)) error_message=statusErrorMap[status];

Issue apparently in XHR request, check in Network tab, how long takes this request in this case?

Here is the related page statistics in network tab. This page includes xhr object that load data via php file. What should I learn from these results? How can I find the thing that causes slowdown?


1 Like

It means your server takes a lot of time to respond to request ~ 4.32s, so you need to optimize on server side. Not related to Framework7

1 Like