Website review, no card needed

seastrom-mfg.com logo

seastrom-mfg.com website review

Visit site (opens in a new tab)Reviewed 22 October 202632 issues · 78 checks

This review found 32 issues worth fixing on seastrom-mfg.com, 9 of them high impact, across 78 checks. The most urgent: render-blocking requests. 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

Full-page screenshot of seastrom-mfg.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. seastrom-mfg.com at 0.4 s0.4 s
  2. seastrom-mfg.com at 0.8 s0.8 s
  3. seastrom-mfg.com at 1.1 s1.1 s
  4. seastrom-mfg.com at 1.5 s1.5 s
  5. seastrom-mfg.com at 1.9 s1.9 s
  6. seastrom-mfg.com at 2.3 s2.3 s
  7. seastrom-mfg.com at 2.6 s2.6 s
  8. seastrom-mfg.com at 3.0 s3.0 s

Speed

7 to fix64
  • Render-blocking requests

    2.2 s

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

  • Use efficient cache lifetimes

    1.1 s · 947 KiB

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

  • Mobile performance score: 64

    64/100

    Your mobile performance score is 64 (desktop: 91). Pages that score under 90 lose visitors before the first paint.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Bing Ads and Google Analytics and others), adding 633 KiB and 901 ms of main-thread time.

  • Improve image delivery

    450 ms · 437 KiB

    21 images could be 437 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • Google Tag Manager adds 765 ms

    765 ms

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

  • 6 long tasks on the main thread

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

  • Reduce unused JavaScript

    200 KiB

    About 200 KiB of JavaScript is downloaded but never used on this page.

  • Phones get a much slower page than desktops

    Desktop scores 91 but mobile only 64. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.7 s

    A phone's processor spends 1.7 s on main-thread work while loading, 837 ms of it running JavaScript. That is comfortably low.

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

5 to fix62
  • Time to Interactive: 11.1 s

    11.1 s

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

  • Largest Contentful Paint: 4.9 s

    4.9 s

    Your largest element takes 4.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Standard Stocked Washers & Hardware CONTINUE »”.

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Total Blocking Time: 516 ms

    516 ms

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

  • 24 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Speed Index: 3.0 s

    3.0 s

    Visually, the page fills in at 3.0 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0.02

    0.02

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

Images and page weight

100
  • 2 images in older formats

    2 images (71 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.

  • 3 images below the first screen load straight away

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

  • About 0.5 g of CO₂ per visit

    0.50 g

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

2 checks passed
  • Page weight: 1.8 MB in 89 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 89 requests on a phone: images 895 KiB (38), scripts 667 KiB (24) and fonts 205 KiB (3). That is a lean page.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 8290
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 4 images without alt text

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

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

  • No main landmark

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

1 checks passed
  • 29 automated accessibility rules passed

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

SEO

5 to fixGoogle 7572
  • No meta description

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

  • Title is short (22 characters)

    Your title is only 22 characters: “Seastrom Manufacturing”. 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.

  • 3 H1 headlines

    There are 3 <h1> headlines (“Seastrom has been providing Custom to Print parts…”, “Seastrom is the Premier Manufacturer of Precision…” and “Proudly made in America for 97 years and counting”). One clear main headline is easier for people and search engines.

  • 8 links crawlers can't follow

    8 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 119 internal links, 10 external

    The homepage links to 119 pages on seastrom-mfg.com and 10 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.seastrom-mfg.com/home.aspx.

  • 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://www.seastrom-mfg.com/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://seastrom-mfg.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.

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

Other pages

3 to fix83
  • 8 pages share a title

    /, https://seastrom-mfg.com/quick_search.aspx, https://seastrom-mfg.com/online_quote.aspx, https://seastrom-mfg.com/engineering_resources.aspx, https://seastrom-mfg.com/contact_us.aspx and https://seastrom-mfg.com/customer_service.aspx and 2 others all use the title “Seastrom Manufacturing”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://seastrom-mfg.com/quick_search.aspx, https://seastrom-mfg.com/online_quote.aspx, https://seastrom-mfg.com/customer_service.aspx, https://seastrom-mfg.com/viewcart.aspx and https://seastrom-mfg.com/washersearch.aspx have no meta description, so Google writes the search snippet from whatever text it finds.

  • 13 pages without an H1

    https://seastrom-mfg.com/quick_search.aspx, https://seastrom-mfg.com/online_quote.aspx, https://seastrom-mfg.com/custom_capabilities.aspx, https://seastrom-mfg.com/standardhardware.aspx, https://seastrom-mfg.com/militarymenu.aspx and https://seastrom-mfg.com/standardwashers.aspx and 7 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 37 found) and read each the way a search engine does.

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

3 to fixGoogle 6976
  • 3 broken images

    3 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=25063373&Ver=2&mid=b1f8fe8c-0e47-4f42-a500-1c1238ae5c5f&bo=1&sid=9247b640cde911f18dd6a99890414bd3&vid=92480960cde911f18cffff3b67bdfe5f&vids=1&msclkid=N&pi=918639831&lg.

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Uncaught SyntaxError: Unexpected token ','”.

  • 5 low-resolution images

    5 images are served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    33 of 34 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: 2 trust badges. 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 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 302 words of copy

    The homepage carries about 302 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: “Request a Quote” and “Contact Us”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Request a Quote”, “Contact Us” and “Register”.

  • 1 short form

    A short form (2 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.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Microsoft Ads and The Trade Desk (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

    15

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

  • 22 other companies contacted

    Loading the homepage contacts 22 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 seastrom-mfg.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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on seastrom-mfg.com, including 12 speed issues, 5 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