Website review, no card needed
mysticseaport.org website review
Visit site (opens in a new tab)Reviewed 26 October 202649 issues · 95 checks
This review found 49 issues worth fixing on mysticseaport.org, 19 of them high impact, across 95 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
67DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.6 s |
| May 16, 2026 | 1.7 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 134 ms |
| May 16, 2026 | 135 ms |
| May 23, 2026 | 133 ms |
| May 30, 2026 | 136 ms |
| Jun 6, 2026 | 136 ms |
| Jun 13, 2026 | 138 ms |
| Jun 20, 2026 | 140 ms |
| Jun 27, 2026 | 140 ms |
| Jul 4, 2026 | 139 ms |
| Jul 11, 2026 | 138 ms |
| Jul 18, 2026 | 138 ms |
| Jul 25, 2026 | 141 ms |
| Aug 1, 2026 | 148 ms |
| Aug 8, 2026 | 158 ms |
| Aug 15, 2026 | 167 ms |
| Aug 22, 2026 | 177 ms |
| Aug 29, 2026 | 179 ms |
| Sep 5, 2026 | 180 ms |
| Sep 12, 2026 | 185 ms |
| Sep 19, 2026 | 188 ms |
| Sep 26, 2026 | 196 ms |
| Oct 3, 2026 | 204 ms |
| Oct 10, 2026 | 209 ms |
| Oct 17, 2026 | 212 ms |
| Oct 24, 2026 | 213 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
6.3 s51 files block the first paint until they finish downloading. Deferring or inlining them could save about 6.3 s.
Reduce unused JavaScript
4.0 s · 800 KiBAbout 800 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.0 s faster on a phone.
Improve image delivery
3.3 s · 1.1 MB9 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.3 s faster on a phone.
Google Tag Manager adds 1.1 s
1.1 sGoogle Tag Manager costs a phone 1.1 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: 35
35/100Your mobile performance score is 35 (desktop: 37). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Google Analytics and others), adding 1.6 MB and 1.6 s of main-thread time.
Use efficient cache lifetimes
850 ms · 342 KiB14 files are served with short cache lifetimes, so returning visitors download them again (342 KiB).
Facebook adds 426 ms
426 msFacebook costs a phone 426 ms of main-thread work and 334 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.
Main-thread work: 2.9 s
A phone's processor spends 2.9 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 235 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 37 KiBAbout 37 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
150 ms · 12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify CSS
7 KiB7 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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
First Contentful Paint: 8.7 s
8.7 sThe first text or image appears after 8.7 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 38.1 s
38.1 sYour largest element takes 38.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “WHAT LURKS BENEATH: GHOST SHIP SELECT DATES THROUGH OCTOBER…”.
Speed Index: 15.5 s
15.5 sVisually, the page fills in at 15.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 38.6 s
38.6 sThe page becomes fully interactive after 38.6 s. Good is under 3.8 s.
Total Blocking Time: 868 ms
868 msScripts block taps and scrolling for 868 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 235 ms
235 msReal visitors wait 235 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 58% slower for real visitors
+58%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 134 ms to 213 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 655 ms
655 msReal visitors wait 655 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 7.0 MB in 176 requests
7.0 MBYour homepage downloads 7.0 MB in 176 requests on a phone: images 4.3 MB (27), scripts 1.9 MB (51) and fonts 667 KiB (9). Under 2 MB keeps phones on slow connections fast.
5 images in older formats
5 images (853 KiB) 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.
6 images below the first screen load straight away
6 images further down the page (879 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
4 images far larger than shown
25 KiB4 images are downloaded at several times the size a phone draws them, for example d2016-08-0437-packard-1200x792.jpg at 1,200 px wide, shown at 390 px. Resized copies would save about 25 KiB.
About 2.0 g of CO₂ per visit
1.98 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.98 g of CO₂e: 237.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
21 text elements with low contrast
21 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
10 tap targets too small
10 tap targets are too small or too close together to hit reliably with a finger.
Elements must only use permitted ARIA attributes (6 elements)
Elements must only use permitted ARIA attributes: 6 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner 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.
The skip-link target should exist and be focusable (1 element)
The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
2 checks passed
Every image has alt text
All 12 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 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 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
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
11 links with vague text
11 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
96 internal links, 49 external
The homepage links to 96 pages on mysticseaport.org and 49 external pages.
7 checks passed
Meta description: 137 characters
Your meta description is 137 characters: “Mystic Seaport Museum is located in Mystic, CT and is the nation's leading maritime museum. Learn more now about our ex…”.
Title: 53 characters
Your title is a healthy 53 characters: “Mystic Seaport Museum - Maritime Museum in Mystic, CT”.
Canonical URL set
The canonical URL is https://mysticseaport.org/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://mysticseaport.org/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://mysticseaport.org/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 (825 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a title
https://mysticseaport.org/calendar has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://mysticseaport.org/calendar is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages without a meta description
https://mysticseaport.org/calendar and https://mysticseaport.org/find-your-sea-story have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://mysticseaport.org/explore/vessels and https://mysticseaport.org/explore/village use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://mysticseaport.org/visit/plan-your-visit/mystic-seaport-marina, whose canonical is https://mysticseaport.org/visit/mystic-seaport-marina. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 pages without an H1
https://mysticseaport.org/visit/hours-tickets, https://mysticseaport.org/whatlurksbeneath, https://mysticseaport.org/exhibit/brickwrecks, https://mysticseaport.org/lantern-lights, https://mysticseaport.org/calendar and https://mysticseaport.org/exhibit/monstrous and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 62 found) and read each the way a search engine does.
2 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343135298&tm=gtm002&Ver=2&mid=16ea0ec3-9d04-4aa8-9e82-d8e9f5ff80b3&bo=1&sid=270fae90d11d11f19217d76339204314&vid=270fc400d11d11f19f89b3c933a70b5c&vids=1&msclkid=N&pi=9.
6 small tap targets
6 of 13 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 distorted images
2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Requests the geolocation permission on page load
Requests the geolocation permission on page load.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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: 30 testimonial or review blocks. 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 793 words of copy
The homepage carries about 793 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “JOIN”.
10 calls to action
The homepage has 10 calls to action, for example “JOIN”, “SHOP” and “CONTACT US”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel and 2 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.
15 cookies set on arrival
15Opening the homepage sets 15 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.
32 other companies contacted
Loading the homepage contacts 32 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 mysticseaport.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2021.
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
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 mysticseaport.org, including 18 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.