: Leverage browser caching for Facebook, Google+, or other 3rd party resource files I tested my website with Google PageSpeed Insights. I did cache optimization in my .htaccess, but it didn't affect
I tested my website with Google PageSpeed Insights.
I did cache optimization in my .htaccess, but it didn't affect resource files that are from Facebook and Google+
Leverage browser caching
connect.facebook.net/fr_FR/all.js (20 minutes)
apis.google.com/js/plusone.js (30 minutes)
oauth.googleusercontent.com/…e:rpc:shindig.random:shindig.sha1.js?c=2 (60 minutes)
What can I do to solve this?
More posts by @Candy875
3 Comments
Sorted by latest first Latest Oldest Best
It is a high level conspiracy by web market icons like Google and Facebook.
I was using these scripts on my website which caused it to work slowly. When I removed the scripts, it achieved my goal (i.e. page speed 100/100). My site is now performing very well. It opens almost like it is AMP supported.
So page speed matters. I think you should stand on your own not by holding Google or Facebook's hand. Just remove the code. Your subscribers needs site performance but performance starts with website loading. If you are loser from beginning, there is no way to come first in any search engine in the world. If users come first on your website, no search engine can put you behind cause you start making challenges for search engines.
So my suggestion is remove the scripts and make your own for better user experience.
You should consider removing third party JavaScript from Facebook and Google from your pages. The only third party JavaScript I typically have is for advertising.
All of the social networks have ways that you can use plain links (no JavaScript) to share your page. See this question on StackOverflow. You wouldn't be able to see stats for likes and +1 in the page though.
You have no control over them because they are hosted by another provider. And honestly speaking you should not worry about them, it's up to Google, Facebook, etc to handle the caching accordingly to their need.
You could potentially proxy the URLs or download the files locally, but I don't encourage you to follow that route. In fact, you may potentially end up with a configuration that do not reflect the changes when the upstream provider publish an update, or simply conflict with the caching already applied by Google, Facebook, etc.
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.