Website review, no card needed

sama.nyc logo

sama.nyc website review

Visit site (opens in a new tab)Reviewed 10 November 202640 issues · 85 checks

This review found 40 issues worth fixing on sama.nyc, 17 of them high impact, across 85 checks. The most urgent: google Tag Manager adds 1.4 s. 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
2.6 s2.1 sJul 4Nov 72.2 s
Show as table
DateReal-visitor load time (LCP)
Jul 4, 20262.5 s
Jul 11, 20262.4 s
Jul 18, 20262.3 s
Jul 25, 20262.5 s
Oct 24, 20262.6 s
Oct 31, 20262.3 s
Nov 7, 20262.2 s

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 sama.nyc (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sama.nyc at 1.2 s1.2 s
  2. sama.nyc at 2.4 s2.4 s
  3. sama.nyc at 3.6 s3.6 s
  4. sama.nyc at 4.9 s4.9 s
  5. sama.nyc at 6.1 s6.1 s
  6. sama.nyc at 7.3 s7.3 s
  7. sama.nyc at 8.5 s8.5 s
  8. sama.nyc at 9.7 s9.7 s

Speed

11 to fix30
  • Google Tag Manager adds 1.4 s

    1.4 s

    Google Tag Manager costs a phone 1.4 s of main-thread work and 519 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 30

    30/100

    Your mobile performance score is 30. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 8.6 s

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

  • 3,124 HTML elements

    The page has 3,124 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Shopify and Other Google APIs/SDKs and others), adding 1.5 MB and 3.1 s of main-thread time.

  • 20 long tasks on the main thread

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

  • Shopify adds 543 ms

    543 ms

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

  • Google CDN adds 448 ms

    448 ms

    Google CDN costs a phone 448 ms of main-thread work and 296 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.

  • Other Google APIs/SDKs adds 452 ms

    452 ms

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

    414 KiB

    About 414 KiB of JavaScript is downloaded but never used on this page.

  • Render-blocking requests

    400 ms

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

  • Improve image delivery

    229 KiB

    13 images could be 229 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    69 KiB

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

  • Duplicated JavaScript

    13 KiB

    13 KiB JavaScript is shipped twice across bundles.

  • Reduce unused CSS

    11 KiB

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

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 15 ms

    15 ms

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

Core Web Vitals

8 to fix50
  • 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 CLS: 0.27

    0.27

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

  • Largest Contentful Paint: 13.7 s

    13.7 s

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

  • Time to Interactive: 23.6 s

    23.6 s

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

  • Total Blocking Time: 2.8 s

    2.8 s

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

  • Speed Index: 7.6 s

    7.6 s

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

  • Cumulative Layout Shift: 0.182

    0.182

    The layout shifts by 0.182 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 2 images without width and height

    2 images have no width and height attributes, so the layout jumps as each one loads.

  • Largest content (LCP) held steady for real visitors

    -8%

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

4 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 556 ms

    556 ms

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

  • First Contentful Paint: 1.2 s

    1.2 s

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

Images and page weight

3 to fix50
  • Page weight: 5.9 MB in 306 requests

    5.9 MB

    Your homepage downloads 5.9 MB in 306 requests on a phone: images 3.5 MB (133), scripts 1.4 MB (68) and other files 775 KiB (65). Under 2 MB keeps phones on slow connections fast.

  • 11 images in older formats

    11 images (645 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.

  • 2 images far larger than shown

    134 KiB

    2 images are downloaded at several times the size a phone draws them, for example rugs.jpeg at 1,020 px wide, shown at 33 px. Resized copies would save about 134 KiB.

  • 1 image below the first screen load straight away

    1 image further down the page (33 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.7 g of CO₂ per visit

    1.69 g

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

Accessibility

8 to fixGoogle 7488
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Orphan list items

    Some list items are not inside a list.

  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 173 images without alt text

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

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

1 checks passed
  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 8 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 8586
  • Title is short (21 characters)

    Your title is only 21 characters: “Sama Department Store”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • One H1 headline

    Your <h1> is empty.

  • 253 internal links, 12 external

    The homepage links to 253 pages on sama.nyc and 12 external pages.

6 checks passed
  • Meta description: 152 characters

    Your meta description is 152 characters: “Explore your creative self with SAMA. Specializing in home decor, bedroom, bathroom, kitchen and all your everyday good…”.

  • Canonical URL set

    The canonical URL is https://sama.nyc/.

  • 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://sama.nyc/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://sama.nyc/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,364 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 2 pages without a meta description

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

  • 1 page without an H1

    https://sama.nyc/collections/wall-decor has 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 103 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    3 pages of 15 loaded without an error (the rest turned automated requests away).

  • 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 3 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9291
  • 13 small tap targets

    13 of 64 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 24 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 549 words of copy

    The homepage carries about 549 words of visible text.

4 checks passed
  • Clear next step on the first screen

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

  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact us”, “Shop all” and “Contact Us”.

  • 24 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, 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.

  • 12 cookies set on arrival

    12

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

  • 19 other companies contacted

    Loading the homepage contacts 19 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 sama.nyc, 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 5 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Powerful Form Builder · Smart Filter Search · Judge Me Reviews · Froonze Loyalty Wishlist · Smart Product Filters

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
Google Tag Manager
Hosting
Shopify

Company

Headquarters
New York

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on sama.nyc, including 19 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

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