Website review, no card needed
1clickproduct.com website review
Visit site (opens in a new tab)Reviewed 3 November 202629 issues · 85 checks
This review found 29 issues worth fixing on 1clickproduct.com, 11 of them high impact, across 85 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
75C- #79,069 of 120,386 reviewed websitesbeats 30%
- #50,434 of 68,161 online storesbeats 22%
- #47,655 of 62,115 Shopify storesbeats 19%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.0 s |
| May 23, 2026 | 3.0 s |
| May 30, 2026 | 3.0 s |
| Jun 6, 2026 | 3.0 s |
| Jun 13, 2026 | 3.1 s |
| Jun 20, 2026 | 3.2 s |
| Jun 27, 2026 | 3.4 s |
| Jul 4, 2026 | 3.5 s |
| Jul 11, 2026 | 3.5 s |
| Jul 18, 2026 | 3.5 s |
| Jul 25, 2026 | 3.5 s |
| Aug 1, 2026 | 3.4 s |
| Aug 8, 2026 | 3.4 s |
| Aug 15, 2026 | 3.4 s |
| Aug 22, 2026 | 3.4 s |
| Aug 29, 2026 | 3.4 s |
| Sep 5, 2026 | 3.4 s |
| Sep 12, 2026 | 3.4 s |
| Sep 19, 2026 | 3.4 s |
| Sep 26, 2026 | 3.4 s |
| Oct 3, 2026 | 3.4 s |
| Oct 10, 2026 | 3.4 s |
| Oct 17, 2026 | 3.4 s |
| Oct 24, 2026 | 3.4 s |
| Oct 31, 2026 | 3.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 226 ms |
| May 23, 2026 | 232 ms |
| May 30, 2026 | 238 ms |
| Jun 6, 2026 | 245 ms |
| Jun 13, 2026 | 251 ms |
| Jun 20, 2026 | 254 ms |
| Jun 27, 2026 | 257 ms |
| Jul 4, 2026 | 262 ms |
| Jul 11, 2026 | 261 ms |
| Jul 18, 2026 | 257 ms |
| Jul 25, 2026 | 253 ms |
| Aug 1, 2026 | 248 ms |
| Aug 8, 2026 | 247 ms |
| Aug 15, 2026 | 250 ms |
| Aug 22, 2026 | 248 ms |
| Aug 29, 2026 | 248 ms |
| Sep 5, 2026 | 247 ms |
| Sep 12, 2026 | 246 ms |
| Sep 19, 2026 | 246 ms |
| Sep 26, 2026 | 244 ms |
| Oct 3, 2026 | 243 ms |
| Oct 10, 2026 | 243 ms |
| Oct 17, 2026 | 241 ms |
| Oct 24, 2026 | 243 ms |
| Oct 31, 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
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
Render-blocking requests
650 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.
Reduce unused JavaScript
249 KiBAbout 249 KiB of JavaScript is downloaded but never used on this page.
Improve image delivery
233 KiB8 images could be 233 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 146 ms. During a long task the page ignores taps.
Legacy JavaScript
48 KiBPolyfills for old browsers add 48 KiB JavaScript that modern phones do not need.
1 third-party service on the page
1 third-party service load with your homepage (Google Tag Manager), adding 87 KiB and 35 ms of main-thread time.
Reduce unused CSS
17 KiBAbout 17 KiB of CSS is downloaded but never applied on this page.
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.
3 checks passed
Mobile performance score: 99
99/100Your mobile performance score is 99. That is in Google's “good” band (90 and up).
Main-thread work: 1.0 s
A phone's processor spends 1.0 s on main-thread work while loading, 432 ms of it running JavaScript. That is comfortably low.
Server response: 40 ms
40 msYour server sent the HTML in 40 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 TTFB: 1.9 s
1.9 sReal visitors wait 1.9 s for your server to start answering (75th percentile). Good is under 800 ms.
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 LCP: 3.3 s
3.3 sReal visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 244 ms
244 msReal visitors wait 244 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.5 s
2.5 sReal visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.
14 images without width and height
14 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 226 ms to 243 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.0 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
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.8 s
2.8 sVisually, the page fills in at 2.8 s (Speed Index), inside the 3.4 s “good” threshold.
Total Blocking Time: 89 ms
89 msScripts block the page for only 89 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).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Largest Contentful Paint: 1.1 s
1.1 sYour largest element renders in 1.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Paste a product link from Amazon, AliExpress or eBay, or a …”.
Images and page weight
2 images in older formats
2 images (145 KiB) 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.
About 0.5 g of CO₂ per visit
0.50 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.50 g of CO₂e: 59.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.7 MB in 77 requests
1.7 MBYour homepage downloads 1.7 MB in 77 requests on a phone: images 954 KiB (36), scripts 573 KiB (20) and fonts 180 KiB (4). That is a lean page.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
[role="img"] and [role="image"] elements must have alternative text (21 elements)
[role="img"] and [role="image"] elements must have alternative text: 21 elements on the page fail this check, rated serious by axe-core.
Hidden but focusable
3 elements hidden from screen readers can still receive keyboard focus.
Interactive controls must not be nested (3 elements)
Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
11 images without alt text
11 images have no alt text, which hurts accessibility and image search.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 6 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 (107 characters)
Your title is 107 characters, so Google will cut it off around 60: “1Click: Copy Product Importer - Import products from suppliers and rewrite them with AI |…”.
Structured data has 1 problem
Structured data found (SoftwareApplication) but with 1 problem, for example “SoftwareApplication: no offers (price) block”.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
54 internal links, 27 external
The homepage links to 54 pages on 1clickproduct.com and 27 external pages.
6 checks passed
Meta description: 150 characters
Your meta description is 150 characters: “Paste a product link from Amazon, AliExpress or eBay, or a product or collection link from a store you manage, and 1Cli…”.
One H1 headline
Your main headline reads: “1Click: Copy Product Importer”.
Canonical URL set
The canonical URL is https://apps.shopify.com/1clickproduct.
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://apps.shopify.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.
Parts of the site are closed to 3 AI crawlers
Your robots.txt lets ChatGPT (ChatGPT-User), Claude (Claude-User) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.
No llms.txt
There is no https://apps.shopify.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
Text is in the HTML
Your server sends the page's text in the HTML (1,056 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages share a meta description
/, https://apps.shopify.com/stories and https://apps.shopify.com/partners/ecomfusion use the same meta description. A description written for each page earns more clicks.
1 page without an H1
/ has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 26 found) and read each the way a search engine does.
6 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.
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
1 broken image
1 image failed to load on a phone, for example https://apps.shopify.com/1clickproduct.
14 small tap targets
14 of 19 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
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.
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 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 557 words of copy
The homepage carries about 557 words of visible text.
4 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Start for free”, “Try Shopify free for 3 days” and “Sign up”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block, a star rating and 2 trust badges.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads 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.
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.
3 other companies contacted
Loading the homepage contacts 3 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 1clickproduct.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google Analytics
- Hosting
- Cloudflare
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 1clickproduct.com, including 8 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.