Website review, no card needed

siconnex.com logo

siconnex.com website review

Visit site (opens in a new tab)Reviewed 21 October 202633 issues · 77 checks

This review found 33 issues worth fixing on siconnex.com, 13 of them high impact, across 77 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
6.2 s4.3 sMay 2Sep 125.0 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20265.9 s
May 9, 20265.9 s
May 16, 20265.8 s
May 23, 20265.3 s
May 30, 20264.8 s
Jun 6, 20264.8 s
Jun 13, 20264.9 s
Jun 20, 20264.9 s
Jun 27, 20265.0 s
Jul 4, 20265.1 s
Jul 11, 20265.0 s
Jul 18, 20265.0 s
Jul 25, 20265.0 s
Aug 1, 20265.3 s
Aug 8, 20265.6 s
Aug 15, 20265.6 s
Aug 22, 20265.3 s
Aug 29, 20264.5 s
Sep 5, 20264.7 s
Sep 12, 20265.0 s
Real-visitor tap response (INP)75th percentile, phones
328 ms161 msMay 2Sep 12241 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026309 ms
May 9, 2026293 ms
May 16, 2026278 ms
May 23, 2026236 ms
May 30, 2026246 ms
Jun 6, 2026236 ms
Jun 13, 2026205 ms
Jun 20, 2026181 ms
Jun 27, 2026180 ms
Jul 4, 2026198 ms
Jul 11, 2026198 ms
Jul 18, 2026204 ms
Jul 25, 2026204 ms
Aug 1, 2026209 ms
Aug 8, 2026236 ms
Aug 15, 2026242 ms
Aug 22, 2026223 ms
Aug 29, 2026197 ms
Sep 5, 2026206 ms
Sep 12, 2026241 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 siconnex.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. siconnex.com at 0.5 s0.5 s
  2. siconnex.com at 1.0 s1.0 s
  3. siconnex.com at 1.5 s1.5 s
  4. siconnex.com at 2.0 s2.0 s
  5. siconnex.com at 2.5 s2.5 s
  6. siconnex.com at 2.9 s2.9 s
  7. siconnex.com at 3.4 s3.4 s
  8. siconnex.com at 3.9 s3.9 s

Speed

10 to fix58
  • Use efficient cache lifetimes

    3.6 s · 669 KiB

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

  • Reduce unused JavaScript

    1.5 s · 304 KiB

    About 304 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

  • Render-blocking requests

    1.3 s

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

  • Mobile performance score: 58

    58/100

    Your mobile performance score is 58 (desktop: 80). 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, Facebook and Hubspot and others), adding 1.1 MB and 578 ms of main-thread time.

  • Legacy JavaScript

    450 ms · 39 KiB

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

  • Google Tag Manager adds 323 ms

    323 ms

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

  • Reduce unused CSS

    300 ms · 17 KiB

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

  • Main-thread work: 2.6 s

    A phone's processor spends 2.6 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • imagekit.io adds 0 ms

    0 ms

    imagekit.io costs a phone 0 ms of main-thread work and 385 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.

  • 10 long tasks on the main thread

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

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

    110 ms

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

Core Web Vitals

10 to fix0
  • 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.6 s

    6.6 s

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

  • Real-user CLS: 0.86

    0.86

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

  • Largest Contentful Paint: 12.1 s

    12.1 s

    Your largest element takes 12.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We want your old batch spray tool.”.

  • Time to Interactive: 12.2 s

    12.2 s

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

  • Speed Index: 6.5 s

    6.5 s

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

  • Real-user INP: 352 ms

    352 ms

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • Real-user TTFB: 1.4 s

    1.4 s

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

  • Total Blocking Time: 447 ms

    447 ms

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

4 checks passed
  • Tap response (INP) got 26% faster for real visitors

    -26%

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

  • Largest content (LCP) got 18% faster for real visitors

    -18%

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

  • 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

100
  • About 0.4 g of CO₂ per visit

    0.43 g

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

4 checks passed
  • Page weight: 1.5 MB in 89 requests

    1.5 MB

    Your homepage downloads 1.5 MB in 89 requests on a phone: scripts 1,001 KiB (31), images 391 KiB (13) and stylesheets 54 KiB (16). That is a lean page.

  • 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

5 to fixGoogle 8391
  • 1 button without a name

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

  • 3 text elements with low contrast

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

  • 26 images without alt text

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

  • 5 links without text

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

  • 1 form field without a label

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

1 checks passed
  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 4 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 8594
  • No structured data

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

  • 4 links with vague text

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

  • No X (Twitter) card tag

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

  • 58 internal links, 8 external

    The homepage links to 58 pages on siconnex.com and 8 external pages.

7 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “Discover innovative BATCHSPRAY technology for semiconductor wet processing. Optimize wafer yield, reduce cleanroom foot…”.

  • One H1 headline

    Your main headline reads: “We want your old batch spray tool.”.

  • Title: 49 characters

    Your title is a healthy 49 characters: “Siconnex | Semiconductor Wet Processing Equipment”.

  • Canonical URL set

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

  • 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.siconnex.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://www.siconnex.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 (689 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 2 pages with very little text

    https://www.siconnex.com/videos and https://www.siconnex.com/applications have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 35 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

Google 96100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    16 of 18 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix58
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • Thin social proof

    Social proof on the homepage: 6 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

    The homepage carries about 726 words of visible text.

2 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact” and “Get in touch”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 1 more (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.

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

  • 20 other companies contacted

    Loading the homepage contacts 20 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 siconnex.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
Next.js

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on siconnex.com, including 20 speed issues, 2 SEO issues and 4 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