alysbeach.com website review

About 2.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 10.5 s faster on a phone.

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

19 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Google CDN and others), adding 18.3 MB and 2.5 s of main-thread time.

Vimeo costs a phone 253 ms of main-thread work and 14.9 MB 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.

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

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

Google CDN costs a phone 448 ms of main-thread work and 733 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 costs a phone 458 ms of main-thread work and 412 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.

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

Polyfills for old browsers add 45 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.

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

pages.dev costs a phone 150 ms of main-thread work and 990 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.

3 KiB could be saved by minifying CSS.

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

6 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

Your largest element takes 77.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This is Alys Beach, a luxury beachfront community on Florid…”.

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

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

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

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

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

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

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

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

Your homepage downloads 30.9 MB in 261 requests on a phone: other files 22.7 MB (81), scripts 4.6 MB (81) and images 2.3 MB (48). Under 2 MB keeps phones on slow connections fast.

12 images are downloaded at several times the size a phone draws them, for example 22_fall_Alys.jpg at 1,080 px wide, shown at 251 px. Resized copies would save about 877 KiB.

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

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

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

5 frames have no title, so screen-reader users cannot tell what they contain.

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

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

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Elements with visible text labels do not have matching accessible names. (1 element).

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 17 characters: “Home – Alys Beach”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

1 link has no real href, so search engines can't follow it.

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 81 pages on alysbeach.com and 19 external pages.

/amenities/the-silva is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/live, /stay, /merchants, /the-town, /events and /interactive-map and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

/interactive-map has no <h1> headline, so visitors and search engines get no clear main topic.

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

2 images failed to load on a phone, for example https://cartstack-dialogs.s3.us-west-2.amazonaws.com/nudges/icons/Nudges_Icons-01.svg.

3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

6 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'children')”.

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

1 link from your homepage to your own site is broken, for example https://alysbeach.com/cdn-cgi/l/email-protection (404).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

2 links go through two or more redirects, for example https://alysinsider.alysbeach.com/51Ud.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

alysbeach.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

alysbeach.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Your longest form asks for 8 fields (1 required). Every extra field lowers completion.

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

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

DMARC is set to p=none, so mail pretending to be alysbeach.com is still delivered. Add a report address, check the reports, then move to quarantine.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

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

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