Website review, no card needed

smartmakshop.com logo

smartmakshop.com website review

Visit site (opens in a new tab)Reviewed 10 November 202637 issues · 80 checks

This review found 37 issues worth fixing on smartmakshop.com, 11 of them high impact, across 80 checks. The most urgent: mobile performance score: 44. 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
4.7 s1.2 sMay 23Nov 72.1 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.9 s
May 30, 20263.6 s
Jun 6, 20264.1 s
Jun 13, 20264.3 s
Jun 20, 20264.1 s
Jun 27, 20263.2 s
Jul 4, 20262.3 s
Jul 11, 20262.1 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.7 s
Sep 5, 20261.7 s
Sep 12, 20263.0 s
Sep 19, 20263.1 s
Sep 26, 20263.2 s
Oct 3, 20263.4 s
Oct 10, 20262.7 s
Oct 17, 20262.3 s
Oct 24, 20262.3 s
Oct 31, 20262.3 s
Nov 7, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
838 ms34 msMay 23Nov 7282 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026149 ms
May 30, 2026150 ms
Jun 6, 2026127 ms
Jun 13, 2026205 ms
Jun 20, 2026197 ms
Jun 27, 2026211 ms
Jul 4, 2026273 ms
Jul 11, 2026281 ms
Jul 18, 2026281 ms
Jul 25, 2026321 ms
Aug 1, 2026261 ms
Aug 8, 2026204 ms
Aug 15, 2026196 ms
Aug 22, 2026152 ms
Aug 29, 2026163 ms
Sep 5, 2026194 ms
Sep 12, 2026647 ms
Sep 19, 2026665 ms
Sep 26, 2026679 ms
Oct 3, 2026745 ms
Oct 10, 2026475 ms
Oct 17, 2026354 ms
Oct 24, 2026339 ms
Oct 31, 2026309 ms
Nov 7, 2026282 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 smartmakshop.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. smartmakshop.com at 0.6 s0.6 s
  2. smartmakshop.com at 1.3 s1.3 s
  3. smartmakshop.com at 1.9 s1.9 s
  4. smartmakshop.com at 2.5 s2.5 s
  5. smartmakshop.com at 3.2 s3.2 s
  6. smartmakshop.com at 3.8 s3.8 s
  7. smartmakshop.com at 4.4 s4.4 s
  8. smartmakshop.com at 5.1 s5.1 s

Speed

10 to fix44
  • 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: 5.1 s

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

  • Reduce unused JavaScript

    750 ms · 773 KiB

    About 773 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.

  • Improve image delivery

    650 ms · 781 KiB

    15 images could be 781 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Shopify and loox.io and others), adding 1.4 MB and 954 ms of main-thread time.

  • Use efficient cache lifetimes

    650 ms · 88 KiB

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

  • 7 long tasks on the main thread

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

  • YouTube adds 608 ms

    608 ms

    YouTube costs a phone 608 ms of main-thread work and 1,000 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 · 194 KiB

    About 194 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.

  • Render-blocking requests

    450 ms

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

  • Legacy JavaScript

    150 ms · 8 KiB

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

  • Minify JavaScript

    10 KiB

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

    12 ms

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

Core Web Vitals

10 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: 10.4 s

    10.4 s

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

  • Time to Interactive: 18.1 s

    18.1 s

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

  • Speed Index: 8.5 s

    8.5 s

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

  • Total Blocking Time: 802 ms

    802 ms

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

  • Real-user INP: 282 ms

    282 ms

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

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

    +98%

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • 1 image without width and height

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

5 checks passed
  • 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 CLS: 0.00

    0.00

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

  • Real-user TTFB: 772 ms

    772 ms

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

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

    -32%

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

  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

2 to fix75
  • Page weight: 3.8 MB in 231 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 231 requests on a phone: scripts 1.5 MB (65), images 1.0 MB (28) and other files 799 KiB (117). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    164 KiB

    1 image is downloaded at several times the size a phone draws it, for example 8-10_people_outdoor_square_sauna_-_6_2000x.png at 2,000 px wide, shown at 390 px. Resized copies would save about 164 KiB.

  • About 1.1 g of CO₂ per visit

    1.09 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.09 g of CO₂e: 130.3 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 load when needed

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

Accessibility

6 to fixGoogle 8993
  • ARIA commands must have an accessible name (27 elements)

    ARIA commands must have an accessible name: 27 elements on the page fail this check, rated serious by axe-core.

  • 3 images without alt text

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

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

  • 2 form fields without a label

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

  • 1 link without text

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

  • Alternative text of images should not be repeated as text (5 elements)

    Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 50 automated accessibility rules passed

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

SEO

1 to fixGoogle 9290
  • No H1 headline

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

  • 53 internal links, 10 external

    The homepage links to 53 pages on smartmakshop.com and 10 external pages.

7 checks passed
  • Meta description: 158 characters

    Your meta description is 158 characters: “Shop our range of Portable Steam, Infrared & Wooden Saunas online at SMARTMAK Save Up to 50% Off Free Delivery over $49…”.

  • Title: 52 characters

    Your title is a healthy 52 characters: “Sauna, Diy sauna, Sauna room, Outdoor sauna-Smartmak”.

  • Canonical URL set

    The canonical URL is https://www.smartmakshop.com/.

  • Structured data in place

    Structured data found: 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://www.smartmakshop.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

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.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 5 pages without a meta description

    https://www.smartmakshop.com/collections/new-sqaure-sauna, https://www.smartmakshop.com/collections/outdoor-steam-barrel-sauna, https://www.smartmakshop.com/collections/indoor-steam-sauna, https://www.smartmakshop.com/collections/outdoor-infrared-sauna and https://www.smartmakshop.com/collections/all-products have no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages without an H1

    https://www.smartmakshop.com/collections/new-sqaure-sauna, https://www.smartmakshop.com/collections/outdoor-steam-barrel-sauna, https://www.smartmakshop.com/collections/indoor-steam-sauna, https://www.smartmakshop.com/collections/indoor-110v-220v-infrared-sauna, https://www.smartmakshop.com/collections/outdoor-infrared-sauna and https://www.smartmakshop.com/pages/smartmak-installation-services and 2 others have 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 20 found) and read each the way a search engine does.

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

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

Best practices

2 to fixGoogle 7791
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Error initializing managers Error: Endpoint key not set”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • 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.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 644 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact us”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact Us” and “Tacking Order”.

  • 6 short forms

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

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

  • 25 other companies contacted

    Loading the homepage contacts 25 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 smartmakshop.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

Dr Stacked Discounts · Inbox · Globo Product Options · Event Promotion Bar · loox.io · hextom.com · getsitecontrol.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 37 issues on smartmakshop.com, including 20 speed issues, 1 SEO issue 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