Website review, no card needed
vicfirth.com website review
Visit site (opens in a new tab)Reviewed 5 November 202630 issues · 79 checks
This review found 30 issues worth fixing on vicfirth.com, 8 of them high impact, across 79 checks. The most urgent: improve image delivery. 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
85B- #13,482 of 97,881 reviewed websitesbeats 82%
- #8,283 of 53,367 online storesbeats 79%
- #8,045 of 48,397 Shopify storesbeats 78%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.7 s |
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 130 ms |
| May 23, 2026 | 128 ms |
| May 30, 2026 | 127 ms |
| Jun 6, 2026 | 129 ms |
| Jun 13, 2026 | 129 ms |
| Jun 20, 2026 | 131 ms |
| Jun 27, 2026 | 136 ms |
| Jul 4, 2026 | 139 ms |
| Jul 11, 2026 | 141 ms |
| Jul 18, 2026 | 137 ms |
| Jul 25, 2026 | 136 ms |
| Aug 1, 2026 | 135 ms |
| Aug 8, 2026 | 136 ms |
| Aug 15, 2026 | 136 ms |
| Aug 22, 2026 | 130 ms |
| Aug 29, 2026 | 128 ms |
| Sep 5, 2026 | 129 ms |
| Sep 12, 2026 | 134 ms |
| Sep 19, 2026 | 137 ms |
| Sep 26, 2026 | 138 ms |
| Oct 3, 2026 | 138 ms |
| Oct 10, 2026 | 138 ms |
| Oct 17, 2026 | 138 ms |
| Oct 24, 2026 | 138 ms |
| Oct 31, 2026 | 138 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
Speed
Improve image delivery
1.1 s · 410 KiB14 images could be 410 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.
Render-blocking requests
1.6 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Klaviyo and others), adding 2.0 MB and 968 ms of main-thread time.
Mobile performance score: 58
58/100Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
300 ms · 458 KiB15 files are served with short cache lifetimes, so returning visitors download them again (458 KiB).
Reduce unused JavaScript
745 KiBAbout 745 KiB of JavaScript is downloaded but never used on this page.
Google Tag Manager adds 401 ms
401 msGoogle Tag Manager costs a phone 401 ms of main-thread work and 652 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.
Main-thread work: 3.2 s
A phone's processor spends 3.2 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,959 HTML elements
The page has 2,959 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 104 ms
104 msKlaviyo costs a phone 104 ms of main-thread work and 308 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 42 ms
42 msShopify costs a phone 42 ms of main-thread work and 341 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
150 ms · 46 KiBAbout 46 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.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 162 ms. During a long task the page ignores taps.
Legacy JavaScript
38 KiBPolyfills for old browsers add 38 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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 19 ms
19 msYour server sent the HTML in 19 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 25.8 s
25.8 sThe page becomes fully interactive after 25.8 s. Good is under 3.8 s.
Largest Contentful Paint: 8.9 s
8.9 sYour largest element takes 8.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 6.8 s
6.8 sVisually, the page fills in at 6.8 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 380 ms
380 msScripts block taps and scrolling for 380 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 130 ms to 138 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.7 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: 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: 167 ms
167 msReal visitors wait 167 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: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 611 ms
611 msReal visitors wait 611 ms for your server to start answering (75th percentile). Good is under 800 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.9 MB in 297 requests
4.9 MBYour homepage downloads 4.9 MB in 297 requests on a phone: scripts 2.1 MB (99), images 1.5 MB (40) and other files 853 KiB (103). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Vic_Holiday_2026_Holiday_Campaign_Template_revised_Homepage_ 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).
3 images far larger than shown
68 KiB3 images are downloaded at several times the size a phone draws them, for example Heavy-Hitter-Promo-Block-Horizontal.jpg at 1,256 px wide, shown at 350 px. Resized copies would save about 68 KiB.
1 image in older formats
1 image (108 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.
5 images below the first screen load straight away
5 images further down the page (146 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.4 g of CO₂ per visit
1.38 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.38 g of CO₂e: 165.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
2 checks passed
Every image has alt text
All 132 images in the HTML carry an alt attribute.
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 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
Title is long (67 characters)
Your title is 67 characters, so Google will cut it off around 60: “Vic Firth | Official Site | Drumsticks, Mallets and Branded Apparel”.
4 H1 headlines
There are 4 <h1> headlines (“”, “Heavy Hitter - Power Your Practice” and “Corpsmaster Iain Moyer Keyboard Series”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
15 links crawlers can't follow
15 links have no real href, so search engines can't follow them.
226 internal links, 15 external
The homepage links to 226 pages on vicfirth.com and 15 external pages.
5 checks passed
Meta description: 103 characters
Your meta description is 103 characters: “Shop the official Vic Firth online store, featuring drumsticks, percussion mallets and branded apparel.”.
Canonical URL set
The canonical URL is https://vicfirth.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://vicfirth.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, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,352 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://vicfirth.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 pages without a meta description
https://vicfirth.com/collections/all, https://vicfirth.com/collections/vic-firth-category-sticks-drum-set, https://vicfirth.com/collections/vic-firth-category-sticks-drum-set-american-classic, https://vicfirth.com/collections/vic-firth-category-sticks-drum-set-american-heritage, https://vicfirth.com/collections/vic-firth-category-sticks-drum-set-american-jazz and https://vicfirth.com/collections/vic-firth-category-sticks-drum-set-american-sound and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://vicfirth.com/collections/all, https://vicfirth.com/collections/vic-firth-category-sticks-drum-set, https://vicfirth.com/collections/vic-firth-category-sticks-drum-set-american-classic, https://vicfirth.com/collections/vic-firth-category-sticks-drum-set-american-heritage, https://vicfirth.com/collections/vic-firth-category-sticks-drum-set-american-jazz and https://vicfirth.com/collections/vic-firth-category-sticks-drum-set-american-sound and 9 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 109 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.
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.
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 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Shopify's Google Analytics stub called with: [array Array] See https://help.shopify.com/manual/promoting-marketing/pixe…”.
2 checks passed
Tap targets are thumb-sized
49 of 57 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 588 words of copy
The homepage carries about 588 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: “Learn more” and “Subscribe Now”.
2 calls to action
The homepage has 2 calls to action, for example “Join Now” and “CONTACT US”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 25 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Microsoft Clarity.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 mores (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.
25 cookies set on arrival
25Opening the homepage sets 25 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.
40 other companies contacted
Loading the homepage contacts 40 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 vicfirth.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
Pandectes Gdpr · Judge Me Reviews · Hulk Form Builder · Boost Ai Search Filter · Klaviyo Email Marketing Sms · Gdpr Cookie Consent · yotpo.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
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Shopify
Hiring
- Hiring
- 2 open roles
- Job board
- adp
Company
- Employees
- 25
- Founded
- 1963
- Headquarters
- Boston
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 vicfirth.com, including 16 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.