Website review, no card needed

ocean-medical.com logo

ocean-medical.com website review

Visit site (opens in a new tab)Reviewed 29 October 202648 issues · 85 checks

This review found 48 issues worth fixing on ocean-medical.com, 23 of them high impact, across 85 checks. The most urgent: improve image delivery. 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
1.8 s1.1 sMay 9Oct 241.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.2 s
May 16, 20261.2 s
May 23, 20261.2 s
May 30, 20261.3 s
Jun 6, 20261.3 s
Jun 13, 20261.4 s
Jun 20, 20261.4 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.6 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.6 s
Sep 12, 20261.5 s
Sep 19, 20261.4 s
Sep 26, 20261.4 s
Oct 3, 20261.5 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Oct 24, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
211 ms130 msMay 9Oct 24202 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026144 ms
May 16, 2026139 ms
May 23, 2026142 ms
May 30, 2026151 ms
Jun 6, 2026171 ms
Jun 13, 2026192 ms
Jun 20, 2026182 ms
Jun 27, 2026183 ms
Jul 4, 2026169 ms
Jul 11, 2026176 ms
Jul 18, 2026184 ms
Aug 8, 2026173 ms
Aug 15, 2026167 ms
Aug 22, 2026169 ms
Aug 29, 2026167 ms
Sep 5, 2026170 ms
Sep 12, 2026172 ms
Sep 19, 2026175 ms
Sep 26, 2026182 ms
Oct 3, 2026192 ms
Oct 10, 2026194 ms
Oct 17, 2026197 ms
Oct 24, 2026202 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 ocean-medical.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ocean-medical.com at 1.6 s1.6 s
  2. ocean-medical.com at 3.3 s3.3 s
  3. ocean-medical.com at 4.9 s4.9 s
  4. ocean-medical.com at 6.5 s6.5 s
  5. ocean-medical.com at 8.2 s8.2 s
  6. ocean-medical.com at 9.8 s9.8 s
  7. ocean-medical.com at 11.4 s11.4 s
  8. ocean-medical.com at 13.1 s13.1 s

Speed

11 to fix12
  • Improve image delivery

    45.4 s · 9.1 MB

    19 images could be 9.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 45.4 s faster on a phone.

  • Reduce unused JavaScript

    17.1 s · 1.3 MB

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

  • Render-blocking requests

    5.2 s

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

  • Font display

    3.0 s

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

  • Google Tag Manager adds 1.2 s

    1.2 s

    Google Tag Manager costs a phone 1.2 s of main-thread work and 1.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 12

    12/100

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

  • Main-thread work: 4.8 s

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Google CDN and Other Google APIs/SDKs and others), adding 2.4 MB and 2.2 s of main-thread time.

  • Google CDN adds 938 ms

    938 ms

    Google CDN costs a phone 938 ms of main-thread work and 1.1 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.

  • Reduce unused CSS

    650 ms · 64 KiB

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

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    8 KiB

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

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

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

  • Use efficient cache lifetimes

    2 KiB

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

1 checks passed
  • Server response: 2 ms

    2 ms

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

Core Web Vitals

11 to fix50
  • 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 CLS: 0.71

    0.71

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

  • Largest Contentful Paint: 94.2 s

    94.2 s

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

  • Speed Index: 17.5 s

    17.5 s

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

  • Time to Interactive: 95.4 s

    95.4 s

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

  • Total Blocking Time: 1.9 s

    1.9 s

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

  • Cumulative Layout Shift: 0.578

    0.578

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

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

    +41%

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

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

    +20%

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

  • First Contentful Paint: 2.5 s

    2.5 s

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

  • 28 images without width and height

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

3 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 568 ms

    568 ms

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

Images and page weight

5 to fix18
  • Page weight: 18.1 MB in 125 requests

    18.1 MB

    Your homepage downloads 18.1 MB in 125 requests on a phone: images 14.7 MB (72), scripts 2.4 MB (20) and fonts 458 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 6.4 MB together. On a phone connection a single image that size takes seconds.

  • 8 images far larger than shown

    5.1 MB

    8 images are downloaded at several times the size a phone draws them, for example FD512527-0FF60_1.jpg at 4,741 px wide, shown at 360 px. Resized copies would save about 5.1 MB.

  • 24 images in older formats

    24 images (8.3 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.

  • 11 images below the first screen load straight away

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

  • About 5.1 g of CO₂ per visit

    5.12 g

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

Accessibility

5 to fixGoogle 8893
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • 98 text elements with low contrast

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

  • 4 tap targets too small

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

  • All page content should be contained by landmarks (5 elements)

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

  • 7 form fields without a label

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

2 checks passed
  • Every image has alt text

    All 57 images in the HTML carry an alt attribute.

  • 48 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: 48 passed and 4 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 10081
  • Title is long (154 characters)

    Your title is 154 characters, so Google will cut it off around 60: “Ocean Medical - Formação certificada em Suporte Básico de Vida (SBV), Suporte Avançado de…”.

  • No structured data

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

  • Meta description is long (241 characters)

    Your meta description is 241 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

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

  • 51 internal links, 21 external

    The homepage links to 51 pages on ocean-medical.com and 21 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Bem-vindo à Ocean Medical,”.

  • Canonical URL set

    The canonical URL is https://ocean-medical.com/pt/home.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://ocean-medical.com/sitemap.xml.

AI search readiness

2 to fix75
  • 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.

  • Some text only appears after JavaScript runs

    31%

    The HTML your server sends has 495 of the 1,607 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • No llms.txt

    There is no https://ocean-medical.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.

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

Other pages

3 to fix86
  • 8 pages share a title

    https://ocean-medical.com/pt/home, https://ocean-medical.com/pt/formacoes, https://ocean-medical.com/pt/empresas, https://ocean-medical.com/pt/voucher-oferta, https://ocean-medical.com/pt/adiar-cancelar and https://ocean-medical.com/pt/certificados and 2 others all use the title “Ocean Medical - Formação certificada em Suporte Básico de Vida (SBV),…”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages share a meta description

    https://ocean-medical.com/pt/formacoes, https://ocean-medical.com/pt/empresas, https://ocean-medical.com/pt/voucher-oferta, https://ocean-medical.com/pt/adiar-cancelar, https://ocean-medical.com/pt/certificados and https://ocean-medical.com/pt/mapa-formacoes-hoje and 1 other use the same meta description. A description written for each page earns more clicks.

  • 5 pages without an H1

    https://ocean-medical.com/pt/formacoes, https://ocean-medical.com/pt/empresas, https://ocean-medical.com/pt/adiar-cancelar, https://ocean-medical.com/pt/certificados and https://ocean-medical.com/pt/mapa-formacoes-hoje have no <h1> headline, so visitors and search engines get no clear main topic.

  • 10 pages with very little text

    https://ocean-medical.com/pt/formacoes, https://ocean-medical.com/pt/empresas, https://ocean-medical.com/pt/certificados, https://ocean-medical.com/pt/mapa-formacoes-hoje, https://ocean-medical.com/pt/politica-descontos and https://ocean-medical.com/pt/noticia/526/nova-formacao-em-ocean-medical-porto-no-distrito-do-porto and 4 others have 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.

  • 8 pages slow to respond

    https://ocean-medical.com/pt/voucher-oferta, https://ocean-medical.com/pt/adiar-cancelar, https://ocean-medical.com/pt/certificados, https://ocean-medical.com/pt/mapa-formacoes-hoje, https://ocean-medical.com/pt/politica-descontos and https://ocean-medical.com/pt/noticia/524/nova-formacao-em-ocean-medical-lisboa-no-distrito-de-lisboa and 2 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

  • Every page has a meta description

    All 12 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 12 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9671
  • 10 broken images

    10 images failed to load on a phone, for example https://ocean-medical.com/pt/home.

  • 23 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “gtag is not defined”.

1 checks passed
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • Thin social proof

    Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 1,607 words of copy

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

3 checks passed
  • 1 short form

    A short form (5 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 4 cookies set on arrival

    4

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

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 11 other companies contacted

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

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 ocean-medical.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Analytics | Google Tag Manager
Hosting
Hetzner

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 48 issues on ocean-medical.com, including 22 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