Website review, no card needed

laubergedelmar.com logo

laubergedelmar.com website review

Visit site (opens in a new tab)Reviewed 18 October 202628 issues · 89 checks

This review found 28 issues worth fixing on laubergedelmar.com, 7 of them high impact, across 89 checks. The most urgent: fails Core Web Vitals for real visitors. 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.4 s1.4 sApr 25Oct 102.3 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20261.6 s
May 2, 20261.7 s
May 9, 20261.7 s
May 16, 20261.7 s
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.5 s
Jul 4, 20261.5 s
Jul 11, 20261.5 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.8 s
Oct 3, 20262.1 s
Oct 10, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
203 ms148 msApr 25Oct 10197 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026161 ms
May 2, 2026179 ms
May 9, 2026188 ms
May 16, 2026184 ms
May 23, 2026179 ms
May 30, 2026172 ms
Jun 6, 2026166 ms
Jun 13, 2026162 ms
Jun 20, 2026163 ms
Jun 27, 2026154 ms
Jul 4, 2026162 ms
Jul 11, 2026167 ms
Jul 18, 2026167 ms
Jul 25, 2026164 ms
Aug 1, 2026163 ms
Aug 8, 2026161 ms
Aug 15, 2026162 ms
Aug 22, 2026165 ms
Aug 29, 2026162 ms
Sep 5, 2026166 ms
Sep 12, 2026159 ms
Sep 19, 2026162 ms
Sep 26, 2026179 ms
Oct 3, 2026186 ms
Oct 10, 2026197 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 laubergedelmar.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. laubergedelmar.com at 0.6 s0.6 s
  2. laubergedelmar.com at 1.1 s1.1 s
  3. laubergedelmar.com at 1.7 s1.7 s
  4. laubergedelmar.com at 2.2 s2.2 s
  5. laubergedelmar.com at 2.8 s2.8 s
  6. laubergedelmar.com at 3.3 s3.3 s
  7. laubergedelmar.com at 3.9 s3.9 s
  8. laubergedelmar.com at 4.4 s4.4 s

Speed

6 to fix66
  • Mobile performance score: 66

    66/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (OptiMonk, chatbot.com and Clarity and others), adding 1.2 MB and 380 ms of main-thread time.

  • Reduce unused JavaScript

    338 KiB

    About 338 KiB of JavaScript is downloaded but never used on this page.

  • 2,718 HTML elements

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

  • Main-thread work: 2.5 s

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

  • nitrocdn.com adds 0 ms

    0 ms

    nitrocdn.com costs a phone 0 ms of main-thread work and 651 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.

  • Reduce unused CSS

    160 KiB

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

  • 11 long tasks on the main thread

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

  • Use efficient cache lifetimes

    150 KiB

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

  • Legacy JavaScript

    21 KiB

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

  • Duplicated JavaScript

    17 KiB

    17 KiB JavaScript is shipped twice across bundles.

  • 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: 9 ms

    9 ms

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

Core Web Vitals

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

  • Time to Interactive: 11.6 s

    11.6 s

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

  • Cumulative Layout Shift: 0.345

    0.345

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

  • Real-user LCP: 2.8 s

    2.8 s

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

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

    +31%

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

  • Largest Contentful Paint: 3.5 s

    3.5 s

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

  • Total Blocking Time: 330 ms

    330 ms

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

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

    +13%

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

6 checks passed
  • Real-user INP: 171 ms

    171 ms

    Real visitors wait 171 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.

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 770 ms

    770 ms

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

  • Speed Index: 2.8 s

    2.8 s

    Visually, the page fills in at 2.8 s (Speed Index), inside the 3.4 s “good” threshold.

  • 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

1 to fix85
  • Page weight: 2.4 MB in 105 requests

    2.4 MB

    Your homepage downloads 2.4 MB in 105 requests on a phone: other files 853 KiB (59), scripts 804 KiB (23) and images 318 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • About 0.7 g of CO₂ per visit

    0.67 g

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

3 checks passed
  • 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

12 to fixGoogle 8687
  • ARIA dialog and alertdialog nodes should have an accessible name (2 elements)

    ARIA dialog and alertdialog nodes should have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

  • 2 text elements with low contrast

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

  • ARIA commands must have an accessible name (1 element)

    ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Main landmark should not be contained in another landmark (1 element)

    Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one main landmark (1 element)

    Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 links without text

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

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (12 elements).

2 checks passed
  • Every image has alt text

    All 43 images in the HTML carry an alt attribute.

  • 43 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: 43 passed and 13 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
  • 134 internal links, 61 external

    The homepage links to 134 pages on laubergedelmar.com and 61 external pages.

8 checks passed
  • Meta description: 148 characters

    Your meta description is 148 characters: “OFFICIAL SITE - BEST RATE GUARANTEED - FLEXIBLE CANCELLATION - Beachside luxury spa resort perfect for your next getawa…”.

  • One H1 headline

    Your main headline reads: “Your home by the sea.”.

  • Title: 47 characters

    Your title is a healthy 47 characters: “L'Auberge Del Mar - San Diego, CA Luxury Resort”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, Resort and WebPage.

  • 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.laubergedelmar.com/sitemap_index.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: 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,288 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.laubergedelmar.com/llms.txt (52 KiB, 0 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 46 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

1 to fixGoogle 10093
  • 46 small tap targets

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix89
  • 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 form on the homepage

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

  • About 604 words of copy

    The homepage carries about 604 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 NOW” and “Noble House Shop”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Contact & Directions”, “Contact” and “BOOK NOW”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 4 trackers load before any consent

    4

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

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 cookies, 1 of them by other companies (measured from a US location before any click).

  • 23 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) 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 laubergedelmar.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on laubergedelmar.com, including 13 speed issues and 1 conversion gap. 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