Website review, no card needed
shinearmor.com website review
Visit site (opens in a new tab)Reviewed 6 November 202649 issues · 93 checks
This review found 49 issues worth fixing on shinearmor.com, 20 of them high impact, across 93 checks. The most urgent: improve image delivery. 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
70C- #96,050 of 114,596 reviewed websitesbeats 14%
- #59,608 of 66,250 online storesbeats 8%
- #55,420 of 60,622 Shopify storesbeats 7%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 6.2 s |
| May 23, 2026 | 6.2 s |
| May 30, 2026 | 6.2 s |
| Jun 6, 2026 | 6.2 s |
| Jun 13, 2026 | 6.3 s |
| Jun 20, 2026 | 6.2 s |
| Jun 27, 2026 | 6.2 s |
| Jul 4, 2026 | 6.1 s |
| Jul 11, 2026 | 6.2 s |
| Jul 18, 2026 | 6.2 s |
| Jul 25, 2026 | 6.2 s |
| Aug 1, 2026 | 6.2 s |
| Aug 8, 2026 | 6.2 s |
| Aug 15, 2026 | 6.2 s |
| Aug 22, 2026 | 6.2 s |
| Aug 29, 2026 | 6.2 s |
| Sep 5, 2026 | 6.3 s |
| Sep 12, 2026 | 6.3 s |
| Sep 19, 2026 | 6.3 s |
| Sep 26, 2026 | 6.3 s |
| Oct 3, 2026 | 6.2 s |
| Oct 10, 2026 | 6.3 s |
| Oct 17, 2026 | 6.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 156 ms |
| May 23, 2026 | 147 ms |
| May 30, 2026 | 121 ms |
| Jun 6, 2026 | 123 ms |
| Jun 13, 2026 | 125 ms |
| Jun 20, 2026 | 112 ms |
| Jun 27, 2026 | 112 ms |
| Jul 4, 2026 | 105 ms |
| Jul 11, 2026 | 108 ms |
| Jul 18, 2026 | 112 ms |
| Jul 25, 2026 | 113 ms |
| Aug 1, 2026 | 109 ms |
| Aug 8, 2026 | 106 ms |
| Aug 15, 2026 | 114 ms |
| Aug 22, 2026 | 119 ms |
| Aug 29, 2026 | 129 ms |
| Sep 5, 2026 | 142 ms |
| Sep 12, 2026 | 127 ms |
| Sep 19, 2026 | 120 ms |
| Sep 26, 2026 | 121 ms |
| Oct 3, 2026 | 116 ms |
| Oct 10, 2026 | 121 ms |
| Oct 17, 2026 | 137 ms |
| Oct 24, 2026 | 133 ms |
| Oct 31, 2026 | 146 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.8 s
1.5 s
2.3 s
3.1 s
3.8 s
4.6 s
5.4 s
6.1 s
Speed
Improve image delivery
5.8 s · 10.5 MB99 images could be 10.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.8 s faster on a phone.
Reduce unused JavaScript
3.6 s · 502 KiBAbout 502 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.6 s faster on a phone.
Use efficient cache lifetimes
1.0 s · 166 KiB26 files are served with short cache lifetimes, so returning visitors download them again (166 KiB).
Mobile performance score: 34
34/100Your mobile performance score is 34. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.7 s
A phone's processor spends 6.7 s on main-thread work while loading, 3.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Accessibe Accessibility Overlay and Snapchat and others), adding 827 KiB and 1.9 s of main-thread time.
Reduce unused CSS
900 ms · 87 KiBAbout 87 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
Render-blocking requests
800 ms11 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
Google Tag Manager adds 656 ms
656 msGoogle Tag Manager costs a phone 656 ms of main-thread work and 312 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 460 ms. During a long task the page ignores taps.
Font display
350 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).
Accessibe Accessibility Overlay adds 317 ms
317 msAccessibe Accessibility Overlay costs a phone 317 ms of main-thread work and 250 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.
Snapchat adds 270 ms
270 msSnapchat costs a phone 270 ms of main-thread work and 55 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.
Legacy JavaScript
200 ms · 35 KiBPolyfills for old browsers add 35 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
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: 6 ms
6 msYour server sent the HTML in 6 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.
Real-user LCP: 6.2 s
6.2 sReal visitors wait 6.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 6.2 s
6.2 sReal visitors see the first content after 6.2 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 53.2 s
53.2 sYour largest element takes 53.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Reveal-your shine”.
Time to Interactive: 55.9 s
55.9 sThe page becomes fully interactive after 55.9 s. Good is under 3.8 s.
Speed Index: 12.6 s
12.6 sVisually, the page fills in at 12.6 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.7 s
1.7 sScripts block taps and scrolling for 1.7 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 156 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 6.2 s to 6.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 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.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 663 ms
663 msReal visitors wait 663 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 14.4 MB in 383 requests
14.4 MBYour homepage downloads 14.4 MB in 383 requests on a phone: images 11.7 MB (114), scripts 1.4 MB (87) and other files 865 KiB (154). Under 2 MB keeps phones on slow connections fast.
39 images far larger than shown
6.5 MB39 images are downloaded at several times the size a phone draws them, for example BIG-BUNDLE_mobile.webp at 3,011 px wide, shown at 390 px. Resized copies would save about 6.5 MB.
1 image over 500 KB
BIG-BUNDLE_mobile.webp weighs 748 KiB. On a phone connection a single image that size takes seconds.
20 images in older formats
20 images (3.8 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.
An image on the first screen is lazy-loaded
BIG-BUNDLE_mobile.webp 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 4.1 g of CO₂ per visit
4.08 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.08 g of CO₂e: 489.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
12 text elements with low contrast
12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (8 elements)
Scrollable region must have keyboard access: 8 elements on the page fail this check, rated serious by axe-core.
6 images without alt text
6 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (57 elements)
All page content should be contained by landmarks: 57 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
10 form fields without a label
10 form fields have no label, so screen readers announce an empty box and autofill guesses.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (67 characters)
Your title is 67 characters, so Google will cut it off around 60: “Auto Detailing Supplies | Best Car Detailing Products | Shine Armor”.
Meta description is long (211 characters)
Your meta description is 211 characters; Google truncates after about 160, so the end of your pitch is cut.
67 internal links, 7 external
The homepage links to 67 pages on shinearmor.com and 7 external pages.
6 checks passed
One H1 headline
Your main headline reads: “<img class="" src="//www.shinearmor.com/cdn/shop/files/shine-armor-logo_1000x1000.png?v=1678198420" alt="Shine Armor" i…”.
Canonical URL set
The canonical URL is https://www.shinearmor.com/.
Structured data in place
Structured data found: BreadcrumbList, HowTo 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://www.shinearmor.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 (815 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.shinearmor.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 linked pages are broken
Your homepage links to https://www.shinearmor.com/collections/gear and https://www.shinearmor.com/collections/car-detailing-products, which answer with an error. Visitors hit a dead end and search engines drop them.
2 pages without a meta description
https://www.shinearmor.com/pages/holiday-landing and https://www.shinearmor.com/collections/homepage-best-sellers have 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.shinearmor.com/pages/holiday-landing, whose canonical is https://www.shinearmor.com/pages/detailing-bundle. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://www.shinearmor.com/pages/holiday-landing has no <h1> headline, so visitors and search engines get no clear main topic.
10 pages slow to respond
https://www.shinearmor.com/collections/interior, https://www.shinearmor.com/collections/kits, https://www.shinearmor.com/collections/best-sellers, https://www.shinearmor.com/pages/holiday-landing, https://www.shinearmor.com/products/fortify-quick-coat and https://www.shinearmor.com/products/shine-armor-graphene-ceramic-spray and 4 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 30 found) and read each the way a search engine does.
3 checks passed
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 13 pages that loaded have a <title>.
Best practices
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Missing source maps
Large scripts ship without source maps.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
32 of 32 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 8 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 539 words of copy
The homepage carries about 539 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Now”.
18 calls to action
The homepage has 18 calls to action, for example “Shop Now” and “Contact Us”.
10 short forms
10 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, Meta Pixel and Microsoft Ads and 4 mores (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.
25 cookies set on arrival
25Opening the homepage sets 25 cookies, 2 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.
50 other companies contacted
Loading the homepage contacts 50 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 shinearmor.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 8 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Bnb App Amazon Buy Now Button · azureedge.net · snapchat.com · trafficmanager.net · stamped.io · cjpowered.com · cloudfront.net
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
- Google Analytics | Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- Saint Petersburg
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 49 issues on shinearmor.com, including 21 speed issues, 2 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.