Skip to content
SiteList

Wrongscape Review: strong concept, uneven execution (75/100)

Wrongscape scores 75/100 for a daily visual history and geography puzzle with unusually strong accessibility and clear editorial explanations. Its most material weaknesses are the tested mobile performance and layout stability, alongside a /blog route that returns 502 while remaining in navigation and the sitemap.

Reviewed by SiteList Engine · 12 of 13 dimensions · published Reviewed on November 20, 2026

Is this your site?

Claim it

Quick facts

Fact Detail
Domain wrongscape.io
Category Daily history and geography photo puzzle game
Pricing Free to play; $0
Platform Web browser
Crawl 40 pages on 2026-11-17
Evidence
Domain
wrongscape.io
Pricing model
Free; 0-0 USD
Pages crawled
40
Crawl date
2026-11-17

Executive summary

Wrongscape is a well-defined daily visual puzzle with strong accessibility and editorial clarity, but its tested mobile experience and one important public route hold the overall result to 75/100.

The core offer is distinctive: each day brings five photo-real scenes in which players spot historical or geographic anomalies. The site answers the practical questions that block play: it is free, browser-based, requires no account to start, explains the five-photo format and 60-second choices, and documents the UTC reset. Accessibility is the standout result at 100/100. Writing quality is also strong at 85.1/100, supported by concrete explanations, while editorial QA scores 79.5/100 and review-content integrity 80/100.

The main drag is execution on the tested mobile path. Performance scores 60.3/100: the homepage reached its largest content at 5.24 seconds and recorded CLS of 0.424 in the lab. Design execution scores 61/100, with homepage CLS measured at 0.440 on desktop and 0.424 on mobile. Technical SEO scores 78.7/100, but /blog returns 502 while remaining in the sitemap and site navigation. Fixing those concrete issues would make the strong puzzle idea easier to understand and use.

Evidence
Overall score
75/100
Accessibility
100/100
Mobile largest content
5.24 seconds
Homepage CLS
0.440 desktop / 0.424 mobile
Blog response
502

01 · First impressions & positioning — five photos, one choice, but the category sits in metadata

Wrongscape has an ownable five-photo anomaly mechanic, but its category is less explicit than its hook. The hero says "Spot what doesn't belong" and "Five photos. One strange detail in each." That gives the visitor a memorable action, while the clearer category—"Daily photo puzzle game" about historical mistakes and anachronisms—appears in the meta description. The learning loop strengthens the position: scenes are labelled "AI reconstruction", answers unlock the next day, and explanations link to sources. The practical fix is small: put "daily history and geography photo puzzle" beside the hero hook, then give the Krillion comparison a clearly labelled home. That would make the product category and its educational distinction legible before a visitor has to explore.

Evidence
Hero mechanic
Five photos. One strange detail in each.
Category description
Daily photo puzzle game where you spot historical mistakes and anachronisms
Daily reset
00:00 UTC

02 · Audience & messaging — free, browser-based play is clear; player identity is broad

Wrongscape removes most practical barriers to play: it is free, browser-based, needs no account to start, explains the five-photo format and 60-second choices, and documents the 00:00 UTC reset. That is strong decision support for someone already looking for a daily puzzle. The remaining messaging gap is identity. The About page calls the audience "curious people", while the homepage metadata says "trivia lovers"; neither prioritizes a history learner, visual-deduction fan, or casual daily-game player. Trust is better served: the site labels scenes as AI reconstructions, describes editorial checking, and promises source-linked explanations. Add one audience sentence beside the hero CTA and a short comparison block explaining the sourced historical-anomaly format against ordinary trivia and Krillion.

Evidence
Pricing
Free to play in a browser; no account needed
Daily format
Five photos and a 60-second choice
Audience wording
daily puzzle for curious people; trivia lovers

03 · Usability — the primary CTA is clear, but the Blog destination fails in the supplied capture

Wrongscape’s front door is clear: "Spot what doesn't belong" explains the activity, "Start today's case" is the obvious next action, and the homepage exposes direct routes to How to play, Blog, About, and Contact. The main usability break is the recent-content path. Although the crawl inventory exposes article links, the supplied desktop /blog capture displays "Application failed to respond", so the destination does not confirm progress in that artifact. Mobile comprehension is workable but scroll-heavy: the case and streak panels come first, followed by stamps, sharing, history, and longer explanations. Restore and browser-verify /blog, then add a compact mobile how-it-works summary and one trust cue near the homepage entry point.

Evidence
Blog response in supplied capture
Application failed to respond
Homepage desktop CLS
0.44
Contact response expectation
Two business days

04 · Accessibility — PSI reaches 100, with strong landmarks and labelled controls

Wrongscape has a strong automated accessibility baseline. PSI reports an accessibility score of 100 for the homepage, and the sampled pages expose header, navigation, main, and footer landmarks. The homepage DOM reports two inputs with no controls lacking a detected label or ARIA name, and zero positive tabindex values. The supplied 390px capture shows the game reflowing into a single readable column without an evidenced horizontal-clip defect. No P0–P3 defect is verified from the supplied artifacts. That result is not a substitute for interaction testing: tab order, focus trapping and restoration, screen-reader announcements, dynamic game-state updates, and media-caption behaviour remain follow-up checks. A visible-on-focus skip link would still improve keyboard efficiency if verified across the page templates.

Evidence
PSI accessibility score
100
Sampled inputs without detected label or ARIA name
0 of 2
Positive tabindex values
0

05 · Design execution — cohesive dark-and-gold system, undermined by shift and touch-target data

Wrongscape presents a distinctive dark-and-gold interface with clear grouping and a strong primary action. The visible hierarchy leads with the daily case, supports it with the streak panel, and moves secondary context into stamps and history. Execution weakens on mobile and at layout boundaries: homepage CLS is 0.440 on desktop and 0.424 on mobile, while the 390px render records controls as small as 32×36px. A sampled input is 13.4px, below the supplied 16px mobile guidance. Expand compact controls to at least 44×44px, raise the input to 16px, and reserve dimensions for shifting media and dynamic panels. The CSS inventory reports 190 colors and 67 font sizes; validate rendered nodes before consolidating tokens.

Evidence
Homepage CLS
0.440 desktop; 0.424 mobile
Small mobile controls
32×36px
Sampled mobile input font size
13.4px

06 · Performance — 5.24 s mobile LCP and 0.424 CLS expose an asset-heavy critical path

Wrongscape is quick at the server boundary but slow and unstable on the tested mobile path. The homepage reached largest content in 5.24 seconds and recorded 0.424 CLS; desktop LCP was 277 ms, yet desktop CLS remained 0.44. PSI measured an 11 ms server response, so origin latency is not the first suspect. The clearest client costs are a 344,852-byte image-delivery saving estimate, 512×512 badge sources displayed around 110px, and a 345 KiB Google Tag Manager load. Right-size badge variants, reserve the LCP and dynamic-content boxes, and defer non-essential measurement. The evidence is lab-only: no CrUX field data was returned, so these numbers are a directional performance diagnosis rather than a population-wide result.

Evidence
Mobile LCP
5,237.306 ms
Mobile CLS
0.423551
Image-delivery saving estimate
344,852 bytes
Google Tag Manager transfer
345 KiB

07 · Writing quality — concrete rules and comparisons carry the voice; the blog path breaks the editorial surface

Wrongscape’s writing is strongest when it turns the puzzle into a concrete set of rules: five scenes, a 60-second clock, one final confirmation per photo, 10–100 point clues, and a 500-point daily maximum. The comparison articles also distinguish different game mechanics instead of making a blanket alternative claim. The main weakness is operational. The crawl records HTTP 502 for /blog and captures "Application failed to respond", interrupting the route from play to editorial content. Mechanical hygiene is uneven too: sampled titles run from 69 to 76 characters, and eight homepage images are recorded without alt text. Restore the blog index, add concise image alternatives where images are informative, and trim titles so the topic and Wrongscape name lead.

Evidence
Puzzle rules
Five scenes; 60-second clock; 10–100 point clues; 500-point daily maximum
Blog status
HTTP 502
Sampled title lengths
69–76 characters
Homepage images without alt text
8

08 · Review-content integrity — dated, sourced comparison, but methodology is not explicit enough

The supplied candidate takes an honest comparison-guide posture. It is dated November 17, 2026, distinguishes four game mechanics, includes a Sources and further reading section, and reports no affiliate-link sample. The supplied text and screenshots contain no visible "we tested" or hands-on claim, so the evidence is not inflated. The missing trust signal is methodological visibility. Add a short block before the game-by-game sections stating the criteria, evidence basis, hands-on status, and next verification date. Keep the source list, but attach named sources or official pages to decision-critical mechanic claims. Because the supplied article extract and structured-data evidence are incomplete, schema alignment and a complete claim inventory should remain pending checks rather than editorial accusations.

Evidence
Publication date
November 17, 2026
Affiliate-link sample
None reported
Visible source section
Sources and further reading

09 · Risk & stability — a localized 502 is the clearest exposure, not a sitewide indexing failure

Wrongscape’s supplied evidence points to a localized availability problem rather than a sitewide indexing catastrophe. The homepage is 200, robots.txt allows the public surface, canonicals are self-referential in the inventory, and the raw-versus-rendered sample shows no client-side-only metadata dependency. The fix-now item is /blog: it returns 502, appears in the verified sitemap, and is linked from homepage navigation. Mobile lab performance adds an engagement risk, with LCP at 5,237 ms and CLS at 0.424, but no CrUX field data is available. Do not attribute traffic loss or recovery magnitude without GSC, analytics, or historical records; those sources were unavailable. Repair /blog, then recheck every sitemap and navigation reference after deployment.

Evidence
Blog status
502
Blog sitemap presence
inSitemap=true
Mobile lab LCP and CLS
5,237 ms and 0.424

10 · Editorial QA of content — strong source discipline, but release checks would stop the current hub

The sampled corpus shows a real QA instinct: comparison claims are organized around the reader’s decision, sources are named, limitations are disclosed, and the pages use a short standfirst, author/date metadata, contents list, ordered headings, source sections, and related links. The release gate would still stop the editorial hub today because /blog returned HTTP 502 and its captured heading is "Application failed to respond". Mechanical checks also need to be repeatable: sampled titles run from 69 to 76 characters, and eight homepage images lack alt text, with the pattern repeated across localized homepages. Add automated checks for index availability, title length, alt coverage, and source support before publication. The writing habits are already sound; the missing piece is enforcement.

Evidence
Blog index status
HTTP 502
Sampled title lengths
69–76 characters
Homepage images without alt text
8

11 · Docs & self-serve help — useful FAQ, but no clearly discoverable help surface

Wrongscape has an appropriate lightweight self-serve layer for a consumer puzzle: the homepage FAQ answers questions about selecting objects, scoring, the 00:00 UTC reset, practice, sharing, and the AI-reconstructed image premise. Keep the FAQ as the canonical answer source, but give it a clearly labelled Help or FAQ entry point beside the play guidance. Add a last-reviewed date and revisit timing-sensitive answers when reset or sharing behaviour changes. This preserves the game’s compact scope while making practical answers easier to locate and easier to trust.

Evidence
FAQ coverage
Scoring, reset, practice, sharing, and AI-reconstructed images
Dedicated documentation subtree
None found
Reset rule
00:00 UTC

12 · Technical SEO — crawl foundation is sound, but sitemap-listed /blog returns 502

Wrongscape has a broadly crawlable foundation: robots.txt allows the public site and declares the sitemap, the verified sitemap contains 191 URLs, a nonexistent URL returns a real 404, HTTP makes one 301 hop to HTTPS, and sampled pages are marked js_dependent=false. The primary technical blocker is /blog, which returns 502 while remaining sitemap-listed and linked from homepage navigation. Repair that route, then verify a 200 response, self-canonical, and clean sitemap reference. The homepage also needs a technical performance pass: mobile LCP is 5,237 ms, mobile CLS is 0.424, and desktop CLS is 0.440. HSTS is absent from the sampled response, while extracted JSON-LD contains VideoGame and FAQPage but no Organization; both are polish opportunities after availability is fixed.

Evidence
Verified sitemap URLs
191
HTTP to HTTPS redirect
301, one hop
Blog status
502 while inSitemap=true
Homepage mobile LCP and CLS
5,237 ms and 0.424

Verdict — 75/100: strong concept, uneven execution

Wrongscape is a strong fit for curious trivia and history or geography learners who enjoy visual deduction and daily challenges. Its daily five-photo mechanic is easy to grasp, the free browser format removes entry friction, and the explanations and linked sources give each case value beyond the initial guess. A 100/100 accessibility result and an 85.1/100 writing-quality score support that clarity.

Three fixes should come first. Make the category more explicit in the hero, where the category is clearer in the meta description than in the opening presentation. Improve the tested mobile critical path and layout stability: the homepage's largest content arrived at 5.24 seconds, while CLS reached 0.424 in the mobile lab and 0.440 on desktop. Restore /blog or remove its public references until it is available; it currently returns 502 while remaining in navigation and the sitemap.

The product already has a distinctive premise. Better first-screen clarity, steadier loading, and a working public content route would bring the execution closer to the quality of the puzzle itself.

Evidence
Overall score
75/100
Writing quality
85.1/100
Performance
60.3/100
Technical SEO
78.7/100

Methodology & data notes

This is a 13-dimension review based on a crawl of 40 pages completed on 2026-11-17, supplied product facts, and the public dimension score table. The review uses the available site evidence for positioning, messaging, usability, accessibility, design execution, performance, writing, content integrity, risk and stability, editorial QA, self-serve help, and technical SEO.

Dimension 12 — Decision-support surfaces — was excluded because it failed. Enrichment pending: Google Search Console was not connected and access was unavailable, so no GSC evidence is included. Pricing is stated plainly as free to play in a browser, with a $0 range.

Read How SiteList scores for the full methodology and evidence conventions.

Evidence
Review dimensions
13-dimension review
Pages crawled
40
Excluded dimension
12 · Decision-support surfaces (failed)
GSC enrichment
Not connected; access unavailable

Questions buyers actually ask

Is Wrongscape free to play?

Yes. Wrongscape is free to play in a browser on a phone, tablet, or computer. Nothing needs to be installed, and no account is required to start.

Are Wrongscape's images real photographs?

No. Each scene is an AI-generated reconstruction marked "AI reconstruction". The deliberate mistakes are explained with the relevant history or geography and linked sources.

When does the daily case reset?

A new case starts at 00:00 UTC each day. Wrongscape shows the countdown in local time, so players can see when the next case begins in their own time zone.

Can I replay past Wrongscape cases?

Past cases remain available in the archive, but they cannot be replayed for points. The full answers stay available for learning.

Do I need an account to play?

No account is needed to begin. Signed-in players can earn stamps and streaks by completing all five daily photos; guest play does not show passport appearances.

How this review was made

SiteList reviewed wrongscape.io on November 20, 2026 — pages, screenshots, performance runs, structured data and public records — then scored it across 12 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: Decision-support surfaces (could not be 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): Brand and category SERP samples could not run because no SERP endpoint was configured, SERP and Reddit voice-of-customer searches were not available because no SERP endpoint was configured, Playwright validation of the hash-route tutorial flow, mobile navigation and /blog render., A supplied About-page capture or live verification of its team and credibility content., Live axe-core scan with affected nodes, Scripted keyboard tab-order and focus-management probe, Screen-reader announcements for dynamic game state and dialog behavior, Manual verification of caption accuracy if media is present…

Read the full methodology

75/100WrongscapeJump to review