Website review, no card needed
addshoppers.com website review
Visit site (opens in a new tab)Reviewed 21 October 202622 issues · 65 checks
This review found 22 issues worth fixing on addshoppers.com, 4 of them high impact, across 65 checks. The most urgent: fails Core Web Vitals for real visitors. 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
81BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.0 s |
| May 9, 2026 | 2.0 s |
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.4 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 179 ms |
| May 9, 2026 | 184 ms |
| May 16, 2026 | 183 ms |
| May 23, 2026 | 182 ms |
| May 30, 2026 | 183 ms |
| Jun 6, 2026 | 186 ms |
| Jun 13, 2026 | 190 ms |
| Jun 20, 2026 | 185 ms |
| Jun 27, 2026 | 182 ms |
| Jul 4, 2026 | 176 ms |
| Jul 11, 2026 | 173 ms |
| Jul 18, 2026 | 181 ms |
| Jul 25, 2026 | 180 ms |
| Aug 1, 2026 | 183 ms |
| Aug 8, 2026 | 186 ms |
| Aug 15, 2026 | 187 ms |
| Aug 22, 2026 | 191 ms |
| Aug 29, 2026 | 196 ms |
| Sep 5, 2026 | 205 ms |
| Sep 12, 2026 | 212 ms |
| Sep 19, 2026 | 220 ms |
| Sep 26, 2026 | 219 ms |
| Oct 3, 2026 | 220 ms |
| Oct 10, 2026 | 236 ms |
| Oct 17, 2026 | 243 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
Speed
Mobile performance score: 75
75/100Your mobile performance score is 75 (desktop: 97). Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
150 ms · 433 KiB7 files are served with short cache lifetimes, so returning visitors download them again (433 KiB).
Reduce unused JavaScript
150 ms · 272 KiBAbout 272 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Render-blocking requests
150 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 102 ms. During a long task the page ignores taps.
Legacy JavaScript
14 KiBPolyfills for old browsers add 14 KiB JavaScript that modern phones do not need.
1 third-party service on the page
1 third-party service load with your homepage (Adobe TypeKit), adding 130 KiB and 0 ms of main-thread time.
2 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 509 ms of it running JavaScript. That is comfortably low.
Server response: 17 ms
17 msYour server sent the HTML in 17 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: 5.8 s
5.8 sYour largest element takes 5.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Minty AI Shopping Assistant”.
Time to Interactive: 7.6 s
7.6 sThe page becomes fully interactive after 7.6 s. Good is under 3.8 s.
Real-user INP: 238 ms
238 msReal visitors wait 238 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 32% slower for real visitors
+32%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 179 ms to 243 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 963 ms
963 msReal visitors wait 963 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
Largest content (LCP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Speed Index: 2.4 s
2.4 sVisually, the page fills in at 2.4 s (Speed Index), inside the 3.4 s “good” threshold.
Total Blocking Time: 70 ms
70 msScripts block the page for only 70 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.006
0.006The layout barely moves while loading (CLS 0.006, good is under 0.1).
Images and page weight
Page weight: 2.0 MB in 78 requests
2.0 MBYour homepage downloads 2.0 MB in 78 requests on a phone: scripts 758 KiB (36), other files 545 KiB (16) and images 485 KiB (18). Under 2 MB keeps phones on slow connections fast.
About 0.6 g of CO₂ per visit
0.58 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.58 g of CO₂e: 69.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 checks passed
Every image has alt text
All 23 images in the HTML carry an alt attribute.
28 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 29 WCAG 2.2 A/AA and best-practice rules on the phone render: 28 passed and 1 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (170 characters)
Your meta description is 170 characters; Google truncates after about 160, so the end of your pitch is cut.
52 internal links, 14 external
The homepage links to 52 pages on addshoppers.com and 14 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Save up to 5x more with AI”.
Title: 42 characters
Your title is a healthy 42 characters: “Minty - Your AI-Powered Shopping Companion”.
Canonical URL set
The canonical URL is https://www.minty.com/.
Structured data in place
Structured data found: Dataset, MobileApplication, Organization, SoftwareApplication 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.minty.com/sitemap.xml.
AI search readiness
Opted out of AI training for 1 crawler
robots.txt blocks Applebot-Extended, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
llms.txt published
The site publishes https://www.minty.com/llms.txt (3 KiB, 19 links), a plain-text guide to the site for AI tools.
Other pages
3 pages share a meta description
https://www.minty.com/s/all-stores, https://www.minty.com/s/all-stores/A and https://www.minty.com/s/all-stores/B use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 50 found) and read each the way a search engine does.
7 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
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 15 pages that loaded have a <title>.
Best practices
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “TypeError: Cannot read properties of undefined (reading 'register')”.
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.
Thin social proof
Social proof on the homepage: a star rating. 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.
Only about 59 words
The homepage has only about 59 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
1 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact”.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 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.
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 addshoppers.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 22 issues on addshoppers.com, including 11 speed issues, 1 SEO issue and 5 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.