Website review, no card needed

1906.shop logo

1906.shop website review

Visit site (opens in a new tab)Reviewed 27 October 202634 issues · 85 checks

This review found 34 issues worth fixing on 1906.shop, 11 of them high impact, across 85 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

Real-visitor load time (LCP)75th percentile, phones
2.0 s1.7 sMay 9Oct 241.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.8 s
May 16, 20261.8 s
May 23, 20261.8 s
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20261.8 s
Oct 10, 20261.8 s
Oct 17, 20261.8 s
Oct 24, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
154 ms118 msMay 9Oct 24146 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026122 ms
May 16, 2026124 ms
May 23, 2026129 ms
May 30, 2026130 ms
Jun 6, 2026136 ms
Jun 13, 2026137 ms
Jun 20, 2026138 ms
Jun 27, 2026140 ms
Jul 4, 2026143 ms
Jul 11, 2026146 ms
Jul 18, 2026146 ms
Jul 25, 2026146 ms
Aug 1, 2026146 ms
Aug 8, 2026145 ms
Aug 15, 2026145 ms
Aug 22, 2026146 ms
Aug 29, 2026146 ms
Sep 5, 2026148 ms
Sep 12, 2026150 ms
Sep 19, 2026148 ms
Sep 26, 2026146 ms
Oct 3, 2026146 ms
Oct 10, 2026145 ms
Oct 17, 2026145 ms
Oct 24, 2026146 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 1906.shop (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 1906.shop at 1.0 s1.0 s
  2. 1906.shop at 2.1 s2.1 s
  3. 1906.shop at 3.1 s3.1 s
  4. 1906.shop at 4.2 s4.2 s
  5. 1906.shop at 5.2 s5.2 s
  6. 1906.shop at 6.3 s6.3 s
  7. 1906.shop at 7.3 s7.3 s
  8. 1906.shop at 8.4 s8.4 s

Speed

16 to fix44
  • Reduce unused JavaScript

    5.5 s · 986 KiB

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

  • Use efficient cache lifetimes

    2.5 s · 488 KiB

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

  • Render-blocking requests

    2.8 s

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

  • Improve image delivery

    2.2 s · 385 KiB

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

  • Mobile performance score: 44

    44/100

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

  • Main-thread work: 7.6 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (moonshot-ai.com, alia-prod.com and Klaviyo and others), adding 2.6 MB and 1.8 s of main-thread time.

  • moonshot-ai.com adds 921 ms

    921 ms

    moonshot-ai.com costs a phone 921 ms of main-thread work and 38 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

    600 ms · 120 KiB

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

  • Legacy JavaScript

    600 ms · 102 KiB

    Polyfills for old browsers add 102 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 600 ms faster on a phone.

  • Minify CSS

    300 ms · 9 KiB

    9 KiB could be saved by minifying CSS.

  • alia-prod.com adds 252 ms

    252 ms

    alia-prod.com costs a phone 252 ms of main-thread work and 474 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,356 HTML elements

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

  • rebuyengine.com adds 123 ms

    123 ms

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

  • Klaviyo adds 146 ms

    146 ms

    Klaviyo costs a phone 146 ms of main-thread work and 619 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.

  • yuma.ai adds 92 ms

    92 ms

    yuma.ai costs a phone 92 ms of main-thread work and 489 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.

  • 12 long tasks on the main thread

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

  • Font display

    100 ms

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

  • 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

6 to fix100
  • First Contentful Paint: 9.6 s

    9.6 s

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

  • Largest Contentful Paint: 44.1 s

    44.1 s

    Your largest element takes 44.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “TRY YOUR LUCK Scratch below to see what you win YOU'VE GOT …”.

  • Speed Index: 21.3 s

    21.3 s

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

  • Time to Interactive: 44.4 s

    44.4 s

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

  • Total Blocking Time: 450 ms

    450 ms

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

  • 10 images without width and height

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

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

    +18%

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

  • Largest content (LCP) held steady for real visitors

    0%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.8 s 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 this page (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: 163 ms

    163 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Real-user TTFB: 718 ms

    718 ms

    Real visitors wait 718 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

2 to fix64
  • Page weight: 7.0 MB in 539 requests

    7.0 MB

    Your homepage downloads 7.0 MB in 539 requests on a phone: scripts 2.8 MB (164), images 1.7 MB (61) and other files 1.2 MB (237). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    DTC_-_September_2026_-_Subscription_Offer-Hero_Banner-Mobile 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 2.0 g of CO₂ per visit

    1.97 g

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

2 checks passed
  • 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

2 to fixGoogle 10097
  • 3 links without text

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

  • 1 form field without a label

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 79 images in the HTML carry an alt attribute.

  • 31 automated accessibility rules passed

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

SEO

2 to fixGoogle 9293
  • 2 H1 headlines

    There are 2 <h1> headlines (“FREE TIN OF GO FREE TIN OF GO” and “25% OffYour FirstSubscription 25% OffYour First S…”). One clear main headline is easier for people and search engines.

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 105 internal links, 4 external

    The homepage links to 105 pages on 1906.shop and 4 external pages.

7 checks passed
  • Meta description: 159 characters

    Your meta description is 159 characters: “Buy THC online at 1906! Fast-acting THC and CBD pills, gummies and more delivered to your door. Pharma-grade plant-powe…”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Buy THC Online | THC & CBD Pills, Gummies & More | 1906”.

  • Canonical URL set

    The canonical URL is https://1906.shop/.

  • 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://1906.shop/sitemap.xml.

AI search readiness

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

  • llms.txt published

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

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 37 found) and read each the way a search engine does.

7 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7385
  • 12 small tap targets

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

  • 1 third-party cookie

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

  • 4 JavaScript errors while loading

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

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • Thin social proof

    Social proof on the homepage: 6 customer or partner logos. 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.

  • About 416 words of copy

    The homepage carries about 416 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”.

  • 32 calls to action

    The homepage has 32 calls to action, for example “Shop”, “Shop for Connection” and “Shop for Brainpower & Energy”.

  • 7 short forms

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

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 46 cookies set on arrival

    46

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

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

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 1906.shop, 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
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

Company

Employees
130
Headquarters
Stamford

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on 1906.shop, including 22 speed issues, 2 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