remove query string from Fv-flowplayer custom/JS

Hi Martin,

The FV-flowplayer file is the only file (out of many dozen) which the query string is not removed by 3rd party plug-in. It is interesting and odd to find out why your product does not conform like the others. It is the only file left and which fails for query string removal in testing results with pingdom or GTMetrix. You can run these test and see results for http://fritzimages.com. Additionally, your file prevented rendering in webmaster tools of part of my site and I had to add file path to robots.txt to open up the rendering. I do not know why these fv-flowplayer files are different.

to answer your Q:

I am using other plugs which remove query strings. Speed Booster Pack which has option to remove query strings. It does a very good job. I have also deactivated Speed Booster Pack and activated Remove query stings from static resources plug in…it behaved the same way as Speed Booster pack, which was the FV-Flowplayer query string is not removed. Somehow it seems it is in a location or being protected from these plugins. I have spent many hours activating and deactivating and flushing out caches and retesting results with pingdom to try and isolate problem Nothing I did could remove your file strings (path noted in opening thread). Then following your instructions they could not remove your file string ( a new path was generated as noted in last posting http://fritzimages.com/blog/wp-content/plugins/fv-wordpress-flowplayer/css/flowplayer.css?ver=2.3.16). Why this query string is being generated which is different from the first is just plain interesting to me. Maybe you can tell me what is going on after I follow you instructions ? I’m not really that worried about this, it is the only nonconforming plugin query string I have. I thought I’d bring it to your attention and see if you can find out why your product is not behaving like everyone else’s on my site. There is probably a simple answer somewhere :). You make a great product and have great support and continue to update and keep your plugin active…

thanks,

Hello Ed,

thank you for the details.

What GTMetrix says is:

Resources with a "?" in the URL are not cached by some proxy caching servers.

So it doesn’t say the caching doesn’t work for everybody, it might occur when using a proxy server. Our system works, as you can still set the caching as you want on your web server. Then when a new version of our plugin is out, the ?ver= in the JS URL changes and the browser knows there is a new version of the file and that it should use that.

Originally we didn’t used this, but then we had to start using it as people had issues after updating our plugin – we had to always ask them to clear the browser cache etc.

As a test, you can try to store the raw HTML of your page, remove the query string there and then save it on your server and run a test on that. You will see how much the score improves.

I see the Webmaster Tools issue – it’s something which we had to fix for some of our websites as well.

I’ll check “Speed Booster Pack” and “Remove query stings from static resources” plugins.

Thanks,
Martin

Hi Martin,

I really would like some more help on this. This plug-in CSS path: http://fritzimages.com/blog/wp-content/fv-flowplayer-custom/style-1.css?ver=1436580848
Stops my website rendering by about 1 full second. Which is an ugly truth…and just not acceptable… We have got to come up with a way that this CSS this does not load at top of the waterfall stack. I can not figure out a way. It does not need to be loaded so early and my attempts to find a way to fix it are exhausted. I also think it is irrelevant to have ? and versions number on CSS. Please look into this for me…I would like to have that info stripped away….

2nd Problem:
Your recent release now creates HTTP 400 error with W3TC. This version CSS file can not be minified and is not compatible as CDN in Pingdom waterfall show as error and HTTP 400 also I have w3tc emails set to notify me of minify errors and my inbox is getting full of the emails.

I have tested my videos using a competitor product plugin and they do not have the issue of blocking site rendering. I use a lot of plugins and their CSS is minified using Speed Booster Pack…for some reason your product is not performing like the other products…..

So to recap:
1) Latest release throwing HTTP 400 Error on CSS being minified for CDN using w3tc.
2) CSS blocking page rendering for web site. Site loads 1 Second Faster with FV disabled.
3) No solution to put CSS below the line for rendering.
4) Product does not perform like other WP peer plugins for CSS using Speed Booster Pack or remove query string from static resources….

Could these issue be address with someone in your software team in a timely manner,

I have not heard anymore about this for three weeks….

thanks,,

Ed

Hi Martin,

I discovered that if I use W3TC to minify and use my CDN that I would get HTTP 400 error. Further researched and I discovered that W3TC can not minify url with ?version numbers. I deactivated using minify on your CSS. This returned google and Pingdom scores near previous. I think I’m going to fallback to an earlier version of FV. Your previous FV release did not have custom CSS ? version numbers. I will read your link.

Yes, that little bit of code blocks page from rendering. I ran 4 or 5 Pingdom tests. Then I noticed the HTTP error emails from WT3C, so I am concluding that FV added a new ?version number in the custom.css file name which caused the HTTP 400 error which caused the delay time. I decided to discontinue minifying FV custom CSS anymore.

My Plan is to read your link info, double check how I can prevent static content in w3tc. Then decide coarse of action. a) fallback to earlier FV. 2) reconfigure w3tc then test results…. My goal is to remove FV customs css from blocking page rendering.. One way or another…. All other CSS on my site is below the line and compatible with Speed Booster pack . For some reason your engineers are putting your custom.CSS in the header(?) or on top of file and that is not where it belongs for my application.

thanks,
Ed

Hello Ed,

please upgrade to FV Flowplayer 2.4. We reworked how the CSS is loaded and now the Speed Booster Pack plugin removes the version number successfully.

Please let us know if it works for you as well. Also let us know if you need help with the W3TC issue.

Thanks,
Martin

Hello Ed,

I’m glad it works, we will keep these requirements in mind.

Thanks,
Martin

Hi Ed,

I’d suggest watermarking and then using TinEye.com. Without watermarks, you can sue people like Getty Images and make more money that way than with legitimate paid photographic gigs.

Making the web work for you, Alec