Website review, no card needed
cesoinc.com website review
Visit site (opens in a new tab)Reviewed 3 November 202636 issues · 82 checks
This review found 36 issues worth fixing on cesoinc.com, 11 of them high impact, across 82 checks. The most urgent: improve image delivery. 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 16, 2026 | 950 ms |
| May 23, 2026 | 970 ms |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.0 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.1 s |
| Jul 4, 2026 | 1.1 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 796 ms |
| Jul 25, 2026 | 870 ms |
| Aug 1, 2026 | 888 ms |
| Aug 8, 2026 | 901 ms |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.2 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.3 s |
| Oct 31, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 62 ms |
| May 23, 2026 | 61 ms |
| May 30, 2026 | 61 ms |
| Jun 6, 2026 | 62 ms |
| Jun 13, 2026 | 62 ms |
| Jun 20, 2026 | 65 ms |
| Jun 27, 2026 | 65 ms |
| Jul 4, 2026 | 65 ms |
| Jul 11, 2026 | 65 ms |
| Jul 18, 2026 | 55 ms |
| Jul 25, 2026 | 55 ms |
| Aug 1, 2026 | 55 ms |
| Aug 8, 2026 | 60 ms |
| Aug 15, 2026 | 70 ms |
| Aug 22, 2026 | 62 ms |
| Aug 29, 2026 | 62 ms |
| Sep 5, 2026 | 62 ms |
| Sep 12, 2026 | 54 ms |
| Sep 19, 2026 | 62 ms |
| Sep 26, 2026 | 63 ms |
| Oct 3, 2026 | 62 ms |
| Oct 10, 2026 | 62 ms |
| Oct 17, 2026 | 60 ms |
| Oct 24, 2026 | 60 ms |
| Oct 31, 2026 | 62 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Improve image delivery
2.3 s · 24.5 MB17 images could be 24.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.3 s faster on a phone.
Mobile performance score: 68
68/100Your mobile performance score is 68. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
310 ms · 42 KiBAbout 42 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 310 ms faster on a phone.
Render-blocking requests
350 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.
Use efficient cache lifetimes
300 ms · 35 KiB2 files are served with short cache lifetimes, so returning visitors download them again (35 KiB).
Minify JavaScript
150 ms · 5 KiB5 KiB could be saved by minifying JavaScript.
3 third-party services on the page
3 third-party services load with your homepage (Cookiebot, Google Fonts and Google Tag Manager), adding 361 KiB and 105 ms of main-thread time.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 50 ms. During a long task the page ignores taps.
Reduce unused CSS
10 ms · 31 KiBAbout 31 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 10 ms faster on a phone.
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
4 KiB4 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 0.5 s
A phone's processor spends 0.5 s on main-thread work while loading, 165 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 81.7 s
81.7 sYour largest element takes 81.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “500+ PassionateAssociates 16 Offices Across the Country 35+…”.
Time to Interactive: 88.5 s
88.5 sThe page becomes fully interactive after 88.5 s. Good is under 3.8 s.
Largest content (LCP) got 41% slower for real visitors
+41%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 5.5 s
5.5 sVisually, the page fills in at 5.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
17 images without width and height
17 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 62 ms to 62 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 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.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 39.2 MB in 44 requests
39.2 MBYour homepage downloads 39.2 MB in 44 requests on a phone: images 25.8 MB (26), media 12.9 MB (1) and scripts 399 KiB (10). Under 2 MB keeps phones on slow connections fast.
16 images over 500 KB
16 images weigh 24.9 MB together. On a phone connection a single image that size takes seconds.
11 images far larger than shown
6.0 MB11 images are downloaded at several times the size a phone draws them, for example Land-Planning_With-Shadow.png at 500 px wide, shown at 102 px. Resized copies would save about 6.0 MB.
17 images in older formats
17 images (25.3 MB) 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.
16 images below the first screen load straight away
16 images further down the page (24.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 11.1 g of CO₂ per visit
11.10 gBy the Sustainable Web Design model, a visit to your homepage emits about 11.10 g of CO₂e: 1331.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
4 text elements with low contrast
4 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 (4 elements)
All page content should be contained by landmarks: 4 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.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
Alternative text of images should not be repeated as text (11 elements)
Alternative text of images should not be repeated as text: 11 elements on the page fail this check, rated minor by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
1 checks passed
39 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: 39 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (15 characters)
Your title is only 15 characters: “Home - CESO Inc”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (383 characters)
Your meta description is 383 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “ld+json block 3 is not valid JSON (Unexpected non-whitespace character after JSON at position 8)”.
45 internal links, 1 external
The homepage links to 45 pages on cesoinc.com and 1 external page.
4 checks passed
Canonical URL set
The canonical URL is https://www.cesoinc.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.
XML sitemap found
Your XML sitemap is reachable at https://www.cesoinc.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.cesoinc.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.
3 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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, description and contact details; sameAs (social profiles) would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (244 words), so crawlers that don't run JavaScript still read it.
Other pages
13 pages share a meta description
https://www.cesoinc.com/about, https://www.cesoinc.com/markets, https://www.cesoinc.com/projects, https://www.cesoinc.com/careers, https://www.cesoinc.com/contact and https://www.cesoinc.com/projects/fedex-ground-2 and 7 others use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://www.cesoinc.com/about has no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://www.cesoinc.com/markets, https://www.cesoinc.com/projects and https://www.cesoinc.com/contact 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 41 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.
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.
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 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
2 checks passed
Tap targets are thumb-sized
15 of 15 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 315 words of copy
The homepage carries about 315 words of visible text.
2 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact” and “Start a Project”.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
5 other companies contacted
Loading the homepage contacts 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) 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 cesoinc.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
- Hosting
- Liquid Web
Hiring
- Hiring
- 41 open roles
- Teams
- Mechanical, Electrical, and Plumbing (13), Survey (7), Architecture (6), Civil Engineering (6)
- Job board
- lever
- Careers page
- www.cesoinc.com/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 36 issues on cesoinc.com, including 11 speed issues, 4 SEO issues and 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.