Website review, no card needed

keyshot.com logo

keyshot.com website review

Visit site (opens in a new tab)Reviewed 18 October 202626 issues · 74 checks

This review found 26 issues worth fixing on keyshot.com, 8 of them high impact, across 74 checks. The most urgent: fails Core Web Vitals for real visitors. 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
8.0 s1.7 sApr 25Oct 103.0 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20267.3 s
May 2, 20267.0 s
May 9, 20266.9 s
May 16, 20266.4 s
May 23, 20265.6 s
May 30, 20264.2 s
Jun 6, 20263.2 s
Jun 13, 20262.8 s
Jun 20, 20262.8 s
Jun 27, 20263.0 s
Jul 4, 20263.0 s
Jul 11, 20262.9 s
Jul 18, 20262.9 s
Jul 25, 20262.8 s
Aug 1, 20262.8 s
Aug 8, 20262.7 s
Aug 15, 20262.6 s
Aug 22, 20262.6 s
Aug 29, 20262.4 s
Sep 5, 20262.5 s
Sep 12, 20262.5 s
Sep 19, 20262.7 s
Sep 26, 20262.9 s
Oct 3, 20263.0 s
Oct 10, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
220 ms108 msApr 25Oct 10207 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026136 ms
May 2, 2026125 ms
May 9, 2026123 ms
May 16, 2026121 ms
May 23, 2026123 ms
May 30, 2026134 ms
Jun 6, 2026147 ms
Jun 13, 2026163 ms
Jun 20, 2026164 ms
Jun 27, 2026165 ms
Jul 4, 2026165 ms
Jul 11, 2026164 ms
Jul 18, 2026161 ms
Jul 25, 2026172 ms
Aug 1, 2026185 ms
Aug 8, 2026181 ms
Aug 15, 2026172 ms
Aug 22, 2026163 ms
Aug 29, 2026149 ms
Sep 5, 2026149 ms
Sep 12, 2026157 ms
Sep 19, 2026179 ms
Sep 26, 2026196 ms
Oct 3, 2026201 ms
Oct 10, 2026207 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 keyshot.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

1 to fix97
  • Use efficient cache lifetimes

    5.2 MB

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

  • Improve image delivery

    150 ms · 21 KiB

    1 image could be 21 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused CSS

    12 KiB

    About 12 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

3 checks passed
  • Mobile performance score: 97

    97/100

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

  • Main-thread work: 0.4 s

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

  • Server response: 58 ms

    58 ms

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

Core Web Vitals

7 to fix67
  • 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 INP: 235 ms

    235 ms

    Real visitors wait 235 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Tap response (INP) got 56% slower for real visitors

    +56%

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • Real-user TTFB: 1.6 s

    1.6 s

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

  • Largest Contentful Paint: 2.6 s

    2.6 s

    Your largest element takes 2.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • 1 image without width and height

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

8 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user CLS: 0.06

    0.06

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

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

    -58%

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

  • Time to Interactive: 2.6 s

    2.6 s

    The page is fully interactive after 2.6 s.

  • Cumulative Layout Shift: 0.04

    0.04

    The layout barely moves while loading (CLS 0.04, 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.

  • Speed Index: 1.1 s

    1.1 s

    Visually, the page fills in at 1.1 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

2 to fix64
  • Page weight: 6.7 MB in 68 requests

    6.7 MB

    Your homepage downloads 6.7 MB in 68 requests on a phone: media 5.2 MB (7), other files 1.1 MB (43) and fonts 241 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    keyshot-home-header-v2-sq-poster-opt.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 1.9 g of CO₂ per visit

    1.89 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.89 g of CO₂e: 227.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

9 to fixGoogle 7184
  • Certain ARIA roles must be contained by particular parents (16 elements)

    Certain ARIA roles must be contained by particular parents: 16 elements on the page fail this check, rated critical by axe-core.

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 37 text elements with low contrast

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

  • Interactive controls must not be nested (8 elements)

    Interactive controls must not be nested: 8 elements on the page fail this check, rated serious by axe-core.

  • 3 tap targets too small

    3 tap targets are too small or too close together to hit reliably with a finger.

  • 16 images without alt text

    16 images have no alt text, which hurts accessibility and image search.

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

    All page content should be contained by landmarks: 10 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.

  • 7 links without text

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

1 checks passed
  • 38 automated accessibility rules passed

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

SEO

2 to fixGoogle 9294
  • 2 H1 headlines

    There are 2 <h1> headlines (“The industry standard for 3D product visualization” and “The industry standard for 3D product visualization”). One clear main headline is easier for people and search engines.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 55 internal links, 12 external

    The homepage links to 55 pages on keyshot.com and 12 external pages.

7 checks passed
  • Meta description: 139 characters

    Your meta description is 139 characters: “KeyShot's cutting-edge real-time 3D rendering technology enables collaboration from concept to product launch for produ…”.

  • Title: 42 characters

    Your title is a healthy 42 characters: “3D Rendering and AI Visualization Software”.

  • Canonical URL set

    The canonical URL is https://www.keyshot.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, SoftwareApplication, WebPage and WebSite.

  • 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.keyshot.com/sitemap_index.xml.

AI search readiness

1 to fix83
  • Parts of the site are closed to 6 AI crawlers

    Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

3 checks passed
  • 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 (739 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.keyshot.com/llms.txt (10 KiB, 36 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 8 pages without a meta description

    https://www.keyshot.com/keyshot-dam, https://www.keyshot.com/keyshot-studio/network-rendering, https://www.keyshot.com/support, https://www.keyshot.com/partners, https://www.keyshot.com/keyshot-studio/plugins and https://www.keyshot.com/keyshot-dam/integration and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.keyshot.com/luminaries, whose canonical is https://www.keyshot.com/community. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 41 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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 to fixGoogle 9692
  • 2 JavaScript errors while loading

    2 errors were 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 fix92
  • 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 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 450 words of copy

    The homepage carries about 450 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Start free trial”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Pricing”, “Contact us” and “Free trial”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 14 customer or partner logos and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager and HubSpot.

Privacy and tracking

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

  • 1 other company contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 keyshot.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 Tag Manager

Company

Founded
2007

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on keyshot.com, including 8 speed issues, 2 SEO issues 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