fritex
February 14, 2022, 4:22pm
2
Greetings,
Thank you for asking.
It’s still a beta feature. You might want to disable it, or at least I’d suggest you to check below posts:
You can check my own tool here: https://code103.hotmann.de
try it several times, if it once tells you it could confirm the 103 Headers you can be sure it works. Please also notice the unique behaviour of Cloudflare in that case: Early Hints | Need More Data Before Switching Over - #21 by LucasCF
Please run it severare times to make sure it works, or does not work.
This does not answer the question at all, just connects ot to another question which searches for the same result.
To verrify yo…
The property that matters is returning the Link header field at the earliest opportunity to the client. Whether that occurs an an 103 Early Hint or a 200 is not important for how clients act on the the value. So while it might appear more consistent to strictly order 103 before 200, if that comes at the cost of delaying the 200 then it is not a positive improvement,
I believe my colleague @M4rt1n could add a few valuable notes and provide information about this here as far as he is more experienced than me with this kind of a feature.
In case if you see some error, below article help a bit to troubleshoot, if so:
Error
Try the suggestions in this Community Tip to help you fix the error The Speed test could not run .
Background
The “Speed test could not run ” error on the Speed app of the Cloudflare Dashboard indicates the test was somehow blocked. The blocks can occur due to a rule you have set in Cloudflare, a restriction from your hosting provider, or it may just be a temporary issue that resolves without intervention. When the test is somehow blocked, you’ll see the error “The Speed test could not ru…
3 Likes