Well its the api call that is taking much time to get out response.
Its strange how its taking that much time there .
Is it happening for the first time user starts the course or happens everytime ?
You can also enable cache first in service worker : https://www.youtube.com/watch?v=lLDs4Ue1vzU
This is happening to all users every time they log in. Also, the video mentioned here refers to PWA enhancement more than the website.
Well if cache first strategy enabled in service worker and service worker is enabled then this issue should not be replicated .
The api hit fetches from server only first time then its cached in browser itself unless the course curriculum or any of its setting are changed .
This api hit is optimized to its final of its levels and this much time will be taken actually to fetch curriculum and some of the course settings details .
So, you are saying it's at its full potential and there is no way to optimize it anymore?
Yes this much data is needed which we are using in loading the continue course page there.IT fetches basic settings of course and its curriculum title and access details only .
Would suggest to try upgrading the mysql server . As userbase increases and site activity increases this delay could be possible to appear .
.