Journest — Путеводитель по миру

Откройте для себя удивительные страны, города и достопримечательности по всему миру.

Tailwind CSS

Report generated on April 5, 2026

journest.app
Screenshot of journest.app

A note on how to read this

This report is ProdPoke's take on your site — think of it as a first impression from a very opinionated robot. We check real things (load times, broken links, accessibility patterns), but we also try to understand what your site is trying to do and whether the technical details support that goal. Some of our observations might not apply to your specific situation, and that's okay. We're getting sharper with every scan. If something feels off, tell us — it makes us better.

Key Insights for Journest — Путеводитель по миру

All five core destination pages (homepage, Countries, Cities, Islands, Places) are returning 502 errors—your travel guide platform is completely inaccessible.

Users cannot reach any content on Journest, meaning zero traffic can discover your destination guides, compare countries, or plan trips. This is a total service outage blocking all business activity.

Six interactive destination filters and two search inputs lack accessible names—screen reader users can't understand how to explore your travel guides.

Assistive technology users (estimated 15% of web users) cannot use your discovery features to browse countries, cities, or places. You're excluding travelers with disabilities from your core product.

Your analytics script (analytics.journest.app/script.js) is blocked by browser security policies (ORB), so you're collecting zero behavioral data on how users explore destinations.

Without analytics, you cannot measure which countries or cities attract the most interest, which guides drive engagement, or where users drop off during trip planning—making data-driven product decisions impossible.

Missing Open Graph image tags mean your destination guides display as plain text links on social media instead of showing attractive preview images of countries, cities, or islands.

When travelers share your guides on Facebook, Twitter, or messaging apps, potential users see no visual preview. This directly reduces click-through rates on travel recommendations.

Pages load 97 HTTP requests, which creates slow navigation between destination categories—particularly painful when users browse multiple countries or cities.

Travel research requires fast switching between guides. Slow load times increase bounce rates when users want to quickly compare destinations before planning a trip.

What ProdPoke understands about Journest — Путеводитель по миру

I was unable to determine what Journest does based on the pages explored. All five pages—the homepage (journest.app/en), Countries, Cities, Islands, and Places sections—returned a '502 Bad Gateway' error message displayed by nginx. No product features, content, navigation elements, or business information were visible on any of the pages. The website appears to be experiencing a server connectivity issue that prevented me from observing the actual product content.

Based on exploring 5 pages across the site

First Impression — How clear is your site?

85
Crystal clear

Journest is a travel destination discovery platform with the tagline 'Where to next?' and 'Find your perfect travel destination.' Users can search for countries, cities, islands, and places using a search bar, then explore categorized destinations like Megacities, Capitals, History, Islands, Resorts, and 'Warm Now' through browsable cards with 'Explore' buttons.

This score measures how quickly a first-time visitor understands what your site does — based on visible headings, navigation, and visual hierarchy alone.

79/ 100

Overall Score

Good start — room to grow.

Performance

92/100

High request count: 97 requests

medium

The travel guide pages make 97 HTTP requests, which slows down initial load time for users browsing destinations. High request counts are particularly problematic for travel research, where users expect fast navigation between countries and places.

Expected: Under 50 requests
Found: 97 requests

SEO

92/100

Missing Open Graph tags: og:image

medium

Missing Open Graph image tag means Journest travel guides won't display an attractive preview (destination photo, map, or branded image) when users share links to countries, cities, islands, or places on social media—reducing click-through rates on travel recommendation posts.

Expected: og:title, og:description, og:image all present
Found: Missing: og:image

Accessibility

70/100

6 interactive element(s) without accessible names

high

Six interactive elements on Journest (likely filters, toggles, or navigation controls for exploring destinations) lack accessible names. Screen reader users cannot determine what these travel discovery controls do.

Expected: All interactive elements have accessible names
Found: 6 missing: <input[type=text].hero-search-input>, <a>, <a>, <button[type=submit].p-1>, <input[type=text].input-field>

2 form input(s) without labels

high

Two form inputs (possibly search fields or travel preference filters) lack associated labels. This makes it difficult for assistive technology users to understand what information they should enter when searching for destinations or filtering travel guides.

Expected: Every input has a <label> or aria-label
Found: Missing labels: text: Country, city or place..., text: Ask a travel question...

Functional

38/100

Dead link: Connection failed — Journest

likelyhigh

The main Journest homepage link (https://journest.app/en) is returning connection errors. Visitors cannot access the travel guide platform's home page.

Expected: Link should return a valid page (200)
Found: Connection failed

Dead link: Connection failed — Countries

likelyhigh

The Countries section (https://journest.app/en/countries) is returning connection errors. Users cannot browse the destination catalog by country.

Expected: Link should return a valid page (200)
Found: Connection failed

Dead link: Connection failed — Cities

likelyhigh

The Cities section (https://journest.app/en/cities) is returning connection errors. Users cannot explore travel guides organized by city.

Expected: Link should return a valid page (200)
Found: Connection failed

Dead link: HTTP 502 — Islands

likelyhigh

The Islands section (https://journest.app/en/islands) returns an HTTP 502 error. Users cannot access island destination guides.

Expected: Link should return a valid page (200)
Found: HTTP 502

Dead link: HTTP 502 — Places

likelyhigh

The Places section (https://journest.app/en/places) returns an HTTP 502 error. Users cannot access specific travel destination guides.

Expected: Link should return a valid page (200)
Found: HTTP 502

1 button(s) with no visible text or icon

medium

One button on Journest (likely a key action such as 'search destinations' or 'explore more') has no visible text or icon. Users cannot understand what this travel discovery button does.

Expected: All buttons have visible text or icon
Found: 1 empty buttons

Technical Health

Network request failed: https://analytics.journest.app/script.js

likelyhigh

Journest's analytics script (https://analytics.journest.app/script.js) is blocked by browser security policies (ORB). This prevents the travel guide platform from tracking user behavior across its destination guides and discovery features.

Compliance

97/100

Cookie consent banner found but no cookie policy link

medium

Journest displays a cookie consent banner but does not link to a dedicated cookie policy. For a travel platform that may use analytics and tracking for destination recommendations, users cannot review what data is being collected or how it's used.

Key Metrics

Crawlability

Robots.txt
Broken Links5

Standards

HTTPS
Mobile Responsive
Images Missing Alt0

Improvement Plan

Journest is currently experiencing a critical infrastructure crisis: all five core pages return 502 Bad Gateway errors, meaning the travel guide platform is completely offline. This must be your immediate priority. Contact your hosting provider or DevOps team to restore server connectivity. Until the homepage, Countries, Cities, Islands, and Places sections are accessible, no other improvements matter.

Once the site is live again, your second priority is accessibility. Six interactive destination filters and two unlabeled search inputs are blocking screen reader users from discovering your guides. Add descriptive aria-labels to all filter buttons and toggles (e.g., 'Filter by continent', 'Sort by popularity'). Associate labels with your search and preference inputs so assistive technology users understand what data to enter. These fixes take hours but make your platform usable for travelers with disabilities.

Your third priority is analytics recovery. Your analytics script is blocked by browser security policies, leaving you blind to user behavior. Migrate your analytics domain (analytics.journest.app) to a first-party domain (e.g., tracking.journest.app or journest.app/analytics) to bypass ORB restrictions. Without this data, you cannot measure which destinations drive engagement or optimize your destination guides.

Add Open Graph image tags to every destination guide page immediately after. When travelers share links to specific countries, cities, or islands, these tags will display attractive preview images (destination photos, maps, or branded graphics) on social platforms. This simple addition dramatically increases click-through rates on travel recommendations.

Finally, audit and consolidate your 97 HTTP requests. Combine CSS files, defer non-critical JavaScript, and lazy-load destination images. Fast page loads are essential for travel research, where users expect seamless navigation between countries and places.

Suggested priority order:

  1. 502 Bad Gateway errors on all pages (infrastructure outage)
  2. 6 interactive elements without accessible names (accessibility barrier)
  3. 2 form inputs without labels (accessibility barrier)
  4. Analytics script blocked by ORB (data collection failure)
  5. Missing Open Graph image tags (social sharing impact)
  6. 97 HTTP requests causing slow load times (performance)
  7. 1 button with no visible text or icon (UX clarity)
  8. Cookie policy link missing from consent banner (compliance)

This is your site? Get the full picture.

Claim this report to unlock ongoing monitoring, deeper analysis, and actionable alerts.

What is ProdPoke?

Automated analysis generated on April 5, 2026. Not professional advice. Contact us to modify or remove this report.