Website review, no card needed
usfeel.com website review
Visit site (opens in a new tab)Reviewed 10 November 202636 issues · 81 checks
This review found 36 issues worth fixing on usfeel.com, 8 of them high impact, across 81 checks. The most urgent: render-blocking requests. 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- #62,126 of 94,338 reviewed websitesbeats 30%
- #37,496 of 50,609 online storesbeats 22%
- #35,234 of 45,742 Shopify storesbeats 19%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
Speed
Render-blocking requests
1.6 s16 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Mobile performance score: 72
72/100Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
310 ms · 110 KiBAbout 110 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 310 ms faster on a phone.
Improve image delivery
150 ms · 23 KiB4 images could be 23 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
7 third-party services on the page
7 third-party services load with your homepage (callback-button.app, Google CDN and Shopify and others), adding 526 KiB and 64 ms of main-thread time.
Use efficient cache lifetimes
95 KiB14 files are served with short cache lifetimes, so returning visitors download them again (95 KiB).
1 long task on the main thread
1 long task block the main thread while loading, the longest for 51 ms. During a long task the page ignores taps.
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 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.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 568 ms of it running JavaScript. That is comfortably low.
Server response: 15 ms
15 msYour server sent the HTML in 15 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 6.7 s
6.7 sYour largest element takes 6.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 6.7 s
6.7 sThe page becomes fully interactive after 6.7 s. Good is under 3.8 s.
Speed Index: 4.7 s
4.7 sVisually, the page fills in at 4.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
9 images without width and height
9 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Cumulative Layout Shift: 0.032
0.032The layout barely moves while loading (CLS 0.032, good is under 0.1).
Total Blocking Time: 1 ms
1 msScripts block the page for only 1 ms while loading. Good is under 200 ms.
Images and page weight
About 0.6 g of CO₂ per visit
0.55 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.55 g of CO₂e: 66.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 2.0 MB in 162 requests
2.0 MBYour homepage downloads 2.0 MB in 162 requests on a phone: other files 748 KiB (82), images 450 KiB (13) and scripts 385 KiB (42). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
8 text elements with low contrast
8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA input fields must have an accessible name (1 element)
ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
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.
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.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
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 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 11 images in the HTML carry an alt attribute.
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 9 failed. 1 more 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.
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 (164 characters)
Your meta description is 164 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
9 links crawlers can't follow
9 links have no real href, so search engines can't follow them.
55 internal links, 4 external
The homepage links to 55 pages on usfeel.com and 4 external pages.
4 checks passed
Title: 34 characters
Your title is a healthy 34 characters: “해외직구 구매대행 사이트 - USFEEL – usfeelcom”.
Canonical URL set
The canonical URL is https://www.usfeel.com/.
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.usfeel.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 (220 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.usfeel.com/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
6 linked pages are broken
Your homepage links to https://www.usfeel.com/pages/wishlist, https://www.usfeel.com/panacur-c-canine-dewormer-three-4-gram-packages-fenbendazole-br-%ED%8C%8C%EB%82%98%ED%81%90%EC%96%B4-c-4%EA%B7%B8%EB%9E%A8-3%ED%8C%A9-%ED%8C%AC%EB%B2%A4%EB%8B%A4%EC%A1%B8-%EA%B5%AC%EC%B6%A9%EC%A0%9C, https://www.usfeel.com/panacur-c-canine-dewormer-three-2-gram-packages-fenbendazole-br-%ED%8C%8C%EB%82%98%ED%81%90%EC%96%B4-c-2%EA%B7%B8%EB%9E%A8-3%ED%8C%A9-%ED%8C%AC%EB%B2%A4%EB%8B%A4%EC%A1%B8-%EA%B5%AC%EC%B6%A9%EC%A0%9C, https://www.usfeel.com/kal-3000-mg-ultra-pancreatin-tablets-100-count-br-kal-3000%EB%AF%B8%EB%A6%AC-%EC%9A%B8%ED%8A%B8%EB%9D%BC-%ED%8C%90%ED%81%AC%EB%A6%AC%ED%8B%B4-100%EC%A0%95, https://www.usfeel.com/theracurmin%C2%AE-hp-60-veg-capsules-br-%ED%85%8C%EB%9D%BC%ED%81%90%EB%AF%BC-hp-60-veg-%EC%A0%95 and https://www.usfeel.com/theracurmin%C2%AE-hp-120-veg-capsules, which answer with an error. Visitors hit a dead end and search engines drop them.
2 pages without a meta description
https://www.usfeel.com/collections/all and https://www.usfeel.com/blogs/news have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages share a meta description
https://www.usfeel.com/products/panacur-c-canine-dewormer-three-2-gram-packages-fenbendazole-br-%ED%8C%8C%EB%82%98%ED%81%90%EC%96%B4-c-2%EA%B7%B8%EB%9E%A8-3%ED%8C%A9-%ED%8C%AC%EB%B2%A4%EB%8B%A4%EC%A1%B8-%EA%B5%AC%EC%B6%A9%EC%A0%9C and https://www.usfeel.com/products/panacur-c-canine-dewormer-three-1-gram-packages-fenbendazole-br-%ED%8C%8C%EB%82%98%ED%81%90%EC%96%B4-c-1%EA%B7%B8%EB%9E%A8-3%ED%8C%A9-%ED%8C%AC%EB%B2%A4%EB%8B%A4%EC%A1%B8-%EA%B5%AC%EC%B6%A9%EC%A0%9C use the same meta description. A description written for each page earns more clicks.
6 links to non-canonical URLs
Your homepage links to 6 pages by a URL that isn't their canonical one, for example https://www.usfeel.com/products/panacur-c-canine-dewormer-three-4-gram-packages-fenbendazole-br-%ED%8C%8C%EB%82%98%ED%81%90%EC%96%B4-c-4%EA%B7%B8%EB%9E%A8-3%ED%8C%A9-%ED%8C%AC%EB%B2%A4%EB%8B%A4%EC%A1%B8-%EA%B5%AC%EC%B6%A9%EC%A0%9C, whose canonical is https://www.usfeel.com/products/panacur-c-canine-dewormer-three-4-gram-packages-fenbendazole-br-%ed%8c%8c%eb%82%98%ed%81%90%ec%96%b4-c-4%ea%b7%b8%eb%9e%a8-3%ed%8c%a9-%ed%8c%ac%eb%b2%a4%eb%8b%a4%ec%a1%b8-%ea%b5%ac%ec%b6%a9%ec%a0%9c. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
8 pages without an H1
https://www.usfeel.com/collections/all, https://www.usfeel.com/products/panacur-c-canine-dewormer-three-4-gram-packages-fenbendazole-br-%ED%8C%8C%EB%82%98%ED%81%90%EC%96%B4-c-4%EA%B7%B8%EB%9E%A8-3%ED%8C%A9-%ED%8C%AC%EB%B2%A4%EB%8B%A4%EC%A1%B8-%EA%B5%AC%EC%B6%A9%EC%A0%9C, https://www.usfeel.com/products/panacur-c-canine-dewormer-three-2-gram-packages-fenbendazole-br-%ED%8C%8C%EB%82%98%ED%81%90%EC%96%B4-c-2%EA%B7%B8%EB%9E%A8-3%ED%8C%A9-%ED%8C%AC%EB%B2%A4%EB%8B%A4%EC%A1%B8-%EA%B5%AC%EC%B6%A9%EC%A0%9C, https://www.usfeel.com/products/kal-3000-mg-ultra-pancreatin-tablets-100-count-br-kal-3000%EB%AF%B8%EB%A6%AC-%EC%9A%B8%ED%8A%B8%EB%9D%BC-%ED%8C%90%ED%81%AC%EB%A6%AC%ED%8B%B4-100%EC%A0%95, https://www.usfeel.com/products/theracurmin%C2%AE-hp-60-veg-capsules-br-%ED%85%8C%EB%9D%BC%ED%81%90%EB%AF%BC-hp-60-veg-%EC%A0%95 and https://www.usfeel.com/products/panacur-c-canine-dewormer-three-1-gram-packages-fenbendazole-br-%ED%8C%8C%EB%82%98%ED%81%90%EC%96%B4-c-1%EA%B7%B8%EB%9E%A8-3%ED%8C%A9-%ED%8C%AC%EB%B2%A4%EB%8B%A4%EC%A1%B8-%EA%B5%AC%EC%B6%A9%EC%A0%9C and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.usfeel.com/blogs/news has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 19 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 9 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 (“Unload event listeners are deprecated and will be removed.”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
34 of 34 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: 18 testimonial or review blocks. 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 165 words
The homepage has only about 165 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW!”.
4 calls to action
The homepage has 4 calls to action, for example “Shop now!”, “SUBSCRIBE” and “Contact Us”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Privacy and tracking
6 cookies set on arrival
6Opening the homepage sets 6 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.
9 other companies contacted
Loading the homepage contacts 9 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 usfeel.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 1 app. It is code from another company running for your shoppers.
Apps your storefront loads
callback-button.app
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
- The footer still says © 2019.
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on usfeel.com, including 8 speed issues, 5 SEO issues and 6 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.