Website review, no card needed
croccrusher.com website review
Visit site (opens in a new tab)Reviewed 16 November 202621 issues · 71 checks
This review found 21 issues worth fixing on croccrusher.com, 8 of them high impact, across 71 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
One score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.3 s
1.7 s
2.1 s
2.5 s
3.0 s
3.4 s
Speed
Render-blocking requests
1.2 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
Mobile performance score: 56
56/100Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.
Shopify adds 42 ms
42 msShopify costs a phone 42 ms of main-thread work and 467 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.
6 third-party services on the page
6 third-party services load with your homepage (Cloudflare CDN, Shopify and Bootstrap CDN and others), adding 565 KiB and 112 ms of main-thread time.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Reduce unused CSS
24 KiBAbout 24 KiB of CSS is downloaded but never applied on this page.
Improve image delivery
22 KiB4 images could be 22 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
Use efficient cache lifetimes
2 KiB1 file is served with short cache lifetimes, so returning visitors download them again (2 KiB).
2 checks passed
Main-thread work: 0.8 s
A phone's processor spends 0.8 s on main-thread work while loading, 230 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
Cumulative Layout Shift: 1.669
1.669The layout shifts by 1.669 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest Contentful Paint: 5.0 s
5.0 sYour largest element takes 5.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
50 images without width and height
50 images have no width and height attributes, so the layout jumps as each one loads.
Time to Interactive: 5.1 s
5.1 sThe page becomes fully interactive after 5.1 s. Good is under 3.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.3 s
3.3 sVisually, the page fills in at 3.3 s (Speed Index), inside the 3.4 s “good” threshold.
First Contentful Paint: 0.9 s
0.9 sThe first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
2 images below the first screen load straight away
2 images further down the page (40 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.6 g of CO₂ per visit
0.56 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.56 g of CO₂e: 67.2 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: 2.0 MB in 177 requests
2.0 MBYour homepage downloads 2.0 MB in 177 requests on a phone: images 903 KiB (51), other files 661 KiB (68) and scripts 236 KiB (36). 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
Orphan list items
Some list items are not inside a list.
13 text elements with low contrast
13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
4 elements hidden from screen readers can still receive keyboard focus.
49 images without alt text
49 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h1 → h3 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).
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 7 failed. 3 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 “Premium Herb Grinders”). One clear main headline is easier for people and search engines.
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.
56 internal links, 0 external
The homepage links to 56 pages on croccrusher.com and 0 external pages.
7 checks passed
Meta description: 74 characters
Your meta description is 74 characters: “Retail and wholesale supplier or premium herb grinders and pollen presses.”.
Title: 59 characters
Your title is a healthy 59 characters: “Premium Herb Grinders - Croc Crusher - Smoke Shop Wholesale”.
Canonical URL set
The canonical URL is https://www.croccrusher.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://www.croccrusher.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.croccrusher.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
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.
Text is in the HTML
Your server sends the page's text in the HTML (583 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://www.croccrusher.com/collections/1-2-inch has no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 18 found) and read each the way a search engine does.
6 checks passed
Linked pages load
2 pages of 15 loaded without an error (the rest turned automated requests away).
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 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 2 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of null (reading 'add')”.
4 low-resolution images
4 images are served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
48 of 50 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.
Thin social proof
Social proof on the homepage: 13 testimonial or review blocks. 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 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 526 words of copy
The homepage carries about 526 words of visible text.
2 checks passed
4 calls to action
The homepage has 4 calls to action, for example “LEARN MORE”, “Contact Us” and “SIGN UP”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Privacy and tracking
5 cookies set on arrival
5Opening the homepage sets 5 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.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 croccrusher.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 21 issues on croccrusher.com, including 7 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.