Hi, I'm Kelvin. I built this.

WenToGo is me: Kelvin Zhao, an independent developer. There is no editorial team churning out destination guides and no network of sister sites quietly linking to each other.

Every destination here was researched by hand against published weather records, holiday calendars and event schedules before it earned a page. That is slow. That is also the point. Nothing was scraped from an article mill and lightly reworded.

You give a destination and your exact dates. The engine scores those dates on weather, crowds, prices and comfort, then lets the rough days drag the total down. One miserable day can become the story of a whole trip, so it counts for more.

The same data version always produces the same answer. Quote a score, compare it, cite it. It will say the same thing tomorrow. Research ships as versioned exports. When the data changes, every payload carries a new source_version you can cache against. When it has not changed, the answers stay identical.

No language model writes the scores, the verdicts or the suggestions. Machines are very good at producing confident sentences about places they have never checked, which is roughly the problem I set out to fix.

It also means a page cannot quietly change its mind between visits or answer a question it has no evidence for.

Most travel advice tells you somewhere is lovely in spring. Fine. Which week? A month can hold perfect weather, a public holiday, a packed festival and three days of rain that make your shoes regret everything.

WenToGo answers the harder question: whether your exact dates are a good time to go, what pulls them down and which nearby week would treat you better.

The longer version of that story is in the origin post.

Every scored trip page names its sources beside the verdict: published station records, tourism bodies and official event calendars. The counts are real rather than padded to look impressive.

Where no published source exists, the page says so instead of inventing confidence. If you catch me getting something wrong, the contact page has one channel and I read it.