Website review, no card needed
shoplikelihood.com website review
Visit site (opens in a new tab)Reviewed 7 November 202632 issues · 76 checks
This review found 32 issues worth fixing on shoplikelihood.com, 12 of them high impact, across 76 checks. The most urgent: use efficient cache lifetimes. 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
1.1 s
2.1 s
3.2 s
4.2 s
5.3 s
6.3 s
7.4 s
8.4 s
Speed
Use efficient cache lifetimes
5.2 s · 1.2 MB32 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).
Reduce unused CSS
3.7 s · 51 KiBAbout 51 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.7 s faster on a phone.
Render-blocking requests
2.1 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.
Mobile performance score: 64
64/100Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.
Minify CSS
750 ms · 10 KiB10 KiB could be saved by minifying CSS.
Font display
300 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).
2,637 HTML elements
The page has 2,637 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
archive.org adds 139 ms
139 msarchive.org costs a phone 139 ms of main-thread work and 578 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.
3 third-party services on the page
3 third-party services load with your homepage (archive.org, Cloudflare and imagedelivery.net), adding 679 KiB and 148 ms of main-thread time.
Reduce unused JavaScript
106 KiBAbout 106 KiB of JavaScript is downloaded but never used on this page.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 51 ms. During a long task the page ignores taps.
Improve image delivery
22 KiB1 image could be 22 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
18 KiBPolyfills for old browsers add 18 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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 0.7 s
A phone's processor spends 0.7 s on main-thread work while loading, 223 ms of it running JavaScript. That is comfortably low.
Server response: 210 ms
210 msYour server sent the HTML in 210 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 7.4 s
7.4 sYour largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “LIKELIHOOD”. Most of its time is element render delay (8.2 s).
Speed Index: 7.8 s
7.8 sVisually, the page fills in at 7.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 7.4 s
7.4 sThe page becomes fully interactive after 7.4 s. Good is under 3.8 s.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
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.
2 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 1 ms
1 msScripts block the page for only 1 ms while loading. Good is under 200 ms.
Images and page weight
About 0.4 g of CO₂ per visit
0.43 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.43 g of CO₂e: 51.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.5 MB in 116 requests
1.5 MBYour homepage downloads 1.5 MB in 116 requests on a phone: scripts 1.0 MB (33), images 221 KiB (13) and stylesheets 109 KiB (4). That is a lean page.
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.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
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 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (6 elements)
All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.
1 checks passed
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (86 characters)
Your title is 86 characters, so Google will cut it off around 60: “WIN88 - LIKELIHOOD Seattle Specialty Boutique for Creators, Collectors and the Curious”.
4 H1 headlines
There are 4 <h1> headlines (“Your cart -”, “” and “”). One clear main headline is easier for people and search engines.
Meta description is long (292 characters)
Your meta description is 292 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://likelihood.us)”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://shoplikelihood.com/sitemap.xml, so Google discovers your pages only by following links.
371 internal links, 15 external
The homepage links to 371 pages on shoplikelihood.com and 15 external pages.
2 checks passed
Canonical URL set
The canonical URL is https://shoplikelihood.com/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
AI search readiness
No llms.txt
There is no https://shoplikelihood.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 (1,963 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages point its canonical at the homepage
https://shoplikelihood.com/collections/just-in, https://shoplikelihood.com/collections/acronym, https://shoplikelihood.com/collections/adidas, https://shoplikelihood.com/collections/affxwrks, https://shoplikelihood.com/collections/agaric-fly and https://shoplikelihood.com/collections/a-hope-hemp and 9 others declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.
16 pages share a title
/, https://shoplikelihood.com/collections/just-in, https://shoplikelihood.com/collections/acronym, https://shoplikelihood.com/collections/adidas, https://shoplikelihood.com/collections/affxwrks and https://shoplikelihood.com/collections/agaric-fly and 10 others all use the title “WIN88 - LIKELIHOOD Seattle Specialty Boutique for Creators, Collector…”. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages share a meta description
https://shoplikelihood.com/collections/just-in, https://shoplikelihood.com/collections/acronym, https://shoplikelihood.com/collections/adidas, https://shoplikelihood.com/collections/affxwrks, https://shoplikelihood.com/collections/agaric-fly and https://shoplikelihood.com/collections/a-hope-hemp and 9 others use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 196 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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 15 pages that loaded have a <title>.
Best practices
3 broken images
3 images failed to load on a phone, for example https://web.archive.org/web/20250724114535im_/https://shoplikelihood.com/cdn/shop/files/LH_Logo_Type_Black_PNG_200x.png?v=1657825538.
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.”).
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.
2 checks passed
Tap targets are thumb-sized
5 of 5 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.
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.
Thin social proof
Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 664 words of copy
The homepage carries about 664 words of visible text.
5 checks passed
15 calls to action
The homepage has 15 calls to action, for example “Shop All”, “Shop The Collection” and “Subscribe →”.
6 short forms
6 short forms (2 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
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.
5 other companies contacted
Loading the homepage contacts 5 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 shoplikelihood.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 3 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Sami Product Labels Badges · Fontify Google Custom Fonts · archive.org
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
- The footer still says © 2023.
Stack
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on shoplikelihood.com, including 13 speed issues, 6 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.