Big Issue with javascript and admin panel refreshing

[shimei]

Originally Posted by Max Taxable

Yeah, that old article is crap. They later ADMITTED CF screws with the handshake. Plus, they don't understand what is happening in request #1 - this is where the server queries the code, scripts and database to create the executable page source code file, and uploads this to the browser to execute. It's no mystery anymore why this file is so much larger and takes a lot longer to compile when you have a CDN. Request #1 IS the FBT. It's not even a debate anymore and ceased to be one some time back.

Are the issues you're stating still accurate? I don't how accurate WebPageTest is but I just ran my site through WebPageTest and came out with a first byte time of .401s and second repeat view of .269s. The site scored an A for first byte time.

This is through Cloudflare: http://www.webpagetest.org/result/160128_YG_9SK/

[Max Taxable]

Originally Posted by shimei

Are the issues you're stating still accurate?

Yes they are and in fact, I was able to successfully lobby Patrick Meenan to adjust WPT so it doesn't assign really low target first byte times to sites that have CDNs. That is why now we get a artificial score on FBT for sites using CDNs. WPT changed the way it handles CDNs, that does NOT change the issue CDNs create with FBT.

Here's what you really look like, use IE 11 only as the test browser, for worst case. Firefox and Chrome skip certian types of calls to make themselves appear "faster" to the end user.

http://www.webpagetest.org/result/160128_F8_AW6/




It's not open to debate, CF acknowledged it. It's simply a fact. But like any other religious belief, no amount of facts can persuade a CF evangelist.

[shimei]

Originally Posted by Max Taxable

Yes they are and in fact, I was able to successfully lobby Patrick Meenan to adjust WPT so it doesn't assign really low target first byte times to sites that have CDNs. That is why now we get a artificial score on FBT for sites using CDNs. WPT changed the way it handles CDNs, that does NOT change the issue CDNs create with FBT.

Here's what you really look like, use IE 11 only as the test browser, for worst case. Firefox and Chrome skip certian types of calls to make themselves appear "faster" to the end user.

http://www.webpagetest.org/result/160128_F8_AW6/

Thanks Max.

[Max Taxable]

Originally Posted by shimei

Thanks Max.

When I got CF to admit the issue, and got Meenan to CHANGE WPT, pretty much case closed. Wouldn't you say? I got tired of wasting mine and other people's time over FBT on sites that use CDNs and in the process, ended the debate.

Originally Posted by shimei

I don't how accurate WebPageTest is

It is the ONLY test site out there that uses real browsers, real connections and is REAL WORLD scientific testing.

[Max Taxable]

More edification. Long read but very educational:

https://thethemefoundry.com/blog/why...-cdn-spdy-ssl/

On the second line, SSL negotiation time is bothersome. This line represents the download of our site’s CSS file from MaxCDN’s servers. This request involves a DNS lookup (76ms; blue-green), a TCP connection (110ms; orange), an SSL negotiation (429ms; purple) and the content download (243ms; bright green). Notice that the SSL negotiation was roughly 4 times the length of the initial TCP connection. Clearly, the SSL negotiation is not well tuned. We spent a lot of time tuning our SSL connection for speed and now we are suffering from slow SSL negotiation on the CDN. This was not the result I was hoping for when we implemented the CDN.

Another thing to note about the CDN performance (items 2-13, 15-16) is that this negotiation is repeated 3 times. Additionally, we incur extra DNS lookups, which slows our asset loads. Fortunately, the last time, I believe that the SSL negotiation uses SSL resumption and it is much quicker. Finally, notice the diagonal waterfall of the elements. We are seeing the same serial download pattern that we saw in our pre-launch site tests.

[RichieBoy67]

Originally Posted by shimei

For your admincp...

I had the same issue. You have to create a page rule in Cloudflare. Create a rule for your admincp, mine is as following: http://yourdomain/admincp/index.php*

The above rule was for my Vb5 site, I don't know whether your admincp is using a different url. Just basically disable all caching and performance related options for admincp in your page rule.

Regarding issues with other parts of the site... there's a performance option in cloudflare that is beta... it is under the speed category and is called "Rocket Loader". It caused all kinds of issues so I turned it off.

Thanks, I will try that though the issues has gone away since I turned off Rocketbooster..I think that thing has been in beta a long time.

I just wasn't sure which setting was causing the issue at first so I disabled everything and turned them on one at a time. All seems ok now.

--------------- Added [DATE]1453972257[/DATE] at [TIME]1453972257[/TIME] ---------------

Originally Posted by Max Taxable

More edification. Long read but very educational:

https://thethemefoundry.com/blog/why...-cdn-spdy-ssl/

Well the site in question usually takes around 5 seconds for first page load depending on what page is visited. It is heavily customized and very media heavy. I would like to get the speed down but I have done pretty much what can be done without re-themeing.

As for Cloudflare, I really switched to it because I needed a free external dns and they seemed pretty solid. Like I said, I have not noticed a difference in first time page load but once cached i have noticed a much faster load time so far.

Some of the options are pretty decent as well like the smart error page. if someone gets a 404 they will get an error page with a search of your pages related to what they were visiting. That is pretty awesome.

Thanks for the research. I will definitely check it out. I am always happy to learn more.

[final kaoss]

Richie, one thing you can do is increase the caching of static content beyond 5 hours for repeat visitors.

You have a 404 to fix as well http://www.webpagetest.org/result/16...P3H/1/details/

[RichieBoy67]

Originally Posted by final kaoss

Richie, one thing you can do is increase the caching of static content beyond 5 hours for repeat visitors.

You have a 404 to fix as well http://www.webpagetest.org/result/16...P3H/1/details/

Thanks!

Funny you mentioned that as I had increased that already from 4 to 5 upon set up.

I am checking that link right now! I am sure we have a few of those kicking around..

--------------- Added [DATE]1453985467[/DATE] at [TIME]1453985467[/TIME] ---------------

I removed the ssl image thing as the javascript was slowing the entire site load.

I am looking at the tag cloud. I think it is the style cache. I wll just turn it off for awhile I think. I recently cleared all the tags and there are only a few now..The rest must be stuck in the style cache.

[final kaoss]

You could probably get away with caching js/css for a month or two and the images for 1-2 weeks.

[RichieBoy67]

Originally Posted by final kaoss

You could probably get away with caching js/css for a month or two and the images for 1-2 weeks.

Actually I was just about to make a new thread about this very topic but seeing as it is related we may as well discuss it here if ok with the mods.

In regards to caching I am still trying to figure out how to do this properly with Cloudflare. With the free account caching options are very limited.

Are you referring to htaccess because those settings are bypassed now by cloudflare. I can set a longer time but the only other options are:
No Query String
Ignore Query String
Standard

I currently have standard set.

I know there are ways to link my images directly from the cdn or use my own ip address which would then use my htaccess but that would remove the security.

#Question.. I have a mail server set up through my domain and ip and the record is in cloudflare. Do I need this record there? It is a security vulnerability as it allows people to see my ip directly.

Thanks!!

--------------- Added [DATE]1454066040[/DATE] at [TIME]1454066040[/TIME] ---------------

Going to create a new post. Having more problems.