Website review, no card needed
crockd.com website review
Visit site (opens in a new tab)Reviewed 9 November 202629 issues · 86 checks
This review found 29 issues worth fixing on crockd.com, 6 of them high impact, across 86 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
Site score
87B- #8,084 of 116,487 reviewed websitesbeats 90%
- #4,750 of 66,776 online storesbeats 89%
- #4,609 of 60,929 Shopify storesbeats 89%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.5 s |
| Nov 7, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 295 ms |
| May 30, 2026 | 295 ms |
| Jun 6, 2026 | 296 ms |
| Jun 13, 2026 | 293 ms |
| Jun 20, 2026 | 288 ms |
| Jun 27, 2026 | 284 ms |
| Jul 4, 2026 | 281 ms |
| Jul 11, 2026 | 288 ms |
| Jul 18, 2026 | 294 ms |
| Jul 25, 2026 | 299 ms |
| Aug 1, 2026 | 312 ms |
| Aug 8, 2026 | 308 ms |
| Aug 15, 2026 | 300 ms |
| Aug 22, 2026 | 304 ms |
| Aug 29, 2026 | 296 ms |
| Sep 5, 2026 | 295 ms |
| Sep 12, 2026 | 289 ms |
| Sep 19, 2026 | 279 ms |
| Sep 26, 2026 | 253 ms |
| Oct 3, 2026 | 238 ms |
| Oct 10, 2026 | 237 ms |
| Oct 17, 2026 | 229 ms |
| Oct 24, 2026 | 227 ms |
| Oct 31, 2026 | 223 ms |
| Nov 7, 2026 | 217 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
1.1 s
2.3 s
3.4 s
4.6 s
5.7 s
6.9 s
8.0 s
9.2 s
Speed
Render-blocking requests
6.7 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 6.7 s.
Improve image delivery
2.3 s · 703 KiB12 images could be 703 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.3 s faster on a phone.
Reduce unused JavaScript
150 ms · 916 KiBAbout 916 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Clarity and azurefd.net and others), adding 1.6 MB and 551 ms of main-thread time.
Shopify adds 177 ms
177 msShopify costs a phone 177 ms of main-thread work and 995 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: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,790 HTML elements
The page has 1,790 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
azurefd.net adds 70 ms
70 msazurefd.net costs a phone 70 ms of main-thread work and 321 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.
Use efficient cache lifetimes
239 KiB14 files are served with short cache lifetimes, so returning visitors download them again (239 KiB).
Reduce unused CSS
150 ms · 51 KiBAbout 51 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.
Minify JavaScript
150 ms · 9 KiB9 KiB could be saved by minifying JavaScript.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 82 ms. During a long task the page ignores taps.
Legacy JavaScript
48 KiBPolyfills for old browsers add 48 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.
1 checks passed
Server response: 39 ms
39 msYour server sent the HTML in 39 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.2 s
8.2 sYour largest element takes 8.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (4.5 s).
Speed Index: 10.7 s
10.7 sVisually, the page fills in at 10.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 12.5 s
12.5 sThe page becomes fully interactive after 12.5 s. Good is under 3.8 s.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 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.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 130 ms
130 msReal visitors wait 130 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.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 647 ms
647 msReal visitors wait 647 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 25% faster for real visitors
-25%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 295 ms to 217 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 26 ms
26 msScripts block the page for only 26 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.9 MB in 281 requests
3.9 MBYour homepage downloads 3.9 MB in 281 requests on a phone: scripts 1.4 MB (116), other files 1.2 MB (127) and images 1.1 MB (21). Under 2 MB keeps phones on slow connections fast.
6 images far larger than shown
418 KiB6 images are downloaded at several times the size a phone draws them, for example 194_2025-10-21_Crockd_1U0A9669.jpg at 1,200 px wide, shown at 171 px. Resized copies would save about 418 KiB.
About 1.1 g of CO₂ per visit
1.11 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.11 g of CO₂e: 133.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
31 text elements with low contrast
31 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
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).
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (5 elements).
2 checks passed
Every image has alt text
All 45 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 3 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 (161 characters)
Your meta description is 161 characters; Google truncates after about 160, so the end of your pitch is cut.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
One H1 headline
Your <h1> is empty.
83 internal links, 8 external
The homepage links to 83 pages on crockd.com and 8 external pages.
6 checks passed
Title: 62 characters
Your title is a healthy 62 characters: “Crockd Studios | Pottery Classes, Courses, Events and Supplies”.
Canonical URL set
The canonical URL is https://studios.crockd.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://studios.crockd.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 (940 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://studios.crockd.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a meta description
https://studios.crockd.com/collections/crockd-studios-manly-fairlight and https://studios.crockd.com/collections/crockd-studios-bondi use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://studios.crockd.com/pages/christmas-party-pottery and https://studios.crockd.com/pages/event-enquiry 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 37 found) and read each the way a search engine does.
6 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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 “Failed to load resource: the server responded with a status of 404 ()”.
2 checks passed
Tap targets are thumb-sized
19 of 21 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 927 words of copy
The homepage carries about 927 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Book your ornament class →”.
15 calls to action
The homepage has 15 calls to action, for example “Book Classes”, “Shop Supplies” and “Sydney — Join the Waitlist!”.
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: 1 testimonial or review block and “5000+ Reviews”.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 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.
20 cookies set on arrival
20Opening the homepage sets 20 cookies, 1 of them by other companies (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.
37 other companies contacted
Loading the homepage contacts 37 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 crockd.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 9 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Microsoft Clarity · Klaviyo Email Marketing Sms · Seguno Popups · Reputon Google Reviews Widget · Forms · Aiod Automatic Discounts · Freegifts · loox.io · rise-ai.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
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- New York
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on crockd.com, including 13 speed issues, 3 SEO issues 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.