Website review, no card needed
gushill.com website review
Visit site (opens in a new tab)Reviewed 11 November 202634 issues · 75 checks
This review found 34 issues worth fixing on gushill.com, 6 of them high impact, across 75 checks. The most urgent: 1 tap target too small. 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Mobile performance score: 64
64/100Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
700 ms · 127 KiB12 files are served with short cache lifetimes, so returning visitors download them again (127 KiB).
Improve image delivery
100 ms · 714 KiB33 images could be 714 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.
Reduce unused JavaScript
450 ms · 116 KiBAbout 116 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
550 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.
2,278 HTML elements
The page has 2,278 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 2.3 s
A phone's processor spends 2.3 s on main-thread work while loading, 697 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
150 ms · 76 KiBAbout 76 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
6 third-party services on the page
6 third-party services load with your homepage (Yotpo, Shopify and Key CDN and others), adding 316 KiB and 172 ms of main-thread time.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 135 ms. During a long task the page ignores taps.
Legacy JavaScript
8 KiBPolyfills for old browsers add 8 KiB JavaScript that modern phones do not need.
Minify CSS
7 KiB7 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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 9.8 s
9.8 sYour largest element takes 9.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Durable Metal & A Fully Encased Design GusHill trailer hitc…”.
Time to Interactive: 10.1 s
10.1 sThe page becomes fully interactive after 10.1 s. Good is under 3.8 s.
Speed Index: 6.8 s
6.8 sVisually, the page fills in at 6.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
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
Total Blocking Time: 111 ms
111 msScripts block the page for only 111 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.7 MB in 184 requests
2.7 MBYour homepage downloads 2.7 MB in 184 requests on a phone: images 1.1 MB (54), other files 688 KiB (79) and scripts 411 KiB (37). Under 2 MB keeps phones on slow connections fast.
14 images below the first screen load straight away
14 images further down the page (457 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images far larger than shown
66 KiB2 images are downloaded at several times the size a phone draws them, for example GH40030-MainImage_450x.jpg at 450 px wide, shown at 90 px. Resized copies would save about 66 KiB.
About 0.8 g of CO₂ per visit
0.76 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.76 g of CO₂e: 90.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
14 images without alt text
14 images have no alt text, which hurts accessibility and image search.
[role]s are not contained by their required parent element
[role]s are not contained by their required parent element (1 element).
All page content should be contained by landmarks (14 elements)
All page content should be contained by landmarks: 14 elements on the page fail this check, rated moderate by axe-core.
69 links without text
69 visible links have no text or label, so screen readers cannot say where they go.
Hidden but focusable
2 elements hidden from screen readers can still receive keyboard focus.
Headings skip levels
Headings skip levels (h1 → h3, h3 → h5 and h1 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
4 H1 headlines
There are 4 <h1> headlines (“My Cart (0)”, “GusHill Collection” and “Why GusHill?”). One clear main headline is easier for people and search engines.
Meta description is long (299 characters)
Your meta description is 299 characters; Google truncates after about 160, so the end of your pitch is cut.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
94 internal links, 5 external
The homepage links to 94 pages on gushill.com and 5 external pages.
5 checks passed
Title: 56 characters
Your title is a healthy 56 characters: “GusHill USA | Most Tamperproof Lock System On The Market”.
Canonical URL set
The canonical URL is https://www.gushill.com/.
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.gushill.com/sitemap.xml.
AI search readiness
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 (473 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.gushill.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://www.gushill.com/collections/hasp is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://www.gushill.com/collections/hasp has no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.gushill.com/collections/accessories/products/additional-keys, whose canonical is https://www.gushill.com/products/additional-keys. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
3 pages slow to respond
https://www.gushill.com/products/the-plug, https://www.gushill.com/products/the-puck-lock-2-pack and https://www.gushill.com/products/the-puck-lock took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 44 found) and read each the way a search engine does.
4 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Maximum call stack size exceeded.”.
2 checks passed
Tap targets are thumb-sized
32 of 38 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 6 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 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 622 words of copy
The homepage carries about 622 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: “SHOP ADDITIONAL KEYS” and “contact us”.
7 calls to action
The homepage has 7 calls to action, for example “Shop additional keys”, “Contact Us” and “Shop Now”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads 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.
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.
11 other companies contacted
Loading the homepage contacts 11 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 gushill.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 2 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
kxcdn.com · nfcube.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
- Framework
- jQuery
- 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 34 issues on gushill.com, including 12 speed issues, 4 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.