Website review, no card needed
strike-mvmnt.com website review
Visit site (opens in a new tab)Reviewed 16 November 202629 issues · 72 checks
This review found 29 issues worth fixing on strike-mvmnt.com, 7 of them high impact, across 72 checks. The most urgent: reduce unused JavaScript. 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- #15,667 of 114,915 reviewed websitesbeats 82%
- #10,126 of 66,337 online storesbeats 79%
- #9,847 of 60,680 Shopify storesbeats 78%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 778 ms |
| Jun 6, 2026 | 778 ms |
| Jun 13, 2026 | 834 ms |
| Jun 20, 2026 | 810 ms |
| Jun 27, 2026 | 794 ms |
| Jul 4, 2026 | 777 ms |
| Jul 11, 2026 | 749 ms |
| Jul 18, 2026 | 747 ms |
| Jul 25, 2026 | 749 ms |
| Aug 1, 2026 | 769 ms |
| Aug 8, 2026 | 749 ms |
| Aug 15, 2026 | 786 ms |
| Aug 22, 2026 | 797 ms |
| Aug 29, 2026 | 781 ms |
| Sep 5, 2026 | 812 ms |
| Sep 12, 2026 | 802 ms |
| Sep 19, 2026 | 828 ms |
| Sep 26, 2026 | 855 ms |
| Oct 3, 2026 | 835 ms |
| Oct 10, 2026 | 862 ms |
| Oct 17, 2026 | 833 ms |
| Oct 24, 2026 | 820 ms |
| Oct 31, 2026 | 816 ms |
| Nov 7, 2026 | 768 ms |
| Nov 14, 2026 | 733 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 70 ms |
| Jun 6, 2026 | 71 ms |
| Jun 13, 2026 | 72 ms |
| Jun 20, 2026 | 73 ms |
| Jun 27, 2026 | 73 ms |
| Jul 4, 2026 | 71 ms |
| Jul 11, 2026 | 70 ms |
| Jul 18, 2026 | 70 ms |
| Jul 25, 2026 | 69 ms |
| Aug 1, 2026 | 69 ms |
| Aug 8, 2026 | 67 ms |
| Aug 15, 2026 | 70 ms |
| Aug 22, 2026 | 70 ms |
| Aug 29, 2026 | 70 ms |
| Sep 5, 2026 | 70 ms |
| Sep 12, 2026 | 70 ms |
| Sep 19, 2026 | 70 ms |
| Sep 26, 2026 | 70 ms |
| Oct 3, 2026 | 70 ms |
| Oct 10, 2026 | 71 ms |
| Oct 17, 2026 | 70 ms |
| Oct 24, 2026 | 70 ms |
| Oct 31, 2026 | 71 ms |
| Nov 7, 2026 | 71 ms |
| Nov 14, 2026 | 71 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
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
Reduce unused JavaScript
2.3 s · 398 KiBAbout 398 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.
Improve image delivery
1.3 s · 502 KiB11 images could be 502 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.
Mobile performance score: 67
67/100Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Klaviyo and rise-ai.com and others), adding 927 KiB and 553 ms of main-thread time.
Legacy JavaScript
400 ms · 58 KiBPolyfills for old browsers add 58 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.
Google Tag Manager adds 300 ms
300 msGoogle Tag Manager costs a phone 300 ms of main-thread work and 443 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.
Render-blocking requests
300 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
Main-thread work: 2.4 s
A phone's processor spends 2.4 s on main-thread work while loading, 862 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
150 ms · 170 KiB9 files are served with short cache lifetimes, so returning visitors download them again (170 KiB).
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 180 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 20 KiBAbout 20 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.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.
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: 13.5 s
13.5 sYour largest element takes 13.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: 13.5 s
13.5 sThe page becomes fully interactive after 13.5 s. Good is under 3.8 s.
Speed Index: 4.9 s
4.9 sVisually, the page fills in at 4.9 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 213 ms
213 msScripts block taps and scrolling for 213 ms in total while the page loads. Good is under 200 ms.
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.
11 images without width and height
11 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 70 ms to 71 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 0.8 s to 0.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 86 ms
86 msReal visitors wait 86 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 385 ms
385 msReal visitors wait 385 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.015
0.015The layout barely moves while loading (CLS 0.015, good is under 0.1).
Images and page weight
Page weight: 3.1 MB in 203 requests
3.1 MBYour homepage downloads 3.1 MB in 203 requests on a phone: scripts 1.1 MB (62), images 1.1 MB (23) and other files 788 KiB (109). Under 2 MB keeps phones on slow connections fast.
About 0.9 g of CO₂ per visit
0.88 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.88 g of CO₂e: 106.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Delayed refresh under 20 hours must not be used (1 element)
Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
ARIA input fields do not have accessible names
ARIA input fields do not have accessible names (2 elements).
ARIA toggle fields do not have accessible names
ARIA toggle fields do not have accessible names (2 elements).
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.
2 checks passed
Every image has alt text
All 19 images in the HTML carry an alt attribute.
20 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 23 WCAG 2.2 A/AA and best-practice rules on the phone render: 20 passed and 3 failed. 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.
Meta description is long (192 characters)
Your meta description is 192 characters; Google truncates after about 160, so the end of your pitch is cut.
92 internal links, 17 external
The homepage links to 92 pages on strike-mvmnt.com and 17 external pages.
6 checks passed
One H1 headline
Your main headline reads: “STRIKE MVMNT”.
Title: 64 characters
Your title is a healthy 64 characters: “STRIKE MVMNT | Athletic footwear and apparel | UNITED BY MOTION®”.
Canonical URL set
The canonical URL is https://strike-mvmnt.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://strike-mvmnt.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.
No llms.txt
There is no https://strike-mvmnt.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.
1 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.
Other pages
2 pages without a meta description
https://strike-mvmnt.com/collections/shop-all-footwear and https://strike-mvmnt.com/collections/transit-street-trainer have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 40 found) and read each the way a search engine does.
6 checks passed
Linked pages load
2 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.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 2 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 “Failed to load resource: the server responded with a status of 429 ()”.
1 checks passed
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.
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 10 words
The homepage has only about 10 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.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
3 checks passed
4 calls to action
The homepage has 4 calls to action, for example “SHOP ALL”, “SHOP” and “CONTACT US”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
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.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 strike-mvmnt.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 3 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · rise-ai.com · addons.business
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
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Company
- Headquarters
- Vancouver
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on strike-mvmnt.com, including 14 speed issues, 2 SEO issues and 4 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.