Website review, no card needed
amaiamara.com website review
Visit site (opens in a new tab)Reviewed 6 November 202636 issues · 78 checks
This review found 36 issues worth fixing on amaiamara.com, 11 of them high impact, across 78 checks. The most urgent: page weight: 15.8 MB in 231 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
85B- #16,318 of 120,970 reviewed websitesbeats 82%
- #10,337 of 68,463 online storesbeats 79%
- #10,041 of 62,386 Shopify storesbeats 78%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
Speed
Improve image delivery
9.2 MB16 images could be 9.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
797 KiB51 files are served with short cache lifetimes, so returning visitors download them again (797 KiB).
8 third-party services on the page
8 third-party services load with your homepage (Klaviyo, omnisnippet1.com and Cloudflare CDN and others), adding 1.4 MB and 375 ms of main-thread time.
Klaviyo adds 247 ms
247 msKlaviyo costs a phone 247 ms of main-thread work and 503 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.
1,524 HTML elements
The page has 1,524 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 656 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.
Reduce unused JavaScript
216 KiBAbout 216 KiB of JavaScript is downloaded but never used on this page.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 101 ms. During a long task the page ignores taps.
Reduce unused CSS
80 KiBAbout 80 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
29 KiBPolyfills for old browsers add 29 KiB JavaScript that modern phones do not need.
Minify JavaScript
8 KiB8 KiB could be saved by minifying JavaScript.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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: 95
95/100Your mobile performance score is 95. That is in Google's “good” band (90 and up).
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 530 ms of it running JavaScript. That is comfortably low.
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 26.0 s
26.0 sThe page becomes fully interactive after 26.0 s. Good is under 3.8 s.
Speed Index: 5.8 s
5.8 sVisually, the page fills in at 5.8 s (Speed Index). Good is under 3.4 s.
46 images without width and height
46 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.
4 checks passed
Total Blocking Time: 67 ms
67 msScripts block the page for only 67 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Largest Contentful Paint: 1.1 s
1.1 sYour largest element renders in 1.1 s on a phone, inside Google's 2.5 s “good” threshold.
Images and page weight
Page weight: 15.8 MB in 231 requests
15.8 MBYour homepage downloads 15.8 MB in 231 requests on a phone: images 13.6 MB (57), scripts 1.1 MB (87) and other files 677 KiB (70). Under 2 MB keeps phones on slow connections fast.
6 images over 500 KB
6 images weigh 9.3 MB together. On a phone connection a single image that size takes seconds.
7 images far larger than shown
2.4 MB7 images are downloaded at several times the size a phone draws them, for example E5E9E148-686C-4D9F-9EE8-DBC4BB68B10B.jpg at 1,961 px wide, shown at 142 px. Resized copies would save about 2.4 MB.
15 images in older formats
15 images (11.1 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.
2 images below the first screen load straight away
2 images further down the page (371 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 4.5 g of CO₂ per visit
4.47 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.47 g of CO₂e: 536.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
42 images without alt text
42 images have no alt text, which hurts accessibility and image search.
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.
Headings skip levels
Headings skip levels (h2 → h4 and h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 6 failed. 1 more 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.
5 H1 headlines
There are 5 <h1> headlines (“Amai Amara”, “JEWELRY BOXES” and “RINGS”). One clear main headline is easier for people and search engines.
Meta description is long (314 characters)
Your meta description is 314 characters; Google truncates after about 160, so the end of your pitch is cut.
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://amaiamara.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at amaiamara.com/robots.txt, the first file search crawlers ask for.
57 internal links, 8 external
The homepage links to 57 pages on amaiamara.com and 8 external pages.
2 checks passed
Title: 53 characters
Your title is a healthy 53 characters: “Amai Amara - Classic Timeless Jewelry Based In Berlin”.
Canonical URL set
The canonical URL is https://amaiamara.com/.
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.
No llms.txt
There is no https://amaiamara.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.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (840 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a title
https://amaiamara.com/collections/new-in has no <title>, so Google invents the link text in results.
3 pages point its canonical at the homepage
https://amaiamara.com/collections/new-in/products/atlas-necklace, https://amaiamara.com/collections/new-in/products/ava-mirror-jewelry-box-cream and https://amaiamara.com/collections/new-in/products/ava-mirror-jewelry-box-olive 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.
4 pages share a title
/, https://amaiamara.com/collections/new-in/products/atlas-necklace, https://amaiamara.com/collections/new-in/products/ava-mirror-jewelry-box-cream and https://amaiamara.com/collections/new-in/products/ava-mirror-jewelry-box-olive all use the title “Amai Amara - Classic Timeless Jewelry Based In Berlin”. Search engines can't tell which page to show for a search, so each competes with the others.
8 pages without a meta description
https://amaiamara.com/collections/bestseller, https://amaiamara.com/collections/jewelry-boxes, https://amaiamara.com/collections/new-in, https://amaiamara.com/collections/necklaces, https://amaiamara.com/collections/earrings and https://amaiamara.com/collections/bracelets and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages share a meta description
https://amaiamara.com/collections/new-in/products/atlas-necklace, https://amaiamara.com/collections/new-in/products/ava-mirror-jewelry-box-cream and https://amaiamara.com/collections/new-in/products/ava-mirror-jewelry-box-olive use the same meta description. A description written for each page earns more clicks.
8 pages without an H1
https://amaiamara.com/collections/bestseller, https://amaiamara.com/collections/jewelry-boxes, https://amaiamara.com/collections/new-in, https://amaiamara.com/collections/necklaces, https://amaiamara.com/collections/earrings and https://amaiamara.com/collections/bracelets and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://amaiamara.com/collections/rings 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.
1 page slow to respond
https://amaiamara.com/collections/bestseller/products/sofia-jewelry-box-cappuccino took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 30 found) and read each the way a search engine does.
2 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
10 broken images
10 images failed to load on a phone, for example https://amaiamara.com/cdn/shop/files/heart_31.png?v=1719819060.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
2 checks passed
Tap targets are thumb-sized
30 of 36 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
About 694 words of copy
The homepage carries about 694 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW” and “Shop Best Sellers”.
18 calls to action
The homepage has 18 calls to action, for example “SHOP NOW”, “Shop Best Sellers” and “Quick shop”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 9 testimonial or review blocks, a star rating, 1 trust badge and “10.000+ Happy Customers”.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
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.
5 cookies set on arrival
5Opening the homepage sets 5 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.
22 other companies contacted
Loading the homepage contacts 22 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 amaiamara.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 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Instafeed · Omnisend · Swish Formerly Wishlist King · loox.io · wetracked.io · 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
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on amaiamara.com, including 9 speed issues, 6 SEO issues and 1 conversion gap. 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.