Website review, no card needed

moonlinetravel.com logo

moonlinetravel.com website review

Visit site (opens in a new tab)Reviewed 27 October 202639 issues · 73 checks

This review found 39 issues worth fixing on moonlinetravel.com, 11 of them high impact, across 73 checks. The most urgent: reduce unused JavaScript. 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
2.6 s1.5 sJun 6Oct 242.5 s
Show as table
DateReal-visitor load time (LCP)
Jun 6, 20262.0 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.8 s
Aug 29, 20261.9 s
Sep 5, 20261.7 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.6 s
Oct 3, 20262.1 s
Oct 10, 20262.2 s
Oct 17, 20262.3 s
Oct 24, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
121 ms86 msJun 13Sep 2695 ms
Show as table
DateReal-visitor tap response (INP)
Jun 13, 2026113 ms
Jun 20, 2026117 ms
Jun 27, 2026113 ms
Jul 4, 2026106 ms
Jul 11, 2026100 ms
Jul 18, 202695 ms
Jul 25, 2026109 ms
Aug 1, 202696 ms
Aug 8, 2026117 ms
Aug 15, 2026117 ms
Aug 22, 2026107 ms
Aug 29, 2026117 ms
Sep 5, 2026105 ms
Sep 12, 2026103 ms
Sep 19, 202690 ms
Sep 26, 202695 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 moonlinetravel.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. moonlinetravel.com at 0.8 s0.8 s
  2. moonlinetravel.com at 1.6 s1.6 s
  3. moonlinetravel.com at 2.4 s2.4 s
  4. moonlinetravel.com at 3.1 s3.1 s
  5. moonlinetravel.com at 3.9 s3.9 s
  6. moonlinetravel.com at 4.7 s4.7 s
  7. moonlinetravel.com at 5.5 s5.5 s
  8. moonlinetravel.com at 6.3 s6.3 s

Speed

8 to fix40
  • Reduce unused JavaScript

    2.6 s · 570 KiB

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

  • Improve image delivery

    1.2 s · 644 KiB

    19 images could be 644 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.

  • Mobile performance score: 40

    40/100

    Your mobile performance score is 40 (desktop: 66). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Use efficient cache lifetimes

    13.1 MB

    38 files are served with short cache lifetimes, so returning visitors download them again (13.1 MB).

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and Google Fonts), adding 806 KiB and 651 ms of main-thread time.

  • Google CDN adds 588 ms

    588 ms

    Google CDN costs a phone 588 ms of main-thread work and 741 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

    450 ms

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

  • Main-thread work: 3.9 s

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

  • 16 long tasks on the main thread

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

  • Reduce unused CSS

    33 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 66 but mobile only 40. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

Core Web Vitals

11 to fix50
  • 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: 9.2 s

    9.2 s

    Your largest element takes 9.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 23.5 s

    23.5 s

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

  • Cumulative Layout Shift: 0.265

    0.265

    The layout shifts by 0.265 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Real-user CLS: 0.17

    0.17

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

  • Largest content (LCP) got 28% slower for real visitors

    +28%

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

  • Real-user TTFB: 827 ms

    827 ms

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

  • Total Blocking Time: 540 ms

    540 ms

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

  • Speed Index: 5.1 s

    5.1 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

3 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Tap response (INP) got 20% faster for real visitors

    -20%

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

Images and page weight

4 to fix43
  • Page weight: 17.7 MB in 110 requests

    17.7 MB

    Your homepage downloads 17.7 MB in 110 requests on a phone: media 12.7 MB (2), images 1.8 MB (69) and fonts 1.5 MB (3). Under 2 MB keeps phones on slow connections fast.

  • 19 images in older formats

    19 images (1.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.

  • 19 images below the first screen load straight away

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

  • 10 images far larger than shown

    463 KiB

    10 images are downloaded at several times the size a phone draws them, for example hotel.jpg at 825 px wide, shown at 157 px. Resized copies would save about 463 KiB.

  • About 5.0 g of CO₂ per visit

    5.01 g

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

Accessibility

3 to fix89
  • 2 images without alt text

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

SEO

4 to fixGoogle 9283
  • Title is short (29 characters)

    Your title is only 29 characters: “Moonline Travel and Trade Ltd”. 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.

  • Only 4 internal links

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

5 checks passed
  • Meta description: 147 characters

    Your meta description is 147 characters: “Moonline travel and trade is a full-service travel agency and it has quickly grown to become a leading company in the r…”.

  • One H1 headline

    Your main headline reads: “Your one-step partner for everythingeverything inTravelTourismTravelTourismTravel”.

  • 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://moonlinetravel.com/sitemap.xml.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    4%

    A phone browser shows 1,227 words, but the HTML your server sends has only 45. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • 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://moonlinetravel.com/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.

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

Other pages

2 to fix93
  • 2 pages share a meta description

    https://moonlinetravel.com/about-us and https://moonlinetravel.com/contact-us use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://moonlinetravel.com/about-us and https://moonlinetravel.com/contact-us have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://moonlinetravel.com/about-us and https://moonlinetravel.com/contact-us 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.

  • 2 internal pages checked

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

6 checks passed
  • Linked pages load

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

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 2 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    16 of 17 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: 5 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 1,227 words of copy

    The homepage carries about 1,227 words of visible text.

1 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact Us”.

Privacy and tracking

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

  • 3 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Upkeep, stack and company

Stack

Framework
Nuxt
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on moonlinetravel.com, including 19 speed issues, 4 SEO issues and 4 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