Website review, no card needed

catalinaop.com logo

catalinaop.com website review

Visit site (opens in a new tab)Reviewed 22 November 202644 issues · 97 checks

This review found 44 issues worth fixing on catalinaop.com, 18 of them high impact, across 97 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
2.1 s1.6 sMay 30Nov 141.9 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.7 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20262.0 s
Oct 10, 20262.0 s
Oct 17, 20261.9 s
Oct 24, 20262.0 s
Oct 31, 20262.0 s
Nov 7, 20262.0 s
Nov 14, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
71 ms61 msMay 30Nov 1465 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202666 ms
Jun 6, 202667 ms
Jun 13, 202667 ms
Jun 20, 202664 ms
Jun 27, 202664 ms
Jul 4, 202665 ms
Jul 11, 202669 ms
Jul 18, 202670 ms
Jul 25, 202670 ms
Aug 1, 202670 ms
Aug 8, 202670 ms
Aug 15, 202669 ms
Aug 22, 202667 ms
Aug 29, 202670 ms
Sep 5, 202666 ms
Sep 12, 202669 ms
Sep 19, 202670 ms
Sep 26, 202669 ms
Oct 3, 202669 ms
Oct 10, 202666 ms
Oct 17, 202663 ms
Oct 24, 202662 ms
Oct 31, 202664 ms
Nov 7, 202665 ms
Nov 14, 202665 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 catalinaop.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. catalinaop.com at 0.8 s0.8 s
  2. catalinaop.com at 1.7 s1.7 s
  3. catalinaop.com at 2.5 s2.5 s
  4. catalinaop.com at 3.3 s3.3 s
  5. catalinaop.com at 4.1 s4.1 s
  6. catalinaop.com at 5.0 s5.0 s
  7. catalinaop.com at 5.8 s5.8 s
  8. catalinaop.com at 6.6 s6.6 s

Speed

10 to fix56
  • Use efficient cache lifetimes

    5.5 s · 2.2 MB

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

  • Improve image delivery

    4.8 s · 2.1 MB

    29 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 4.8 s faster on a phone.

  • Reduce unused JavaScript

    2.5 s · 1.2 MB

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

  • Render-blocking requests

    1.2 s

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

  • Main-thread work: 4.0 s

    A phone's processor spends 4.0 s on main-thread work while loading, 1.8 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 CDN, YouTube and Google Tag Manager and others), adding 2.7 MB and 1.1 s of main-thread time.

  • Mobile performance score: 56

    56/100

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

  • Reduce unused CSS

    750 ms · 185 KiB

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

  • Google CDN adds 474 ms

    474 ms

    Google CDN costs a phone 474 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.

  • YouTube adds 385 ms

    385 ms

    YouTube costs a phone 385 ms of main-thread work and 1,003 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.

  • Minify JavaScript

    130 ms · 5 KiB

    5 KiB could be saved by minifying JavaScript.

  • 14 long tasks on the main thread

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

  • Legacy JavaScript

    31 KiB

    Polyfills for old browsers add 31 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 199 ms

    199 ms

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

Core Web Vitals

8 to fix100
  • 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.

  • Largest Contentful Paint: 15.9 s

    15.9 s

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

  • Time to Interactive: 25.4 s

    25.4 s

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

  • Speed Index: 12.1 s

    12.1 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • Total Blocking Time: 235 ms

    235 ms

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

  • 9 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -2%

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

  • Largest content (LCP) held steady for real visitors

    +9%

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

5 checks passed
  • Real-user LCP: 1.7 s

    1.7 s

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

  • Real-user INP: 68 ms

    68 ms

    Real visitors wait 68 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.

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix25
  • Page weight: 6.3 MB in 177 requests

    6.3 MB

    Your homepage downloads 6.3 MB in 177 requests on a phone: images 2.7 MB (81), scripts 2.3 MB (41) and fonts 488 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    hero-bg.png weighs 1.0 MB. On a phone connection a single image that size takes seconds.

  • 10 images far larger than shown

    1.4 MB

    10 images are downloaded at several times the size a phone draws them, for example hero-bg.png at 1,920 px wide, shown at 390 px. Resized copies would save about 1.4 MB.

  • 15 images in older formats

    15 images (2.1 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.

  • 4 images below the first screen load straight away

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

  • About 1.8 g of CO₂ per visit

    1.79 g

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

Accessibility

9 to fixGoogle 8089
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 9 text elements with low contrast

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

  • 9 tap targets too small

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

  • Hidden but focusable

    2 elements hidden from screen readers can still receive keyboard focus.

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

    All page content should be contained by landmarks: 27 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.

  • 11 links without text

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

  • Alternative text of images should not be repeated as text (12 elements)

    Alternative text of images should not be repeated as text: 12 elements on the page fail this check, rated minor by axe-core.

  • 2 form fields without a label

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 135 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 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

4 to fixGoogle 9276
  • No meta description

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

  • Title is short (26 characters)

    Your title is only 26 characters: “Catalina Offshore Products”. 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.

  • 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 X (Twitter) card tag

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

  • 95 internal links, 7 external

    The homepage links to 95 pages on catalinaop.com and 7 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Fresh & Premium Fish”.

  • Canonical URL set

    The canonical URL is https://catalinaop.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://catalinaop.com/wp-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://catalinaop.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.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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 (834 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 15 pages share a title

    /, https://catalinaop.com/order-tracking, https://catalinaop.com/product-category/all-seafood, https://catalinaop.com/product-category/tuna, https://catalinaop.com/product-category/salmon and https://catalinaop.com/product-category/bluefin and 9 others all use the title “Catalina Offshore Products”. 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://catalinaop.com/order-tracking, https://catalinaop.com/product-category/all-seafood, https://catalinaop.com/product-category/tuna, https://catalinaop.com/product-category/salmon, https://catalinaop.com/product-category/bluefin and https://catalinaop.com/product-category/shellfish and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 14 pages slow to respond

    https://catalinaop.com/order-tracking, https://catalinaop.com/product-category/all-seafood, https://catalinaop.com/product-category/tuna, https://catalinaop.com/product-category/salmon, https://catalinaop.com/product-category/bluefin and https://catalinaop.com/product-category/shellfish and 8 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 41 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

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

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

3 to fixGoogle 4692
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 9 distorted images

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

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

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

    The homepage carries about 702 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Order tracking”, “Contact Us” and “Shop now”.

  • 3 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics and Cloudflare Web Analytics.

  • 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

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.

  • 13 cookies set on arrival

    13

    Opening the homepage sets 13 cookies, 1 of them by other companies (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.

  • 15 other companies contacted

    Loading the homepage contacts 15 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 catalinaop.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Analytics
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on catalinaop.com, including 18 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

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