Website review, no card needed
kbsgolfshafts.com website review
Visit site (opens in a new tab)Reviewed 10 November 202639 issues · 86 checks
This review found 39 issues worth fixing on kbsgolfshafts.com, 13 of them high impact, across 86 checks. The most urgent: reduce unused JavaScript. 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
77C- #69,994 of 126,417 reviewed websitesbeats 39%
- #44,928 of 70,458 online storesbeats 31%
- #42,682 of 63,959 Shopify storesbeats 28%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 859 ms |
| May 30, 2026 | 868 ms |
| Jun 6, 2026 | 861 ms |
| Jun 13, 2026 | 874 ms |
| Jun 20, 2026 | 871 ms |
| Jun 27, 2026 | 894 ms |
| Jul 4, 2026 | 970 ms |
| Jul 11, 2026 | 1.0 s |
| Jul 18, 2026 | 1.1 s |
| Jul 25, 2026 | 1.1 s |
| Aug 1, 2026 | 1.1 s |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 1.0 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.0 s |
| Sep 26, 2026 | 1.0 s |
| Oct 3, 2026 | 1.0 s |
| Oct 10, 2026 | 1.0 s |
| Oct 17, 2026 | 1.0 s |
| Oct 24, 2026 | 1.0 s |
| Oct 31, 2026 | 1.0 s |
| Nov 7, 2026 | 1.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 80 ms |
| May 30, 2026 | 82 ms |
| Jun 6, 2026 | 84 ms |
| Jun 13, 2026 | 83 ms |
| Jun 20, 2026 | 84 ms |
| Jun 27, 2026 | 84 ms |
| Jul 4, 2026 | 83 ms |
| Jul 11, 2026 | 82 ms |
| Jul 18, 2026 | 82 ms |
| Jul 25, 2026 | 81 ms |
| Aug 1, 2026 | 80 ms |
| Aug 8, 2026 | 81 ms |
| Aug 15, 2026 | 80 ms |
| Aug 22, 2026 | 80 ms |
| Aug 29, 2026 | 80 ms |
| Sep 5, 2026 | 79 ms |
| Sep 12, 2026 | 79 ms |
| Sep 19, 2026 | 79 ms |
| Sep 26, 2026 | 79 ms |
| Oct 3, 2026 | 79 ms |
| Oct 10, 2026 | 79 ms |
| Oct 17, 2026 | 79 ms |
| Oct 24, 2026 | 79 ms |
| Oct 31, 2026 | 79 ms |
| Nov 7, 2026 | 79 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.9 s
1.7 s
2.6 s
3.5 s
4.4 s
5.2 s
6.1 s
7.0 s
Speed
Reduce unused JavaScript
1.4 s · 489 KiBAbout 489 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Mobile performance score: 34
34/100Your mobile performance score is 34. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.4 s
A phone's processor spends 4.4 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
150 ms · 1.6 MB8 images could be 1.6 MB 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.
Render-blocking requests
950 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
8 third-party services on the page
8 third-party services load with your homepage (Accessibe Accessibility Overlay, Klaviyo and kayako.com and others), adding 1.2 MB and 739 ms of main-thread time.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 286 ms. During a long task the page ignores taps.
Klaviyo adds 202 ms
202 msKlaviyo costs a phone 202 ms of main-thread work and 323 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.
kayako.com adds 172 ms
172 mskayako.com costs a phone 172 ms of main-thread work and 339 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.
1,850 HTML elements
The page has 1,850 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
150 ms · 23 KiBAbout 23 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
100 ms · 30 KiBPolyfills for old browsers add 30 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Use efficient cache lifetimes
14 KiB8 files are served with short cache lifetimes, so returning visitors download them again (14 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.
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: 9 ms
9 msYour server sent the HTML in 9 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 13.1 s
13.1 sYour largest element takes 13.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 20.2 s
20.2 sThe page becomes fully interactive after 20.2 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.862
0.862The layout shifts by 0.862 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 8.4 s
8.4 sVisually, the page fills in at 8.4 s (Speed Index). Good is under 3.4 s.
97 images without width and height
97 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 385 ms
385 msScripts block taps and scrolling for 385 ms in total while the page loads. Good is under 200 ms.
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 80 ms to 79 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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: 1.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 84 ms
84 msReal visitors wait 84 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.6 s
0.6 sReal visitors see the first content after 0.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 316 ms
316 msReal visitors wait 316 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 5.1 MB in 252 requests
5.1 MBYour homepage downloads 5.1 MB in 252 requests on a phone: images 2.7 MB (50), scripts 1.3 MB (79) and other files 765 KiB (102). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
8ab6aafc02fc3d5fb6da2b5aba7357c9.png weighs 1.6 MB. On a phone connection a single image that size takes seconds.
1 image far larger than shown
1.5 MB1 image is downloaded at several times the size a phone draws it, for example 8ab6aafc02fc3d5fb6da2b5aba7357c9.png at 4,096 px wide, shown at 390 px. Resized copies would save about 1.5 MB.
2 images below the first screen load straight away
2 images further down the page (1.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
An image on the first screen is lazy-loaded
hdr_tgblack_pre_m.jpg 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.4 g of CO₂ per visit
1.43 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.43 g of CO₂e: 171.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
109 images without alt text
109 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Elements with role="dialog" or role="alertdialog" do not have accessible names.
Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
1 checks passed
47 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: 47 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (15 characters)
Your title is only 15 characters: “KBS Golf Shafts”. Between 30 and 65 characters leaves room to say what you do and for whom.
154 internal links, 26 external
The homepage links to 154 pages on kbsgolfshafts.com and 26 external pages.
7 checks passed
Meta description: 111 characters
Your meta description is 111 characters: “KBS Golf Shafts is a premium golf shafts manufacturer of steel and graphite shafts. Player Driven. Tour Proven.”.
One H1 headline
Your main headline reads: “KBS Golf Shafts”.
Canonical URL set
The canonical URL is https://kbsgolfshafts.com/.
Structured data in place
Structured data found: BreadcrumbList, FAQPage, 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://kbsgolfshafts.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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,010 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://kbsgolfshafts.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://kbsgolfshafts.com/collections/pro is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://kbsgolfshafts.com/collections/pro has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://kbsgolfshafts.com/collections/pro has 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 67 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.
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.
Every page has a title
All 1 page that loaded have a <title>.
Best practices
13 small tap targets
13 of 29 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
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 348 words of copy
The homepage carries about 348 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP TOUR V-X”.
11 calls to action
The homepage has 11 calls to action, for example “Subscribe”, “SHOP TOUR V-X” and “RESERVE YOUR SPOT”.
3 short forms
3 short forms (1 field at most) are right on the homepage, asking for an email.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Klaviyo (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.
10 cookies set on arrival
10Opening the homepage sets 10 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 kbsgolfshafts.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 4 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Kaching Bundles · Gsc Countdown Timer · Selleasy
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 39 issues on kbsgolfshafts.com, including 16 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.