Website review, no card needed
angelux-online.com website review
Visit site (opens in a new tab)Reviewed 10 November 202642 issues · 88 checks
This review found 42 issues worth fixing on angelux-online.com, 16 of them high impact, across 88 checks. The most urgent: reduce unused JavaScript. 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- #82,597 of 126,442 reviewed websitesbeats 30%
- #51,992 of 70,471 online storesbeats 22%
- #49,000 of 63,972 Shopify storesbeats 19%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 2.0 s |
| Nov 7, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 105 ms |
| May 30, 2026 | 107 ms |
| Jun 6, 2026 | 107 ms |
| Jun 13, 2026 | 107 ms |
| Jun 20, 2026 | 108 ms |
| Jun 27, 2026 | 107 ms |
| Jul 4, 2026 | 109 ms |
| Jul 11, 2026 | 109 ms |
| Jul 18, 2026 | 107 ms |
| Jul 25, 2026 | 109 ms |
| Aug 1, 2026 | 107 ms |
| Aug 8, 2026 | 110 ms |
| Aug 15, 2026 | 110 ms |
| Aug 22, 2026 | 111 ms |
| Aug 29, 2026 | 112 ms |
| Sep 5, 2026 | 112 ms |
| Sep 12, 2026 | 113 ms |
| Sep 19, 2026 | 113 ms |
| Sep 26, 2026 | 113 ms |
| Oct 3, 2026 | 114 ms |
| Oct 10, 2026 | 116 ms |
| Oct 17, 2026 | 114 ms |
| Oct 24, 2026 | 114 ms |
| Oct 31, 2026 | 112 ms |
| Nov 7, 2026 | 111 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.7 s
1.4 s
2.0 s
2.7 s
3.4 s
4.1 s
4.7 s
5.4 s
Speed
Reduce unused JavaScript
4.5 s · 1.6 MBAbout 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.5 s faster on a phone.
Use efficient cache lifetimes
2.5 s · 457 KiB23 files are served with short cache lifetimes, so returning visitors download them again (457 KiB).
Render-blocking requests
1.3 s10 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
8 third-party services on the page
8 third-party services load with your homepage (revico.jp, pages.dev and Clarity and others), adding 1.6 MB and 867 ms of main-thread time.
Mobile performance score: 66
66/100Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
300 ms · 307 KiB13 images could be 307 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Reduce unused CSS
450 ms · 86 KiBAbout 86 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Main-thread work: 3.4 s
A phone's processor spends 3.4 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
revico.jp adds 298 ms
298 msrevico.jp costs a phone 298 ms of main-thread work and 84 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.
2,183 HTML elements
The page has 2,183 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
pages.dev adds 138 ms
138 mspages.dev costs a phone 138 ms of main-thread work and 363 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.
Shopify adds 92 ms
92 msShopify costs a phone 92 ms of main-thread work and 618 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.
Minify JavaScript
150 ms · 154 KiB154 KiB could be saved by minifying JavaScript.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 167 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify CSS
12 KiB12 KiB could be saved by minifying CSS.
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: 5 ms
5 msYour server sent the HTML in 5 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: 17.3 s
17.3 sYour largest element takes 17.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “image”.
Time to Interactive: 21.2 s
21.2 sThe page becomes fully interactive after 21.2 s. Good is under 3.8 s.
Speed Index: 8.4 s
8.4 sVisually, the page fills in at 8.4 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 105 ms to 111 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.8 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user INP: 99 ms
99 msReal visitors wait 99 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.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 498 ms
498 msReal visitors wait 498 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 110 ms
110 msScripts block the page for only 110 ms while loading. Good is under 200 ms.
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.
Cumulative Layout Shift: 0.03
0.03The layout barely moves while loading (CLS 0.03, good is under 0.1).
Images and page weight
Page weight: 4.3 MB in 307 requests
4.3 MBYour homepage downloads 4.3 MB in 307 requests on a phone: scripts 1.9 MB (71), other files 808 KiB (115) and images 754 KiB (52). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
article_PC_thumbnail_h2_new_sub.png 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).
4 images below the first screen load straight away
4 images further down the page (133 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.2 g of CO₂ per visit
1.21 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.21 g of CO₂e: 145.3 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
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
20 text elements with low contrast
20 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
50 form fields without a label
50 form fields have no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (20 elements)
ARIA role should be appropriate for the element: 20 elements on the page fail this check, rated minor by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
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 67 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 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 8 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
One H1 headline
Your <h1> is empty.
159 internal links, 5 external
The homepage links to 159 pages on angelux-online.com and 5 external pages.
6 checks passed
Meta description: 101 characters
Your meta description is 101 characters: “スキンケアは裏切らない。洗顔、クレンジング、角質ケアなど毎日のスキンケアに必要なアイテムをラインナップ。オリジナルブランド「My NADESHICO」シリーズをはじめ、各種セレクト商品を販売しています。”.
Title: 37 characters
Your title is a healthy 37 characters: “スキンケア製品のオンラインストア – MY NADESHICO Store”.
Canonical URL set
The canonical URL is https://mynadeshico.com/.
Structured data in place
Structured data found: Organization and WebSite.
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://mynadeshico.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://mynadeshico.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
5 pages without a meta description
https://mynadeshico.com/blogs/importantnotice, https://mynadeshico.com/collections/all-products-2, https://mynadeshico.com/collections/monthly, https://mynadeshico.com/collections/starter and https://mynadeshico.com/collections/m_select have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://mynadeshico.com/collections/all-products-2, whose canonical is https://mynadeshico.com/collections/all. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
14 pages without an H1
https://mynadeshico.com/collections/all-products-2, https://mynadeshico.com/collections/monthly, https://mynadeshico.com/collections/starter, https://mynadeshico.com/collections/m_select, https://mynadeshico.com/collections/subscription and https://mynadeshico.com/collections/gifttools and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 pages with very little text
https://mynadeshico.com/blogs/importantnotice, https://mynadeshico.com/collections/all-products-2, https://mynadeshico.com/collections/monthly, https://mynadeshico.com/collections/starter, https://mynadeshico.com/collections/m_select and https://mynadeshico.com/collections/subscription and 9 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.
8 pages slow to respond
https://mynadeshico.com/collections/all-products-2, https://mynadeshico.com/collections/m_select, https://mynadeshico.com/collections/subscription, https://mynadeshico.com/collections/gifttools, https://mynadeshico.com/collections/cleansing-facewash and https://mynadeshico.com/collections/exfoliationcare and 2 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 68 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
17 small tap targets
17 of 43 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Invalid regular expression: missing /”.
1 checks passed
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.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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 122 words
The homepage has only about 122 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.
2 checks passed
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
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, 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.
17 cookies set on arrival
17Opening the homepage sets 17 cookies, 1 of them by other companies (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.
37 other companies contacted
Loading the homepage contacts 37 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 angelux-online.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 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pagefly Ai Page Builder · Omnisend · Forms · Promolayer · Subscription Test · firebaseapp.com · amp-cdn.tokyo · pages.dev · amazonaws.com · mixlogue.jp · useamp.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
- 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 42 issues on angelux-online.com, including 18 speed issues, 2 SEO issues and 5 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.