Website review, no card needed
ourhome305.com website review
Visit site (opens in a new tab)Reviewed 10 November 202642 issues · 89 checks
This review found 42 issues worth fixing on ourhome305.com, 17 of them high impact, across 89 checks. The most urgent: page weight: 11.1 MB in 429 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
73C- #81,314 of 109,350 reviewed websitesbeats 22%
- #50,750 of 61,859 online storesbeats 15%
- #47,561 of 56,401 Shopify storesbeats 13%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.4 s |
| Nov 7, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 112 ms |
| May 30, 2026 | 112 ms |
| Jun 6, 2026 | 113 ms |
| Jun 13, 2026 | 115 ms |
| Jun 20, 2026 | 114 ms |
| Jun 27, 2026 | 116 ms |
| Jul 4, 2026 | 118 ms |
| Jul 11, 2026 | 119 ms |
| Jul 18, 2026 | 121 ms |
| Jul 25, 2026 | 120 ms |
| Aug 1, 2026 | 119 ms |
| Aug 8, 2026 | 118 ms |
| Aug 15, 2026 | 118 ms |
| Aug 22, 2026 | 118 ms |
| Aug 29, 2026 | 120 ms |
| Sep 5, 2026 | 121 ms |
| Sep 12, 2026 | 121 ms |
| Sep 19, 2026 | 122 ms |
| Sep 26, 2026 | 121 ms |
| Oct 3, 2026 | 122 ms |
| Oct 10, 2026 | 123 ms |
| Oct 17, 2026 | 123 ms |
| Oct 24, 2026 | 123 ms |
| Oct 31, 2026 | 121 ms |
| Nov 7, 2026 | 119 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
Mobile performance score: 45
45/100Your mobile performance score is 45. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.4 s
A phone's processor spends 7.4 s on main-thread work while loading, 3.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,278 HTML elements
The page has 3,278 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (channel.io, Clarity and storecrm.com and others), adding 1.2 MB and 1.1 s of main-thread time.
Improve image delivery
450 ms · 611 KiB22 images could be 611 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
Reduce unused JavaScript
600 ms · 374 KiBAbout 374 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Render-blocking requests
850 ms10 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
channel.io adds 389 ms
389 mschannel.io costs a phone 389 ms of main-thread work and 349 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.
storecrm.com adds 260 ms
260 msstorecrm.com costs a phone 260 ms of main-thread work and 74 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 261 ms
261 msClarity costs a phone 261 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.
leeep.jp adds 49 ms
49 msleeep.jp costs a phone 49 ms of main-thread work and 479 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.
Font display
250 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 156 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
126 KiB15 files are served with short cache lifetimes, so returning visitors download them again (126 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: 11 ms
11 msYour server sent the HTML in 11 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: 21.2 s
21.2 sYour largest element takes 21.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 46.5 s
46.5 sThe page becomes fully interactive after 46.5 s. Good is under 3.8 s.
Speed Index: 8.6 s
8.6 sVisually, the page fills in at 8.6 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.262
0.262The layout shifts by 0.262 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user CLS: 0.20
0.20For real visitors the layout shifts by 0.20 (75th percentile). Good is under 0.1.
Total Blocking Time: 308 ms
308 msScripts block taps and scrolling for 308 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 112 ms to 119 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 135 ms
135 msReal visitors wait 135 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 340 ms
340 msReal visitors wait 340 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 11.1 MB in 429 requests
11.1 MBYour homepage downloads 11.1 MB in 429 requests on a phone: images 4.8 MB (116), fonts 4.0 MB (5) and other files 1.2 MB (205). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
slide_bannerSL_03_shop_slider.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).
19 images below the first screen load straight away
19 images further down the page (1.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
3 images in older formats
3 images (210 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
About 3.1 g of CO₂ per visit
3.14 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.14 g of CO₂e: 376.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
4 buttons without a name
4 buttons have no accessible name, so screen readers announce just “button”.
ARIA attributes must conform to valid values (2 elements)
ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
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.
27 images without alt text
27 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
34 links without text
34 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 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. (3 elements).
1 checks passed
48 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: 48 passed and 9 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 2 problems
Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: sameAs is not an absolute URL ("/")”.
8 links crawlers can't follow
8 links have no real href, so search engines can't follow them.
One H1 headline
Your <h1> is empty.
268 internal links, 38 external
The homepage links to 268 pages on ourhome305.com and 38 external pages.
6 checks passed
Meta description: 109 characters
Your meta description is 109 characters: “OURHOME(アワーホーム)は、Emi主宰の“ちょうどいい”暮らしとオリジナルウエアのお店。おかげさまで11周年◎兵庫・西宮北口に実店舗も。インテリア/ウエア/バッグ/アクセサリー/スキンケア/手帳/写真整理を展開。”.
Title: 35 characters
Your title is a healthy 35 characters: “OURHOME(アワーホーム) - 暮らしの発信とオリジナル商品のお店”.
Canonical URL set
The canonical URL is https://ourhome305.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://ourhome305.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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (435 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://ourhome305.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
11 pages without a meta description
https://ourhome305.com/apps/obake/favorites, https://ourhome305.com/pages/ourhome-monodukuri, https://ourhome305.com/pages/ourhome-no-kurashi, https://ourhome305.com/pages/about-emi, https://ourhome305.com/collections/wear and https://ourhome305.com/collections/bags and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
12 pages without an H1
https://ourhome305.com/apps/obake/favorites, https://ourhome305.com/collections/all, https://ourhome305.com/collections/wear, https://ourhome305.com/collections/inner, https://ourhome305.com/collections/bags and https://ourhome305.com/collections/shoes and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages with very little text
https://ourhome305.com/apps/obake/favorites, https://ourhome305.com/pages/ourhome-monodukuri, https://ourhome305.com/pages/ourhome-no-kurashi and https://ourhome305.com/pages/about-emi 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 100 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.
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
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
2 checks passed
Tap targets are thumb-sized
45 of 54 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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 351 words of copy
The homepage carries about 351 words of visible text.
3 checks passed
7 calls to action
The homepage has 7 calls to action, for example “ONLINE SHOP”, “SHOP&EVENT” and “sold out みんなで!どこでもOURHOME SHOP 0円(税込0円)”.
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
4 trackers load before any consent
4Before a visitor clicks anything, the page loads 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.
13 cookies set on arrival
13Opening the homepage sets 13 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.
26 other companies contacted
Loading the homepage contacts 26 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 ourhome305.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
Order Limits · Page Speed Booster · Helium Customer Fields · Leeep Ugc · Tipo Related Products · Quick Link · Globo Also Bought Cross Sell · Raffle · amp-cdn.tokyo · mixlogue.jp · storecrm.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 ourhome305.com, including 20 speed issues, 3 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.