Website review, no card needed
atlantisbahamas.com website review
Visit site (opens in a new tab)Reviewed 26 October 202636 issues · 89 checks
This review found 36 issues worth fixing on atlantisbahamas.com, 19 of them high impact, across 89 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
76CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.3 s |
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.2 s |
| Aug 1, 2026 | 1.2 s |
| Aug 8, 2026 | 1.2 s |
| Aug 15, 2026 | 1.2 s |
| Aug 22, 2026 | 1.2 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 162 ms |
| May 16, 2026 | 162 ms |
| May 23, 2026 | 162 ms |
| May 30, 2026 | 162 ms |
| Jun 6, 2026 | 162 ms |
| Jun 13, 2026 | 162 ms |
| Jun 20, 2026 | 162 ms |
| Jun 27, 2026 | 161 ms |
| Jul 4, 2026 | 157 ms |
| Jul 11, 2026 | 154 ms |
| Jul 18, 2026 | 160 ms |
| Jul 25, 2026 | 161 ms |
| Aug 1, 2026 | 162 ms |
| Aug 8, 2026 | 169 ms |
| Aug 15, 2026 | 170 ms |
| Aug 22, 2026 | 172 ms |
| Aug 29, 2026 | 178 ms |
| Sep 5, 2026 | 179 ms |
| Sep 12, 2026 | 181 ms |
| Sep 19, 2026 | 180 ms |
| Sep 26, 2026 | 179 ms |
| Oct 3, 2026 | 177 ms |
| Oct 10, 2026 | 172 ms |
| Oct 17, 2026 | 171 ms |
| Oct 24, 2026 | 173 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
How it loaded on a phone
0.5 s
1.0 s
1.5 s
2.0 s
2.5 s
3.0 s
3.5 s
4.0 s
Speed
Improve image delivery
11.3 s · 2.1 MB6 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 11.3 s faster on a phone.
Reduce unused JavaScript
2.8 s · 647 KiBAbout 647 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.8 s faster on a phone.
Mobile performance score: 34
34/100Your mobile performance score is 34 (desktop: 43). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.4 s
A phone's processor spends 4.4 s on main-thread work while loading, 2.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Optanon and Monetate and others), adding 1.1 MB and 849 ms of main-thread time.
Google Tag Manager adds 720 ms
720 msGoogle Tag Manager costs a phone 720 ms of main-thread work and 646 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.
Use efficient cache lifetimes
450 ms · 148 KiB9 files are served with short cache lifetimes, so returning visitors download them again (148 KiB).
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 232 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
19 KiBAbout 19 KiB of CSS is downloaded but never applied on this page.
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.
1 checks passed
Server response: 31 ms
31 msYour server sent the HTML in 31 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 23.8 s
23.8 sYour largest element takes 23.8 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.8 s
23.8 sThe page becomes fully interactive after 23.8 s. Good is under 3.8 s.
First Contentful Paint: 5.7 s
5.7 sThe first text or image appears after 5.7 s on a phone. Good is under 1.8 s.
Speed Index: 9.1 s
9.1 sVisually, the page fills in at 9.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 162 ms to 173 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 173 ms
173 msReal visitors wait 173 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 541 ms
541 msReal visitors wait 541 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.4 MB in 136 requests
4.4 MBYour homepage downloads 4.4 MB in 136 requests on a phone: images 2.2 MB (15), scripts 1.6 MB (78) and HTML 233 KiB (1). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 1.3 MB together. On a phone connection a single image that size takes seconds.
5 images far larger than shown
1.1 MB5 images are downloaded at several times the size a phone draws them, for example coral-pool.jpg at 1,679 px wide, shown at 390 px. Resized copies would save about 1.1 MB.
1 image in older formats
1 image (97 KiB) is 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.
About 1.2 g of CO₂ per visit
1.24 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.24 g of CO₂e: 149.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
4 buttons without a name
4 buttons have no accessible name, so screen readers announce just “button”.
Images must have alternative text (3 elements)
Images must have alternative text: 3 elements on the page fail this check, rated critical by axe-core.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (17 elements)
All page content should be contained by landmarks: 17 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
6 form fields without a label
6 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
30 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 39 WCAG 2.2 A/AA and best-practice rules on the phone render: 30 passed and 9 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (76 characters)
Your title is 76 characters, so Google will cut it off around 60: “Atlantis Paradise Island Bahamas | Bahamas Vacation Resort | Luxury Resort |”.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
118 internal links, 7 external
The homepage links to 118 pages on atlantisbahamas.com and 7 external pages.
6 checks passed
Meta description: 155 characters
Your meta description is 155 characters: “Experience Atlantis Paradise Island resorts entertainment and adventures. See what activities and amenities this Bahama…”.
Canonical URL set
The canonical URL is https://www.atlantisbahamas.com/.
Structured data in place
Structured data found: Resort.
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.atlantisbahamas.com/sitemap.xml.
AI search readiness
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.
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 (469 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.atlantisbahamas.com/llms.txt (20 KiB, 54 links), a plain-text guide to the site for AI tools.
Other pages
5 pages without an H1
https://www.atlantisbahamas.com/events, https://www.atlantisbahamas.com/photo-gallery, https://www.atlantisbahamas.com/things-to-do/aquaventure-water-park, https://www.atlantisbahamas.com/meetings and https://www.atlantisbahamas.com/blog have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.atlantisbahamas.com/photo-gallery has 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 54 found) and read each the way a search engine does.
6 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.
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
4 broken images
4 images failed to load on a phone, for example https://t.teads.tv/track?action=pageView&env=js-web&tag_version=8.15.2_a4a3745&provider=tag&buyer_pixel_id=7114&referer=https%3A%2F%2Fwww.atlantisbahamas.com%2F&hasConsent=true&cht=timeout.
4 small tap targets
4 of 14 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
Only about 194 words
The homepage has only about 194 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Call Atlantis” and “BOOK NOW”.
12 calls to action
The homepage has 12 calls to action, for example “Book Activities”, “Call 1-800-285-2684” and “Book Now”.
Analytics in place
Analytics detected: Google Tag Manager and PostHog.
Direct contact links
Visitors can reach you directly: 4 phone links 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.
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
15 trackers load before any consent
15Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight and 10 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.
21 cookies set on arrival
21Opening the homepage sets 21 cookies (measured from a US location before any click).
75 other companies contacted
Loading the homepage contacts 75 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 atlantisbahamas.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- CloudFront
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on atlantisbahamas.com, including 12 speed issues, 4 SEO issues and 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.