Test Diary's tech stack
What does Test Diary use?
Test Diary (testdiary.com) uses at least 7 tools we can see from public records, including Google Analytics for analytics and WordPress for its website. Last checked .
- Industry
- IT Services
- Size
- 11–50 employees
- Based in
- London, United Kingdom
- Founded
- 2016
- Company page
- Tools found
- 7
- Categories
- 5
- Layers
- 4 of 5
- Last checked
- Oct 2026
Test Diary's stack, layer by layer
Each tool links to the other companies we've found using it. The label says what kind of public trace gave it away.
Edge & Hosting
1 tool, where the bytes are served from
DNS
Application
2 tools, what the product is built with
Media & UI
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
3 tools, how they find and keep customers
Website & CMS
Marketing
Test Diary tech stack FAQ
What tools does Test Diary use?
As of October 2026, runsonwhat has found 7 tools at Test Diary (testdiary.com) in public records. Edge & Hosting: GoDaddy. Application: Google Fonts and Vimeo. Data & Observability: Google Analytics. Go-to-market: WordPress and Yoast SEO. Last checked October 20, 2026.
What analytics tools does Test Diary use?
Test Diary uses Google Analytics for analytics, according to runsonwhat (October 2026). runsonwhat found Google Analytics through Google Analytics code on testdiary.com. Google Analytics is used by 885,940 companies runsonwhat tracks.
What is Test Diary's website built with?
Test Diary uses WordPress for its website, alongside Yoast SEO, according to runsonwhat (October 2026). runsonwhat found WordPress through WordPress code on testdiary.com. WordPress is used by 599,527 companies runsonwhat tracks.
Does Test Diary use Google Fonts?
Yes. runsonwhat found Google Fonts at Test Diary through Google Fonts code on testdiary.com. Google Fonts is a Media & UI tool used by 813,482 companies runsonwhat tracks.
How does runsonwhat know what Test Diary uses?
runsonwhat reads public records only. Of the 7 tools at Test Diary, 5 were found through code on testdiary.com, 2 through DNS records. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and testdiary.com about monthly.
We read public traces only: DNS and email records, certificate logs, website code and published subprocessor lists. A tool is listed when a direct record backs it up, and dropped when a recheck no longer finds it. Is this your company? See how to opt out.