Half a second on our about-us section, five on the problem section

456 seconds, and where they went

In the seven days ending 1 October at 02:15, Mexico City time, our own site took 35 page loads from 29 distinct visitors. Those loads produced 456 seconds of active attention in total. Not seconds with the tab open: active seconds, counted while the page was in front of someone who was doing something.

456 seconds for a whole week is very little, and I will come back to how little. The useful part is not the total. The useful part is that we can see which part of the page the seconds went to, and the split is lopsided enough to make a decision on.

Seconds per view, section by section:

• The problem block: 5.0 seconds (145 seconds across 29 views)
• FAQ: 3.8 seconds (42 across 11)
• Proof: 2.1 seconds (29 across 14)
• Pricing: 2.0 seconds (22 across 11)
• How it works: 1.7 seconds (22 across 13)
• Contact: 1.2 seconds (13 across 11)
• Our own results: 0.6 seconds (7 across 11)
• About the founder: 0.5 seconds (5 across 11)

The block that describes the reader's problem earned ten times the attention per view of the block that describes me. I wrote both. I spent longer on the second one.

There are two different numbers in that list

Look at the views column, not only the seconds. The problem block was seen by 29 loads. The blocks lower down were seen by 11. Those are two separate findings, and they are fixed in different ways.

The first is reach: of every ten people who open the page, fewer than four ever see what you put in the bottom half. They did not dislike it. It never arrived on their screen.

The second is dwell: of the 11 loads that did reach the founder block, the average was half a second. That is not reading. That is a thumb or a scroll wheel passing over it.

The uncomfortable part has to be said: page order explains a good share of this. The problem block sits near the top and the founder block sits near the bottom. Part of what I am measuring is the order in which I wrote the page, not a clean reader preference. That does not make the number useless, it makes it more actionable: if position is what rules, then section order is the lever I actually hold, not wording.

The most clicked thing on the site was a compatibility answer

In the same seven days, the most clicked element on the entire site was one FAQ answer, the one naming which system the engine works best with and why its API lets us write rates: 12 clicks. The question above it, asking which PMS or booking engine is supported, got 1 click. The only other clicks all week were two language switches.

That answer is not a link. It goes nowhere. It does not expand. People clicked it twelve times anyway, and one of those sessions registered as a rage click: the same element hit repeatedly within a few seconds.

That is information, not visitor error. Twelve clicks on text that does nothing means that is where the question they actually came with was sitting, and they expected that block to give them more.

What I would change on a hostel's own page

A hostel's compatibility question is not which PMS. But it exists, and it blocks the same way. It is: is the dorm mixed? Is anyone at reception when the eleven o'clock bus gets in? Can I drop my bag before check-in? How late can I cancel without a charge? Until that question is answered, nothing else you wrote is being read, it is being skimmed past.

Four concrete moves, in the order I would do them:

• Move the unblocking answer up. One short block, near the top, with the three or four doubts that decide whether your property fits that trip at all. Before your story, before the rooftop photos.
• Treat section order as the main decision. 29 views up top against 11 below. Moving a block upward nearly triples the number of people who see it, and it costs nothing.
• Make clickable the thing people are already clicking. If they click it, they wanted it to lead somewhere. At a hostel that is usually the room name, the photo, or the how-to-get-here line.
• The price has to read in two seconds. Our pricing section gets 2.0 seconds per view. A table with three tiers, four rows and a footnote does not get read in two seconds. One number and one unit does.

What this does not prove

35 loads in seven days is a small sample. I am saying that before anyone treats it as a law.

Of the 456 seconds, 171 of them, 37.5 per cent, could not be attributed to any section at all. The 285 that remain are what the list above divides up. If those 171 had all landed in one block, the order of that list would change.

30 of the 35 loads were desktop and only 5 were mobile. Our visitor is a property owner at a computer. The guest booking a bed is almost always on a phone, where every block is three times taller and order matters even more. Do not port my seconds onto your page; measure your own.

And the number that keeps me from celebrating anything: 11 of the 35 loads reached the trial form, and none of them started it. Zero of 35 clicked the call to action. Attention is not intent. A block can earn five seconds and move no bookings at all.

The measurement worth running on your own page

You do not need what we built. Two routes, both cheap:

The first is a per-section timer: a short script that counts active seconds while each block is on screen, and lets you read the split weekly. If your site is on WordPress or Wix, a free scroll map gives you reach, which is half the finding and the easier half to fix.

The second needs no analytics at all. Take the next five emails or WhatsApp messages from guests who ask something before booking, and write down the question. If three of the five ask the same thing, that answer belongs near the top of your page, not buried in an FAQ.

One reason to do it this week rather than in December: in Oaxaca the Day of the Dead run-up is 19 days out. The page that will meet that demand is the page you have today. If you are going to move a block upward, move it before the traffic that matters arrives, not after, because by then you will not know whether the change worked or whether it was just the season.

If this sounds like your property, see the three Nightfill tiers and start a free 14-day pilot on your own data: view pricing.