Website review, no card needed
keebsforall.com website review
Visit site (opens in a new tab)Reviewed 9 November 202619 issues · 73 checks
This review found 19 issues worth fixing on keebsforall.com, 3 of them high impact, across 73 checks. The most urgent: 1 page without a title. 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
93A- #460 of 102,930 reviewed websitesbeats 99%
- #163 of 57,283 online storesbeats 99%
- #156 of 52,120 Shopify storesbeats 99%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.2 s |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 924 ms |
| Jun 13, 2026 | 892 ms |
| Jun 20, 2026 | 1.0 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 942 ms |
| Aug 1, 2026 | 944 ms |
| Aug 8, 2026 | 981 ms |
| Aug 15, 2026 | 1.0 s |
| Aug 22, 2026 | 1.0 s |
| Aug 29, 2026 | 1.0 s |
| Sep 5, 2026 | 977 ms |
| Sep 12, 2026 | 960 ms |
| Sep 19, 2026 | 970 ms |
| Sep 26, 2026 | 968 ms |
| Oct 3, 2026 | 950 ms |
| Oct 10, 2026 | 958 ms |
| Oct 17, 2026 | 933 ms |
| Oct 24, 2026 | 894 ms |
| Oct 31, 2026 | 902 ms |
| Nov 7, 2026 | 873 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 108 ms |
| May 30, 2026 | 99 ms |
| Jun 6, 2026 | 97 ms |
| Jun 13, 2026 | 95 ms |
| Jun 20, 2026 | 110 ms |
| Jun 27, 2026 | 162 ms |
| Jul 4, 2026 | 148 ms |
| Jul 11, 2026 | 138 ms |
| Jul 18, 2026 | 121 ms |
| Jul 25, 2026 | 93 ms |
| Aug 1, 2026 | 90 ms |
| Aug 8, 2026 | 94 ms |
| Aug 15, 2026 | 97 ms |
| Aug 22, 2026 | 97 ms |
| Aug 29, 2026 | 101 ms |
| Sep 5, 2026 | 96 ms |
| Sep 12, 2026 | 94 ms |
| Sep 19, 2026 | 96 ms |
| Sep 26, 2026 | 95 ms |
| Oct 3, 2026 | 99 ms |
| Oct 10, 2026 | 108 ms |
| Oct 17, 2026 | 111 ms |
| Oct 24, 2026 | 106 ms |
| Oct 31, 2026 | 104 ms |
| Nov 7, 2026 | 99 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
Reduce unused JavaScript
488 KiBAbout 488 KiB of JavaScript is downloaded but never used on this page.
rebuyengine.com adds 102 ms
102 msrebuyengine.com costs a phone 102 ms of main-thread work and 330 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 32 ms
32 msShopify costs a phone 32 ms of main-thread work and 325 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 (rebuyengine.com, Shopify and shiptection.com and others), adding 743 KiB and 155 ms of main-thread time.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 104 ms. During a long task the page ignores taps.
Improve image delivery
87 KiB3 images could be 87 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
25 KiB14 files are served with short cache lifetimes, so returning visitors download them again (25 KiB).
Legacy JavaScript
18 KiBPolyfills for old browsers add 18 KiB JavaScript that modern phones do not need.
Reduce unused CSS
18 KiBAbout 18 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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
3 checks passed
Mobile performance score: 97
97/100Your mobile performance score is 97. That is in Google's “good” band (90 and up).
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 365 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 8.4 s
8.4 sThe page becomes fully interactive after 8.4 s. Good is under 3.8 s.
Speed Index: 3.8 s
3.8 sVisually, the page fills in at 3.8 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 108 ms to 99 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
11 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: 0.7 s
0.7 sReal visitors wait 0.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 60 ms
60 msReal visitors wait 60 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.7 s
0.7 sReal visitors see the first content after 0.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 479 ms
479 msReal visitors wait 479 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 22% faster for real visitors
-22%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.2 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s, inside the 1.8 s “good” threshold.
Largest Contentful Paint: 1.8 s
1.8 sYour largest element renders in 1.8 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “PRECISION INPUT GEAR.”.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 27 ms
27 msScripts block the page for only 27 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.1 MB in 175 requests
2.1 MBYour homepage downloads 2.1 MB in 175 requests on a phone: other files 825 KiB (111), scripts 795 KiB (46) and images 413 KiB (7). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
74 KiB1 image is downloaded at several times the size a phone draws it, for example hero-bg.webp at 1,408 px wide, shown at 390 px. Resized copies would save about 74 KiB.
1 image in older formats
1 image (238 KiB) is 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.
About 0.6 g of CO₂ per visit
0.60 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.60 g of CO₂e: 71.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 7 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 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
Meta description is long (289 characters)
Your meta description is 289 characters; Google truncates after about 160, so the end of your pitch is cut.
53 internal links, 4 external
The homepage links to 53 pages on keebsforall.com and 4 external pages.
7 checks passed
One H1 headline
Your main headline reads: “PRECISIONINPUT GEAR.”.
Title: 37 characters
Your title is a healthy 37 characters: “KeebsForAll Mechanical Keyboard Store”.
Canonical URL set
The canonical URL is https://keebsforall.com/.
Structured data in place
Structured data found: Organization 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://keebsforall.com/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
2 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.
llms.txt published
The site publishes https://keebsforall.com/llms.txt (3 KiB, 23 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://keebsforall.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://keebsforall.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
3 pages without a meta description
https://keebsforall.com/customer_authentication/redirect, https://keebsforall.com/pages/collab and https://keebsforall.com/collections/all have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://keebsforall.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://keebsforall.com/pages/collab 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 31 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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.
Best practices
9 small tap targets
9 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Only about 132 words
The homepage has only about 132 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “[ START BUILD ]”.
4 calls to action
The homepage has 4 calls to action, for example “[ START BUILD ]” and “Contact”.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and 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.
14 cookies set on arrival
14Opening the homepage sets 14 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.
18 other companies contacted
Loading the homepage contacts 18 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 keebsforall.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 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Forms · shiptection.com · chimpstatic.com · cloudfront.net · rebuyengine.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
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Hosting
- Shopify
Company
- Headquarters
- Los Angeles
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 19 issues on keebsforall.com, including 5 speed issues, 1 SEO issue 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.