Website review, no card needed

atlasvoyages.com logo

atlasvoyages.com website review

Visit site (opens in a new tab)Reviewed 30 October 202633 issues · 78 checks

This review found 33 issues worth fixing on atlasvoyages.com, 16 of them high impact, across 78 checks. The most urgent: use efficient cache lifetimes. 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
3.3 s1.9 sMay 9Oct 242.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.1 s
May 16, 20262.1 s
May 23, 20262.1 s
May 30, 20262.1 s
Jun 6, 20262.2 s
Jun 13, 20262.5 s
Jun 20, 20262.7 s
Jun 27, 20262.9 s
Jul 4, 20263.0 s
Jul 11, 20263.0 s
Jul 18, 20263.0 s
Jul 25, 20262.9 s
Aug 1, 20262.9 s
Aug 8, 20262.9 s
Aug 15, 20262.9 s
Aug 22, 20262.9 s
Aug 29, 20262.9 s
Sep 5, 20262.9 s
Sep 12, 20263.0 s
Sep 19, 20263.1 s
Sep 26, 20263.1 s
Oct 3, 20263.1 s
Oct 10, 20263.0 s
Oct 17, 20262.9 s
Oct 24, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
179 ms90 msMay 9Oct 24164 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026169 ms
May 16, 2026169 ms
May 23, 2026166 ms
May 30, 2026162 ms
Jun 6, 2026154 ms
Jun 13, 2026137 ms
Jun 20, 2026120 ms
Jun 27, 2026100 ms
Jul 4, 2026101 ms
Jul 11, 2026109 ms
Jul 18, 2026117 ms
Jul 25, 2026119 ms
Aug 1, 2026118 ms
Aug 8, 2026123 ms
Aug 15, 2026128 ms
Aug 22, 2026140 ms
Aug 29, 2026150 ms
Sep 5, 2026154 ms
Sep 12, 2026158 ms
Sep 19, 2026151 ms
Sep 26, 2026151 ms
Oct 3, 2026152 ms
Oct 10, 2026161 ms
Oct 17, 2026163 ms
Oct 24, 2026164 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 atlasvoyages.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. atlasvoyages.com at 0.5 s0.5 s
  2. atlasvoyages.com at 0.9 s0.9 s
  3. atlasvoyages.com at 1.4 s1.4 s
  4. atlasvoyages.com at 1.8 s1.8 s
  5. atlasvoyages.com at 2.3 s2.3 s
  6. atlasvoyages.com at 2.8 s2.8 s
  7. atlasvoyages.com at 3.2 s3.2 s
  8. atlasvoyages.com at 3.7 s3.7 s

Speed

5 to fix63
  • Use efficient cache lifetimes

    22.5 s · 12.0 MB

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

  • Improve image delivery

    12.7 s · 2.4 MB

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

  • Reduce unused JavaScript

    900 ms · 184 KiB

    About 184 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • Mobile performance score: 63

    63/100

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

  • Render-blocking requests

    600 ms

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Facebook, Google Tag Manager and JSDelivr CDN and others), adding 508 KiB and 294 ms of main-thread time.

  • 4 long tasks on the main thread

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

  • Legacy JavaScript

    13 KiB

    Polyfills for old browsers add 13 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.

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 0.7 s

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

  • Server response: 116 ms

    116 ms

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

Core Web Vitals

9 to fix67
  • 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: 33.9 s

    33.9 s

    Your largest element takes 33.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “MAISON DE VOYAGES SUR MESURE Des voyages signature depuis 1…”.

  • Time to Interactive: 34.6 s

    34.6 s

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

  • Speed Index: 6.1 s

    6.1 s

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

  • First Contentful Paint: 3.1 s

    3.1 s

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

  • Real-user LCP: 3.5 s

    3.5 s

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

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

    +37%

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

  • Real-user FCP: 2.9 s

    2.9 s

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

  • Real-user TTFB: 1.7 s

    1.7 s

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

  • Tap response (INP) held steady for real visitors

    -3%

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

4 checks passed
  • Real-user INP: 178 ms

    178 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Total Blocking Time: 111 ms

    111 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix18
  • Page weight: 12.3 MB in 49 requests

    12.3 MB

    Your homepage downloads 12.3 MB in 49 requests on a phone: images 7.0 MB (14), media 4.7 MB (1) and scripts 562 KiB (18). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 3.1 MB together. On a phone connection a single image that size takes seconds.

  • 5 images far larger than shown

    2.1 MB

    5 images are downloaded at several times the size a phone draws them, for example shutterstock_2157007419-1-scaled.jpg at 2,560 px wide, shown at 342 px. Resized copies would save about 2.1 MB.

  • 11 images in older formats

    11 images (3.9 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.

  • 10 images below the first screen load straight away

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

  • About 3.5 g of CO₂ per visit

    3.49 g

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

Accessibility

4 to fixGoogle 9492
  • 8 text elements with low contrast

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

  • No main landmark

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

1 checks passed
  • 33 automated accessibility rules passed

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

SEO

2 to fixGoogle 10093
  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://atlasvoyages.com/sitemap_index.xml, so Google discovers your pages only by following links.

  • 33 internal links, 4 external

    The homepage links to 33 pages on atlasvoyages.com and 4 external pages.

6 checks passed
  • Meta description: 137 characters

    Your meta description is 137 characters: “Depuis 1964, Atlas Voyages imagine des voyages sur mesure, circuits et séjours d’exception, accompagnés par nos conseil…”.

  • One H1 headline

    Your main headline reads: “Des voyages signaturedepuis 1964.”.

  • Title: 46 characters

    Your title is a healthy 46 characters: “Atlas Voyages | Voyages sur mesure depuis 1964”.

  • Canonical URL set

    The canonical URL is https://atlasvoyages.com/.

  • Structured data in place

    Structured data found: ImageObject, Organization, TravelAgency, WebPage and WebSite.

  • robots.txt in place

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

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing url, logo and sameAs (social profiles). These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

3 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 (488 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://atlasvoyages.com/llms.txt (1 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix70
  • 1 linked page is broken

    Your homepage links to https://atlasvoyages.com/privacy-policy, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 5 pages without an H1

    https://atlasvoyages.com/destinations-2, https://atlasvoyages.com/nos-agences, https://atlasvoyages.com/club-med, https://atlasvoyages.com/croisiere and https://atlasvoyages.com/conditions-generales-de-vente have no <h1> headline, so visitors and search engines get no clear main topic.

  • 13 internal pages checked

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

5 checks passed
  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 12 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 12 pages that loaded have a <title>.

Best practices

1 to fixGoogle 7393
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Mixed Content: The page at 'https://atlasvoyages.com/' was loaded over HTTPS, but requested an insecure font 'http://at…”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Mixed content”).

2 checks passed
  • Tap targets are thumb-sized

    13 of 14 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix57
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 462 words of copy

    The homepage carries about 462 words of visible text.

4 checks passed
  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

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.

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 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.

  • 8 other companies contacted

    Loading the homepage contacts 8 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 atlasvoyages.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
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
Hostinger

Company

Founded
2010
Headquarters
Casablanca

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on atlasvoyages.com, including 14 speed issues, 2 SEO 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