Website review, no card needed
thebocaraton.com website review
Visit site (opens in a new tab)Reviewed 2 November 202637 issues · 87 checks
This review found 37 issues worth fixing on thebocaraton.com, 14 of them high impact, across 87 checks. The most urgent: reduce unused JavaScript. 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
75CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 4.0 s |
| May 23, 2026 | 4.4 s |
| May 30, 2026 | 4.3 s |
| Jun 6, 2026 | 4.3 s |
| Jun 13, 2026 | 4.2 s |
| Jun 20, 2026 | 4.2 s |
| Jun 27, 2026 | 4.2 s |
| Jul 4, 2026 | 4.2 s |
| Jul 11, 2026 | 4.3 s |
| Jul 18, 2026 | 4.3 s |
| Jul 25, 2026 | 4.3 s |
| Aug 1, 2026 | 4.3 s |
| Aug 8, 2026 | 4.2 s |
| Aug 15, 2026 | 4.2 s |
| Aug 22, 2026 | 4.1 s |
| Aug 29, 2026 | 4.1 s |
| Sep 5, 2026 | 4.2 s |
| Sep 12, 2026 | 4.3 s |
| Sep 19, 2026 | 4.4 s |
| Sep 26, 2026 | 4.2 s |
| Oct 3, 2026 | 4.0 s |
| Oct 10, 2026 | 3.7 s |
| Oct 17, 2026 | 3.5 s |
| Oct 24, 2026 | 3.5 s |
| Oct 31, 2026 | 3.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 158 ms |
| May 23, 2026 | 155 ms |
| May 30, 2026 | 154 ms |
| Jun 6, 2026 | 154 ms |
| Jun 13, 2026 | 153 ms |
| Jun 20, 2026 | 150 ms |
| Jun 27, 2026 | 153 ms |
| Jul 4, 2026 | 154 ms |
| Jul 11, 2026 | 153 ms |
| Jul 18, 2026 | 155 ms |
| Jul 25, 2026 | 154 ms |
| Aug 1, 2026 | 155 ms |
| Aug 8, 2026 | 158 ms |
| Aug 15, 2026 | 157 ms |
| Aug 22, 2026 | 158 ms |
| Aug 29, 2026 | 156 ms |
| Sep 5, 2026 | 157 ms |
| Sep 12, 2026 | 162 ms |
| Sep 19, 2026 | 166 ms |
| Sep 26, 2026 | 168 ms |
| Oct 3, 2026 | 171 ms |
| Oct 10, 2026 | 171 ms |
| Oct 17, 2026 | 172 ms |
| Oct 24, 2026 | 176 ms |
| Oct 31, 2026 | 178 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.7 s
1.4 s
2.2 s
2.9 s
3.6 s
4.3 s
5.0 s
5.8 s
Speed
Reduce unused JavaScript
1.4 s · 1.0 MBAbout 1.0 MB 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: 40
40/100Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.3 s
A phone's processor spends 5.3 s on main-thread work while loading, 3.2 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, gethovr.com and VWO and others), adding 2.0 MB and 1.6 s of main-thread time.
Improve image delivery
150 ms · 1.3 MB19 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
789 KiB98 files are served with short cache lifetimes, so returning visitors download them again (789 KiB).
Google Tag Manager adds 665 ms
665 msGoogle Tag Manager costs a phone 665 ms of main-thread work and 816 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.
gethovr.com adds 284 ms
284 msgethovr.com costs a phone 284 ms of main-thread work and 660 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.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 206 ms. During a long task the page ignores taps.
Reduce unused CSS
59 KiBAbout 59 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
17 KiBPolyfills for old browsers add 17 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.
1 checks passed
Server response: 100 ms
100 msYour server sent the HTML in 100 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Real-user TTFB: 2.3 s
2.3 sReal visitors wait 2.3 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 25.3 s
25.3 sThe page becomes fully interactive after 25.3 s. Good is under 3.8 s.
Largest Contentful Paint: 7.8 s
7.8 sYour largest element takes 7.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Speed Index: 11.5 s
11.5 sVisually, the page fills in at 11.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 944 ms
944 msScripts block taps and scrolling for 944 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.0 s
3.0 sReal visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.6 s
2.6 sReal visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
11 images without width and height
11 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 158 ms to 178 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 180 ms
180 msReal visitors wait 180 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
Largest content (LCP) got 16% faster for real visitors
-16%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.0 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.022
0.022The layout barely moves while loading (CLS 0.022, good is under 0.1).
Images and page weight
Page weight: 16.2 MB in 226 requests
16.2 MBYour homepage downloads 16.2 MB in 226 requests on a phone: media 10.0 MB (4), images 3.0 MB (55) and scripts 2.4 MB (108). Under 2 MB keeps phones on slow connections fast.
15 images far larger than shown
1.4 MB15 images are downloaded at several times the size a phone draws them, for example suite-collection-main-new.webp at 2,400 px wide, shown at 390 px. Resized copies would save about 1.4 MB.
9 images in older formats
9 images (829 KiB) 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.
4 images below the first screen load straight away
4 images further down the page (325 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 4.6 g of CO₂ per visit
4.60 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.60 g of CO₂e: 552.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Scrollable region must have keyboard access (4 elements)
Scrollable region must have keyboard access: 4 elements on the page fail this check, rated serious by axe-core.
Elements must only use permitted ARIA attributes (2 elements)
Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
ARIA role should be appropriate for the element (5 elements)
ARIA role should be appropriate for the element: 5 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (6 elements).
2 checks passed
Every image has alt text
All 73 images in the HTML carry an alt attribute.
52 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: 52 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Structured data has 1 problem
Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON ("[object Object]" is not valid JSON)”.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
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.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
114 internal links, 11 external
The homepage links to 114 pages on thebocaraton.com and 11 external pages.
5 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “Discover The Boca Raton: five hotels within one luxury resort in the heart of Boca Raton. Captivating water views, grac…”.
One H1 headline
Your main headline reads: “A Century of Being Iconic A Century of Being Iconic”.
Title: 57 characters
Your title is a healthy 57 characters: “Resorts In Florida | The Boca Raton | A Boca Raton Resort”.
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.thebocaraton.com/sitemap_index.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.
No llms.txt
There is no https://www.thebocaraton.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.
2 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 (1,220 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://www.thebocaraton.com/experiences/programming has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.thebocaraton.com/experiences/programming has no <h1> headline, so visitors and search engines get no clear main topic.
7 pages slow to respond
https://www.thebocaraton.com/suites-rooms, https://www.thebocaraton.com/suites-rooms/beach-club, https://www.thebocaraton.com/suites-rooms/yacht-club, https://www.thebocaraton.com/suite-collection, https://www.thebocaraton.com/packages and https://www.thebocaraton.com/drink-dine and 1 other took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 49 found) and read each the way a search engine does.
5 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.
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
1 broken image
1 image failed to load on a phone, for example https://px.adentifi.com/Pixels?a_id=27856;p_url=https%3A%2F%2Fwww.thebocaraton.com%2F;uq=557780104703.5024.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
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”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
27 of 28 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
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.
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 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 752 words of copy
The homepage carries about 752 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “BOOK NOW”.
5 calls to action
The homepage has 5 calls to action, for example “Book Now”, “Learn More” and “Contact”.
Social proof on the page
Social proof on the homepage: 7 testimonial or review blocks, 6 customer or partner logos and 11 trust badges.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
4 trackers load before any consent
4Before 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 (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
22 cookies set on arrival
22Opening the homepage sets 22 cookies (measured from a US location before any click).
31 other companies contacted
Loading the homepage contacts 31 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 thebocaraton.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Nuxt
- Analytics
- Google Tag Manager
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on thebocaraton.com, including 18 speed issues, 4 SEO 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.