Rodgers Leask's tech stack
What does Rodgers Leask use?
Rodgers Leask (rodgersleask.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
- Construction
- Size
- 51–200 employees
- Based in
- Derby, United Kingdom
- Founded
- 1984
- Company page
- Tools found
- 7
- Categories
- 4
- Layers
- 3 of 5
- Last checked
- Oct 2026
Rodgers Leask'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.
Application
4 tools, what the product is built with
Frontend
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
2 tools, how they find and keep customers
Website & CMS
Rodgers Leask tech stack FAQ
What tools does Rodgers Leask use?
As of October 2026, runsonwhat has found 7 tools at Rodgers Leask (rodgersleask.com) in public records. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics. Go-to-market: WordPress and Yoast SEO. Last checked October 20, 2026.
What analytics tools does Rodgers Leask use?
Rodgers Leask uses Google Analytics for analytics, according to runsonwhat (October 2026). runsonwhat found Google Analytics through Google Analytics code on rodgersleask.com. Google Analytics is used by 864,639 companies runsonwhat tracks.
What is Rodgers Leask's website built with?
Rodgers Leask uses WordPress for its website, alongside Yoast SEO, according to runsonwhat (October 2026). runsonwhat found WordPress through WordPress code on rodgersleask.com. WordPress is used by 588,993 companies runsonwhat tracks.
Does Rodgers Leask use jQuery?
Yes. runsonwhat found jQuery at Rodgers Leask through jQuery code on rodgersleask.com. jQuery is a Frontend tool used by 905,829 companies runsonwhat tracks.
How does runsonwhat know what Rodgers Leask uses?
runsonwhat reads public records only. Of the 7 tools at Rodgers Leask, 7 were found through code on rodgersleask.com. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and rodgersleask.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.