Timelinevisualizer Review: strong browser utility (84/100)

Field	Value
Domain	timelinevisualizer.org
Category	Browser-based Google Maps Timeline visualizer and travel-video exporter
Pricing	Free; price range 0–0 USD
Pages crawled	7
Crawl date	2026-10-31

Timelinevisualizer is a focused browser utility that turns Google Maps Timeline exports into shareable travel videos while keeping the source file in the browser. The strongest results are usability and accessibility, both scored at 100/100, supported by a clear path from export to replay and strong baseline page structure.

The product also performs well for writing quality at 86/100, decision-support surfaces at 87/100, risk and stability at 92/100, and technical SEO at 83.3/100. Audience and messaging score 81.4/100, with first impressions and positioning at 80.1/100.

The main constraint is performance: the dimension scores 58/100, and both homepage PageSpeed Insights runs returned no lab or field metrics, so a valid Core Web Vitals verdict is not available from this crawl. Design execution remains strong at 76.9/100, but the review flags mechanical issues with several mobile controls. The result is a useful, unusually direct browser workflow whose next gains are practical: resolve the performance measurement gap and refine the mobile interaction details.

Timeline Visualizer makes its core job clear in five seconds: turn a Google Maps Timeline export into a shareable travel video. The hero names the input, replay behavior, and outcome, then pairs that promise with the concrete claim that the file stays in the browser. The FAQ adds an important boundary: default map tiles go to CARTO, while Privacy mode removes tile requests. That precision gives the local-processing message credibility. The audience is still defined by the task rather than a named segment, and the supplied evidence contains no direct competitor frame. Add a short audience cue such as travelers or road-trippers, then position the product as a private travel-video maker while retaining the tile qualification.

A visitor with Google Timeline data can understand the offer, start without an account, and get concrete answers about formats, export steps, and local processing. The homepage and FAQ cover Records.json, timelineObjects, semanticSegments, coordinate arrays, Android and iPhone export steps, MP4 versus WebM behavior, large files, and sharing destinations. That is strong decision support for a self-service browser utility. The remaining friction is audience specificity: the user is inferred from the job rather than named above the fold. The evidence also shows no comparison surface and no attributable finished-trip outcomes. Add one audience phrase beside the H1, keep the export guide adjacent to the upload action, and add a sourced example of a completed trip video.

The supplied crawl shows a low-friction path for both core goals: understand the product and find the export instructions. The headline explains the job, the Open Timeline JSON action gives a direct start, and the local-file and no-account messages answer immediate trust questions. The plainly named How to export link reaches the guide in one click, while the Guides card repeats the Android and iPhone scope. All six simulated task-persona runs completed cleanly. This remains a crawl-based result, not live user testing: only the homepage has a mobile screenshot, PageSpeed Insights returned no usable metrics, and 7 of 40 pages were crawled. Preserve the current path and test the export destination at mobile widths.

The sampled pages show a strong heuristic accessibility baseline. They expose header, nav, main, and footer landmarks, declare lang="en", keep orderly heading sequences, report zero missing image alt attributes in the sampled checks, and report zero positive tabindex values. The captured stylesheet contains 41 focus rules, 25 focus-visible rules, and four prefers-reduced-motion matches, with no outline:none or outline:0 matches. One homepage input is a candidate for missing naming, but the supplied summary says that this is not a complete accessible-name computation, so it is a verification item rather than a defect. Confirm that control in the rendered DOM and accessibility tree, then consider a skip link.

Timeline Visualizer has a coherent editorial surface: the hero establishes a clear path from headline to local-file action, section separation is generous, and the desktop and 390px homepage captures remain visually consistent. The mechanical debt is concentrated on mobile. Small tap targets appear 5 times on the homepage, 3 times on Guides, 10 times on the travel-video article, and 4 times on the export guide; the homepage header controls are 40px high, and related links reach 17px high. Homepage mobile paragraphs also measure 12px. Give controls and compact links 44px hit areas, raise mobile copy to at least 14px, and make Open Timeline JSON the sole filled hero action. Consolidate the 16 radius values after these interaction fixes.

A valid Core Web Vitals verdict is not available: both homepage PageSpeed Insights runs returned no lab or field metrics. The available network evidence still points to a transfer and third-party budget issue. The MIME summary does not support a precise JavaScript-versus-image diagnosis, so start with a typed waterfall. Audit and defer non-essential tags, confirm the role of the 147 KB coastal JPEG before converting it, and review the three font families. Treat the 58/100 score as provisional until a successful mobile trace supplies LCP, INP or TBT, CLS, TTFB, and resource attribution.

The copy is strongest when it names the user's actual files and formats rather than relying on broad promises. It identifies Timeline.json, Records.json, and location-history.json, along with timelineObjects and semanticSegments, and it explains Android and iPhone export details. The openings also establish the local-processing, no-account, and browser-based workflow quickly. Presentation has two clear polish items: the comparison table on /timeline-visualizer-app reaches 461px at a 390px viewport, and the crawl flags two images without alt text per page. Add touch scrolling to the table, provide descriptive alt text for functional images, and keep decorative icons empty. This preserves the direct voice while removing mobile friction.

The Web app or APK page is useful because it compares three options across six practical questions and does not force the web app to win every scenario. It recommends the web app for a no-install path across iPhone and Android, an APK when native Android matters, and an open-source desktop project when running code or self-hosting matters. The main weakness is provenance. Several cells say ~ Varies without naming a project or version, and the page supplies no dated how-we-compared note or source list. Keep the three-way choice architecture, but scope each uncertain cell to a project or version and add a short dated method note below the table.

The comparison guide has a restrained commercial shape: the supplied evidence shows zero affiliate links, no Review or AggregateRating markup, and genuine tradeoffs for the APK and open-source alternatives. That is a sound basis for reader trust. The missing layer is evidentiary disclosure. Phrases such as "a genuinely good tool" and "the fastest path for most people" are judgments, while the page names no versions, sources, sample, or test conditions. The claim that "most walkthroughs" recommend alternatives is also uncited. Add a dated methodology block with criteria, compared versions, evidence sources, and an explicit no-hands-on-testing statement when applicable; otherwise narrow broad synthesis to the site's documented alternatives.

The sampled site is broadly stable and indexable: 7 crawled pages returned 200 with self-canonicals, the sitemap contains 9 URLs, the nonexistent probe returned 404, and raw and rendered word counts matched on all 7 pages. No sitewide noindex, Disallow: /, redirect loop, or 5xx cluster was found. The most actionable risk is that the HTTP root returned 200 instead of redirecting to HTTPS. The app page also measured 461px of scroll width at a 390px viewport. The domain was registered on 2026-08-24 and has one sampled Wayback snapshot from 2026-10-22, so historical conclusions are unavailable. Add the HTTPS redirect, fix the overflow, and connect GSC and analytics before making traffic-loss claims.

The editorial QA evidence points to strong technical discipline. The guides address Google Maps changes and Takeout file behavior, explain Safari MediaRecorder output limits, and align homepage FAQPage data with visible FAQ content. The /make-travel-video-from-google-maps page also uses HowTo data that matches its on-page three-step workflow. The main editorial cleanup is repetition: the internal link log records "make a video" 12 times, "how to export" 12 times, and "timeline visualizer" 12 times. Vary those anchors with contextual phrases while retaining descriptive navigation. Enforce the HTTP-to-HTTPS redirect as the related technical hygiene fix.

The documentation surface has the right lightweight shape for a browser utility. Guides is linked from the main navigation and footer, presents five topic cards, and sits alongside a homepage FAQ covering privacy, formats, sharing, devices, and official status. The hub has six inbound links, and llms.txt lists the guides and core product pages. Retrieval will become harder as the collection grows because the captured hub has no search box, breadcrumbs, or sidebar navigation. The crawl also captured the index rather than complete guide bodies, so prerequisites, expected outputs, and troubleshooting depth remain to be verified. Add breadcrumbs and related-guide links, publish a visible update date, and keep FAQ and llms.txt entries synchronized.

The sampled technical SEO foundation is sound: robots.txt allows the public surface, declares the sitemap, the sitemap parses with 9 URLs, and all 7 crawled pages returned 200 with self-canonicals. Raw and rendered word counts matched on all 7 pages, so this sample shows no JavaScript rendering gap. The highest-priority issue is the HTTP root, which returned 200 without an HTTPS redirect. The app page also measures 461px at a 390px viewport, and HSTS was not observed in sampled HTTPS headers. Homepage structured data includes SoftwareApplication and FAQPage, while the hreflang set lists en, zh, id, vi, ko, ja, and x-default. Ship the redirect, fix overflow, add HSTS after host verification, then broaden locale and URL checks.

Timelinevisualizer earns 84/100 because its core promise is clear and its main workflow is unusually low-friction. People with Google Maps Timeline or location-history JSON can begin without an account, use supported formats, replay a route, and record the canvas locally. The local-processing message is the product’s clearest strength.

Two fixable weaknesses keep the result from being stronger. Performance is the lowest scored dimension at 58/100, and the supplied PageSpeed runs provide no lab or field metrics, leaving Core Web Vitals unresolved. Design execution is 76.9/100, with several mobile controls flagged for mechanical refinement.

This product is for people who want to turn their own location-history export into a replayable or shareable travel video while keeping the source file local. It is a strong fit for a direct browser workflow, provided the performance evidence and mobile details receive another pass.

This is a 13-dimension review based on the supplied crawl of 7 pages on 2026-10-31, together with the product facts and public dimension score table provided to SiteList. The scored dimensions in this frame are 01, 02, 03, 04, 05, 07, 09, 12, 13, 17, 19, 23, and 25. Dimensions outside that supplied set are excluded from this article frame because no public score or summary was provided; this review does not infer results for them.

Google Search Console enrichment was not connected or available in the supplied inputs, so no Search Console findings are included. Performance claims are limited to the reported PageSpeed result: both homepage runs returned no lab or field metrics. The crawl also records that the site is new, with RDAP registration on 2026-08-24 and one Wayback snapshot, so historical stability evidence is limited.

Read the full SiteList methodology for the review framework, evidence handling, and scoring approach.