Simple Digital Clock 🕒

Yes. Use the Locale field and enter any valid BCP-47 tag.

The clock uses the date and time reported by the visitor’s device and formats it for the selected time zone. It does not synchronize with a time server, so an incorrect device clock will affect the displayed time.

Use the Time Zone field and select any valid IANA ID (e.g., Europe/Kyiv , UTC ).

Yes. Enable “Hundredths of a second” in the block settings. It shows two fractional digits and automatically includes seconds while enabled.

You can choose from the available mono fonts (Google Fonts) or select System to use a local monospace font. Selecting a Google Font loads it from Google’s servers.

Yes. Enable 24-Hour to force a 24-hour display. When disabled, the clock follows the selected locale. For AM/PM, choose a locale such as en-US and leave 24-Hour disabled.

Yes. Each block is independent—set its own locale and time zone.

Yes. The bundled clock widget is about 12.2 KiB gzip and is served locally without a runtime JavaScript CDN dependency. On the frontend, the runtime is delivered only when a clock is present in the server-rendered page HTML; clock-free pages receive no plugin script or browser loader. Multiple clocks share one runtime script. The inline layout rule remains scoped to rendered Simple Digital Clock blocks and explicit integrations; raw HTML keeps its existing layout. No external plugin stylesheet is loaded. Server-side HTML observation adds PHP work, including on clock-free pages.

Automatic delivery detects server-rendered clocks. An integration that creates its first clock only after page load must load the widget runtime itself. Calling SDCW_enqueue_scripts() without rendering a clock on the server does not bypass the zero-script rule.

Regenerate full-page caches after updating so visitors receive the corrected HTML. Cached pages served without WordPress running are not rewritten by the plugin.