Website review, no card needed

meetalleyoop.com logo

meetalleyoop.com website review

Visit site (opens in a new tab)Reviewed 19 November 202647 issues · 79 checks

This review found 47 issues worth fixing on meetalleyoop.com, 20 of them high impact, across 79 checks. The most urgent: reduce unused JavaScript. 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

64D

Not ranked: the homepage didn't load normally in this review.

Real-visitor load time (LCP)75th percentile, phones
2.7 s1.7 sMay 30Nov 142.6 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20262.0 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20262.2 s
Jul 25, 20262.3 s
Aug 1, 20262.4 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.3 s
Aug 29, 20262.5 s
Sep 5, 20262.5 s
Sep 12, 20262.5 s
Sep 19, 20262.5 s
Sep 26, 20262.3 s
Oct 3, 20262.3 s
Oct 10, 20262.3 s
Oct 17, 20262.4 s
Oct 24, 20262.3 s
Oct 31, 20262.3 s
Nov 7, 20262.5 s
Nov 14, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
262 ms195 msMay 30Nov 14229 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026203 ms
Jun 6, 2026204 ms
Jun 13, 2026204 ms
Jun 20, 2026212 ms
Jun 27, 2026211 ms
Jul 4, 2026211 ms
Jul 11, 2026213 ms
Jul 18, 2026211 ms
Jul 25, 2026216 ms
Aug 1, 2026213 ms
Aug 8, 2026221 ms
Aug 15, 2026233 ms
Aug 22, 2026241 ms
Aug 29, 2026245 ms
Sep 5, 2026254 ms
Sep 12, 2026245 ms
Sep 19, 2026226 ms
Sep 26, 2026237 ms
Oct 3, 2026225 ms
Oct 10, 2026230 ms
Oct 17, 2026246 ms
Oct 24, 2026224 ms
Oct 31, 2026233 ms
Nov 7, 2026236 ms
Nov 14, 2026229 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 meetalleyoop.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. meetalleyoop.com at 1.3 s1.3 s
  2. meetalleyoop.com at 2.5 s2.5 s
  3. meetalleyoop.com at 3.8 s3.8 s
  4. meetalleyoop.com at 5.0 s5.0 s
  5. meetalleyoop.com at 6.3 s6.3 s
  6. meetalleyoop.com at 7.6 s7.6 s
  7. meetalleyoop.com at 8.8 s8.8 s
  8. meetalleyoop.com at 10.1 s10.1 s

Speed

15 to fix34
  • Reduce unused JavaScript

    2.9 s · 1.4 MB

    About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.9 s faster on a phone.

  • Render-blocking requests

    1.4 s

    16 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.

  • Mobile performance score: 34

    34/100

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

  • Main-thread work: 8.8 s

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

  • 3,243 HTML elements

    The page has 3,243 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 (iubenda, Google Tag Manager and Wicked Reports and others), adding 4.5 MB and 3.0 s of main-thread time.

  • Use efficient cache lifetimes

    850 ms · 748 KiB

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

  • Improve image delivery

    1.1 MB

    28 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • iubenda adds 815 ms

    815 ms

    iubenda costs a phone 815 ms of main-thread work and 123 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 Tag Manager adds 693 ms

    693 ms

    Google Tag Manager costs a phone 693 ms of main-thread work and 748 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

    450 ms · 127 KiB

    About 127 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • rebuyengine.com adds 211 ms

    211 ms

    rebuyengine.com costs a phone 211 ms of main-thread work and 962 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.

  • 20 long tasks on the main thread

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

  • Facebook adds 260 ms

    260 ms

    Facebook costs a phone 260 ms of main-thread work and 275 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.

  • Wicked Reports adds 285 ms

    285 ms

    Wicked Reports costs a phone 285 ms of main-thread work and 13 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.

  • Legacy JavaScript

    57 KiB

    Polyfills for old browsers add 57 KiB JavaScript that modern phones do not need.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Minify CSS

    7 KiB

    7 KiB could be saved by minifying CSS.

  • Minify JavaScript

    7 KiB

    7 KiB could be saved by minifying JavaScript.

  • 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: 10 ms

    10 ms

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

Core Web Vitals

9 to fix67
  • 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.

  • Largest Contentful Paint: 17.5 s

    17.5 s

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

  • Time to Interactive: 40.8 s

    40.8 s

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

  • Speed Index: 11.7 s

    11.7 s

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

  • Total Blocking Time: 1.6 s

    1.6 s

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Real-user LCP: 2.5 s

    2.5 s

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

  • Largest content (LCP) got 43% slower for real visitors

    +43%

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

  • Real-user FCP: 2.4 s

    2.4 s

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

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

    +14%

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

4 checks passed
  • Real-user INP: 177 ms

    177 ms

    Real visitors wait 177 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 TTFB: 577 ms

    577 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 7.9 MB in 613 requests

    7.9 MB

    Your homepage downloads 7.9 MB in 613 requests on a phone: scripts 3.7 MB (154), images 2.4 MB (218) and other files 1.3 MB (199). Under 2 MB keeps phones on slow connections fast.

  • About 2.2 g of CO₂ per visit

    2.24 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

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

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 9093
  • Elements must only use permitted ARIA attributes (22 elements)

    Elements must only use permitted ARIA attributes: 22 elements on the page fail this check, rated serious by axe-core.

  • 14 text elements with low contrast

    14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

  • 11 form fields without a label

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

  • 7 links without text

    7 visible links have no text or label, so screen readers cannot say where they go.

1 checks passed
  • 46 automated accessibility rules passed

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

SEO

8 to fixGoogle 9267
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (28 characters)

    Your title is only 28 characters: “Verifying your connection...”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No favicon declared

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

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

3 checks passed
  • One H1 headline

    Your main headline reads: “Your connection needs to be verified before you can proceed”.

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

AI search readiness

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

Best practices

3 to fixGoogle 7376
  • 10 broken images

    10 images failed to load on a phone, for example https://cdn.shopify.com/s/files/1/0249/4585/2450/files/rose-&-shine_50x.png.

  • 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 “❌ [WAIT-FOR-UTILS] Growi cookie utilities not loaded after 5 retries (500ms total)”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    31 of 34 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix17
  • Homepage answers HTTP 429

    Your homepage answered with HTTP 429, so visitors and search engines may see an error page.

  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 777 words of visible text.

Privacy and tracking

  • 10 trackers load before any consent

    10

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

  • 43 cookies set on arrival

    43

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

  • 70 other companies contacted

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

1 checks passed
  • Consent tool: iubenda

    A consent management tool (iubenda) 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 meetalleyoop.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 22 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Consentmo Gdpr · Intelligems A B Testing · Klaviyo Email Marketing Sms · Microsoft Clarity · Contentsquare Analytics · Pagefly Ai Page Builder · Okendo · Elevar Conversion Tracking · Lantern · Fondue Cashback Promotions · Tolstoy · Onward · Postscript Sms Marketing · Growi Creator Management · Applovin Shop Integration · Trakt · Gdpr Backpack · Test Sms · snapchat.com · cloudfront.net · octaneai.com · wickedreports.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
Microsoft Clarity
Hosting
Shopify

Company

Headquarters
West Hollywood

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on meetalleyoop.com, including 24 speed issues, 8 SEO issues and 6 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