Website review, no card needed
adinaeden.com website review
Visit site (opens in a new tab)Reviewed 19 October 202649 issues · 99 checks
This review found 49 issues worth fixing on adinaeden.com, 19 of them high impact, across 99 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
71C- #99,844 of 123,879 reviewed websitesbeats 17%
- #61,078 of 69,702 online storesbeats 10%
- #56,683 of 63,406 Shopify storesbeats 9%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.0 s |
| May 9, 2026 | 2.1 s |
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 164 ms |
| May 9, 2026 | 152 ms |
| May 16, 2026 | 145 ms |
| May 23, 2026 | 142 ms |
| May 30, 2026 | 138 ms |
| Jun 6, 2026 | 145 ms |
| Jun 13, 2026 | 152 ms |
| Jun 20, 2026 | 154 ms |
| Jun 27, 2026 | 160 ms |
| Jul 4, 2026 | 160 ms |
| Jul 11, 2026 | 155 ms |
| Jul 18, 2026 | 161 ms |
| Jul 25, 2026 | 168 ms |
| Aug 1, 2026 | 167 ms |
| Aug 8, 2026 | 171 ms |
| Aug 15, 2026 | 169 ms |
| Aug 22, 2026 | 162 ms |
| Aug 29, 2026 | 168 ms |
| Sep 5, 2026 | 170 ms |
| Sep 12, 2026 | 169 ms |
| Sep 19, 2026 | 171 ms |
| Sep 26, 2026 | 167 ms |
| Oct 3, 2026 | 163 ms |
| Oct 10, 2026 | 163 ms |
| Oct 17, 2026 | 166 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
1.2 s
2.5 s
3.7 s
4.9 s
6.1 s
7.4 s
8.6 s
9.8 s
Speed
Render-blocking requests
1.6 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
purpledotprice.com adds 1.4 s
1.4 spurpledotprice.com costs a phone 1.4 s of main-thread work and 152 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 13.4 s
A phone's processor spends 13.4 s on main-thread work while loading, 8.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 30
30/100Your mobile performance score is 30. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,490 HTML elements
The page has 3,490 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 (purpledotprice.com, Google Tag Manager and Shopify and others), adding 6.4 MB and 3.7 s of main-thread time.
Improve image delivery
4.1 MB40 images could be 4.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused JavaScript
1.6 MBAbout 1.6 MB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
150 ms · 1.3 MB67 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).
Shopify adds 512 ms
512 msShopify costs a phone 512 ms of main-thread work and 4.9 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.
Reduce unused CSS
450 ms · 117 KiBAbout 117 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Google Tag Manager adds 524 ms
524 msGoogle Tag Manager costs a phone 524 ms of main-thread work and 319 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 527 ms. During a long task the page ignores taps.
POWr adds 371 ms
371 msPOWr costs a phone 371 ms of main-thread work and 13 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.
bc-solutions.net adds 302 ms
302 msbc-solutions.net costs a phone 302 ms of main-thread work and 195 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
130 KiBPolyfills for old browsers add 130 KiB JavaScript that modern phones do not need.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify CSS
46 KiB46 KiB could be saved by minifying CSS.
Duplicated JavaScript
12 KiB12 KiB JavaScript is shipped twice across bundles.
Minify JavaScript
10 KiB10 KiB could be saved by minifying JavaScript.
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.
1 checks passed
Server response: 19 ms
19 msYour server sent the HTML in 19 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Speed Index: 17.0 s
17.0 sVisually, the page fills in at 17.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 56.5 s
56.5 sThe page becomes fully interactive after 56.5 s. Good is under 3.8 s.
Largest Contentful Paint: 7.7 s
7.7 sYour largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Total Blocking Time: 2.7 s
2.7 sScripts block taps and scrolling for 2.7 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.7 s
3.7 sThe first text or image appears after 3.7 s on a phone. Good is under 1.8 s.
Real-user CLS: 0.16
0.16For real visitors the layout shifts by 0.16 (75th percentile). Good is under 0.1.
Real-user TTFB: 1.0 s
1.0 sReal visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.
14 images without width and height
14 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 164 ms to 166 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 198 ms
198 msReal visitors wait 198 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 35% faster for real visitors
-35%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 11.1 MB in 539 requests
11.1 MBYour homepage downloads 11.1 MB in 539 requests on a phone: images 5.5 MB (113), scripts 3.9 MB (195) and other files 917 KiB (187). Under 2 MB keeps phones on slow connections fast.
11 images far larger than shown
3.4 MB11 images are downloaded at several times the size a phone draws them, for example NEWCUFF2.png at 2,048 px wide, shown at 165 px. Resized copies would save about 3.4 MB.
17 images below the first screen load straight away
17 images further down the page (3.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images in older formats
2 images (158 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.
About 3.1 g of CO₂ per visit
3.14 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.14 g of CO₂e: 376.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
Unlabelled dropdowns
2 dropdowns have no label.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
13 form fields without a label
13 form fields have no label, so screen readers announce an empty box and autofill guesses.
9 links without text
9 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 36 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (Organization) but with 1 problem, for example “ld+json block 2 is not valid JSON (Bad control character in string literal in JSON at position )”.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
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.
452 internal links, 15 external
The homepage links to 452 pages on adinaeden.com and 15 external pages.
7 checks passed
Meta description: 145 characters
Your meta description is 145 characters: “Shop Adina Eden, the #1 online fashion and fine jewelry store for bracelets, earrings, necklaces, chokers, rings, and m…”.
One H1 headline
Your main headline reads: “#1 Fashion & Fine Jewelry Store Online by Adina Eden”.
Title: 58 characters
Your title is a healthy 58 characters: “#1 Fashion & Fine Jewelry Store Online | Adina Eden Jewels”.
Canonical URL set
The canonical URL is https://www.adinaeden.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.adinaeden.com/sitemap.xml.
AI search readiness
Parts of the site are closed to 2 AI crawlers
Your robots.txt lets ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.
3 checks passed
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, sameAs (social profiles), description and contact details; logo would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,347 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.adinaeden.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without an H1
https://www.adinaeden.com/collections/fine-ear-cuffs has 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 110 found) and read each the way a search engine does.
6 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.
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
8 broken images
8 images failed to load on a phone, for example https://cdn.shopify.com/s/files/1/0901/1466/t/68/assets/944400e201a3--1-b6799b.png?v=1698871697.
19 small tap targets
19 of 61 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Cannot call lion.init more than once”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Requests the notification permission on page load
Requests the notification permission on page load.
1 checks passed
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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.
3 checks passed
45 calls to action
The homepage has 45 calls to action, for example “Shop All Earrings”, “Shop All 14K Earrings” and “Shop All Necklaces”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Hotjar.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 4 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
36 cookies set on arrival
36Opening the homepage sets 36 cookies (measured from a US location before any click).
82 other companies contacted
Loading the homepage contacts 82 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 adinaeden.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Hotjar
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 49 issues on adinaeden.com, including 24 speed issues, 3 SEO issues and 5 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.