Conversation
supportAs title says, why?
Hello, This could have been caused due to multiple reasons. The settings you have enabled in SpeedyCache, the response time of the server when the request to check the speed was sent, and the results from the API could vary sometimes. Most likely it is caused by an increase in Time to the first byte when that request happened. We could only tell why this happened with certainty if we had more information. Regards, SpeedyCache Team
Tried many different settings, consulted the manual etc. What further details do you require?
I think it is Time to the first byte.
Hello, Try disabling, Critical CSS and Instant page when you try testing and see if you see any difference. Regards, SpeedyCache Team This reply was modified 1 year, 11 months ago by SpeedyCache .
Hello, This could have been caused due to multiple reasons. The settings you have enabled in SpeedyCache, the response time of the server when the request to check the speed was sent, and the results from the API could vary sometimes. Most likely it is caused by an increase in Time to the first byte when that request happened. We could only tell why this happened with certainty if we had more information. Regards, SpeedyCache Team
Tried many different settings, consulted the manual etc. What further details do you require?
I think it is Time to the first byte.
Hello, Try disabling, Critical CSS and Instant page when you try testing and see if you see any difference. Regards, SpeedyCache Team This reply was modified 1 year, 11 months ago by SpeedyCache .