Website review, no card needed

grandvelas.com logo

grandvelas.com website review

Visit site (opens in a new tab)Reviewed 18 November 202628 issues · 88 checks

This review found 28 issues worth fixing on grandvelas.com, 6 of them high impact, across 88 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
1.4 s587 msMay 30Nov 14895 ms
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.1 s
Jun 6, 20261.1 s
Jun 13, 20261.2 s
Jun 20, 20261.3 s
Jun 27, 20261.3 s
Jul 4, 20261.3 s
Jul 11, 20261.2 s
Jul 18, 20261.1 s
Jul 25, 20261.1 s
Aug 1, 2026693 ms
Aug 8, 2026675 ms
Aug 15, 2026677 ms
Aug 22, 2026681 ms
Aug 29, 2026859 ms
Sep 5, 20261.2 s
Sep 12, 20261.2 s
Sep 19, 20261.1 s
Sep 26, 20261.1 s
Oct 3, 20261.0 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Oct 24, 20261.0 s
Oct 31, 20261.0 s
Nov 7, 2026929 ms
Nov 14, 2026895 ms
Real-visitor tap response (INP)75th percentile, phones
133 ms100 msMay 30Nov 14120 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026104 ms
Jun 6, 2026106 ms
Jun 13, 2026111 ms
Jun 20, 2026109 ms
Jun 27, 2026112 ms
Jul 4, 2026108 ms
Jul 11, 2026104 ms
Jul 18, 2026107 ms
Jul 25, 2026105 ms
Aug 1, 2026112 ms
Aug 8, 2026114 ms
Aug 15, 2026114 ms
Aug 22, 2026115 ms
Aug 29, 2026122 ms
Sep 5, 2026124 ms
Sep 12, 2026129 ms
Sep 19, 2026124 ms
Sep 26, 2026124 ms
Oct 3, 2026115 ms
Oct 10, 2026113 ms
Oct 17, 2026120 ms
Oct 24, 2026120 ms
Oct 31, 2026124 ms
Nov 7, 2026120 ms
Nov 14, 2026120 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 grandvelas.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. grandvelas.com at 0.4 s0.4 s
  2. grandvelas.com at 0.9 s0.9 s
  3. grandvelas.com at 1.3 s1.3 s
  4. grandvelas.com at 1.8 s1.8 s
  5. grandvelas.com at 2.2 s2.2 s
  6. grandvelas.com at 2.6 s2.6 s
  7. grandvelas.com at 3.1 s3.1 s
  8. grandvelas.com at 3.5 s3.5 s

Speed

8 to fix68
  • Use efficient cache lifetimes

    1.8 s · 778 KiB

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

  • Reduce unused JavaScript

    1.4 s · 393 KiB

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

  • Mobile performance score: 68

    68/100

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

  • Improve image delivery

    500 ms · 480 KiB

    6 images could be 480 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

  • Render-blocking requests

    750 ms

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

  • Google Tag Manager adds 361 ms

    361 ms

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

  • Minify JavaScript

    300 ms · 59 KiB

    59 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    300 ms · 58 KiB

    About 58 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Airship and FontAwesome CDN and others), adding 412 KiB and 391 ms of main-thread time.

  • 4 long tasks on the main thread

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Legacy JavaScript

    9 KiB

    Polyfills for old browsers add 9 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.2 s

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 9.1 s

    9.1 s

    Your largest element takes 9.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Black Friday + Cyber Monday”.

  • Time to Interactive: 9.1 s

    9.1 s

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

  • Speed Index: 4.2 s

    4.2 s

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

  • First Contentful Paint: 1.9 s

    1.9 s

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

  • Total Blocking Time: 225 ms

    225 ms

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

  • 1 image without width and height

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

  • Tap response (INP) got 14% slower for real visitors

    +14%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 0.9 s

    0.9 s

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

  • Real-user INP: 116 ms

    116 ms

    Real visitors wait 116 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 FCP: 0.8 s

    0.8 s

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

  • Real-user TTFB: 370 ms

    370 ms

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

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

    -17%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.1 s to 0.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).

Images and page weight

100
  • About 0.4 g of CO₂ per visit

    0.41 g

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

4 checks passed
  • Page weight: 1.5 MB in 36 requests

    1.5 MB

    Your homepage downloads 1.5 MB in 36 requests on a phone: images 725 KiB (15), scripts 620 KiB (10) and stylesheets 75 KiB (2). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 9393
  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

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

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 6 links without text

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

  • ARIA role should be appropriate for the element (2 elements)

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

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

  • Elements marked as presentational should be consistently ignored (1 element)

    Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 47 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

3 to fixGoogle 8591
  • Meta description is long (196 characters)

    Your meta description is 196 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 4 links crawlers can't follow

    4 links have no real href, so search engines can't follow them.

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 53 internal links, 19 external

    The homepage links to 53 pages on grandvelas.com and 19 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “All-Inclusive Luxury Vacations”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “All-Inclusive Mexico Luxury Resorts - Velas Resorts”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: FAQPage, LodgingBusiness, WebPage and WebSite.

  • 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.grandvelas.com/image_sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.grandvelas.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.

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.

  • Organization data: 6 of 6 facts

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

  • Text is in the HTML

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

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 34 found) and read each the way a search engine does.

7 checks passed
  • Linked pages load

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

  • Titles are unique

    Every page we checked has its own title.

  • 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 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://resources.velasresorts.com/images/cintillos/VR%20Y%20GV/forbes_gvlc-en.png.

  • 8 small tap targets

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

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • No opening hours

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

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

    The homepage carries about 743 words of visible text.

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “BOOK YOUR STAY”.

  • 13 calls to action

    The homepage has 13 calls to action, for example “Book Your Stay”, “Contact” and “Learn More - Grand Velas Los Cabos”.

  • 3 short forms

    3 short forms (5 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: a star rating and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 4 phone links and 2 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.

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

  • 16 other companies contacted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on grandvelas.com, including 14 speed issues and 3 SEO issues. 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