Why a website that answers one question is useful
Most sites want something from you. A choice, an account, a preference, at minimum a moment spent working out where the thing you came for has been put. A site that answers exactly one question wants none of that. You already know what it does before it finishes loading. The only thing you do not know is which of four words it is going to say.
That makes it useful in a way that is easy to underrate. It costs nothing to keep in a bookmark bar. It answers in less time than it takes to read the answer. There is no state to manage, nothing to configure, and no version of this page that is out of date, because the question is the same every time and so is the method.
The constraint is the whole design. A page that also told you the weather, or the date, or how many days were left in the quarter, would be a worse page and not a better one. Single-purpose sites survive for decades because there is nothing in them to rot.
How this page knows what day it is
There is no answer in this page.
If you view the source of what the server sent, the word YES is not in it. Neither is NO. The box you are looking at arrived empty of any claim about the day, carrying only a sentence saying it would answer in your local time.
That is deliberate, and it is the one genuinely unusual thing here. This site is built once, all at once, on a machine somewhere, and the finished files are then handed out unchanged to everybody who asks for them. It is rebuilt only when something is pushed to it, which might be days apart. If the answer were decided when the page was built, it would be the builder's answer, on the builder's clock, in the builder's timezone, possibly from last Tuesday. It would be wrong for most of the planet most of the time, and confidently so.
So the page does not decide. It asks your device what day it is, on arrival, and fills the box in front of you. That is a single line of arithmetic on the clock you are already carrying.
This is why the page is correct in every timezone at once. It is not one answer distributed to everybody. It is the same question, answered separately, on every device that opens it. When it is Friday in Auckland and Thursday in Los Angeles, both readers are looking at a correct page, and neither one is looking at the other's.
It also means your clock, your timezone and your answer never leave your device. There is no request to make, because there is nothing to ask anybody. The page you already downloaded does the whole calculation and keeps the result to itself. To be exact about it: this site counts page views the way any site does, so a visit is a visit. What does not happen is any of that visit being about you - where you are, what your device thinks the time is, or which of the four words you were shown.
What the countdown is counting
Midnight at the start of the next Friday, in your local time. Not Friday morning, not the end of Thursday's working day - the moment the date changes and the answer above it changes with it.
It is recalculated from the clock every second rather than counted down. The distinction sounds pedantic and is not. A counter that decrements has a number it can lose: shut the laptop for two hours, or leave the tab in the background where browsers quietly stop paying it attention, and it comes back short and stays short for the rest of the week. This one has no stored number to be wrong about. Every second it works out the distance from now to Friday and prints it, so the worst it can ever be is one second stale.
The same applies to the answer itself. Leave this open across midnight and it changes on its own. Leave it in a background tab across midnight and it corrects itself the moment you come back, whether or not the browser let its timer run.
On Fridays there is no countdown, because counting down to something already happening is a strange thing to do. On Saturday it counts six days, which is honest and slightly cruel.
Thursday evening, and the case for ALMOST
From six in the evening on Thursday, the page stops saying NO and says ALMOST instead.
Six is arbitrary. It is not derived from anything, no data supports it, and nothing else on the page computes from it. It is simply the hour that reads as "the evening" in most places, and it is a single number in one file for whoever disagrees.
The case for the state existing at all is that NO is correct on Thursday evening and wrong in every way that matters. The work is done or nearly done. Nothing that starts now finishes before the weekend. The week has effectively ended and the calendar has not caught up. A page that answered strictly by the date would be more accurate and less true, and it would be answering a question nobody was asking.
Why Friday feels different when it is not actually different
Friday has no properties. It is not longer, or brighter, or warmer than Wednesday. Nothing measurable distinguishes it from any other rotation of the planet. Whatever you can feel on a Friday afternoon is not coming from the day.
It is a scheduling convention - a very large number of people agreeing to stop doing one thing at roughly the same time. The convention is recent, it is not universal, and in places where the working week ends on a Thursday the feeling moves with it rather than staying put. That is the giveaway. The feeling is attached to the agreement, not to the day.
And the feeling is anticipation rather than relief, which is why Friday afternoon reliably beats Saturday morning. On Friday afternoon the weekend is entirely ahead of you and entirely unspent. Nothing has gone wrong with it yet. Nobody has asked you to do anything with it. It exists in the best possible form, which is the imagined one, where there is no laundry in it.
By Saturday morning some of it has already been used, and you have begun making decisions about the rest. That is not a worse day. It is just a day that has started spending something Friday was only holding. It is the reason this page says IT WAS on a Saturday rather than NO - Saturday is not a failure to be Friday, it is the part where the thing you were looking forward to is quietly being consumed.
Which makes the countdown, arguably, the real content here. The answer is a single word and you usually know it already. The number underneath it is the part you came to look at, and on a Wednesday it is the whole point of the visit. If you want something else that is the same every day and better for it, there is a dog on this site that can be petted once a day and never more than once.
Questions people ask
How does this page know whether it is Friday?
It asks your device what day it is. The answer is worked out in your browser using your own clock and time zone, which is why it is right for you even though the page itself was built days ago on a server somewhere else.
Why does it say ALMOST on Thursday evening?
From six in the evening on Thursday the page softens. The hour is arbitrary and adjustable rather than derived from anything, and 18:00 simply reads as "the evening" in most places.
What is the countdown counting to?
Midnight at the start of the next Friday, in your local time. It is recalculated from the clock every second rather than counted down, so leaving the tab open or letting your laptop sleep cannot make it drift.
Will it update if I leave the tab open overnight?
Yes. The page re-checks whenever you come back to the tab, and it also sets a timer for the exact moment the answer next changes. If your browser throttled that timer while the tab was hidden, coming back to the tab corrects it immediately.
Does it say anything different at the weekend?
On Saturday it says IT WAS, which felt more honest than NO. On Sunday it goes back to NO like every other day that is not Friday.
Is there sound?
Only on Fridays, only if you turn it on, and it stays off until you do. The setting is remembered in your own browser.