Title: First Byte Time Problem Last modified: November 25, 2017 --- # First Byte Time Problem * [uggur](https://wordpress.org/support/users/uggur/) * (@uggur) * [8 years, 6 months ago](https://wordpress.org/support/topic/first-byte-time-problem/) * Hi, * First of all thank your for this great plugin ^.^ * I just started to use this pluging instead of wp-super-cache, then my sites “ First Byte Time” values jumped. * For instance: [https://www.webpagetest.org/result/171125_PX_a6cccc0b7f52985b57888c118067f577/1/details/#waterfall_view_step1](https://www.webpagetest.org/result/171125_PX_a6cccc0b7f52985b57888c118067f577/1/details/#waterfall_view_step1) * I changed cache plugins to this one because of webp and also I bought “Optimus” plugin licence; but as I said that the only problem is “First Byte Time” jumped. * Before cache enabler, my old “First Byte Time” score is ok. The only changes is I removed wp super cache, than I install cache-enabler and optimus. * Could you examine your code and if there’s optimizations/improvements for codes, I can wait to new release; otherwise I’ve to re-install other plugin 🙁 - This topic was modified 8 years, 6 months ago by [uggur](https://wordpress.org/support/users/uggur/). * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Ffirst-byte-time-problem%2F%3Foutput_format%3Dmd&locale=en_US) to see the link]_ Viewing 8 replies - 1 through 8 (of 8 total) * Thread Starter [uggur](https://wordpress.org/support/users/uggur/) * (@uggur) * [8 years, 6 months ago](https://wordpress.org/support/topic/first-byte-time-problem/#post-9723449) * Edit: Ohh shit! That problem fixed a little bit with advanced configuration. * [https://www.keycdn.com/support/wordpress-cache-enabler-plugin/#bypassing-php](https://www.keycdn.com/support/wordpress-cache-enabler-plugin/#bypassing-php) * But sometimes still that problem’s occuring: [https://www.webpagetest.org/result/171126_DC_0a751587f8fc7a4acdfc487895e344a0/1/details/#waterfall_view_step1](https://www.webpagetest.org/result/171126_DC_0a751587f8fc7a4acdfc487895e344a0/1/details/#waterfall_view_step1) * Thank you - This reply was modified 8 years, 6 months ago by [uggur](https://wordpress.org/support/users/uggur/). * [codyarsenault](https://wordpress.org/support/users/codyarsenault/) * (@codyarsenault) * [8 years, 6 months ago](https://wordpress.org/support/topic/first-byte-time-problem/#post-9725210) * Did you perhaps purge the Cache Enabler’s cache before testing your site? I just ran a few tests and received an A score for your site each time. * Thread Starter [uggur](https://wordpress.org/support/users/uggur/) * (@uggur) * [8 years, 6 months ago](https://wordpress.org/support/topic/first-byte-time-problem/#post-9728894) * No. Actually before make this test, I purged cache then I visited pages when I’m not logged in the wp, than I saw the cache comments lines at source code, than I tested it. Generally, yes the score is “A” but sometimes I’m seeing as B or C. * When I use the wp super cache, rarely I saw these scores, B and C. * Thread Starter [uggur](https://wordpress.org/support/users/uggur/) * (@uggur) * [8 years, 6 months ago](https://wordpress.org/support/topic/first-byte-time-problem/#post-9730630) * For instance while I’m using this plug-in: [https://www.webpagetest.org/result/171128_E8_499334d4d087dd13e68ec66c5ef313a9/](https://www.webpagetest.org/result/171128_E8_499334d4d087dd13e68ec66c5ef313a9/) for this page: [https://www.miyhav.com/soru-cevap](https://www.miyhav.com/soru-cevap) * I checked this page already, its cached. And there’s no load on server. - This reply was modified 8 years, 6 months ago by [uggur](https://wordpress.org/support/users/uggur/). - This reply was modified 8 years, 6 months ago by [uggur](https://wordpress.org/support/users/uggur/). * [codyarsenault](https://wordpress.org/support/users/codyarsenault/) * (@codyarsenault) * [8 years, 6 months ago](https://wordpress.org/support/topic/first-byte-time-problem/#post-9730728) * Are you referring to the “Leverage browser caching of static assets” score? 3 out of 4 of the assets that the test is warning you about are third-party resources that you cannot do anything about. * Thread Starter [uggur](https://wordpress.org/support/users/uggur/) * (@uggur) * [8 years, 6 months ago](https://wordpress.org/support/topic/first-byte-time-problem/#post-9731076) * No, I’m not referring to “Leverage browser caching”. These test for only reference for time to first byte. I’m only talking about first byte time. 🙂 * Thread Starter [uggur](https://wordpress.org/support/users/uggur/) * (@uggur) * [8 years, 5 months ago](https://wordpress.org/support/topic/first-byte-time-problem/#post-9739744) * Another example: [https://www.webpagetest.org/result/171201_X9_3299dca1737e4eda746d3b63f9d62f7a/](https://www.webpagetest.org/result/171201_X9_3299dca1737e4eda746d3b63f9d62f7a/) for [https://www.miyhav.com/kopek/kopek-cinsleri/affenpinscher](https://www.miyhav.com/kopek/kopek-cinsleri/affenpinscher) * [codyarsenault](https://wordpress.org/support/users/codyarsenault/) * (@codyarsenault) * [8 years, 5 months ago](https://wordpress.org/support/topic/first-byte-time-problem/#post-9741498) * Can you also run tests and link them showing what the TTFB is without a caching plugin and with your previous caching plugin? Viewing 8 replies - 1 through 8 (of 8 total) The topic ‘First Byte Time Problem’ is closed to new replies. * ![](https://ps.w.org/cache-enabler/assets/icon.svg?rev=2442383) * [Cache Enabler](https://wordpress.org/plugins/cache-enabler/) * [Support Threads](https://wordpress.org/support/plugin/cache-enabler/) * [Active Topics](https://wordpress.org/support/plugin/cache-enabler/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/cache-enabler/unresolved/) * [Reviews](https://wordpress.org/support/plugin/cache-enabler/reviews/) * 8 replies * 2 participants * Last reply from: [codyarsenault](https://wordpress.org/support/users/codyarsenault/) * Last activity: [8 years, 5 months ago](https://wordpress.org/support/topic/first-byte-time-problem/#post-9741498) * Status: not resolved