Website review, no card needed

cohoferry.com logo

cohoferry.com website review

Visit site (opens in a new tab)Reviewed 5 November 202649 issues · 95 checks

This review found 49 issues worth fixing on cohoferry.com, 24 of them high impact, across 95 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
5.2 s4.6 sMay 16Oct 314.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20264.7 s
May 23, 20264.7 s
May 30, 20264.8 s
Jun 6, 20264.8 s
Jun 13, 20264.9 s
Jun 20, 20265.0 s
Jun 27, 20265.0 s
Jul 4, 20265.0 s
Jul 11, 20265.1 s
Jul 18, 20265.1 s
Jul 25, 20265.0 s
Aug 1, 20265.0 s
Aug 8, 20264.9 s
Aug 15, 20264.9 s
Aug 22, 20264.9 s
Aug 29, 20264.9 s
Sep 5, 20265.0 s
Sep 12, 20265.0 s
Sep 19, 20265.1 s
Sep 26, 20265.0 s
Oct 3, 20265.0 s
Oct 10, 20265.0 s
Oct 17, 20264.9 s
Oct 24, 20264.9 s
Oct 31, 20264.9 s
Real-visitor tap response (INP)75th percentile, phones
124 ms80 msMay 16Oct 31113 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202687 ms
May 23, 202687 ms
May 30, 202688 ms
Jun 6, 202688 ms
Jun 13, 202688 ms
Jun 20, 202687 ms
Jun 27, 202685 ms
Jul 4, 202686 ms
Jul 11, 202688 ms
Jul 18, 202696 ms
Jul 25, 2026103 ms
Aug 1, 2026109 ms
Aug 8, 2026116 ms
Aug 15, 2026117 ms
Aug 22, 2026119 ms
Aug 29, 2026119 ms
Sep 5, 2026113 ms
Sep 12, 2026114 ms
Sep 19, 2026113 ms
Sep 26, 2026116 ms
Oct 3, 2026113 ms
Oct 10, 2026119 ms
Oct 17, 2026118 ms
Oct 24, 2026113 ms
Oct 31, 2026113 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 cohoferry.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cohoferry.com at 4.0 s4.0 s
  2. cohoferry.com at 8.0 s8.0 s
  3. cohoferry.com at 12.1 s12.1 s
  4. cohoferry.com at 16.1 s16.1 s
  5. cohoferry.com at 20.1 s20.1 s
  6. cohoferry.com at 24.1 s24.1 s
  7. cohoferry.com at 28.1 s28.1 s
  8. cohoferry.com at 32.2 s32.2 s

Speed

11 to fix46
  • Use efficient cache lifetimes

    87.8 s · 59.6 MB

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

  • Improve image delivery

    17.3 s · 26.2 MB

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

  • Reduce unused JavaScript

    7.7 s · 1.8 MB

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

  • Reduce unused CSS

    2.7 s · 491 KiB

    About 491 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.7 s faster on a phone.

  • Minify JavaScript

    1.7 s · 425 KiB

    425 KiB could be saved by minifying JavaScript.

  • Mobile performance score: 46

    46/100

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

  • Main-thread work: 4.1 s

    A phone's processor spends 4.1 s on main-thread work while loading, 2.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, Google CDN and Facebook and others), adding 1.8 MB and 1.5 s of main-thread time.

  • Google Tag Manager adds 633 ms

    633 ms

    Google Tag Manager costs a phone 633 ms of main-thread work and 717 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.

  • Google CDN adds 396 ms

    396 ms

    Google CDN costs a phone 396 ms of main-thread work and 736 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 CSS

    320 ms · 91 KiB

    91 KiB could be saved by minifying CSS.

  • 15 long tasks on the main thread

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

  • Legacy JavaScript

    200 ms · 13 KiB

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

  • Font display

    100 ms

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

  • Document request latency

    51 KiB

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

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

    32 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 223.7 s

    223.7 s

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

  • Speed Index: 22.4 s

    22.4 s

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

  • Time to Interactive: 236.6 s

    236.6 s

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

  • Total Blocking Time: 766 ms

    766 ms

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

  • Real-user LCP: 2.9 s

    2.9 s

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

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

    +30%

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

  • 54 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

6 checks passed
  • Real-user INP: 113 ms

    113 ms

    Real visitors wait 113 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.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: 586 ms

    586 ms

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix18
  • Page weight: 61.9 MB in 166 requests

    61.9 MB

    Your homepage downloads 61.9 MB in 166 requests on a phone: images 57.4 MB (55), scripts 3.2 MB (43) and stylesheets 553 KiB (18). Under 2 MB keeps phones on slow connections fast.

  • 18 images over 500 KB

    18 images weigh 54.1 MB together. On a phone connection a single image that size takes seconds.

  • 9 images far larger than shown

    16.8 MB

    9 images are downloaded at several times the size a phone draws them, for example 2026-butchart-fall-mobile.jpg at 2,500 px wide, shown at 390 px. Resized copies would save about 16.8 MB.

  • 31 images in older formats

    31 images (57.2 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 (2.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 17.5 g of CO₂ per visit

    17.55 g

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

Accessibility

12 to fixGoogle 7180
  • Input buttons must have discernible text (1 element)

    Input buttons must have discernible text: 1 element on the page fails this check, rated critical by axe-core.

  • 7 tap targets too small

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

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 83 images without alt text

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

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

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

  • Zoom is disabled

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 16 links without text

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

  • 5 form fields without a label

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

1 checks passed
  • 31 automated accessibility rules passed

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

SEO

7 to fixGoogle 7558
  • No meta description

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

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “Black Ball Ferry Line | Daily Departures to Victoria and Port Angeles”.

  • No structured data

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

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

    There is no robots.txt at cohoferry.com/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.

  • 139 internal links, 8 external

    The homepage links to 139 pages on cohoferry.com and 8 external pages.

1 checks passed
  • XML sitemap found

    Your XML sitemap is reachable at https://cohoferry.com/sitemap.xml.

AI search readiness

1 to fix81
  • 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://cohoferry.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
  • Text is in the HTML

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

Other pages

100
  • 14 pages slow to respond

    https://cohoferry.com/about-us, https://cohoferry.com/the-route, https://cohoferry.com/whats-on-board, https://cohoferry.com/faqs, https://cohoferry.com/schedule-fares and https://cohoferry.com/travel-info 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 66 found) and read each the way a search engine does.

7 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 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • 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 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5062918&Ver=2&mid=79009d22-a12d-4586-ba83-bb165af6af4d&bo=1&sid=561c6980d8e011f1b718df05b24b7431&vid=561c8b30d8e011f1a9ce7bbe60e05def&vids=1&msclkid=N&pi=918639831&lg=.

  • 3 JavaScript errors while loading

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix81
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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 map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 2,177 words of copy

    The homepage carries about 2,177 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: “Online Gift Shop” and “Schedule + Fares”.

  • 19 calls to action

    The homepage has 19 calls to action, for example “Online Gift Shop”, “Schedule + Fares” and “Book Now”.

  • 5 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 4 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
  • 8 trackers load before any consent

    8

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

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 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.

  • 37 other companies contacted

    Loading the homepage contacts 37 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 cohoferry.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
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Liquid Web

Company

Employees
10
Headquarters
Seattle

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 49 issues on cohoferry.com, including 19 speed issues, 7 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