Website review, no card needed
cei.ai website review
Visit site (opens in a new tab)Reviewed 28 October 202621 issues · 64 checks
This review found 21 issues worth fixing on cei.ai, 11 of them high impact, across 64 checks. The most urgent: reduce unused CSS. 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
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.9 s |
| May 16, 2026 | 3.9 s |
| May 23, 2026 | 3.8 s |
| May 30, 2026 | 3.8 s |
| Jun 6, 2026 | 3.7 s |
| Jun 13, 2026 | 3.7 s |
| Jun 20, 2026 | 3.8 s |
| Jun 27, 2026 | 3.8 s |
| Jul 4, 2026 | 3.8 s |
| Jul 11, 2026 | 3.9 s |
| Jul 18, 2026 | 4.0 s |
| Jul 25, 2026 | 4.1 s |
| Aug 1, 2026 | 4.2 s |
| Aug 8, 2026 | 4.2 s |
| Aug 15, 2026 | 4.0 s |
| Aug 22, 2026 | 4.0 s |
| Aug 29, 2026 | 4.0 s |
| Sep 5, 2026 | 3.9 s |
| Sep 12, 2026 | 4.0 s |
| Sep 19, 2026 | 3.9 s |
| Sep 26, 2026 | 4.1 s |
| Oct 3, 2026 | 4.2 s |
| Oct 10, 2026 | 4.2 s |
| Oct 17, 2026 | 4.3 s |
| Oct 24, 2026 | 4.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 110 ms |
| May 16, 2026 | 104 ms |
| May 23, 2026 | 103 ms |
| May 30, 2026 | 104 ms |
| Jun 6, 2026 | 106 ms |
| Jun 13, 2026 | 106 ms |
| Jun 20, 2026 | 112 ms |
| Jun 27, 2026 | 110 ms |
| Jul 4, 2026 | 113 ms |
| Jul 11, 2026 | 120 ms |
| Jul 18, 2026 | 121 ms |
| Jul 25, 2026 | 132 ms |
| Aug 1, 2026 | 126 ms |
| Aug 8, 2026 | 117 ms |
| Aug 15, 2026 | 117 ms |
| Aug 22, 2026 | 118 ms |
| Aug 29, 2026 | 123 ms |
| Sep 5, 2026 | 125 ms |
| Sep 12, 2026 | 126 ms |
| Sep 19, 2026 | 122 ms |
| Sep 26, 2026 | 124 ms |
| Oct 3, 2026 | 125 ms |
| Oct 10, 2026 | 129 ms |
| Oct 17, 2026 | 127 ms |
| Oct 24, 2026 | 117 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
Speed
Reduce unused CSS
1.9 s · 339 KiBAbout 339 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.9 s faster on a phone.
Render-blocking requests
1.8 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Mobile performance score: 65
65/100Your mobile performance score is 65 (desktop: 84). Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
650 ms · 126 KiB6 files are served with short cache lifetimes, so returning visitors download them again (126 KiB).
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, Hubspot and Google/Doubleclick Ads and others), adding 313 KiB and 218 ms of main-thread time.
Legacy JavaScript
200 ms · 13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 86 ms. During a long task the page ignores taps.
Reduce unused JavaScript
58 KiBAbout 58 KiB of JavaScript is downloaded but never used on this page.
Improve image delivery
49 KiB4 images could be 49 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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: 0.8 s
A phone's processor spends 0.8 s on main-thread work while loading, 380 ms of it running JavaScript. That is comfortably low.
Server response: 36 ms
36 msYour server sent the HTML in 36 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.
Real-user LCP: 4.3 s
4.3 sReal visitors wait 4.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.2 s
4.2 sReal visitors see the first content after 4.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.8 s
2.8 sReal visitors wait 2.8 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 5.9 s
5.9 sYour largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (3.1 s).
First Contentful Paint: 4.1 s
4.1 sThe first text or image appears after 4.1 s on a phone. Good is under 1.8 s.
Speed Index: 6.5 s
6.5 sVisually, the page fills in at 6.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 7.0 s
7.0 sThe page becomes fully interactive after 7.0 s. Good is under 3.8 s.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 110 ms to 117 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.9 s to 4.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 162 ms
162 msReal visitors wait 162 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.08
0.08For real visitors the layout shifts by 0.08 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 26 ms
26 msScripts block the page for only 26 ms while loading. Good is under 200 ms.
Images and page weight
About 0.3 g of CO₂ per visit
0.29 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.29 g of CO₂e: 34.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 1.0 MB in 56 requests
1.0 MBYour homepage downloads 1.0 MB in 56 requests on a phone: images 353 KiB (35), stylesheets 347 KiB (4) and scripts 288 KiB (8). That is a lean page.
Accessibility
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
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.
5 links without text
5 links have no text or label, so screen readers cannot say where they go.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
60 internal links, 4 external
The homepage links to 60 pages on cei.ai and 4 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Engineer the Agentic Enterprise”.
Title: 44 characters
Your title is a healthy 44 characters: “Home - CEI | Consulting. Solutions. Results.”.
Canonical URL set
The canonical URL is https://cei.ai/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, WebPage and WebSite.
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.ceiamerica.com/sitemap_index.xml.
AI search readiness
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://cei.ai/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.
1 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.
Other pages
14 pages without a meta description
https://cei.ai/etwin, https://cei.ai/darts-autonomous-code-generation, https://cei.ai/prism-autonomous-operations, https://cei.ai/aim-fire-autonomous-qa-testing, https://cei.ai/clairvoyance-ai-business-use-cases and https://cei.ai/migrateiq and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.
8 pages slow to respond
https://cei.ai/aim-fire-autonomous-qa-testing, https://cei.ai/clairvoyance-ai-business-use-cases, https://cei.ai/migrateiq, https://cei.ai/cosine-match-ai-talent-acquisition, https://cei.ai/ai-governance and https://cei.ai/application-engineering-modernization and 2 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 38 found) and read each the way a search engine does.
6 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 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
1 console error
1 error was logged to the browser console during Google's test (“SyntaxError: Identifier 'litespeed_ui_events' has already been declared”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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,099 words of copy
The homepage carries about 1,099 words of visible text.
3 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Learn more→”, “Contact Us” and “Schedule an Executive Workshop →”.
Social proof on the page
Social proof on the homepage: 6 customer or partner logos and 5 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and HubSpot.
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 cei.ai, 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 Tag Manager
- Hosting
- GoDaddy
Hiring
- Hiring
- 28 open roles
- Teams
- Ophthalmology Medical Office Team (16), Ophthalmologist (2), Optometrist (1)
- Job board
- greenhouse
- Careers page
- cei.ai/about-us/careers (opens in a new tab)
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 21 issues on cei.ai, including 13 speed issues, 1 SEO issue and 1 conversion gap. 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.