Programmable

Website review, no card needed

keefigures.com logo

keefigures.com website review

Visit site (opens in a new tab)Reviewed 11 November 202623 issues · 63 checks

This review found 23 issues worth fixing on keefigures.com, 8 of them high impact, across 63 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

Site score

80B

Closest competitors among Shopify stores

Compare side by side

One score from every part of this review. How it works

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

How it loaded on a phone

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

Speed

4 to fix75

  • Reduce unused JavaScript

    1.8 s · 318 KiB

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

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 75

    75/100

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

  • Shopify adds 103 ms

    103 ms

    Shopify costs a phone 103 ms of main-thread work and 528 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.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Shopify, Google CDN and Judge.me and others), adding 564 KiB and 120 ms of main-thread time.

  • 3 long tasks on the main thread

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

  • Use efficient cache lifetimes

    5 KiB

    3 files are served with short cache lifetimes, so returning visitors download them again (5 KiB).

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

2 checks passed

  • Main-thread work: 1.3 s

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

  • Server response: 8 ms

    8 ms

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

Core Web Vitals

3 to fix69

  • Largest Contentful Paint: 6.7 s

    6.7 s

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

  • Time to Interactive: 7.3 s

    7.3 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

    The first text or image appears after 2.0 s on a phone. Good is under 1.8 s.

  • 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

  • Speed Index: 3.0 s

    3.0 s

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

  • Total Blocking Time: 85 ms

    85 ms

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

  • Cumulative Layout Shift: 0.007

    0.007

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

Images and page weight

1 to fix97

  • An image on the first screen is lazy-loaded

    banner.png 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 0.5 g of CO₂ per visit

    0.51 g

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

3 checks passed

  • Page weight: 1.8 MB in 219 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 219 requests on a phone: other files 936 KiB (143), scripts 674 KiB (44) and images 113 KiB (5). That is a lean page.

  • 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

2 to fixGoogle 9796

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

2 checks passed

  • Every image has alt text

    All 5 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

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

SEO

4 to fixGoogle 10083

  • Title is short (10 characters)

    Your title is only 10 characters: “keefigures”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No favicon declared

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

  • One H1 headline

    Your <h1> is empty.

  • 18 internal links, 7 external

    The homepage links to 18 pages on keefigures.com and 7 external pages.

5 checks passed

  • Meta description: 139 characters

    Your meta description is 139 characters: “Keefigures designs, manufactures and distributes small batch keycaps drawing inspiration from anime, tech, fashion, as …”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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.keefigures.com/sitemap.xml.

AI search readiness

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

  • llms.txt published

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

Other pages

3 to fix78

  • 1 page points its canonical at the homepage

    https://www.keefigures.com/products/1pc-cartoon-personality-tail-gaming-keycap-elves-keycaps-festival-gift-for-cherry-mx-mechanical-keyboard-key-cap-41405 declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://www.keefigures.com/products/1pc-cartoon-personality-tail-gaming-keycap-elves-keycaps-festival-gift-for-cherry-mx-mechanical-keyboard-key-cap-41405 all use the title “keefigures”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://www.keefigures.com/collections/all, https://www.keefigures.com/pages/contact, https://www.keefigures.com/policies/terms-of-service, https://www.keefigures.com/policies/privacy-policy and https://www.keefigures.com/policies/refund-policy have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages with very little text

    https://www.keefigures.com/pages/contact and https://www.keefigures.com/policies/refund-policy 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.

4 checks passed

  • Linked pages load

    All 10 pages we checked loaded without an error.

  • 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

1 to fixGoogle 10093

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

2 checks passed

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64

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

  • Only about 123 words

    The homepage has only about 123 words of visible text; thin pages give Google and first-time buyers little to go on.

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

3 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Shop”, “SHOP NOW” and “Contact”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

Privacy and tracking

1 to fix

  • 1 tracker load before any consent

    1

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

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 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 keefigures.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 2 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Judge Me Reviews · Forms

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

Framework
jQuery
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 23 issues on keefigures.com, including 7 speed issues, 4 SEO issues and 4 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