relative-time-element is GitHub's web component for localised relative timestamps.
About 23,074 websites in the PageSourceSearch index contain the code that reveals it; the 50 highest-ranked are listed below.
How is relative-time-element detected?
Timestamps are marked up with the <relative-time> custom element. The discovery keyword is the exact bytes PageSourceSearch looks for in every stored page and script:
A literal is matched byte for byte, case-sensitively. Combine it with another keyword, a domain, a kind or a date filter on the search page to narrow the list. About relative-time-element
Top 50 websites using relative-time-element
Ranked by the domain's position in the crawl's ranked list (Common Crawl harmonic centrality), highest first. view source opens the stored page or script with the match highlighted. Computed 2026-09-29 21:54:39 UTC.
How does PageSourceSearch know a website uses relative-time-element?
By the source itself: Timestamps are marked up with the <relative-time> custom element. PageSourceSearch stores the raw HTML and first-party JavaScript of each crawled site and matches the keyword byte for byte, so every listed site's stored source contains it.
Is this a complete list of websites using relative-time-element?
No. The page lists the 50 highest-ranked sites in the index whose source holds the keyword, out of about 23,074 websites that do; the count is the index's estimate at the time the list was computed. Run the keyword as a search to page through all of them, or add a kind or date filter.
How do I find websites that use relative-time-element together with another technology?
Search for both keywords at once: several terms separated by spaces must all be found on the same site, or with the Same page toggle in the same page. For example <relative-time with wp-content/plugins/ lists the WordPress sites that use relative-time-element.