Something is adding a small bit of code (i.e. ?f3dcbc
) to your images – which works fine on your own server – but breaks the Twitter image server.
Might it be W3 Total Cache? If it is, there’s a shortcode that allows Rotating Tweets to use fragment caching – which might solve the problem.
Otherwise, I can only suggest testing different variable settings on W3 Total Cache and/or seeing what happens if you switch different plugins on and off – so that we can find what’s clashing and how to fix it!…
Where can I find that shortcode?
It’s w3tc_render_to
and it’s here!