Website review, no card needed
aarialondon.com website review
Visit site (opens in a new tab)Reviewed 17 November 202629 issues · 85 checks
This review found 29 issues worth fixing on aarialondon.com, 9 of them high impact, across 85 checks. The most urgent: main-thread work: 11.8 s. 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,230 of 120,061 reviewed websitesbeats 82%
- #10,291 of 68,036 online storesbeats 79%
- #9,999 of 62,006 Shopify storesbeats 78%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.7 s |
| Sep 12, 2026 | 2.7 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.1 s |
| Oct 31, 2026 | 2.0 s |
| Nov 7, 2026 | 2.2 s |
| Nov 14, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 236 ms |
| Jun 6, 2026 | 245 ms |
| Jun 13, 2026 | 256 ms |
| Jun 20, 2026 | 260 ms |
| Jun 27, 2026 | 260 ms |
| Jul 4, 2026 | 251 ms |
| Jul 11, 2026 | 237 ms |
| Jul 18, 2026 | 229 ms |
| Jul 25, 2026 | 227 ms |
| Aug 1, 2026 | 237 ms |
| Aug 8, 2026 | 252 ms |
| Aug 15, 2026 | 254 ms |
| Aug 22, 2026 | 265 ms |
| Aug 29, 2026 | 255 ms |
| Sep 5, 2026 | 221 ms |
| Sep 12, 2026 | 204 ms |
| Sep 19, 2026 | 188 ms |
| Sep 26, 2026 | 179 ms |
| Oct 3, 2026 | 179 ms |
| Oct 10, 2026 | 171 ms |
| Oct 17, 2026 | 168 ms |
| Oct 24, 2026 | 162 ms |
| Oct 31, 2026 | 157 ms |
| Nov 7, 2026 | 162 ms |
| Nov 14, 2026 | 164 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
4.4 s
8.7 s
13.1 s
17.5 s
21.8 s
26.2 s
30.6 s
34.9 s
Speed
Main-thread work: 11.8 s
A phone's processor spends 11.8 s on main-thread work while loading, 2.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,493 HTML elements
The page has 3,493 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
500 ms · 883 KiB25 images could be 883 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, loox.io and Klaviyo and others), adding 1.7 MB and 785 ms of main-thread time.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 551 ms. During a long task the page ignores taps.
Shopify adds 263 ms
263 msShopify costs a phone 263 ms of main-thread work and 714 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.
loox.io adds 261 ms
261 msloox.io costs a phone 261 ms of main-thread work and 546 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.
Klaviyo adds 141 ms
141 msKlaviyo costs a phone 141 ms of main-thread work and 317 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
198 KiBAbout 198 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
150 KiB21 files are served with short cache lifetimes, so returning visitors download them again (150 KiB).
Render-blocking requests
100 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 100 ms.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Reduce unused CSS
31 KiBAbout 31 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 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.
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: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 15.5 s
15.5 sVisually, the page fills in at 15.5 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 8.3 s
8.3 sYour largest element takes 8.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 20.4 s
20.4 sThe page becomes fully interactive after 20.4 s. Good is under 3.8 s.
First Contentful Paint: 2.5 s
2.5 sThe first text or image appears after 2.5 s on a phone. Good is under 1.8 s.
Total Blocking Time: 361 ms
361 msScripts block taps and scrolling for 361 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 164 ms
164 msReal visitors wait 164 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.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 637 ms
637 msReal visitors wait 637 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 32% faster for real visitors
-32%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 236 ms to 164 ms 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: 5.5 MB in 566 requests
5.5 MBYour homepage downloads 5.5 MB in 566 requests on a phone: images 2.4 MB (70), other files 1.5 MB (282) and scripts 1.2 MB (184). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (45 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.6 g of CO₂ per visit
1.55 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.55 g of CO₂e: 186.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
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.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
28 links without text
28 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (5 elements)
ARIA role should be appropriate for the element: 5 elements on the page fail this check, rated minor by axe-core.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
183 internal links, 4 external
The homepage links to 183 pages on aarialondon.com and 4 external pages.
8 checks passed
Meta description: 103 characters
Your meta description is 103 characters: “Demi fine sterling silver and gold plated jewellery made to mix, layer & stack. Jewelry for every muse.”.
One H1 headline
Your main headline reads: “Aaria London”.
Title: 47 characters
Your title is a healthy 47 characters: “Demi Fine Jewelry For Every Muse - Aaria London”.
Canonical URL set
The canonical URL is https://www.aarialondon.com/en-us.
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.aarialondon.com/sitemap.xml.
AI search readiness
4 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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,951 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.aarialondon.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://www.aarialondon.com/en-us/collections/stud-earrings has no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://www.aarialondon.com/en-us/collections/new-in, https://www.aarialondon.com/en-us/collections/best-sellers-1, https://www.aarialondon.com/en-us/collections/earrings, https://www.aarialondon.com/en-us/collections/illusionearrings, https://www.aarialondon.com/en-us/collections/stud-earrings and https://www.aarialondon.com/en-us/collections/cuff and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://www.aarialondon.com/en-us/collections/solid-gold-earrings-1 and https://www.aarialondon.com/en-us/collections/necklaces 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.
2 pages slow to respond
https://www.aarialondon.com/en-us/collections/pearls and https://www.aarialondon.com/en-us/collections/bracelets took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 77 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 “Failed to load resource: the server responded with a status of 404 ()”.
2 checks passed
Tap targets are thumb-sized
73 of 80 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 716 words of copy
The homepage carries about 716 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW” and “New Arrivals Shop New”.
19 calls to action
The homepage has 19 calls to action, for example “Sign up for 10% off your first order”, “Shop by Metal” and “Shop now”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 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.
28 cookies set on arrival
28Opening the homepage sets 28 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.
38 other companies contacted
Loading the homepage contacts 38 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 aarialondon.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 9 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Trackbee Connect · Early Bird · Triplewhale · Multifeeds · Klaviyo Email Marketing Sms · zooomyapps.com · loox.io · automizely.com · cloudfront.net
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
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on aarialondon.com, including 14 speed 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.