Website review, no card needed
gtpplus.com website review
Visit site (opens in a new tab)Reviewed 12 November 202628 issues · 79 checks
This review found 28 issues worth fixing on gtpplus.com, 9 of them high impact, across 79 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
One score from every part of this review. How it works
Speed
Render-blocking requests
1.8 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Reduce unused JavaScript
1.3 s · 262 KiBAbout 262 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.3 s faster on a phone.
Mobile performance score: 68
68/100Your mobile performance score is 68. Pages that score under 90 lose visitors before the first paint.
2,583 HTML elements
The page has 2,583 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 124 ms
124 msShopify costs a phone 124 ms of main-thread work and 347 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.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Clarity and JSDelivr CDN and others), adding 704 KiB and 335 ms of main-thread time.
Use efficient cache lifetimes
150 ms · 107 KiB10 files are served with short cache lifetimes, so returning visitors download them again (107 KiB).
Minify JavaScript
150 ms · 9 KiB9 KiB could be saved by minifying JavaScript.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 103 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Improve image delivery
34 KiB2 images could be 34 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
21 KiBAbout 21 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
15 KiBPolyfills for old browsers add 15 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
9 KiB9 KiB JavaScript is shipped twice across bundles.
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.
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 930 ms of it running JavaScript. That is comfortably low.
Server response: 16 ms
16 msYour server sent the HTML in 16 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 11.7 s
11.7 sYour largest element takes 11.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 11.9 s
11.9 sThe page becomes fully interactive after 11.9 s. Good is under 3.8 s.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Speed Index: 3.9 s
3.9 sVisually, the page fills in at 3.9 s (Speed Index). Good is under 3.4 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Cumulative Layout Shift: 0.067
0.067The layout barely moves while loading (CLS 0.067, good is under 0.1).
Total Blocking Time: 61 ms
61 msScripts block the page for only 61 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.9 MB in 271 requests
2.9 MBYour homepage downloads 2.9 MB in 271 requests on a phone: other files 1,001 KiB (138), images 903 KiB (25) and scripts 706 KiB (62). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
gtpplusloginslider2.png 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).
1 image in older formats
1 image (43 KiB) 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.
About 0.8 g of CO₂ per visit
0.82 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.82 g of CO₂e: 98.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Summary elements must have discernible text (1 element)
Summary elements must have discernible text: 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 (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3 and h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (23 characters)
Your title is only 23 characters: “Golf Team Products Home”. Between 30 and 65 characters leaves room to say what you do and for whom.
Canonical points to another host
Your canonical URL points to golfteamproducts.com, not gtpplus.com, so Google may credit that host instead.
5 H1 headlines
There are 5 <h1> headlines (“”, “Where Golf Coaches Go to Outfit Themselves and Th…” and “Free Membership”). One clear main headline is easier for people and search engines.
Meta description is long (249 characters)
Your meta description is 249 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
420 internal links, 16 external
The homepage links to 420 pages on gtpplus.com and 16 external pages.
3 checks passed
Structured data in place
Structured data found: Organization and WebSite.
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://gtpplus.com/sitemap.xml.
AI search readiness
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 (1,975 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://gtpplus.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 pages without a meta description
https://gtpplus.com/pages/quick-order, https://gtpplus.com/collections/shop-apparel-mens-polos, https://gtpplus.com/collections/shop-apparel-mens-t-shirts, https://gtpplus.com/collections/shop-apparel-mens-crews-hoodies, https://gtpplus.com/collections/shop-apparel-mens-layering and https://gtpplus.com/collections/shop-apparel-mens-outerwear and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://gtpplus.com/pages/quick-order, https://gtpplus.com/collections/shop-apparel-mens-polos, https://gtpplus.com/collections/shop-apparel-mens-t-shirts, https://gtpplus.com/collections/shop-apparel-mens-crews-hoodies, https://gtpplus.com/collections/shop-apparel-mens-layering and https://gtpplus.com/collections/shop-apparel-mens-outerwear and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://gtpplus.com/collections/shop-apparel-mens-polos took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 189 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
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
16 of 18 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
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 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 663 words of copy
The homepage carries about 663 words of visible text.
5 checks passed
25 calls to action
The homepage has 25 calls to action, for example “Shop Golf”, “Shop All Apparel — Men's” and “Shop All Apparel — Women's”.
5 short forms
5 short forms (3 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager 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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
24 other companies contacted
Loading the homepage contacts 24 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 gtpplus.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 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Blocky Fraud Blocker · Essential Announcer · Microsoft Clarity · Helium Customer Fields · Essential Announcement Bar · Rivo Loyalty Rewards Referrals · Freegifts · merchantyard.com · pulseidconnect.com · getsitecontrol.com · bogos.io
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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on gtpplus.com, including 9 speed issues, 5 SEO issues and 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.