Website review, no card needed

shopyalehome.com logo

shopyalehome.com website review

Visit site (opens in a new tab)Reviewed 19 November 202619 issues · 53 checks

This review found 19 issues worth fixing on shopyalehome.com, 6 of them high impact, across 53 checks. The most urgent: page weight: 4.9 MB. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
3.1 s2.1 sMay 30Nov 142.2 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.9 s
Jun 6, 20262.9 s
Jun 13, 20262.9 s
Jun 20, 20262.9 s
Jun 27, 20262.8 s
Jul 4, 20262.8 s
Jul 11, 20262.9 s
Jul 18, 20262.9 s
Jul 25, 20262.9 s
Aug 1, 20262.9 s
Aug 8, 20262.9 s
Aug 15, 20262.9 s
Aug 22, 20263.0 s
Aug 29, 20262.9 s
Sep 5, 20262.9 s
Sep 12, 20262.9 s
Sep 19, 20262.8 s
Sep 26, 20262.8 s
Oct 3, 20262.8 s
Oct 10, 20262.8 s
Oct 17, 20262.9 s
Oct 24, 20262.9 s
Oct 31, 20262.9 s
Nov 7, 20262.6 s
Nov 14, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
146 ms119 msMay 30Nov 14141 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026122 ms
Jun 6, 2026123 ms
Jun 13, 2026122 ms
Jun 20, 2026122 ms
Jun 27, 2026123 ms
Jul 4, 2026124 ms
Jul 11, 2026125 ms
Jul 18, 2026124 ms
Jul 25, 2026122 ms
Aug 1, 2026124 ms
Aug 8, 2026127 ms
Aug 15, 2026129 ms
Aug 22, 2026132 ms
Aug 29, 2026133 ms
Sep 5, 2026135 ms
Sep 12, 2026137 ms
Sep 19, 2026137 ms
Sep 26, 2026138 ms
Oct 3, 2026139 ms
Oct 10, 2026138 ms
Oct 17, 2026138 ms
Oct 24, 2026138 ms
Oct 31, 2026138 ms
Nov 7, 2026143 ms
Nov 14, 2026141 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

No screenshot is available for this review.

Speed

Not measured in this review.

Core Web Vitals

100
  • Tap response (INP) got 16% slower for real visitors

    +16%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 139 ms

    139 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 404 ms

    404 ms

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

  • Largest content (LCP) got 18% faster for real visitors

    -18%

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

Images and page weight

3 to fix53
  • Page weight: 4.9 MB

    4.9 MB

    Your homepage downloads 4.9 MB on a phone, 2.0 MB of it images (41%). Under 2 MB keeps phones on slow connections fast.

  • 8 images below the first screen load straight away

    8 images further down the page (502 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image far larger than shown

    38 KiB

    1 image is downloaded at several times the size a phone draws it, for example ImgBanner-Mobile-91922-2-1600x1152_1900x.jpg at 1,900 px wide, shown at 390 px. Resized copies would save about 38 KiB.

  • 3 images in older formats

    3 images (185 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.

  • About 1.4 g of CO₂ per visit

    1.38 g

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

Accessibility

9 to fix88
  • Hidden but focusable

    12 elements hidden from screen readers can still receive keyboard focus.

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 3 images without alt text

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

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

    All page content should be contained by landmarks: 21 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.

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

  • 9 form fields without a label

    9 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • ARIA role should be appropriate for the element (3 elements)

    ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 45 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: 45 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fix77
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Meta description is long (173 characters)

    Your meta description is 173 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No XML sitemap

    No XML sitemap at https://shopyalehome.com/sitemap.xml, so Google discovers your pages only by following links.

  • 163 internal links, 19 external

    The homepage links to 163 pages on shopyalehome.com and 19 external pages.

4 checks passed
  • Title: 46 characters

    Your title is a healthy 46 characters: “Yale Locks | Official Online Store | Yale Home”.

  • Canonical URL set

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

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

AI search readiness

100
  • No llms.txt

    There is no https://shopyalehome.com/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,698 words), so crawlers that don't run JavaScript still read it.

Other pages

  • Your server turned our page checks away

    15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.

Best practices

2 to fix87
  • 16 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 848 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 SMART LOCKS”.

  • 45 calls to action

    The homepage has 45 calls to action, for example “Shop”, “Shop by Space” and “Learn More About Integrations”.

  • 13 short forms

    13 short forms (5 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Microsoft Clarity, Hotjar and HubSpot.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

Privacy and tracking

  • 13 trackers load before any consent

    13

    Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Hotjar and 8 mores (measured from a US location before any click). A consent tool (Ketch) is installed; check it blocks these until visitors agree where the law requires it.

  • 46 cookies set on arrival

    46

    Opening the homepage sets 46 cookies, 6 of them by other companies (measured from a US location before any click).

  • 71 other companies contacted

    Loading the homepage contacts 71 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: Ketch

    A consent management tool (Ketch) loads with the page.

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 shopyalehome.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 7 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Sitemap Noindex Pro Seo · hulkapps.com · orderlogicapp.com · shareasale.com · bazaarvoice.com · kount.com

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

Framework
jQuery
E-commerce
Shopify
Analytics
Hotjar | Microsoft Clarity
Hosting
Shopify

Company

Employees
150
Headquarters
San Francisco

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 19 issues on shopyalehome.com, including 4 SEO issues 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