Website review, no card needed

littlewordsproject.com logo

littlewordsproject.com website review

Visit site (opens in a new tab)Reviewed 6 November 202623 issues · 61 checks

This review found 23 issues worth fixing on littlewordsproject.com, 7 of them high impact, across 61 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
2.0 s1.7 sMay 16Oct 311.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.7 s
May 23, 20261.8 s
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.7 s
Jun 20, 20261.8 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.9 s
Oct 24, 20261.8 s
Oct 31, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
305 ms236 msMay 16Oct 31254 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026261 ms
May 23, 2026270 ms
May 30, 2026281 ms
Jun 6, 2026294 ms
Jun 13, 2026297 ms
Jun 20, 2026295 ms
Jun 27, 2026288 ms
Jul 4, 2026284 ms
Jul 11, 2026272 ms
Jul 18, 2026272 ms
Jul 25, 2026271 ms
Aug 1, 2026285 ms
Aug 8, 2026291 ms
Aug 15, 2026294 ms
Aug 22, 2026289 ms
Aug 29, 2026279 ms
Sep 5, 2026275 ms
Sep 12, 2026269 ms
Sep 19, 2026263 ms
Sep 26, 2026258 ms
Oct 3, 2026246 ms
Oct 10, 2026244 ms
Oct 17, 2026245 ms
Oct 24, 2026249 ms
Oct 31, 2026254 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

No screenshot is available for this review.

Speed

Not measured in this review.

Core Web Vitals

3 to fix33
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user INP: 254 ms

    254 ms

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

  • Real-user CLS: 0.12

    0.12

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

  • Tap response (INP) held steady for real visitors

    -5%

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

  • Largest content (LCP) held steady for real visitors

    +4%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 542 ms

    542 ms

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

Images and page weight

3 to fix50
  • Page weight: 8.3 MB

    8.3 MB

    Your homepage downloads 8.3 MB on a phone, 3.5 MB of it images (42%). Under 2 MB keeps phones on slow connections fast.

  • 23 images in older formats

    23 images (1.9 MB) 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.

  • 1 image far larger than shown

    13 KiB

    1 image is downloaded at several times the size a phone draws it, for example GOLD_PLATED-2_750x750.webp at 750 px wide, shown at 218 px. Resized copies would save about 13 KiB.

  • 2 images below the first screen load straight away

    2 images further down the page (57 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.3 g of CO₂ per visit

    2.34 g

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

Accessibility

8 to fix88
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 15 text elements with low contrast

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

  • 9 tap targets too small

    9 tap targets are too small or too close together to hit reliably with a finger.

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

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

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

    All page content should be contained by landmarks: 8 elements on the page fail this check, rated moderate by axe-core.

  • 9 links without text

    9 visible links have no text or label, so screen readers cannot say where they go.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h6), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 152 images in the HTML carry an alt attribute.

  • 47 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: 47 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fix93
  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “Little Words Project® | Original Beaded Word Bracelet To Wear & Share”.

  • 253 internal links, 11 external

    The homepage links to 253 pages on littlewordsproject.com and 11 external pages.

7 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “Little Words Project® makes trackable bead bracelets built on a powerful idea: choose your word, live it, then pass it …”.

  • One H1 headline

    Your main headline reads: “Little Words Project”.

  • Canonical URL set

    The canonical URL is https://www.littlewordsproject.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, 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.littlewordsproject.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing 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,290 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix88
  • 1 linked page hidden from search

    https://www.littlewordsproject.com/collections/bolder-by-little-words-project is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 4 pages without an H1

    https://www.littlewordsproject.com/collections/shop, https://www.littlewordsproject.com/collections/beaded-word-bracelets, https://www.littlewordsproject.com/collections/custom and https://www.littlewordsproject.com/collections/charms-by-little-words-project have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.littlewordsproject.com/collections/custom has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 105 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.

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fix87
  • 28 small tap targets

    28 of 140 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 9 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 1,073 words of copy

    The homepage carries about 1,073 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” and “Shop All”.

  • 15 calls to action

    The homepage has 15 calls to action, for example “Shop All”, “Subscribe & Save” and “Book The Bead Bar®”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 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.

  • 33 cookies set on arrival

    33

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

  • 65 other companies contacted

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

Apps your storefront loads

Elevar Conversion Tracking · Okendo · Ta Mappy Store Locator Maps · Keepcart Coupon Protect · Bta Booking App · Nosto · Ground · Klaviyo Email Marketing Sms · Order Delivery Date Time · Rivo Loyalty Rewards Referrals · powr.io · trafficmanager.net · bookthatapp.com · cloudfront.net · postscript.io · pdqprod.link · getredo.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 Tag Manager | Microsoft Clarity
Hosting
Shopify

Hiring

Hiring
25 open roles
Teams
Retail (21), Corporate (1)
Job board
greenhouse

Company

Employees
140
Headquarters
Mountainside

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 23 issues on littlewordsproject.com, including 3 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

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