Skip to content
SiteList

Analyse Review: focused product, clear fixes (77/100)

Analyse scores 77/100 for its focused player-attribution analytics aimed at Minecraft and Hytale server owners. Its strongest assets are precise positioning and polished design, while accessibility failures, a 1.9MB hero image, and a 522 timeout on /docs are the most material weaknesses.

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

Is this your site?

Claim it

Quick facts

Analyse is a freemium player-attribution analytics service for Minecraft and Hytale server owners.

Fact Value
Domain analyse.net
Category Player attribution analytics for Minecraft & Hytale servers
Pricing Freemium; 9–59 USD
Pages crawled 38
Crawl date 2026-09-24
Evidence
Pages crawled
38
Pricing model
freemium

Executive summary

Analyse earns 77/100 because it is unusually clear about its audience and product purpose. The site is aimed directly at Minecraft and Hytale server owners, and its first-impression and audience-messaging scores are 98/100 and 95/100. Its design execution also scores 94/100, supporting a polished presentation.

The main drag is execution around access and delivery. Accessibility scores 58/100, with critical failures in form labeling, focus management, and navigation. Performance scores 45/100: the homepage takes longer to show its main content, while a 1.9MB hero image blocks rendering. The documentation surface is organized and useful, but a 522 timeout on /docs and conflicting indexation signals create risk for documentation traffic.

Writing quality remains a strength at 86/100, while docs and self-serve help score 72/100 and technical SEO 76/100. The result is a focused product with a strong public explanation and a short, concrete list of high-impact fixes.

Evidence
Overall score
77/100
Accessibility
58/100
Performance
45/100

01 · First impressions & positioning — 1.03M players and $199K attributed

Analyse makes its category and audience clear immediately: it is player-attribution analytics for Minecraft and Hytale server owners. The hero claim, "Scale your server with data. Not Luck." is specific and sits beside proof of 1.03M players tracked and $199K in attributed revenue. The H1 names "Minecraft & Hytale servers," while references to Paper and Spigot reinforce the product’s working context. The positioning is unusually focused and gives prospects a concrete reason to continue. The main opportunity is comparative depth: no comparison or alternative pages were found in the crawl. Adding that material could help visitors already weighing other approaches, but the current first impression already establishes a distinct territory with credible evidence.

Evidence
SiteList score
98/100
Players tracked
1.03M
Revenue attributed
$199K

02 · Audience & messaging — server owners get answers within 1–2 clicks

Analyse answers the main prospect questions with precision: what the product is, who it serves, what it costs, and why its hostname-and-spend attribution matters. The site explicitly targets server owners, offers a free tier and clear pricing tiers, and uses direct task language such as "Install the plugin" and "Create tracking links." Important information is reachable within 1–2 clicks, keeping the path from interest to action short. Case studies and reviews supplied through schema provide proof, although testimonials are not visible. Migration content for people switching from another tool was also not found. A focused migration explanation would complete an already strong message for prospects with an existing setup.

Evidence
SiteList score
95/100
Answer reach
1–2 clicks

03 · Accessibility — unlabeled forms and missing keyboard landmarks block access

Accessibility is a material weakness: all sampled forms lack accessible labels, and the site has no skip link, main landmark structure, or visible focus styles. The contact form alone contains 3 inputs without a label, aria-label, or associated label element; the login and register forms have the same issue. These gaps directly affect screen-reader and keyboard users in essential flows. Contrast was not confirmed because Lighthouse data was unavailable, so no contrast failure is asserted here. Start with explicit labels for every control, then add a skip link, semantic landmarks, and :focus-visible indicators. These are concrete, small changes with immediate effect on navigation and form completion.

Evidence
SiteList score
58/100
Contact inputs without labels
3
Skip links
0 found

04 · Design execution — 11-color system and 44px targets support a polished interface

Analyse’s design execution is strong because its visual system stays coherent across hierarchy, components, and mobile behavior. The sampled interface uses 11 colors from a custom-property scale, one consistent type scale, exactly one H1 per page, and a single primary hero CTA. Mobile checks found no horizontal scroll, tap targets at least 44px, correctly scaled inputs, and compensated sticky bars. The remaining issues are cosmetic: the Pro pricing card uses 24px padding while Starter and Enterprise use 30px; one h2 uses weight 700 while others use 600; and two card shadow declarations differ. Standardizing those three tokens would remove visible drift without changing the underlying experience.

Evidence
SiteList score
94/100
Distinct colors
11
Minimum tap target
44px

05 · Performance — 2.5s LCP and a 1.9MB hero image leave no margin

The homepage’s mobile p75 LCP is 2.5s, exactly at the stated 2.5s bar, so the experience has no performance margin. The LCP hero image weighs 1.9MB, is 4032px wide for a 750px rendered slot, and has neither a preload nor fetchpriority. That oversized asset is the clearest first fix: serve an appropriately sized image and prioritize it deliberately. Static generation or incremental regeneration could reduce server response time; async or defer would reduce script blocking. Address the image first because it is the largest direct render cost.

Evidence
SiteList score
45/100
Mobile p75 LCP
2.5s
Hero image
1.9MB; 4032px served into 750px slot
TTFB
1.05s

06 · Writing quality — specific examples outweigh a generic docs headline

Analyse’s strongest copy is concrete and economical. "Scale your server with data. Not Luck." establishes a clear tension, while examples such as youtube.yourserver.net, PEWDS, and $1,847 make the documentation feel grounded in the product’s actual use. The main editorial weakness is the docs index headline, "Everything you need to grow your server," which does not explain the mechanism or audience. Replace it with a vertical-specific statement that carries the homepage’s precision. Mechanical hygiene also needs attention: sibling docs pages share meta descriptions, and marketing canonicals point to games.analyse.net. Those changes would tighten both reader orientation and search presentation without altering the direct voice.

Evidence
SiteList score
86/100
Docs headline
Everything you need to grow your server
Example value
$1,847

07 · Risk & stability — a 522 docs outage meets conflicting indexation signals

The most material stability risk is concentrated in documentation: https://games.analyse.net/docs returns HTTP 522, while /docs is included in the sitemap but carries noindex, nofollow. Together, the outage and contradictory signals can suppress access to feature and integration content. Marketing pages canonicalize to games.analyse.net, which may dilute root-domain authority if the marketing domain is intended to rank independently. The broader foundation is sound: HTTPS and HSTS are present, raw and rendered content has strong parity, and no sitewide noindex or robots-block pattern was detected. Restore origin connectivity first, then decide and implement one consistent docs and canonical policy.

Evidence
SiteList score
74/100
Docs response
HTTP 522
Docs indexation signals
Sitemap inclusion plus noindex, nofollow

08 · Docs & self-serve help — how-to coverage is present; reference and explanation layers are the gap

Analyse’s docs are organized and useful for getting started, with navigation and how-to guides covering revenue attribution and creator codes. They do not yet provide the reference and explanation layers technical users need in the sampled feature content: no parameter tables, API endpoints, or conceptual pages were found in that sampled content. Add a reference area for available metrics and their meanings, then explain core concepts such as hostname attribution in plain language. A glossary for terms such as hostname attribution and campaign would reduce setup ambiguity; a changelog would help users track releases, deprecations, and breaking changes.

Evidence
SiteList score
72/100
Reference pages found
0 in sampled feature content
Changelog pages found
0 in docs subtree

09 · Technical SEO — 522 docs access and canonical conflicts constrain discovery

Technical foundations are solid, but documentation access and indexation need immediate correction. The layer scorecard gives crawlability 18/20, rendering 15/15, architecture 11/12, structured data 8/10, and page experience 18/18; indexability is the weak layer at 14/25. The docs hub returns HTTP 522, /docs is in the sitemap while marked noindex, nofollow, and /, /login, and /register point canonicals to games.analyse.net. Trailing-slash variants also return a 308 before /docs. Restore the docs origin, align sitemap and robots directives, and make canonical intent consistent across the root and app subdomain. These changes target the largest crawl and authority risks directly.

Evidence
SiteList score
76/100
Indexability
14/25
Rendering
15/15
Docs response
HTTP 522

Verdict — 77/100: strong product, important accessibility and delivery fixes

Analyse is a strong fit for Minecraft and Hytale server teams that need player-source and revenue attribution. The product story is specific, the audience is explicit, and the design is polished.

Three fixes should lead the next pass: resolve the confirmed accessibility failures in forms, focus, and navigation; reduce the homepage rendering cost associated with the 1.9MB hero image; and restore reliable access to /docs after its 522 timeout. The documentation also needs more reference and explanation content for technical users.

At 77/100, Analyse has a credible foundation. Its value is easiest to understand for the server-owner audience it names directly; improving access and delivery would make that clarity more dependable in use.

Evidence
First impressions & positioning
98/100
Design execution
94/100
Documentation timeout
522 on /docs

Methodology & data notes

This is a 13-dimension review based on a crawl of 38 pages completed on 2026-09-24. SiteList combines the public dimension score table with crawl evidence and presents the result as an evidence-led review.

The review excludes 03 · Usability, 12 · Decision-support surfaces, and 13 · Review-content integrity because they were not applicable. 19 · Editorial QA of content was excluded because the required data was missing. Google Search Console was not connected, so no GSC enrichment is included.

Read How SiteList scores for the full methodology and dimension definitions.

Evidence
Review dimensions
13
Crawl date
2026-09-24
GSC access
false

Questions buyers actually ask

Who is Analyse for?

Analyse is built for Minecraft and Hytale server owners, especially small to medium-sized teams that need to track player sources and revenue.

What does Analyse cost?

Analyse uses a freemium model, with a stated price range of 9–59 USD.

What does Analyse do well?

The site explains its player-attribution focus precisely and presents the product with a polished dark design. Its first-impression and audience-messaging scores are 98/100 and 95/100.

What should Analyse improve first?

The clearest priorities are accessibility, the 1.9MB hero image affecting main-content timing, and the 522 timeout affecting /docs.

How this review was made

SiteList reviewed analyse.net on September 24, 2026 — pages, screenshots, performance runs, structured data and public records — then scored it across 9 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: Usability (not applicable), Decision-support surfaces (not applicable), Review-content integrity (not applicable), Editorial QA of content (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): Google PageSpeed Insights API — not reachable., CrUX field data — not available due to low traffic., GSC coverage data to confirm current indexing state of the /docs section., Wayback Machine CDX rows for historical migration/repurposing analysis., docs_lighthouse_run, GSC coverage data to verify if the 522 error is currently blocking indexing., CrUX field data for Core Web Vitals assessment.

Read the full methodology

77/100AnalyseJump to review