Website review, no card needed

e-ci.com logo

e-ci.com website review

Visit site (opens in a new tab)Reviewed 26 October 202640 issues · 91 checks

This review found 40 issues worth fixing on e-ci.com, 13 of them high impact, across 91 checks. The most urgent: reduce unused JavaScript. 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.7 s2.5 sMay 9Oct 243.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20266.2 s
May 16, 20266.1 s
May 23, 20266.1 s
May 30, 20263.9 s
Jun 6, 20263.9 s
Jun 13, 20264.1 s
Jun 20, 20264.0 s
Jun 27, 20263.8 s
Jul 4, 20263.7 s
Jul 11, 20263.7 s
Jul 18, 20263.6 s
Jul 25, 20263.6 s
Aug 1, 20263.4 s
Aug 8, 20263.0 s
Aug 15, 20263.0 s
Aug 22, 20263.2 s
Aug 29, 20263.3 s
Sep 5, 20263.3 s
Sep 12, 20263.4 s
Sep 19, 20263.3 s
Sep 26, 20263.3 s
Oct 3, 20263.2 s
Oct 10, 20263.1 s
Oct 17, 20263.1 s
Oct 24, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
243 ms94 msMay 9Oct 24111 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026226 ms
May 16, 2026203 ms
May 23, 2026207 ms
May 30, 2026137 ms
Jun 6, 2026138 ms
Jun 13, 2026151 ms
Jun 20, 2026145 ms
Jun 27, 2026147 ms
Jul 4, 2026137 ms
Jul 11, 2026128 ms
Jul 18, 2026119 ms
Jul 25, 2026121 ms
Aug 1, 2026125 ms
Aug 8, 2026120 ms
Aug 15, 2026121 ms
Aug 22, 2026125 ms
Aug 29, 2026128 ms
Sep 5, 2026128 ms
Sep 12, 2026137 ms
Sep 19, 2026137 ms
Sep 26, 2026132 ms
Oct 3, 2026131 ms
Oct 10, 2026119 ms
Oct 17, 2026112 ms
Oct 24, 2026111 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 e-ci.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. e-ci.com at 0.8 s0.8 s
  2. e-ci.com at 1.6 s1.6 s
  3. e-ci.com at 2.4 s2.4 s
  4. e-ci.com at 3.2 s3.2 s
  5. e-ci.com at 4.0 s4.0 s
  6. e-ci.com at 4.8 s4.8 s
  7. e-ci.com at 5.6 s5.6 s
  8. e-ci.com at 6.4 s6.4 s

Speed

16 to fix23
  • Reduce unused JavaScript

    7.0 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.0 s faster on a phone.

  • Render-blocking requests

    3.4 s

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

  • Main-thread work: 10.5 s

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

  • Mobile performance score: 23

    23/100

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

  • 3,525 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (ContentSquare, Squarespace and Google Tag Manager and others), adding 3.5 MB and 3.3 s of main-thread time.

  • Improve image delivery

    450 ms · 2.0 MB

    26 images could be 2.0 MB 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.

  • Use efficient cache lifetimes

    900 ms · 557 KiB

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

  • Reduce unused CSS

    900 ms · 174 KiB

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

  • Squarespace adds 914 ms

    914 ms

    Squarespace costs a phone 914 ms of main-thread work and 1.3 MB 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.

  • ContentSquare adds 930 ms

    930 ms

    ContentSquare costs a phone 930 ms of main-thread work and 184 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.

  • Legacy JavaScript

    750 ms · 177 KiB

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

  • Google Tag Manager adds 433 ms

    433 ms

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

  • hsappstatic.net adds 282 ms

    282 ms

    hsappstatic.net costs a phone 282 ms of main-thread work and 584 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.

  • 20 long tasks on the main thread

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

  • sqspcdn.com adds 250 ms

    250 ms

    sqspcdn.com costs a phone 250 ms of main-thread work and 412 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.

  • Font display

    150 ms

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

  • Phones get a much slower page than desktops

    Desktop scores 51 but mobile only 23. 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.

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

    87 ms

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

Core Web Vitals

7 to fix100
  • Largest Contentful Paint: 27.8 s

    27.8 s

    Your largest element takes 27.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “PERFORMANCE THAT DOESN’T AGE.”.

  • Speed Index: 17.7 s

    17.7 s

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

  • Time to Interactive: 39.0 s

    39.0 s

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

  • First Contentful Paint: 6.7 s

    6.7 s

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

  • Total Blocking Time: 1.6 s

    1.6 s

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

  • Cumulative Layout Shift: 0.153

    0.153

    The layout shifts by 0.153 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 1 image without width and height

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

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user CLS: 0.02

    0.02

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

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Real-user TTFB: 587 ms

    587 ms

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

  • Tap response (INP) got 48% faster for real visitors

    -48%

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

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

    -50%

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

Images and page weight

2 to fix63
  • Page weight: 7.4 MB in 262 requests

    7.4 MB

    Your homepage downloads 7.4 MB in 262 requests on a phone: scripts 3.7 MB (108), images 2.9 MB (51) and stylesheets 351 KiB (27). Under 2 MB keeps phones on slow connections fast.

  • 18 images below the first screen load straight away

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

  • About 2.1 g of CO₂ per visit

    2.10 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

4 to fixGoogle 9194
  • 10 text elements with low contrast

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

  • Links must have discernible text (3 elements)

    Links must have discernible text: 3 elements on the page fail this check, rated serious by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

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

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 72 images in the HTML carry an alt attribute.

  • 44 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: 44 passed and 5 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9284
  • 4 H1 headlines

    There are 4 <h1> headlines (“PERFORMANCE THAT DOESN’T AGE.”, “More Than Machines” and “Sponsorships”). One clear main headline is easier for people and search engines.

  • Meta description is long (259 characters)

    Your meta description is 259 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 2 problems

    Structured data found (LocalBusiness, Organization and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/5e66928f9f87a05becd…”.

  • 8 links with vague text

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

  • 306 internal links, 31 external

    The homepage links to 306 pages on e-ci.com and 31 external pages.

5 checks passed
  • Title: 61 characters

    Your title is a healthy 61 characters: “Cincinnati Incorporated - USA Made Metal Fabrication Machines”.

  • Canonical URL set

    The canonical URL is https://www.e-ci.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.e-ci.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing name, url, logo and description. 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://www.e-ci.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 (2,399 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 1 linked page hidden from search

    https://www.e-ci.com/deals is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 6 pages without a meta description

    https://www.e-ci.com/ci-suite-software, https://www.e-ci.com/industries, https://www.e-ci.com/industries/transportation, https://www.e-ci.com/industries/agriculture, https://www.e-ci.com/industries/aerospace and https://www.e-ci.com/deals have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.e-ci.com/ci-suite-software has 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 107 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.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 5488
  • 3 third-party cookies

    3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/5e66928f9f87a05becdce88d/534/5c5…”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    10 of 11 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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 1,026 words of copy

    The homepage carries about 1,026 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: “CALL” and “LEARN MORE”.

  • 25 calls to action

    The homepage has 25 calls to action, for example “Download Product Catalog”, “Order Parts” and “Contact Us”.

  • Social proof on the page

    Social proof on the homepage: 2 customer or partner logos and 4 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and LinkedIn Insight.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

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

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 cookies, 2 of them by other companies (measured from a US location before any click).

  • 45 other companies contacted

    Loading the homepage contacts 45 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) loads with the page.

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 e-ci.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
Squarespace
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Squarespace

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on e-ci.com, including 23 speed issues and 4 SEO issues. 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