Website review, no card needed

yaama.net logo

yaama.net website review

Visit site (opens in a new tab)Reviewed 20 November 202626 issues · 68 checks

This review found 26 issues worth fixing on yaama.net, 4 of them high impact, across 68 checks. The most urgent: fails Core Web Vitals for real visitors. 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

Real-visitor load time (LCP)75th percentile, phones
3.5 s3.0 sOct 10Nov 143.4 s
Show as table
DateReal-visitor load time (LCP)
Oct 10, 20263.1 s
Oct 17, 20263.2 s
Oct 24, 20263.2 s
Oct 31, 20263.2 s
Nov 7, 20263.4 s
Nov 14, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
230 ms214 msOct 10Nov 14228 ms
Show as table
DateReal-visitor tap response (INP)
Oct 10, 2026216 ms
Oct 17, 2026220 ms
Oct 24, 2026224 ms
Oct 31, 2026224 ms
Nov 7, 2026226 ms
Nov 14, 2026228 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

Full-page screenshot of yaama.net (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. yaama.net at 0.4 s0.4 s
  2. yaama.net at 0.8 s0.8 s
  3. yaama.net at 1.1 s1.1 s
  4. yaama.net at 1.5 s1.5 s
  5. yaama.net at 1.9 s1.9 s
  6. yaama.net at 2.3 s2.3 s
  7. yaama.net at 2.6 s2.6 s
  8. yaama.net at 3.0 s3.0 s

Speed

2 to fix93
  • Render-blocking requests

    600 ms

    9 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.

  • Shopify adds 84 ms

    84 ms

    Shopify costs a phone 84 ms of main-thread work and 346 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.

  • 2 third-party services on the page

    2 third-party services load with your homepage (Shopify and shop.app), adding 383 KiB and 89 ms of main-thread time.

  • Reduce unused CSS

    12 KiB

    About 12 KiB of CSS is downloaded but never applied on this page.

  • Use efficient cache lifetimes

    6 KiB

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

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

3 checks passed
  • Mobile performance score: 93

    93/100

    Your mobile performance score is 93. That is in Google's “good” band (90 and up).

  • Main-thread work: 1.0 s

    A phone's processor spends 1.0 s on main-thread work while loading, 359 ms of it running JavaScript. That is comfortably low.

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

6 to fix33
  • 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.

  • Real-user LCP: 3.3 s

    3.3 s

    Real visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 328 ms

    328 ms

    Real visitors wait 328 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 2.5 s

    2.5 s

    Real visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 1.2 s

    1.2 s

    Real visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest Contentful Paint: 3.2 s

    3.2 s

    Your largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Product mockup”.

  • Tap response (INP) held steady for real visitors

    +4%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 216 ms to 228 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +9%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.1 s to 3.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

6 checks passed
  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Time to Interactive: 3.3 s

    3.3 s

    The page is fully interactive after 3.3 s.

  • Speed Index: 2.1 s

    2.1 s

    Visually, the page fills in at 2.1 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

  • First Contentful Paint: 0.9 s

    0.9 s

    The first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix97
  • An image on the first screen is lazy-loaded

    corduroy-hat-camel-front-6afdab4855af5.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).

  • About 0.4 g of CO₂ per visit

    0.45 g

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

3 checks passed
  • Page weight: 1.6 MB in 252 requests

    1.6 MB

    Your homepage downloads 1.6 MB in 252 requests on a phone: other files 813 KiB (116), scripts 398 KiB (101) and images 208 KiB (8). That is a lean page.

  • 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

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

2 checks passed
  • Every image has alt text

    All 8 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 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 1 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10086
  • Title is short (13 characters)

    Your title is only 13 characters: “yaama – Yaama”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • One H1 headline

    Your <h1> is empty.

  • 13 internal links, 1 external

    The homepage links to 13 pages on yaama.net and 1 external page.

6 checks passed
  • Meta description: 85 characters

    Your meta description is 85 characters: “OFFICIAL yaama online store. Home of a selection of branded clothing and accessories.”.

  • Canonical URL set

    The canonical URL is https://yaama.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://yaama.com/sitemap.xml.

AI search readiness

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

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

  • llms.txt published

    The site publishes https://yaama.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

6 to fix60
  • 1 page without a title

    https://yaama.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://yaama.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 7 pages share 2 titles

    https://yaama.com/products/oversized-faded-t-shirt, https://yaama.com/products/oversized-faded-t-shirt-2, https://yaama.com/products/oversized-faded-t-shirt-3 and https://yaama.com/products/oversized-faded-t-shirt-4 all use the title “Oversized faded t-shirt – Yaama”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages without a meta description

    https://yaama.com/collections/all, https://yaama.com/customer_authentication/redirect and https://yaama.com/policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages share a meta description

    https://yaama.com/products/oversized-faded-t-shirt, https://yaama.com/products/oversized-faded-t-shirt-2, https://yaama.com/products/oversized-faded-t-shirt-3 and https://yaama.com/products/oversized-faded-t-shirt-4 use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://yaama.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

  • 10 internal pages checked

    We fetched 10 pages linked from your homepage and read each the way a search engine does.

2 checks passed
  • Linked pages load

    All 10 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

Best practices

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Cannot convert undefined or null to object Object.keys (<anonymous>) https://yaama.com/web-pixels/strict/app/web-pixel-…”.

2 checks passed
  • Tap targets are thumb-sized

    14 of 16 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix50
  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

  • Only about 42 words

    The homepage has only about 42 words of visible text; thin pages give Google and first-time buyers little to go on.

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

2 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Subscribe”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 11 cookies set on arrival

    11

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

  • 15 other companies contacted

    Loading the homepage contacts 15 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 yaama.net, 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 1 app. It is code from another company running for your shoppers.

Apps your storefront loads

Adtrack

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
AWS

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on yaama.net, including 8 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

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