Website review, no card needed
riene-nail.com website review
Visit site (opens in a new tab)Reviewed 10 November 202635 issues · 76 checks
This review found 35 issues worth fixing on riene-nail.com, 11 of them high impact, across 76 checks. The most urgent: page weight: 12.1 MB in 363 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
81B- #36,446 of 107,323 reviewed websitesbeats 60%
- #24,255 of 60,666 online storesbeats 54%
- #23,400 of 55,328 Shopify storesbeats 51%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Aug 22, 2026 | 680 ms |
| Aug 29, 2026 | 709 ms |
| Sep 5, 2026 | 700 ms |
| Oct 31, 2026 | 982 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
Main-thread work: 7.0 s
A phone's processor spends 7.0 s on main-thread work while loading, 2.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
8.9 MB30 images could be 8.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
50 ms · 1.7 MB58 files are served with short cache lifetimes, so returning visitors download them again (1.7 MB).
8 third-party services on the page
8 third-party services load with your homepage (buyee.jp, Clarity and Shopify and others), adding 1.3 MB and 1.3 s of main-thread time.
Mobile performance score: 68
68/100Your mobile performance score is 68. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
850 ms12 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
Reduce unused JavaScript
300 ms · 276 KiBAbout 276 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
buyee.jp adds 348 ms
348 msbuyee.jp costs a phone 348 ms of main-thread work and 391 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.
Clarity adds 258 ms
258 msClarity costs a phone 258 ms of main-thread work and 29 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.
juicer.cc adds 171 ms
171 msjuicer.cc costs a phone 171 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.
1,765 HTML elements
The page has 1,765 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 168 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 18 KiB18 KiB could be saved by minifying JavaScript.
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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
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
Time to Interactive: 18.3 s
18.3 sThe page becomes fully interactive after 18.3 s. Good is under 3.8 s.
Speed Index: 10.5 s
10.5 sVisually, the page fills in at 10.5 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 5.0 s
5.0 sYour largest element takes 5.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Largest content (LCP) got 21% slower for real visitors
+21%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 0.7 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
26 images without width and height
26 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 218 ms
218 msScripts block taps and scrolling for 218 ms in total while the page loads. Good is under 200 ms.
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
First Contentful Paint: 1.3 s
1.3 sThe first text or image appears after 1.3 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.018
0.018The layout barely moves while loading (CLS 0.018, good is under 0.1).
Images and page weight
Page weight: 12.1 MB in 363 requests
12.1 MBYour homepage downloads 12.1 MB in 363 requests on a phone: images 10.0 MB (84), scripts 1,006 KiB (70) and other files 935 KiB (167). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
DSC01469.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).
About 3.4 g of CO₂ per visit
3.42 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.42 g of CO₂e: 411.0 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
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Orphan list items
Some list items are not inside a list.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
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.
Alternative text of images should not be repeated as text (3 elements)
Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 49 images in the HTML carry an alt attribute.
46 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: 46 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
One H1 headline
Your <h1> is empty.
60 internal links, 1 external
The homepage links to 60 pages on riene-nail.com and 1 external page.
7 checks passed
Meta description: 82 characters
Your meta description is 82 characters: “簡単な質問に答えるだけで、ピッタリなネイルカラーとブラシをお届けするパーソナライズネイル「Riéne（リエネ）」大切な自分だけのSTORYに、自分らしいCOLORを”.
Title: 45 characters
Your title is a healthy 45 characters: “パーソナライズ ネイル｜Riéne（リエネ） – Riéne official store”.
Canonical URL set
The canonical URL is https://riene-nail.com/.
Structured data in place
Structured data found: 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://riene-nail.com/sitemap.xml.
AI search readiness
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://riene-nail.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
4 pages without a meta description
https://riene-nail.com/pages/faq, https://riene-nail.com/collections/nail-polish, https://riene-nail.com/collections/manicure and https://riene-nail.com/collections/e-gift-card have no meta description, so Google writes the search snippet from whatever text it finds.
8 pages without an H1
https://riene-nail.com/collections, https://riene-nail.com/pages/about, https://riene-nail.com/pages/faq, https://riene-nail.com/pages/contact, https://riene-nail.com/pages/check-up and https://riene-nail.com/collections/nail-polish and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
13 pages with very little text
https://riene-nail.com/blogs/information/free-ship, https://riene-nail.com/collections, https://riene-nail.com/pages/about, https://riene-nail.com/pages/faq, https://riene-nail.com/pages/contact and https://riene-nail.com/pages/check-up and 7 others have 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 30 found) and read each the way a search engine does.
5 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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 14 pages that loaded have a <title>.
Best practices
17 small tap targets
17 of 27 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://riene-nail.com/cdn/shop/t/28/assets/multicolumn-circle.css?v=4031' because its MIM…”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 86 words
The homepage has only about 86 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “パーソナルネイル診断 START”.
3 calls to action
The homepage has 3 calls to action, for example “CONTACT” and “パーソナルネイル診断 START”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Tag Manager, Meta Pixel and Microsoft Clarity (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.
16 cookies set on arrival
16Opening the homepage sets 16 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.
36 other companies contacted
Loading the homepage contacts 36 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 riene-nail.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
Gsc Product Labels Badges · Gsc Instagram Feed · King Product Options · Gsc Affiliate External Links · Promolayer
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
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on riene-nail.com, including 17 speed issues, 1 SEO issue and 3 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.