Performance-wise, I'd recommend a span hell.
<span id="string"><span id="h">12</span><span class="h">h</span><span id="m">12</span><span class="m">m</span><span id="s">12</span><span class="s">s</span></span>
One span for each h, m and s letters so you can style them properly (can apply either the same or different styling for each).
And another span for each number so you can cache the references. In sum, here's a JS for a very simplistic local-time clock:
//cache number container element references var h = document.getElementById('h'), m = document.getElementById('m'), s = document.getElementById('s'), //IE feature detection textProp = h.textContent !== undefined ? 'textContent' : 'innerText'; function tick() { var date = new Date(), hours = date.getHours(), mins = date.getMinutes(), secs = date.getSeconds(); h[textProp] = hours < 10 ? '0'+hours : hours; m[textProp] = mins < 10 ? '0'+mins : mins; s[textProp] = secs < 10 ? '0'+secs : secs; } tick(); setInterval(tick, 1000);
Fiddle
This illustrates the basic idea of cached selectors. By not re-creating the elements, you also have a good performance boost.
Though, once a second isn't very heavy work for something so simple (unless you have hundreds of clocks in your page).
var seconds = document.getElementById('seconds');then usesecondsinstead ofdocument.getElementById('seconds')inside the loop. Here's a more detailed article: phpied.com/dom-access-optimization