Website review, no card needed
withme-web.jp website review
Visit site (opens in a new tab)Reviewed 16 November 202630 issues · 77 checks
This review found 30 issues worth fixing on withme-web.jp, 11 of them high impact, across 77 checks. The most urgent: main-thread work: 12.5 s. 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
77C- #63,984 of 113,565 reviewed websitesbeats 39%
- #42,172 of 65,507 online storesbeats 30%
- #40,228 of 59,923 Shopify storesbeats 28%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.2 s |
| Jun 20, 2026 | 1.2 s |
| Jun 27, 2026 | 1.2 s |
| Jul 4, 2026 | 1.2 s |
| Jul 11, 2026 | 1.2 s |
| Jul 18, 2026 | 1.2 s |
| Jul 25, 2026 | 1.2 s |
| Aug 1, 2026 | 1.2 s |
| Aug 8, 2026 | 1.2 s |
| Aug 15, 2026 | 1.2 s |
| Aug 22, 2026 | 1.2 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.2 s |
| Sep 12, 2026 | 1.2 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.2 s |
| Oct 10, 2026 | 1.2 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.3 s |
| Oct 31, 2026 | 1.2 s |
| Nov 7, 2026 | 1.2 s |
| Nov 14, 2026 | 1.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 116 ms |
| Jun 6, 2026 | 114 ms |
| Jun 13, 2026 | 110 ms |
| Jun 20, 2026 | 107 ms |
| Jun 27, 2026 | 108 ms |
| Jul 4, 2026 | 106 ms |
| Jul 11, 2026 | 107 ms |
| Jul 18, 2026 | 111 ms |
| Jul 25, 2026 | 114 ms |
| Aug 1, 2026 | 119 ms |
| Aug 8, 2026 | 125 ms |
| Aug 15, 2026 | 127 ms |
| Aug 22, 2026 | 125 ms |
| Aug 29, 2026 | 125 ms |
| Sep 5, 2026 | 124 ms |
| Sep 12, 2026 | 126 ms |
| Sep 19, 2026 | 130 ms |
| Sep 26, 2026 | 132 ms |
| Oct 3, 2026 | 136 ms |
| Oct 10, 2026 | 135 ms |
| Oct 17, 2026 | 132 ms |
| Oct 24, 2026 | 133 ms |
| Oct 31, 2026 | 126 ms |
| Nov 7, 2026 | 120 ms |
| Nov 14, 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
Speed
Main-thread work: 12.5 s
A phone's processor spends 12.5 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
1.1 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 37
37/100Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 2.2 s. During a long task the page ignores taps.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Shopify and Google CDN and others), adding 1.1 MB and 1.6 s of main-thread time.
Google Tag Manager adds 886 ms
886 msGoogle Tag Manager costs a phone 886 ms of main-thread work and 162 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 642 ms
642 msShopify costs a phone 642 ms of main-thread work and 819 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.
Improve image delivery
300 ms · 63 KiB5 images could be 63 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.
2,974 HTML elements
The page has 2,974 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
290 ms · 181 KiBAbout 181 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 290 ms faster on a phone.
Reduce unused CSS
150 ms · 81 KiBAbout 81 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
17 KiBPolyfills for old browsers add 17 KiB JavaScript that modern phones do not need.
Use efficient cache lifetimes
7 KiB5 files are served with short cache lifetimes, so returning visitors download them again (7 KiB).
Minify CSS
6 KiB6 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: 10 ms
10 msYour server sent the HTML in 10 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Total Blocking Time: 4.2 s
4.2 sScripts block taps and scrolling for 4.2 s in total while the page loads. Good is under 200 ms.
Speed Index: 11.7 s
11.7 sVisually, the page fills in at 11.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 13.1 s
13.1 sThe page becomes fully interactive after 13.1 s. Good is under 3.8 s.
Largest Contentful Paint: 5.9 s
5.9 sYour largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “老舗ジュエラーが創る、 高品質で手の届く結婚指輪・婚約指輪。 サンプルを無料でお貸出ししております。 ご自宅でごゆっく…”. Most of its time is element render delay (6.8 s).
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
19 images without width and height
19 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 116 ms to 111 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 116 ms
116 msReal visitors wait 116 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.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 347 ms
347 msReal visitors wait 347 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.2 MB in 233 requests
2.2 MBYour homepage downloads 2.2 MB in 233 requests on a phone: scripts 933 KiB (128), other files 761 KiB (59) and images 304 KiB (14). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (20 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.6 g of CO₂ per visit
0.63 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.63 g of CO₂e: 75.1 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
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
5 images without alt text
5 images have no alt text, which hurts accessibility and image search.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
14 links without text
14 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 4 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 (17 characters)
Your title is only 17 characters: “ネットで選んで自宅で試せる結婚指輪”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is short (62 characters)
Your meta description is only 62 characters: “オンライン専門。高品質で低価格な結婚指輪。自宅で試せるサンプルリングを無料貸出ししております。セカンドマリッジリングにも◎。”. 70 to 160 characters is enough to sell the click.
One H1 headline
Your <h1> is empty.
86 internal links, 3 external
The homepage links to 86 pages on withme-web.jp and 3 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://withme-web.jp/.
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://withme-web.jp/sitemap.xml.
AI search readiness
No llms.txt
There is no https://withme-web.jp/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
2 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 description; contact details would complete it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 31 found) and read each the way a search engine does.
7 checks passed
Linked pages load
1 page 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.
Every page has a meta description
All 1 page that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 1 page that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were 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
23 of 28 tappable elements near the top are at least 24 px.
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.
Thin social proof
Social proof on the homepage: 138 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 59 words
The homepage has only about 59 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: Google Analytics.
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 Meta Pixel (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.
23 other companies contacted
Loading the homepage contacts 23 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 withme-web.jp, 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 10 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Judge Me Reviews · Powerful Form Builder · Inbox · Pagefly Ai Page Builder · Globo Product Options · Yuko Order Limits · Mobilemenu · Qikify Timer Announcement Bar · synctrack.io · nfcube.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
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on withme-web.jp, including 15 speed issues, 3 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.