Skip to content
SiteList

Simple Analytics Review: strong product (83/100)

Simple Analytics scores 83/100, with excellent usability, design execution, and performance as its clearest strengths. Its most material weakness is decision support: pricing gives too little guidance, and the review-content pages need clearer disclosure and evidence methods.

Reviewed by SiteList Engine · 10 of 13 dimensions · published Reviewed on September 24, 2026

Is this your site?

Claim it

Quick facts

Simple Analytics is a SaaS subscription product for privacy-first web analytics.

Fact Value
Domain simpleanalytics.com
Category Privacy-first web analytics for GDPR-compliant websites
Pricing Unknown; price range not supplied
Pages crawled 38
Crawl date 2026-09-24
Evidence
Pages crawled
38
Crawl date
2026-09-24

Executive summary

Simple Analytics is a strong, focused product whose public site performs best when it explains the product and gets visitors to action. Usability scores 92/100, design execution scores 94/100, and performance scores 97/100. The site also presents a clear privacy-first position for tech-savvy businesses and developers who prioritize GDPR compliance.

The overall review score is 83/100. The main gap is decision support. That dimension scores 45/100 because the pricing page presents two options without enough guidance, leaves Self-serve cost transparency incomplete, and does not help readers choose. Review-content integrity is another weak point at 50/100: the vs-content pages need affiliate disclosure and methodology blocks, while their schema makes review claims beyond the available hands-on evidence. Writing quality remains strong at 83/100, although content index pages are less consistent than the commercial and product copy.

Technical SEO is broadly strong at 82/100, with crawlable, server-rendered pages in the available sample.

Evidence
Overall score
83/100
Usability
92/100
Design execution
94/100
Performance
97/100

01 · First impressions & positioning — privacy-first analytics, but the audience stays implicit

Simple Analytics makes a clear privacy-first case, but its first impression would be stronger with an explicitly named audience and nearby proof. The hero calls it a “privacy-friendly alternative to Google Analytics” and emphasizes “no cookies, no trackers,” GDPR compliance, and EU hosting. That separates the product from competitors, yet the hero does not say “for web developers” or “for GDPR-compliant businesses,” and customer logos are not adjacent to the claim. The “Google Analytics alternative” category may also be unfamiliar to searchers who simply need web analytics. Name the audience in the hero, place customer logos with specific outcomes beside the positioning, and frame the category as privacy-first web analytics for GDPR-compliant sites.

Evidence
Positioning claim
“privacy-friendly alternative to Google Analytics”; “no cookies, no trackers”
Audience specificity
Implied, not explicitly named

02 · Audience & messaging — €20/month appears without enough context

The messaging answers the core job of privacy-friendly web analytics, but it leaves the intended buyer and the headline price under-explained. Terms such as “no personal data” and “GDPR compliant” point toward tech-savvy businesses and developers, yet the hero does not name either group. The pricing page uses a tiered structure, while the hero mentions “€20/month” without explaining the plan or usage context; pricing is three clicks from the home page. Technical terms such as GDPR compliant, EU-hosted, and data migration also lack plain-language alternatives. Add audience language to the hero, state what the €20/month covers, and explain key terms in everyday language so non-technical buyers can evaluate the offer.

Evidence
Headline price
€20/month without context in the hero
Pricing depth
3 clicks from home

03 · Usability — intuitive paths, with one weak AI-page CTA (92/100)

Simple Analytics is easy to navigate for its core tasks: visitors can understand the offer, find pricing, and reach trial or signup paths. Navigation provides clear routes to pricing, documentation, and blog content. The remaining friction is concentrated in conversion details. The AI features page has no prominent “Start free” or “Book a demo” button above the fold, so visitors must scroll to find the action. On pricing, the two plans sit side by side but Self-serve is visually less prominent than Enterprise, which can slow selection. Add a high-contrast primary CTA below the AI hero and give Self-serve clearer visual priority while keeping the comparison intact.

Evidence
Usability score
92/100
AI-page CTA
No prominent trial or demo button above the fold

04 · Design execution — 94/100, with 95% of sampled contrast pairs passing

The design system is disciplined across hierarchy, components, and mobile behavior, with only minor contrast drift to resolve. The crawl found 10 font families, 473 colors, and 53 font sizes extracted from CSS custom properties. Pages use one H1 with no skipped heading levels, and component drift is limited to two button styles or fewer. At 390px, there is zero horizontal scroll; tap targets are at least 44px apart by at least 8px, and inputs use at least 16px text. Contrast is mostly AA-compliant: 95% of sampled pairs pass. Two pricing buttons measure 3.2:1 on white; darkening both backgrounds to #4B5563 produces a 7.6:1 ratio.

Evidence
Mobile horizontal scroll
0px at 390px
Contrast pass rate
95% of sampled pairs
Pricing button contrast
3.2:1, fix target 7.6:1 with #4B5563

05 · Performance — 0.5 s desktop LCP and 1.9 s mobile LCP

Performance is a clear strength, with fast lab results on both desktop and mobile and only low-severity image optimizations remaining. Desktop LCP is 0.5s and mobile LCP is 1.9s; INP stays under 200ms on both platforms and CLS is 0.007. Server response time is about 536ms, with minimal render-blocking resources. The LCP image on the AI features page has naturalWidth 2076px and displayWidth 494px but no explicit width or height, and it is a PNG without modern format alternatives. Add explicit width and height attributes matching the image's intended aspect ratio, then provide a WebP alternative with srcset. For images that are offscreen, lazy loading remains appropriate; do not lazy-load the above-the-fold LCP asset.

Evidence
Desktop LCP
0.5s
Mobile LCP
1.9s
CLS
0.007

06 · Writing quality — concrete hooks, but “Blog.” and “Guides.” waste intent

Commercial and product copy is specific and confident, while content index pages undersell what readers will find. The homepage leads with “See the traffic Google Analytics misses,” then explains the mechanism and gives concrete details such as an under 5 KB script and 31k+ Customers. The API page likewise states a direct value proposition. By contrast, the blog and guides pages use the bare H1s “Blog.” and “Guides.”, which provide no scope or audience signal. A duplicate meta description appears on 13 pages, including About and Privacy Policy. Replace the index H1s with descriptive titles, add a short introduction to each collection, and write unique 140–160 character descriptions for affected pages.

Evidence
Script size
under 5 KB
Customer proof
31k+ Customers
Duplicate meta descriptions
13 pages

07 · Decision-support surfaces — two plans, no recommendation or complete cost picture

The pricing page presents Self-serve and Enterprise but does not help a buyer choose between them. The Self-serve plan lists four checkmarks, including “No cookies, no consent banners, no personal data” and “EU-hosted and compliant by design,” yet these are broad claims rather than decision axes such as capacity, integrations, or cost. The page also states $20/month while adding unclear extra-fee language, and its cramped mobile layout weakens parity. Add a recommendation layer that explains who should choose each plan and why, surface all recurring and additional costs with clearly labeled monthly and annual prices, and convert the mobile comparison into readable cards or collapsible sections.

Evidence
Plan options
2: Self-serve and Enterprise
Self-serve checklist
4 checkmark rows
Self-serve price
$20/month plus unclear extra-fee language

08 · Review-content integrity — comparison pages need disclosure and criteria

The comparison pages synthesize information honestly, but their trust signals do not explain commercial relationships or evaluation methods. Pages comparing GA4, Matomo, and Plausible contain affiliate links to the demo page without visible disclosure text. They also present comparisons without a methodology block stating the criteria used before the reader reaches the choices. Finally, the pages use Review schema without a hands-on claim or stated methodology, which overstates the evidence behind the content. Add a plain-language disclosure beside the first affiliate link, mark those links sponsored, and state the comparison criteria. Keep the comparison criteria, affiliate disclosure, and methodology clear, and avoid Review markup unless the page's evidence and methodology support it.

Evidence
Affiliate disclosure
Not visible on comparison pages
Methodology block
Absent before comparison grids
Schema issue
Review markup used without hands-on evidence

09 · Risk & stability — two 302 hops and one external canonical are the main exposures

The available scan shows a stable baseline, but redirect and canonical decisions create avoidable signal friction. Robots permits crawling, sampled pages return 200, the probe 404 is real, and raw and rendered content match. The HTTP root takes two 302 redirects before reaching the canonical www HTTPS host; the non-www HTTPS root also redirects to www. Separately, /press/rightblogger is in the sitemap while its canonical points to rightblogger.com. Consolidate both HTTP and non-www variants into one permanent redirect to the canonical host, then confirm whether the press page is intentionally ceded to the partner. No traffic-drop magnitude or recovery timeline can be claimed because GSC and analytics data were not supplied.

Evidence
HTTP root redirect path
2 redirects, both 302, to canonical host
External canonical
/press/rightblogger points to rightblogger.com
Traffic dataset
No connected GSC or analytics data

10 · Technical SEO — 407 sitemap URLs versus 38 crawled pages

The main fixes are one-hop permanent host redirects and the external canonical on the sitemap-listed RightBlogger page. Coverage is not complete: 38 of 40 crawl slots were used while the sitemap reports 407 URLs. Conclusions are limited to the 38-page crawl sample and cannot be generalized to all 407 sitemap URLs. The crawl also found duplicate titles on 14 pages and duplicate meta descriptions on 13; prioritize unique metadata on commercial, comparison, feature, and editorial templates.

Evidence
Crawl sample
38 of 40 pages
Sitemap inventory
407 URLs
Raw/rendered words
/features/ai: 273 vs 273; homepage: 950 vs 953
Duplicate titles
14 pages

Verdict — 83/100: strong product, weak decision support

Simple Analytics earns 83/100 because the site combines a clear privacy-first position with excellent usability, disciplined design, and strong measured performance. It is a good fit for tech-savvy businesses and developers who prioritize GDPR compliance.

The fixable weaknesses are concentrated in the buying and trust layers. The pricing page needs plan-selection guidance and clearer Self-serve cost transparency. The vs-content pages need affiliate disclosure, methodology blocks, and more defensible review schema. These changes would make the site's strong product communication easier to act on and easier to trust.

Evidence
Overall score
83/100
Decision-support surfaces
45/100
Review-content integrity
50/100

Methodology & data notes

This is a 13-dimension review based on a crawl of 38 pages completed on 2026-09-24, with the public dimension score table and its one-line summaries used for the article frame. Performance figures are lab measurements supplied in the score table; no traffic symptom was supplied, and Google Search Console access was unavailable, so the risk result is a vulnerability scan rather than a measured traffic-drop diagnosis.

Pricing is recorded as unknown in the supplied site facts.

See How SiteList scores for the full methodology.

Evidence
Review dimensions
13
GSC access
false
Excluded dimensions
04, 19, 23

Questions buyers actually ask

Who is Simple Analytics for?

Simple Analytics is aimed at tech-savvy businesses and developers who prioritize GDPR compliance and privacy-first web analytics.

How usable is the Simple Analytics website?

Usability is a major strength, scoring 92/100. Visitors can understand the product, find pricing information, and locate a trial or sign-up path.

How fast is the Simple Analytics website?

Performance scores 97/100 in lab tests, with 0.5-second desktop LCP and 1.9-second mobile LCP measurements in the supplied performance evidence.

Does the pricing page make the plans easy to compare?

Not fully. Decision-support surfaces score 45/100 because the pricing page lists options without enough guidance, and Self-serve cost transparency is incomplete.

What should Simple Analytics improve first?

The clearest priorities are stronger plan-selection guidance, fuller Self-serve cost transparency, and clearer disclosure and methodology on vs-content pages.

How this review was made

SiteList reviewed simpleanalytics.com on September 24, 2026 — pages, screenshots, performance runs, structured data and public records — then scored it across 10 of the 13 public dimensions. Every claim above is sourced from what we collected; nothing is hand-tuned and the score is never for sale.

Not covered in this write-up: Accessibility (not applicable), Editorial QA of content (not assessed), Docs & self-serve help (not assessed). Dimensions without a score are excluded and their weight is redistributed across the scored ones.

Pending enrichment (data we could not fetch this run): readability_api, spell_check_service, Fetch competitor pricing pages to fact-check claims (e.g., GA4 integration vs Plausible)., Check if 'vs' pages exist and are structured with methodology disclosure., Check if any vs-page has a hands-on claim or original data (e.g., 'we tested' language)., Verify if the site's schema policy is documented in its documentation or footer., Google Search Console coverage, clicks, impressions, and canonical-selected URLs, Analytics time series and tracking-change audit…

Read the full methodology

83/100SimpleanalyticsJump to review