Website review, no card needed

smokeandmirrorshobby2.com logo

smokeandmirrorshobby2.com website review

Visit site (opens in a new tab)Reviewed 9 November 202643 issues · 74 checks

This review found 43 issues worth fixing on smokeandmirrorshobby2.com, 21 of them high impact, across 74 checks. The most urgent: improve image delivery. 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

Full-page screenshot of smokeandmirrorshobby2.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. smokeandmirrorshobby2.com at 0.7 s0.7 s
  2. smokeandmirrorshobby2.com at 1.3 s1.3 s
  3. smokeandmirrorshobby2.com at 2.0 s2.0 s
  4. smokeandmirrorshobby2.com at 2.6 s2.6 s
  5. smokeandmirrorshobby2.com at 3.3 s3.3 s
  6. smokeandmirrorshobby2.com at 3.9 s3.9 s
  7. smokeandmirrorshobby2.com at 4.6 s4.6 s
  8. smokeandmirrorshobby2.com at 5.3 s5.3 s

Speed

10 to fix44
  • Improve image delivery

    3.4 s · 563 KiB

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

  • Avoid multiple page redirects

    2.6 s

    The page goes through 2 redirects before it starts loading, costing about 2.6 s. Link and advertise the final URL directly.

  • smokeandmirrorshobby.com adds 1.2 s

    1.2 s

    smokeandmirrorshobby.com costs a phone 1.2 s of main-thread work and 8.1 MB 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: 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.

  • 5,552 HTML elements

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (smokeandmirrorshobby.com, Shopify and JSDelivr CDN and others), adding 8.5 MB and 1.3 s of main-thread time.

  • Reduce unused JavaScript

    750 ms · 165 KiB

    About 165 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 629 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    300 ms · 70 KiB

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

  • Main-thread work: 3.2 s

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

  • Document request latency

    250 ms

    The HTML itself could arrive about 250 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Minify JavaScript

    150 ms · 39 KiB

    39 KiB could be saved by minifying JavaScript.

  • Render-blocking requests

    150 ms

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

  • Use efficient cache lifetimes

    25 KiB

    7 files are served with short cache lifetimes, so returning visitors download them again (25 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.

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

    13 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 44.3 s

    44.3 s

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

  • Speed Index: 16.9 s

    16.9 s

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

  • Time to Interactive: 44.3 s

    44.3 s

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

  • First Contentful Paint: 3.4 s

    3.4 s

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

  • Total Blocking Time: 579 ms

    579 ms

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

  • 11 images without width and height

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

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: 1.4 s

    1.4 s

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

  • Real-user INP: 112 ms

    112 ms

    Real visitors wait 112 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: 0.9 s

    0.9 s

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

  • Real-user TTFB: 419 ms

    419 ms

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

5 to fix18
  • Page weight: 8.6 MB in 143 requests

    8.6 MB

    Your homepage downloads 8.6 MB in 143 requests on a phone: images 7.0 MB (18), scripts 599 KiB (62) and other files 591 KiB (48). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Website_Slideshow_Desktop_1800_x_1000_px_1800x1000.gif weighs 5.7 MB. On a phone connection a single image that size takes seconds.

  • 3 images far larger than shown

    3.7 MB

    3 images are downloaded at several times the size a phone draws them, for example Website_Slideshow_Desktop_1800_x_1000_px_1800x1000.gif at 1,800 px wide, shown at 370 px. Resized copies would save about 3.7 MB.

  • 1 image in older formats

    1 image (5.7 MB) is 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.

  • 4 images below the first screen load straight away

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

  • About 2.4 g of CO₂ per visit

    2.43 g

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

Accessibility

7 to fixGoogle 8190
  • 9 text elements with low contrast

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

  • 3 tap targets too small

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

  • Elements must only use permitted ARIA attributes (1 element)

    Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

  • Invalid ARIA attributes

    3 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 10 links without text

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

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

SEO

7 to fixGoogle 10062
  • No meta description

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

  • No H1 headline

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

  • Title is short (25 characters)

    Your title is only 25 characters: “Smoke and Mirrors Hobby 2”. 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 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.

  • No X (Twitter) card tag

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

3 checks passed
  • Canonical URL set

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

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

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    0%

    A phone browser shows 831 words, but the HTML your server sends has only 3. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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

  • llms.txt published

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

Best practices

1 to fixGoogle 9693
  • 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_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    122 of 127 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix40
  • 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 831 words of copy

    The homepage carries about 831 words of visible text.

1 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Buy-List Singles & Sealed”.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 cookies, 6 of them by other companies (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.

  • 16 other companies contacted

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

Apps your storefront loads

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

E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on smokeandmirrorshobby2.com, including 16 speed issues, 7 SEO issues and 4 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