Website review, no card needed

oceanhotels.com logo

oceanhotels.com website review

Visit site (opens in a new tab)Reviewed 30 October 202655 issues · 92 checks

This review found 55 issues worth fixing on oceanhotels.com, 23 of them high impact, across 92 checks. The most urgent: reduce unused JavaScript. 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
6.1 s4.5 sMay 9Oct 244.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.8 s
May 16, 20264.9 s
May 23, 20264.9 s
May 30, 20265.0 s
Jun 6, 20265.3 s
Jun 13, 20265.6 s
Jun 20, 20265.8 s
Jun 27, 20265.9 s
Jul 4, 20265.8 s
Jul 11, 20265.5 s
Jul 18, 20265.0 s
Jul 25, 20264.7 s
Aug 1, 20264.7 s
Aug 8, 20264.7 s
Aug 15, 20264.8 s
Aug 22, 20265.1 s
Aug 29, 20265.2 s
Sep 5, 20265.4 s
Sep 12, 20265.6 s
Sep 19, 20265.5 s
Sep 26, 20265.6 s
Oct 3, 20265.6 s
Oct 10, 20265.5 s
Oct 17, 20265.2 s
Oct 24, 20264.8 s
Real-visitor tap response (INP)75th percentile, phones
409 ms294 msMay 9Oct 24346 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026310 ms
May 16, 2026312 ms
May 23, 2026308 ms
May 30, 2026307 ms
Jun 6, 2026320 ms
Jun 13, 2026332 ms
Jun 20, 2026340 ms
Jun 27, 2026349 ms
Jul 4, 2026349 ms
Jul 11, 2026339 ms
Jul 18, 2026327 ms
Jul 25, 2026321 ms
Aug 1, 2026335 ms
Aug 8, 2026345 ms
Aug 15, 2026355 ms
Aug 22, 2026361 ms
Aug 29, 2026355 ms
Sep 5, 2026357 ms
Sep 12, 2026373 ms
Sep 19, 2026385 ms
Sep 26, 2026392 ms
Oct 3, 2026396 ms
Oct 10, 2026379 ms
Oct 17, 2026363 ms
Oct 24, 2026346 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 oceanhotels.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. oceanhotels.com at 1.2 s1.2 s
  2. oceanhotels.com at 2.4 s2.4 s
  3. oceanhotels.com at 3.6 s3.6 s
  4. oceanhotels.com at 4.8 s4.8 s
  5. oceanhotels.com at 6.0 s6.0 s
  6. oceanhotels.com at 7.2 s7.2 s
  7. oceanhotels.com at 8.3 s8.3 s
  8. oceanhotels.com at 9.5 s9.5 s

Speed

13 to fix21
  • Reduce unused JavaScript

    8.2 s · 1.6 MB

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

  • Use efficient cache lifetimes

    1.8 s · 450 KiB

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

  • Render-blocking requests

    1.4 s

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.4 s.

  • Mobile performance score: 21

    21/100

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

  • Main-thread work: 9.1 s

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

  • Improve image delivery

    4.1 MB

    27 images could be 4.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

    8 third-party services load with your homepage (opticksprotection.com, cookiepro.com and Impact Radius and others), adding 6.5 MB and 620 ms of main-thread time.

  • Reduce unused CSS

    900 ms · 222 KiB

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

  • h10hotels.com adds 36 ms

    36 ms

    h10hotels.com costs a phone 36 ms of main-thread work and 5.6 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.

  • 20 long tasks on the main thread

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

  • opticksprotection.com adds 383 ms

    383 ms

    opticksprotection.com costs a phone 383 ms of main-thread work and 34 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.

  • 1,819 HTML elements

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

  • cookiepro.com adds 88 ms

    88 ms

    cookiepro.com costs a phone 88 ms of main-thread work and 554 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.

  • Legacy JavaScript

    150 ms · 17 KiB

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

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

    10 ms

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

Core Web Vitals

13 to fix0
  • 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 LCP: 4.7 s

    4.7 s

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

  • Real-user FCP: 3.8 s

    3.8 s

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

  • Largest Contentful Paint: 38.0 s

    38.0 s

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

  • Speed Index: 17.6 s

    17.6 s

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

  • Time to Interactive: 40.4 s

    40.4 s

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

  • Total Blocking Time: 2.1 s

    2.1 s

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

  • Real-user INP: 220 ms

    220 ms

    Real visitors wait 220 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.21

    0.21

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

  • Real-user TTFB: 1.5 s

    1.5 s

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

  • Cumulative Layout Shift: 0.249

    0.249

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

  • First Contentful Paint: 2.6 s

    2.6 s

    The first text or image appears after 2.6 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 14% slower for real visitors

    +14%

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

Images and page weight

5 to fix18
  • Page weight: 10.3 MB in 155 requests

    10.3 MB

    Your homepage downloads 10.3 MB in 155 requests on a phone: images 5.6 MB (82), scripts 4.1 MB (28) and fonts 230 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 14 images far larger than shown

    2.2 MB

    14 images are downloaded at several times the size a phone draws them, for example ORP ssscampbell i chazwick512.jpg at 1,440 px wide, shown at 270 px. Resized copies would save about 2.2 MB.

  • 2 images over 500 KB

    2 images weigh 1.0 MB together. On a phone connection a single image that size takes seconds.

  • 20 images below the first screen load straight away

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

  • 1 image in older formats

    1 image (506 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 2.9 g of CO₂ per visit

    2.92 g

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

Accessibility

11 to fixGoogle 6885
  • Required ARIA attributes must be provided (4 elements)

    Required ARIA attributes must be provided: 4 elements on the page fail this check, rated critical by axe-core.

  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • 3 tap targets too small

    3 tap targets are too small or too close together to hit reliably with a finger.

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

  • 8 images without alt text

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

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

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • 11 links without text

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

  • 10 form fields without a label

    10 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

1 checks passed
  • 41 automated accessibility rules passed

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

SEO

4 to fixGoogle 7789
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

  • 15 links crawlers can't follow

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 56 internal links, 47 external

    The homepage links to 56 pages on oceanhotels.com and 47 external pages.

6 checks passed
  • Meta description: 139 characters

    Your meta description is 139 characters: “The best 5-star resorts in Riviera Maya, Punta Cana, and Jamaica. Book at the best guaranteed price on the Ocean Signat…”.

  • One H1 headline

    Your main headline reads: “BEYOND EVERYTHING”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “Ocean Signature Resorts | Book with the best Offers”.

  • Canonical URL set

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

  • 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.oceanhotels.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.oceanhotels.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,058 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix60
  • 1 linked page is broken

    Your homepage links to https://www.oceanhotels.com/it, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 1 linked page hidden from search

    https://www.oceanhotels.com/en/sustainability is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 3 pages share a title

    /, https://www.oceanhotels.com/en and https://www.oceanhotels.com/en;pageSec=exp all use the title “Ocean Signature Resorts | Book with the best Offers”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://www.oceanhotels.com/en and https://www.oceanhotels.com/en;pageSec=exp use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

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

4 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    17 of 17 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • About 616 words of copy

    The homepage carries about 616 words of visible text.

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Get a free call” and “Contact”.

  • 2 short forms

    2 short forms (7 fields at most) are right on the homepage.

  • 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

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Amazon Ads, Google Analytics and Google Tag Manager (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.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies (measured from a US location before any click).

  • 12 other companies contacted

    Loading the homepage contacts 12 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 oceanhotels.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
Angular
Hosting
Fastly

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 55 issues on oceanhotels.com, including 26 speed issues, 4 SEO issues and 3 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

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