Website Slowness

[Andyjr94]

It seems that the issue has gotten enough attention as they have now acknowledged the issue on their X account.

[Mike]

It seems that the issue has gotten enough attention as they have now acknowledged the issue on their X account.

The issue is not identified. There has been 15-20 people contacting FR24 via support and social media, 1 or 2 videos have been provided but most people just ignore to supply more information. So the issue can't be identifed before we get more information.

[Mike]

A few days ago the website version of FR24 started lagging when I click on an airplane. It doesn't show the flight info or path for up to a minute while it appears to load the info. Is this a known issue or something just local to my laptop.

This topic is about this problem. Off topic posts have been removed. If you want to report other problems, please create a seperate topic.

[Higgi]

I just made a ticket via support@fr24.com
will see the response to this problem

[nodawg]

It is still unusable from any browser I use.

[VOHY]

It is still unusable from any browser I use.

Yes, Chrome is completely broken. It's like a slide-show trying to do anything with the map like move it, zoom in/out. Support staff still in denial "we were unable to replicate the issue". They just delete all your posts now if you complain.

[nodawg]

I have had to switch to AirNavRadar but I really don't like it close to as much. Its a shame.

[Mike]

Yes, Chrome is completely broken. It's like a slide-show trying to do anything with the map like move it, zoom in/out. Support staff still in denial "we were unable to replicate the issue". They just delete all your posts now if you complain.

As I have told you many times, you are very, very welcome to post problems on the forum. But this thread is about a very specific CLICK problem (not zoom or map pan), introduce with a release in February, that we have not been able to identify yet. It makes identification much easier if we can keep this thread on topic instead of posting every issue in the world here. If you have other problems with FR24 feel free to post a new topic.

The only clue we have right now is that it's in some way releated to the network setup.

And just to get some perspective on the problem, we have received about 25-30 tickets out if 25-30 millions monthly users. Some have been able to resolve the problems by doing different updates to theirs systems.

[Andyjr94]

It’s been almost a month and still no resolve for the lagging of data loading on their web version. I can’t believe it’s gotten to this point.

[SlackDarren]

I think after the unfriendly response from FR24, I shall be voting with my feet.

[Vector4traffic]

As I have told you many times, you are very, very welcome to post problems on the forum. But this thread is about a very specific CLICK problem (not zoom or map pan), introduce with a release in February, that we have not been able to identify yet. It makes identification much easier if we can keep this thread on topic instead of posting every issue in the world here. If you have other problems with FR24 feel free to post a new topic.

The only clue we have right now is that it's in some way releated to the network setup.

And just to get some perspective on the problem, we have received about 25-30 tickets out if 25-30 millions monthly users. Some have been able to resolve the problems by doing different updates to theirs systems.

Long time user and happen to be checking the web version of FR24 can confirm that the click issue is there. If I hover over a plane the "hand" never changes to a "pointer" and the Firefox (137.0 (64-bit)) console log confirms that the no JS is running upon clicking the plane, only the regular "livefeed" is running. If I click on the map it takes ~4-8s before the "Setting Weather Filters..etc" pops up at the bottom.

Here are some logs from the FF console:

09:38:50.867 WEBGL_debug_renderer_info is deprecated in Firefox and will be removed. Please use RENDERER. webgl.js:54:377
09:38:50.889 WEBGL_debug_renderer_info is deprecated in Firefox and will be removed. Please use RENDERER. luma.gl.js:810:76359
09:38:56.936 WebGL warning: texSubImage: Texture has not been initialized prior to a partial upload, forcing the browser to clear it. This may be slow.
09:38:56.936 WebGL warning: texSubImage: Tex image TEXTURE_2D level 0 is incurring lazy initialization.
09:38:57.753 Google Maps JavaScript API warning: RetiredVersion https://developers.google.com/maps/d...etired-version util.js:82:65
09:38:58.854 WebGL warning: texSubImage: Texture has not been initialized prior to a partial upload, forcing the browser to clear it. This may be slow.

[Vector4traffic]

Turns out the Web app has incurred some significant graphical driver changes that are out lined in the thread "No aircraft on map or airports in Chrome and edge browsers" and relates to the console logs I posted above.

[HikokiOtaku]

I have had this issue as well since the graphical updates. No response when clicking on planes or very laggy response (using Chrome on a PC).