Website review, no card needed
erimish.com website review
Visit site (opens in a new tab)Reviewed 10 November 202628 issues · 80 checks
This review found 28 issues worth fixing on erimish.com, 8 of them high impact, across 80 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
91A- #1,137 of 88,980 reviewed websitesbeats 98%
- #479 of 46,344 online storesbeats 98%
- #455 of 41,598 Shopify storesbeats 98%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 955 ms |
| May 30, 2026 | 927 ms |
| Jun 6, 2026 | 909 ms |
| Jun 13, 2026 | 881 ms |
| Jun 20, 2026 | 868 ms |
| Jun 27, 2026 | 881 ms |
| Jul 4, 2026 | 877 ms |
| Jul 11, 2026 | 871 ms |
| Jul 18, 2026 | 852 ms |
| Jul 25, 2026 | 832 ms |
| Aug 1, 2026 | 812 ms |
| Aug 8, 2026 | 793 ms |
| Aug 15, 2026 | 796 ms |
| Aug 22, 2026 | 808 ms |
| Aug 29, 2026 | 810 ms |
| Sep 5, 2026 | 807 ms |
| Sep 12, 2026 | 768 ms |
| Sep 19, 2026 | 703 ms |
| Sep 26, 2026 | 648 ms |
| Oct 3, 2026 | 619 ms |
| Oct 10, 2026 | 641 ms |
| Oct 17, 2026 | 717 ms |
| Oct 24, 2026 | 755 ms |
| Oct 31, 2026 | 763 ms |
| Nov 7, 2026 | 766 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 96 ms |
| May 30, 2026 | 97 ms |
| Jun 6, 2026 | 104 ms |
| Jun 13, 2026 | 104 ms |
| Jun 20, 2026 | 109 ms |
| Jun 27, 2026 | 112 ms |
| Jul 4, 2026 | 112 ms |
| Jul 11, 2026 | 112 ms |
| Jul 18, 2026 | 112 ms |
| Jul 25, 2026 | 112 ms |
| Aug 1, 2026 | 112 ms |
| Aug 8, 2026 | 114 ms |
| Aug 15, 2026 | 118 ms |
| Aug 22, 2026 | 121 ms |
| Aug 29, 2026 | 121 ms |
| Sep 5, 2026 | 125 ms |
| Sep 12, 2026 | 123 ms |
| Sep 19, 2026 | 122 ms |
| Sep 26, 2026 | 121 ms |
| Oct 3, 2026 | 123 ms |
| Oct 10, 2026 | 126 ms |
| Oct 17, 2026 | 129 ms |
| Oct 24, 2026 | 129 ms |
| Oct 31, 2026 | 124 ms |
| Nov 7, 2026 | 121 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
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
1.2 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
Improve image delivery
5.8 MB48 images could be 5.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
2,039 HTML elements
The page has 2,039 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 3 ms
3 msShopify costs a phone 3 ms of main-thread work and 572 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.
7 third-party services on the page
7 third-party services load with your homepage (Google CDN, Shopify and JSDelivr CDN and others), adding 802 KiB and 15 ms of main-thread time.
Reduce unused CSS
61 KiBAbout 61 KiB of CSS is downloaded but never applied on this page.
Use efficient cache lifetimes
52 KiB9 files are served with short cache lifetimes, so returning visitors download them again (52 KiB).
Reduce unused JavaScript
22 KiBAbout 22 KiB of JavaScript is downloaded but never used 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.
3 checks passed
Mobile performance score: 98
98/100Your mobile performance score is 98. That is in Google's “good” band (90 and up).
Main-thread work: 0.5 s
A phone's processor spends 0.5 s on main-thread work while loading, 77 ms of it running JavaScript. That is comfortably low.
Server response: 30 ms
30 msYour server sent the HTML in 30 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Tap response (INP) got 27% slower for real visitors
+27%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 96 ms to 121 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.
12 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.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 132 ms
132 msReal visitors wait 132 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: 596 ms
596 msReal visitors wait 596 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.0 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 2.0 s
2.0 sYour largest element renders in 2.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Γ”.
Speed Index: 2.3 s
2.3 sVisually, the page fills in at 2.3 s (Speed Index), inside the 3.4 s “good” threshold.
Time to Interactive: 2.0 s
2.0 sThe page is fully interactive after 2.0 s.
Cumulative Layout Shift: 0.023
0.023The layout barely moves while loading (CLS 0.023, good is under 0.1).
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
Page weight: 7.9 MB in 115 requests
7.9 MBYour homepage downloads 7.9 MB in 115 requests on a phone: images 6.7 MB (56), scripts 895 KiB (33) and HTML 229 KiB (1). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 2.7 MB together. On a phone connection a single image that size takes seconds.
6 images far larger than shown
3.1 MB6 images are downloaded at several times the size a phone draws them, for example fall_llifestyle-24.jpg at 4,339 px wide, shown at 52 px. Resized copies would save about 3.1 MB.
2 images in older formats
2 images (2.0 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.
An image on the first screen is lazy-loaded
BOGO_Black_Friday_Early_Access_Sale_Mobile_updated.jpg 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).
About 2.2 g of CO₂ per visit
2.24 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.24 g of CO₂e: 269.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
6 buttons without a name
6 buttons have no accessible name, so screen readers announce just “button”.
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
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.
17 links without text
17 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (4 elements)
Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 165 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (193 characters)
Your meta description is 193 characters; Google truncates after about 160, so the end of your pitch is cut.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
199 internal links, 2 external
The homepage links to 199 pages on erimish.com and 2 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Erimish”.
Title: 56 characters
Your title is a healthy 56 characters: “America's #1 Bracelet Shop. Erimish Stackable Bracelets.”.
Canonical URL set
The canonical URL is https://www.erimish.com/.
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.erimish.com/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
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 (837 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes /llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
10 pages without a meta description
/collections/featured-list, /collections/holiday, /collections/gifts, /collections/autumn, /collections/ncaa-licensed-merchandise and /collections/phone-chargers and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
/collections/featured-list, /collections/holiday, /collections/gifts, /collections/autumn, /collections/ncaa-licensed-merchandise and /collections/phone-chargers and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
6 pages with very little text
/collections/featured-list, /collections/ncaa-licensed-merchandise, /collections/bracelets-list, /collections/bracelet-bar-list, /collections/gem-jams and /collections/gameday-list have 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.
1 page slow to respond
/collections/autumn took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 113 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
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “window.Shopify.loadFeatures is not a function”.
2 checks passed
Tap targets are thumb-sized
55 of 58 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: 124 testimonial or review blocks. 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 336 words of copy
The homepage carries about 336 words of visible text.
3 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Learn More”, “Buy Gift Cards” and “Fundraiser Request”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Klaviyo (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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
8 other companies contacted
Loading the homepage contacts 8 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 erimish.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
Kaching Bundles · Powerful Form Builder · Bold Subscriptions · Judge Me Reviews · Attentive · Klaviyo Email Marketing Sms · Triplewhale · Microsoft Clarity · Easify Product Options · rise-ai.com · attn.tv · nfcube.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
- Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- Joplin
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on erimish.com, including 6 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.