Website review, no card needed
jinny.com website review
Visit site (opens in a new tab)Reviewed 22 October 202633 issues · 82 checks
This review found 33 issues worth fixing on jinny.com, 5 of them high impact, across 82 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
86B- #9,116 of 92,113 reviewed websitesbeats 86%
- #5,268 of 48,853 online storesbeats 85%
- #5,096 of 44,038 Shopify storesbeats 83%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.0 s |
| May 9, 2026 | 1.9 s |
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 103 ms |
| May 9, 2026 | 94 ms |
| May 16, 2026 | 91 ms |
| May 23, 2026 | 88 ms |
| May 30, 2026 | 87 ms |
| Jun 6, 2026 | 95 ms |
| Jun 13, 2026 | 98 ms |
| Jun 20, 2026 | 99 ms |
| Jun 27, 2026 | 95 ms |
| Jul 4, 2026 | 89 ms |
| Jul 11, 2026 | 88 ms |
| Jul 18, 2026 | 94 ms |
| Jul 25, 2026 | 99 ms |
| Aug 1, 2026 | 103 ms |
| Aug 8, 2026 | 103 ms |
| Aug 15, 2026 | 97 ms |
| Aug 22, 2026 | 94 ms |
| Aug 29, 2026 | 89 ms |
| Sep 5, 2026 | 89 ms |
| Sep 12, 2026 | 93 ms |
| Sep 19, 2026 | 94 ms |
| Sep 26, 2026 | 96 ms |
| Oct 3, 2026 | 94 ms |
| Oct 10, 2026 | 95 ms |
| Oct 17, 2026 | 95 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
5,758 HTML elements
The page has 5,758 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
950 ms · 634 KiB30 images could be 634 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 950 ms faster on a phone.
Mobile performance score: 70
70/100Your mobile performance score is 70 (desktop: 94). Pages that score under 90 lose visitors before the first paint.
Main-thread work: 2.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 784 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Klaviyo adds 104 ms
104 msKlaviyo costs a phone 104 ms of main-thread work and 319 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
200 ms13 files block the first paint until they finish downloading. Deferring or inlining them could save about 200 ms.
5 third-party services on the page
5 third-party services load with your homepage (Klaviyo, Shopify and nfcube.com and others), adding 468 KiB and 139 ms of main-thread time.
Reduce unused JavaScript
130 KiBAbout 130 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
92 KiB6 files are served with short cache lifetimes, so returning visitors download them again (92 KiB).
Legacy JavaScript
24 KiBPolyfills for old browsers add 24 KiB JavaScript that modern phones do not need.
Reduce unused CSS
11 KiBAbout 11 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.
1 checks passed
Server response: 14 ms
14 msYour server sent the HTML in 14 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: 6.2 s
6.2 sYour largest element takes 6.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Jinny Beauty Supply”.
Speed Index: 5.9 s
5.9 sVisually, the page fills in at 5.9 s (Speed Index). Good is under 3.4 s.
Real-user TTFB: 1.0 s
1.0 sReal visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 6.3 s
6.3 sThe page becomes fully interactive after 6.3 s. Good is under 3.8 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.
Tap response (INP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 103 ms to 95 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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 INP: 91 ms
91 msReal visitors wait 91 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 FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 26% faster for real visitors
-26%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.068
0.068The layout barely moves while loading (CLS 0.068, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.4 MB in 261 requests
3.4 MBYour homepage downloads 3.4 MB in 261 requests on a phone: images 1.8 MB (66), other files 747 KiB (98) and scripts 676 KiB (69). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
MU_2.2-MOBILE_3a9905f5-dab6-4c69-a65b-6e31b9cfdfea.jpg 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).
2 images below the first screen load straight away
2 images further down the page (48 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.0 g of CO₂ per visit
0.96 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.96 g of CO₂e: 115.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
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.
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.
Headings should not be empty (3 elements)
Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (4 elements).
2 checks passed
Every image has alt text
All 131 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 5 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 short (19 characters)
Your title is only 19 characters: “Jinny Beauty Supply”. Between 30 and 65 characters leaves room to say what you do and for whom.
Structured data has 1 problem
Structured data found (WebSite) but with 1 problem, for example “ld+json block 1 is not valid JSON (Unexpected token ',', ..."ration\/",,"https:\/"... is not va)”.
11 links with vague text
11 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
One H1 headline
Your <h1> is empty.
838 internal links, 24 external
The homepage links to 838 pages on jinny.com and 24 external pages.
5 checks passed
Meta description: 96 characters
Your meta description is 96 characters: “The BEST and largest multi-cultural and ethnic beauty supply wholesale distributor in the world.”.
Canonical URL set
The canonical URL is https://www.jinny.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://www.jinny.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 (2,927 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.jinny.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
14 pages share a meta description
https://www.jinny.com/pages/dream-world, https://www.jinny.com/pages/customer-information, https://www.jinny.com/collections/all, https://www.jinny.com/collections/jinnybeauty-braids/jinnybeauty, https://www.jinny.com/collections/jinnybeauty-crochet-braids/jinnybeauty and https://www.jinny.com/collections/jinnybeauty-pre-stretched-braids/jinnybeauty and 8 others use the same meta description. A description written for each page earns more clicks.
15 pages without an H1
https://www.jinny.com/pages/dream-world, https://www.jinny.com/pages/urban-beauty, https://www.jinny.com/pages/customer-information, https://www.jinny.com/collections/all, https://www.jinny.com/collections/jinnybeauty-braids/jinnybeauty and https://www.jinny.com/collections/jinnybeauty-crochet-braids/jinnybeauty and 9 others have 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 199 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
85 small tap targets
85 of 218 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Scrolls sideways on phones
On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 (Bad Request)”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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 1,011 words of copy
The homepage carries about 1,011 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn more” and “SHOP ALL”.
25 calls to action
The homepage has 25 calls to action, for example “Learn more”, “Contact Us” and “Create an Order”.
13 short forms
13 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 15 testimonial or review blocks and 2 customer or partner logos.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Klaviyo (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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
15 other companies contacted
Loading the homepage contacts 15 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 jinny.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 33 issues on jinny.com, including 11 speed issues, 5 SEO issues and 2 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.