Website review, no card needed
kior.com website review
Visit site (opens in a new tab)Reviewed 22 November 202612 issues · 70 checks
This review found 12 issues worth fixing on kior.com, 3 of them high impact, across 70 checks. The most urgent: 8 tap targets too small. 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
97A- #12 of 126,442 reviewed websitesbeats 100%
- #4 of 70,471 online storesbeats 100%
- #4 of 63,968 Shopify storesbeats 100%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.2 s |
| Aug 8, 2026 | 1.4 s |
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
Render-blocking requests
900 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Reduce unused CSS
28 KiBAbout 28 KiB of CSS is downloaded but never applied on this page.
4 third-party services on the page
4 third-party services load with your homepage (Shopify, Google Tag Manager and shop.app and others), adding 211 KiB and 5 ms of main-thread time.
Use efficient cache lifetimes
9 KiB4 files are served with short cache lifetimes, so returning visitors download them again (9 KiB).
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.
3 checks passed
Mobile performance score: 100
100/100Your mobile performance score is 100. That is in Google's “good” band (90 and up).
Main-thread work: 0.4 s
A phone's processor spends 0.4 s on main-thread work while loading, 39 ms of it running JavaScript. That is comfortably low.
Server response: 11 ms
11 msYour server sent the HTML in 11 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest content (LCP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.
6 checks passed
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Largest Contentful Paint: 1.2 s
1.2 sYour largest element renders in 1.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “🔄”.
Speed Index: 1.4 s
1.4 sVisually, the page fills in at 1.4 s (Speed Index), inside the 3.4 s “good” threshold.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Time to Interactive: 1.2 s
1.2 sThe page is fully interactive after 1.2 s.
Images and page weight
An image on the first screen is lazy-loaded
Copy_of_Untitled_2000_x_980_px_1200_x_628_px_1200_x_1200_px_ 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 0.2 g of CO₂ per visit
0.21 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.21 g of CO₂e: 25.4 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: 764 KiB in 44 requests
764 KiBYour homepage downloads 764 KiB in 44 requests on a phone: scripts 346 KiB (22), images 231 KiB (13) and HTML 74 KiB (1). That is a lean page.
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
8 tap targets too small
8 tap targets are too small or too close together to hit reliably with a finger.
Elements must only use permitted ARIA attributes (6 elements)
Elements must only use permitted ARIA attributes: 6 elements on the page fail this check, rated serious by axe-core.
Scrollable region must have keyboard access (2 elements)
Scrollable region must have keyboard access: 2 elements on the page fail 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.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 29 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
66 internal links, 11 external
The homepage links to 66 pages on kior.com and 11 external pages.
8 checks passed
Meta description: 136 characters
Your meta description is 136 characters: “Shop Kior's Ozone high frequency wand and at-home IPL hair removal. Made for sensitive skin. 30-day returns. Ships to t…”.
One H1 headline
Your main headline reads: “Kior High Frequency Wand & At-Home IPL Hair Removal”.
Title: 45 characters
Your title is a healthy 45 characters: “Kior | High Frequency Wand & IPL Hair Removal”.
Canonical URL set
The canonical URL is https://kior.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization 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://kior.com/sitemap.xml.
AI search readiness
4 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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (905 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://kior.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://kior.com/blogs/news/tagged/high-frequency-wand is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
https://kior.com/blogs/news and https://kior.com/blogs/news/tagged/high-frequency-wand all use the title “Kior Blog | High Frequency Wand & IPL Hair Removal Tips”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://kior.com/blogs/news and https://kior.com/blogs/news/tagged/high-frequency-wand 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 21 found) and read each the way a search engine does.
5 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.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
21 of 25 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 map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
About 767 words of copy
The homepage carries about 767 words of visible text.
8 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW”.
21 calls to action
The homepage has 21 calls to action, for example “Shop”, “Contact Us” and “Track your order”.
8 short forms
8 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, 1 customer or partner logo and a star rating.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Hotjar.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
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.
7 cookies set on arrival
7Opening the homepage sets 7 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.
4 other companies contacted
Loading the homepage contacts 4 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 kior.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 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Judge Me Reviews · Doran Shoppable Videos · Nova Multi Currency Converter · nfcube.com · goaffpro.com
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
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Hotjar
- Hosting
- Shopify
Company
- Headquarters
- Pasadena
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 12 issues on kior.com, including 1 speed issue, 1 SEO issue and 1 conversion gap. 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.