Website review, no card needed
gentemstick.com website review
Visit site (opens in a new tab)Reviewed 8 November 202624 issues · 76 checks
This review found 24 issues worth fixing on gentemstick.com, 6 of them high impact, across 76 checks. The most urgent: page weight: 7.0 MB in 136 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
Site score
85B- #16,047 of 118,247 reviewed websitesbeats 82%
- #10,204 of 67,198 online storesbeats 79%
- #9,917 of 61,274 Shopify storesbeats 78%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 97 ms |
| May 23, 2026 | 98 ms |
| May 30, 2026 | 97 ms |
| Jun 6, 2026 | 100 ms |
| Jun 13, 2026 | 101 ms |
| Jun 20, 2026 | 99 ms |
| Jun 27, 2026 | 94 ms |
| Jul 4, 2026 | 92 ms |
| Jul 11, 2026 | 87 ms |
| Jul 18, 2026 | 83 ms |
| Jul 25, 2026 | 86 ms |
| Aug 1, 2026 | 87 ms |
| Aug 8, 2026 | 87 ms |
| Aug 15, 2026 | 86 ms |
| Aug 22, 2026 | 86 ms |
| Aug 29, 2026 | 81 ms |
| Sep 5, 2026 | 83 ms |
| Sep 12, 2026 | 84 ms |
| Sep 19, 2026 | 86 ms |
| Sep 26, 2026 | 86 ms |
| Oct 3, 2026 | 84 ms |
| Oct 10, 2026 | 83 ms |
| Oct 17, 2026 | 83 ms |
| Oct 24, 2026 | 82 ms |
| Oct 31, 2026 | 86 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
How it loaded on a phone
1.1 s
2.2 s
3.3 s
4.4 s
5.5 s
6.6 s
7.7 s
8.8 s
Speed
Improve image delivery
450 ms · 829 KiB12 images could be 829 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
Mobile performance score: 61
61/100Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
450 ms · 303 KiBAbout 303 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Render-blocking requests
750 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, tidio.co and Shopify and others), adding 1.1 MB and 507 ms of main-thread time.
Main-thread work: 3.2 s
A phone's processor spends 3.2 s on main-thread work while loading, 963 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
tidio.co adds 111 ms
111 mstidio.co costs a phone 111 ms of main-thread work and 515 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.
Use efficient cache lifetimes
150 ms · 110 KiB12 files are served with short cache lifetimes, so returning visitors download them again (110 KiB).
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 177 ms. During a long task the page ignores taps.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Reduce unused CSS
60 ms · 20 KiBAbout 20 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 60 ms faster on a phone.
Legacy JavaScript
14 KiBPolyfills for old browsers add 14 KiB JavaScript that modern phones do not need.
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: 22 ms
22 msYour server sent the HTML in 22 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 21.2 s
21.2 sYour largest element takes 21.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “SNOWBOARDS”.
Time to Interactive: 27.2 s
27.2 sThe page becomes fully interactive after 27.2 s. Good is under 3.8 s.
Speed Index: 8.4 s
8.4 sVisually, the page fills in at 8.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 268 ms
268 msScripts block taps and scrolling for 268 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
10 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 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 104 ms
104 msReal visitors wait 104 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 506 ms
506 msReal visitors wait 506 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 97 ms to 86 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 38% faster for real visitors
-38%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.3 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Images and page weight
Page weight: 7.0 MB in 136 requests
7.0 MBYour homepage downloads 7.0 MB in 136 requests on a phone: fonts 3.2 MB (4), images 2.1 MB (28) and scripts 1.0 MB (49). Under 2 MB keeps phones on slow connections fast.
About 2.0 g of CO₂ per visit
1.99 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.99 g of CO₂e: 239.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 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.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
Alternative text of images should not be repeated as text (4 elements)
Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 21 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (194 characters)
Your meta description is 194 characters; Google truncates after about 160, so the end of your pitch is cut.
146 internal links, 4 external
The homepage links to 146 pages on gentemstick.com and 4 external pages.
7 checks passed
One H1 headline
Your main headline reads: “GENTEMSTICK”.
Title: 44 characters
Your title is a healthy 44 characters: “GENTEMSTICK Official Web l THE SNOWSURF SHOP”.
Canonical URL set
The canonical URL is https://gentemstick.com/.
Structured data in place
Structured data found: BreadcrumbList, 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://gentemstick.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://gentemstick.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Other pages
6 pages without an H1
https://gentemstick.com/collections/snowboards, https://gentemstick.com/pages/the-snowsurf-shop-hard-goods, https://gentemstick.com/pages/the-snowsurf-shop-apparel, https://gentemstick.com/pages/the-snowsurf-shop-accessories, https://gentemstick.com/pages/gentemstick-niseko-showroom-the-snowsurf-shop and https://gentemstick.com/pages/dealers 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 46 found) and read each the way a search engine does.
6 checks passed
Linked pages load
6 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 6 pages that loaded have a meta description.
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 6 pages that loaded have a <title>.
Best practices
14 small tap targets
14 of 33 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 117 words
The homepage has only about 117 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “PRE-ORDER”.
7 calls to action
The homepage has 7 calls to action, for example “PRE-ORDER”, “NISEKO SHOWROOM &THE SNOWSURF SHOP” and “CONTACT”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot 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.
19 cookies set on arrival
19Opening the homepage sets 19 cookies, 3 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.
18 other companies contacted
Loading the homepage contacts 18 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 gentemstick.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 24 issues on gentemstick.com, including 12 speed issues, 1 SEO issue 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.