Website review, no card needed
ayvaofficial.com website review
Visit site (opens in a new tab)Reviewed 20 November 202634 issues · 85 checks
This review found 34 issues worth fixing on ayvaofficial.com, 12 of them high impact, across 85 checks. The most urgent: improve image delivery. 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
81B- #41,205 of 123,216 reviewed websitesbeats 61%
- #27,351 of 69,453 online storesbeats 54%
- #26,360 of 63,227 Shopify storesbeats 52%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 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 |
| Nov 7, 2026 | 1.7 s |
| Nov 14, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 188 ms |
| Jun 6, 2026 | 193 ms |
| Jun 13, 2026 | 195 ms |
| Jun 20, 2026 | 196 ms |
| Jun 27, 2026 | 188 ms |
| Jul 4, 2026 | 188 ms |
| Jul 11, 2026 | 194 ms |
| Jul 18, 2026 | 189 ms |
| Jul 25, 2026 | 196 ms |
| Aug 1, 2026 | 211 ms |
| Aug 8, 2026 | 221 ms |
| Aug 15, 2026 | 230 ms |
| Aug 22, 2026 | 243 ms |
| Aug 29, 2026 | 252 ms |
| Sep 5, 2026 | 254 ms |
| Sep 12, 2026 | 254 ms |
| Sep 19, 2026 | 251 ms |
| Sep 26, 2026 | 240 ms |
| Oct 3, 2026 | 228 ms |
| Oct 10, 2026 | 228 ms |
| Oct 17, 2026 | 226 ms |
| Oct 24, 2026 | 228 ms |
| Oct 31, 2026 | 220 ms |
| Nov 7, 2026 | 210 ms |
| Nov 14, 2026 | 203 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.5 s
1.0 s
1.5 s
2.0 s
2.5 s
3.0 s
3.5 s
4.1 s
Speed
Improve image delivery
1.6 s · 916 KiB26 images could be 916 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.
Reduce unused JavaScript
1.5 s · 485 KiBAbout 485 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Main-thread work: 4.7 s
A phone's processor spends 4.7 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Facebook, Clarity and Google Tag Manager and others), adding 1.4 MB and 912 ms of main-thread time.
Mobile performance score: 59
59/100Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
600 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
Reduce unused CSS
470 ms · 72 KiBAbout 72 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 470 ms faster on a phone.
Use efficient cache lifetimes
100 ms · 315 KiB13 files are served with short cache lifetimes, so returning visitors download them again (315 KiB).
2,334 HTML elements
The page has 2,334 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 119 ms
119 msShopify costs a phone 119 ms of main-thread work and 639 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.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 174 ms. During a long task the page ignores taps.
Legacy JavaScript
39 KiBPolyfills for old browsers add 39 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: 13 ms
13 msYour server sent the HTML in 13 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 16.9 s
16.9 sYour largest element takes 16.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “FALL BAG SZN”.
Time to Interactive: 22.4 s
22.4 sThe page becomes fully interactive after 22.4 s. Good is under 3.8 s.
Speed Index: 8.2 s
8.2 sVisually, the page fills in at 8.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.1 s
3.1 sThe first text or image appears after 3.1 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 188 ms to 203 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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 1.6 s to 1.5 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: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 184 ms
184 msReal visitors wait 184 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.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 456 ms
456 msReal visitors wait 456 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 196 ms
196 msScripts block the page for only 196 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).
Images and page weight
Page weight: 5.3 MB in 471 requests
5.3 MBYour homepage downloads 5.3 MB in 471 requests on a phone: images 2.1 MB (106), scripts 1.6 MB (94) and other files 1.4 MB (258). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
7.png 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).
1 image in older formats
1 image (38 KiB) is 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 1.5 g of CO₂ per visit
1.50 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.50 g of CO₂e: 180.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
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.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
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.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
2 links without text
2 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.
Headings skip levels
Headings skip levels (h3 → h5), 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
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
65 internal links, 1 external
The homepage links to 65 pages on ayvaofficial.com and 1 external page.
7 checks passed
Meta description: 143 characters
Your meta description is 143 characters: “Vegan leather that looks luxe, priced like it shouldn't be. Crossbodies, totes & mini bags designed in Stockholm. Free …”.
Title: 39 characters
Your title is a healthy 39 characters: “AYVA | Vegan Leather Bags, Made To Last”.
Canonical URL set
The canonical URL is https://ayvaofficial.com/.
Structured data in place
Structured data found: 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://ayvaofficial.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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,016 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://ayvaofficial.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://ayvaofficial.com/apps/track123, which answers with an error. Visitors hit a dead end and search engines drop it.
5 pages share a meta description
https://ayvaofficial.com/collections/all-bags, https://ayvaofficial.com/collections/fall-bag-szn, https://ayvaofficial.com/collections/charms, https://ayvaofficial.com/pages/contact and https://ayvaofficial.com/pages/our-materials use the same meta description. A description written for each page earns more clicks.
7 pages without an H1
https://ayvaofficial.com/collections/all-bags, https://ayvaofficial.com/collections/fall-bag-szn, https://ayvaofficial.com/collections/charms, https://ayvaofficial.com/pages/contact, https://ayvaofficial.com/pages/our-materials and https://ayvaofficial.com/pages/reviews and 1 other 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 27 found) and read each the way a search engine does.
5 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 14 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 14 pages that loaded have a <title>.
Best practices
42 small tap targets
42 of 88 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.
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 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
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.
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 368 words of copy
The homepage carries about 368 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”.
6 calls to action
The homepage has 6 calls to action, for example “Contact”, “Track your order” and “SHOP”.
31 short forms
31 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: a star rating and “30,000+ CUSTOMERS”.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, Meta Pixel and Microsoft Clarity 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.
20 cookies set on arrival
20Opening the homepage sets 20 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.
31 other companies contacted
Loading the homepage contacts 31 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 ayvaofficial.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
No apps were seen in the code your storefront loads.
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 34 issues on ayvaofficial.com, including 14 speed issues, 1 SEO issue 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.