Website review, no card needed

ssamarine.mx logo

ssamarine.mx website review

Visit site (opens in a new tab)Reviewed 1 November 202648 issues · 82 checks

This review found 48 issues worth fixing on ssamarine.mx, 24 of them high impact, across 82 checks. The most urgent: use efficient cache lifetimes. 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
19.4 s4.7 sMay 9Oct 247.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20267.7 s
May 16, 20268.4 s
May 23, 20266.5 s
May 30, 20266.4 s
Jun 6, 20267.1 s
Jun 13, 20267.5 s
Jun 20, 20269.4 s
Jun 27, 202615.0 s
Jul 4, 202615.2 s
Jul 11, 202615.0 s
Jul 18, 202612.1 s
Jul 25, 20268.6 s
Aug 1, 202610.1 s
Aug 8, 202613.8 s
Aug 15, 202614.5 s
Aug 22, 202616.3 s
Aug 29, 202617.1 s
Sep 5, 202617.7 s
Sep 12, 202616.9 s
Sep 19, 202617.2 s
Sep 26, 202616.2 s
Oct 3, 202616.1 s
Oct 10, 202616.0 s
Oct 17, 202610.5 s
Oct 24, 20267.3 s
Real-visitor tap response (INP)75th percentile, phones
242 ms87 msMay 9Oct 24224 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026115 ms
May 16, 2026112 ms
May 23, 2026111 ms
May 30, 2026113 ms
Jun 6, 2026113 ms
Jun 13, 2026113 ms
Jun 20, 2026113 ms
Jun 27, 2026108 ms
Jul 4, 2026105 ms
Jul 11, 2026107 ms
Jul 18, 2026108 ms
Jul 25, 2026113 ms
Aug 1, 2026113 ms
Aug 8, 2026112 ms
Aug 15, 2026113 ms
Aug 22, 2026115 ms
Aug 29, 2026122 ms
Sep 5, 2026132 ms
Sep 12, 2026143 ms
Sep 19, 2026149 ms
Sep 26, 2026158 ms
Oct 3, 2026161 ms
Oct 10, 2026171 ms
Oct 17, 2026202 ms
Oct 24, 2026224 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 ssamarine.mx (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ssamarine.mx at 1.3 s1.3 s
  2. ssamarine.mx at 2.5 s2.5 s
  3. ssamarine.mx at 3.8 s3.8 s
  4. ssamarine.mx at 5.0 s5.0 s
  5. ssamarine.mx at 6.3 s6.3 s
  6. ssamarine.mx at 7.5 s7.5 s
  7. ssamarine.mx at 8.8 s8.8 s
  8. ssamarine.mx at 10.0 s10.0 s

Speed

9 to fix55
  • Use efficient cache lifetimes

    46.4 s · 18.3 MB

    34 files are served with short cache lifetimes, so returning visitors download them again (18.3 MB).

  • Improve image delivery

    41.1 s · 14.1 MB

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

  • Document request latency

    5.0 s

    The HTML itself could arrive about 5.0 s sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce initial server response time

    5.0 s

    Reduce initial server response time. Google estimates savings of 5.0 s on a phone.

  • Render-blocking requests

    1.3 s

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

  • Main-thread work: 7.3 s

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

  • Server response: 5.1 s

    5.1 s

    Your server takes 5.1 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Mobile performance score: 55

    55/100

    Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.

  • Font display

    600 ms

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

  • Reduce unused CSS

    220 ms · 36 KiB

    About 36 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 220 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.

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

  • 1 third-party service on the page

    1 third-party service load with your homepage (Google Fonts), adding 1 KiB and 0 ms of main-thread time.

Core Web Vitals

9 to fix67
  • 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: 8.3 s

    8.3 s

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

  • Real-user FCP: 3.2 s

    3.2 s

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

  • First Contentful Paint: 24.0 s

    24.0 s

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

  • Largest Contentful Paint: 87.4 s

    87.4 s

    Your largest element takes 87.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “PUERTO COZUMEL Su privilegiada ubicación dentro del Caribe …”.

  • Speed Index: 26.8 s

    26.8 s

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

  • Time to Interactive: 89.0 s

    89.0 s

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

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

    +88%

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

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

    +11%

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

4 checks passed
  • Real-user INP: 156 ms

    156 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

5 to fix18
  • Page weight: 22.7 MB in 49 requests

    22.7 MB

    Your homepage downloads 22.7 MB in 49 requests on a phone: images 18.2 MB (24), HTML 4.2 MB (1) and fonts 155 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 10 images far larger than shown

    3.8 MB

    10 images are downloaded at several times the size a phone draws them, for example Instagram.png at 7,813 px wide, shown at 25 px. Resized copies would save about 3.8 MB.

  • 5 images over 500 KB

    5 images weigh 2.8 MB together. On a phone connection a single image that size takes seconds.

  • 10 images in older formats

    10 images (3.8 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.

  • 3 images below the first screen load straight away

    3 images further down the page (384 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 6.4 g of CO₂ per visit

    6.44 g

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

Accessibility

6 to fixGoogle 7990
  • Links must have discernible text (6 elements)

    Links must have discernible text: 6 elements on the page fail this check, rated serious by axe-core.

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

  • 12 images without alt text

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

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

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

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • Page language is “zxx”

    The page declares lang=“zxx”, which is not a usable language code (“zxx” means “no linguistic content”), so screen readers and translation tools guess.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Headings skip levels

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

1 checks passed
  • 38 automated accessibility rules passed

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

SEO

8 to fixGoogle 8259
  • No meta description

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

  • Title is short (17 characters)

    Your title is only 17 characters: “SSA Marine México”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • 7 H1 headlines

    There are 7 <h1> headlines (“Puerto COZUMEL”, “Puerto LÁZARO CÁRDENAS” and “Puerto MANZANILLO”). One clear main headline is easier for people and search engines.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

  • No XML sitemap

    No XML sitemap at https://www.ssamarine.mx/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at ssamarine.mx/robots.txt, the first file search crawlers ask for.

  • No X (Twitter) card tag

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

  • 21 internal links, 12 external

    The homepage links to 21 pages on ssamarine.mx and 12 external pages.

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.ssamarine.mx/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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (592 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 7 pages share 3 titles

    https://www.ssamarine.mx/manzanillo.html, https://www.ssamarine.mx/manzanillo2.html and https://www.ssamarine.mx/manzanillo3.html all use the title “SSA Marine México MANZANILLO”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 14 pages without a meta description

    https://www.ssamarine.mx/about.html, https://www.ssamarine.mx/cozumel.html, https://www.ssamarine.mx/lazaro-cardenas.html, https://www.ssamarine.mx/manzanillo.html, https://www.ssamarine.mx/manzanillo2.html and https://www.ssamarine.mx/manzanillo3.html and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 13 pages without an H1

    https://www.ssamarine.mx/about.html, https://www.ssamarine.mx/cozumel.html, https://www.ssamarine.mx/lazaro-cardenas.html, https://www.ssamarine.mx/manzanillo.html, https://www.ssamarine.mx/manzanillo2.html and https://www.ssamarine.mx/manzanillo3.html and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://www.ssamarine.mx/noticias.aspx, https://www.ssamarine.mx/Contact.aspx and https://www.ssamarine.mx/vernoticia.aspx 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.

  • 14 internal pages checked

    We fetched 14 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 14 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 8891
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Loading the stylesheet 'https://fonts.googleapis.com/css2?family=Kanit:wght@200;500;600;700&display=swap' violates the …”.

  • 5 distorted images

    5 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix20
  • 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.

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • 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 365 words of copy

    The homepage carries about 365 words of visible text.

Privacy and tracking

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

  • 1 other company contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Upkeep, stack and company

Stack

Hosting
Internacional, S.A. de C.V.

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 ssamarine.mx, including 18 speed issues, 8 SEO issues and 5 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