Website review, no card needed
kaisercatcinema.com website review
Visit site (opens in a new tab)Reviewed 12 November 202630 issues · 85 checks
This review found 30 issues worth fixing on kaisercatcinema.com, 9 of them high impact, across 85 checks. The most urgent: render-blocking requests. 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
87B- #7,648 of 109,350 reviewed websitesbeats 90%
- #4,460 of 61,859 online storesbeats 89%
- #4,330 of 56,401 Shopify storesbeats 89%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.4 s |
| Nov 7, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 94 ms |
| May 30, 2026 | 98 ms |
| Jun 6, 2026 | 95 ms |
| Jun 13, 2026 | 95 ms |
| Jun 20, 2026 | 93 ms |
| Jun 27, 2026 | 86 ms |
| Jul 4, 2026 | 83 ms |
| Jul 11, 2026 | 84 ms |
| Jul 18, 2026 | 86 ms |
| Jul 25, 2026 | 89 ms |
| Aug 1, 2026 | 100 ms |
| Aug 8, 2026 | 103 ms |
| Aug 15, 2026 | 99 ms |
| Aug 22, 2026 | 89 ms |
| Aug 29, 2026 | 88 ms |
| Sep 5, 2026 | 89 ms |
| Sep 12, 2026 | 94 ms |
| Sep 19, 2026 | 96 ms |
| Sep 26, 2026 | 104 ms |
| Oct 3, 2026 | 102 ms |
| Oct 10, 2026 | 97 ms |
| Oct 17, 2026 | 102 ms |
| Oct 24, 2026 | 96 ms |
| Oct 31, 2026 | 96 ms |
| Nov 7, 2026 | 96 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
Render-blocking requests
1.0 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.
6,732 HTML elements
The page has 6,732 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 4.0 s
A phone's processor spends 4.0 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 83
83/100Your mobile performance score is 83. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
550 ms · 385 KiB12 images could be 385 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 550 ms faster on a phone.
Reduce unused JavaScript
805 KiBAbout 805 KiB of JavaScript is downloaded but never used on this page.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Shopify and Other Google APIs/SDKs and others), adding 1.8 MB and 512 ms of main-thread time.
YouTube adds 336 ms
336 msYouTube costs a phone 336 ms of main-thread work and 1,014 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.
Shopify adds 169 ms
169 msShopify costs a phone 169 ms of main-thread work and 803 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.
Reduce unused CSS
280 ms · 139 KiBAbout 139 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 280 ms faster on a phone.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 112 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
17 KiB9 files are served with short cache lifetimes, so returning visitors download them again (17 KiB).
Minify JavaScript
9 KiB9 KiB could be saved by minifying JavaScript.
Legacy JavaScript
7 KiBPolyfills for old browsers add 7 KiB JavaScript that modern phones do not need.
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: 76 ms
76 msYour server sent the HTML in 76 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 17.8 s
17.8 sThe page becomes fully interactive after 17.8 s. Good is under 3.8 s.
Largest Contentful Paint: 4.2 s
4.2 sYour largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 4.4 s
4.4 sVisually, the page fills in at 4.4 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 94 ms to 96 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
10 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.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 180 ms
180 msReal visitors wait 180 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 717 ms
717 msReal visitors wait 717 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 85 ms
85 msScripts block the page for only 85 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.5 MB in 201 requests
4.5 MBYour homepage downloads 4.5 MB in 201 requests on a phone: images 1.6 MB (30), scripts 1.5 MB (74) and other files 806 KiB (77). Under 2 MB keeps phones on slow connections fast.
About 1.3 g of CO₂ per visit
1.27 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.27 g of CO₂e: 152.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 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.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
8 text elements with low contrast
8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 94 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“” and “”). One clear main headline is easier for people and search engines.
Meta description is long (234 characters)
Your meta description is 234 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (Organization, Person, WebPage and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://vincentdenil.com/)”.
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.
106 internal links, 21 external
The homepage links to 106 pages on kaisercatcinema.com and 21 external pages.
5 checks passed
Title: 46 characters
Your title is a healthy 46 characters: “Kaiser Cat Cinema ~ the Alt-History Collective”.
Canonical URL set
The canonical URL is https://kaisercatcinema.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://kaisercatcinema.com/sitemap.xml.
AI search readiness
4 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, sameAs (social profiles) and description; logo and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (3,604 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://kaisercatcinema.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://kaisercatcinema.com/pages/about and https://kaisercatcinema.com/about all use the title “About Kaiser Cat Cinema - The Alt-History Collective”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://kaisercatcinema.com/pages/about and https://kaisercatcinema.com/about use the same meta description. A description written for each page earns more clicks.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://kaisercatcinema.com/connect, whose canonical is https://kaisercatcinema.com/pages/connect. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
11 pages without an H1
https://kaisercatcinema.com/pages/patreon-programme, https://kaisercatcinema.com/pages/about, https://kaisercatcinema.com/connect, https://kaisercatcinema.com/about, https://kaisercatcinema.com/products/go-over-the-top-with-us-army-modernized-propaganda-poster and https://kaisercatcinema.com/products/medieval-american-museum-poster-manhattan-castle-exhibition and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 47 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“CSS appearance value `slider-vertical` is not standardized and will be removed.”).
2 low-resolution images
2 images are served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
37 of 38 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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 1,635 words of copy
The homepage carries about 1,635 words of visible text.
3 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Contact”, “Register / Login” and “Sign up”.
18 short forms
18 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 215 testimonial or review blocks and 2 trust badges.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 1 more (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.
12 cookies set on arrival
12Opening the homepage sets 12 cookies, 1 of them by other companies (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.
24 other companies contacted
Loading the homepage contacts 24 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 kaisercatcinema.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Ymq B2b Login Lock Hide Price · Judge Me Reviews · Pagefly Ai Page Builder · Avada Upsell · b-cdn.net · makeprosimp.com · printful.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on kaisercatcinema.com, including 12 speed issues, 4 SEO issues and 3 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.