Website review, no card needed

shinkai.com logo

shinkai.com website review

Visit site (opens in a new tab)Reviewed 9 November 202615 issues · 68 checks

This review found 15 issues worth fixing on shinkai.com, 3 of them high impact, across 68 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

Full-page screenshot of shinkai.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. shinkai.com at 0.4 s0.4 s
  2. shinkai.com at 0.9 s0.9 s
  3. shinkai.com at 1.3 s1.3 s
  4. shinkai.com at 1.7 s1.7 s
  5. shinkai.com at 2.2 s2.2 s
  6. shinkai.com at 2.6 s2.6 s
  7. shinkai.com at 3.0 s3.0 s
  8. shinkai.com at 3.5 s3.5 s

Speed

3 to fix74
  • Reduce unused JavaScript

    1.2 s · 196 KiB

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

  • Mobile performance score: 74

    74/100

    Your mobile performance score is 74. Pages that score under 90 lose visitors before the first paint.

  • Main-thread work: 2.7 s

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and Cloudflare and others), adding 343 KiB and 139 ms of main-thread time.

  • Legacy JavaScript

    150 ms · 19 KiB

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

  • Use efficient cache lifetimes

    150 ms · 4 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (4 KiB).

  • Render-blocking requests

    150 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

  • 3 long tasks on the main thread

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

  • Improve image delivery

    27 KiB

    2 images could be 27 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.

1 checks passed
  • Server response: 5 ms

    5 ms

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

Core Web Vitals

4 to fix68
  • Largest Contentful Paint: 7.1 s

    7.1 s

    Your largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Shinkai connects you to multiple AI networks while keeping …”. Most of its time is element render delay (3.2 s).

  • Time to Interactive: 7.1 s

    7.1 s

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

  • Speed Index: 4.0 s

    4.0 s

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

  • 6 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

3 checks passed
  • Total Blocking Time: 84 ms

    84 ms

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • First Contentful Paint: 1.1 s

    1.1 s

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

Images and page weight

100
  • 2 images in older formats

    2 images (93 KiB) 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.

  • 2 images below the first screen load straight away

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

  • About 0.3 g of CO₂ per visit

    0.27 g

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

2 checks passed
  • Page weight: 978 KiB in 50 requests

    978 KiB

    Your homepage downloads 978 KiB in 50 requests on a phone: scripts 513 KiB (17), images 231 KiB (19) and fonts 140 KiB (4). That is a lean page.

  • Images are sized for phones

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

Accessibility

2 to fixGoogle 8996
  • 5 text elements with low contrast

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

  • 10 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 18 images in the HTML carry an alt attribute.

  • 37 automated accessibility rules passed

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

SEO

3 to fixGoogle 9288
  • Title is short (26 characters)

    Your title is only 26 characters: “Shinkai - AI on Your Terms”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 2 links with vague text

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

  • 15 internal links, 28 external

    The homepage links to 15 pages on shinkai.com and 28 external pages.

6 checks passed
  • Meta description: 145 characters

    Your meta description is 145 characters: “Shinkai connects you to multiple AI networks while keeping your identity, privacy, and payments decentralized. Build ag…”.

  • One H1 headline

    Your main headline reads: “AI That Works on Your Terms.Not Theirs”.

  • Canonical URL set

    The canonical URL is https://shinkai.com/.

  • Structured data in place

    Structured data found: FAQPage and Organization.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://shinkai.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

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

  • Text is in the HTML

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

Other pages

100
  • 4 pages with very little text

    https://shinkai.com/get-shinkai, https://shinkai.com/alternative-to-langchain, https://shinkai.com/alternative-to-lm-studio and https://shinkai.com/alternative-to-ai16z-eliza-os 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.

  • 10 internal pages checked

    We fetched 10 pages linked from your homepage and read each the way a search engine does.

7 checks passed
  • Linked pages load

    All 10 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 10 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 10 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

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix80
  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 768 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Try Shinkai Web” and “Download Desktop”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Try Shinkai Web”, “Download Desktop” and “Learn More”.

  • Analytics in place

    Analytics detected: Google Analytics and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads 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.

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

  • 7 other companies contacted

    Loading the homepage contacts 7 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 shinkai.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
Tailwind CSS
Analytics
Google Analytics
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 15 issues on shinkai.com, including 7 speed issues, 3 SEO issues and 2 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