Free tool · no account

Hear how your delivery actually lands.

Record 45 seconds against a real interview prompt and get three plain numbers about how you speak — plus the one thing worth working on. Your audio is analysed in your browser and never reaches our servers.

Your prompt

Tell me about a project you worked on recently — start with why it landed on your plate.

We'll count you in from three. Your recording never reaches our servers — nothing is uploaded and nothing is stored.

Questions people ask

What is a good speaking pace for a job interview?
Most interviewers follow a candidate comfortably between roughly 110 and 160 words per minute. Below that range you usually sound like you are searching for the word rather than thinking carefully; above it, interviewers tend to hear speed as nerves rather than enthusiasm. The range is a guide, not a rule — non-native English speakers often sit naturally below it and are perfectly clear, and consistency of rhythm matters more than hitting a specific number.
Are pauses bad in an interview answer?
No. Short pauses of under a second read as considered and give an interviewer room to follow you. What costs you is inconsistency: a pause long enough that the interviewer starts to wonder whether you have finished, which in practice is somewhere past three or four seconds. That is why this tool reports your longest pause and how steady your phrasing was, rather than counting pauses and calling them mistakes.
Is my recording uploaded or stored anywhere?
No. The pause and rhythm analysis runs entirely in your browser using the Web Audio API, and the recording is discarded when you leave the page — it is never sent to withLyra, never written to a server and never stored. The one exception to disclose: the optional words-per-minute count uses your browser's own speech recognition, and in Chrome that feature processes audio through Google. On browsers without it, the tool simply shows two metrics instead of three.
Does this work in Safari and Firefox?
Yes. Pause stability and longest pause are computed from raw audio energy and work in every modern browser. Words per minute relies on the Web Speech API, which today only Chrome implements, so on Safari and Firefox that one metric is simply not shown. Nothing else about the tool changes.