CMS
WordPress site breakdown
How TaylorSwift.com Runs on WordPress
A friendly, public-source breakdown of the CMS, theme, plugins and infrastructure behind a global artist website.
▣ Updated July 2026
01 / STACK
Stack snapshot
The important pieces, without the jargon.Network
Multisite · Site ID 2529
Theme
UMG Grand Royal 3.5.4
Blocks
Gutenberg + Kadence
Edge
Imperva CDN/WAF
Store
Separate Shopify site
02 / ARCHITECTURE
Follow the request
What happens between a visitor and the page.Visitor
Fans, readers and browsers
Imperva edge
Filters and caches content
UMG WordPress
Multisite platform
Theme + plugins
Grand Royal and public tools
Shopify store
Separate products and checkout
03 / PUBLIC EVIDENCE
Plugins spotted
These are visible signals, not a complete backend inventory.PluginWhat it does
Yoast SEOManages SEO titles, metadata and structured data.
AutoptimizeOptimizes and caches the site's CSS and JavaScript assets.
Contact Form 7Provides the public contact and enquiry forms.
Kadence BlocksAdds flexible page-building blocks to the WordPress editor.
Appreciation EngineSupports fan registration and engagement features.
Custom UMG pluginsAdds custom features for UMG's shared WordPress platform.
04 / TAKEAWAYS
5 things WordPress builders can learn
- 1
Multisite can power huge brand networks
One installation can run many sites, share users and simplify operations.
- 2
A custom theme can still use the block editor
UMG's bespoke visual system works alongside Gutenberg and Kadence blocks.
- 3
Keep commerce separate when it makes sense
Shopify handles checkout while WordPress stays focused on content.
- 4
Edge caching matters at global scale
Imperva helps serve a worldwide audience and shields the origin.
- 5
Public source reveals more than you think
HTML, assets, headers and DNS can explain a stack without logging in.