Website review, no card needed

claritycrafts.com logo

claritycrafts.com website review

Visit site (opens in a new tab)Reviewed 9 November 202640 issues · 87 checks

This review found 40 issues worth fixing on claritycrafts.com, 12 of them high impact, across 87 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.4 s1.1 sMay 23Nov 71.1 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.2 s
May 30, 20261.2 s
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.3 s
Jul 18, 20261.3 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.4 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.2 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Oct 24, 20261.1 s
Oct 31, 20261.2 s
Nov 7, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
125 ms105 msMay 23Nov 7111 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026111 ms
May 30, 2026113 ms
Jun 6, 2026112 ms
Jun 13, 2026118 ms
Jun 20, 2026119 ms
Jun 27, 2026118 ms
Jul 4, 2026120 ms
Jul 11, 2026123 ms
Jul 18, 2026120 ms
Jul 25, 2026121 ms
Aug 1, 2026121 ms
Aug 8, 2026119 ms
Aug 15, 2026120 ms
Aug 22, 2026120 ms
Aug 29, 2026120 ms
Sep 5, 2026116 ms
Sep 12, 2026113 ms
Sep 19, 2026112 ms
Sep 26, 2026111 ms
Oct 3, 2026110 ms
Oct 10, 2026108 ms
Oct 17, 2026107 ms
Oct 24, 2026109 ms
Oct 31, 2026110 ms
Nov 7, 2026111 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

Full-page screenshot of claritycrafts.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. claritycrafts.com at 0.4 s0.4 s
  2. claritycrafts.com at 0.8 s0.8 s
  3. claritycrafts.com at 1.2 s1.2 s
  4. claritycrafts.com at 1.6 s1.6 s
  5. claritycrafts.com at 2.0 s2.0 s
  6. claritycrafts.com at 2.4 s2.4 s
  7. claritycrafts.com at 2.8 s2.8 s
  8. claritycrafts.com at 3.2 s3.2 s

Speed

14 to fix45
  • Reduce unused JavaScript

    3.3 s · 1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.3 s faster on a phone.

  • Improve image delivery

    1.9 s · 860 KiB

    32 images could be 860 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.

  • Mobile performance score: 45

    45/100

    Your mobile performance score is 45. 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, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 3,495 HTML elements

    The page has 3,495 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Yotpo and zotabox.com and others), adding 3.3 MB and 1.2 s of main-thread time.

  • Minify JavaScript

    760 ms · 54 KiB

    54 KiB could be saved by minifying JavaScript.

  • Shopify adds 415 ms

    415 ms

    Shopify costs a phone 415 ms of main-thread work and 1.2 MB 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.

  • Render-blocking requests

    450 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

  • Use efficient cache lifetimes

    150 ms · 293 KiB

    14 files are served with short cache lifetimes, so returning visitors download them again (293 KiB).

  • Yotpo adds 265 ms

    265 ms

    Yotpo costs a phone 265 ms of main-thread work and 396 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.

  • zotabox.com adds 179 ms

    179 ms

    zotabox.com costs a phone 179 ms of main-thread work and 548 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.

  • Klaviyo adds 159 ms

    159 ms

    Klaviyo costs a phone 159 ms of main-thread work and 310 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.

  • rechargecdn.com adds 89 ms

    89 ms

    rechargecdn.com costs a phone 89 ms of main-thread work and 296 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.

  • Legacy JavaScript

    250 ms · 25 KiB

    Polyfills for old browsers add 25 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.

  • 11 long tasks on the main thread

    11 long tasks block the main thread while loading, the longest for 187 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    130 KiB

    About 130 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 CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 79 ms

    79 ms

    Your server sent the HTML in 79 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 38.9 s

    38.9 s

    Your largest element takes 38.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “With regular updates for our USA customers... To hear from …”.

  • Time to Interactive: 41.3 s

    41.3 s

    The page becomes fully interactive after 41.3 s. Good is under 3.8 s.

  • Cumulative Layout Shift: 0.387

    0.387

    The layout shifts by 0.387 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Speed Index: 6.7 s

    6.7 s

    Visually, the page fills in at 6.7 s (Speed Index). Good is under 3.4 s.

  • 30 images without width and height

    30 images have no width and height attributes, so the layout jumps as each one loads.

  • Total Blocking Time: 261 ms

    261 ms

    Scripts block taps and scrolling for 261 ms in total while the page loads. Good is under 200 ms.

  • Tap response (INP) held steady for real visitors

    -1%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 111 ms to 111 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -3%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.1 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.6 s

    1.6 s

    Real visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 150 ms

    150 ms

    Real visitors wait 150 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.06

    0.06

    For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.0 s

    1.0 s

    Real visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 466 ms

    466 ms

    Real visitors wait 466 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

Images and page weight

4 to fix42
  • Page weight: 9.7 MB in 485 requests

    9.7 MB

    Your homepage downloads 9.7 MB in 485 requests on a phone: scripts 4.6 MB (181), images 2.0 MB (50) and other files 1.8 MB (180). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Felt_by_Clarity_Logo_Button_800x.png 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).

  • 8 images in older formats

    8 images (888 KiB) are 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.

  • 6 images far larger than shown

    471 KiB

    6 images are downloaded at several times the size a phone draws them, for example homepage_image-STAMPS_800x.webp at 800 px wide, shown at 167 px. Resized copies would save about 471 KiB.

  • About 2.7 g of CO₂ per visit

    2.74 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.74 g of CO₂e: 328.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

5 to fixGoogle 9194
  • 21 text elements with low contrast

    21 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Frames without titles

    2 frames have no title, so screen-reader users cannot tell what they contain.

  • All page content should be contained by landmarks (3 elements)

    All page content should be contained by landmarks: 3 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.

  • Alternative text of images should not be repeated as text (6 elements)

    Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 42 images in the HTML carry an alt attribute.

  • 52 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 5 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9288
  • Meta description is long (174 characters)

    Your meta description is 174 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.

  • 582 internal links, 16 external

    The homepage links to 582 pages on claritycrafts.com and 16 external pages.

6 checks passed
  • Title: 54 characters

    Your title is a healthy 54 characters: “Claritystamp | The Home of Papercraft – Clarity Crafts”.

  • Canonical URL set

    The canonical URL is https://claritycrafts.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://claritycrafts.com/sitemap.xml.

AI search readiness

100
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,371 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://claritycrafts.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix88
  • 4 pages without a meta description

    https://claritycrafts.com/collections/all-stamps, https://claritycrafts.com/collections/claritystamps, https://claritycrafts.com/collections/miniature-stamps and https://claritycrafts.com/collections/timestamp-creations have no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages share a meta description

    https://claritycrafts.com/collections/stamps/theme_kiss, https://claritycrafts.com/collections/stamps/theme_two-way-overlay, https://claritycrafts.com/collections/stamps/size_a4, https://claritycrafts.com/collections/stamps/size_a4-square, https://claritycrafts.com/collections/stamps/size_a5 and https://claritycrafts.com/collections/stamps/size_a5-square and 2 others use the same meta description. A description written for each page earns more clicks.

  • 15 pages without an H1

    https://claritycrafts.com/collections/all-stamps, https://claritycrafts.com/collections/claritystamps, https://claritycrafts.com/collections/mixed-impressions-texture-stamps, https://claritycrafts.com/collections/stamps/theme_kiss, https://claritycrafts.com/collections/word-chains and https://claritycrafts.com/collections/wee-stamps 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 199 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

2 to fixGoogle 7791
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn-gallery.xotiny.com/clarity-test-site-01/xo-gallery-main.css?v=1793362210777' f…”.

2 checks passed
  • Tap targets are thumb-sized

    38 of 46 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • 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 803 words of copy

    The homepage carries about 803 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: “Subscribe”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Clarity TV Shop”, “Contact Us” and “Contact information”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 7 testimonial or review blocks and a star rating.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before 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.

  • 26 cookies set on arrival

    26

    Opening the homepage sets 26 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.

  • 42 other companies contacted

    Loading the homepage contacts 42 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 claritycrafts.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 12 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Pagefly Ai Page Builder · Judge Me Reviews · Yotpo Loyalty Rewards · Xo Gallery · Klaviyo Email Marketing Sms · Swym Wishlist Plus · Codemate Product Custom Fields · zotabox.com · aura-apps.com · tidio.co · rechargecdn.com · hextom.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

E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
Edenbridge

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on claritycrafts.com, including 20 speed issues, 3 SEO issues 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25