Website review, no card needed

torraslife.co.jp logo

torraslife.co.jp website review

Visit site (opens in a new tab)Reviewed 16 November 202635 issues · 73 checks

This review found 35 issues worth fixing on torraslife.co.jp, 16 of them high impact, across 73 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.2 s1.4 sMay 30Nov 142.2 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.9 s
Jun 6, 20263.0 s
Jun 13, 20262.8 s
Jun 20, 20262.3 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.0 s
Jul 18, 20261.9 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.7 s
Sep 26, 20261.6 s
Oct 3, 20261.7 s
Oct 10, 20261.8 s
Oct 17, 20262.0 s
Oct 24, 20262.2 s
Oct 31, 20262.3 s
Nov 7, 20262.2 s
Nov 14, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
181 ms112 msMay 30Nov 14120 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026173 ms
Jun 6, 2026173 ms
Jun 13, 2026163 ms
Jun 20, 2026161 ms
Jun 27, 2026161 ms
Jul 4, 2026162 ms
Jul 11, 2026163 ms
Jul 18, 2026158 ms
Jul 25, 2026150 ms
Aug 1, 2026144 ms
Aug 8, 2026139 ms
Aug 15, 2026136 ms
Aug 22, 2026134 ms
Aug 29, 2026133 ms
Sep 5, 2026136 ms
Sep 12, 2026137 ms
Sep 19, 2026137 ms
Sep 26, 2026134 ms
Oct 3, 2026128 ms
Oct 10, 2026126 ms
Oct 17, 2026123 ms
Oct 24, 2026124 ms
Oct 31, 2026124 ms
Nov 7, 2026123 ms
Nov 14, 2026120 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

Full-page screenshot of torraslife.co.jp (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. torraslife.co.jp at 1.1 s1.1 s
  2. torraslife.co.jp at 2.2 s2.2 s
  3. torraslife.co.jp at 3.3 s3.3 s
  4. torraslife.co.jp at 4.4 s4.4 s
  5. torraslife.co.jp at 5.5 s5.5 s
  6. torraslife.co.jp at 6.6 s6.6 s
  7. torraslife.co.jp at 7.7 s7.7 s
  8. torraslife.co.jp at 8.8 s8.8 s

Speed

9 to fix58
  • Render-blocking requests

    1.2 s

    14 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.

  • Main-thread work: 4.8 s

    A phone's processor spends 4.8 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 4,472 HTML elements

    The page has 4,472 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 (Shopify, omnisnippet1.com and Google Tag Manager and others), adding 8.9 MB and 713 ms of main-thread time.

  • Shopify adds 258 ms

    258 ms

    Shopify costs a phone 258 ms of main-thread work and 8.1 MB 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.

  • Mobile performance score: 58

    58/100

    Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    150 ms · 683 KiB

    About 683 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Use efficient cache lifetimes

    372 KiB

    16 files are served with short cache lifetimes, so returning visitors download them again (372 KiB).

  • smile.io adds 50 ms

    50 ms

    smile.io costs a phone 50 ms of main-thread work and 367 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.

  • 6 long tasks on the main thread

    6 long tasks block the main thread while loading, the longest for 209 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    150 ms · 40 KiB

    About 40 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.

  • Improve image delivery

    98 KiB

    6 images could be 98 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 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.

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 33 ms

    33 ms

    Your server sent the HTML in 33 ms, well inside Google's 600 ms guideline.

Core Web Vitals

7 to fix100
  • 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: 43.3 s

    43.3 s

    Your largest element takes 43.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Speed Index: 20.0 s

    20.0 s

    Visually, the page fills in at 20.0 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 59.2 s

    59.2 s

    The page becomes fully interactive after 59.2 s. Good is under 3.8 s.

  • Real-user FCP: 2.2 s

    2.2 s

    Real visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.

  • First Contentful Paint: 2.6 s

    2.6 s

    The first text or image appears after 2.6 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.

8 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

    Real visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 125 ms

    125 ms

    Real visitors wait 125 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user TTFB: 691 ms

    691 ms

    Real visitors wait 691 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Tap response (INP) got 30% faster for real visitors

    -30%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 173 ms to 120 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 26% faster for real visitors

    -26%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.9 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Total Blocking Time: 199 ms

    199 ms

    Scripts block the page for only 199 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.001

    0.001

    The layout barely moves while loading (CLS 0.001, good is under 0.1).

Images and page weight

2 to fix64
  • Page weight: 11.0 MB in 305 requests

    11.0 MB

    Your homepage downloads 11.0 MB in 305 requests on a phone: fonts 7.7 MB (6), scripts 1.5 MB (147) and images 777 KiB (25). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    banner-MB-1_7d2a79e4-99ec-43e8-b0a4-ae69e8a7be84.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.1 g of CO₂ per visit

    3.12 g

    By the Sustainable Web Design model, a visit to your homepage emits about 3.12 g of CO₂e: 374.4 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

7 to fixGoogle 9091
  • Elements must only use permitted ARIA attributes (97 elements)

    Elements must only use permitted ARIA attributes: 97 elements on the page fail this check, rated serious by axe-core.

  • 5 text elements with low contrast

    5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 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.

  • 14 images without alt text

    14 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.

  • 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.

  • Alternative text of images should not be repeated as text (2 elements)

    Alternative text of images should not be repeated as text: 2 elements on the page fail 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. (4 elements).

1 checks passed
  • 51 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 7 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9282
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No XML sitemap

    No XML sitemap at https://torras.co.jp/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at torras.co.jp/robots.txt, the first file search crawlers ask for.

  • 136 internal links, 5 external

    The homepage links to 136 pages on torraslife.co.jp and 5 external pages.

5 checks passed
  • Meta description: 72 characters

    Your meta description is 72 characters: “TORRASのiPhoneケースで、機能性とおしゃれを両立させた究極のデザインを体験。あなたのiPhoneをスタイリッシュに守る、上質な選択を。”.

  • Title: 37 characters

    Your title is a healthy 37 characters: “おしゃれ・高機能なiPhoneケース|TORRAS – TORRAS-JP”.

  • Canonical URL set

    The canonical URL is https://torras.co.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.

AI search readiness

100
  • No llms.txt

    There is no https://torras.co.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
  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (396 words), so crawlers that don't run JavaScript still read it.

Other pages

  • Your server turned our page checks away

    15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.

Best practices

2 to fixGoogle 9687
  • 21 small tap targets

    21 of 74 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://dsp-trk.eskimi.com/tracking/cssession?tst&id=36794&url=https%3A%2F%2Ftorras.co.jp%…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix42
  • 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.

  • 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 267 words of copy

    The homepage carries about 267 words of visible text.

2 checks passed
  • 2 short forms

    2 short forms (2 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before 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.

  • 32 cookies set on arrival

    32

    Opening the homepage sets 32 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.

  • 51 other companies contacted

    Loading the homepage contacts 51 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 torraslife.co.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

Intelligems A B Testing · Redirects By Shopkit · Ryviu Product Reviews · App Unity Tracking Ga4 · Powerful Form Builder · Pagefly Ai Page Builder · Attribuly · Omnisend · Zak Affiliate Marketing And Link · Hulk Product Options

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
Google Tag Manager
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 torraslife.co.jp, including 16 speed issues, 3 SEO issues and 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25