Website review, no card needed
tateossian.com website review
Visit site (opens in a new tab)Reviewed 7 November 202630 issues · 77 checks
This review found 30 issues worth fixing on tateossian.com, 9 of them high impact, across 77 checks. The most urgent: fails Core Web Vitals for real visitors. 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
83B- #28,148 of 123,879 reviewed websitesbeats 72%
- #18,424 of 69,698 online storesbeats 67%
- #17,844 of 63,406 Shopify storesbeats 65%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 128 ms |
| May 23, 2026 | 149 ms |
| May 30, 2026 | 171 ms |
| Jun 6, 2026 | 179 ms |
| Jun 13, 2026 | 179 ms |
| Jun 20, 2026 | 187 ms |
| Jun 27, 2026 | 200 ms |
| Jul 4, 2026 | 215 ms |
| Jul 11, 2026 | 230 ms |
| Jul 18, 2026 | 231 ms |
| Jul 25, 2026 | 236 ms |
| Aug 1, 2026 | 235 ms |
| Aug 8, 2026 | 234 ms |
| Aug 15, 2026 | 227 ms |
| Aug 22, 2026 | 221 ms |
| Aug 29, 2026 | 217 ms |
| Sep 5, 2026 | 207 ms |
| Sep 12, 2026 | 198 ms |
| Sep 19, 2026 | 204 ms |
| Sep 26, 2026 | 204 ms |
| Oct 3, 2026 | 209 ms |
| Oct 10, 2026 | 221 ms |
| Oct 17, 2026 | 236 ms |
| Oct 24, 2026 | 246 ms |
| Oct 31, 2026 | 257 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
Speed
6,173 HTML elements
The page has 6,173 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 4.0 s
A phone's processor spends 4.0 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
850 ms · 383 KiB10 images could be 383 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 850 ms faster on a phone.
Mobile performance score: 72
72/100Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
950 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
8 third-party services on the page
8 third-party services load with your homepage (Klaviyo, Shopify and Clarity and others), adding 1.2 MB and 653 ms of main-thread time.
Reduce unused JavaScript
150 ms · 381 KiBAbout 381 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Klaviyo adds 159 ms
159 msKlaviyo costs a phone 159 ms of main-thread work and 315 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.
Feefo.com adds 68 ms
68 msFeefo.com costs a phone 68 ms of main-thread work and 300 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.
Use efficient cache lifetimes
238 KiB19 files are served with short cache lifetimes, so returning visitors download them again (238 KiB).
Reduce unused CSS
150 ms · 46 KiBAbout 46 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 168 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
25 KiBPolyfills for old browsers add 25 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
11 KiB11 KiB JavaScript is shipped twice across bundles.
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: 33 ms
33 msYour server sent the HTML in 33 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.
Time to Interactive: 14.7 s
14.7 sThe page becomes fully interactive after 14.7 s. Good is under 3.8 s.
Largest Contentful Paint: 5.9 s
5.9 sYour largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Real-user INP: 218 ms
218 msReal visitors wait 218 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 82% slower for real visitors
+82%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 128 ms to 257 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 4.1 s
4.1 sVisually, the page fills in at 4.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 232 ms
232 msScripts block taps and scrolling for 232 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 674 ms
674 msReal visitors wait 674 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.3 s
1.3 sThe first text or image appears after 1.3 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.012
0.012The layout barely moves while loading (CLS 0.012, good is under 0.1).
Images and page weight
Page weight: 4.7 MB in 304 requests
4.7 MBYour homepage downloads 4.7 MB in 304 requests on a phone: images 2.3 MB (32), scripts 1.3 MB (152) and other files 772 KiB (97). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Navigation_Homepage_Banner-Mobile_a3d03dfd-4d9d-4710-b661-ac 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 1.3 g of CO₂ per visit
1.33 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.33 g of CO₂e: 160.2 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
5 images without alt text
5 images have no alt text, which hurts accessibility and image search.
35 links without text
35 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h4 and h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 3 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
3 H1 headlines
There are 3 <h1> headlines (“THE COLLECTOR'S CABINET”, “Stone of the Month: Citrine” and “A WORLD IN MOTION”). One clear main headline is easier for people and search engines.
Meta description is long (215 characters)
Your meta description is 215 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.
348 internal links, 1 external
The homepage links to 348 pages on tateossian.com and 1 external page.
5 checks passed
Title: 49 characters
Your title is a healthy 49 characters: “Tateossian | Designer Jewellery for Men and Women”.
Canonical URL set
The canonical URL is https://tateossian.com/.
Structured data in place
Structured data found: Organization.
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://tateossian.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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 (2,356 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://tateossian.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://tateossian.com/products/gift-card, which answers with an error. Visitors hit a dead end and search engines drop it.
2 pages without a meta description
https://tateossian.com/pages/newsletter and https://tateossian.com/collections/gifts-for-her-christmas have no meta description, so Google writes the search snippet from whatever text it finds.
14 pages without an H1
https://tateossian.com/pages/newsletter, https://tateossian.com/collections/the-mechanical-mind, https://tateossian.com/collections/the-modern-collector, https://tateossian.com/collections/small-luxuries, https://tateossian.com/collections/the-natural-wonder and https://tateossian.com/collections/the-signature-gentleman and 8 others have 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 153 found) and read each the way a search engine does.
4 checks passed
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 14 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
33 of 34 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 402 words of copy
The homepage carries about 402 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop now” and “Shop Now”.
26 calls to action
The homepage has 26 calls to action, for example “Shop All”, “Shop all” and “The Wedding Shop”.
13 short forms
13 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
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
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 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.
18 cookies set on arrival
18Opening the homepage sets 18 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.
30 other companies contacted
Loading the homepage contacts 30 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 tateossian.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
Microsoft Clarity · Zepto Product Personalizer · Klaviyo Email Marketing Sms · Simprosys Google Shopping Feed · Instafeed · Rakuten Affiliate Tracking · Orbe Geolocation · webmarked.net · nulls.solutions · azureedge.net · amazonaws.com · Swym Wishlist Plus
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
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- London
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on tateossian.com, including 16 speed issues, 3 SEO issues and 2 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.