Website review, no card needed
staystrongbrand.com website review
Visit site (opens in a new tab)Reviewed 16 November 202638 issues · 78 checks
This review found 38 issues worth fixing on staystrongbrand.com, 11 of them high impact, across 78 checks. The most urgent: use efficient cache lifetimes. 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
How it loaded on a phone
0.6 s
1.3 s
1.9 s
2.5 s
3.2 s
3.8 s
4.4 s
5.1 s
Speed
Use efficient cache lifetimes
3.6 s · 3.4 MB142 files are served with short cache lifetimes, so returning visitors download them again (3.4 MB).
Render-blocking requests
2.1 s40 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.
Improve image delivery
300 ms · 2.2 MB25 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Mobile performance score: 69
69/100Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
450 ms · 91 KiBAbout 91 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.
Reduce unused CSS
450 ms · 83 KiBAbout 83 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.
Minify CSS
150 ms · 21 KiB21 KiB could be saved by minifying CSS.
Minify JavaScript
150 ms · 18 KiB18 KiB could be saved by minifying JavaScript.
Legacy JavaScript
6 KiBPolyfills for old browsers add 6 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.
2 checks passed
Main-thread work: 1.0 s
A phone's processor spends 1.0 s on main-thread work while loading, 313 ms of it running JavaScript. That is comfortably low.
Server response: 105 ms
105 msYour server sent the HTML in 105 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 9.6 s
9.6 sYour largest element takes 9.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Slide background”.
Time to Interactive: 10.1 s
10.1 sThe page becomes fully interactive after 10.1 s. Good is under 3.8 s.
Real-user LCP: 3.5 s
3.5 sReal visitors wait 3.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.3 s
1.3 sReal visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 5.8 s
5.8 sVisually, the page fills in at 5.8 s (Speed Index). Good is under 3.4 s.
14 images without width and height
14 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 114 ms to 107 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user INP: 141 ms
141 msReal visitors wait 141 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
Largest content (LCP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.3 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.042
0.042The layout barely moves while loading (CLS 0.042, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
13 images far larger than shown
2.0 MB13 images are downloaded at several times the size a phone draws them, for example banner-home-2500x572-world_20260511163143.jpg at 2,500 px wide, shown at 390 px. Resized copies would save about 2.0 MB.
Page weight: 3.5 MB in 143 requests
3.5 MBYour homepage downloads 3.5 MB in 143 requests on a phone: images 2.8 MB (40), scripts 421 KiB (52) and stylesheets 177 KiB (44). Under 2 MB keeps phones on slow connections fast.
15 images in older formats
15 images (2.2 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.
10 images below the first screen load straight away
10 images further down the page (1.5 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
9e1c0158143b3173e4b7_staystrong-banner-home-1903x930-grailc1 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).
About 1.0 g of CO₂ per visit
0.98 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.98 g of CO₂e: 117.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Positive tabindex
1 element has a tabindex above 0, which scrambles the keyboard order.
24 images without alt text
24 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
1 form field without a label
1 form field has 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.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
29 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 31 WCAG 2.2 A/AA and best-practice rules on the phone render: 29 passed and 2 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (11 characters)
Your title is only 11 characters: “Stay Strong”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is short (21 characters)
Your meta description is only 21 characters: “Shop powered by HBSYS”. 70 to 160 characters is enough to sell the click.
Structured data has 1 problem
Structured data found (Organization, WebPage and WebSite) but with 1 problem, for example “WebSite: missing name”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.staystrongbrand.com/sitemap.xml, so Google discovers your pages only by following links.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
29 internal links, 16 external
The homepage links to 29 pages on staystrongbrand.com and 16 external pages.
2 checks passed
Canonical URL set
The canonical URL is https://www.staystrongbrand.com/.
robots.txt in place
robots.txt is in place.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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.
Text is in the HTML
Your server sends the page's text in the HTML (693 words), so crawlers that don't run JavaScript still read it.
Other pages
4 linked pages are broken
Your homepage links to https://www.staystrongbrand.com/127-frames, https://www.staystrongbrand.com/268-staystrong-parts, https://www.staystrongbrand.com/118-gear and https://www.staystrongbrand.com/161-casual, which answer with an error. Visitors hit a dead end and search engines drop them.
7 pages without a meta description
https://www.staystrongbrand.com/114-bikes, https://www.staystrongbrand.com/160-miscellaneous, https://www.staystrongbrand.com/169-complete-your-bike, https://www.staystrongbrand.com/135-tools, https://www.staystrongbrand.com/112-outlet and https://www.staystrongbrand.com/277-grips and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
8 pages without an H1
https://www.staystrongbrand.com/114-bikes, https://www.staystrongbrand.com/160-miscellaneous, https://www.staystrongbrand.com/169-complete-your-bike, https://www.staystrongbrand.com/135-tools, https://www.staystrongbrand.com/112-outlet and https://www.staystrongbrand.com/277-grips and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://www.staystrongbrand.com/160-miscellaneous, https://www.staystrongbrand.com/169-complete-your-bike and https://www.staystrongbrand.com/112-outlet took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 17 found) and read each the way a search engine does.
4 checks passed
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 11 pages that loaded have a <title>.
Best practices
3 distorted images
3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
3 low-resolution images
3 images are served at too low a resolution for sharp phone screens.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
31 of 35 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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 557 words of copy
The homepage carries about 557 words of visible text.
4 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Subscribe” and “Contact us”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 76 testimonial or review blocks and 3 trust badges.
Direct contact links
Visitors can reach you directly: 2 phone links and 1 email link.
Privacy and tracking
4 cookies set on arrival
4Opening the homepage sets 4 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.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 staystrongbrand.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 38 issues on staystrongbrand.com, including 15 speed issues, 6 SEO issues 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.