Website review, no card needed

tripscout.co logo

tripscout.co website review

Visit site (opens in a new tab)Reviewed 29 October 202636 issues · 73 checks

This review found 36 issues worth fixing on tripscout.co, 13 of them high impact, across 73 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
4.8 s1.7 sMay 9Oct 32.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.4 s
May 16, 20264.4 s
May 23, 20264.3 s
May 30, 20264.0 s
Sep 26, 20262.9 s
Oct 3, 20262.1 s

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 tripscout.co (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tripscout.co at 0.4 s0.4 s
  2. tripscout.co at 0.8 s0.8 s
  3. tripscout.co at 1.1 s1.1 s
  4. tripscout.co at 1.5 s1.5 s
  5. tripscout.co at 1.9 s1.9 s
  6. tripscout.co at 2.3 s2.3 s
  7. tripscout.co at 2.6 s2.6 s
  8. tripscout.co at 3.0 s3.0 s

Speed

9 to fix52
  • Improve image delivery

    44.5 s · 9.8 MB

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

  • Use efficient cache lifetimes

    2.5 s · 396 KiB

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

  • Reduce unused JavaScript

    1.8 s · 348 KiB

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

  • Mobile performance score: 52

    52/100

    Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Facebook and InMobi and others), adding 930 KiB and 824 ms of main-thread time.

  • Render-blocking requests

    750 ms

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

  • Google Tag Manager adds 329 ms

    329 ms

    Google Tag Manager costs a phone 329 ms of main-thread work and 288 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.

  • Facebook adds 287 ms

    287 ms

    Facebook costs a phone 287 ms of main-thread work and 278 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.

  • InMobi adds 208 ms

    208 ms

    InMobi costs a phone 208 ms of main-thread work and 361 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.

  • 10 long tasks on the main thread

    10 long tasks block the main thread while loading, the longest for 225 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    24 KiB

    Polyfills for old browsers add 24 KiB JavaScript that modern phones do not need.

  • 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.

2 checks passed
  • Main-thread work: 1.9 s

    A phone's processor spends 1.9 s on main-thread work while loading, 1.0 s of it running JavaScript. That is comfortably low.

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

4 to fix52
  • Largest Contentful Paint: 54.3 s

    54.3 s

    Your largest element takes 54.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “If you wish to opt-out of the sale, sharing to third partie…”.

  • Speed Index: 15.6 s

    15.6 s

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

  • Time to Interactive: 54.4 s

    54.4 s

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

  • Total Blocking Time: 522 ms

    522 ms

    Scripts block taps and scrolling for 522 ms in total while the page loads. Good is under 200 ms.

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

3 checks passed
  • Largest content (LCP) got 44% faster for real visitors

    -44%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.4 s to 2.1 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).

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

Images and page weight

5 to fix18
  • Page weight: 11.2 MB in 45 requests

    11.2 MB

    Your homepage downloads 11.2 MB in 45 requests on a phone: images 10.1 MB (6), scripts 984 KiB (18) and other files 94 KiB (13). Under 2 MB keeps phones on slow connections fast.

  • 5 images over 500 KB

    5 images weigh 8.2 MB together. On a phone connection a single image that size takes seconds.

  • 4 images far larger than shown

    3.8 MB

    4 images are downloaded at several times the size a phone draws them, for example tropical-beach.jpg at 1,248 px wide, shown at 390 px. Resized copies would save about 3.8 MB.

  • 5 images in older formats

    5 images (8.2 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 4 images below the first screen load straight away

    4 images further down the page (6.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 3.2 g of CO₂ per visit

    3.18 g

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

Accessibility

4 to fixGoogle 8892
  • Certain ARIA roles must be contained by particular parents (1 element)

    Certain ARIA roles must be contained by particular parents: 1 element on the page fails this check, rated critical by axe-core.

  • 3 text elements with low contrast

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 10 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

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

SEO

7 to fixGoogle 10074
  • Title is short (9 characters)

    Your title is only 9 characters: “Tripscout”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://tripscout.co/sitemap.xml, so Google discovers your pages only by following links.

  • Only 3 internal links

    The homepage links to only 3 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

3 checks passed
  • Meta description: 87 characters

    Your meta description is 87 characters: “The whole trip, scouted — flight, hotel, and the context that makes now the right time.”.

  • One H1 headline

    Your main headline reads: “Cheap Flights + Great Hotels. Straight to your inbox.”.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://tripscout.co/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

2 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.

  • Text is in the HTML

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

Other pages

1 to fix93
  • 2 pages share a title

    / and https://tripscout.co/onboarding/airports all use the title “Tripscout”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page with very little text

    https://tripscout.co/onboarding/airports has 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.

  • 1 internal page checked

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

6 checks passed
  • Linked pages load

    All 1 page 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 1 page that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 1 page that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 5 small tap targets

    5 of 13 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 404 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • 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 503 words of copy

    The homepage carries about 503 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Get started”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Get started”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies (measured from a US location before any click).

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 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.

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 tripscout.co, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Analytics
Google Tag Manager
Hosting
Vercel

Hiring

Hiring
1 open role
Teams
Open Role (1)
Job board
lever

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on tripscout.co, including 13 speed issues, 7 SEO issues and 2 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