Website review, no card needed

simspacegolf.com logo

simspacegolf.com website review

Visit site (opens in a new tab)Reviewed 13 November 202647 issues · 94 checks

This review found 47 issues worth fixing on simspacegolf.com, 21 of them high impact, across 94 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
1.4 s1.2 sMay 23Nov 71.2 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.4 s
May 30, 20261.3 s
Jun 6, 20261.3 s
Jun 13, 20261.3 s
Jun 20, 20261.3 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.4 s
Jul 25, 20261.4 s
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.2 s
Oct 3, 20261.2 s
Oct 10, 20261.2 s
Oct 17, 20261.2 s
Oct 24, 20261.2 s
Oct 31, 20261.2 s
Nov 7, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
114 ms94 msMay 23Nov 7110 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202696 ms
May 30, 202696 ms
Jun 6, 2026100 ms
Jun 13, 2026102 ms
Jun 20, 2026102 ms
Jun 27, 2026104 ms
Jul 4, 2026103 ms
Jul 11, 2026100 ms
Jul 18, 2026102 ms
Jul 25, 2026103 ms
Aug 1, 202698 ms
Aug 8, 2026101 ms
Aug 15, 2026103 ms
Aug 22, 2026101 ms
Aug 29, 2026104 ms
Sep 5, 2026105 ms
Sep 12, 2026107 ms
Sep 19, 2026107 ms
Sep 26, 2026104 ms
Oct 3, 2026104 ms
Oct 10, 2026103 ms
Oct 17, 2026104 ms
Oct 24, 2026105 ms
Oct 31, 2026112 ms
Nov 7, 2026110 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 simspacegolf.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. simspacegolf.com at 1.0 s1.0 s
  2. simspacegolf.com at 2.0 s2.0 s
  3. simspacegolf.com at 3.0 s3.0 s
  4. simspacegolf.com at 4.0 s4.0 s
  5. simspacegolf.com at 5.0 s5.0 s
  6. simspacegolf.com at 6.0 s6.0 s
  7. simspacegolf.com at 7.0 s7.0 s
  8. simspacegolf.com at 8.0 s8.0 s

Speed

11 to fix47
  • Reduce unused JavaScript

    2.1 s · 549 KiB

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

  • Mobile performance score: 47

    47/100

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

  • Main-thread work: 5.0 s

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

  • 4,387 HTML elements

    The page has 4,387 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 (Shopify, pop-convert.com and Clarity and others), adding 14.2 MB and 791 ms of main-thread time.

  • Improve image delivery

    400 ms · 1.2 MB

    12 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.

  • Shopify adds 245 ms

    245 ms

    Shopify costs a phone 245 ms of main-thread work and 12.5 MB 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.

  • Render-blocking requests

    600 ms

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

  • pop-convert.com adds 169 ms

    169 ms

    pop-convert.com costs a phone 169 ms of main-thread work and 1,005 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 CDN adds 140 ms

    140 ms

    Google CDN costs a phone 140 ms of main-thread work and 299 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.

  • azurefd.net adds 60 ms

    60 ms

    azurefd.net costs a phone 60 ms of main-thread work and 331 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

    270 ms · 71 KiB

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

  • Use efficient cache lifetimes

    195 KiB

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

  • Minify JavaScript

    150 ms · 32 KiB

    32 KiB could be saved by minifying JavaScript.

  • 6 long tasks on the main thread

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

  • Minify CSS

    7 KiB

    7 KiB could be saved by minifying CSS.

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

    35 ms

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

Core Web Vitals

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

  • Real-user CLS: 0.38

    0.38

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

  • Largest Contentful Paint: 12.5 s

    12.5 s

    Your largest element takes 12.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: 16.4 s

    16.4 s

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

  • Speed Index: 7.8 s

    7.8 s

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

  • Cumulative Layout Shift: 0.364

    0.364

    The layout shifts by 0.364 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 34 images without width and height

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

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

    +16%

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

  • Largest content (LCP) held steady for real visitors

    -9%

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

6 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user INP: 96 ms

    96 ms

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

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

    425 ms

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

  • Total Blocking Time: 190 ms

    190 ms

    Scripts block the page for only 190 ms while loading. Good is under 200 ms.

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

Images and page weight

6 to fix29
  • Page weight: 16.7 MB in 505 requests

    16.7 MB

    Your homepage downloads 16.7 MB in 505 requests on a phone: media 11.6 MB (2), images 1.6 MB (31) and scripts 1.6 MB (160). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 2.3 MB together. On a phone connection a single image that size takes seconds.

  • 8 images in older formats

    8 images (3.3 MB) 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.

  • 5 images below the first screen load straight away

    5 images further down the page (1.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • An image on the first screen is lazy-loaded

    SimSpace_Black_Friday_Sale_2026_US_Mobile.webp 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).

  • 4 images far larger than shown

    373 KiB

    4 images are downloaded at several times the size a phone draws them, for example Enclosure-Screen.webp at 1,080 px wide, shown at 351 px. Resized copies would save about 373 KiB.

  • About 4.7 g of CO₂ per visit

    4.73 g

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

Accessibility

8 to fixGoogle 8288
  • 4 text elements with low contrast

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

  • 4 tap targets too small

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

  • 3 links without text

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

1 checks passed
  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 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

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

  • One H1 headline

    Your <h1> is empty.

  • 306 internal links, 13 external

    The homepage links to 306 pages on simspacegolf.com and 13 external pages.

7 checks passed
  • Meta description: 159 characters

    Your meta description is 159 characters: “Sim Space sells high quality golf enclosures and practice nets for use with golf simulators. Simspace has various diffe…”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Golf Simulator Enclosures & Practice Nets – SimSpace Golf”.

  • Canonical URL set

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

  • 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://simspacegolf.com/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 (2,520 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

3 to fix78
  • 1 page points its canonical at the homepage

    https://simspacegolf.com/products/golfzon-wave-home-simulator-bundle declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://simspacegolf.com/products/golfzon-wave-home-simulator-bundle all use the title “Golf Simulator Enclosures & Practice Nets – SimSpace Golf”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages without an H1

    https://simspacegolf.com/pages/contact, https://simspacegolf.com/collections/enclosure-bundles, https://simspacegolf.com/products/nvisage-neo-e-golf-enclosure-bundle, https://simspacegolf.com/products/full-swing-kit-home-simulator-bundle, https://simspacegolf.com/products/golfbuddy-shot-mate-practice-net-bundle and https://simspacegolf.com/products/slx-hybrid-mini-practice-net-bundle 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 103 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

4 to fixGoogle 7370
  • 1 broken image

    1 image failed to load on a phone, for example https://lantern.roeye.com/track.php?fingerprint=fb450ac3-8024-40c1-90d8-dc22e56e050f&referrer=&landingpage=https%3A%2F%2Fsimspacegolf.com%2F&useragent=Mozilla%2F5.0%20(iPhone%3B%20CPU%20iPhone%20OS%20.

  • 8 small tap targets

    8 of 26 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.

  • 3 JavaScript errors while loading

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

  • 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

5 to fix63
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: 24 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.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 307 words of visible text.

3 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “LEARN MORE”, “BUY NOW” and “BUY SIMULATORS”.

  • 5 short forms

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

  • Analytics in place

    Analytics detected: Microsoft Clarity.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 15 cookies set on arrival

    15

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

  • 38 other companies contacted

    Loading the homepage contacts 38 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 simspacegolf.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 13 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Triplewhale · Microsoft Clarity · Awin Affiliate Marketing · Multifeeds · Google Youtube · Inbox · Hulk Contact Form Builder · Pop Convert · Glo Color Swatch · Frontend · Rivyo Product Review · goaffpro.com · cloudfront.net

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
Bootstrap
E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

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 simspacegolf.com, including 18 speed issues, 2 SEO issues and 5 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