Programmable

Website review, no card needed

cedarai.com logo

cedarai.com website review

Visit site (opens in a new tab)Reviewed 23 October 202618 issues · 69 checks

This review found 18 issues worth fixing on cedarai.com, 7 of them high impact, across 69 checks. The most urgent: page weight: 16.6 MB in 50 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

Site score

87B

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
4.0 s2.9 sMay 9Oct 173.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.0 s
May 16, 20263.1 s
May 23, 20263.1 s
May 30, 20263.1 s
Jun 6, 20263.2 s
Jun 13, 20263.1 s
Jun 20, 20263.1 s
Jun 27, 20263.2 s
Jul 4, 20263.2 s
Jul 11, 20263.2 s
Jul 18, 20263.2 s
Jul 25, 20263.3 s
Aug 1, 20263.3 s
Aug 8, 20263.4 s
Aug 15, 20263.7 s
Aug 22, 20263.9 s
Aug 29, 20263.5 s
Sep 5, 20263.6 s
Sep 12, 20263.4 s
Sep 19, 20263.2 s
Sep 26, 20263.2 s
Oct 3, 20263.2 s
Oct 10, 20263.3 s
Oct 17, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
207 ms52 msMay 23Oct 1775 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026189 ms
May 30, 2026171 ms
Jun 6, 2026164 ms
Jun 13, 2026167 ms
Jun 20, 2026157 ms
Jun 27, 2026122 ms
Jul 4, 2026110 ms
Jul 18, 202670 ms
Jul 25, 202692 ms
Aug 1, 202689 ms
Aug 8, 202680 ms
Aug 15, 202687 ms
Aug 22, 202679 ms
Aug 29, 202670 ms
Sep 19, 2026116 ms
Sep 26, 2026126 ms
Oct 3, 2026109 ms
Oct 10, 202676 ms
Oct 17, 202675 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

www.cedarai.com (opens in a new tab)
Full-page screenshot of cedarai.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cedarai.com at 0.4 s0.4 s
  2. cedarai.com at 0.8 s0.8 s
  3. cedarai.com at 1.1 s1.1 s
  4. cedarai.com at 1.5 s1.5 s
  5. cedarai.com at 1.9 s1.9 s
  6. cedarai.com at 2.3 s2.3 s
  7. cedarai.com at 2.6 s2.6 s
  8. cedarai.com at 3.0 s3.0 s

Speed

4 to fix98

  • Use efficient cache lifetimes

    800 ms · 15.2 MB

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

  • Render-blocking requests

    800 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.

  • Reduce unused JavaScript

    150 ms · 417 KiB

    About 417 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Google Tag Manager adds 372 ms

    372 ms

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, lfeeder.com and Clickagy Audience Lab and others), adding 745 KiB and 398 ms of main-thread time.

  • 5 long tasks on the main thread

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

  • Reduce unused CSS

    20 KiB

    About 20 KiB of CSS is downloaded but never applied on this page.

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

3 checks passed

  • Mobile performance score: 98

    98/100

    Your mobile performance score is 98 (desktop: 97). That is in Google's “good” band (90 and up).

  • Main-thread work: 0.8 s

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

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

5 to fix50

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

    4.2 s

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

  • Real-user FCP: 3.4 s

    3.4 s

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

  • Real-user TTFB: 2.4 s

    2.4 s

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

  • Time to Interactive: 7.6 s

    7.6 s

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

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

    +10%

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

7 checks passed

  • Real-user CLS: 0.00

    0.00

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

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

    -58%

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

  • Total Blocking Time: 131 ms

    131 ms

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

  • Largest Contentful Paint: 2.0 s

    2.0 s

    Your largest element renders in 2.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the image.

  • First Contentful Paint: 1.3 s

    1.3 s

    The first text or image appears after 1.3 s, inside the 1.8 s “good” threshold.

  • Speed Index: 2.3 s

    2.3 s

    Visually, the page fills in at 2.3 s (Speed Index), inside the 3.4 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

2 to fix60

  • Page weight: 16.6 MB in 50 requests

    16.6 MB

    Your homepage downloads 16.6 MB in 50 requests on a phone: media 15.7 MB (3), scripts 794 KiB (15) and images 65 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    28 KiB

    1 image is downloaded at several times the size a phone draws it, for example freight-yard-poster.avif at 1,600 px wide, shown at 390 px. Resized copies would save about 28 KiB.

  • About 4.7 g of CO₂ per visit

    4.71 g

    By the Sustainable Web Design model, a visit to your homepage emits about 4.71 g of CO₂e: 565.0 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 load when needed

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

Accessibility

Google 100100
2 checks passed

  • Every image has alt text

    All 1 image in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

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

SEO

1 to fixGoogle 10096

  • Structured data has 1 problem

    Structured data found (Organization, SoftwareApplication and WebSite) but with 1 problem, for example “SoftwareApplication: no offers (price) block”.

  • 39 internal links, 5 external

    The homepage links to 39 pages on cedarai.com and 5 external pages.

7 checks passed

  • Meta description: 155 characters

    Your meta description is 155 characters: “Cedar AI's ARMS platform connects rail operations, billing, and visibility for railroads, shippers, terminals, and swit…”.

  • One H1 headline

    Your main headline reads: “One platform. End-to-end rail operations.”.

  • Title: 43 characters

    Your title is a healthy 43 characters: “Cedar AI | Automated Rail Management System”.

  • Canonical URL set

    The canonical URL is https://www.cedarai.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.cedarai.com/sitemap_index.xml.

AI search readiness

100

  • No llms.txt

    There is no https://www.cedarai.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: 6 of 6 facts

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

  • Text is in the HTML

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

Other pages

2 to fix90

  • 3 pages without a meta description

    https://www.cedarai.com/category/news, https://www.cedarai.com/category/blog and https://www.cedarai.com/privacy-policy have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.cedarai.com/privacy-policy and https://www.cedarai.com/aup have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.cedarai.com/demo has 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.

  • 8 pages slow to respond

    https://www.cedarai.com/solutions/railroads, https://www.cedarai.com/solutions/transload, https://www.cedarai.com/insights, https://www.cedarai.com/category/news, https://www.cedarai.com/company/careers and https://www.cedarai.com/contact 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 18 found) and read each the way a search engine does.

5 checks passed

  • Linked pages load

    13 pages of 15 loaded without an error (the rest turned automated requests away).

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087

  • 2 small tap targets

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

  • 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 checks passed

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix80

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 602 words of copy

    The homepage carries about 602 words of visible text.

4 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Schedule a Demo”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact Us” and “Schedule a Demo”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

Privacy and tracking

1 to fix

  • 3 trackers load before any consent

    3

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

  • 4 cookies set on arrival

    4

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

  • 12 other companies contacted

    Loading the homepage contacts 12 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 cedarai.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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 18 issues on cedarai.com, including 9 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

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