Website review, no card needed

polarsteps.com logo

polarsteps.com website review

Visit site (opens in a new tab)Reviewed 25 October 202630 issues · 76 checks

This review found 30 issues worth fixing on polarsteps.com, 13 of them high impact, across 76 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
5.0 s2.3 sMay 2Oct 172.9 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.6 s
May 9, 20264.7 s
May 16, 20264.6 s
May 23, 20264.6 s
May 30, 20264.6 s
Jun 6, 20264.6 s
Jun 13, 20264.6 s
Jun 20, 20264.5 s
Jun 27, 20264.4 s
Jul 4, 20264.3 s
Jul 11, 20264.2 s
Jul 18, 20264.1 s
Jul 25, 20263.9 s
Aug 1, 20263.4 s
Aug 8, 20263.1 s
Aug 15, 20262.8 s
Aug 22, 20262.6 s
Aug 29, 20262.7 s
Sep 5, 20262.8 s
Sep 12, 20262.8 s
Sep 19, 20262.7 s
Sep 26, 20262.7 s
Oct 3, 20262.7 s
Oct 10, 20262.8 s
Oct 17, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
319 ms242 msMay 2Oct 17260 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026292 ms
May 9, 2026275 ms
May 16, 2026259 ms
May 23, 2026253 ms
May 30, 2026251 ms
Jun 6, 2026253 ms
Jun 13, 2026260 ms
Jun 20, 2026269 ms
Jun 27, 2026279 ms
Jul 4, 2026285 ms
Jul 11, 2026282 ms
Jul 18, 2026281 ms
Jul 25, 2026285 ms
Aug 1, 2026293 ms
Aug 8, 2026301 ms
Aug 15, 2026310 ms
Aug 22, 2026305 ms
Aug 29, 2026294 ms
Sep 5, 2026278 ms
Sep 12, 2026256 ms
Sep 19, 2026253 ms
Sep 26, 2026259 ms
Oct 3, 2026261 ms
Oct 10, 2026260 ms
Oct 17, 2026260 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of polarsteps.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. polarsteps.com at 0.4 s0.4 s
  2. polarsteps.com at 0.8 s0.8 s
  3. polarsteps.com at 1.2 s1.2 s
  4. polarsteps.com at 1.6 s1.6 s
  5. polarsteps.com at 2.0 s2.0 s
  6. polarsteps.com at 2.4 s2.4 s
  7. polarsteps.com at 2.8 s2.8 s
  8. polarsteps.com at 3.2 s3.2 s

Speed

9 to fix64
  • Improve image delivery

    2.7 s · 1.3 MB

    33 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.7 s faster on a phone.

  • framerusercontent.com adds 2.7 s

    2.7 s

    framerusercontent.com costs a phone 2.7 s of main-thread work and 3.0 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Reduce unused JavaScript

    1.1 s · 206 KiB

    About 206 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Main-thread work: 4.5 s

    A phone's processor spends 4.5 s on main-thread work while loading, 3.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 6 third-party services on the page

    6 third-party services load with your homepage (framerusercontent.com, cdn-cookieyes.com and framer.com and others), adding 3.7 MB and 2.8 s of main-thread time.

  • Mobile performance score: 64

    64/100

    Your mobile performance score is 64 (desktop: 80). Pages that score under 90 lose visitors before the first paint.

  • Use efficient cache lifetimes

    411 KiB

    8 files are served with short cache lifetimes, so returning visitors download them again (411 KiB).

  • 1,927 HTML elements

    The page has 1,927 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • YouTube adds 0 ms

    0 ms

    YouTube costs a phone 0 ms of main-thread work and 528 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Render-blocking requests

    150 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

  • Reduce unused CSS

    14 KiB

    About 14 KiB of CSS is downloaded but never applied on this page.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 208 ms

    208 ms

    Your server sent the HTML in 208 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix100
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Largest Contentful Paint: 14.4 s

    14.4 s

    Your largest element takes 14.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A traveler on a trip through Southeast Asia”.

  • Time to Interactive: 14.7 s

    14.7 s

    The page becomes fully interactive after 14.7 s. Good is under 3.8 s.

  • First Contentful Paint: 3.2 s

    3.2 s

    The first text or image appears after 3.2 s on a phone. Good is under 1.8 s.

  • Speed Index: 5.9 s

    5.9 s

    Visually, the page fills in at 5.9 s (Speed Index). Good is under 3.4 s.

  • Real-user FCP: 2.0 s

    2.0 s

    Real visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.

  • Tap response (INP) held steady for real visitors

    -8%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 292 ms to 260 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

7 checks passed
  • Real-user LCP: 2.5 s

    2.5 s

    Real visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 88 ms

    88 ms

    Real visitors wait 88 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.

  • Real-user TTFB: 767 ms

    767 ms

    Real visitors wait 767 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 39% faster for real visitors

    -39%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 4.6 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix68
  • Page weight: 3.8 MB in 93 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 93 requests on a phone: images 2.7 MB (47), scripts 791 KiB (35) and fonts 218 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 5 images far larger than shown

    183 KiB

    5 images are downloaded at several times the size a phone draws them, for example d7V759Z2rkhXK6iEx17ey1ekGU.jpg at 1,049 px wide, shown at 342 px. Resized copies would save about 183 KiB.

  • 6 images below the first screen load straight away

    6 images further down the page (341 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.1 g of CO₂ per visit

    1.08 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.08 g of CO₂e: 129.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

4 to fixGoogle 8793
  • 4 text elements with low contrast

    4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 6 images without alt text

    6 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (34 elements)

    All page content should be contained by landmarks: 34 elements on the page fail this check, rated moderate by axe-core.

  • 3 links without text

    3 visible links have no text or label, so screen readers cannot say where they go.

1 checks passed
  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

Google 92100
  • 54 internal links, 24 external

    The homepage links to 54 pages on polarsteps.com and 24 external pages.

8 checks passed
  • Meta description: 139 characters

    Your meta description is 139 characters: “Easily create travel itineraries and watch your route unfold on a beautiful world map. Join 20M+ travelers and download…”.

  • One H1 headline

    Your main headline reads: “One travel app for all your adventures”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Polarsteps Travel App | Plan, Track & Relive Your Trips”.

  • Canonical URL set

    The canonical URL is https://www.polarsteps.com/.

  • Structured data in place

    Structured data found: Organization.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.polarsteps.com/sitemap.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (753 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.polarsteps.com/llms.txt (4 KiB, 13 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix86
  • 3 pages share a title

    https://www.polarsteps.com/app, https://www.polarsteps.com/travel-book and https://www.polarsteps.com/gift-card all use the title “Polarsteps - Automatic Travel Tracker - Explore. Dream. Discover.”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages share a meta description

    https://www.polarsteps.com/app, https://www.polarsteps.com/travel-book and https://www.polarsteps.com/gift-card use the same meta description. A description written for each page earns more clicks.

  • 3 pages without an H1

    https://www.polarsteps.com/app, https://www.polarsteps.com/travel-book and https://www.polarsteps.com/gift-card have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://www.polarsteps.com/app, https://www.polarsteps.com/travel-book and https://www.polarsteps.com/gift-card have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 13 internal pages checked

    We fetched 13 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 13 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 13 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 4 small tap targets

    4 of 9 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 463 words of copy

    The homepage carries about 463 words of visible text.

2 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Trip Reel x Travel Book”, “Gift a Travel Book” and “Contact us”.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (measured from a US location before any click).

  • 10 other companies contacted

    Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) loads with the page.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at polarsteps.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Framer
Analytics
Google Analytics

Company

Founded
2015
Headquarters
Amsterdam

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on polarsteps.com, including 15 speed issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25