Website review, no card needed

balseal.com logo

balseal.com website review

Visit site (opens in a new tab)Reviewed 29 October 202634 issues · 76 checks

This review found 34 issues worth fixing on balseal.com, 14 of them high impact, across 76 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

Real-visitor load time (LCP)75th percentile, phones
8.4 s2.2 sMay 9Oct 247.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.4 s
May 16, 20263.4 s
May 23, 20263.3 s
May 30, 20263.5 s
Jun 6, 20263.6 s
Jun 13, 20263.7 s
Jun 20, 20263.4 s
Jun 27, 20263.1 s
Jul 4, 20263.1 s
Jul 11, 20262.9 s
Jul 18, 20263.3 s
Aug 8, 20263.3 s
Aug 15, 20263.0 s
Aug 22, 20262.9 s
Aug 29, 20263.3 s
Sep 5, 20263.8 s
Sep 12, 20266.4 s
Sep 19, 20266.5 s
Sep 26, 20266.5 s
Oct 3, 20266.5 s
Oct 10, 20266.6 s
Oct 17, 20267.1 s
Oct 24, 20267.7 s
Real-visitor tap response (INP)75th percentile, phones
402 ms55 msMay 9Oct 24362 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202695 ms
May 16, 2026102 ms
May 23, 2026105 ms
May 30, 2026105 ms
Jun 6, 2026104 ms
Jun 13, 202697 ms
Jun 20, 202699 ms
Jun 27, 2026104 ms
Jul 4, 2026104 ms
Jul 11, 2026104 ms
Jul 18, 2026103 ms
Aug 8, 2026118 ms
Aug 15, 2026106 ms
Aug 22, 202698 ms
Aug 29, 2026109 ms
Sep 5, 2026136 ms
Sep 12, 2026214 ms
Sep 19, 2026294 ms
Sep 26, 2026324 ms
Oct 3, 2026343 ms
Oct 10, 2026346 ms
Oct 17, 2026362 ms
Oct 24, 2026362 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 balseal.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. balseal.com at 0.4 s0.4 s
  2. balseal.com at 0.9 s0.9 s
  3. balseal.com at 1.3 s1.3 s
  4. balseal.com at 1.7 s1.7 s
  5. balseal.com at 2.1 s2.1 s
  6. balseal.com at 2.6 s2.6 s
  7. balseal.com at 3.0 s3.0 s
  8. balseal.com at 3.4 s3.4 s

Speed

7 to fix54
  • Render-blocking requests

    14.3 s

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

  • Reduce unused CSS

    9.2 s · 1.8 MB

    About 1.8 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 9.2 s faster on a phone.

  • Reduce unused JavaScript

    1.1 s · 1.3 MB

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

  • Use efficient cache lifetimes

    2.2 MB

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

  • Mobile performance score: 54

    54/100

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

  • Improve image delivery

    511 KiB

    9 images could be 511 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 1,621 HTML elements

    The page has 1,621 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 2 long tasks on the main thread

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

  • Legacy JavaScript

    32 KiB

    Polyfills for old browsers add 32 KiB JavaScript that modern phones do not need.

  • 4 third-party services on the page

    4 third-party services load with your homepage (cloudflare.com, JSDelivr CDN and Google Fonts and others), adding 80 KiB and 23 ms of main-thread time.

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

2 checks passed
  • Main-thread work: 1.1 s

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

  • Server response: 31 ms

    31 ms

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

Core Web Vitals

12 to fix33
  • 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: 6.9 s

    6.9 s

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

  • Real-user FCP: 6.7 s

    6.7 s

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

  • Real-user TTFB: 1.8 s

    1.8 s

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

  • First Contentful Paint: 14.9 s

    14.9 s

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

  • Largest Contentful Paint: 17.0 s

    17.0 s

    Your largest element takes 17.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Bal Seal Engineering: Custom Seals, Springs & Connectors Ba…”.

  • Time to Interactive: 24.2 s

    24.2 s

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

  • Speed Index: 14.9 s

    14.9 s

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

  • Real-user INP: 358 ms

    358 ms

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

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

    +268%

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

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

    +120%

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

  • 5 images without width and height

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

3 checks passed
  • Real-user CLS: 0.01

    0.01

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

  • Cumulative Layout Shift: 0.079

    0.079

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

  • Total Blocking Time: 6 ms

    6 ms

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

Images and page weight

1 to fix70
  • Page weight: 8.1 MB in 101 requests

    8.1 MB

    Your homepage downloads 8.1 MB in 101 requests on a phone: media 2.2 MB (3), stylesheets 2.0 MB (29) and scripts 1.8 MB (36). Under 2 MB keeps phones on slow connections fast.

  • About 2.3 g of CO₂ per visit

    2.30 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

8 to fixGoogle 9190
  • 7 text elements with low contrast

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

  • 8 links without text

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

  • 3 form fields without a label

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

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

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

  • ARIA role should be appropriate for the element (2 elements)

    ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

  • Elements marked as presentational should be consistently ignored (2 elements)

    Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 42 automated accessibility rules passed

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

SEO

2 to fixGoogle 9293
  • 3 H1 headlines

    There are 3 <h1> headlines (“Custom Spring-energized PTFE Seals For Surgical R…”, “SYGNUS Electrical Connectors for Neuromodulation …” and “Seal Starter 3D”). One clear main headline is easier for people and search engines.

  • 10 links with vague text

    10 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 110 internal links, 10 external

    The homepage links to 110 pages on balseal.com and 10 external pages.

7 checks passed
  • Meta description: 146 characters

    Your meta description is 146 characters: “Custom seals, spring energized seals, & canted coil springs for critical applications. Trusted by aerospace, medical, &…”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Bal Seal Engineering | Custom Seals, Springs & Contacts”.

  • Canonical URL set

    The canonical URL is https://www.balseal.com/.

  • 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://www.balseal.com/sitemap_index.xml.

AI search readiness

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

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.balseal.com/llms.txt (1 KiB, 16 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 53 found) and read each the way a search engine does.

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

2 to fixGoogle 9687
  • 6 small tap targets

    6 of 24 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Cannot set properties of undefined (setting 'domFonts')”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix80
  • Thin social proof

    Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • A 11-field form

    Your longest form asks for 11 fields (4 required). Every extra field lowers completion.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 546 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Bal Contact®”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “BAL CONTACT”, “Sygnus Contact System” and “Design Request”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

  • 3 cookies set on arrival

    3

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

  • 7 other companies contacted

    Loading the homepage contacts 7 hosts 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 balseal.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
Analytics
Google Analytics | Google Tag Manager
Hosting
Akamai Cloud

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on balseal.com, including 19 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

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