NEW ONE


API  | Pagespeed | Performance 


Regarding the deprecated APIs warning: that's unfortunately a result of our script's age, as it was developed several years ago. To tackle this, our product team is actively working on rebuilding the endpoint with a more modern approach, aligning with current web standards.



Regarding the reported slowdown in website performance: our analysis suggests that while Fareharbor contributes to some extent, it's not the primary factor. For instance, optimizing image sizes and especially formats, as well as minimizing code, could significantly improve page speed. In terms of integration and performance enhancement, we unfortunately can't do much. One approach for them would be to remove our API, thus the lightframe popup, and have all links open in new tabs. Then repeat the PageSpeed Insight again.  This would isolate the impact of the API on page speed.




https://pagespeed.web.dev/analysis/https-www-letzgocitytours-com/rvtq89dt91?form_factor=desktop this is the analysis I based my notes on



**********************



Regarding Core Web Vitals, in the test I conducted that part seems okay, but nonetheless FH integration is rarely the deciding factor, and if the score is low we have little impact on it.
Typically, with well-optimized sites, it makes little difference whether our API is present or not.
As for the rest, links and buttons do not cause significant slowdowns.
They can always temporarily remove our API and run a test to understand how much our integration affects the final result.
However, it's also worth considering that their homepage is really heavy on content, which can have a significant impact.