Benefit with compromise?

Not sure how you tested, but to be sure I re-ran a simple test on a page with a normal YT embed and one with Lyte (with page caching & css/js optimization active).

The result;
1. normal embed testresult
time until document complete: 1.811s
bytes when document complete: 404KB
time until fully loaded: 2.129s
bytes when fully loaded: 421KB

2. lyte embed testresult
time until document complete: 0.342s
bytes when document complete: 15KB
time until fully loaded: 0.597s
bytes when fully loaded: 35KB

So a page with a lyte embed is approx. 4 times faster (and a requires a significantly less data to be transferred) then the same page with a normal YT embed.

Not sure what you mean with the last remark; as you can here, lyte does load the image, no idea how user experience would be compromised. Could you elaborate?

frank

Ok, seems like i used the wrong judgement. I based it upon speed of my own loading which is at 1mbps and both appeared at almost the same time. But you will initially see the page load already before the player does, and eventually youtube loads everything async in the background which users aren’t likely to notice it.

And for the image preview, i did a few test and it was inconclusive. I had 2014 theme loaded at first, posted link, no image.

Then I switched to 2012, load it, image appears, switch back to 2014 and image stays there.

pre switch:
beachweddingcakes dot org/t3/

after switch:
beachweddingcakes dot org/wp-yt-test/

The above was done with 3.8.3

On 3.9.1 2014 theme both produced no image.

ok, https://futtta.be/wordpress/blog/2012/04/02/wp-youtube-lyte-embed/ switched my testblog (wp 3.9.1 multisite) to twentyfourteen, all works OK there, so I have no immediate idea of what is going wrong.

what is the exact link (code) you have in the article (the one with Radiohead for example)?

in the wp yt test page httpv://youtu.be/1kfXOHohijo
in t3 httpv://youtu.be/57q2uFaMjNs

when you switch over to 2014, you have to post a new video ( i assume new link ) and it wont load. but if you switch back to 2012, you must load the page first on your browser before switching to 2014 otherwise the image also wont appear.

for some reason t3 is cached now, don’t know if it’s because i visited your site thus it is “cached”.

created /t5/ httpv://youtu.be/2xd2SE-kieU

tested your t5-vid on my blog straight in 2014, works fine.

But your latests comment helped a lot, I now understand what is going on. The problem is that the Lyte-code contacts the YouTube api to fetch all kinds of information (title, thumbnail image, description, …). If fetched successfully, that information is stored in Lyte’s cache. If the information cannot be fetched however (Lyte on the server not being able to contact https://gdata.youtube.com/feeds/api/), you get an empty lyte player (no title, no thumbnail). Lyte will try to contact youtube on every request and when succesful (e.g. for your t3 now) will cache the information and all is fine.

So bottom line; there must be something that limits outgoing requests on your server which stops Lyte from fetching information from the YouTube API.

frank

Your comment about my server stopping communication helped me solve another mystery i have since a long time.

I tried embedding it using the default wp embed method which is pasting the url without hyperlink but it wouldn’t show the video.

I’m contacting my server at the mean time, but for some reason i don’t think the server has any fault. It just doesn’t make sense when the iframe embed works.

Oh and, switching to 2012 theme, the default embed works, as well as your plugin, but not 2014 theme. Now things got more complicated and the question of why 2014 theme, and what does that have to do with my server config?

i don’t think the server has any fault. It just doesn’t make sense when the iframe embed works.

On the contrary; lyte and the default wp embedding (oEmbed) relies on your server being able to communicate with youtube, whereas the iframe-method only relies on the browser (so no server-side communication).

As far as 2012 vs 2014 is concerned; no idea whatsoever I’m afraid, that really should not make any difference and Lyte indeed works perfectly on my test-blog with 2014?

Just figured that I update this thread. My server didn’t want to settle the problem and instead want to charge me a separate fee for it. If anyone wants to know, it’s stablehost . Gotta let the whole world know they are just being stubborn and ignorant.

After digging the oembed stuff, there’s only 2 reasons why my site returned nothing.

1.
Problem with API rate limiting (server denied it’s happening)

2.
Problem with WP not flushing the cache (because when I republish it, the video pops up, but sometimes it just doesn’t at all). Again, the server has fault, and they also denied it.

So I’ve come into conclusion that my server is hammering the providers and thus the API is rate limiting the IP. And secondly, my server config isn’t flushing the cache properly.