Website review, no card needed

ayanaeg.com logo

ayanaeg.com website review

Visit site (opens in a new tab)Reviewed 10 November 202636 issues · 72 checks

This review found 36 issues worth fixing on ayanaeg.com, 13 of them high impact, across 72 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of ayanaeg.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ayanaeg.com at 0.9 s0.9 s
  2. ayanaeg.com at 1.9 s1.9 s
  3. ayanaeg.com at 2.8 s2.8 s
  4. ayanaeg.com at 3.7 s3.7 s
  5. ayanaeg.com at 4.7 s4.7 s
  6. ayanaeg.com at 5.6 s5.6 s
  7. ayanaeg.com at 6.6 s6.6 s
  8. ayanaeg.com at 7.5 s7.5 s

Speed

9 to fix56
  • Improve image delivery

    3.2 s · 589 KiB

    3 images could be 589 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.2 s faster on a phone.

  • Use efficient cache lifetimes

    2.0 s · 397 KiB

    25 files are served with short cache lifetimes, so returning visitors download them again (397 KiB).

  • Reduce unused JavaScript

    1.2 s · 246 KiB

    About 246 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Mobile performance score: 56

    56/100

    Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.

  • 7 third-party services on the page

    7 third-party services load with your homepage (Other Google APIs/SDKs, teepublic.com and Google Tag Manager and others), adding 830 KiB and 773 ms of main-thread time.

  • Main-thread work: 3.6 s

    A phone's processor spends 3.6 s on main-thread work while loading, 864 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Other Google APIs/SDKs adds 316 ms

    316 ms

    Other Google APIs/SDKs costs a phone 316 ms of main-thread work and 138 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.

  • Render-blocking requests

    300 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.

  • teepublic.com adds 214 ms

    214 ms

    teepublic.com costs a phone 214 ms of main-thread work and 385 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 CSS

    150 ms · 40 KiB

    About 40 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.

  • 9 long tasks on the main thread

    9 long tasks block the main thread while loading, the longest for 167 ms. During a long task the page ignores taps.

  • 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.

1 checks passed
  • Server response: 141 ms

    141 ms

    Your server sent the HTML in 141 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix54
  • Largest Contentful Paint: 10.3 s

    10.3 s

    Your largest element takes 10.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “COLOK123 ✘ Sambungan Cepat Menuju Pilihan Lebih Terarah by …”. Most of its time is resource load duration (4.2 s).

  • Time to Interactive: 10.3 s

    10.3 s

    The page becomes fully interactive after 10.3 s. Good is under 3.8 s.

  • Speed Index: 6.1 s

    6.1 s

    Visually, the page fills in at 6.1 s (Speed Index). Good is under 3.4 s.

  • Total Blocking Time: 466 ms

    466 ms

    Scripts block taps and scrolling for 466 ms in total while the page loads. Good is under 200 ms.

  • First Contentful Paint: 2.2 s

    2.2 s

    The first text or image appears after 2.2 s on a phone. Good is under 1.8 s.

  • 4 images without width and height

    4 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.

1 checks passed
  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

3 to fix65
  • 1 image over 500 KB

    banner.png weighs 495 KiB. On a phone connection a single image that size takes seconds.

  • 2 images in older formats

    2 images (553 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.

  • 1 image far larger than shown

    18 KiB

    1 image is downloaded at several times the size a phone draws it, for example bubu-angry.gif at 480 px wide, shown at 132 px. Resized copies would save about 18 KiB.

  • About 0.4 g of CO₂ per visit

    0.42 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.42 g of CO₂e: 50.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 checks passed
  • Page weight: 1.5 MB in 42 requests

    1.5 MB

    Your homepage downloads 1.5 MB in 42 requests on a phone: images 750 KiB (20), scripts 513 KiB (11) and fonts 142 KiB (4). That is a lean page.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

9 to fixGoogle 7087
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • Positive tabindex

    1 element has a tabindex above 0, which scrambles the keyboard order.

  • 17 images without alt text

    17 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (38 elements)

    All page content should be contained by landmarks: 38 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings skip levels

    Headings skip levels (h1 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 40 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 9 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 8598
  • 4 links crawlers can't follow

    4 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 140 internal links, 9 external

    The homepage links to 140 pages on ayanaeg.com and 9 external pages.

8 checks passed
  • Meta description: 147 characters

    Your meta description is 147 characters: “Setiap bagian di COLOK123 disusun agar saling terhubung dengan baik, memberikan jalur yang jelas serta akses yang lebih…”.

  • One H1 headline

    Your main headline reads: “COLOK123 ✘ Sambungan Cepat Menuju Pilihan Lebih Terarah”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “COLOK123 ✘ Sambungan Cepat Menuju Pilihan Lebih Terarah”.

  • Canonical URL set

    The canonical URL is https://ayanaeg.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, FAQPage and Product.

  • 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://ayanaeg.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

2 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 (1,505 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix0
  • 15 linked pages are broken

    Your homepage links to https://ayanaeg.com/t-shirts, https://ayanaeg.com/order/status, https://ayanaeg.com/contact, https://ayanaeg.com/shipping, https://ayanaeg.com/sizechart and https://ayanaeg.com/about and 9 others, which answer with an error. Visitors hit a dead end and search engines drop them.

Best practices

4 to fixGoogle 6974
  • 7 broken images

    7 images failed to load on a phone, for example https://assets.teepublic.com/assets/teepublicons/x_close_orange400-c1926221e50e7f6686d23ac344405449054e43f23d0f3306f15d8dfd546f999a.svg.

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Unexpected identifier 'Gender'”.

  • 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”).

2 checks passed
  • Tap targets are thumb-sized

    25 of 30 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • 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 1,041 words of copy

    The homepage carries about 1,041 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 All Designs”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Shop All Designs”, “Order Status” and “Contact Us”.

  • 4 short forms

    4 short forms (2 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 45 testimonial or review blocks, 1 customer or partner logo and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (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.

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 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.

  • 8 other companies contacted

    Loading the homepage contacts 8 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 ayanaeg.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
10 Shopify Products;Shopify;Shopify Plus
Analytics
Google Analytics | Google Tag Manager
Hosting
Namecheap

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 ayanaeg.com, including 15 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25