Caching & Performance

MuRu Reviews is fast by architecture: the frontend only ever reads the local file cache. Google is contacted server-side when you refresh -- visitors never wait on an API, and no visitor data is sent to Google.

How refreshing works

• Refresh Now (Dashboard) refetches from your ticked sources. Cached-vs-total counts show exactly what is stored.
• Clear Cache empties it.
• Cache duration options: 1h, 6h, 12h (default), 24h, or 7 days.

Why pages stay fast

• Dependency-free markup and CSS; the carousel is vanilla JS. No CDN scripts, fonts, or images -- ever.
• Reviewer avatars lazy-load with an initials fallback, never blocking rendering.
• Reviews render as real crawlable HTML with structured-data basics, readable by search engines.

Automatic scheduled refresh is on the Pro roadmap. Until then, set a generous TTL and hit Refresh Now whenever new Google reviews matter -- the cache makes refreshes cheap.